FHIR Release 3 (STU)

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 of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

Patient Care Work GroupMaturity Level: 2 Trial UseCompartments: Patient, Practitioner, RelatedPerson

Detailed Descriptions for the elements in the CareTeam resource.

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.

Control1..1
CareTeam.identifier
Definition

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.

NoteThis is a business identifer, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
Summarytrue
CareTeam.status
Definition

Indicates the current state of the care team.

Control0..1
Terminology BindingCareTeamStatus (Required)
Typecode
Is Modifiertrue
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
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.

Control0..*
Terminology BindingCareTeamCategory (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
Definition

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

Control0..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
Definition

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

Control0..1
TypeReference(Patient | Group)
Requirements

Allows the team to care for a group (e.g. marriage) therapy.

Alternate Namespatient
Summarytrue
CareTeam.context
Definition

The encounter or episode of care that establishes the context for this care team.

Control0..1
TypeReference(Encounter | EpisodeOfCare)
Alternate Namesencounter
Summarytrue
CareTeam.period
Definition

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

Control0..1
TypePeriod
Requirements

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

Summarytrue
CareTeam.participant
Definition

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

Control0..*
InvariantsDefined on this element
ctm-1: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner (expression : onBehalfOf.exists() implies (member.resolve() is Practitioner), xpath: contains(f:member/f:reference/@value, '/Practitioner/') or not(exists(f:onBehalfOf)))
Affect this element
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.

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

CareTeam.participant.member
Definition

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

Control0..1
TypeReference(Practitioner | 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
Definition

The organization of the practitioner.

Control0..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.period
Definition

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

Control0..1
TypePeriod
CareTeam.reasonCode
Definition

Describes why the care team exists.

Control0..*
Terminology BindingSNOMED CT Clinical Findings (Example)
TypeCodeableConcept
CareTeam.reasonReference
Definition

Condition(s) that this care team addresses.

Control0..*
TypeReference(Condition)
CareTeam.managingOrganization
Definition

The organization responsible for the care team.

Control0..*
TypeReference(Organization)
Requirements

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

Summarytrue
CareTeam.note
Definition

Comments made about the CareTeam.

Control0..*
TypeAnnotation