- 1 EpisodeOfCare
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
Owning committee name
Contributing or Reviewing Work Groups
- Patient Care
- Financial Management
FHIR Resource Development Project Insight ID
Scope of coverage
The EpisodeOfCare Resource contains information about an association of a Patient with a Healthcare Provider for a period of time under which related healthcare activities may occur.
This may include information such as:
- Practitioners (and roles)
- Care Team
- Care Manager/Care co-ordinator
- Funding Sources (Government Agencies/Health Insurers/Individual payers/Guarantors)
- Contact information
- Status information
- Referral source
- other episodes of care
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.
Note: The primary difference between the EpisodeOfCare and the Encounter is that the Encounter records the details of an activity directly relating to the patient, while the EpisodeOfCare is the container that can link a series of Enounters together for a specific problem/issue.
These resources are typically known in existing systems as:
- EpisodeOfCare: Case, Program, Problem
- Encounter: Visit, Contact
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 Episode Of Care 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, healthcare provider and a reason for the ongoing association.
Other reasons for creating an EpisodeOfCare could be for tracking the details required for government reporting or billing.
This resource is likely to be implemented by applications:
- 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)
We will refer to the HL7 v2, v3 and OpenEHR messages and models.
A General Practitioner wants to review how well his patient is managing his diabetes over time from information within his clinic and also the regional community care organization's system(s).
The Episode Of Care enables him to easily separate the diabetes activities from the mental health problem's activities.
A Community Care organization wants to track all activities that occur with a patient relating to their disability to simplify the reporting to the government to receive funding to care for the patient.
This resource is expected to reference Patient, Location, Organization and Practitioner.
Resources that are expected to reference the EpisodeOfCare are: Appointment, Encounter, Coverage and CarePlan.
Other draft resources such as Claim and Invoice may also reference the EpisodeOfCare resource.
We are hoping that this resource will be ready for inclusion in the next Ballot (expecting September 2014).