This
page
is
part
of
the
FHIR
Specification
(v3.0.2:
STU
3).
The
current
version
which
supercedes
this
version
is
5.0.0
.
For
a
full
list
Continuous
Integration
Build
of
available
versions,
see
FHIR
(will
be
incorrect/inconsistent
at
times).
See
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
R3
Responsible
Owner:
Patient
Care
Work
Group
|
Normative
|
|
Compartments : Group , Patient , Practitioner , RelatedPerson |
Detailed Descriptions for the elements in the CareTeam resource.
| CareTeam | |||||||||
|
| CareTeam | ||||||||
| Definition |
The
Care
Team
includes
all
the
|
||||||||
| Short Display | Planned participants in the coordination and delivery of care | ||||||||
| Cardinality | 0..* | ||||||||
|
| DomainResource | ||||||||
| Summary | false | ||||||||
| CareTeam.identifier | |||||||||
|
| CareTeam.identifier | ||||||||
| Definition |
|
||||||||
|
| External Ids for this team | ||||||||
| Note |
This
is
a
business
|
||||||||
|
|
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 | |||||||||
|
| CareTeam.status | ||||||||
| Definition |
Indicates the current state of the care team. |
||||||||
| Short Display | proposed | active | suspended | inactive | entered-in-error | ||||||||
| Cardinality | 0..1 | ||||||||
| Terminology Binding |
|
||||||||
| 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 | |||||||||
|
| 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. |
||||||||
| Short Display | Type of team | ||||||||
| Cardinality | 0..* | ||||||||
| Terminology Binding |
|
||||||||
| 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 | |||||||||
|
| CareTeam.name | ||||||||
| Definition |
A
label
for
human
use
intended
to
distinguish
like
teams.
E.g.
the
|
||||||||
| Short Display | Name of the team, such as crisis assessment team | ||||||||
| 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.
|
||||||||
| CareTeam.subject | |||||||||
|
|
CareTeam.subject | ||||||||
| Definition |
Identifies the patient or group whose intended care is handled by the team. |
||||||||
| Short Display | Who care team is for | ||||||||
|
|
0..1 | ||||||||
| Type | Reference ( Patient | Group ) | ||||||||
| 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 | ||||||||
|
|
|
||||||||
|
|
|||||||||
|
|
|
||||||||
| Definition |
Indicates when the team did (or is intended to) come into effect and end. |
||||||||
| Short Display | Time period team covers | ||||||||
| Cardinality | 0..1 | ||||||||
| Type | Period | ||||||||
| Requirements |
Allows tracking what team(s) are in effect at a particular time. |
||||||||
| Summary | true | ||||||||
| CareTeam.participant | |||||||||
|
| CareTeam.participant | ||||||||
| Definition |
Identifies all people and organizations who are expected to be involved in the care team. |
||||||||
| Short Display | Members of the team | ||||||||
|
|
0..* | ||||||||
|
|
false | ||||||||
| Constraints |
|
||||||||
| CareTeam.participant.role | |||||||||
|
|
CareTeam.participant.role | ||||||||
| Definition |
Indicates
specific
responsibility
of
an
individual
within
the
care
team,
such
as
|
||||||||
| Short Display | Type of involvement | ||||||||
|
|
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. |
||||||||
| Constraints |
| ||||||||
| CareTeam.participant.member | |||||||||
|
| CareTeam.participant.member | ||||||||
| Definition |
The specific person or organization who is participating/expected to participate in the care team. |
||||||||
| Short Display | Who is involved | ||||||||
|
|
0..1 | ||||||||
| Type | Reference ( Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam | Group | HealthcareService ) | ||||||||
| Summary | true | ||||||||
| Comments |
Patient
only
needs
to
be
listed
if
they
have
a
role
other
than
Member is optional because some participants may be known only by their role, particularly in draft plans. Using Group is only allowed when the group represents a family or a household and should not represent groups of Practitioners. |
||||||||
| Constraints |
| ||||||||
| CareTeam.participant.onBehalfOf | |||||||||
|
| CareTeam.participant.onBehalfOf | ||||||||
| Definition |
|
||||||||
| Short Display | Entity that the participant is acting as a proxy of, or an agent of, or in the interest of, or as a representative of | ||||||||
| Cardinality | 0..1 | ||||||||
| Type | Reference ( Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam | Group | HealthcareService ) | ||||||||
| Requirements |
|
||||||||
| Summary | true | ||||||||
| Comments |
Using Group is only allowed when the group represents a family or a household and should not represent groups of Practitioners. | ||||||||
|
|
|||||||||
|
|
CareTeam.participant.effective[x] | ||||||||
| Definition |
|
||||||||
| Short Display | When the member is generally available within this care team | ||||||||
|
|
0..1 | ||||||||
| Type | Period | Timing | ||||||||
| [x] Note | See Choice of Datatypes 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. | ||||||||
| Summary | false | ||||||||
| Comments | This is populated while creating / managing the CareTeam to ensure there is coverage when servicing CarePlan activities from the Schedule. | ||||||||
|
|
|||||||||
|
| CareTeam.participant.supportingInfo | ||||||||
| Definition |
|
||||||||
| Short Display | Basis for the member's participation | ||||||||
| Cardinality | 0..* | ||||||||
|
|
|
||||||||
|
|
true | ||||||||
| Comments |
Enables care providers a more efficient path to review the participation, if necessary. |
||||||||
|
|
|||||||||
|
|
CareTeam.reason | ||||||||
| Definition |
|
||||||||
| Short Display | Why the care team exists | ||||||||
| Cardinality | 0..* | ||||||||
| Terminology Binding | SNOMED CT Clinical Findings ( Example ) | ||||||||
| Type |
|
||||||||
| Summary | false | ||||||||
| CareTeam.managingOrganization | |||||||||
|
| CareTeam.managingOrganization | ||||||||
| Definition |
The organization responsible for the care team. |
||||||||
| Short Display | Organization responsible for the care team | ||||||||
|
|
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). | ||||||||
| Short Display | A contact detail for the care team (that applies to all members) | ||||||||
| Cardinality | 0..* | ||||||||
| Type | ContactPoint | ||||||||
| Summary | false | ||||||||
| 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 | |||||||||
|
|
CareTeam.note | ||||||||
| Definition |
Comments made about the CareTeam. |
||||||||
| Short Display | Comments made about the CareTeam | ||||||||
| Cardinality | 0..* | ||||||||
| Type | Annotation | ||||||||
| Summary | false | ||||||||