# Conceptual to Logical Model Mapping - xShare Project CarePlan v0.1.0

* [**Table of Contents**](toc.md)
* **Conceptual to Logical Model Mapping**

## Conceptual to Logical Model Mapping

The **data domain** describes the Care Plan data model and the FHIR content specifications used to exchange it.

This page provides an overview of how the key conceptual elements shown in Figure 1 are represented in the Care Plan logical model.

Fig. 1: Care Plan conceptual key data

Figure 2 shows how patient information from the conceptual view is represented in the logical model. The patient is carried through the inherited header subject element, identifying the person whose intended care is described by the plan.

Fig. 2: Patient information mapped to the logical model

Figure 3 focuses on the condition or health concern addressed by the care plan. In the logical model, this clinical context is represented by the `addresses[x]` element, which can identify the problems, concerns, diagnoses, or conditions managed by the plan.

Fig. 3: Condition addressed by the Care Plan

Figure 4 shows how goals are refined in the logical model. A conceptual goal is represented with a description, category, target, due date, and outcome information so that treatment goals and patient-expressed goals can be described consistently.

Fig. 4: Goal information mapped to the logical model

Figure 5 describes how planned or performed activities are represented. The logical model separates the activity grouping from the coded or referenced activity details, workflow status, human-readable description, progress notes, and references to performed activity evidence.

Fig. 5: Activity details and execution information in the logical model

