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

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/StructureDefinition/CarePlan
copyright
date	2019-08-29	2020-03-29	Values Differ
description	Defines constraints and extensions on the CarePlan resource for the minimal set of data to query and retrieve a patient's Care Plan.	This profile constrains the FHIR Care Plan Resource to represent the requirements of a care plan for patients with multiple chronic conditions.	Values Differ
experimental	false		Removed the item 'false'
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]	urn:iso:std:iso:3166#US		Removed the item 'urn:iso:std:iso:3166#US'
jurisdiction[1]		urn:iso:std:iso:3166:-2#US	Added the item 'urn:iso:std:iso:3166:-2#US'
kind	resource
name	USCoreCarePlanProfile	MCCCarePLan	Values Differ
publisher	HL7 US Realm Steering Committee	HL7 International - Patient Care WG	Values Differ
purpose
status	active
title	US Core CarePlan Profile	Multiple Chronic Care Condition Care Plan	Values Differ
type	CarePlan
url	http://hl7.org/fhir/us/core/StructureDefinition/us-core-careplan	http://hl7.org/fhir/us/mcc/StructureDefinition/mccCarePlan	Values Differ
version	3.1.1	0.1.0	Values Differ

Structure

Name	L Flags	L Card.	L Type	L Description & Constraints	R Flags	R Card.	L Type	L Description & Constraints	Comments
CarePlan									Elements differ in definition: "The US Core CarePlan Profile is based upon the core FHIR CarePlan Resource and created to meet the 2015 Edition Common Clinical Data Set 'Assessment and Plan of Treatment requirements." "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."
id	Σ				Σ
meta	Σ				Σ
implicitRules	?!Σ				?!Σ
language
text	S								Elements differ in definition for mustSupport: "true" "false"
id
extension			Extension				Extension
status	S								Elements differ in definition: "generated | additional." "The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data." Elements differ in definition for mustSupport: "true" "false" Elements differ in description: "Constrained value set of narrative statuses." "The status of a resource narrative." Elements differ in description: "Constrained value set of narrative statuses." "The status of a resource narrative."
div	I				I
contained
extension			Extension				Extension
modifierExtension	?!				?!
identifier	Σ				Σ
instantiatesCanonical	Σ				Σ
instantiatesUri	Σ				Σ
basedOn	Σ				Σ
replaces	Σ				Σ
partOf	Σ				Σ
status	?!SΣ				?!SΣ				Elements differ in requirements: "Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record." "Allows clinicians to determine whether the plan is actionable or not."
intent	?!SΣ				?!SΣ				Elements differ in description: "Codes indicating the degree of authority/intentionality associated with a care plan" "Codes indicating the degree of authority/intentionality associated with a care plan." Elements differ in description: "Codes indicating the degree of authority/intentionality associated with a care plan" "Codes indicating the degree of authority/intentionality associated with a care plan."
category	SΣ		(Slice Definition)		Σ				Elements differ in short: "Type of plan" "Care Plan category code describes the type of care plan. Please see CarePlan.category detail for guidance." Elements differ in definition: "Type of plan." "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." Elements differ in requirements: "Identifies what "kind" of plan this is to support differentiation between multiple co-existing plans; e.g. "Home health", "psychiatric", "asthma", "disease management", "wellness plan", etc." "Used for filtering what plan(s) are retrieved and displayed to different types of users." Elements differ in definition for mustSupport: "true" "false"
title	Σ				Σ
description	Σ				Σ
subject	SΣ				Σ				Elements differ in definition: "Who care plan is for." "Identifies the patient or group whose intended care is described by the plan." Elements differ in definition for mustSupport: "true" "false"
encounter	Σ				Σ
period	Σ				Σ
created	Σ				Σ
author	Σ				SΣ				Elements differ in short: "Who is the designated responsible party" "Who is the designated responsible party. CUSTODIAN OR CARE PLAN OWNER" Elements differ in definition: "When populated, the author is responsible for the care plan. The care plan is attributed to the author." " Who is the designated responsible party. (CarePlan.author to be renamed to CarePlan.custodian in R5)" Elements differ in definition for mustSupport: "false" "true"
contributor					S				Elements differ in definition for mustSupport: "false" "true"
careTeam					S				Elements differ in definition for mustSupport: "false" "true"
addresses	Σ				Σ		(Slice Definition)
supportingInfo					S				Elements differ in short: "Information considered as part of plan" "Please see library of available MCC US Core conformant profiles to use for supportingInfo on the Artifact Index page. Any of the MCC defined profiles may be used to represent supporting information" Elements differ in 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." "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." Elements differ in definition for mustSupport: "false" "true"
goal									Elements differ in short: "Desired outcome of plan" "This Goal represents one or more overarching goal applicable to the entire care plan" Elements differ in definition: "Describes the intended objective(s) of carrying out the care plan." "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."
activity	I				SI				Elements differ in short: "Action to occur as part of plan" "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" Elements differ in definition for mustSupport: "false" "true"
id
extension			Extension				Extension
modifierExtension	?!Σ				?!Σ
outcomeCodeableConcept
outcomeReference					S				Elements differ in short: "Appointment, Encounter, Procedure, etc." "PERFORMED ACTIVITY. Please see library of available MCC US Core conformant profiles to use for CarePlan.outcomeReference on the Artifact Index page." Elements differ in 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)." "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." Elements differ in definition for mustSupport: "false" "true"
progress
reference	I				SI				Elements differ in short: "Activity details defined in specific resource" "PLANNED ACTIVITY. Please see library of available MCC US Core conformant profiles to use for CarePlan.activityReference on the Artifact Index page." Elements differ in definition: "The details of the proposed activity represented in a specific resource." "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." Elements differ in definition for mustSupport: "false" "true" Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Appointment], CanonicalType[http://hl7.org/fhir/StructureDefinition/CommunicationRequest], CanonicalType[http://hl7.org/fhir/StructureDefinition/DeviceRequest], CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationRequest], CanonicalType[http://hl7.org/fhir/StructureDefinition/NutritionOrder], CanonicalType[http://hl7.org/fhir/StructureDefinition/Task], CanonicalType[http://hl7.org/fhir/StructureDefinition/ServiceRequest], CanonicalType[http://hl7.org/fhir/StructureDefinition/VisionPrescription], CanonicalType[http://hl7.org/fhir/StructureDefinition/RequestGroup]]) Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/NutritionOrder], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-medicationrequest], CanonicalType[http://hl7.org/fhir/StructureDefinition/CommunicationRequest], CanonicalType[http://hl7.org/fhir/StructureDefinition/DeviceRequest], CanonicalType[http://hl7.org/fhir/StructureDefinition/Task], CanonicalType[http://hl7.org/fhir/StructureDefinition/ServiceRequest], CanonicalType[http://hl7.org/fhir/StructureDefinition/VisionPrescription], CanonicalType[http://hl7.org/fhir/StructureDefinition/RequestGroup], CanonicalType[http://hl7.org/fhir/StructureDefinition/Appointment]])
detail	I				I				Elements differ in short: "In-line definition of activity" "CarePlan.activity.detail SHALL NOT be used in the MCC eCare Plan"
id
extension			Extension				Extension
modifierExtension	?!Σ				?!Σ
kind
instantiatesCanonical
instantiatesUri
code
reasonCode
reasonReference
goal
status	?!				?!
statusReason
doNotPerform	?!				?!
scheduled[x]
location
performer
product[x]
dailyAmount
quantity
description
note
Documentation for this format