Release 4B 5

This page is part of the FHIR Specification (v4.3.0: R4B (v5.0.0: R5 - STU ). The This is the current published version which supercedes in it's permanent home (it will always be available at this version is 5.0.0 . URL). For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R5 R4B R4 R3

Patient Care icon Work Group Maturity Level : 2   Trial Use Security Category : Patient Compartments : Encounter , Patient , Practitioner , RelatedPerson

Detailed Descriptions for the elements in the CareTeam resource.

CareTeam.encounter Element Id CareTeam.encounter CareTeam.participant.period Type CodeableConcept
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 for a patient. care.

Short Display Planned participants in the coordination and delivery of care
Cardinality 0..*
Type DomainResource
Summary false
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.

Short Display External Ids for this team
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.

Short Display proposed | active | suspended | inactive | entered-in-error
Cardinality 0..1
Terminology Binding CareTeamStatus Care Team Status ( 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.

Short Display Type of 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.

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. "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.

Short Display Who care team is for
Cardinality 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 Comments

The Encounter during which this CareTeam was created or Use Group for care provision to which the creation all members of this record is tightly associated. Cardinality 0..1 Type Reference ( Encounter ) Summary true Comments This will typically be the encounter the event occurred within, but some activities may be initiated prior group (e.g. group therapy). Use Patient for care provision to or after the official completion of an encounter but still be tied to the context of the encounter. individual patient.

CareTeam.period
Element Id CareTeam.period
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
Element Id CareTeam.participant
Definition

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

Short Display Members of the team
Cardinality 0..*
Summary false
Invariants
Defined on this element
ctm-1 Rule CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner onBehalfOf.exists() implies (member.resolve().iif(empty(), true, ofType(Practitioner).exists())) (member.resolve() is Practitioner)
Affect this element ctm-2 Warning CareTeam.participant.role or CareTeam.participant.member exists role.exists() or member.exists()
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.

Short Display Type of involvement
Cardinality 0..* 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.

Invariants
Affect this element
ctm-2 Warning CareTeam.participant.role or CareTeam.participant.member exists role.exists() or member.exists()
CareTeam.participant.member
Element Id CareTeam.participant.member
Definition

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

Short Display Who is involved
Cardinality 0..1
Type Reference ( Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam )
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.

Invariants
Affect this element
ctm-1 Rule CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner onBehalfOf.exists() implies (member.resolve() is Practitioner)
ctm-2 Warning CareTeam.participant.role or CareTeam.participant.member exists role.exists() or member.exists()
CareTeam.participant.onBehalfOf
Element Id CareTeam.participant.onBehalfOf
Definition

The organization of the practitioner.

Short Display 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
Element Id Invariants CareTeam.participant.period Definition Cardinality false
Affect this element Indicates when the specific member or organization did (or is intended to) come into effect and end.
ctm-1 0..1 Type Rule Period CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner Summary onBehalfOf.exists() implies (member.resolve() is Practitioner)
CareTeam.reasonCode CareTeam.participant.coverage[x]
Element Id CareTeam.reasonCode CareTeam.participant.coverage[x]
Definition

Describes why When the member is generally available within this care team exists. team.

Short Display When the member is generally available within this care team
Cardinality 0..* 0..1
Terminology Binding Type SNOMED CT Clinical Findings Period ( Example | 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.reasonReference CareTeam.reason
Element Id CareTeam.reasonReference CareTeam.reason
Definition

Condition(s) that this Describes why the care team addresses. exists.

Short Display Why the care team exists
Cardinality 0..*
Terminology Binding SNOMED CT Clinical Findings ( Example )
Type Reference CodeableReference ( Condition )
Summary false
CareTeam.managingOrganization
Element Id CareTeam.managingOrganization
Definition

The organization responsible for the care team.

Short Display 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).

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
Element Id CareTeam.note
Definition

Comments made about the CareTeam.

Short Display Comments made about the CareTeam
Cardinality 0..*
Type Annotation
Summary false