Resources: DSTU2: CarePlan
The CarePlan resource is used to retrieve a specific patient's care plans (DAF CarePlan). This can include the patient's care team and the patient's assessment and plan for treatment. The logical ID of the patient is passed as part of the URL. The logical ID is found as the result of a patient search.
To retrieve a patient's assessment and plan for treatment, use the following syntax:
GET {FHIR URL}/Patient/{ID}/CarePlan?category=assess-plan
To retrieve a patient's care team, use the following syntax:
GET {FHIR URL}/Patient/{ID}/CarePlan?category=careteam
| Name | Required? | Type | Description |
|---|---|---|---|
| ID | Yes | URL | The patient's logical ID. This is retrieved using the search function. |
| date | No | string | A string representing a date to include in the search. See below for more information. |
| Name | Type | Cardinality | Description |
|---|---|---|---|
| identifier | 0..* | External IDs for this plan. This records identifiers associated with this care team that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. This is a business identifier, not a resource identifier. | |
| subject | Reference (Patient, Group) | 0..1 | Who the care team is for. Identifies the patient whose intended care is handled by the team. |
| status | code | 1..1 | Indicates whether the plan is currently being acted upon, represents future intentions, or is now a historical record. It also allows clinicians to determine whether the plan is actionable or not. Statuses returned include: Proposed, Draft (Pending), Active, Completed, and Cancelled. For more information on this value set, see: here. |
| category | CodeableConcept | 0..* | Options could include Problem, Health Concern, Care Team, or Assessment and Plan of Treatment. A type of plan which utilizes "Assessment and Plan of Treatment" the clinical conclusions and assumptions that guide the patient's treatment and the clinical activities formulated for a patient. Where the category is just "Assessment and Plan" only the category "Assessment and Plan" will be returned. Values come from Argonaut Extension Codes for Care Plan here. |
| participant | 0..* | Members of the team. Identifies all people and organizations who are expected to be involved in the care team. Allows representation of care teams, and helps scope the care plan. In some cases, this may be a determiner of access permissions. | |
| -- participant.role | CodeableConcept | 0..1 | Indicates the specific responsibility of an individual within the care team, such as primary physician, team coordinator, or caregiver. Roles may be inferred by type of practitioner. These are relationships that hold only within the context of the care team. General relationships should be handled as properties of the patient resource directly. For more information on this value set, see here. |
| -- participant.member | Reference (Practitioner, RelatedPerson, Patient, Organization) | 0..1 | The specific person or organization who is participating in or expected to participate in the care team. The patient only needs to be listed if they have a role other than subject of care. Member is optional because some participants may be known only by their role, particularly in draft plans. |
The Argonaut Assessment and Plan of Treatment IG provides the API documentation for searching for and fetching patient assessment and plan of treatment data using the CarePlan resource. The search supports the narrative elements of the Assessment and Plan section which is the minimal necessary criteria to support the 2015 Edition ONC Certification criterion Data Category Request 170.315(g)(8).
| Name | Type | Cardinality | Description |
|---|---|---|---|
| identifier | 0..* | External IDs for this plan. This is a business identifier, not a resource identifier. This records identifiers associated with this care plan that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. For example, in CDA documents or in written/printed documentation. | |
| subject | Reference (Patient, Group) | 0..1 | Who the care plan is for. This identifies the patient or group whose intended care is described by the plan. |
| status | code | 1..1 | Indicates hether the plan is currently acted upon, represents future intentions, or is now a historical record. It allows clinicians to determine whether the plan is actionable or not. Conformance is required, and the valid statuses include: Proposed, Pending, Active, Completed, and Cancelled. For more information on this value set, see: here. |
| category | CodeableConcept | 0..* | Identifies what kind of plan this is to support differentiation between multiple co-existing plans. For example, "Home health", "psychiatric", "asthma", "disease management", "wellness plan", and so forth. There may be multiple axis of categorization, and one plan may serve multiple purposes. In some cases, this may be redundant with references to CarePlan.concern. This value set contains 21 concepts. For more information on this value set, see: here. |
| narrative summary | string | 0..1 | Text or HTML description of the assessment and plan. CarePlan.text.status is either Generated or Additional. This tool uses Generated. For more information on this value set, see: here, which defines the following codes: Generated, Extensions, Additional, and Empty. |