Care team for patient
Retrieving a patient’s care team(s)
The logical ID of the patient to retrieve is passed as part of the URL. The logical ID is found as the result of a search.
GET https://tw171.open.allscripts.com/FHIR/Patient/id/CarePlan?category=careteam
GET https://tw171.open.allscripts.com/FHIR/Patient/id/CarePlan?category=careteam&date=eq2016-01-01
| Name | Required? | Type | Description |
|---|---|---|---|
| id | yes | URL | The logical ID of the patient. 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. |
A DAF care plan is returned. Since we are using the CarePlan Resource for identifying the care team members, constraints on that resource are defined for this purpose only. For example, creating a care team profile using care plan.
| 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: http://hl7.org/fhir/ValueSet/care-plan-status. |
| 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 http://argonautwiki.hl7.org/index.php?title=Argonaut_Extension_Codes. |
| 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 http://hl7.org/fhir/ValueSet/participant-role. |
| – 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. |
Searching by date
Dates are passed as query parameters on the URL. Since the URL parameters cannot handle comparators (e.g. >, <=), these are passed in as part of the date.
date=eq2016-01-01
date=gt2016-01-01
The following comparators are supported:
| Comparator | Description |
|---|---|
| eq | equal |
| gt | greater than |
| ge | greater than or equal |
| lt | less than |
| le | less than or equal |
To search for a date range, pass in the date twice:
e.g. date=ge2010-01-01&date=le2010-12-31
This search would include every day in the year 2010.