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-careplan

Official URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-careplan Version: 3.0.0
Active as of 2024-05-16 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.

Usage:

Formal Views of Profile Content

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

This structure is derived from CarePlan

NameFlagsCard.TypeDescription & Constraintsdoco
.. CarePlan CarePlan
... Slices for extension 1..*ExtensionExtension
Slice: Unordered, Open by value:url
... episodeOfCare 1..1Reference(EpisodeOfCare)Associated Encounter episode of care
URL: http://hl7.org/fhir/StructureDefinition/workflow-episodeOfCare
... statusHistory 0..*(Complex)Careplan status history
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-careplan-statusHistory
... statusSchedule 0..*(Complex)Careplan status schedule
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-careplan-statusschedule
... teamSchedule 0..*(Complex)Team Schedule
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-teamschedule
... basedOn 0..0
... replaces 0..0
... partOf 0..1Reference(ehealth-careplan) {r}Part of referenced CarePlan
... status 1..1codedraft | active | on-hold | revoked | completed | entered-in-error | unknown
Binding: RequestStatus (required)
... category 0..*CodeableConceptType of plan
Binding: Careplan Category (required)
... subject 1..1Reference(ehealth-patient) {r}Who the care plan is for
... period 1..1PeriodTime period plan covers
... author 0..1Reference(ehealth-patient | ehealth-practitioner | ehealth-relatedperson | ehealth-organization | ehealth-careteam)Who is the designated responsible party
... careTeam 0..*Reference(ehealth-careteam) {r}Who's involved in plan?
... addresses 1..1Reference(ehealth-condition) {r}Health issues this plan addresses
... supportingInfo 0..*Reference(Resource) {r}Information considered as part of plan
... goal 0..*Reference(ehealth-goal) {r}Desired outcome of plan
... activity
.... outcomeReference 0..*Reference(Resource) {r}Appointment, Encounter, Procedure, etc.
.... progress
..... Slices for author[x] 0..1Reference(Practitioner | Patient | RelatedPerson | Organization), stringIndividual responsible for the annotation
Slice: Unordered, Open by type:$this
...... author[x]:authorReference 0..1Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson)Individual responsible for the annotation
...... author[x]:authorString 0..1stringIndividual responsible for the annotation
.... reference 1..1Reference(ehealth-servicerequest) {r, r, b}Activity details defined in specific resource
.... detail
..... reasonReference 0..*Reference(ehealth-condition) {r}Why activity is needed
..... goal 0..*Reference(Goal) {r}Goals this activity relates to
..... location 0..1Reference(Location) {r}Where it should happen
..... performer 0..*Reference(ehealth-practitioner | ehealth-organization | ehealth-relatedperson | ehealth-patient | ehealth-careteam) {r}Who will be responsible?
... note
.... Slices for author[x] 0..1Reference(Practitioner | Patient | RelatedPerson | Organization), stringIndividual responsible for the annotation
Slice: Unordered, Open by type:$this
..... author[x]:authorReference 0..1Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson)Individual responsible for the annotation
..... author[x]:authorString 0..1stringIndividual responsible for the annotation

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
CarePlan.statusrequiredRequestStatus
http://hl7.org/fhir/ValueSet/request-status
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