Logical model representing a draft Care Plan structure, including ownership, goals, evidence, and activities with outcomes.

Human-friendly title of the care plan.

Narrative description of the care plan.

Workflow/lifecycle status of the care plan.

Categorization of the care plan (e.g., rehab, chronic care, oncology).

Time period the care plan covers.

Person or organization responsible for creating the care plan.

CareTeam or responsible organization having charge of the 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 basis for this care plan.

Goals defined by the care team; not always visible to the patient.

Goals expressed by the patient; visible to the patient.

Planned or performed activities as part of the care plan.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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.

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

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.

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.

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

Outcome(s) captured for the activity.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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.

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

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.

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.

Short textual summary of the outcome.

References to observations/documents or other evidence supporting the outcome.

Logical model representing a draft Care Plan structure, including ownership, goals, evidence, and activities with outcomes.

Human-friendly title of the care plan.

Narrative description of the care plan.

Workflow/lifecycle status of the care plan.

Categorization of the care plan (e.g., rehab, chronic care, oncology).

Time period the care plan covers.

Person or organization responsible for creating the care plan.

CareTeam or responsible organization having charge of the 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 basis for this care plan.

Goals defined by the care team; not always visible to the patient.

Goals expressed by the patient; visible to the patient.

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

Outcome(s) captured for the activity.

Short textual summary of the outcome.

References to observations/documents or other evidence supporting the outcome.

Logical model representing a draft Care Plan structure, including ownership, goals, evidence, and activities with outcomes.

Human-friendly title of the care plan.

Narrative description of the care plan.

Workflow/lifecycle status of the care plan.

Categorization of the care plan (e.g., rehab, chronic care, oncology).

Time period the care plan covers.

Person or organization responsible for creating the care plan.

CareTeam or responsible organization having charge of the 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 basis for this care plan.

Goals defined by the care team; not always visible to the patient.

Goals expressed by the patient; visible to the patient.

Planned or performed activities as part of the care plan.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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.

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

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.

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.

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

Outcome(s) captured for the activity.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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.

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

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.

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.

Short textual summary of the outcome.

References to observations/documents or other evidence supporting the outcome.