Nerve
FHIRResources

CarePlan

Maturity LevelSecurity CategoryResource Category
2Patient
Clinical

Describes the intention of how one or more practitioners intend to deliver care for a particular patient, group or community for a period of time, possibly limited to care for a specific condition or set of conditions.

Resource Content

NameCard.TypeDescription
TUDomainResourceHealthcare plan for patient or group
Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
identifier0..*IdentifierExternal Ids for this plan
instantiatesCanonical0..*canonical(PlanDefinition | Questionnaire | Measure | ActivityDefinition | OperationDefinition)Instantiates FHIR protocol or definition
instantiatesUri0..*uriInstantiates external protocol or definition
basedOn0..*Reference(CarePlan)Fulfills CarePlan
replaces0..*Reference(CarePlan)CarePlan replaced by this CarePlan
partOf0..*Reference(CarePlan)Part of referenced CarePlan
status1..1codedraft | active | on-hold | revoked | completed | entered-in-error | unknown
intent1..1codeproposal | plan | order | option
category0..*CodeableConceptType of plan
title0..1stringHuman-friendly name for the care plan
description0..1stringSummary of nature of plan
subject1..1Reference(Patient | Group)Who the care plan is for
encounter0..1Reference(Encounter)Encounter created as part of
period0..1PeriodTime period plan covers
created0..1dateTimeDate record was first recorded
author0..1Reference(Patient | Practitioner | PractitionerRole | Device | RelatedPerson | Organization | CareTeam)Who is the designated responsible party
contributor0..*Reference(Patient | Practitioner | PractitionerRole | Device | RelatedPerson | Organization | CareTeam)Who provided the content of the care plan
careTeam0..*Reference(CareTeam)Who's involved in plan?
addresses0..*Reference(Condition)Health issues this plan addresses
supportingInfo0..*Reference(Any)Information considered as part of plan
goal0..*Reference(Goal)Desired outcome of plan
activity0..*BackboneElementAction to occur as part of plan
└─ outcomeCodeableConcept0..*CodeableConceptResults of the activity
└─ outcomeReference0..*Reference(Any)Appointment, Encounter, Procedure, etc.
└─ progress0..*AnnotationComments about the activity status/progress
└─ reference0..1Reference(Appointment | CommunicationRequest | DeviceRequest | MedicationRequest | NutritionOrder | Task | ServiceRequest | VisionPrescription)Activity details defined in specific resource
└─ detail0..1BackboneElementIn-line definition of activity
└───kind0..1codeAppointment | CommunicationRequest | DeviceRequest | MedicationRequest | NutritionOrder | Task | ServiceRequest | VisionPrescription
└───instantiatesCanonical0..*canonical(PlanDefinition | ActivityDefinition | Questionnaire | Measure | OperationDefinition)Instantiates FHIR protocol or definition
└───instantiatesUri0..*uriInstantiates external protocol or definition
└───code0..1CodeableConceptDetail type of activity
└───reasonCode0..*CodeableConceptWhy activity should be done or why activity was prohibited
└───reasonReference0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference)Why activity is needed
└───goal0..*Reference(Goal)Goals this activity relates to
└───status1..1codenot-started | scheduled | in-progress | on-hold | completed | cancelled | stopped | unknown | entered-in-error
└───statusReason0..1CodeableConceptReason for current status
└───doNotPerform0..1booleanIf true, activity is prohibiting action
└───scheduled[x]0..1Timing | Period | stringWhen activity is to occur
└───location0..1Reference(Location)Where it should happen
└───performer0..*Reference(Practitioner | PractitionerRole | Organization | RelatedPerson | Patient | CareTeam | HealthcareService | Device)Who will be responsible?
└───product[x]0..1CodeableConcept | Reference(Medication | Substance)What is to be administered/supplied
└───dailyAmount0..1SimpleQuantityHow to consume/day?
└───quantity0..1SimpleQuantityHow much to administer/supply/consume
└───description0..1stringExtra info describing activity to perform
note0..*AnnotationComments about the plan

Search Parameters

NameTypeDescriptionExpression
datedateTime period plan coversCarePlan.period
identifiertokenExternal Ids for this planCarePlan.identifier
patientreferenceWho the care plan is forCarePlan.subject.where(resolve() is Patient)
activity-codetokenDetail type of activityCarePlan.activity.detail.code
activity-datedateSpecified date occurs within period specified by CarePlan.activity.detail.scheduled[x]CarePlan.activity.detail.scheduled
activity-referencereferenceActivity details defined in specific resourceCarePlan.activity.reference
based-onreferenceFulfills CarePlanCarePlan.basedOn
care-teamreferenceWho's involved in plan?CarePlan.careTeam
categorytokenType of planCarePlan.category
conditionreferenceHealth issues this plan addressesCarePlan.addresses
encounterreferenceEncounter created as part ofCarePlan.encounter
goalreferenceDesired outcome of planCarePlan.goal
instantiates-canonicalreferenceInstantiates FHIR protocol or definitionCarePlan.instantiatesCanonical
instantiates-uriuriInstantiates external protocol or definitionCarePlan.instantiatesUri
intenttokenproposal | plan | order | optionCarePlan.intent
part-ofreferencePart of referenced CarePlanCarePlan.partOf
performerreferenceMatches if the practitioner is listed as a performer in any of the "simple" activitiesCarePlan.activity.detail.performer
replacesreferenceCarePlan replaced by this CarePlanCarePlan.replaces
statustokendraft | active | on-hold | revoked | completed | entered-in-error | unknownCarePlan.status
subjectreferenceWho the care plan is forCarePlan.subject

Scope and Usage

CarePlan is one of the request resources in the FHIR workflow specification.

Overview

Care Plans are used across healthcare with varying levels of complexity:

  • Simple Plans: Basic tracking (e.g., tetanus immunization schedules)
  • Complex Plans: Detailed treatment protocols (e.g., oncology plans including diet, chemotherapy, radiation, lab work, and counseling)
  • Special Uses:
    • Veterinary care for herds/groups of animals
    • Public health campaigns (education, immunization)

Implementation Approach

This resource uses an intermediate complexity approach:

  • Captures basic details about participants and intended actions
  • Does not handle complex dependencies or timing relationships
  • Supports additional complexity through extensions when needed

Common Use Cases

  1. Multi-disciplinary Care

    • Cross-organizational coordination
    • Example: Oncology plans involving multiple specialists
  2. Condition Management

    • Nutritional plans post surgery
    • Neurological plans post injury
    • Pre-natal and post-partum care
    • Grief management
  3. Protocol-Based Care

    • Decision support generated plans
    • Clinical practice guidelines
    • Examples: Stroke care, diabetes management, falls prevention
  4. Patient-Centered Plans

    • Self-maintained by patients/caregivers
    • Focus on personal goals and actions

Boundaries and Relationships

Implementation Details

  1. Activity Definition

    • Can be defined inline using activity.detail
    • Can reference external "request" resources
    • Activities can exist independently without a CarePlan
  2. Relationship to Conditions

    • May be condition-specific
    • Can be condition-independent (focused on care type or provider)

Important Distinctions

  1. Scope Limitations

    • Represents specific patient/group instances
    • Not for defining generic protocols
    • Protocols and order sets use PlanDefinition resource
  2. Related Resources

    • ImmunizationRecommendation preferred for immunization-specific plans
    • PlanDefinition used for generic protocols

Referenced Elements

This resource is referenced by:

On this page