HL7 FHIR CarePlan Resource: Goal, Condition & ServiceRequest Linkage and US Core Profile

The FHIR CarePlan resource (CarePlan in HL7 FHIR R4) defines the structured clinical intention of how one or more practitioners, care teams, and patients plan to deliver longitudinal care for a specific patient, group, or population over a designated period.

In health informatics and electronic health record (EHR) interoperability, CarePlan serves two distinct architectural roles: (1) exchanging the clinician’s narrative Assessment and Plan (A&P) section under US Core FHIR certification rules, and (2) orchestrating a computable, multidisciplinary electronic care plan (eCare Plan) that links problems (Condition), patient-centered targets (Goal), care team participants (CareTeam), and planned clinical interventions (FHIR MedicationRequest, ServiceRequest, and NutritionOrder).

What Is the FHIR CarePlan Resource?

When clinical interoperability engineers examine what is the FHIR CarePlan resource, they position it within the HL7 FHIR Workflow Request pattern. Whereas a definitional protocol or order set template is represented by a PlanDefinition (see clinical order sets), a CarePlan is instantiated for a specific patient (CarePlan.subject) and tracks both the high-level clinical strategy and the status of individual planned activities:

• Lifecycle Status (CarePlan.status, 1..1): Controlled by the required value set draft | active | on-hold | revoked | completed | entered-in-error | unknown.
• Clinical Intent (CarePlan.intent, 1..1): Distinguishes whether the resource represents a preliminary proposal, a collaborative care plan, an actionable clinical order, or a protocol option.
• Protocol Instantiation (instantiatesCanonical & basedOn): Links a patient’s active CarePlan back to the standardized evidence-based clinical pathway (Canonical(PlanDefinition | Questionnaire | Measure)) or a higher-level parent CarePlan from which it was derived.
• Hierarchical Composition (partOf & replaces): Allows specialty sub-plans (such as an oncology chemotherapy plan, a physical therapy rehabilitation plan, or a behavioral health treatment plan) to link into an overarching primary care master CarePlan via CarePlan.partOf.

Core FHIR R4 CarePlan Elements and C-CDA Crosswalk

In health information exchange pipelines converting HL7 C-CDA R2.1 Care Plan Documents (template OID 2.16.840.1.113883.10.20.22.1.15) and Assessment and Plan sections (LOINC 51847-2) into FHIR R4, see C-CDA to FHIR, the core fields map as follows:

FHIR R4 CarePlan Element	Cardinality	Data Type & Target Profiles	Clinical Role & C-CDA Equivalent
status	1..1	code (active, completed, on-hold, etc.)	Current operational state of the care plan
intent	1..1	code (proposal | plan | order | option)	C-CDA moodCode (INT for intent, PRP for proposal)
category	0..*	CodeableConcept (assess-plan or SNOMED category)	Classifies narrative A&P vs longitudinal specialty care plan
subject	1..1	Reference(Patient | Group)	C-CDA recordTarget / patientRole
period	0..1	Period (start and end timestamps)	Timeframe over which the care plan covers clinical management
careTeam	0..*	Reference(CareTeam)	Multidisciplinary practitioners, caregivers, and patient participants
addresses	0..*	Reference(Condition)	C-CDA Health Concerns Section: diagnoses/problems managed by the plan
goal	0..*	Reference(Goal)	C-CDA Goals Section (2.16.840.1.113883.10.20.22.2.60)
activity	0..*	BackboneElement (reference or inline detail)	C-CDA Interventions / Planned Acts (orders, procedures, education)

How Does FHIR CarePlan Link to Goal, Condition, and ServiceRequest?

Understanding how does FHIR CarePlan link to Goal, Condition, and ServiceRequest is the key to building longitudinal chronic care management and post-acute transitions-of-care platforms. Rather than duplicating clinical data inside text blobs, CarePlan acts as a relational hub connecting four distinct FHIR resource types:

                      +---> addresses[]: Reference(Condition/type-2-diabetes)
                      |
                      +---> careTeam[]:  Reference(CareTeam/multidisciplinary-team)
                      |
CarePlan (Hub) -------+---> goal[]:      Reference(Goal/hba1c-below-7-percent)
                      |                       ^
                      |                       | outcomeReference / addresses
                      +---> activity[]: ------+
                              |--> reference: Reference(ServiceRequest/cgm-referral)
                              |--> reference: Reference(MedicationRequest/metformin)
                              +--> detail:    { kind, code, status, scheduledTiming }

1. Linking Problems (`CarePlan.addresses` -> `Condition`): The addresses array points to active Condition resources on the patient’s Problem List or Health Concerns list (such as Stage 3b Chronic Kidney Disease or Heart Failure with Reduced Ejection Fraction), explicitly answering why the care plan exists.
2. Linking Measurable Targets (`CarePlan.goal` -> `Goal`): The goal array references discrete FHIR Goal resources. Each Goal specifies a target measure (e.g., LOINC 4548-4 HbA1c < 7.0% or LOINC 29463-7 Body Weight target) and a target.dueDate, and links back to the underlying Condition via Goal.addresses.
3. Linking Planned Interventions (`CarePlan.activity` -> `ServiceRequest` / `MedicationRequest`): Each entry in CarePlan.activity[] represents an actionable step toward achieving one or more goals (activity.detail.goal) and is represented in one of two ways (enforced by invariant cpl-3: detail.empty() or reference.empty()):
   • External Resource Reference (`activity.reference`): Points to a standalone FHIR request resource—such as a ServiceRequest (diagnostic lab order, physical therapy referral, or home health order), a MedicationRequest, a NutritionOrder, or a Task.
   • Inline Summary (`activity.detail`): Embeds a lightweight planned activity directly inside the CarePlan (using detail.kind, detail.code, detail.status [not-started | scheduled | in-progress | on-hold | completed | cancelled], and detail.scheduledTiming) for patient self-management tasks (such as daily home weight checks or 30 minutes of aerobic exercise) that do not generate formal hospital orders.
4. Tracking Activity Outcomes (`activity.outcomeCodeableConcept` & `outcomeReference`): Links the completed intervention to the resulting Observation, Procedure, or DiagnosticReport that proves the activity was carried out.

How Is US Core CarePlan Profiled for ONC Certification?

Developers asking how is US Core CarePlan profiled for ONC certification must understand a critical pragmatic design choice made in the HL7 US Core Implementation Guide (STU 3.1.1 through STU 6.1.0) to support the US Core Data for Interoperability (USCDI) Assessment and Plan of Treatment data class:

• Required `assess-plan` Category Slice: Every conformant US Core CarePlan must populate CarePlan.category with the code assess-plan from code system http://hl7.org/fhir/us/core/CodeSystem/careplan-category.
• Mandatory XHTML Narrative (`CarePlan.text`): Because most clinicians author their outpatient or inpatient assessment and plan template as rich clinical prose inside the EHR progress note rather than discrete database rows, the US Core CarePlan Profile elevates CarePlan.text (`1..1` MustSupport) with text.status (generated | extensions | additional) and text.div (valid XHTML narrative).
• Advancing to Structured eCare Plans (HL7 MCC Care Plan IG): While US Core guarantees baseline interoperability of narrative A&P text across all certified EHRs, specialized HL7 Implementation Guides—such as the HL7 / NIDDK Multiple Chronic Conditions (MCC) Electronic Care Plan IG and the HL7 Gravity Project SDOH Clinical Care IG—profile the full relational graph (addresses, goal, careTeam, and activity.reference) to enable automated chronic disease registries and closed-loop social care coordination.

Frequently Asked Questions

What is the FHIR CarePlan resource?

The HL7 FHIR CarePlan resource is a clinical workflow resource that documents how one or more healthcare providers, care teams, and patients intend to manage a patient’s health conditions over time, capturing either a narrative Assessment and Plan or a structured graph of conditions, goals, care team members, and planned interventions.

How does FHIR CarePlan link to Goal, Condition, and ServiceRequest?

CarePlan links to the diagnoses or health concerns it manages via CarePlan.addresses (Reference(Condition)), to measurable clinical or patient-reported targets via CarePlan.goal (Reference(Goal)), to participating clinicians and caregivers via CarePlan.careTeam (Reference(CareTeam)), and to specific orders or referrals via CarePlan.activity.reference (Reference(ServiceRequest | MedicationRequest | NutritionOrder | Task)).

How is US Core CarePlan profiled for ONC certification?

To satisfy ONC 45 CFR § 170.315(g)(10) and USCDI Assessment and Plan of Treatment requirements, the US Core CarePlan Profile requires status, intent, subject, a category slice fixed to assess-plan, and a mandatory XHTML narrative block in CarePlan.text.div containing the clinician’s Assessment and Plan narrative.

Sources

• HL7 International — FHIR R4 CarePlan Resource Specification
• HL7 US Core Implementation Guide — US Core CarePlan Profile
• HL7 International / NIDDK — Multiple Chronic Conditions (MCC) Electronic Care Plan Implementation Guide