EpisodeOfCare
Readiness: In review.
Open EpisodeOfCare profile on Simplifier
Profile base: FHIR R4 EpisodeOfCare. The selected no-basis 2.2.2 package has no EpisodeOfCare profile.
Design choices
EpisodeOfCare groups activity under a defined organisational responsibility over time. A treatment request describes intended work; an episode describes the responsibility within which that work may occur. This distinction is why an episode is not required merely to connect a request, booking and contact.
The model avoids both one episode per appointment and one universal lifetime episode. Its identity follows the represented responsibility, not a calendar year, clinician, room or EHR supplier.
Use in practice
In the recall-to-treatment scenario, one general-care responsibility covers examination and later restoration. Completing the restoration does not end that continuing responsibility.
A referral can lead to a separate responsibility at the receiving organisation while the sender's responsibility continues. The two organisations need not share one episode identity. Ending an episode should reflect the end of that responsibility rather than the completion of one procedure.
For historical data, establish the responsibility and its boundaries from the source. Patient, organisation and nearby dates alone do not prove that records belong to one episode. The example catalogue includes planning without EpisodeOfCare as well as the complete care scenario.
EHDS and later FHIR versions
The EHDS Care plan model describes intended care, activities and goals. It should not be treated as a direct equivalent of organisational responsibility. An EHDS mapping must identify the requested plan information separately rather than rename EpisodeOfCare as CarePlan.
FHIR R5 EpisodeOfCare changes diagnosis representation, adds reasons and renames team to careTeam. These affect a future field mapping, while the distinction between responsibility and an individual contact remains useful. See the shared assessment.