us-core-careplan vs PADI-PreferenceCarePlan

Fulfills CarePlan

0..*

Fulfills CarePlan

replaces

0..*

CarePlan replaced by this CarePlan

0..*

CarePlan replaced by this CarePlan

partOf

0..*

Part of referenced CarePlan

0..*

Part of referenced CarePlan

status

?!SΣ

1..1

code

?!Σ

1..1

code

Elements differ in requirements: 'Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record.' vs 'Allows clinicians to determine whether the plan is actionable or not.'
Elements differ in definition for mustSupport: 'true' vs 'false'

intent

?!SΣ

1..1

code

proposal | plan | order | option
Binding: todo (required): Codes indicating the degree of authority/intentionality associated with a care plan

?!Σ

1..1

code

proposal | plan | order | option
Binding: todo (required): Codes indicating the degree of authority/intentionality associated with a care plan.

Required Pattern: proposal

Elements differ in definition for mustSupport: 'true' vs 'false'
Elements differ in description: 'Codes indicating the degree of authority/intentionality associated with a care plan' vs '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' vs 'Codes indicating the degree of authority/intentionality associated with a care plan.'

Slices for category

SΣ

1..*

CodeableConcept

Type of plan
Slice: Unordered, Open by pattern:$this
Binding: todo (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.

1..*

CodeableConcept

Elements differ in definition: 'Type of plan.' vs '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.'
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.' vs 'Used for filtering what plan(s) are retrieved and displayed to different types of users.'
Elements differ in definition for mustSupport: 'true' vs 'false'

title

0..1

string

Human-friendly name for the care plan

SΣ

1..1

string

Human-friendly name for the care plan

Elements differ in definition for mustSupport: 'false' vs 'true'
Element minimum cardinalities differ: '0' vs '1'

description

0..1

string

Summary of nature of plan

0..1

string

Summary of nature of plan

subject

SΣ

1..1

Reference(http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient)

Who the care plan is for

SΣ

1..1

Reference(http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient)

Who the care plan is for

Elements differ in definition: 'Who care plan is for.' vs 'Identifies the patient or group whose intended care is described by the plan.'

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

0..1

Who is the designated responsible party

0..1

Who is the designated responsible party

contributor

0..*

Who provided the content of the care plan

0..*

Who provided the content of the care plan

careTeam

0..*

Reference(CareTeam)

Who's involved in plan?

0..*

Reference(CareTeam)

Who's involved in plan?

addresses

0..*

Reference(Condition)

Health issues this plan addresses

SΣ

1..*

Reference(Condition)

Health issues this plan addresses (use display only for potential conditions the patient does not currently have)

Elements differ in short: 'Health issues this plan addresses' vs 'Health issues this plan addresses (use display only for potential conditions the patient does not currently have)'
Elements differ in 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.' vs 'The conditions or circumstances in which the stated preferences and goals of the care plan apply. If there are no contained or referenceable resources (e.g. these are potential future conditions that do not represent a condition the patient currently has), the display should be in addresses.display. If no specific circumstances, then the display should indicate something like 'General' or 'All''
Elements differ in definition for mustSupport: 'false' vs 'true'
Element minimum cardinalities differ: '0' vs '1'

supportingInfo

0..*

Information considered as part of plan

0..*

Information considered as part of plan

goal

0..*

Reference(Goal)

Desired outcome of plan

1..*

Reference(http://hl7.org/fhir/us/pacio-adi/StructureDefinition/PADI-PersonalInterventionPreference | http://hl7.org/fhir/us/pacio-adi/StructureDefinition/PADI-PersonalGoal | http://hl7.org/fhir/us/pacio-adi/StructureDefinition/PADI-CareExperiencePreference)

Patient's preferences and goals for the scope of this care plan.

Elements differ in short: 'Desired outcome of plan' vs 'Patient's preferences and goals for the scope of this care plan.'
Elements differ in definition for mustSupport: 'false' vs 'true'
Element minimum cardinalities differ: '0' vs '1'

activity

0..*

BackboneElement

Action to occur as part of plan

0..*

BackboneElement

Action to occur as part of plan

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: todo (example): Identifies the results of the activity.

0..*

CodeableConcept

Results of the activity
Binding: todo (example): Identifies the results of the activity.

outcomeReference

0..*

Appointment, Encounter, Procedure, etc.

0..*

Appointment, Encounter, Procedure, etc.

progress

0..*

Annotation

Comments about the activity status/progress

0..*

Annotation

Comments about the activity status/progress

reference

0..1

Activity details defined in specific resource

0..1

Activity details defined in specific resource

detail

0..1

BackboneElement

In-line definition of activity

0..1

BackboneElement

In-line definition of activity

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

0..1

code

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: todo (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: todo (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: todo (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

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

1..1

code

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..*

Who will be responsible?

0..*

Who will be responsible?

product[x]

0..1

CodeableConcept, Reference(Medication | Substance)

What is to be administered/supplied
Binding: todo (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: todo (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