eHealth Infrastructure
3.0.0 - release

eHealth Infrastructure - Local Development build (v3.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Resource Profile: ehealth-episodeofcare

Official URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-episodeofcare Version: 3.0.0
Active as of 2024-05-16 Computable Name: ehealth-episodeofcare

Introduction

An EpisodeOfCare is an association between a patient and an organization / healthcare provider(s) during which time encounters may occur.

Scope and Usage

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 planned, the Practitioner updates the status to active once:

  • a Consent to enroll in the program has been given by the Patient
  • Adjustments have possibly been made to assigned CareTeam(s) in team.

The EpisodeOfCare functions as a representation of a program while the activities comprising it are defined in one or more CarePlan resources.

careManagerOrganization and managingOrganization

An EpisodeOfCare is required to have exactly one reference to the Organization responsible for the treatment through the element ehealth-episodeofcare-caremanagerOrganization.

The element managingOrganization references the Organization which is data controller for the EpisodeOfCare and all other resources directly or indirectly referencing it.

CareTeam and history of CareTeam

The CareTeam(s) currently responsible for the EpisodeOfCare are referenced in element team. Changes in CareTeam references are automatically maintained in the element ehealth-teamHistory.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from EpisodeOfCare

NameFlagsCard.TypeDescription & Constraintsdoco
.. EpisodeOfCare EpisodeOfCare
... Slices for extension 1..*ExtensionExtension
Slice: Unordered, Open by value:url
... caremanagerOrganization 1..1Reference(ehealth-organization) {r}Reference to caremanagers organization
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-episodeofcare-caremanagerOrganization
... teamHistory 0..*(Complex)History of assigned careTeam
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-teamHistory
... teamschedule 0..*(Complex)Team Schedule
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-teamschedule
... diagnosis 1..*BackboneElementThe list of diagnosis relevant to this episode of care
.... condition 1..1Reference(ehealth-condition) {r}Conditions/problems/diagnoses this episode of care is for
... patient 1..1Reference(ehealth-patient) {r}The patient who is the focus of this episode of care
... managingOrganization 1..1Reference(ehealth-organization) {r}Organization that assumes care
... period 1..1PeriodInterval during responsibility is assumed
... careManager 0..0
... team 0..*Reference(ehealth-careteam) {r}Other practitioners facilitating this episode of care
... account 0..0

doco Documentation for this format

 

Other representations of profile: CSV, Excel, Schematron