Generated Narrative: StructureDefinition Careplan-logical Name Flags Card. Type Description & Constraints Careplan-logical 0..* Base Care Plan (Logical Model) #xD; title 0..1 string Title #xD; description 0..1 markdown Description #xD; status 0..1 code Status #xD; category 0..* CodeableConcept Category #xD; period 0..1 Period Period #xD; author[x] 0..* Author #xD; authorEHDSHealthProfessional EHDSHealthProfessional #xD; authorEHDSOrganisation EHDSOrganisation #xD; careTeam 0..* BackboneElement Care team / organization in charge #xD; member[x] 0..* Care team member #xD; memberEHDSHealthProfessional EHDSHealthProfessional #xD; memberEHDSOrganisation EHDSOrganisation #xD; subject 1..1 EHDSPatient Subject #xD; reason 0..* EHDSCondition Reason (problem/health concern) #xD; supportingInfo 0..* Reference(Resource) Evidence / supporting information #xD; goal 0..* BackboneElement Goal #xD; category 0..1 CodeableConcept Goal category #xD; description 1..1 string Goal description #xD; target 0..1 CodeableConcept Goal target #xD; due 0..1 date Goal due date #xD; activity 0..* BackboneElement Activity #xD; workflowStatus 0..1 code Workflow status #xD; narrative 0..1 markdown Narrative #xD; structured 0..1 Reference(Resource) Reference to formal artifact #xD; outcome 0..* BackboneElement Outcome #xD; summary 0..1 string Outcome summary #xD; evidence 0..* Reference(Resource) Outcome evidence #xD; Documentation for this format
Logical model representing a Care Plan structure with metadata, care team participation, subject and clinical context, goals, supporting information, planned or performed activities, and activity outcomes.
Workflow/lifecycle status of the care plan.
Categorization of the care plan (e.g., rehab, chronic care, oncology).
Person or organization responsible for creating the care plan.
Care team or responsible organization in charge of the plan.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. 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.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
References to practitioners, organizations, or related persons involved in the care plan.
The patient who is the subject of this care plan.
Problems/health concerns prompting the care plan.
Evidence or other supporting information used as the basis for this care plan.
Goals defined for the care plan, including treatment goals defined by the care team and patient goals expressed by the patient.
Categorization of the goal (e.g., treatment goal, patient goal).
Date by which the goal should be met or reviewed.
Planned or performed activities as part of the care plan.
Workflow status of the activity (e.g., planned, in-progress, completed, stopped).
Human-readable narrative describing the activity.
Reference to a formal request/performance (e.g., ServiceRequest, Procedure, Task).
References to observations/documents or other evidence supporting the outcome.