MCC eCare Plan Draft Implementation Guide
0.1.0 - CI Build

MCC eCare Plan Draft Implementation Guide - Local Development build (v0.1.0). See the Directory of published versions

Resource Profile: MCCCarePLan - Detailed Descriptions

Definitions for the mccCarePlan resource profile.

1. CarePlan
Definition

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.

Control0..*
Alternate NamesCare Team
InvariantsDefined on this element
dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources (: contained.contained.empty())
dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource (: contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty())
dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated (: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty())
dom-5: If a resource is contained in another resource, it SHALL NOT have a security label (: contained.meta.security.empty())
dom-6: A resource should have narrative for robust management (: text.`div`.exists())
2. CarePlan.id
Definition

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Control0..1
Typestring
Comments

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

3. CarePlan.meta
Definition

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

Control0..1
TypeMeta
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
4. CarePlan.implicitRules
Definition

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Control0..1
Typeuri
Is Modifiertrue
Comments

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
5. CarePlan.language
Definition

The base language in which the resource is written.

Control0..1
BindingA human language.
The codes SHOULD be taken from CommonLanguages
Max Binding: AllLanguages
Typecode
Comments

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
6. CarePlan.text
Definition

A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Control0..1
TypeNarrative
Alternate Namesnarrative, html, xhtml, display
Comments

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
7. CarePlan.contained
Definition

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

Control0..*
TypeResource
Alternate Namesinline resources, anonymous resources, contained resources
Comments

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.

8. CarePlan.extension
Definition

May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
9. CarePlan.modifierExtension
Definition

May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

Control0..*
TypeExtension
Is Modifiertrue
Requirements

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
10. CarePlan.identifier
Definition

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.

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

Allows identification of the care plan as it is known by various participating systems and in a way that remains consistent across servers.

Comments

This is a business identifier, not a resource identifier (see discussion). 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.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
11. CarePlan.instantiatesCanonical
Definition

The URL pointing to a FHIR-defined protocol, guideline, questionnaire or other definition that is adhered to in whole or in part by this CarePlan.

Control0..*
Typecanonical(PlanDefinition | Questionnaire | Measure | ActivityDefinition | OperationDefinition)
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
12. CarePlan.instantiatesUri
Definition

The URL pointing to an externally maintained protocol, guideline, questionnaire or other definition that is adhered to in whole or in part by this CarePlan.

Control0..*
Typeuri
Comments

This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
13. CarePlan.basedOn
Definition

A care plan that is fulfilled in whole or in part by this care plan.

Control0..*
TypeReference(CarePlan)
Requirements

Allows tracing of the care plan and tracking whether proposals/recommendations were acted upon.

Alternate Namesfulfills
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
14. CarePlan.replaces
Definition

Completed or terminated care plan whose function is taken by this new care plan.

Control0..*
TypeReference(CarePlan)
Requirements

Allows tracing the continuation of a therapy or administrative process instantiated through multiple care plans.

Alternate Namessupersedes
Comments

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.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
15. CarePlan.partOf
Definition

A larger care plan of which this particular care plan is a component or step.

Control0..*
TypeReference(CarePlan)
Comments

Each care plan is an independent request, such that having a care plan be part of another care plan can cause issues with cascading statuses. As such, this element is still being discussed.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
16. CarePlan.status
Definition

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

Control1..1
BindingIndicates whether the plan is currently being acted upon, represents future intentions or is now a historical record.
The codes SHALL be taken from RequestStatus
Typecode
Is Modifiertrue
Must Supporttrue
Requirements

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

Comments

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.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
17. CarePlan.intent
Definition

Indicates the level of authority/intentionality associated with the care plan and where the care plan fits into the workflow chain.

Control1..1
BindingCodes indicating the degree of authority/intentionality associated with a care plan.
The codes SHALL be taken from CarePlanIntent
Typecode
Is Modifiertrue
Must Supporttrue
Requirements

Proposals/recommendations, plans and orders all use the same structure and can exist in the same fulfillment chain.

Comments

This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
18. CarePlan.category
Definition

The Care Plan categoy code example value set currently (August 2020) consists of 173 types of SNOMED CT Care Plan record artifact codes that are children of and inclusive of 734163000 Care Plan. Currently in the MCC Care plan this is available to use but not required or Must Support. Testing may prove we should design this as must support. A code that could be used for this version of the MCC Care Plan is 737429003 Chronic kidney disease clinical management plan. Note that more than 1 code is allowed here and through "slicing" the MCC Care Plan could accumulate multiple applicable code to represent mutliple types of Care Plans that the Mutliple Chronic Condition Care Plan is intended to represent.

Control0..*
BindingIdentifies what "kind" of plan this is to support differentiation between multiple co-existing plans; e.g. "Home health", "psychiatric", "asthma", "disease management", etc.
For example codes, see CarePlanCategory
TypeCodeableConcept
Requirements

Used for filtering what plan(s) are retrieved and displayed to different types of users.

Comments

There may be multiple axes of categorization and one plan may serve multiple purposes. In some cases, this may be redundant with references to CarePlan.concern.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
19. CarePlan.title
Definition

Human-friendly name for the care plan.

Control0..1
Typestring
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
20. CarePlan.description
Definition

A description of the scope and nature of the plan.

Control0..1
Typestring
Requirements

Provides more detail than conveyed by category.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
21. CarePlan.subject
Definition

Identifies the patient or group whose intended care is described by the plan.

Control1..1
TypeReference(USCorePatientProfile)
Alternate Namespatient
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
22. CarePlan.encounter
Definition

The Encounter during which this CarePlan was created or to which the creation of this record is tightly associated.

Control0..1
TypeReference(Encounter)
Comments

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.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
23. 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.

Alternate Namestiming
Comments

Any activities scheduled as part of the plan should be constrained to the specified period regardless of whether the activities are planned within a single encounter/episode or across multiple encounters/episodes (e.g. the longitudinal management of a chronic condition).

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
24. CarePlan.created
Definition

Represents when this particular CarePlan record was created in the system, which is often a system-generated date.

Control0..1
TypedateTime
Alternate NamesauthoredOn
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
25. CarePlan.author
Definition
Who is the designated responsible party. (CarePlan.author to be renamed to CarePlan.custodian in R5)
Control0..1
TypeReference(USCorePatientProfile | USCorePractitionerProfile | USCorePractitionerRoleProfile | USCoreCareTeam | USCoreOrganizationProfile | RelatedPerson | Device)
Must Supporttrue
Must Support TypesNo must-support rules about the choice of types/profiles
Comments

The author may also be a contributor. For example, an organization can be an author, but not listed as a contributor.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
26. CarePlan.contributor
Definition

Identifies the individual(s) or organization who provided the contents of the care plan.

Control0..*
TypeReference(USCorePatientProfile | USCorePractitionerProfile | USCorePractitionerRoleProfile | USCoreCareTeam | USCoreOrganizationProfile | RelatedPerson | Device)
Must Supporttrue
Must Support TypesNo must-support rules about the choice of types/profiles
Comments

Collaborative care plans may have multiple contributors.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
27. CarePlan.careTeam
Definition

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

Control0..*
TypeReference(CareTeam)
Must Supporttrue
Requirements

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

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
28. CarePlan.addresses
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. The element can identify risks addressed by the plan as well as active conditions. (The Condition resource can include things like "at risk for hypertension" or "fall risk".) Also scopes plans - multiple plans may exist addressing different concerns.

Comments

When the diagnosis is related to an allergy or intolerance, the Condition and AllergyIntolerance resources can both be used. However, to be actionable for decision support, using Condition alone is not sufficient as the allergy or intolerance condition needs to be represented as an AllergyIntolerance.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
SlicingThis element introduces a set of slices on CarePlan.addresses. The slices are unordered and Open, and can be differentiated using the following discriminators:
  • profile @ $this.resource
29. CarePlan.addresses:sliceChronicKidneyDisease
SliceNamesliceChronicKidneyDisease
Definition

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

Control0..*
TypeReference(ChronicKidneyDiseaseCondition)
Must Supporttrue
Requirements

Links plan to the conditions it manages. The element can identify risks addressed by the plan as well as active conditions. (The Condition resource can include things like "at risk for hypertension" or "fall risk".) Also scopes plans - multiple plans may exist addressing different concerns.

Comments

When the diagnosis is related to an allergy or intolerance, the Condition and AllergyIntolerance resources can both be used. However, to be actionable for decision support, using Condition alone is not sufficient as the allergy or intolerance condition needs to be represented as an AllergyIntolerance.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
30. CarePlan.supportingInfo
Definition

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. These may be thought of as Health Concerns within the Care Plan context. In the MCC Care Plan supportingInfor when available (Must Support) should contain US Core compliant profiles identified in the Artifact Index Library of profiles, the identified CIMI profiles for vital signs, and QuestionnaireResponses preferentially using the QuestionnaireLOINC Panel codes identified <insert Link>. Please also see the Care Plan Profile Relationship diagram for addtional guidance <link?>. Profiles not identified in the library may also be used and are not precluded.

Control0..*
TypeReference(BloodPressurePanel | BodyWeight | BodyMassIndex | USCoreCondition | USCoreLaboratoryResultObservationProfile | USCoreDiagnosticReportProfileLaboratoryReporting | USCoreDiagnosticReportProfileNoteExchange | USCoreProcedureProfile | USCoreImmunizationProfile | FamilyHistoryofCKD | DocRefPACP | Resource | QuestionnaireResponse)
Must Supporttrue
Must Support TypesNo must-support rules about the choice of types/profiles
Requirements

Identifies barriers and other considerations associated with the care plan.

Comments

Use "concern" to identify specific conditions addressed by the care plan.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
31. CarePlan.goal
Definition

Describes the intended objective(s) of carrying out the care plan. In the MCC Care Plan, CarePlan.goal When used US Core Goal should be used.

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

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
32. 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..*
TypeBackboneElement
Must Supporttrue
Requirements

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

InvariantsDefined on this element
cpl-3: Provide a reference or detail, not both (: detail.empty() or reference.empty())
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
33. CarePlan.activity.id
Definition

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control0..1
Typestring
34. CarePlan.activity.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
35. CarePlan.activity.modifierExtension
Definition

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

Control0..*
TypeExtension
Is Modifiertrue
Requirements

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Alternate Namesextensions, user content, modifiers
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
36. CarePlan.activity.outcomeCodeableConcept
Definition

Identifies the outcome at the point when the status of the activity is assessed. For example, the outcome of an education activity could be patient understands (or not).

Control0..*
BindingIdentifies the results of the activity.
For example codes, see CarePlanActivityOutcome
TypeCodeableConcept
Comments

Note that this should not duplicate the activity status (e.g. completed or in progress).

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
37. CarePlan.activity.outcomeReference
Definition

Details of the outcome or action resulting from the activity. The reference to an "event" resource, such as Procedure or Encounter or Observation, is the result/outcome of the activity itself. The activity can be conveyed using CarePlan.activity.detail OR using the CarePlan.activity.reference (a reference to a “request” resource). MedicationStatement is directly referenced to fetch or record ANY medication that is being consumed by a patient.

In the MCC Care Plan, CarePlan.activity.OutcomeReference (Must Support) should contain US Core compliant profiles identified in the Artifact Index Library of procedure, lab result, and diagnostic report profiles. Please also see the Care Plan Profile Relationship diagram for additional guidance <link?>. Goal Profiles not identified in the library may also be used and are not precluded.

There is an existing FHIR JIRA #26064 with respect to clarifying the description and names for activity within Care Plan: 1. Rename: activity.outcome to performedActivity, 2. Rename: activity.reference to plannedActivityReference, 3. Rename: activity.detail to plannedActivityDetail.

Control0..*
TypeReference(USCoreProcedureProfile | USCoreLaboratoryResultObservationProfile | USCoreImmunizationProfile | USCoreDiagnosticReportProfileNoteExchange | USCoreDiagnosticReportProfileLaboratoryReporting | USCoreImmunizationProfile | MedicationStatement | Resource | BloodPressurePanel | BodyWeight | BodyMassIndex | USCoreGoalProfile)
Must Supporttrue
Must Support TypesNo must-support rules about the choice of types/profiles
Requirements

Links plan to resulting actions.

Comments

The activity outcome is independent of the outcome of the related goal(s). For example, if the goal is to achieve a target body weight of 150 lbs and an activity is defined to diet, then the activity outcome could be calories consumed whereas the goal outcome is an observation for the actual body weight measured.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
38. CarePlan.activity.progress
Definition

Notes about the adherence/status/progress of the activity.

Control0..*
TypeAnnotation
Requirements

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

Comments

This element should NOT be used to describe the activity to be performed - that occurs either within the resource pointed to by activity.detail.reference or in activity.detail.description.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
39. CarePlan.activity.reference
Definition

The details of the proposed activity represented in a specific resource. Proposed Activites represent ordered or planned activities that are part of the Care Plan. Please see library of available MCC US Core conformant MedicationRequest profiles to use for CarePlan.activityReference on the Artifact Index page. BsER ReferralRequest SHOULD be used to represent the MCC ReferralRequests such as Vascular Surgery Referral, Dietician Referral, Social Work referral, etc. In the <xx> of the this guide, the primary referral types of interest for CKD and other chronic diseases that can be used will be listed including and in addition to the extensible serviceRequest.code Bidirectional Services eReferral Type value set.

There is an exsiting FHIR JIRA #26064 with respect to clarifying the description and names for activity within Care Plan: 1. Rename: activity.outcome to performedActivity, 2. Rename: activity.reference to plannedActivityReference, 3. Rename: activity.detail to plannedActivityDetail.

Control0..1 This element is affected by the following invariants: cpl-3
TypeReference(NutritionOrder | USCoreMedicationRequestProfile | CommunicationRequest | DeviceRequest | Task | ServiceRequest | VisionPrescription | RequestGroup | Appointment)
Must Supporttrue
Must Support TypesNo must-support rules about the choice of types/profiles
Requirements

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

Comments

Standard extension exists (resource-pertainsToGoal) that allows goals to be referenced from any of the referenced resources in CarePlan.activity.reference.
The goal should be visible when the resource referenced by CarePlan.activity.reference is viewed independently from the CarePlan. Requests that are pointed to by a CarePlan using this element should not point to this CarePlan using the "basedOn" element. i.e. Requests that are part of a CarePlan are not "based on" the CarePlan.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
40. CarePlan.activity.detail
Definition

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

Control0..0 This element is affected by the following invariants: cpl-3
TypeBackboneElement
Requirements

Details in a simple form for generic care plan systems.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
41. CarePlan.activity.detail.id
Definition

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control0..1
Typestring
42. CarePlan.activity.detail.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
43. CarePlan.activity.detail.modifierExtension
Definition

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

Control0..*
TypeExtension
Is Modifiertrue
Requirements

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Alternate Namesextensions, user content, modifiers
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
44. CarePlan.activity.detail.kind
Definition

A description of the kind of resource the in-line definition of a care plan activity is representing. The CarePlan.activity.detail is an in-line definition when a resource is not referenced using CarePlan.activity.reference. For example, a MedicationRequest, a ServiceRequest, or a CommunicationRequest.

Control0..1
BindingResource types defined as part of FHIR that can be represented as in-line definitions of a care plan activity.
The codes SHALL be taken from CarePlanActivityKind
Typecode
Requirements

May determine what types of extensions are permitted.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
45. CarePlan.activity.detail.instantiatesCanonical
Definition

The URL pointing to a FHIR-defined protocol, guideline, questionnaire or other definition that is adhered to in whole or in part by this CarePlan activity.

Control0..*
Typecanonical(PlanDefinition | ActivityDefinition | Questionnaire | Measure | OperationDefinition)
Requirements

Allows Questionnaires that the patient (or practitioner) should fill in to fulfill the care plan activity.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
46. CarePlan.activity.detail.instantiatesUri
Definition

The URL pointing to an externally maintained protocol, guideline, questionnaire or other definition that is adhered to in whole or in part by this CarePlan activity.

Control0..*
Typeuri
Requirements

Allows Questionnaires that the patient (or practitioner) should fill in to fulfill the care plan activity.

Comments

This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
47. CarePlan.activity.detail.code
Definition

Detailed description of the type of planned activity; e.g. what lab test, what procedure, what kind of encounter.

Control0..1
BindingDetailed description of the type of activity; e.g. What lab test, what procedure, what kind of encounter.
For example codes, see ProcedureCodes(SNOMEDCT)
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.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
48. CarePlan.activity.detail.reasonCode
Definition

Provides the rationale that drove the inclusion of this particular activity as part of the plan or the reason why the activity was prohibited.

Control0..*
BindingIdentifies why a care plan activity is needed. Can include any health condition codes as well as such concepts as "general wellness", prophylaxis, surgical preparation, etc.
For example codes, see SNOMEDCTClinicalFindings
TypeCodeableConcept
Comments

This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonCondition instead.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
49. CarePlan.activity.detail.reasonReference
Definition

Indicates another resource, such as the health condition(s), whose existence justifies this request and drove the inclusion of this particular activity as part of the plan.

Control0..*
TypeReference(Condition | Observation | DiagnosticReport | DocumentReference)
Comments

Conditions can be identified at the activity level that are not identified as reasons for the overall plan.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
50. CarePlan.activity.detail.goal
Definition

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

Control0..*
TypeReference(Goal)
Requirements

So that participants know the link explicitly.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
51. CarePlan.activity.detail.status
Definition

Identifies what progress is being made for the specific activity.

Control1..1
BindingCodes that reflect the current state of a care plan activity within its overall life cycle.
The codes SHALL be taken from CarePlanActivityStatus
Typecode
Is Modifiertrue
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.
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 activity.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
52. CarePlan.activity.detail.statusReason
Definition

Provides reason why the activity isn't yet started, is on hold, was cancelled, etc.

Control0..1
TypeCodeableConcept
Comments

Will generally not be present if status is "complete". Be sure to prompt to update this (or at least remove the existing value) if the status is changed.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
53. CarePlan.activity.detail.doNotPerform
Definition

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

Control0..1
Typeboolean
Is Modifiertrue
Requirements

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

Comments

This element is labeled as a modifier because it marks an activity as an activity that is not to be performed.

Meaning if MissingIf missing indicates that the described activity is one that should be engaged in when following the plan.
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
54. CarePlan.activity.detail.scheduled[x]
Definition

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

Control0..1
TypeChoice of: Timing, Period, string
[x] NoteSee Choice of Data Types for further information about how to use [x]
Requirements

Allows prompting for activities and detection of missed planned activities.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
55. CarePlan.activity.detail.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 identify a type of location.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
56. CarePlan.activity.detail.performer
Definition

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

Control0..*
TypeReference(Practitioner | PractitionerRole | Organization | RelatedPerson | Patient | CareTeam | HealthcareService | Device)
Requirements

Helps in planning of activity.

Comments

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

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
57. CarePlan.activity.detail.product[x]
Definition

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

Control0..1
BindingA product supplied or administered as part of a care plan activity.
For example codes, see SNOMEDCTMedicationCodes
TypeChoice of: CodeableConcept, Reference(Medication | Substance)
[x] NoteSee Choice of Data Types for further information about how to use [x]
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
58. CarePlan.activity.detail.dailyAmount
Definition

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

Control0..1
TypeQuantity(SimpleQuantity)
Requirements

Allows rough dose checking.

Alternate Namesdaily dose
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
59. CarePlan.activity.detail.quantity
Definition

Identifies the quantity expected to be supplied, administered or consumed by the subject.

Control0..1
TypeQuantity(SimpleQuantity)
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
60. CarePlan.activity.detail.description
Definition

This provides a textual description of constraints on the intended 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
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
61. CarePlan.note
Definition

General notes about the care plan not covered elsewhere.

Control0..*
TypeAnnotation
Requirements

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

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))