0.1.0 - ci-build
CarePlanDAM - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
Identifying a concern, creating goals, identifying interventions, etc. (no "Plan" artifact necessary)
| Barrier |
A factor that impedes progress toward goals or planned activities. Examples include a food desert that prevents a healthy eating, an injury that prevents exercise, and lack of transportation to rehabilitation center. |
| Care Delivery Resource |
A resource used in care provision, such as a provider, a medication, or a third-party service |
| Care Plan Goal |
A goal in the care plan. Possible relationship to concern, planned activity, performed activity, observation. |
| Care Plan Patient |
A person under the care of one or more healthcare service providers |
| Care Team |
A team of individuals involved in the patient's care. For more details, consult the Care Team Domain Analysis Model. |
| Care Team Member |
A person, including the patient, responsible for clinical or ancillary healthcare services for a patient. A care team member may have various roles in the Care Plan process, such as authoring a plan element or performing an activity execution. |
| Concern |
A health concern or condition addressed by the care plan |
| Health Risk |
A risk identified to the patient's health, not to include risks to care team members, intervention efficacy, etc. |
| PartOf |
Abstract pattern for elements that can be organized in hierarchical compositions |
| Planned Activity |
An activity planned as part of the care plan |
| Preference |
A patient or care team preference that informs care planning |
| Priority |
Abstract pattern for elements that can be prioritized |
| Protective Factor |
A characteristic of the patient or patient's community that reduces health risks or overcomes barriers |
| Resource Requirement |
A resource needed to perform an activity |
The process of instantiating a plan using the MVC pattern - data (Model) flows through specifications (Controller) to produce manifestations (View) as Paper Documents, User Interfaces, or API Payloads
| API Plan Payload |
A care plan manifested as a digital payload for system exchange |
| Care Plan Definition |
A definition or template for care plans |
| Care Plan Manifestation |
A manifestation of a care plan as a Paper Document, User Interface, or API Payload. May be curated (explicitly authored) or generated (rule-based). Follows the MVC pattern where data flows through controllers to produce views. |
| Change and Reconciliation Data |
Data tracking changes and reconciliation of curated plan data |
| Clinician Assertion of Plan Inclusion |
A clinician's assertion that specific items should be included in the plan |
| Controller |
Base class for the Controller layer in MVC pattern, representing specifications that control how persisted data shows up in manifestations |
| Curated Plan Data |
Data explicitly incuded in a plan, typically with signature and date representing acceptance |
| Data Specification |
Profile, Template, Pathway, Protocol - specifications that define the structure and content of care plan data |
| Document Specification |
Specification for generating plan documents (e.g., CCD, C-CDA templates) |
| Guideline |
An external clinical protocol or pathway that informs the care plan |
| Human Intent |
Abstract representation of human intention that drives care planning |
| Model |
Base class for the Model layer in MVC pattern representing data persistence |
| Payload Specification |
Specification for API payloads |
| Plan Document (curated) |
A document representing a care plan that has been explicitly curated by a provider |
| Plan Document (generated) |
A document generated automatically by rules or queries to represent a care plan |
| Plan Element |
Abstract base class for all care plan content elements to support modeling general capabilities, such as the possibility of being the subject of communication. All plan elements are specific to a Patient. |
| Planning Form (Controller) |
Controller specification for a planning form UI |
| Planning Form (View) |
A user interface form for viewing and entering care plan data |
| Record Data |
Data from clinical records (EHR, CarePlan Application), including record items such as problems, goals, medications, procedures |
| SOAP Note |
Clinician plan in text. May be used to authorize orders or to create an explicit structured Plan. |
| Structured Data |
Clinical data conforming to a data model that can be processed programmatically |
| UI Plan View |
A user interface view of the care plan |
| UI Software Rules |
Rules that control how data is presented in a UI plan view |
| Unstructured Data |
Clinical data not conforming to a structured data model, such as free text notes |
| View |
Base class for the View layer in MVC pattern representing plan manifestations such as paper documents, user interfaces,or API payloads |
Turning two plans into one plan, with attendant questions about provenance, authority, and audience roles
| Organization |
An organization involved in care delivery |
| Reconciliation Act |
An act of assessing multiple plans and determining when respective elements should be merged, superseded, or removed |
| Reconciliation Log |
A record of reconciliation activities |
Assessing the appropriateness of proposed items and the effectiveness of executed items
| Acceptance Review |
A review where acknowledgment decisions are made about plan elements |
| Activity Execution |
An execution of a planned activity |
| Activity Outcome Observation |
An observation characterizing the outcome of an activity execution |
| Communication |
A communication event related to the care plan. A communication can refer to any care plan element, and may belong to a thread of related communications. |
| Communication Thread |
A collection of related communications in which later communications are aware of earlier ones, within security and privacy constraints |
| Modification |
A change made to a plan element adopted from a Guideline |
| Outcome Review |
A review assessing outcomes of performable elements |
| Revision |
Abstract pattern for elements that can be revised over time |
Example instances illustrating a NICU discharge care plan
| Baby Smith |
NICU patient - premature infant |
| Body weight observation |
Observation of infant body weight (LOINC 29463-7) |
| Caregiver education |
Supporting goal: caregivers are educated on infant care |
| Discharge from NICU |
Primary goal for NICU patient: discharge from the unit |
| Feeding execution |
Execution of oral feeding activity |
| Infant formula intake observation |
Observation of infant formula intake over 24 hours (LOINC 80469-0) |
| NICU Nurse - Care Team Member |
Primary NICU nurse caring for the infant |
| NICU Physician - Care Team Member |
Attending neonatologist |
| Nutrition improved |
Outcome review: oral nutrition intake improved |
| On oral nutrition |
Supporting goal: infant can take nutrition orally |
| On room air |
Supporting goal: infant can breathe room air without supplemental oxygen |
| Oral feeding advancement |
Gradual advancement of oral feeding |
| Prematurity |
Health concern: infant born prematurely |
| Respiratory assessment |
Regular respiratory status assessment |
| Respiratory assessment execution |
Execution of respiratory status assessment |
| Respiratory status observation |
Observation of respiratory status (LOINC 53756-3) |
| Respiratory status resolved |
Outcome review: respiratory issues resolved |
| Weigh infant daily |
Daily weight measurement activity |
| Weight gain |
Supporting goal: infant achieves adequate weight gain |
| Weight measurement execution |
Execution of daily weight measurement |
| Weight stabilized |
Outcome review: weight has stabilized |
These define sets of codes used by systems conforming to this implementation guide.
| Acknowledgement Value Set |
Value set for acknowledgment decisions |
| Activity Completion Status Value Set |
Value set for activity completion status |
| Activity Order Status Value Set |
Value set for activity order status |
| Care Plan Definition Value Set |
Value set for care plan definitions |
| Decision Mode Value Set |
Value set for decision modes |
| Modification Type Value Set |
Value set for modification types |
| Outcome Value Set |
Value set for outcome assessment |
| Performance Status Value Set |
Value set for performance status |
| Plan Purpose Value Set |
Value set for plan purposes |
| Preference Context Value Set |
Value set for preference contexts |
| Review Event Value Set |
Value set for review events |
| Specification Type Value Set |
Value set for specification types |
These define new code systems used by systems conforming to this implementation guide.
| Acknowledgement Code System |
Codes for acknowledgment decisions |
| Activity Completion Status Code System |
Codes for activity completion status |
| Activity Order Status Code System |
Codes for activity order status |
| Care Plan Definition Code System |
Codes for types of care plan definitions |
| Decision Mode Code System |
Codes for how decisions are made |
| Modification Type Code System |
Codes for types of modifications |
| Outcome Code System |
Codes for outcome assessment |
| Performance Status Code System |
Codes for performance status of activities |
| Plan Purpose Code System |
Codes for care plan purposes |
| Preference Context Code System |
Codes for preference contexts |
| Review Event Code System |
Codes for events that trigger reviews |
| Specification Type Code System |
Codes for care plan specification types |