STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

M.?? StructureDefinition: C-CDA on FHIR Care Plan

The official URL for this profile is: 

http://hl7.org/fhir/StructureDefinition/ccda-care-plan-composition

CARE PLAN FRAMEWORK. Care Plan (including Home Health Plan of Care (HHPoC)) is a consensus-driven dynamic plan that represents a patient’s and Care Team Members’ prioritized concerns, goals, and planned interventions. It serves as a blueprint shared by all Care Team Members (including the patient, their caregivers and providers), to guide the patient’s care. A Care Plan integrates multiple interventions proposed by multiple providers and disciplines for multiple conditions. A Care Plan represents one or more Plan(s) of Care and serves to reconcile and resolve conflicts between the various Plans of Care developed for a specific patient by different providers. While both a plan of care and a care plan include the patient’s life goals and require Care Team Members (including patients) to prioritize goals and interventions, the reconciliation process becomes more complex as the number of plans of care increases. The Care Plan also serves to enable longitudinal coordination of care. The Care Plan represents an instance of this dynamic Care Plan at a point in time. The composition itself is NOT dynamic. Key differentiators between a Care Plan profile and CCD profile (another “snapshot in time” document): • Requires relationships between various acts: o Health Concerns o Problems o Interventions o Goals o Outcomes • Provides the ability to identify patient and provider priorities with each act • Provides a header participant to indicate occurrences of Care Plan review

This profile was published on [no date] with unknown status '" by .

M.??.1 Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.

This structure is derived from Composition.

Summary

Mandatory: 9 elements (+6 nested mandatory elements)
Fixed Value: 5 elements

Slices

This structure defines the following Slices:

  • The element Composition.section is sliced based on the value of Composition.section.code

This structure is derived from Composition.

NameFlagsCard.TypeDescription & Constraintsdoco
.. Composition 0..*DomainResource
... type 1..1CodeableConcepttype
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"52521-2"}]}
... section BackboneElementSlice: Unordered, Open, by Composition.section.code
... section 1..1BackboneElementsection
.... title 1..1stringtitle
.... code 1..1CodeableConceptcode
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"75310-3"}]}
.... text 1..1Narrativetext
... section 1..1BackboneElementsection
.... title 1..1stringtitle
.... code 1..1CodeableConceptcode
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"61146-7"}]}
.... text 1..1Narrativetext
... section 0..1BackboneElementsection
.... title 1..1stringtitle
.... code 1..1CodeableConceptcode
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"62387-6"}]}
.... text 1..1Narrativetext
... section 0..1BackboneElementsection
.... title 1..1stringtitle
.... code 1..1CodeableConceptcode
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"11383-7"}]}
.... text 1..1Narrativetext

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. Composition 0..*DomainResourceA set of resources composed into a single coherent clinical statement with clinical attestation
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier ∑0..1IdentifierLogical identifier of composition (version-independent)
... date ∑1..1dateTimeComposition editing time
... type ∑1..1CodeableConcepttype
Binding: FHIR Document Type Codes (preferred)
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"52521-2"}]}
... class ∑0..1CodeableConceptCategorization of Composition
Binding: FHIR Document Class Codes (example)
... title ∑1..1stringHuman Readable name/title
... status ?! ∑1..1codepreliminary | final | amended | entered-in-error
Binding: CompositionStatus (required)
... confidentiality ?! ∑0..1codeAs defined by affinity domain
Binding: v3 Code System Confidentiality (required)
... subject ∑1..1Reference(Resource)Who and/or what the composition is about
... author ∑1..*Reference(Practitioner | Device | Patient | RelatedPerson)Who and/or what authored the composition
... attester ∑0..*BackboneElementAttests to accuracy of composition
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... mode ∑1..*codepersonal | professional | legal | official
Binding: CompositionAttestationMode (required)
.... time ∑0..1dateTimeWhen composition attested
.... party ∑0..1Reference(Patient | Practitioner | Organization)Who attested the composition
... custodian ∑0..1Reference(Organization)Organization which maintains the composition
... event ∑0..*BackboneElementThe clinical service(s) being documented
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... code ∑0..*CodeableConceptCode(s) that apply to the event being documented
Binding: v3 Code System ActCode (example)
.... period ∑0..1PeriodThe period covered by the documentation
.... detail ∑0..*Reference(Resource)The event(s) being documented
... encounter ∑0..1Reference(Encounter)Context of the Composition
... section IBackboneElementComposition is broken into sections
Slice: Unordered, Open, by Composition.section.code
cmp-2: A section can only have an emptyReason if it is empty
cmp-1: A section must at least one of text, entries, or sub-sections
... section I1..1BackboneElementsection
cmp-2: A section can only have an emptyReason if it is empty
cmp-1: A section must at least one of text, entries, or sub-sections
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... title 1..1stringtitle
.... code 1..1CodeableConceptcode
Binding: Document Section Codes (example)
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"75310-3"}]}
.... text I1..1Narrativetext
.... mode ?! ∑0..1codeworking | snapshot | changes
Binding: ListMode (required)
.... orderedBy 0..1CodeableConceptOrder of section entries
Binding: List Order Codes (preferred)
.... entry I0..*Reference(Resource)A reference to data that supports this section
.... emptyReason I0..1CodeableConceptWhy the section is empty
Binding: List Empty Reasons (preferred)
.... section I0..*Unknown reference to #section
Nested Section
... section I1..1BackboneElementsection
cmp-2: A section can only have an emptyReason if it is empty
cmp-1: A section must at least one of text, entries, or sub-sections
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... title 1..1stringtitle
.... code 1..1CodeableConceptcode
Binding: Document Section Codes (example)
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"61146-7"}]}
.... text I1..1Narrativetext
.... mode ?! ∑0..1codeworking | snapshot | changes
Binding: ListMode (required)
.... orderedBy 0..1CodeableConceptOrder of section entries
Binding: List Order Codes (preferred)
.... entry I0..*Reference(Resource)A reference to data that supports this section
.... emptyReason I0..1CodeableConceptWhy the section is empty
Binding: List Empty Reasons (preferred)
.... section I0..*Unknown reference to #section
Nested Section
... section I0..1BackboneElementsection
cmp-2: A section can only have an emptyReason if it is empty
cmp-1: A section must at least one of text, entries, or sub-sections
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... title 1..1stringtitle
.... code 1..1CodeableConceptcode
Binding: Document Section Codes (example)
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"62387-6"}]}
.... text I1..1Narrativetext
.... mode ?! ∑0..1codeworking | snapshot | changes
Binding: ListMode (required)
.... orderedBy 0..1CodeableConceptOrder of section entries
Binding: List Order Codes (preferred)
.... entry I0..*Reference(Resource)A reference to data that supports this section
.... emptyReason I0..1CodeableConceptWhy the section is empty
Binding: List Empty Reasons (preferred)
.... section I0..*Unknown reference to #section
Nested Section
... section I0..1BackboneElementsection
cmp-2: A section can only have an emptyReason if it is empty
cmp-1: A section must at least one of text, entries, or sub-sections
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... title 1..1stringtitle
.... code 1..1CodeableConceptcode
Binding: Document Section Codes (example)
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"11383-7"}]}
.... text I1..1Narrativetext
.... mode ?! ∑0..1codeworking | snapshot | changes
Binding: ListMode (required)
.... orderedBy 0..1CodeableConceptOrder of section entries
Binding: List Order Codes (preferred)
.... entry I0..*Reference(Resource)A reference to data that supports this section
.... emptyReason I0..1CodeableConceptWhy the section is empty
Binding: List Empty Reasons (preferred)
.... section I0..*Unknown reference to #section
Nested Section

doco Documentation for this format

todo

This structure is derived from Composition.

Summary

Mandatory: 9 elements (+6 nested mandatory elements)
Fixed Value: 5 elements

Slices

This structure defines the following Slices:

  • The element Composition.section is sliced based on the value of Composition.section.code

Differential View

This structure is derived from Composition.

NameFlagsCard.TypeDescription & Constraintsdoco
.. Composition 0..*DomainResource
... type 1..1CodeableConcepttype
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"52521-2"}]}
... section BackboneElementSlice: Unordered, Open, by Composition.section.code
... section 1..1BackboneElementsection
.... title 1..1stringtitle
.... code 1..1CodeableConceptcode
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"75310-3"}]}
.... text 1..1Narrativetext
... section 1..1BackboneElementsection
.... title 1..1stringtitle
.... code 1..1CodeableConceptcode
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"61146-7"}]}
.... text 1..1Narrativetext
... section 0..1BackboneElementsection
.... title 1..1stringtitle
.... code 1..1CodeableConceptcode
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"62387-6"}]}
.... text 1..1Narrativetext
... section 0..1BackboneElementsection
.... title 1..1stringtitle
.... code 1..1CodeableConceptcode
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"11383-7"}]}
.... text 1..1Narrativetext

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Composition 0..*DomainResourceA set of resources composed into a single coherent clinical statement with clinical attestation
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier ∑0..1IdentifierLogical identifier of composition (version-independent)
... date ∑1..1dateTimeComposition editing time
... type ∑1..1CodeableConcepttype
Binding: FHIR Document Type Codes (preferred)
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"52521-2"}]}
... class ∑0..1CodeableConceptCategorization of Composition
Binding: FHIR Document Class Codes (example)
... title ∑1..1stringHuman Readable name/title
... status ?! ∑1..1codepreliminary | final | amended | entered-in-error
Binding: CompositionStatus (required)
... confidentiality ?! ∑0..1codeAs defined by affinity domain
Binding: v3 Code System Confidentiality (required)
... subject ∑1..1Reference(Resource)Who and/or what the composition is about
... author ∑1..*Reference(Practitioner | Device | Patient | RelatedPerson)Who and/or what authored the composition
... attester ∑0..*BackboneElementAttests to accuracy of composition
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... mode ∑1..*codepersonal | professional | legal | official
Binding: CompositionAttestationMode (required)
.... time ∑0..1dateTimeWhen composition attested
.... party ∑0..1Reference(Patient | Practitioner | Organization)Who attested the composition
... custodian ∑0..1Reference(Organization)Organization which maintains the composition
... event ∑0..*BackboneElementThe clinical service(s) being documented
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... code ∑0..*CodeableConceptCode(s) that apply to the event being documented
Binding: v3 Code System ActCode (example)
.... period ∑0..1PeriodThe period covered by the documentation
.... detail ∑0..*Reference(Resource)The event(s) being documented
... encounter ∑0..1Reference(Encounter)Context of the Composition
... section IBackboneElementComposition is broken into sections
Slice: Unordered, Open, by Composition.section.code
cmp-2: A section can only have an emptyReason if it is empty
cmp-1: A section must at least one of text, entries, or sub-sections
... section I1..1BackboneElementsection
cmp-2: A section can only have an emptyReason if it is empty
cmp-1: A section must at least one of text, entries, or sub-sections
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... title 1..1stringtitle
.... code 1..1CodeableConceptcode
Binding: Document Section Codes (example)
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"75310-3"}]}
.... text I1..1Narrativetext
.... mode ?! ∑0..1codeworking | snapshot | changes
Binding: ListMode (required)
.... orderedBy 0..1CodeableConceptOrder of section entries
Binding: List Order Codes (preferred)
.... entry I0..*Reference(Resource)A reference to data that supports this section
.... emptyReason I0..1CodeableConceptWhy the section is empty
Binding: List Empty Reasons (preferred)
.... section I0..*Unknown reference to #section
Nested Section
... section I1..1BackboneElementsection
cmp-2: A section can only have an emptyReason if it is empty
cmp-1: A section must at least one of text, entries, or sub-sections
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... title 1..1stringtitle
.... code 1..1CodeableConceptcode
Binding: Document Section Codes (example)
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"61146-7"}]}
.... text I1..1Narrativetext
.... mode ?! ∑0..1codeworking | snapshot | changes
Binding: ListMode (required)
.... orderedBy 0..1CodeableConceptOrder of section entries
Binding: List Order Codes (preferred)
.... entry I0..*Reference(Resource)A reference to data that supports this section
.... emptyReason I0..1CodeableConceptWhy the section is empty
Binding: List Empty Reasons (preferred)
.... section I0..*Unknown reference to #section
Nested Section
... section I0..1BackboneElementsection
cmp-2: A section can only have an emptyReason if it is empty
cmp-1: A section must at least one of text, entries, or sub-sections
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... title 1..1stringtitle
.... code 1..1CodeableConceptcode
Binding: Document Section Codes (example)
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"62387-6"}]}
.... text I1..1Narrativetext
.... mode ?! ∑0..1codeworking | snapshot | changes
Binding: ListMode (required)
.... orderedBy 0..1CodeableConceptOrder of section entries
Binding: List Order Codes (preferred)
.... entry I0..*Reference(Resource)A reference to data that supports this section
.... emptyReason I0..1CodeableConceptWhy the section is empty
Binding: List Empty Reasons (preferred)
.... section I0..*Unknown reference to #section
Nested Section
... section I0..1BackboneElementsection
cmp-2: A section can only have an emptyReason if it is empty
cmp-1: A section must at least one of text, entries, or sub-sections
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... title 1..1stringtitle
.... code 1..1CodeableConceptcode
Binding: Document Section Codes (example)
Fixed Value: {"coding":[{"system":"urn:oid:2.16.840.1.113883.6.1","code":"11383-7"}]}
.... text I1..1Narrativetext
.... mode ?! ∑0..1codeworking | snapshot | changes
Binding: ListMode (required)
.... orderedBy 0..1CodeableConceptOrder of section entries
Binding: List Order Codes (preferred)
.... entry I0..*Reference(Resource)A reference to data that supports this section
.... emptyReason I0..1CodeableConceptWhy the section is empty
Binding: List Empty Reasons (preferred)
.... section I0..*Unknown reference to #section
Nested Section

doco Documentation for this format

XML Template

JSON Template

todo

 

Other representations of profile: Schematron

M.??.2 Terminology Bindings

PathNameConformanceValueSet
Composition.language?extrequiredhttp://tools.ietf.org/html/bcp47
Composition.typeFHIR Document Type CodespreferredFHIR Document Type Codes
Composition.classFHIR Document Class CodesexampleFHIR Document Class Codes
Composition.statusCompositionStatusrequiredCompositionStatus
Composition.confidentialityv3 Code System Confidentialityrequiredv3 Code System Confidentiality
Composition.attester.modeCompositionAttestationModerequiredCompositionAttestationMode
Composition.event.codev3 Code System ActCodeexamplev3 Code System ActCode
Composition.section.codeDocument Section CodesexampleDocument Section Codes
Composition.section.modeListModerequiredListMode
Composition.section.orderedByList Order CodespreferredList Order Codes
Composition.section.emptyReasonList Empty ReasonspreferredList Empty Reasons
Composition.section.codeDocument Section CodesexampleDocument Section Codes
Composition.section.modeListModerequiredListMode
Composition.section.orderedByList Order CodespreferredList Order Codes
Composition.section.emptyReasonList Empty ReasonspreferredList Empty Reasons
Composition.section.codeDocument Section CodesexampleDocument Section Codes
Composition.section.modeListModerequiredListMode
Composition.section.orderedByList Order CodespreferredList Order Codes
Composition.section.emptyReasonList Empty ReasonspreferredList Empty Reasons
Composition.section.codeDocument Section CodesexampleDocument Section Codes
Composition.section.modeListModerequiredListMode
Composition.section.orderedByList Order CodespreferredList Order Codes
Composition.section.emptyReasonList Empty ReasonspreferredList Empty Reasons

M.??.3 Constraints

IdPathDetailsRequirements
cmp-2Composition.sectionA section can only have an emptyReason if it is empty
XPath: not(exists(f:emptyReason) and exists(f:entry))
cmp-1Composition.sectionA section must at least one of text, entries, or sub-sections
XPath: exists(f:text) or exists(f:entry) or exists(f:section)
cmp-2Composition.sectionA section can only have an emptyReason if it is empty
XPath: not(exists(f:emptyReason) and exists(f:entry))
cmp-1Composition.sectionA section must at least one of text, entries, or sub-sections
XPath: exists(f:text) or exists(f:entry) or exists(f:section)
cmp-2Composition.sectionA section can only have an emptyReason if it is empty
XPath: not(exists(f:emptyReason) and exists(f:entry))
cmp-1Composition.sectionA section must at least one of text, entries, or sub-sections
XPath: exists(f:text) or exists(f:entry) or exists(f:section)
cmp-2Composition.sectionA section can only have an emptyReason if it is empty
XPath: not(exists(f:emptyReason) and exists(f:entry))
cmp-1Composition.sectionA section must at least one of text, entries, or sub-sections
XPath: exists(f:text) or exists(f:entry) or exists(f:section)
cmp-2Composition.sectionA section can only have an emptyReason if it is empty
XPath: not(exists(f:emptyReason) and exists(f:entry))
cmp-1Composition.sectionA section must at least one of text, entries, or sub-sections
XPath: exists(f:text) or exists(f:entry) or exists(f:section)
.