eHealth Infrastructure
3.4.1 - release Denmark flag

eHealth Infrastructure, published by Den telemedicinske infrastruktur (eHealth Infrastructure). This guide is not an authorized publication; it is the continuous build for version 3.4.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/fut-infrastructure/implementation-guide/ and changes regularly. See the Directory of published versions

Resource Profile: ehealth-careplan

Official URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-careplan Version: 3.4.1
Active as of 2025-03-06 Computable Name: ehealth-careplan

Introduction

A CarePlan describes the intention of how one or more practitioners intend to deliver care for a particular patient, group or community for a period of time, possibly limited to care for a specific condition or set of conditions.

Scope and Usage

In scope of the eHealth infrastructure CarePlans represent specific tele-medicine plans prepared by a Practitioner and applied to a specific Patient for the treatment a condition such as chronic obstructive pulmonary disease (COPD).

Hierarchies of care plans

A CarePlan can be constructed as a hierarchy of sub plans. The initial hierarchy is inherited from the PlanDefinition, but can be modified for the specific patient. This modification is possible both when instantiating the CarePlan and during execution of the plan.

Sub plans can be attached by making them partOf the parent plan.

Restrictions on deletion

In order to preserve the context and history, it is not allowed to delete sub plans or remove ServiceRequest from the CarePlan. The status element can be used to either cancel or complete a CarePlan or ServiceRequest, if it is no longer relevant for the Patient.

The history of changes in status is automatically maintained in the element ehealth-careplan-statusHistory.

Responsible CareTeam and responsibleHistory

A CarePlan can have a number of responsible CareTeam set in careTeam. The history of changes in careTeam is automatically maintained in the element ehealth-teamHistory.

Participant

A CarePlan can have a number of Participants set in participant. Participants can have up to one function of either Primary or Secondary Contact, and can be of type Practitioner or CareTeam. One should not set the value actorref directly, but rather use the actor element to reference the Practitioner or CareTeam. The actorref element is used as a workaround, to allow searching with Composite search parameters.

Usage:

Formal Views of Profile Content

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

NameFlagsCard.TypeDescription & Constraintsdoco
.. CarePlan 0..* CarePlan Healthcare plan for patient or group
dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources
dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
dom-5: If a resource is contained in another resource, it SHALL NOT have a security label
dom-6: A resource should have narrative for robust management
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
ele-1: All FHIR elements must have a @value or children
... Slices for extension 1..* Extension Extension
Slice: Unordered, Open by value:url
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
.... extension:episodeOfCare 1..1 Reference(EpisodeOfCare) Associated Encounter episode of care
URL: http://hl7.org/fhir/StructureDefinition/workflow-episodeOfCare
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
.... extension:statusHistory 0..* (Complex) Careplan status history
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-careplan-statusHistory
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
.... extension:teamHistory 0..* (Complex) History of assigned careTeam
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-teamHistory
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
.... extension:statusSchedule 0..* (Complex) Careplan status schedule
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-careplan-statusschedule
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
.... extension:teamSchedule 0..* (Complex) Team Schedule
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-teamschedule
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
.... extension:participant 0..* (Complex) Who or what is participating
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-participant
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
... status ?!Σ 1..1 code draft | active | on-hold | revoked | completed | entered-in-error | unknown
Binding: RequestStatus (required)
ele-1: All FHIR elements must have a @value or children
... intent ?!Σ 1..1 code proposal | plan | order | option
Binding: CarePlanIntent (required): Codes indicating the degree of authority/intentionality associated with a care plan.


ele-1: All FHIR elements must have a @value or children
... category Σ 0..* CodeableConcept Type of plan
Binding: Careplan Category (required)
ele-1: All FHIR elements must have a @value or children
... subject Σ 1..1 Reference(ehealth-patient) {r} Who the care plan is for
ele-1: All FHIR elements must have a @value or children
... period Σ 1..1 Period Time period plan covers
ele-1: All FHIR elements must have a @value or children
... author Σ 0..1 Reference(ehealth-patient | ehealth-practitioner | ehealth-relatedperson | ehealth-organization | ehealth-careteam) Who is the designated responsible party
ele-1: All FHIR elements must have a @value or children
... careTeam 0..* Reference(ehealth-careteam) {r} Who's involved in plan?
ele-1: All FHIR elements must have a @value or children
... addresses Σ 1..1 Reference(ehealth-condition) {r} Health issues this plan addresses
ele-1: All FHIR elements must have a @value or children
... supportingInfo 0..* Reference(Resource) {r} Information considered as part of plan
ele-1: All FHIR elements must have a @value or children
... goal 0..* Reference(ehealth-goal) {r} Desired outcome of plan
ele-1: All FHIR elements must have a @value or children

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
CarePlan.statusrequiredRequestStatus
http://hl7.org/fhir/ValueSet/request-status
from the FHIR Standard
CarePlan.intentrequiredCarePlanIntent
http://hl7.org/fhir/ValueSet/care-plan-intent|4.0.1
from the FHIR Standard
CarePlan.categoryrequiredCareplanCategory (a valid code from CarePlan Category)
http://ehealth.sundhed.dk/vs/careplan-category
from this IG

 

Other representations of profile: CSV, Excel, Schematron