CarePlan REST Endpoints
Description
This topic describes information for the CarePlan resource.
Overview
Note:
The FHIR API endpoints described below are currently pending production deployment for electronic health record (EHR) environments. Developers are welcome and encouraged to develop against the specifications in anticipation of production availability, which will be announced at a later date.The CarePlan resource describes how one or more practitioners plan to deliver care to a specific patient. Care plans are used in a variety of areas and scopes ranging from encounter-specific or visit-specific to cross-visits. Care plans are used to group activities, goals, and practitioners to create context. Care plans are intended to be specific to the patient. A planned activity can stand alone without a care plan such as a scheduled appointment.
Profile Support
This resource supports the US Core CarePlan Profile from the HL7 FHIR US Core Implementation Guide STU 6.1.0.
Note:
The examples provided here are nonnormative and replaying them in the public sandbox is not guaranteed to yield the results shown on the site.Returned Fields
Terminology Bindings
| Element | Description | Details |
|---|---|---|
CarePlan.status |
Whether the plan is currently being acted upon, represents future intentions, or is now a historical record. | System |
CarePlan.intent |
Codes indicating the degree of authority or intentionality associated with a care plan. Currently, plan is the only supported status binding. |
System |
CarePlan.category |
The type of plan. This element supports differentiation between multiple coexisting plans. Currently, assess-plan is the only supported category binding. |
System |
CarePlan
The operations from the CarePlan category.
- Get a care plan by ID
- Method: getPath:
/CarePlan/{id} - Get a list of care plans
- Method: getPath:
/CarePlan