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 Resource CarePlan - Content

This resource maintained by the Patient Care Work Group

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.

4.4.1 Scope and Usage

Care Plans are used in many of areas of healthcare with a variety of scopes. They can be as simple as a general practitioner keeping track of when their patient is next due for a tetanus immunization through to a detailed plan for an oncology patient covering diet, chemotherapy, radiation, lab work and counseling with detailed timing relationships, pre-conditions and goals.

This resource takes an intermediate approach. It captures basic details about who is involved and what actions are intended without dealing in discrete data about dependencies and timing relationships. These can be supported where necessary using the extension mechanisms.

Comments are welcome about the appropriateness of the proposed level of granularity, whether it's too much detail for what most systems need, or not sufficient for common essential use cases.

This resource is referenced by ClinicalAssessment and Procedure

4.4.2 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. CarePlan DomainResourceHealthcare plan for patient
... identifier 0..*IdentifierExternal Ids for this plan
... patient 0..1PatientWho care plan is for
... status M1..1codeplanned | active | completed
CarePlanStatus (Required)
... period 0..1PeriodTime period plan covers
... modified 0..1dateTimeWhen last updated
... concern 0..*ConditionHealth issues this plan addresses
... participant 0..*ElementWho's involved in plan?
.... role 0..1CodeableConceptType of involvement
.... member 1..1Practitioner | RelatedPerson | Patient | OrganizationWho is involved
... goal 0..*ElementDesired outcome of plan
.... description 1..1stringWhat's the desired outcome?
.... status 0..1codein-progress | achieved | sustaining | cancelled
CarePlanGoalStatus (Required)
.... notes 0..1stringComments about the goal
.... concern 0..*ConditionHealth issues this goal addresses
... activity 0..*ElementAction to occur as part of plan
.... goal 0..*uriGoals this activity relates to
.... status 0..1codenot-started | scheduled | in-progress | on-hold | completed | cancelled
CarePlanActivityStatus (Required)
.... prohibited M1..1booleanDo NOT do
.... actionResulting 0..*AnyAppointments, orders, etc.
.... notes 0..1stringComments about the activity
.... detail I0..1Procedure | MedicationPrescription | DiagnosticOrder | Encounter | SupplyActivity details defined in specific resource
.... simple I0..1ElementActivity details summarised here
DailyDose can only be specified if activity category is drug or food
Quantity can only be specified if activity category is supply
Only provide a detail reference, or a simple detail summary
..... category 1..1codediet | drug | encounter | observation | procedure | supply | other
CarePlanActivityCategory (Required)
..... code 0..1CodeableConceptDetail type of activity
..... scheduled[x] When activity is to occur
...... scheduledTiming0..1Timing
...... scheduledPeriod0..1Period
...... scheduledString0..1string
..... location 0..1LocationWhere it should happen
..... performer 0..*Practitioner | Organization | RelatedPerson | PatientWho's responsible?
..... product 0..1Medication | SubstanceWhat's administered/supplied
..... dailyAmount I0..1QuantityHow much consumed/day?
..... quantity I0..1QuantityHow much is administered/supplied/consumed
..... details 0..1stringExtra info on activity occurrence
... notes 0..1stringComments about the plan

UML Diagram

CarePlan (DomainResource)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)identifier : Identifier 0..*Identifies the patient/subject whose intended care is described by the planpatient : Reference(Patient) 0..1Indicates whether the plan is currently being acted upon, represents future intentions or is now just historical record (this element modifies the meaning of other elements)status : code 1..1 « Indicates whether the plan is currently being acted upon, represents future intentions or is now just historical record.CarePlanStatus »Indicates when the plan did (or is intended to) come into effect and endperiod : Period 0..1Identifies the most recent date on which the plan has been revisedmodified : dateTime 0..1Identifies the conditions/problems/concerns/diagnoses/etc. whose management and/or mitigation are handled by this planconcern : Reference(Condition) 0..*General notes about the care plan not covered elsewherenotes : string 0..1ParticipantIndicates specific responsibility of an individual within the care plan. E.g. "Primary physician", "Team coordinator", "Caregiver", etcrole : CodeableConcept 0..1The specific person or organization who is participating/expected to participate in the care planmember : Reference(Practitioner|RelatedPerson| Patient|Organization) 1..1GoalHuman-readable description of a specific desired objective of the care plandescription : string 1..1Indicates whether the goal has been reached and is still considered relevantstatus : code 0..1 « Indicates whether the goal has been met and is still being targetedCarePlanGoalStatus »Any comments related to the goalnotes : string 0..1The identified conditions that this goal relates to - the condition that caused it to be created, or that it is intended to addressconcern : Reference(Condition) 0..*ActivityInternal reference that identifies the goals that this activity is intended to contribute towards meetinggoal : uri 0..*Identifies what progress is being made for the specific activitystatus : code 0..1 « Indicates where the activity is at in its overall life cycleCarePlanActivityStatus »If true, indicates that the described activity is one that must NOT be engaged in when following the plan (this element modifies the meaning of other elements)prohibited : boolean 1..1Resources that describe follow-on actions resulting from the plan, such as drug prescriptions, encounter records, appointments, etcactionResulting : Reference(Any) 0..*Notes about the execution of the activitynotes : string 0..1The details of the proposed activity represented in a specific resourcedetail : Reference(Procedure| MedicationPrescription|DiagnosticOrder| Encounter|Supply) 0..1SimpleHigh-level categorization of the type of activity in a care plancategory : code 1..1 « High-level categorization of the type of activity in a care plan.CarePlanActivityCategory »Detailed description of the type of activity. E.g. What lab test, what procedure, what kind of encountercode : CodeableConcept 0..1The period, timing or frequency upon which the described activity is to occurscheduled[x] : Timing|Period|string 0..1Identifies the facility where the activity will occur. E.g. home, hospital, specific clinic, etclocation : Reference(Location) 0..1Identifies who's expected to be involved in the activityperformer : Reference(Practitioner|Organization| RelatedPerson|Patient) 0..*Identifies the food, drug or other product being consumed or supplied in the activityproduct : Reference(Medication|Substance) 0..1Identifies the quantity expected to be consumed in a given daydailyAmount : Quantity 0..1Identifies the quantity expected to be suppliedquantity : Quantity 0..1This 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, etcdetails : string 0..1Identifies all people and organizations who are expected to be involved in the care envisioned by this planparticipant0..*Describes the intended objective(s) of carrying out the Care Plangoal0..*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 etcsimple0..1Identifies a planned action to occur as part of the plan. For example, a medication to be used, lab tests to perform, self-monitoring, education, etcactivity0..*

XML Template

<CarePlan xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier External Ids for this plan --></identifier>
 <patient><!-- 0..1 Reference(Patient) Who care plan is for --></patient>
 <status value="[code]"/><!-- 1..1 planned | active | completed -->
 <period><!-- 0..1 Period Time period plan covers --></period>
 <modified value="[dateTime]"/><!-- 0..1 When last updated -->
 <concern><!-- 0..* Reference(Condition) Health issues this plan addresses --></concern>
 <participant>  <!-- 0..* Who's involved in plan? -->
  <role><!-- 0..1 CodeableConcept Type of involvement --></role>
  <member><!-- 1..1 Reference(Practitioner|RelatedPerson|Patient|Organization) 
      Who is involved --></member>
 </participant>
 <goal>  <!-- 0..* Desired outcome of plan -->
  <description value="[string]"/><!-- 1..1 What's the desired outcome? -->
  <status value="[code]"/><!-- 0..1 in-progress | achieved | sustaining | cancelled -->
  <notes value="[string]"/><!-- 0..1 Comments about the goal -->
  <concern><!-- 0..* Reference(Condition) Health issues this goal addresses --></concern>
 </goal>
 <activity>  <!-- 0..* Action to occur as part of plan -->
  <goal value="[uri]"/><!-- 0..* Goals this activity relates to -->
  <status value="[code]"/><!-- 0..1 not-started | scheduled | in-progress | on-hold | completed | cancelled -->
  <prohibited value="[boolean]"/><!-- 1..1 Do NOT do -->
  <actionResulting><!-- 0..* Reference(Any) Appointments, orders, etc. --></actionResulting>
  <notes value="[string]"/><!-- 0..1 Comments about the activity -->
  <detail><!-- ?? 0..1 Reference(Procedure|MedicationPrescription|DiagnosticOrder|
    Encounter|Supply) Activity details defined in specific resource --></detail>
  <simple>  <!-- ?? 0..1 Activity details summarised here -->
   <category value="[code]"/><!-- 1..1 diet | drug | encounter | observation | procedure | supply | other -->
   <code><!-- 0..1 CodeableConcept Detail type of activity --></code>
   <scheduled[x]><!-- 0..1 Timing|Period|string When activity is to occur --></scheduled[x]>
   <location><!-- 0..1 Reference(Location) Where it should happen --></location>
   <performer><!-- 0..* Reference(Practitioner|Organization|RelatedPerson|Patient) 
       Who's responsible? --></performer>
   <product><!-- 0..1 Reference(Medication|Substance) What's administered/supplied --></product>
   <dailyAmount><!-- ?? 0..1 Quantity How much consumed/day? --></dailyAmount>
   <quantity><!-- ?? 0..1 Quantity How much is administered/supplied/consumed --></quantity>
   <details value="[string]"/><!-- 0..1 Extra info on activity occurrence -->
  </simple>
 </activity>
 <notes value="[string]"/><!-- 0..1 Comments about the plan -->
</CarePlan>

JSON Template

{doco
  "resourceType" : "CarePlan",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // External Ids for this plan
  "patient" : { Reference(Patient) }, // Who care plan is for
  "status" : "<code>", // R! planned | active | completed
  "period" : { Period }, // Time period plan covers
  "modified" : "<dateTime>", // When last updated
  "concern" : [{ Reference(Condition) }], // Health issues this plan addresses
  "participant" : [{ // Who's involved in plan?
    "role" : { CodeableConcept }, // Type of involvement
    "member" : { Reference(Practitioner|RelatedPerson|Patient|Organization) } // R! 
      Who is involved
  }],
  "goal" : [{ // Desired outcome of plan
    "description" : "<string>", // R! What's the desired outcome?
    "status" : "<code>", // in-progress | achieved | sustaining | cancelled
    "notes" : "<string>", // Comments about the goal
    "concern" : [{ Reference(Condition) }] // Health issues this goal addresses
  }],
  "activity" : [{ // Action to occur as part of plan
    "goal" : ["<uri>"], // Goals this activity relates to
    "status" : "<code>", // not-started | scheduled | in-progress | on-hold | completed | cancelled
    "prohibited" : <boolean>, // R! Do NOT do
    "actionResulting" : [{ Reference(Any) }], // Appointments, orders, etc.
    "notes" : "<string>", // Comments about the activity
    "detail" : { Reference(Procedure|MedicationPrescription|DiagnosticOrder|
    Encounter|Supply) }, // C? Activity details defined in specific resource
    "simple" : { // C? Activity details summarised here
      "category" : "<code>", // R! diet | drug | encounter | observation | procedure | supply | other
      "code" : { CodeableConcept }, // Detail type of activity
      // scheduled[x]: When activity is to occur. One of these 3:
      "scheduledTiming" : { Timing },
      "scheduledPeriod" : { Period },
      "scheduledString" : "<string>",
      "location" : { Reference(Location) }, // Where it should happen
      "performer" : [{ Reference(Practitioner|Organization|RelatedPerson|Patient) }], // 
       Who's responsible?
      "product" : { Reference(Medication|Substance) }, // What's administered/supplied
      "dailyAmount" : { Quantity }, // C? How much consumed/day?
      "quantity" : { Quantity }, // C? How much is administered/supplied/consumed
      "details" : "<string>" // Extra info on activity occurrence
    }
  }],
  "notes" : "<string>" // Comments about the plan
}

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. CarePlan DomainResourceHealthcare plan for patient
... identifier 0..*IdentifierExternal Ids for this plan
... patient 0..1PatientWho care plan is for
... status M1..1codeplanned | active | completed
CarePlanStatus (Required)
... period 0..1PeriodTime period plan covers
... modified 0..1dateTimeWhen last updated
... concern 0..*ConditionHealth issues this plan addresses
... participant 0..*ElementWho's involved in plan?
.... role 0..1CodeableConceptType of involvement
.... member 1..1Practitioner | RelatedPerson | Patient | OrganizationWho is involved
... goal 0..*ElementDesired outcome of plan
.... description 1..1stringWhat's the desired outcome?
.... status 0..1codein-progress | achieved | sustaining | cancelled
CarePlanGoalStatus (Required)
.... notes 0..1stringComments about the goal
.... concern 0..*ConditionHealth issues this goal addresses
... activity 0..*ElementAction to occur as part of plan
.... goal 0..*uriGoals this activity relates to
.... status 0..1codenot-started | scheduled | in-progress | on-hold | completed | cancelled
CarePlanActivityStatus (Required)
.... prohibited M1..1booleanDo NOT do
.... actionResulting 0..*AnyAppointments, orders, etc.
.... notes 0..1stringComments about the activity
.... detail I0..1Procedure | MedicationPrescription | DiagnosticOrder | Encounter | SupplyActivity details defined in specific resource
.... simple I0..1ElementActivity details summarised here
DailyDose can only be specified if activity category is drug or food
Quantity can only be specified if activity category is supply
Only provide a detail reference, or a simple detail summary
..... category 1..1codediet | drug | encounter | observation | procedure | supply | other
CarePlanActivityCategory (Required)
..... code 0..1CodeableConceptDetail type of activity
..... scheduled[x] When activity is to occur
...... scheduledTiming0..1Timing
...... scheduledPeriod0..1Period
...... scheduledString0..1string
..... location 0..1LocationWhere it should happen
..... performer 0..*Practitioner | Organization | RelatedPerson | PatientWho's responsible?
..... product 0..1Medication | SubstanceWhat's administered/supplied
..... dailyAmount I0..1QuantityHow much consumed/day?
..... quantity I0..1QuantityHow much is administered/supplied/consumed
..... details 0..1stringExtra info on activity occurrence
... notes 0..1stringComments about the plan

UML Diagram

CarePlan (DomainResource)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)identifier : Identifier 0..*Identifies the patient/subject whose intended care is described by the planpatient : Reference(Patient) 0..1Indicates whether the plan is currently being acted upon, represents future intentions or is now just historical record (this element modifies the meaning of other elements)status : code 1..1 « Indicates whether the plan is currently being acted upon, represents future intentions or is now just historical record.CarePlanStatus »Indicates when the plan did (or is intended to) come into effect and endperiod : Period 0..1Identifies the most recent date on which the plan has been revisedmodified : dateTime 0..1Identifies the conditions/problems/concerns/diagnoses/etc. whose management and/or mitigation are handled by this planconcern : Reference(Condition) 0..*General notes about the care plan not covered elsewherenotes : string 0..1ParticipantIndicates specific responsibility of an individual within the care plan. E.g. "Primary physician", "Team coordinator", "Caregiver", etcrole : CodeableConcept 0..1The specific person or organization who is participating/expected to participate in the care planmember : Reference(Practitioner|RelatedPerson| Patient|Organization) 1..1GoalHuman-readable description of a specific desired objective of the care plandescription : string 1..1Indicates whether the goal has been reached and is still considered relevantstatus : code 0..1 « Indicates whether the goal has been met and is still being targetedCarePlanGoalStatus »Any comments related to the goalnotes : string 0..1The identified conditions that this goal relates to - the condition that caused it to be created, or that it is intended to addressconcern : Reference(Condition) 0..*ActivityInternal reference that identifies the goals that this activity is intended to contribute towards meetinggoal : uri 0..*Identifies what progress is being made for the specific activitystatus : code 0..1 « Indicates where the activity is at in its overall life cycleCarePlanActivityStatus »If true, indicates that the described activity is one that must NOT be engaged in when following the plan (this element modifies the meaning of other elements)prohibited : boolean 1..1Resources that describe follow-on actions resulting from the plan, such as drug prescriptions, encounter records, appointments, etcactionResulting : Reference(Any) 0..*Notes about the execution of the activitynotes : string 0..1The details of the proposed activity represented in a specific resourcedetail : Reference(Procedure| MedicationPrescription|DiagnosticOrder| Encounter|Supply) 0..1SimpleHigh-level categorization of the type of activity in a care plancategory : code 1..1 « High-level categorization of the type of activity in a care plan.CarePlanActivityCategory »Detailed description of the type of activity. E.g. What lab test, what procedure, what kind of encountercode : CodeableConcept 0..1The period, timing or frequency upon which the described activity is to occurscheduled[x] : Timing|Period|string 0..1Identifies the facility where the activity will occur. E.g. home, hospital, specific clinic, etclocation : Reference(Location) 0..1Identifies who's expected to be involved in the activityperformer : Reference(Practitioner|Organization| RelatedPerson|Patient) 0..*Identifies the food, drug or other product being consumed or supplied in the activityproduct : Reference(Medication|Substance) 0..1Identifies the quantity expected to be consumed in a given daydailyAmount : Quantity 0..1Identifies the quantity expected to be suppliedquantity : Quantity 0..1This 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, etcdetails : string 0..1Identifies all people and organizations who are expected to be involved in the care envisioned by this planparticipant0..*Describes the intended objective(s) of carrying out the Care Plangoal0..*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 etcsimple0..1Identifies a planned action to occur as part of the plan. For example, a medication to be used, lab tests to perform, self-monitoring, education, etcactivity0..*

XML Template

<CarePlan xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier External Ids for this plan --></identifier>
 <patient><!-- 0..1 Reference(Patient) Who care plan is for --></patient>
 <status value="[code]"/><!-- 1..1 planned | active | completed -->
 <period><!-- 0..1 Period Time period plan covers --></period>
 <modified value="[dateTime]"/><!-- 0..1 When last updated -->
 <concern><!-- 0..* Reference(Condition) Health issues this plan addresses --></concern>
 <participant>  <!-- 0..* Who's involved in plan? -->
  <role><!-- 0..1 CodeableConcept Type of involvement --></role>
  <member><!-- 1..1 Reference(Practitioner|RelatedPerson|Patient|Organization) 
      Who is involved --></member>
 </participant>
 <goal>  <!-- 0..* Desired outcome of plan -->
  <description value="[string]"/><!-- 1..1 What's the desired outcome? -->
  <status value="[code]"/><!-- 0..1 in-progress | achieved | sustaining | cancelled -->
  <notes value="[string]"/><!-- 0..1 Comments about the goal -->
  <concern><!-- 0..* Reference(Condition) Health issues this goal addresses --></concern>
 </goal>
 <activity>  <!-- 0..* Action to occur as part of plan -->
  <goal value="[uri]"/><!-- 0..* Goals this activity relates to -->
  <status value="[code]"/><!-- 0..1 not-started | scheduled | in-progress | on-hold | completed | cancelled -->
  <prohibited value="[boolean]"/><!-- 1..1 Do NOT do -->
  <actionResulting><!-- 0..* Reference(Any) Appointments, orders, etc. --></actionResulting>
  <notes value="[string]"/><!-- 0..1 Comments about the activity -->
  <detail><!-- ?? 0..1 Reference(Procedure|MedicationPrescription|DiagnosticOrder|
    Encounter|Supply) Activity details defined in specific resource --></detail>
  <simple>  <!-- ?? 0..1 Activity details summarised here -->
   <category value="[code]"/><!-- 1..1 diet | drug | encounter | observation | procedure | supply | other -->
   <code><!-- 0..1 CodeableConcept Detail type of activity --></code>
   <scheduled[x]><!-- 0..1 Timing|Period|string When activity is to occur --></scheduled[x]>
   <location><!-- 0..1 Reference(Location) Where it should happen --></location>
   <performer><!-- 0..* Reference(Practitioner|Organization|RelatedPerson|Patient) 
       Who's responsible? --></performer>
   <product><!-- 0..1 Reference(Medication|Substance) What's administered/supplied --></product>
   <dailyAmount><!-- ?? 0..1 Quantity How much consumed/day? --></dailyAmount>
   <quantity><!-- ?? 0..1 Quantity How much is administered/supplied/consumed --></quantity>
   <details value="[string]"/><!-- 0..1 Extra info on activity occurrence -->
  </simple>
 </activity>
 <notes value="[string]"/><!-- 0..1 Comments about the plan -->
</CarePlan>

JSON Template

{doco
  "resourceType" : "CarePlan",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // External Ids for this plan
  "patient" : { Reference(Patient) }, // Who care plan is for
  "status" : "<code>", // R! planned | active | completed
  "period" : { Period }, // Time period plan covers
  "modified" : "<dateTime>", // When last updated
  "concern" : [{ Reference(Condition) }], // Health issues this plan addresses
  "participant" : [{ // Who's involved in plan?
    "role" : { CodeableConcept }, // Type of involvement
    "member" : { Reference(Practitioner|RelatedPerson|Patient|Organization) } // R! 
      Who is involved
  }],
  "goal" : [{ // Desired outcome of plan
    "description" : "<string>", // R! What's the desired outcome?
    "status" : "<code>", // in-progress | achieved | sustaining | cancelled
    "notes" : "<string>", // Comments about the goal
    "concern" : [{ Reference(Condition) }] // Health issues this goal addresses
  }],
  "activity" : [{ // Action to occur as part of plan
    "goal" : ["<uri>"], // Goals this activity relates to
    "status" : "<code>", // not-started | scheduled | in-progress | on-hold | completed | cancelled
    "prohibited" : <boolean>, // R! Do NOT do
    "actionResulting" : [{ Reference(Any) }], // Appointments, orders, etc.
    "notes" : "<string>", // Comments about the activity
    "detail" : { Reference(Procedure|MedicationPrescription|DiagnosticOrder|
    Encounter|Supply) }, // C? Activity details defined in specific resource
    "simple" : { // C? Activity details summarised here
      "category" : "<code>", // R! diet | drug | encounter | observation | procedure | supply | other
      "code" : { CodeableConcept }, // Detail type of activity
      // scheduled[x]: When activity is to occur. One of these 3:
      "scheduledTiming" : { Timing },
      "scheduledPeriod" : { Period },
      "scheduledString" : "<string>",
      "location" : { Reference(Location) }, // Where it should happen
      "performer" : [{ Reference(Practitioner|Organization|RelatedPerson|Patient) }], // 
       Who's responsible?
      "product" : { Reference(Medication|Substance) }, // What's administered/supplied
      "dailyAmount" : { Quantity }, // C? How much consumed/day?
      "quantity" : { Quantity }, // C? How much is administered/supplied/consumed
      "details" : "<string>" // Extra info on activity occurrence
    }
  }],
  "notes" : "<string>" // Comments about the plan
}

 

Alternate definitions: Schema/Schematron, Resource Profile (XML, JSON), Questionnaire

4.4.2.1 Terminology Bindings

PathDefinitionTypeReference
CarePlan.status Indicates whether the plan is currently being acted upon, represents future intentions or is now just historical record.Fixedhttp://hl7.org/fhir/care-plan-status
CarePlan.participant.role Indicates specific responsibility of an individual within the care plan. E.g. "Primary physician", "Team coordinator", "Caregiver", etc.UnknownNo details provided yet
CarePlan.goal.status Indicates whether the goal has been met and is still being targetedFixedhttp://hl7.org/fhir/care-plan-goal-status
CarePlan.activity.status Indicates where the activity is at in its overall life cycleFixedhttp://hl7.org/fhir/care-plan-activity-status
CarePlan.activity.simple.category High-level categorization of the type of activity in a care plan.Fixedhttp://hl7.org/fhir/care-plan-activity-category
CarePlan.activity.simple.code Detailed description of the type of activity. E.g. What lab test, what procedure, what kind of encounter.UnknownNo details provided yet

4.4.2.2 Constraints

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

4.4.3 Open Issues

  • This resource combines the concepts of "Care Plan" and "Care Team" into a single resource. Is this appropriate?
  • DSTU: At present, the patient element is optional to allow experimentation with care plan templates, though the resource was not designed for this use. Feedback on this subject is requested during the trial use period.

4.4.4 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPaths
activitycodetokenDetail type of activityCarePlan.activity.simple.code
activitydatedateSpecified date occurs within period specified by CarePlan.activity.timingScheduleCarePlan.activity.simple.scheduled[x]
activitydetailreferenceActivity details defined in specific resourceCarePlan.activity.detail
(Supply, MedicationPrescription, Encounter, Procedure, DiagnosticOrder)
conditionreferenceHealth issues this plan addressesCarePlan.concern
(Condition)
datedateTime period plan coversCarePlan.period
participantreferenceWho is involvedCarePlan.participant.member
(Organization, Patient, Practitioner, RelatedPerson)
patientreferenceWho care plan is forCarePlan.patient
(Patient)