FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon

Patient Care icon Work GroupMaturity Level: 2 Trial UseSecurity Category: Patient Compartments: Patient, Practitioner, RelatedPerson

Detailed Descriptions for the elements in the CareTeam resource.

CareTeam
Element IdCareTeam
Definition

The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care.

Short DisplayPlanned participants in the coordination and delivery of care
Cardinality0..*
TypeDomainResource
Summaryfalse
CareTeam.identifier
Element IdCareTeam.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.

Short DisplayExternal Ids for this team
NoteThis is a business identifier, not a resource identifier (see discussion)
Cardinality0..*
TypeIdentifier
Requirements

Allows identification of the care team as it is known by various participating systems and in a way that remains consistent across servers.

Summarytrue
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 IdCareTeam.status
Definition

Indicates the current state of the care team.

Short Displayproposed | active | suspended | inactive | entered-in-error
Cardinality0..1
Terminology BindingCareTeamStatus (Required)
Typecode
Is Modifiertrue (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)
Summarytrue
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 IdCareTeam.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 DisplayType of team
Cardinality0..*
Terminology BindingCare Team category (Example)
TypeCodeableConcept
Requirements

Used for filtering what teams(s) are retrieved and displayed to different types of users.

Summarytrue
Comments

There may be multiple axis of categorization and one team may serve multiple purposes.

CareTeam.name
Element IdCareTeam.name
Definition

A label for human use intended to distinguish like teams. E.g. the "red" vs. "green" trauma teams.

Short DisplayName of the team, such as crisis assessment team
Cardinality0..1
Typestring
Summarytrue
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 IdCareTeam.subject
Definition

Identifies the patient or group whose intended care is handled by the team.

Short DisplayWho care team is for
Cardinality0..1
TypeReference(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 Namespatient
Summarytrue
CareTeam.period
Element IdCareTeam.period
Definition

Indicates when the team did (or is intended to) come into effect and end.

Short DisplayTime period team covers
Cardinality0..1
TypePeriod
Requirements

Allows tracking what team(s) are in effect at a particular time.

Summarytrue
CareTeam.participant
Element IdCareTeam.participant
Definition

Identifies all people and organizations who are expected to be involved in the care team.

Short DisplayMembers of the team
Cardinality0..*
Summaryfalse
Invariants
Defined on this element
ctm-1Rule CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a PractitioneronBehalfOf.exists() implies (member.resolve() is Practitioner)
ctm-2Warning CareTeam.participant.role or CareTeam.participant.member existsrole.exists() or member.exists()
Affect this element
CareTeam.participant.role
Element IdCareTeam.participant.role
Definition

Indicates specific responsibility of an individual within the care team, such as "Primary care physician", "Trained social worker counselor", "Caregiver", etc.

Short DisplayType of involvement
Cardinality0..1
Terminology BindingParticipant Roles (Example)
TypeCodeableConcept
Summarytrue
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 IdCareTeam.participant.member
Definition

The specific person or organization who is participating/expected to participate in the care team.

Short DisplayWho is involved
Cardinality0..1
TypeReference(Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam)
Summarytrue
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 IdCareTeam.participant.onBehalfOf
Definition

The organization of the practitioner.

Short DisplayOrganization of the practitioner
Cardinality0..1
TypeReference(Organization)
Requirements

Practitioners can be associated with multiple organizations. This element indicates which organization they were acting on behalf of.

Summarytrue
CareTeam.participant.coverage[x]
Element IdCareTeam.participant.coverage[x]
Definition

When the member is generally available within this care team.

Short DisplayWhen the member is generally available within this care team
Cardinality0..1
TypePeriod|Timing
[x] NoteSee 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.

Summaryfalse
Comments

This is populated while creating / managing the CareTeam to ensure there is coverage when servicing CarePlan activities from the Schedule.

CareTeam.reason
Element IdCareTeam.reason
Definition

Describes why the care team exists.

Short DisplayWhy the care team exists
Cardinality0..*
Terminology BindingSNOMED CT Clinical Findings (Example)
TypeCodeableReference(Condition)
Summaryfalse
CareTeam.managingOrganization
Element IdCareTeam.managingOrganization
Definition

The organization responsible for the care team.

Short DisplayOrganization responsible for the care team
Cardinality0..*
TypeReference(Organization)
Requirements

Allows for multiple organizations to collaboratively manage cross-organizational, longitudinal care plan.

Summarytrue
CareTeam.telecom
Element IdCareTeam.telecom
Definition

A central contact detail for the care team (that applies to all members).

Short DisplayA contact detail for the care team (that applies to all members)
Cardinality0..*
TypeContactPoint
Summaryfalse
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 IdCareTeam.note
Definition

Comments made about the CareTeam.

Short DisplayComments made about the CareTeam
Cardinality0..*
TypeAnnotation
Summaryfalse