--- type: "resource" title: "CarePlan" resource: "CarePlan" --- # CarePlan ## Introduction ## Scope and Usage CarePlan is one of the [request](workflow#request) resources in the FHIR [workflow](workflow) specification. Care Plans are used in many 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. They may be used in veterinary care or clinical research to describe the care of a herd or other collection of animals. In public health, they may describe education or immunization campaigns. This resource takes an intermediate approach to complexity. 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 mechanism. The scope of care plans may vary widely. Examples include: - Multi-disciplinary cross-organizational care plans; e.g. An oncology plan including the oncologist, home nursing staff, pharmacy and others - Plans to manage specific disease/condition(s) (e.g. nutritional plan for a patient post bowel resection, neurological plan post head injury, prenatal plan, postpartum plan, grief management plan, etc.) - Decision support generated plans following specific practice guidelines (e.g. stroke care plan, diabetes plan, falls prevention, etc.) - Self-maintained patient or care-giver authored plans identifying their goals and an integrated understanding of actions to be taken. This does not include the legal Advance Directives, which should be represented with either the Consent resource with Consent.category = Advance Directive or with a specific request resource with intent = directive. Informal advance directives could be represented as a Goal, such as "I want to die at home." This resource can be used to represent both proposed plans (for example, recommendations from a decision support engine or returned as part of a consult report) as well as active plans. The nature of the plan is communicated by the status. Some systems may need to filter CarePlans to ensure that only appropriate plans are exposed via a given user interface. ## Boundaries and Relationships CarePlan activities can be defined using references to the various "request" resources. These references could be to resources with a status of "planned" or to an active order. It is possible for planned activities to exist (e.g. appointments) without needing a CarePlan at all. CarePlans are used when there's a need to group activities, goals and/or participants together to provide some degree of context. The CarePlan resource represents an authorization as well as fulfillment on the service provided, while not necessarily providing all the details of such fulfillment. Further details about the fulfillment are handled by the [Task](task) resource. For further information about this separation of responsibilities, refer to the [Fulfillment/Execution](request#fulfillment) section of the Request pattern. CarePlans can be tied to specific [Conditions](condition), however they can also be condition-independent and instead focused on a particular type of care (e.g. psychological, nutritional) or the care delivered by a particular practitioner or group of practitioners. An [ImmunizationRecommendation](https://build.fhir.org/ig/HL7/immunization-incubator/en/StructureDefinition-ImmunizationRecommendation.html) can be interpreted as a narrow type of CarePlan dealing only with immunization events. Where such information could appear in either resource, the immunization-specific resource is preferred. CarePlans represent a specific plan instance for a particular patient or group. It is not intended to be used to define generic plans or protocols that are independent of a specific individual or group. CarePlan represents a specific intent, not a general definition. Protocols and order sets are supported through [PlanDefinition](plandefinition). ## Notes ### Notes The [Provenance](provenance) resource can be used for detailed review information, such as when the care plan was last reviewed and by whom. ## Open Issues ## StructureDefinition ### Elements (Simplified) - **[CarePlan](/careplan-definitions#CarePlan)** [0..*]: - Healthcare plan for patient or group - **[CarePlan.identifier](/careplan-definitions#CarePlan.identifier)** [0..*]: [Identifier](/Identifier) External Ids for this plan - **[CarePlan.basedOn](/careplan-definitions#CarePlan.basedOn)** [0..*]: [Reference(CarePlan](/Reference(CarePlan), [ServiceRequest](/ServiceRequest), [RequestOrchestration](/RequestOrchestration), [NutritionOrder)](/NutritionOrder)) Fulfills plan, proposal or order - **[CarePlan.replaces](/careplan-definitions#CarePlan.replaces)** [0..*]: Reference([CarePlan](/CarePlan)) CarePlan replaced by this CarePlan - **[CarePlan.partOf](/careplan-definitions#CarePlan.partOf)** [0..*]: Reference([CarePlan](/CarePlan)) Part of referenced CarePlan - **[CarePlan.status](/careplan-definitions#CarePlan.status)** [1..1]: [code](/code) required:[request-status](/valueset-request-status) draft | active | on-hold | entered-in-error | ended | completed | revoked | unknown - **[CarePlan.intent](/careplan-definitions#CarePlan.intent)** [1..1]: [code](/code) required:[care-plan-intent](/valueset-care-plan-intent) proposal | plan | order | option | directive - **[CarePlan.category](/careplan-definitions#CarePlan.category)** [0..*]: [CodeableConcept](/CodeableConcept) example:[care-plan-category](/valueset-care-plan-category) Type of plan - **[CarePlan.title](/careplan-definitions#CarePlan.title)** [0..1]: [string](/string) Human-friendly name for the care plan - **[CarePlan.description](/careplan-definitions#CarePlan.description)** [0..1]: [string](/string) Summary of nature of plan - **[CarePlan.subject](/careplan-definitions#CarePlan.subject)** [1..1]: [Reference(Patient](/Reference(Patient), [Group)](/Group)) Who the care plan is for - **[CarePlan.encounter](/careplan-definitions#CarePlan.encounter)** [0..1]: Reference([Encounter](/Encounter)) The Encounter during which this CarePlan was created - **[CarePlan.period](/careplan-definitions#CarePlan.period)** [0..1]: [Period](/Period) Time period plan covers - **[CarePlan.created](/careplan-definitions#CarePlan.created)** [0..1]: [dateTime](/dateTime) Date record was first recorded - **[CarePlan.custodian](/careplan-definitions#CarePlan.custodian)** [0..1]: [Reference(Patient](/Reference(Patient), [Practitioner](/Practitioner), [PractitionerRole](/PractitionerRole), [Device](/Device), [RelatedPerson](/RelatedPerson), [Organization](/Organization), [CareTeam)](/CareTeam)) Who is the designated responsible party - **[CarePlan.contributor](/careplan-definitions#CarePlan.contributor)** [0..*]: [Reference(Patient](/Reference(Patient), [Practitioner](/Practitioner), [PractitionerRole](/PractitionerRole), [Device](/Device), [RelatedPerson](/RelatedPerson), [Organization](/Organization), [CareTeam)](/CareTeam)) Who provided the content of the care plan - **[CarePlan.careTeam](/careplan-definitions#CarePlan.careTeam)** [0..*]: Reference([CareTeam](/CareTeam)) Who's involved in plan? - **[CarePlan.addresses](/careplan-definitions#CarePlan.addresses)** [0..*]: [CodeableReference](/CodeableReference) example:[clinical-findings](/valueset-clinical-findings) Health issues this plan addresses - **[CarePlan.supportingInfo](/careplan-definitions#CarePlan.supportingInfo)** [0..*]: Reference([Resource](/Resource)) Information considered as part of plan - **[CarePlan.goal](/careplan-definitions#CarePlan.goal)** [0..*]: Reference([Goal](/Goal)) Desired outcome of plan - **[CarePlan.activity](/careplan-definitions#CarePlan.activity)** [0..*]: [BackboneElement](/BackboneElement) Action to occur or has occurred as part of plan - **[CarePlan.activity.performedActivity](/careplan-definitions#CarePlan.activity.performedActivity)** [0..*]: [CodeableReference](/CodeableReference) example:[care-plan-activity-performed](/valueset-care-plan-activity-performed) Activities that are completed or in progress (concept, or Appointment, Encounter, Procedure, etc.) - **[CarePlan.activity.progress](/careplan-definitions#CarePlan.activity.progress)** [0..*]: [Annotation](/Annotation) Comments about the activity status/progress - **[CarePlan.activity.plannedActivityReference](/careplan-definitions#CarePlan.activity.plannedActivityReference)** [0..1]: [Reference(Appointment](/Reference(Appointment), [CommunicationRequest](/CommunicationRequest), [DeviceRequest](/DeviceRequest), [MedicationRequest](/MedicationRequest), [NutritionOrder](/NutritionOrder), [Task](/Task), [ServiceRequest](/ServiceRequest), [VisionPrescription](/VisionPrescription), [RequestOrchestration)](/RequestOrchestration)) Activity that is intended to be part of the care plan - **[CarePlan.note](/careplan-definitions#CarePlan.note)** [0..*]: [Annotation](/Annotation) Comments about the plan ## Mappings - [CarePlan Mappings](/careplan-mappings) — 53 mapping entries ## Implementation Guide ### implementationguide-CarePlan-core.xml ```xml <status value="draft"/> <date value="2015-03-27T00:00:00.000"/> <publisher value="Health Level Seven, Inc. - Patient Care WG"/> <description value="A set of commonly used extensions that don't make the usage requirements for inclusion in the resource itself"/> </ImplementationGuide> ``` ## Resource Packs ### list-CarePlan-packs.xml ```xml <?xml version="1.0" encoding="UTF-8"?> <List xmlns="http://hl7.org/fhir"> <id value="CarePlan-packs"/> <status value="current"/> <mode value="working"/> <entry> <item> <reference value="ImplementationGuide/CarePlan-core"/> </item> </entry> </List> ``` ## Search Parameters - [activity-reference](/careplan-search#activity-reference) — **reference** — Activity that is intended to be part of the care plan — `CarePlan.activity.plannedActivityReference` - [based-on](/careplan-search#based-on) — **reference** — Fulfills CarePlan — `CarePlan.basedOn` - [care-team](/careplan-search#care-team) — **reference** — Who's involved in plan? — `CarePlan.careTeam` - [category](/careplan-search#category) — **token** — Type of plan — `CarePlan.category` - [condition](/careplan-search#condition) — **reference** — Reference to a resource (by instance) — `CarePlan.addresses.reference` - [custodian](/careplan-search#custodian) — **reference** — Who is the designated responsible party — `CarePlan.custodian` - [date](/careplan-search#date) — **date** — Time period plan covers — `CarePlan.period` - [encounter](/careplan-search#encounter) — **reference** — The Encounter during which this CarePlan was created — `CarePlan.encounter` - [goal](/careplan-search#goal) — **reference** — Desired outcome of plan — `CarePlan.goal` - [identifier](/careplan-search#identifier) — **token** — External Ids for this plan — `CarePlan.identifier` - [intent](/careplan-search#intent) — **token** — proposal | plan | order | option | directive — `CarePlan.intent` - [part-of](/careplan-search#part-of) — **reference** — Part of referenced CarePlan — `CarePlan.partOf` - [patient](/careplan-search#patient) — **reference** — Who the care plan is for — `CarePlan.subject.where(resolve() is Patient)` - [replaces](/careplan-search#replaces) — **reference** — CarePlan replaced by this CarePlan — `CarePlan.replaces` - [status](/careplan-search#status) — **token** — draft | active | on-hold | revoked | completed | entered-in-error | unknown — `CarePlan.status` - [subject](/careplan-search#subject) — **reference** — Who the care plan is for — `CarePlan.subject` [Full Search Parameters](/careplan-search) ## Examples - [careplan-example](/careplan-example-careplan-example) — careplan-example - [careplan-example-asthma](/careplan-example-careplan-example-asthma) — careplan-example-asthma - [careplan-example-f001-heart](/careplan-example-careplan-example-f001-heart) — careplan-example-f001-heart - [careplan-example-f002-lung](/careplan-example-careplan-example-f002-lung) — careplan-example-f002-lung - [careplan-example-f003-pharynx](/careplan-example-careplan-example-f003-pharynx) — careplan-example-f003-pharynx - [careplan-example-f201-renal](/careplan-example-careplan-example-f201-renal) — careplan-example-f201-renal - [careplan-example-f202-malignancy](/careplan-example-careplan-example-f202-malignancy) — careplan-example-f202-malignancy - [careplan-example-f203-sepsis](/careplan-example-careplan-example-f203-sepsis) — careplan-example-f203-sepsis - [careplan-example-GPVisit](/careplan-example-careplan-example-GPVisit) — careplan-example-GPVisit - [careplan-example-integrated](/careplan-example-careplan-example-integrated) — careplan-example-integrated - [careplan-example-obesity-narrative](/careplan-example-careplan-example-obesity-narrative) — careplan-example-obesity-narrative - [careplan-example-pregnancy](/careplan-example-careplan-example-pregnancy) — careplan-example-pregnancy - [careplan-examples-header](/careplan-example-careplan-examples-header) — careplan-examples-header - [example](/careplan-example-example) — careplan-example — Care plan to address obesity that has a goal of weight loss - [f001](/careplan-example-f001) — careplan-example-f001-heart — Care plan for an operative procedure on heart - [f002](/careplan-example-f002) — careplan-example-f002-lung — Care plan for a partial lobectomy of lung - [f003](/careplan-example-f003) — careplan-example-f003-pharynx — Care plan with goal of retropharyngeal abscess removal - [f201](/careplan-example-f201) — careplan-example-f201-renal — Care plan to address renal insufficiency - [f202](/careplan-example-f202) — careplan-example-f202-malignancy — Care plan to address head-neck tumor by chemotherapy - [f203](/careplan-example-f203) — careplan-example-f203-sepsis — Care plan to address sepsis - [gpvisit](/careplan-example-gpvisit) — careplan-example-GPVisit — Encounter-specific care plan for GP visit - [integrate](/careplan-example-integrate) — careplan-example-integrated — Integrated care plan with multiple goals & conditions (from Mayo) - [obesity-narrative](/careplan-example-obesity-narrative) — careplan-example-obesity-narrative — Primarily narrative care plan to address obesity - [preg](/careplan-example-preg) — careplan-example-pregnancy — Care plan to address pregnancy [Full Examples](/careplan-examples) ## Mapping Exceptions ### careplan-fivews-mapping-exceptions.xml ### Unmapped Elements - **FiveWs.author** — Unknown - **FiveWs.cause** — Unknown - **FiveWs.version** — Unknown - **FiveWs.witness** — Unknown - **FiveWs.where** — Unknown - **FiveWs.init** — Unknown - **FiveWs.who** — Unknown - **FiveWs.grade** — Unknown - **FiveWs.done** — Unknown ### careplan-request-mapping-exceptions.xml ### Divergent Elements - **Request.identifier** → **CarePlan.identifier** - shortUnmatched | reason=Unknown | pattern=Business Identifier for care plan | resource=External Ids for this plan - definitionUnmatched | reason=Unknown | pattern=Business identifiers assigned to this care plan by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server. | resource=Business identifiers assigned to this care plan by the performer or other systems which remain constant as the resource is updated and propagates from server to server. - commentsUnmatched | reason=Unknown | pattern=The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler. Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number. | resource=This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number. - **Request.basedOn** → **CarePlan.basedOn** - missingTypes | reason=Unknown | pattern=Reference(Request) - extraTypes | reason=Unknown - definitionUnmatched | reason=Unknown | pattern=A higher-level request resource (i.e. a plan, proposal or order) that is fulfilled in whole or in part by this care plan. Authorization from the 'basedOn' request flows through to the referencing care plan. | resource=A higher-level request resource (i.e. a plan, proposal or order) that is fulfilled in whole or in part by this care plan. - commentsUnmatched | reason=Unknown | pattern=basedOn represents the 'authorization' chain for an action, not the 'reason for action'. For example, an order might be placed on hold under the authorization for a surgery. However the 'reason' for placing the hold is "to avoid interaction with anesthesia medications" . - requirementsUnmatched | reason=Unknown | pattern=Allows tracing of authorization for the request and tracking whether proposals/recommendations were acted upon. | resource=Allows tracing of the care plan and tracking whether proposals/recommendations were acted upon. - **Request.replaces** → **CarePlan.replaces** - missingTypes | reason=Unknown | pattern=Reference(Request) - extraTypes | reason=Unknown - shortUnmatched | reason=Unknown | pattern=Request(s) replaced by this care plan | resource=CarePlan replaced by this CarePlan - definitionUnmatched | reason=Unknown | pattern=Completed or terminated request(s) whose function is taken by this new care plan. | resource=Completed or terminated care plan whose function is taken by this new care plan. - commentsUnmatched | reason=Unknown | pattern=The replacement could be because the initial request was immediately rejected (due to an issue) or because the previous request was completed, but the need for the action described by the request remains ongoing. | resource=The replacement could be because the initial care plan was immediately rejected (due to an issue) or because the previous care plan was completed, but the need for the action described by the care plan remains ongoing. - requirementsUnmatched | reason=Unknown | pattern=Allows tracing the continuation of a therapy or administrative process instantiated through multiple requests. | resource=Allows tracing the continuation of a therapy or administrative process instantiated through multiple care plans. - **Request.status** → **CarePlan.status** - shortUnmatched | reason=Unknown | pattern=draft | active | on-hold | revoked | completed | entered-in-error | unknown | resource=draft | active | on-hold | entered-in-error | ended | completed | revoked | unknown - definitionUnmatched | reason=Unknown | pattern=The current state of the care plan. | resource=Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record. - commentsUnmatched | reason=Unknown | pattern=The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, completed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding]](s) or using the]] resource. A nominal state-transition diagram can be found in the] documentation Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. A status of 'active' when doNotPerform is true means that the request to not perform is currently in force. A status of completed for a "doNotPerform" request indicates that the period of non-performance is now satisfied and the request no longer holds. | resource=The unknown code is not to be used to convey other statuses. The unknown code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the care plan. This element is labeled as a modifier because the status contains the code entered-in-error that marks the plan as not currently valid. - **Request.intent** → **CarePlan.intent** - shortUnmatched | reason=Unknown | pattern=proposal | plan | order (immutable) | resource=proposal | plan | order | option | directive - definitionUnmatched | reason=Unknown | pattern=Indicates the level of authority/intentionality associated with the care plan and where the request fits into the workflow chain. | resource=Indicates the level of authority/intentionality associated with the care plan and where the care plan fits into the workflow chain. - commentsUnmatched | reason=Unknown | pattern=This element is expected to be immutable. E.g. A "proposal" instance should never change to be a "plan" instance or "order" instance. Instead, a new instance 'basedOn' the prior instance should be created with the new 'intent' value. One exception to this is that the granularity of Request.intent is allowed to change. For example, a Request identified as an "order" might later be clarified to be a "filler-order". Or, in rarer cases (to meet recipient constraints), the reverse might also occur. When resources map to this element, they are free to define as many codes as necessary to cover their space and will map to "proposal, plan or order". Can have multiple codes that map to one of these. E.g. "original order", "encoded order", "reflex order" would all map to "order". Expectation is that the set of codes is mutually exclusive or a strict all-encompassing hierarchy. | resource=This element is labeled as a modifier because the intent alters when and how the resource is actually applicable. This element is expected to be immutable. E.g. A "proposal" instance should never change to be a "plan" instance or "order" instance. Instead, a new instance 'basedOn' the prior instance should be created with the new 'intent' value. - **Request.subject** → **CarePlan.subject** - shortUnmatched | reason=Unknown | pattern=Individual the service is ordered/prohibited for | resource=Who the care plan is for - definitionUnmatched | reason=Unknown | pattern=The individual or set of individuals the action is to be performed/not performed on or for. | resource=Identifies the patient or group whose intended care is described by the plan. - requirementsUnmatched | reason=Unknown | pattern=Links the request to the Patient context. - **Request.encounter** → **CarePlan.encounter** - shortUnmatched | reason=Unknown | pattern=Encounter the care plan is tied to | resource=The Encounter during which this CarePlan was created - definitionUnmatched | reason=Unknown | pattern=The Encounter during which this care plan was created or to which the creation of this record is tightly associated. | resource=The Encounter during which this CarePlan was created or to which the creation of this record is tightly associated. - commentsUnmatched | reason=Unknown | pattern=This will typically be the encounter during which the care plan was created. However, some {{title}s may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission activities). | resource=This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. CarePlan activities conducted as a result of the care plan may well occur as part of other encounters. - requirementsUnmatched | reason=Unknown | pattern=Links the care plan to the Encounter context. - **Request.occurrence[x]** → **CarePlan.period** - missingTypes | reason=Unknown | pattern=dateTime, Timing - shortUnmatched | reason=Unknown | pattern=When service should (not) occur | resource=Time period plan covers - definitionUnmatched | reason=Unknown | pattern=The date or time(s) at which the activity or service is desired to occur or not occur. | resource=Indicates when the plan did (or is intended to) come into effect and end. - **Request.authoredOn** → **CarePlan.created** - shortUnmatched | reason=Unknown | pattern=When request was created/transitioned to active | resource=Date record was first recorded - definitionUnmatched | reason=Unknown | pattern=For draft care plans, indicates the date of initial creation. For requests with other statuses, indicates the date of activation. | resource=Represents when this particular CarePlan record was created in the system, which is often a system-generated date. - **Request.requester** → **CarePlan.custodian** - extraTypes | reason=Unknown - shortUnmatched | reason=Unknown | pattern=Who/what is requesting service | resource=Who is the designated responsible party - definitionUnmatched | reason=Unknown | pattern=Who initiated the {{request}} and has responsibility for its activation. | resource=When populated, the custodian is responsible for the care plan. The care plan is attributed to the custodian. - **Request.performer** → **CarePlan.careTeam** - missingTypes | reason=Unknown | pattern=Reference(Practitioner, PractitionerRole, Organization, HealthcareService, Patient, Device, RelatedPerson) - summary | reason=Unknown | pattern=true - shortUnmatched | reason=Unknown | pattern=Specific desired (non)performer | resource=Who's involved in plan? - definitionUnmatched | reason=Unknown | pattern=Indicates who or what is being asked to perform (or not perform) the {{request}}. | resource=Identifies all people and organizations who are expected to be involved in the care envisioned by this plan. - **Request.reason** → **CarePlan.addresses** - shortUnmatched | reason=Unknown | pattern=Why is service (not) needed? | resource=Health issues this plan addresses - definitionUnmatched | reason=Unknown | pattern=Describes why the request is being made in coded or textual form, or Indicates another resource whose existence justifies this request. | resource=Identifies the conditions/problems/concerns/diagnoses/etc. whose management and/or mitigation are handled by this plan. - commentsUnmatched | reason=Unknown | pattern=Textual reasons can be captured using reasonCode.text. If doNoPerform is true, this will be the reason why the request is being made to not act. | resource=Use CarePlan.addresses.concept when a code sufficiently describes the concern (e.g. condition, problem, diagnosis, risk). Use CarePlan.addresses.reference when referencing a resource, which allows more information to be conveyed, such as onset date. CarePlan.addresses.concept and CarePlan.addresses.reference are not meant to be duplicative. For a single concern, either CarePlan.addresses.concept or CarePlan.addresses.reference can be used. CarePlan.addresses.concept may be a summary code, or CarePlan.addresses.reference may be used to reference a very precise definition of the concern using Condition. Both CarePlan.addresses.concept and CarePlan.addresses.reference can be used if they are describing different concerns for the care plan. - **Request.supportingInfo** → **CarePlan.supportingInfo** - missingTypes | reason=Unknown | pattern=Reference(Any) - extraTypes | reason=Unknown - shortUnmatched | reason=Unknown | pattern=Extra information to use in performing request | resource=Information considered as part of plan - definitionUnmatched | reason=Unknown | pattern=Information that may be needed by/relevant to the performer in their execution of this care plan. | resource=Identifies portions of the patient's record that specifically influenced the formation of the plan. These might include comorbidities, recent procedures, limitations, recent assessments, etc. - commentsUnmatched | reason=Unknown | pattern=See guidance on [notes vs. supportingInfo](request.html#notes). | resource=Use "concern" to identify specific conditions addressed by the care plan. supportingInfo can be used to convey one or more Advance Directives or Medical Treatment Consent Directives by referencing Consent or any other request resource with intent = directive. - **Request.note** → **CarePlan.note** - shortUnmatched | reason=Unknown | pattern=Comments made about care plan | resource=Comments about the plan - definitionUnmatched | reason=Unknown | pattern=Comments made about the care plan by the requester, performer, subject or other participants. | resource=General notes about the care plan not covered elsewhere. - commentsUnmatched | reason=Unknown | pattern=See guidance on [notes vs. supportingInfo](request.html#notes). ### Unmapped Elements - **Request.insurance** — Unknown - **Request.priority** — Unknown - **Request.groupIdentifier** — Unknown - **Request.deliverTo** — Unknown - **Request.category** — Unknown - **Request.reported** — Unknown - **Request.relevantHistory** — Unknown - **Request.code** — Unknown - **Request.statusReason** — Unknown - **Request.performerType** — Unknown - **Request.doNotPerform** — Unknown - **Request.product** — Unknown