Union of https://hl7.cz/fhir/core/StructureDefinition/carePlan-cz-core and https://hl7.cz/fhir/core/StructureDefinition/carePlan-cz-core

This is the set of resources that conform to either of the profiles Care plan (CZ Core) (https://hl7.cz/fhir/core/StructureDefinition/carePlan-cz-core) and Care plan (CZ Core) (https://hl7.cz/fhir/core/StructureDefinition/carePlan-cz-core). E.g. what you have to deal with if you get resources conforming to one of them

Structure

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. CarePlan 0..*Healthcare plan for patient or group
... 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: ?? (preferred): A human language.
... text 0..1NarrativeText summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierExternal Ids for this plan
... instantiatesCanonical Σ0..*canonical(PlanDefinition | Questionnaire | Measure | ActivityDefinition | OperationDefinition)Instantiates FHIR protocol or definition
... instantiatesUri Σ0..*uriInstantiates external protocol or definition
... basedOn Σ0..*Reference(Care plan (CZ Core)), Reference(Care plan (CZ Core))Fulfills CarePlan
... replaces Σ0..*Reference(Care plan (CZ Core)), Reference(Care plan (CZ Core))CarePlan replaced by this CarePlan
... partOf Σ0..*Reference(Care plan (CZ Core)), Reference(Care plan (CZ Core))Part of referenced CarePlan
... status ?!Σ1..1codedraft | 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.
... intent ?!Σ1..1codeproposal | plan | order | option
Binding: ?? (required): Codes indicating the degree of authority/intentionality associated with a care plan.
... category Σ0..*CodeableConceptType of plan
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..1stringHuman-friendly name for the care plan
... description Σ0..1stringSummary of nature of plan
... subject Σ1..1Reference(Patient (CZ core) | Patient: Animal (CZ) | Group | #sd-2-cz-patient-core-cz-patient-core)Who the care plan is for
... encounter Σ0..1Reference(Encounter)Encounter created as part of
... period Σ0..1PeriodTime period plan covers
... created Σ0..1dateTimeDate record was first recorded
... author Σ0..1Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Device: Performer/Observer (CZ core) | Patient (CZ core) | Related Person (CZ core) | Organization (CZ core) | CareTeam | #sd-6-cz-practitioner-core-cz-practitioner-core)Who is the designated responsible party
... contributor 0..*Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Device: Performer/Observer (CZ core) | Patient (CZ core) | Related Person (CZ core) | Organization (CZ core) | CareTeam | #sd-6-cz-practitioner-core-cz-practitioner-core)Who provided the content of the care plan
... careTeam 0..*Reference(CareTeam)Who's involved in plan?
... addresses Σ0..*Reference(Condition (CZ core) | #sd-7-condition-cz-core-condition-cz-core)Health issues this plan addresses
... supportingInfo 0..*Reference(Resource)Information considered as part of plan
... goal 0..*Reference(Goal)Desired outcome of plan
... activity C0..*BackboneElementAction to occur as part of plan
Constraints: cpl-3
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... outcomeCodeableConcept 0..*CodeableConceptResults of the activity
Binding: ?? (example): Identifies the results of the activity.
.... outcomeReference 0..*Reference(Resource)Appointment, Encounter, Procedure, etc.
.... progress 0..*AnnotationComments about the activity status/progress
.... reference 0..1Reference(Appointment (CZ Core) | CommunicationRequest | DeviceRequest | MedicationRequest | NutritionOrder | Task | ServiceRequest | VisionPrescription | RequestGroup | #sd-22-appointment-cz-core-appointment-cz-core)Activity details defined in specific resource
.... detail 0..1BackboneElementIn-line definition of activity
..... extension 0..*ExtensionAdditional content defined by implementations
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... kind 0..1codeAppointment | 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
..... instantiatesUri 0..*uriInstantiates external protocol or definition
..... code 0..1CodeableConceptDetail 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..*CodeableConceptWhy 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 (CZ core) | Observation: Medical Test Result (CZ core) | DiagnosticReport (CZ core) | DocumentReference | #sd-7-condition-cz-core-condition-cz-core)Why activity is needed
..... goal 0..*Reference(Goal)Goals this activity relates to
..... status ?!1..1codenot-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..1CodeableConceptReason for current status
..... doNotPerform ?!0..1booleanIf true, activity is prohibiting action
..... scheduled[x] 0..1When activity is to occur
...... scheduledTimingTiming
...... scheduledPeriodPeriod
...... scheduledStringstring
..... location 0..1Reference(Location (CZ core) | #sd-9-cz-location-core-cz-location-core)Where it should happen
..... performer 0..*Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Organization (CZ core) | CareTeam | HealthcareService | Patient (CZ core) | Related Person (CZ core) | Device: Performer/Observer (CZ core) | #sd-6-cz-practitioner-core-cz-practitioner-core)Who will be responsible?
..... product[x] 0..1What is to be administered/supplied
Binding: ?? (example): A product supplied or administered as part of a care plan activity.
...... productCodeableConceptCodeableConcept
...... productReferenceReference(Medication | Substance)
..... dailyAmount 0..1??How to consume/day?
..... quantity 0..1??How much to administer/supply/consume
..... description 0..1stringExtra info describing activity to perform
... note 0..*AnnotationComments about the plan

doco Documentation for this format