eHealth Infrastructure (v2019.5.3)
An EpisodeOfCare is an association between a patient and an organization / healthcare provider(s) during which time encounters may occur.
In scope of the eHealth infrastructure, creation of an EpisodeOfCare resource is triggered by a number of actions taking place out-of-band, that is, outside the scope of the eHealth infrastructure. Firstly, a patient is diagnosed with one or more conditions; then assessed as fulfilling criteria for enrollment in a telemedical care program leading to a referral being made to an organization providing such program. At this point a Practitioner within the providing organization creates an EpisodeOfCare referring to the Patient and the corresponding Conditions, all in the eHealth infrastructure. Created with status draft, the Practitioner updates the status to active once:
The EpisodeOfCare functions as a representation of a program while the activities comprising it are defined in one or more CarePlan resources.
An EpisodeOfCare is required to have at least one care manager (Danish: “Behandlingsansvarlig”) at any time. The careManagers element states who is the current care manager.
Historical care managers are referenced from the careManagerHistory element together with the period during which they were current.
An EpisodeOfCare can have a number of responsible CareTeams, Practitioners or Organizations with different roles who are responsible for monitoring different aspects of the EpisodeOfCare. For instance a Practitioner could have the role of “monitoringResponsible”. All responsibles referenced from element responsible currently hold the responsibility defined by their role.
Historically responsible CareTeams, Practitioners or Organizations are referenced from element responsibleHistory. This structure is identical to values of the responsible element except that entries in responsibleHistory also carry a “period” which states the period during which the referenced party was responsible for the EpisodeOfCare.
The official URL for this profile is:
http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-episodeofcare
This profile builds on EpisodeOfCare.
This profile was published on Fri Jun 07 11:10:06 UTC 2019 as a draft by ehealth.sundhed.dk.
Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.
| Path | Name | Conformance | ValueSet |
| EpisodeOfCare.language | Common Languages | extensible | Common Languages |
| EpisodeOfCare.status | EpisodeOfCareStatus | required | EpisodeOfCareStatus |
| EpisodeOfCare.statusHistory.status | EpisodeOfCareStatus | required | EpisodeOfCareStatus |
| EpisodeOfCare.type | EpisodeOfCareType | example | EpisodeOfCareType |
| EpisodeOfCare.diagnosis.role | DiagnosisRole | preferred | DiagnosisRole |
| Id | Path | Details | Requirements |
| dom-2 | EpisodeOfCare | If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty() | |
| dom-1 | EpisodeOfCare | If the resource is contained in another resource, it SHALL NOT contain any narrative : contained.text.empty() | |
| dom-4 | EpisodeOfCare | If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated : contained.meta.versionId.empty() and contained.meta.lastUpdated.empty() | |
| dom-3 | EpisodeOfCare | If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource : contained.where(('#'+id in %resource.descendants().reference).not()).empty() | |
| ele-1 | EpisodeOfCare.statusHistory | All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count()) | |
| ele-1 | EpisodeOfCare.diagnosis | All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count()) |
