This page is part of the FHIR Specification (v3.2.0: R4 Ballot 1). 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

9.7 Resource CareTeam - Content

Patient Care

Work Group

Maturity Level: 2

Trial Use

Compartments: Patient, Practitioner, RelatedPerson

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

9.7.1 Scope and Usage

The CareTeam includes all the people, teams, and organizations who plan to participate in the coordination and delivery of care for a single patient or a group (such as a married couple in therapy or a support group). CareTeam can also be organizationally assigned without a subject in context, such as a code blue team or emergency response team. This is not limited to practitioners, but may include other caregivers such as family members, guardians, the patient themself, or others. The Care Team, depending on where used, may include care team members specific to a particular care plan, an episode, an encounter, or may reflect all known team members across these perspectives. An individual's CareTeam can be dynamic over time, such that there can be transience of team members, such as a rehabilitation team.

9.7.2 Boundaries and Relationships

Care Team is distinct from Group. Group is patient-independent and identifies an undifferentiated set of individuals who are intended to be the target of one or more clinical activities (e.g. set of clinical trial participants, set of individuals impacted by or at risk of a public health event, a herd or flock, etc.) The CareTeam resource establishes a set of relationships and roles and is specific to a particular Patient. The actors are the individual members or organized group of individuals. CareTeam can be referenced by EpisodeOfCare, Encounter, or CarePlan to identify the set of individuals (and their respective roles) who are intended to be involved in providing the care defined by those resources.

This resource is referenced by CarePlan, Communication, CommunicationRequest, Consent, DeviceRequest, DiagnosticReport, EpisodeOfCare, Media, MedicationRequest, Observation, ServiceRequest and Task

Structure

Name	Flags	Card.	Type	Description & Constraints
CareTeam	TU		DomainResource	Planned participants in the coordination and delivery of care for a patient or group Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
identifier	Σ	0..*	Identifier	External Ids for this team
status	?!Σ	0..1	code	proposed \| active \| suspended \| inactive \| entered-in-error CareTeamStatus (Required)
category	Σ	0..*	CodeableConcept	Type of team CareTeamCategory (Example)
name	Σ	0..1	string	Name of the team, such as crisis assessment team
subject	Σ	0..1	Reference(Patient \| Group)	Who care team is for
context	Σ	0..1	Reference(Encounter \| EpisodeOfCare)	Encounter or episode associated with CareTeam
period	Σ	0..1	Period	Time period team covers
participant	I	0..*	BackboneElement	Members of the team + CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner
role	Σ	0..1	CodeableConcept	Type of involvement Participant Roles (Example)
member	Σ	0..1	Reference(Practitioner \| RelatedPerson \| Patient \| Organization \| CareTeam)	Who is involved
onBehalfOf	Σ	0..1	Reference(Organization)	Organization of the practitioner
period		0..1	Period	Time period of participant
reasonCode		0..*	CodeableConcept	Why the care team exists SNOMED CT Clinical Findings (Example)
reasonReference		0..*	Reference(Condition)	Why the care team exists
managingOrganization	Σ	0..*	Reference(Organization)	Organization responsible for the care team
telecom		0..*	ContactPoint	A contact detail for the care team (that applies to all members)
note		0..*	Annotation	Comments made about the CareTeam
Documentation for this format

UML Diagram (Legend)

XML Template

<CareTeam xmlns="http://hl7.org/fhir"> 
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier External Ids for this team --></identifier>
 <status value="[code]"/><!-- 0..1 proposed | active | suspended | inactive | entered-in-error -->
 <category><!-- 0..* CodeableConcept Type of team --></category>
 <name value="[string]"/><!-- 0..1 Name of the team, such as crisis assessment team -->
 <subject><!-- 0..1 Reference(Patient|Group) Who care team is for --></subject>
 <context><!-- 0..1 Reference(Encounter|EpisodeOfCare) Encounter or episode associated with CareTeam --></context>
 <period><!-- 0..1 Period Time period team covers --></period>
 <participant>  <!--  0..* Members of the team -->
  <role><!-- 0..1 CodeableConcept Type of involvement --></role>
  <member><!-- 0..1 Reference(Practitioner|RelatedPerson|Patient|Organization|
    CareTeam) Who is involved --></member>
  <onBehalfOf><!-- 0..1 Reference(Organization) Organization of the practitioner --></onBehalfOf>
  <period><!-- 0..1 Period Time period of participant --></period>
 </participant>
 <reasonCode><!-- 0..* CodeableConcept Why the care team exists --></reasonCode>
 <reasonReference><!-- 0..* Reference(Condition) Why the care team exists --></reasonReference>
 <managingOrganization><!-- 0..* Reference(Organization) Organization responsible for the care team --></managingOrganization>
 <telecom><!-- 0..* ContactPoint A contact detail for the care team (that applies to all members) --></telecom>
 <note><!-- 0..* Annotation Comments made about the CareTeam --></note>
</CareTeam>

JSON Template

{
  "resourceType" : "CareTeam",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // External Ids for this team
  "status" : "<code>", // proposed | active | suspended | inactive | entered-in-error
  "category" : [{ CodeableConcept }], // Type of team
  "name" : "<string>", // Name of the team, such as crisis assessment team
  "subject" : { Reference(Patient|Group) }, // Who care team is for
  "context" : { Reference(Encounter|EpisodeOfCare) }, // Encounter or episode associated with CareTeam
  "period" : { Period }, // Time period team covers
  "participant" : [{ // C? Members of the team
    "role" : { CodeableConcept }, // Type of involvement
    "member" : { Reference(Practitioner|RelatedPerson|Patient|Organization|
    CareTeam) }, // Who is involved
    "onBehalfOf" : { Reference(Organization) }, // Organization of the practitioner
    "period" : { Period } // Time period of participant
  }],
  "reasonCode" : [{ CodeableConcept }], // Why the care team exists
  "reasonReference" : [{ Reference(Condition) }], // Why the care team exists
  "managingOrganization" : [{ Reference(Organization) }], // Organization responsible for the care team
  "telecom" : [{ ContactPoint }], // A contact detail for the care team (that applies to all members)
  "note" : [{ Annotation }] // Comments made about the CareTeam
}

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .


[ a fhir:CareTeam;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:CareTeam.identifier [ Identifier ], ... ; # 0..* External Ids for this team
  fhir:CareTeam.status [ code ]; # 0..1 proposed | active | suspended | inactive | entered-in-error
  fhir:CareTeam.category [ CodeableConcept ], ... ; # 0..* Type of team
  fhir:CareTeam.name [ string ]; # 0..1 Name of the team, such as crisis assessment team
  fhir:CareTeam.subject [ Reference(Patient|Group) ]; # 0..1 Who care team is for
  fhir:CareTeam.context [ Reference(Encounter|EpisodeOfCare) ]; # 0..1 Encounter or episode associated with CareTeam
  fhir:CareTeam.period [ Period ]; # 0..1 Time period team covers
  fhir:CareTeam.participant [ # 0..* Members of the team
    fhir:CareTeam.participant.role [ CodeableConcept ]; # 0..1 Type of involvement
    fhir:CareTeam.participant.member [ Reference(Practitioner|RelatedPerson|Patient|Organization|CareTeam) ]; # 0..1 Who is involved
    fhir:CareTeam.participant.onBehalfOf [ Reference(Organization) ]; # 0..1 Organization of the practitioner
    fhir:CareTeam.participant.period [ Period ]; # 0..1 Time period of participant
  ], ...;
  fhir:CareTeam.reasonCode [ CodeableConcept ], ... ; # 0..* Why the care team exists
  fhir:CareTeam.reasonReference [ Reference(Condition) ], ... ; # 0..* Why the care team exists
  fhir:CareTeam.managingOrganization [ Reference(Organization) ], ... ; # 0..* Organization responsible for the care team
  fhir:CareTeam.telecom [ ContactPoint ], ... ; # 0..* A contact detail for the care team (that applies to all members)
  fhir:CareTeam.note [ Annotation ], ... ; # 0..* Comments made about the CareTeam
]

Changes since DSTU2

This resource did not exist in Release 2

This analysis is available as XML or JSON.

Structure

Name	Flags	Card.	Type	Description & Constraints
CareTeam	TU		DomainResource	Planned participants in the coordination and delivery of care for a patient or group Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
identifier	Σ	0..*	Identifier	External Ids for this team
status	?!Σ	0..1	code	proposed \| active \| suspended \| inactive \| entered-in-error CareTeamStatus (Required)
category	Σ	0..*	CodeableConcept	Type of team CareTeamCategory (Example)
name	Σ	0..1	string	Name of the team, such as crisis assessment team
subject	Σ	0..1	Reference(Patient \| Group)	Who care team is for
context	Σ	0..1	Reference(Encounter \| EpisodeOfCare)	Encounter or episode associated with CareTeam
period	Σ	0..1	Period	Time period team covers
participant	I	0..*	BackboneElement	Members of the team + CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner
role	Σ	0..1	CodeableConcept	Type of involvement Participant Roles (Example)
member	Σ	0..1	Reference(Practitioner \| RelatedPerson \| Patient \| Organization \| CareTeam)	Who is involved
onBehalfOf	Σ	0..1	Reference(Organization)	Organization of the practitioner
period		0..1	Period	Time period of participant
reasonCode		0..*	CodeableConcept	Why the care team exists SNOMED CT Clinical Findings (Example)
reasonReference		0..*	Reference(Condition)	Why the care team exists
managingOrganization	Σ	0..*	Reference(Organization)	Organization responsible for the care team
telecom		0..*	ContactPoint	A contact detail for the care team (that applies to all members)
note		0..*	Annotation	Comments made about the CareTeam
Documentation for this format

UML Diagram (Legend)

XML Template

<CareTeam xmlns="http://hl7.org/fhir"> 
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier External Ids for this team --></identifier>
 <status value="[code]"/><!-- 0..1 proposed | active | suspended | inactive | entered-in-error -->
 <category><!-- 0..* CodeableConcept Type of team --></category>
 <name value="[string]"/><!-- 0..1 Name of the team, such as crisis assessment team -->
 <subject><!-- 0..1 Reference(Patient|Group) Who care team is for --></subject>
 <context><!-- 0..1 Reference(Encounter|EpisodeOfCare) Encounter or episode associated with CareTeam --></context>
 <period><!-- 0..1 Period Time period team covers --></period>
 <participant>  <!--  0..* Members of the team -->
  <role><!-- 0..1 CodeableConcept Type of involvement --></role>
  <member><!-- 0..1 Reference(Practitioner|RelatedPerson|Patient|Organization|
    CareTeam) Who is involved --></member>
  <onBehalfOf><!-- 0..1 Reference(Organization) Organization of the practitioner --></onBehalfOf>
  <period><!-- 0..1 Period Time period of participant --></period>
 </participant>
 <reasonCode><!-- 0..* CodeableConcept Why the care team exists --></reasonCode>
 <reasonReference><!-- 0..* Reference(Condition) Why the care team exists --></reasonReference>
 <managingOrganization><!-- 0..* Reference(Organization) Organization responsible for the care team --></managingOrganization>
 <telecom><!-- 0..* ContactPoint A contact detail for the care team (that applies to all members) --></telecom>
 <note><!-- 0..* Annotation Comments made about the CareTeam --></note>
</CareTeam>

JSON Template

{
  "resourceType" : "CareTeam",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // External Ids for this team
  "status" : "<code>", // proposed | active | suspended | inactive | entered-in-error
  "category" : [{ CodeableConcept }], // Type of team
  "name" : "<string>", // Name of the team, such as crisis assessment team
  "subject" : { Reference(Patient|Group) }, // Who care team is for
  "context" : { Reference(Encounter|EpisodeOfCare) }, // Encounter or episode associated with CareTeam
  "period" : { Period }, // Time period team covers
  "participant" : [{ // C? Members of the team
    "role" : { CodeableConcept }, // Type of involvement
    "member" : { Reference(Practitioner|RelatedPerson|Patient|Organization|
    CareTeam) }, // Who is involved
    "onBehalfOf" : { Reference(Organization) }, // Organization of the practitioner
    "period" : { Period } // Time period of participant
  }],
  "reasonCode" : [{ CodeableConcept }], // Why the care team exists
  "reasonReference" : [{ Reference(Condition) }], // Why the care team exists
  "managingOrganization" : [{ Reference(Organization) }], // Organization responsible for the care team
  "telecom" : [{ ContactPoint }], // A contact detail for the care team (that applies to all members)
  "note" : [{ Annotation }] // Comments made about the CareTeam
}

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .


[ a fhir:CareTeam;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:CareTeam.identifier [ Identifier ], ... ; # 0..* External Ids for this team
  fhir:CareTeam.status [ code ]; # 0..1 proposed | active | suspended | inactive | entered-in-error
  fhir:CareTeam.category [ CodeableConcept ], ... ; # 0..* Type of team
  fhir:CareTeam.name [ string ]; # 0..1 Name of the team, such as crisis assessment team
  fhir:CareTeam.subject [ Reference(Patient|Group) ]; # 0..1 Who care team is for
  fhir:CareTeam.context [ Reference(Encounter|EpisodeOfCare) ]; # 0..1 Encounter or episode associated with CareTeam
  fhir:CareTeam.period [ Period ]; # 0..1 Time period team covers
  fhir:CareTeam.participant [ # 0..* Members of the team
    fhir:CareTeam.participant.role [ CodeableConcept ]; # 0..1 Type of involvement
    fhir:CareTeam.participant.member [ Reference(Practitioner|RelatedPerson|Patient|Organization|CareTeam) ]; # 0..1 Who is involved
    fhir:CareTeam.participant.onBehalfOf [ Reference(Organization) ]; # 0..1 Organization of the practitioner
    fhir:CareTeam.participant.period [ Period ]; # 0..1 Time period of participant
  ], ...;
  fhir:CareTeam.reasonCode [ CodeableConcept ], ... ; # 0..* Why the care team exists
  fhir:CareTeam.reasonReference [ Reference(Condition) ], ... ; # 0..* Why the care team exists
  fhir:CareTeam.managingOrganization [ Reference(Organization) ], ... ; # 0..* Organization responsible for the care team
  fhir:CareTeam.telecom [ ContactPoint ], ... ; # 0..* A contact detail for the care team (that applies to all members)
  fhir:CareTeam.note [ Annotation ], ... ; # 0..* Comments made about the CareTeam
]

Changes since DSTU2

This resource did not exist in Release 2

This analysis is available as XML or JSON.

Alternate definitions: Master Definition (XML, JSON), XML Schema/Schematron + JSON Schema, ShEx (for Turtle) + see the extensions & the dependency analysis

9.7.3.1 Terminology Bindings

Path	Definition	Type	Reference
CareTeam.status	Indicates the status of the care team.	Required	CareTeamStatus
CareTeam.category	Indicates the type of care team.	Example	CareTeamCategory
CareTeam.participant.role	Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.	Example	Participant Roles
CareTeam.reasonCode	Indicates the reason for the care team.	Example	SNOMED CT Clinical Findings

Path

Definition

Type

Reference

CareTeam.status

Indicates the status of the care team.

Required

CareTeamStatus

CareTeam.category

Indicates the type of care team.

Example

CareTeamCategory

CareTeam.participant.role

Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.

Example

Participant Roles

CareTeam.reasonCode

Indicates the reason for the care team.

Example

SNOMED CT Clinical Findings

9.7.3.2 Constraints

ctm-1: On CareTeam.participant: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner (expression on CareTeam.participant: onBehalfOf.exists() implies (member.resolve() is Practitioner))

9.7.3.3 Notes

The Provenance resource can be used for detailed review information, such as when the care team was last reviewed and by whom.

9.7.4 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

Name	Type	Description	Expression	In Common
category	token	Type of team	CareTeam.category
context	reference	Encounter or episode associated with CareTeam	CareTeam.context (EpisodeOfCare, Encounter)
date	date	Time period team covers	CareTeam.period	17 Resources
encounter	reference	Encounter or episode associated with CareTeam	CareTeam.context (Encounter)
identifier	token	External Ids for this team	CareTeam.identifier	26 Resources
participant	reference	Who is involved	CareTeam.participant.member (Practitioner, Organization, CareTeam, Patient, RelatedPerson)
patient	reference	Who care team is for	CareTeam.subject (Patient)	29 Resources
status	token	proposed \| active \| suspended \| inactive \| entered-in-error	CareTeam.status
subject	reference	Who care team is for	CareTeam.subject (Group, Patient)