Profile Comparison between http://hl7.org/fhir/us/mcc/StructureDefinition/mccCarePlan vs http://hl7.org/fhir/us/mcc/StructureDefinition/mccCarePlan

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/us/core/StructureDefinition/us-core-careplan
copyright
date	2022-04-13
description	This profile constrains the FHIR Care Plan Resource to represent the requirements of a care plan for patients with multiple chronic conditions.
experimental
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]	urn:iso:std:iso:3166#US
kind	resource
name	MCCCarePLan	MCCCarePlan	Values Differ
publisher	HL7 International - Patient Care WG
purpose
status	active
title	Multiple Chronic Care Condition Care Plan
type	CarePlan
url	http://hl7.org/fhir/us/mcc/StructureDefinition/mccCarePlan
version	1.0.0-ballot	1.0.0-ballot2	Values Differ

Structure

Name	L Flags	L Card.	L Type	L Description & Constraints	R Flags	R Card.	L Type	L Description & Constraints	Comments
CarePlan		0..*	USCoreCarePlanProfile	Healthcare plan for patient or group		0..*	USCoreCarePlanProfile	Healthcare plan for patient or group
id	Σ	0..1	id	Logical id of this artifact	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: ?? (preferred): A human language. Additional Bindings Purpose ?? Max Binding		0..1	code	Language of the resource content Binding: ?? (preferred): A human language. Additional Bindings Purpose ?? Max Binding
text	S	1..1	Narrative	Text summary of the resource, for human interpretation	S	0..1	Narrative	(USCDI) Text summary of the resource, for human interpretation	Elements differ in short: 'Text summary of the resource, for human interpretation' vs '(USCDI) Text summary of the resource, for human interpretation' Element minimum cardinalities differ: '1' vs '0'
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
status	S	1..1	code	generated | extensions | additional | empty Binding: ?? (required): Constrained value set of narrative statuses.	S	1..1	code	(USCDI) generated | extensions | additional | empty Binding: ?? (required): Constrained value set of narrative statuses.	Elements differ in short: 'generated | extensions | additional | empty' vs '(USCDI) generated | extensions | additional | empty'
div	SC	1..1	xhtml	Limited xhtml content	SC	1..1	xhtml	(USCDI) Limited xhtml content	Elements differ in short: 'Limited xhtml content' vs '(USCDI) Limited xhtml content'
contained		0..*	Resource	Contained, inline Resources		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Extension Slice: Unordered, Open by value:url	Elements differ in short: 'Additional content defined by implementations' vs 'Extension' Elements differ in 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.' vs 'An Extension'
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored	?!	0..*	Extension	Extensions that cannot be ignored
identifier	Σ	0..*	Identifier	External Ids for this plan	Σ	0..*	Identifier	External Ids for this plan
instantiatesCanonical	Σ	0..*	canonical(PlanDefinition | Questionnaire | Measure | ActivityDefinition | OperationDefinition)	Instantiates FHIR protocol or definition	Σ	0..*	canonical(PlanDefinition | Questionnaire | Measure | ActivityDefinition | OperationDefinition)	Instantiates FHIR protocol or definition
instantiatesUri	Σ	0..*	uri	Instantiates external protocol or definition	Σ	0..*	uri	Instantiates external protocol or definition
basedOn	Σ	0..*	Reference(CarePlan)	Fulfills CarePlan	Σ	0..*	Reference(CarePlan)	Fulfills CarePlan
replaces	Σ	0..*	Reference(CarePlan)	CarePlan replaced by this CarePlan	Σ	0..*	Reference(CarePlan)	CarePlan replaced by this CarePlan
partOf	Σ	0..*	Reference(CarePlan)	Part of referenced CarePlan	Σ	0..*	Reference(CarePlan)	Part of referenced CarePlan
status	?!SΣ	1..1	code	draft | active | on-hold | revoked | completed | entered-in-error | unknown Binding: ?? (required): Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record.	?!SΣ	1..1	code	(USCDI) draft | active | on-hold | revoked | completed | entered-in-error | unknown Binding: ?? (required): Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record.	Elements differ in short: 'draft | active | on-hold | revoked | completed | entered-in-error | unknown' vs '(USCDI) draft | active | on-hold | revoked | completed | entered-in-error | unknown'
intent	?!SΣ	1..1	code	proposal | plan | order | option Binding: ?? (required): Codes indicating the degree of authority/intentionality associated with a care plan	?!SΣ	1..1	code	(USCDI) proposal | plan | order | option Binding: ?? (required): Codes indicating the degree of authority/intentionality associated with a care plan	Elements differ in short: 'proposal | plan | order | option' vs '(USCDI) proposal | plan | order | option'
Slices for category	SΣ	1..*	CodeableConcept	Care Plan category code describes the type of care plan. Please see CarePlan.category detail for guidance. Slice: Unordered, Open by pattern:$this Binding: ?? (example): Identifies what "kind" of plan this is to support differentiation between multiple co-existing plans; e.g. "Home health", "psychiatric", "asthma", "disease management", etc.	SΣ	1..*	CodeableConcept	Care Plan category code describes the type of care plan. Please see CarePlan.category detail for guidance. Slice: Unordered, Open by pattern:$this Binding: ?? (example): Identifies what "kind" of plan this is to support differentiation between multiple co-existing plans; e.g. "Home health", "psychiatric", "asthma", "disease management", etc.
title	Σ	0..1	string	Human-friendly name for the care plan	Σ	0..1	string	Human-friendly name for the care plan
description	Σ	0..1	string	Summary of nature of plan	Σ	0..1	string	Summary of nature of plan
subject	SΣ	1..1	Reference(US Core Patient Profile)	Who the care plan is for	SΣ	1..1	Reference(US Core Patient Profile)	(USCDI) Who the care plan is for	Elements differ in short: 'Who the care plan is for' vs '(USCDI) Who the care plan is for'
encounter	Σ	0..1	Reference(Encounter)	Encounter created as part of	Σ	0..1	Reference(Encounter)	Encounter created as part of
period	Σ	0..1	Period	Time period plan covers	Σ	0..1	Period	Time period plan covers
created	Σ	0..1	dateTime	Date record was first recorded	Σ	0..1	dateTime	Date record was first recorded
author	SΣ	0..1	Reference(US Core Patient Profile | US Core Practitioner Profile | US Core PractitionerRole Profile | US Core CareTeam Profile | US Core Organization Profile | RelatedPerson | Device | Multiple Chronic Condition Care Plan Care Team)	Who is the designated responsible party. CUSTODIAN OR CARE PLAN OWNER	Σ	0..1	Reference(Patient | Practitioner | PractitionerRole | Device | RelatedPerson | Organization | CareTeam)	Use the CarePlan custodian extension instead. Use of CarePlan.author is discouraged, it is removed in R5.	Elements differ in short: 'Who is the designated responsible party. CUSTODIAN OR CARE PLAN OWNER' vs 'Use the CarePlan custodian extension instead. Use of CarePlan.author is discouraged, it is removed in R5.' Elements differ in definition: ' Who is the designated responsible party. (CarePlan.author to be renamed to CarePlan.custodian in R5)' vs 'Use of CarePlan.author is discouraged. It is removed from the R5 CarePlan Resource and replaced with CarePlan.custodian and should not be used to indicate the responsible party. CarePlan custodian extension should be used to identify a responsible party in the MCC CarePlan Profile' Elements differ in definition for mustSupport: 'true' vs 'false'
contributor	S	0..*	Reference(US Core Patient Profile | US Core Practitioner Profile | US Core PractitionerRole Profile | US Core CareTeam Profile | US Core Organization Profile | RelatedPerson | Device | Multiple Chronic Condition Care Plan Care Team)	Who provided the content of the care plan	S	0..*	Reference(US Core Patient Profile | US Core Practitioner Profile | US Core PractitionerRole Profile | US Core CareTeam Profile | US Core Organization Profile | RelatedPerson | Device | Multiple Chronic Condition Care Plan Care Team)	Who provided the content of the care plan	Elements differ in definition: 'Identifies the individual(s) or organization who provided the contents of the care plan.' vs 'CarePlan.contributor SHALL be used to represent contributors to the care plan instead of author in the MCC CarePlan. Contributors can range from devices (e.g. a home BP monitor) to an individual, team or organization'
careTeam	S	0..*	Reference(Multiple Chronic Condition Care Plan Caregiver on Care Team | Multiple Chronic Condition Care Plan Care Team | US Core CareTeam Profile)	Who's involved in plan?	S	0..*	Reference(Multiple Chronic Condition Care Plan Care Team | US Core CareTeam Profile)	Who's involved in plan?
addresses	Σ	0..*	Reference(Condition)	Health issues this plan addresses	Σ	0..*	Reference(Condition)	Health issues this plan addresses
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
reference	ΣC	0..1	string	Literal reference, Relative, internal or absolute URL	ΣC	0..1	string	Literal reference, Relative, internal or absolute URL
type	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).
identifier	Σ	0..1	Identifier	Logical reference, when literal reference is not known	Σ	0..1	Identifier	Logical reference, when literal reference is not known
display	Σ	0..1	string	Text alternative for the resource	Σ	0..1	string	Text alternative for the resource
supportingInfo	S	0..*	Reference(US Core Blood Pressure Profile | US Core BMI Profile | US Core Body Weight Profile | Multiple Chronic Condition Care Plan Chronic Disease Conditions | Multiple Chronic Condition Care Plan Laboratory Result Observation | Multiple Chronic Condition Care Plan Diagnostic Report and Note | Multiple Chronic Condition Care Plan Procedure | US Core Immunization Profile | Multiple Chronic Condition Care Plan Family History | Document Reference to Patient's Personal Advance Care Plan (Advance Directive) | SDC Questionnaire Response | Multiple Chronic Condition Care Plan Symptom Observation | Multiple Chronic Condition Care Plan Service Request | Multiple Chronic Condition Care Plan Observation SDOH Assessment | Multiple Chronic Condition Care Plan Immunization | Multiple Chronic Condition Care Plan Nutrition Order | Multiple Chronic Condition Care Plan Clinical Impression | Multiple Chronic Condition Care Plan Patient/Caregiver Condition Status Observation | Multiple Chronic Condition Care Plan Questionnaire Response | Multiple Chronic Condition Care Plan Caregiver Considerations Observation | Multiple Chronic Condition Care Plan Clinical Test Observation | Multiple Chronic Condition Care Plan Caregiver on Care Team)	Please see the libraries of available value sets pertinent for use with the appropriate Multiple Chronic Condition Care Plan Profile for use within the referenced profiles at CarePlan.supportingInfo	S	0..*	Reference(US Core Blood Pressure Profile | US Core BMI Profile | US Core Body Weight Profile | Multiple Chronic Condition Care Plan Chronic Disease Conditions | Multiple Chronic Condition Care Plan Laboratory Result Observation | Multiple Chronic Condition Care Plan Diagnostic Report and Note | Multiple Chronic Condition Care Plan Procedure | US Core Immunization Profile | Multiple Chronic Condition Care Plan Family History | Document Reference to Patient's Personal Advance Care Plan (Advance Directive) | SDC Questionnaire Response | Multiple Chronic Condition Care Plan Symptom Observation | Multiple Chronic Condition Care Plan Service Request | Multiple Chronic Condition Care Plan Observation SDOH Assessment | Multiple Chronic Condition Care Plan Immunization | Multiple Chronic Condition Care Plan Nutrition Order | Multiple Chronic Condition Care Plan Clinical Impression | Multiple Chronic Condition Care Plan Patient/Caregiver Condition Status Observation | Multiple Chronic Condition Care Plan Questionnaire Response | Multiple Chronic Condition Care Plan Caregiver Considerations Observation | Multiple Chronic Condition Care Plan Clinical Test Observation | US Core RelatedPerson Profile | US Core Observation Occupation Profile)	Please see the libraries of available value sets pertinent for use with the appropriate Multiple Chronic Condition Care Plan Profile for use within the referenced profiles at CarePlan.supportingInfo
goal		0..*	Reference(Multiple Chronic Condition Care Plan Goal)	This Goal represents one or more overarching goal applicable to the entire care plan		0..*	Reference(Multiple Chronic Condition Care Plan Goal)	This Goal represents one or more overarching goal applicable to the entire care plan
activity	SC	0..*	BackboneElement	Action to occur as part of plan. This is the backbone element of the care plan that is the root of care coordination activities. While there can be many activities in a care plan, each activity has only one planned.activityRefence	SC	0..*	BackboneElement	Action to occur as part of plan. This is the backbone element of the care plan that is the root of care coordination activities. While there can be many activities in a care plan, each activity has only one planned.activityRefence
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
outcomeCodeableConcept		0..*	CodeableConcept	Results of the activity Binding: ?? (example): Identifies the results of the activity.		0..*	CodeableConcept	Results of the activity Binding: ?? (example): Identifies the results of the activity.
outcomeReference	S	0..*	Reference(Multiple Chronic Condition Care Plan Procedure | Multiple Chronic Condition Care Plan Laboratory Result Observation | US Core Immunization Profile | Multiple Chronic Condition Care Plan Diagnostic Report and Note | US Core Immunization Profile | Multiple Chronic Condition Care Plan Medication Request | Multiple Chronic Condition Care Plan Chronic Disease Conditions | US Core Body Weight Profile | US Core Blood Pressure Profile | Multiple Chronic Condition Care Plan Goal | US Core BMI Profile | Multiple Chronic Condition Care Plan Symptom Observation)	This CarePlan element represents a PERFORMED ACTIVITY. Please see the libraries of available value sets pertinent for use with the appropriate Multiple Chronic Condition Care Plan Profile for use within the referenced profiles at CarePlan.activity.outcomeReference	S	0..*	Reference(Multiple Chronic Condition Care Plan Procedure | Multiple Chronic Condition Care Plan Laboratory Result Observation | US Core Immunization Profile | Multiple Chronic Condition Care Plan Diagnostic Report and Note | US Core Immunization Profile | Multiple Chronic Condition Care Plan Medication Request | Multiple Chronic Condition Care Plan Chronic Disease Conditions | US Core Body Weight Profile | US Core Blood Pressure Profile | Multiple Chronic Condition Care Plan Goal | US Core BMI Profile | Multiple Chronic Condition Care Plan Symptom Observation)	This CarePlan element represents a PERFORMED ACTIVITY. Please see the libraries of available value sets pertinent for use with the appropriate Multiple Chronic Condition Care Plan Profile for use within the referenced profiles at CarePlan.activity.outcomeReference	Elements differ in definition: 'This element details 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). In the MCC Care Plan, CarePlan.activity.OutcomeReference (Must Support) is preferred. Please see the libraries of available value sets (insert link(s)?) pertinent for use with the appropriate Multiple Chronic Condition Care Plan Profile for use within the referenced profiles at CarePlan.activity.outcomeReference. Please also see the Care Plan Profile Relationship diagram for additional guidance <link?>. There is an existing Ticket FHIR- 26064 (https://jira.hl7.org/browse/FHIR-26064) with respect to clarifying the description and names for activity within Care Plan applied in R5: 1. Rename: activity.outcome to performedActivity, 2. Rename: activity.reference to plannedActivityReference, 3. Rename: activity.detail to plannedActivityDetail.' vs 'This element details 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 the CarePlan.activity.reference (a reference to a “request” resource). In the MCC Care Plan, CarePlan.activity.OutcomeReference (Must Support) is preferred over outcomeCodeableConcept. Please see the libraries of available value sets pertinent for use with the appropriate Multiple Chronic Condition Care Plan Profile for use within the referenced profiles at CarePlan.activity.outcomeReference. Please also see the Care Plan Profile Relationship diagram for additional guidance <link?>. There is an existing Ticket FHIR- 26064 (https://jira.hl7.org/browse/FHIR-26064) with respect to clarifying the description and names for activity within Care Plan applied in R5: 1. Rename: activity.outcome to performedActivity, 2. Rename: activity.reference to plannedActivityReference. The R5 CarePlan does not have activity.detail, accordingly the MCC CarePlan prefers the use of the targeted reference of activity.outcomeReference for details.'
progress		0..*	Annotation	Comments about the activity status/progress		0..*	Annotation	Comments about the activity status/progress
reference	SC	0..1	Reference(NutritionOrder | Multiple Chronic Condition Care Plan Medication Request | CommunicationRequest | DeviceRequest | Task | ServiceRequest | VisionPrescription | RequestGroup | Appointment)	This CarePlan element represents a PLANNED ACTIVITY. Please see the libraries of available value sets pertinent for use with the appropriate Multiple Chronic Condition Care Plan Profile for use within the referenced profiles at CarePlan.activityReference	SC	0..1	Reference(NutritionOrder | Multiple Chronic Condition Care Plan Medication Request | CommunicationRequest | DeviceRequest | Task | ServiceRequest | VisionPrescription | RequestGroup | Appointment)	This CarePlan element represents a PLANNED ACTIVITY. Please see the libraries of available value sets pertinent for use with the appropriate Multiple Chronic Condition Care Plan Profile for use within the referenced profiles at CarePlan.activity.reference	Elements differ in short: 'This CarePlan element represents a PLANNED ACTIVITY. Please see the libraries of available value sets pertinent for use with the appropriate Multiple Chronic Condition Care Plan Profile for use within the referenced profiles at CarePlan.activityReference' vs 'This CarePlan element represents a PLANNED ACTIVITY. Please see the libraries of available value sets pertinent for use with the appropriate Multiple Chronic Condition Care Plan Profile for use within the referenced profiles at CarePlan.activity.reference' Elements differ in definition: 'This CarePlan element holds the details of the proposed activity represented in a specific resource. Planned activities represent ordered or planned activities that are part of the Care Plan. Please see the libraries of available value sets (insert link(s)?) pertinent for use with the appropriate Multiple Chronic Condition Care Plan Profile for use within the referenced profiles at CarePlan.activityReference. The referred to profiles are suggested for use within the MCC Care Plan, but additional ServiceRequest may be used. When US Core R5 is published. US Core Service Request will be used and may be profiled to add additional requirements for whn serviceRequest is used within a FHIR Care Plan There is an existing Ticket FHIR- 26064 (https://jira.hl7.org/browse/FHIR-26064) with respect to clarifying the description and names for activity within Care Plan applied in R5: 1. Rename: activity.outcome to performedActivity, 2. Rename: activity.reference to plannedActivityReference, 3. Rename: activity.detail to plannedActivityDetail.' vs 'This CarePlan element holds the details of the proposed activity represented in a specific resource. Planned activities represent ordered or planned activities that are part of the Care Plan. Please see the libraries of available value sets pertinent for use with the appropriate Multiple Chronic Condition Care Plan Profile for use within the referenced profiles at CarePlan.activity.reference. The referred to profiles are suggested for use within the MCC Care Plan, but additional ServiceRequest may be used. When US Core R5 is published. US Core Service Request will be used and may be profiled to add additional requirements for when serviceRequest is used within a FHIR Care Plan There is an existing Ticket FHIR- 26064 (https://jira.hl7.org/browse/FHIR-26064) with respect to clarifying the description and names for activity within Care Plan applied in R5: 1. Rename: activity.outcome to performedActivity, 2. Rename: activity.reference to plannedActivityReference. The R5 CarePlan does not have activity.detail, accordingly the MCC CarePlan prefers the use of the targeted reference for activity.reference to provide details.'
detail	C	0..0			C	0..0
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
kind		0..1	code	Appointment | CommunicationRequest | DeviceRequest | MedicationRequest | NutritionOrder | Task | ServiceRequest | VisionPrescription Binding: ?? (required): Resource types defined as part of FHIR that can be represented as in-line definitions of a care plan activity.		0..1	code	Appointment | CommunicationRequest | DeviceRequest | MedicationRequest | NutritionOrder | Task | ServiceRequest | VisionPrescription Binding: ?? (required): Resource types defined as part of FHIR that can be represented as in-line definitions of a care plan activity.
instantiatesCanonical		0..*	canonical(PlanDefinition | ActivityDefinition | Questionnaire | Measure | OperationDefinition)	Instantiates FHIR protocol or definition		0..*	canonical(PlanDefinition | ActivityDefinition | Questionnaire | Measure | OperationDefinition)	Instantiates FHIR protocol or definition
instantiatesUri		0..*	uri	Instantiates external protocol or definition		0..*	uri	Instantiates external protocol or definition
code		0..1	CodeableConcept	Detail type of activity Binding: ?? (example): Detailed description of the type of activity; e.g. What lab test, what procedure, what kind of encounter.		0..1	CodeableConcept	Detail type of activity Binding: ?? (example): Detailed description of the type of activity; e.g. What lab test, what procedure, what kind of encounter.
reasonCode		0..*	CodeableConcept	Why activity should be done or why activity was prohibited Binding: ?? (example): Identifies 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.		0..*	CodeableConcept	Why activity should be done or why activity was prohibited Binding: ?? (example): Identifies 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.
reasonReference		0..*	Reference(Condition | Observation | DiagnosticReport | DocumentReference)	Why activity is needed		0..*	Reference(Condition | Observation | DiagnosticReport | DocumentReference)	Why activity is needed
goal		0..*	Reference(Goal)	Goals this activity relates to		0..*	Reference(Goal)	Goals this activity relates to
status	?!	1..1	code	not-started | scheduled | in-progress | on-hold | completed | cancelled | stopped | unknown | entered-in-error Binding: ?? (required): Codes that reflect the current state of a care plan activity within its overall life cycle.	?!	1..1	code	not-started | scheduled | in-progress | on-hold | completed | cancelled | stopped | unknown | entered-in-error Binding: ?? (required): Codes that reflect the current state of a care plan activity within its overall life cycle.
statusReason		0..1	CodeableConcept	Reason for current status		0..1	CodeableConcept	Reason for current status
doNotPerform	?!	0..1	boolean	If true, activity is prohibiting action	?!	0..1	boolean	If true, activity is prohibiting action
scheduled[x]		0..1	Timing, Period, string	When activity is to occur		0..1	Timing, Period, string	When activity is to occur
location		0..1	Reference(Location)	Where it should happen		0..1	Reference(Location)	Where it should happen
performer		0..*	Reference(Practitioner | PractitionerRole | Organization | RelatedPerson | Patient | CareTeam | HealthcareService | Device)	Who will be responsible?		0..*	Reference(Practitioner | PractitionerRole | Organization | RelatedPerson | Patient | CareTeam | HealthcareService | Device)	Who will be responsible?
product[x]		0..1	CodeableConcept, Reference(Medication | Substance)	What is to be administered/supplied Binding: ?? (example): A product supplied or administered as part of a care plan activity.		0..1	CodeableConcept, Reference(Medication | Substance)	What is to be administered/supplied Binding: ?? (example): A product supplied or administered as part of a care plan activity.
dailyAmount		0..1	??	How to consume/day?		0..1	??	How to consume/day?
quantity		0..1	??	How much to administer/supply/consume		0..1	??	How much to administer/supply/consume
description		0..1	string	Extra info describing activity to perform		0..1	string	Extra info describing activity to perform
note		0..*	Annotation	Comments about the plan		0..*	Annotation	Comments about the plan
Documentation for this format