The [EpisodeOfCare](/content/docs/api/fhir/resources/episodeofcare/index.html) Resource contains information about an association of a [Patient](/content/docs/api/fhir/resources/patient/index.html) with a Healthcare Provider for a period of time under which related healthcare activities may occur.

In many cases, this represents a period of time where the Healthcare Provider has some level of responsibility for the care of the patient regarding a specific condition or problem, even if not currently participating in an encounter.

These resources are typically known in existing systems as:

- EpisodeOfCare: Case, Program, Problem, Episode
- Encounter: Visit, Contact

### Multiple [Organizations](/content/docs/api/fhir/resources/organization/index.html) and Transfer of Care

Many organizations can be involved in an [EpisodeOfCare](/content/docs/api/fhir/resources/episodeofcare/index.html); however each organization will have its own [EpisodeOfCare](/content/docs/api/fhir/resources/episodeofcare/index.html) resource instance that tracks its responsibility with the patient.

When an [Organization](/content/docs/api/fhir/resources/organization/index.html) completes their involvement with the patient and transfers care to another [Organization](/content/docs/api/fhir/resources/organization/index.html). This is often in the form of a referral to another [Organization](/content/docs/api/fhir/resources/organization/index.html) (or [Organizations](/content/docs/api/fhir/resources/organization/index.html)).

When an incoming referral is received a new [EpisodeOfCare](/content/docs/api/fhir/resources/episodeofcare/index.html) may be created for this organization. The initial step(s) in the intake workflow for the referral often involve some form of assessment(s), eligibility, capacity, care levels, which could take some time.

Once the intake process is completed and the patient is accepted, a [CarePlan](/content/docs/api/fhir/resources/careplan/index.html) is often created.

The primary difference between the [EpisodeOfCare](/content/docs/api/fhir/resources/episodeofcare/index.html) and the [Encounter](/content/docs/api/fhir/resources/encounter/index.html) is that the [Encounter](/content/docs/api/fhir/resources/encounter/index.html) records the details of an activity directly relating to the patient, while the [EpisodeOfCare](/content/docs/api/fhir/resources/episodeofcare/index.html) is the container that can link a series of [Encounters](/content/docs/api/fhir/resources/encounter/index.html) together for problems/issues.

The Example scenarios below give some good examples as to when you might want to be using an [EpisodeOfCare](/content/docs/api/fhir/resources/episodeofcare/index.html).

This difference is a similar difference between the [EpisodeOfCare](/content/docs/api/fhir/resources/episodeofcare/index.html) and a [CarePlan](/content/docs/api/fhir/resources/careplan/index.html). The [EpisodeOfCare](/content/docs/api/fhir/resources/episodeofcare/index.html) is a tracking resource, rather than a planning resource.

The [EpisodeOfCare](/content/docs/api/fhir/resources/episodeofcare/index.html) usually exists before the [CarePlan](/content/docs/api/fhir/resources/careplan/index.html). You don't need a [CarePlan](/content/docs/api/fhir/resources/careplan/index.html) to use an [EpisodeOfCare](/content/docs/api/fhir/resources/episodeofcare/index.html).

Systems collect a coherent group of activities (such as encounters) related to a patient's health condition or problem often referred to as a Care Episode. Information about an episode is often shared across systems, and in some cases organizational and disciplinary boundaries. An [EpisodeOfCare](/content/docs/api/fhir/resources/episodeofcare/index.html) contains details about the purpose of the care and can exist without any activities.

The minimal information that would be required in an episode of care would be a patient, organization and a reason for the ongoing association. Other reasons for creating an [EpisodeOfCare](/content/docs/api/fhir/resources/episodeofcare/index.html) could be for tracking the details required for government reporting or billing.

### Expected Implementations

- Chronic Disease Management Systems
- Community Care Systems
- Tracking progress of a specific condition
- Tracking government funding
- Problem based General Practice systems
- Disability Support Systems
- Aged Care Systems (Community and Residential)

- [ChargeItem](/content/docs/api/fhir/resources/chargeitem/index.html)  
- [Contract](/content/docs/api/fhir/resources/contract/index.html)  
- [DocumentReference](/content/docs/api/fhir/resources/documentreference/index.html)  
- [Encounter](/content/docs/api/fhir/resources/encounter/index.html)  
- [MedicationAdministration](/content/docs/api/fhir/resources/medicationadministration/index.html)  
- [MedicationDispense](/content/docs/api/fhir/resources/medicationdispense/index.html)  
- [MedicationStatement](/content/docs/api/fhir/resources/medicationstatement/index.html)

- [Elements](/content/docs/api/fhir/resources/episodeofcare#elements/index.html)  
- [Search Parameters](/content/docs/api/fhir/resources/episodeofcare#search-parameters/index.html)  
- [Inherited Elements](/content/docs/api/fhir/resources/episodeofcare#inherited-elements/index.html)