This page is part of the FHIR Specification (v4.4.0: R5 Preview #2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3
Patient Care Work Group | Maturity Level: 2 | Trial Use | Security Category: Patient | Compartments: Patient, Practitioner, RelatedPerson |
Detailed Descriptions for the elements in the CareTeam resource.
CareTeam | |||||||||||||
Element Id | CareTeam | ||||||||||||
Definition | The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care. | ||||||||||||
Cardinality | 0..* | ||||||||||||
Type | DomainResource | ||||||||||||
CareTeam.identifier | |||||||||||||
Element Id | CareTeam.identifier | ||||||||||||
Definition | Business identifiers assigned to this care team by the performer or other systems which remain constant as the resource is updated and propagates from server to server. | ||||||||||||
Note | This is a business identifier, not a resource identifier (see discussion) | ||||||||||||
Cardinality | 0..* | ||||||||||||
Type | Identifier | ||||||||||||
Requirements | Allows identification of the care team as it is known by various participating systems and in a way that remains consistent across servers. | ||||||||||||
Summary | true | ||||||||||||
Comments | This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number. | ||||||||||||
CareTeam.status | |||||||||||||
Element Id | CareTeam.status | ||||||||||||
Definition | Indicates the current state of the care team. | ||||||||||||
Cardinality | 0..1 | ||||||||||||
Terminology Binding | CareTeamStatus (Required) | ||||||||||||
Type | code | ||||||||||||
Is Modifier | true (Reason: This element is labelled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid) | ||||||||||||
Summary | true | ||||||||||||
Comments | This element is labeled as a modifier because the status contains the code entered-in-error that marks the care team as not currently valid. | ||||||||||||
CareTeam.category | |||||||||||||
Element Id | CareTeam.category | ||||||||||||
Definition | Identifies what kind of team. This is to support differentiation between multiple co-existing teams, such as care plan team, episode of care team, longitudinal care team. | ||||||||||||
Cardinality | 0..* | ||||||||||||
Terminology Binding | Care Team category (Example) | ||||||||||||
Type | CodeableConcept | ||||||||||||
Requirements | Used for filtering what teams(s) are retrieved and displayed to different types of users. | ||||||||||||
Summary | true | ||||||||||||
Comments | There may be multiple axis of categorization and one team may serve multiple purposes. | ||||||||||||
CareTeam.name | |||||||||||||
Element Id | CareTeam.name | ||||||||||||
Definition | A label for human use intended to distinguish like teams. E.g. the "red" vs. "green" trauma teams. | ||||||||||||
Cardinality | 0..1 | ||||||||||||
Type | string | ||||||||||||
Summary | true | ||||||||||||
Comments | The meaning/purpose of the team is conveyed in CareTeam.category. This element may also convey semantics of the team (e.g. "Red trauma team"), but its primary purpose is to distinguish between identical teams in a human-friendly way. ("Team 18735" isn't as friendly.). | ||||||||||||
CareTeam.subject | |||||||||||||
Element Id | CareTeam.subject | ||||||||||||
Definition | Identifies the patient or group whose intended care is handled by the team. | ||||||||||||
Cardinality | 0..1 | ||||||||||||
Type | Reference(Patient | Group) | ||||||||||||
Patterns | Reference(Patient,Group): Common patterns = Participant | ||||||||||||
Requirements | Allows the team to care for a group (e.g. marriage) therapy. Allows for an organization to designate a team such as the PICC line team. | ||||||||||||
Alternate Names | patient | ||||||||||||
Summary | true | ||||||||||||
CareTeam.period | |||||||||||||
Element Id | CareTeam.period | ||||||||||||
Definition | Indicates when the team did (or is intended to) come into effect and end. | ||||||||||||
Cardinality | 0..1 | ||||||||||||
Type | Period | ||||||||||||
Requirements | Allows tracking what team(s) are in effect at a particular time. | ||||||||||||
Summary | true | ||||||||||||
CareTeam.participant | |||||||||||||
Element Id | CareTeam.participant | ||||||||||||
Definition | Identifies all people and organizations who are expected to be involved in the care team. | ||||||||||||
Cardinality | 0..* | ||||||||||||
Invariants |
| ||||||||||||
CareTeam.participant.role | |||||||||||||
Element Id | CareTeam.participant.role | ||||||||||||
Definition | Indicates specific responsibility of an individual within the care team, such as "Primary care physician", "Trained social worker counselor", "Caregiver", etc. | ||||||||||||
Cardinality | 0..1 | ||||||||||||
Terminology Binding | Participant Roles (Example) | ||||||||||||
Type | CodeableConcept | ||||||||||||
Summary | true | ||||||||||||
Comments | Roles may sometimes 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. If a participant has multiple roles within the team, then there should be multiple participants. | ||||||||||||
CareTeam.participant.member | |||||||||||||
Element Id | CareTeam.participant.member | ||||||||||||
Definition | The specific person or organization who is participating/expected to participate in the care team. | ||||||||||||
Cardinality | 0..1 | ||||||||||||
Type | Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam) | ||||||||||||
Patterns | Reference(Practitioner,PractitionerRole,RelatedPerson,Patient,Organization,CareTeam): Common patterns = Participant | ||||||||||||
Summary | true | ||||||||||||
Comments | 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. | ||||||||||||
CareTeam.participant.onBehalfOf | |||||||||||||
Element Id | CareTeam.participant.onBehalfOf | ||||||||||||
Definition | The organization of the practitioner. | ||||||||||||
Cardinality | 0..1 | ||||||||||||
Type | Reference(Organization) | ||||||||||||
Requirements | Practitioners can be associated with multiple organizations. This element indicates which organization they were acting on behalf of. | ||||||||||||
Summary | true | ||||||||||||
CareTeam.participant.coverage[x] | |||||||||||||
Element Id | CareTeam.participant.coverage[x] | ||||||||||||
Definition | When the member is generally available within this care team. | ||||||||||||
Cardinality | 0..1 | ||||||||||||
Type | Period|Timing | ||||||||||||
[x] Note | See Choice of Data Types for further information about how to use [x] | ||||||||||||
Requirements | To manage members who share the same role, but with different timing. For example, two physical therapists where one is available Monday through Friday whereas the other is available on the weekend. | ||||||||||||
Comments | This is populated while creating / managing the CareTeam to ensure there is coverage when servicing CarePlan activities from the Schedule. | ||||||||||||
CareTeam.reason | |||||||||||||
Element Id | CareTeam.reason | ||||||||||||
Definition | Describes why the care team exists. | ||||||||||||
Cardinality | 0..* | ||||||||||||
Terminology Binding | SNOMED CT Clinical Findings (Example) | ||||||||||||
Type | CodeableReference(Condition) | ||||||||||||
CareTeam.managingOrganization | |||||||||||||
Element Id | CareTeam.managingOrganization | ||||||||||||
Definition | The organization responsible for the care team. | ||||||||||||
Cardinality | 0..* | ||||||||||||
Type | Reference(Organization) | ||||||||||||
Requirements | Allows for multiple organizations to collaboratively manage cross-organizational, longitudinal care plan. | ||||||||||||
Summary | true | ||||||||||||
CareTeam.telecom | |||||||||||||
Element Id | CareTeam.telecom | ||||||||||||
Definition | A central contact detail for the care team (that applies to all members). | ||||||||||||
Cardinality | 0..* | ||||||||||||
Type | ContactPoint | ||||||||||||
Comments | The ContactPoint.use code of home is not appropriate to use. These contacts are not the contact details of individual care team members. | ||||||||||||
CareTeam.note | |||||||||||||
Element Id | CareTeam.note | ||||||||||||
Definition | Comments made about the CareTeam. | ||||||||||||
Cardinality | 0..* | ||||||||||||
Type | Annotation |