This page is part of the FHIR Specification (v0.0.82: DSTU 1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

4.5.4 Resource CarePlan2 - Detailed Descriptions

Detailed Descriptions for the elements in the CarePlan2 resource.

CarePlan2
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
CarePlan2.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).

NoteThis is a business identifer, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
Requirements

Need to allow connection to a wider workflow.

CarePlan2.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.

CarePlan2.status
Definition

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

Control1..1
BindingCarePlan2Status: Required: http://hl7.org/fhir/care-plan2-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.

CarePlan2.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.

CarePlan2.modified
Definition

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

Control0..1
TypedateTime
Requirements

Indicates how current the plan is.

CarePlan2.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.

CarePlan2.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
CarePlan2.participant.role
Definition

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

Control0..1
BindingCarePlan2ParticipantRole: 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.

CarePlan2.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".

CarePlan2.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.

CarePlan2.goal
Definition

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

Control0..*
TypeReference(Goal)
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.

CarePlan2.activity
Definition

Identifies an action that is planned to happen as part of the careplan. For example, a medication to be used, lab tests to perform, self-monitoring, education, etc.

Control0..*
TypeReference(ProcedureRequest | MedicationPrescription | DiagnosticOrder | ReferralRequest | CommunicationRequest | NutritionOrder)
Requirements

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