2nd DSTU Draft For Comment

This page is part of the FHIR Specification (v0.4.0: DSTU 2 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

4.4.5 Resource CarePlan - Detailed Descriptions

Detailed Descriptions for the elements in the CarePlan resource.

CarePlan
Definition

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

Control1..1
Alternate NamesCare Team
CarePlan.identifier
Definition

This records identifiers associated with this care plan that are defined by business processed and/ or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation).

Control0..*
TypeIdentifier
Requirements

Need to allow connection to a wider workflow.

CarePlan.patient
Definition

Identifies the patient/subject whose intended care is described by the plan.

Control0..1
TypeReference(Patient)
Requirements

Care plans are associated with the patient the plan is for.

CarePlan.status
Definition

Indicates whether the plan is currently being acted upon, represents future intentions or is now just historical record.

Control1..1
BindingCarePlanStatus: Required: http://hl7.org/fhir/care-plan-status (Indicates whether the plan is currently being acted upon, represents future intentions or is now just historical record.)
Typecode
Is Modifiertrue
Requirements

Allows clinicians to determine whether the plan is actionable or not.

CarePlan.period
Definition

Indicates when the plan did (or is intended to) come into effect and end.

Control0..1
TypePeriod
Requirements

Allows tracking what plan(s) are in effect at a particular time.

Comments

Any activities scheduled as part of the plan should be constrained to the specified period.

CarePlan.modified
Definition

Identifies the most recent date on which the plan has been revised.

Control0..1
TypedateTime
Requirements

Indicates how current the plan is.

CarePlan.concern
Definition

Identifies the conditions/problems/concerns/diagnoses/etc. whose management and/or mitigation are handled by this plan.

Control0..*
TypeReference(Condition)
Requirements

Links plan to the conditions it manages. Also scopes plans - multiple plans may exist addressing different concerns.

CarePlan.participant
Definition

Identifies all people and organizations who are expected to be involved in the care envisioned by this plan.

Control0..*
Requirements

Allows representation of care teams, helps scope care plan. In some cases may be a determiner of access permissions.

Alternate NamesCare Team
CarePlan.participant.role
Definition

Indicates specific responsibility of an individual within the care plan. E.g. "Primary physician", "Team coordinator", "Caregiver", etc.

Control0..1
BindingCarePlanParticipantRole: Indicates specific responsibility of an individual within the care plan. E.g. "Primary physician", "Team coordinator", "Caregiver", etc.
TypeCodeableConcept
Comments

Roles may sometimes be inferred by type of Practitioner. These are relationships that hold only within the context of the care plan. General relationships should be handled as properties of the Patient resource directly.

CarePlan.participant.member
Definition

The specific person or organization who is participating/expected to participate in the care plan.

Control1..1
TypeReference(Practitioner | RelatedPerson | Patient | Organization)
Comments

Patient only needs to be listed if they have a role other than "subject of care".

CarePlan.goal
Definition

Describes the intended objective(s) of carrying out the Care Plan.

Control0..*
Requirements

Provides context for plan. Allows plan effectiveness to be evaluated by clinicians.

Comments

Goal can be achieving a particular change or merely maintaining a current state or even slowing a decline.

CarePlan.goal.description
Definition

Human-readable description of a specific desired objective of the care plan.

Control1..1
Typestring
Requirements

Without a description of what's trying to be achieved, element has no purpose.

CarePlan.goal.status
Definition

Indicates whether the goal has been reached and is still considered relevant.

Control0..1
BindingCarePlanGoalStatus: Required: http://hl7.org/fhir/care-plan-goal-status (Indicates whether the goal has been met and is still being targeted)
Typecode
Requirements

Allows measuring outcome and also indicates relevance of goal to plan.

CarePlan.goal.notes
Definition

Any comments related to the goal.

Control0..1
Typestring
Requirements

There's a need to capture information about the goal that doesn't actually describe the goal.

Comments

May be used for progress notes, concerns or other related information that doesn't actually describe the goal itself.

CarePlan.goal.concern
Definition

The identified conditions that this goal relates to - the condition that caused it to be created, or that it is intended to address.

Control0..*
TypeReference(Condition)
Requirements

Allows specific goals to explicitly linked to conditions - makes the plan more understandable.

Comments

The concerns do not also need to be listed under CarePlan.concern, but may be.

CarePlan.activity
Definition

Identifies a planned action to occur as part of the plan. For example, a medication to be used, lab tests to perform, self-monitoring, education, etc.

Control0..*
Requirements

Allows systems to prompt for performance of planned activities, validate plans against best practice.

CarePlan.activity.goal
Definition

Internal reference that identifies the goals that this activity is intended to contribute towards meeting.

Control0..*
Typeuri
Requirements

So that participants know the link explicitly.

CarePlan.activity.status
Definition

Identifies what progress is being made for the specific activity.

Control0..1
BindingCarePlanActivityStatus: Required: http://hl7.org/fhir/care-plan-activity-status (Indicates where the activity is at in its overall life cycle)
Typecode
Requirements

Indicates progress against the plan, whether the activity is still relevant for the plan.

Comments

Some aspects of Status can be inferred based on the resources linked in actionTaken. Note that "status" is only as current as the plan was most recently updated.

CarePlan.activity.prohibited
Definition

If true, indicates that the described activity is one that must NOT be engaged in when following the plan.

Control1..1
Typeboolean
Is Modifiertrue
Requirements

Captures intention to not do something that may have been previously typical.

CarePlan.activity.actionResulting
Definition

Resources that describe follow-on actions resulting from the plan, such as drug prescriptions, encounter records, appointments, etc.

Control0..*
TypeReference(Any)
Requirements

Links plan to resulting actions.

CarePlan.activity.notes
Definition

Notes about the execution of the activity.

Control0..1
Typestring
Requirements

Can be used to capture information about adherence, progress, concerns, etc.

Comments

Doesn't describe the activity - that goes in details.

CarePlan.activity.detail
Definition

The details of the proposed activity represented in a specific resource.

Control0..1
TypeReference(Procedure | MedicationPrescription | DiagnosticOrder | Encounter | Supply)
Requirements

Details in a form consistent with other applications and contexts of use.

InvariantsAffect this element
cpl-3: Only provide a detail reference, or a simple detail summary (xpath: not(exists(f:detail)) or not(exists(f:simple)))
CarePlan.activity.simple
Definition

A simple summary of details suitable for a general care plan system (e.g. form driven) that doesn't know about specific resources such as procedure etc.

Control0..1
Requirements

Details in a simple form for generic care plan systems.

InvariantsDefined on this element
cpl-1: DailyDose can only be specified if activity category is drug or food (xpath: (f:category/@value=('drug','diet')) = exists(f:dailyAmount))
cpl-2: Quantity can only be specified if activity category is supply (xpath: (f:category/@value=('supply')) = exists(f:quantity))
cpl-3: Only provide a detail reference, or a simple detail summary (xpath: not(exists(f:detail)) or not(exists(f:simple)))
Affect this element
cpl-3: Only provide a detail reference, or a simple detail summary (xpath: not(exists(f:detail)) or not(exists(f:simple)))
CarePlan.activity.simple.category
Definition

High-level categorization of the type of activity in a care plan.

Control1..1
BindingCarePlanActivityCategory: Required: http://hl7.org/fhir/care-plan-activity-category (High-level categorization of the type of activity in a care plan.)
Typecode
Requirements

May determine what types of extensions are permitted.

CarePlan.activity.simple.code
Definition

Detailed description of the type of activity. E.g. What lab test, what procedure, what kind of encounter.

Control0..1
BindingCarePlanActivityType: Detailed description of the type of activity. E.g. What lab test, what procedure, what kind of encounter.
TypeCodeableConcept
Requirements

Allows matching performed to planned as well as validation against protocols.

Comments

Tends to be less relevant for activities involving particular products. Codes should not convey negation - use "prohibited" instead.

CarePlan.activity.simple.scheduled[x]
Definition

The period, timing or frequency upon which the described activity is to occur.

Control0..1
TypeTiming|Period|string
Requirements

Allows prompting for activities and detection of missed planned activities.

CarePlan.activity.simple.location
Definition

Identifies the facility where the activity will occur. E.g. home, hospital, specific clinic, etc.

Control0..1
TypeReference(Location)
Requirements

Helps in planning of activity.

Comments

May reference a specific clinical location or may just identify a type of location.

CarePlan.activity.simple.performer
Definition

Identifies who's expected to be involved in the activity.

Control0..*
TypeReference(Practitioner | Organization | RelatedPerson | Patient)
Requirements

Helps in planning of activity.

Comments

A performer MAY also be a participant in the care plan.

CarePlan.activity.simple.product
Definition

Identifies the food, drug or other product being consumed or supplied in the activity.

Control0..1
TypeReference(Medication | Substance)
CarePlan.activity.simple.dailyAmount
Definition

Identifies the quantity expected to be consumed in a given day.

Control0..1
TypeQuantity
Requirements

Allows rough dose checking.

Alternate Namesdaily dose
InvariantsAffect this element
cpl-1: DailyDose can only be specified if activity category is drug or food (xpath: (f:category/@value=('drug','diet')) = exists(f:dailyAmount))
CarePlan.activity.simple.quantity
Definition

Identifies the quantity expected to be supplied.

Control0..1
TypeQuantity
InvariantsAffect this element
cpl-2: Quantity can only be specified if activity category is supply (xpath: (f:category/@value=('supply')) = exists(f:quantity))
CarePlan.activity.simple.details
Definition

This provides a textual description of constraints on the activity occurrence, including relation to other activities. It may also include objectives, pre-conditions and end-conditions. Finally, it may convey specifics about the activity such as body site, method, route, etc.

Control0..1
Typestring
CarePlan.notes
Definition

General notes about the care plan not covered elsewhere.

Control0..1
Typestring
Requirements

Used to capture information that applies to the plan as a whole that doesn't fit into discrete elements.