CarePlan

The FHIR R4 CarePlan resource represents a set of planned activities, interventions, and goals for a patient or group of patients. Care plans describe what care is intended, who is responsible, and when activities should occur, supporting coordinated and longitudinal care delivery.

Health Gorilla exposes CarePlan as part of its FHIR R4 API to support access to patient-centered care planning information.

Use Cases

  • Retrieving a patient’s active or historical care plans
  • Reviewing planned interventions and goals across care teams
  • Supporting care coordination, case management, and longitudinal care workflows
  • Displaying structured care plans within patient charts or care-management tools
  • Filtering care plans by intent, status, or clinical category

Scope and Behavior

This documentation describes the FHIR R4 API interface for CarePlan. Health Gorilla’s platform may use additional internal services and data standards to acquire, normalize, and route clinical information. Only the FHIR R4–exposed behavior is documented here.

Health Gorilla supports a subset of the HL7 FHIR R4 CarePlan resource. Not all optional elements defined in the HL7 specification may be stored, indexed, or returned. Unsupported or unrecognized elements may be ignored or normalized during processing.

In Health Gorilla, CarePlan is most commonly accessed as part of patient record retrieval workflows, where care planning data may be aggregated from connected clinical sources and normalized for longitudinal review. This resource supports care coordination, case management, and interdisciplinary collaboration by exposing structured goals, planned activities, and responsible participants alongside other patient clinical data.

Authentication

All requests to the FHIR R4 API require OAuth 2.0 authentication using a bearer token. Unauthorized requests return a 401 Unauthorized response.

Required Scopes

  • careplan.read for GET
  • careplan.write for POST, PUT, and DELETE

For details on authentication and token acquisition, see OAuth 2.0 Authentication.

Search Behavior

  • Searches are scoped to the authenticated tenant.
  • The patient parameter is required for patient-scoped searches and is recommended for most search use cases.
  • Results are returned as a FHIR Bundle.
  • Pagination may be applied. Use standard FHIR pagination links (Bundle.link) to retrieve additional result pages.

Note: The parameters listed below are not exhaustive and reflect commonly used fields in typical Health Gorilla workflows. Supported parameters and behavior may vary by configuration.

Frequently Used Search Parameters

ParameterDescriptionExample ValuesFHIR Data Type
patientFilters by patientPatient/{id}Reference
statusFilters by care plan statusdraft, active, completedtoken
intentFilters by care plan intentplan, order, proposaltoken
categoryFilters by care plan typeassess-plan, disease-managementtoken
dateFilters by plan periodge2023-01-01, le2024-12-31date
authorFilters by plan authorPractitioner/{id}Reference

Commonly Returned Resource Attributes

The following attributes are commonly present in CarePlan resources returned by Health Gorilla.

AttributeDescriptionExample ValuesFHIR Data Type
subjectPatient or group the care plan applies toPatient/{id}Reference(Patient)
statusCurrent state of the care plandraft, active, completedcode
intentPurpose or level of authorityplan, order, proposalcode
categoryType or clinical focus of the care planassess-planCodeableConcept[]
titleHuman-readable titleFree textstring
descriptionSummary description of the care planFree textstring
periodTime period the care plan coversstart, end datesPeriod
authorIndividual or organization who created the care planPractitioner/{id}Reference(Practitioner)
careTeamParticipants involved in the planCareTeam/{id}Reference[]
goalGoals addressed by the care planGoal/{id}Reference[]
activityPlanned actions or interventionsStructured activity entriesBackboneElement[]

Notifications

The FHIR R4 API does not provide direct resource-change subscriptions for CarePlan. Changes to care planning information may surface through broader notification workflows, depending on enabled Health Gorilla products and configuration.

Error Handling

All CarePlan operations use standard Health Gorilla error handling and return a FHIR OperationOutcome resource for structured error details. For more information, go to Error Handling.

Additional Resources

HL7 FHIR CarePlan