FHIR Release 3 (STU) 4

This page is part of the FHIR Specification (v3.0.2: (v4.0.1: R4 - Mixed Normative and STU 3). ) in it's permanent home (it will always be available at this URL). 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 R4 R3

9.7 Resource CareTeam - Content

Patient Care Work Group Maturity Level : 2   Trial Use Security Category : Patient Compartments : Encounter , 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 Care Team resource CareTeam includes all the people and/or people, teams, and organizations who plan to participate in the coordination and delivery of care for a patient. 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 , itself, ChargeItem , Communication , CommunicationRequest , Consent , Contract , DeviceRequest , DiagnosticReport , EpisodeOfCare , ImagingStudy , Media , MedicationRequest , Observation , ServiceRequest and EpisodeOfCare Task

9.7.3 Resource Content

Structure

0..1
Name Flags Card. Type Description & Constraints doco
. . 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 Care Team category ( 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 encounter Σ 0..1 Reference ( Encounter | EpisodeOfCare ) Encounter or episode associated with CareTeam created as part of
. . . period Σ 0..1 Period Time period team covers
. . . participant I 0..* BackboneElement Members of the team
+ Rule: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner
. . . . role Σ 0..* CodeableConcept Type of involvement
Participant Roles ( Example )
. . . . member Σ 0..1 Reference ( Practitioner | PractitionerRole | 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

doco Documentation for this format

UML Diagram ( Legend )

CareTeam ( DomainResource ) This records Business identifiers associated with assigned to this care team that are defined by business processes and/or used to refer to it when a direct URL reference to the performer or other systems which remain constant as the resource itself is not appropriate updated and propagates from server to server identifier : Identifier [0..*] Indicates the current state of the care team (this element modifies the meaning of other elements) status : code [0..1] « Indicates the status of the care team. (Strength=Required) CareTeamStatus ! » 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 category : CodeableConcept [0..*] « Indicates the type of care team. (Strength=Example) CareTeamCategory ?? » A label for human use intended to distinguish like teams. E.g. the "red" "red" vs. "green" "green" trauma teams name : string [0..1] Identifies the patient or group whose intended care is handled by the team subject : Reference [0..1] « Patient | Group » The encounter Encounter during which this CareTeam was created or episode of care that establishes to which the context for creation of this care team record is tightly associated context encounter : Reference [0..1] « Encounter | EpisodeOfCare » Indicates when the team did (or is intended to) come into effect and end period : Period [0..1] Describes why the care team exists reasonCode : CodeableConcept [0..*] « Indicates the reason for the care team. (Strength=Example) SNOMED CT Clinical Findings SNOMEDCTClinicalFindings ?? » Condition(s) that this care team addresses reasonReference : Reference [0..*] « Condition » The organization responsible for the care team managingOrganization : Reference [0..*] « Organization » A central contact detail for the care team (that applies to all members) telecom : ContactPoint [0..*] Comments made about the CareTeam note : Annotation [0..*] Participant Indicates specific responsibility of an individual within the care team, such as "Primary "Primary care physician", "Trained physician", "Trained social worker counselor", "Caregiver", counselor", "Caregiver", etc role : CodeableConcept [0..1] [0..*] « Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", "Primary physician", "Team coordinator", "Caregiver", etc. (Strength=Example) Participant Roles ParticipantRoles ?? » The specific person or organization who is participating/expected to participate in the care team member : Reference [0..1] « Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam » The organization of the practitioner onBehalfOf : Reference [0..1] « Organization » Indicates when the specific member or organization did (or is intended to) come into effect and end period : Period [0..1] Identifies all people and organizations who are expected to be involved in the care team participant [0..*]

XML Template 

<

<CareTeam xmlns="http://hl7.org/fhir"> doco

 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <</identifier>
 <

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

 <encounter><!-- 0..1 Reference(Encounter) Encounter created as part of --></encounter>

 <period><!-- 0..1 Period Time period team covers --></period>
 <participant>  <!-- ?? 0..* Members of the team -->
  <</role>
  <|
    </member>

  <role><!-- 0..* CodeableConcept Type of involvement --></role>
  <member><!-- 0..1 Reference(Practitioner|PractitionerRole|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>

Turtle Template 

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


[ 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:

  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:

  fhir:CareTeam.encounter [ Reference(Encounter) ]; # 0..1 Encounter created as part of

  fhir:CareTeam.period [ Period ]; # 0..1 Time period team covers
  fhir:CareTeam.participant [ # 0..* Members of the team
    fhir:
    fhir:

    fhir:CareTeam.participant.role [ CodeableConcept ], ... ; # 0..* Type of involvement
    fhir:CareTeam.participant.member [ Reference(Practitioner|PractitionerRole|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 R3

CareTeam
CareTeam.status
  • Change value set from http://hl7.org/fhir/ValueSet/care-team-status to http://hl7.org/fhir/ValueSet/care-team-status|4.0.1
CareTeam.encounter
  • Added Element
CareTeam.participant.role
  • Max Cardinality changed from 1 to *
CareTeam.participant.member
  • Type Reference: Added Target Type PractitionerRole
CareTeam.telecom
  • Added Element
CareTeam.context
  • deleted

This resource did not exist in Release 2 See the Full Difference for further information

This analysis is available as XML or JSON .

See R3 <--> R4 Conversion Maps (status = 1 test that all execute ok. All tests pass round-trip testing and 1 r3 resources are invalid (0 errors). )

Structure

0..1
Name Flags Card. Type Description & Constraints doco
. . 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 Care Team category ( 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 encounter Σ 0..1 Reference ( Encounter | EpisodeOfCare ) Encounter or episode associated with CareTeam created as part of
. . . period Σ 0..1 Period Time period team covers
. . . participant I 0..* BackboneElement Members of the team
+ Rule: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner
. . . . role Σ 0..* CodeableConcept Type of involvement
Participant Roles ( Example )
. . . . member Σ 0..1 Reference ( Practitioner | PractitionerRole | 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

doco Documentation for this format

UML Diagram ( Legend )

CareTeam ( DomainResource ) This records Business identifiers associated with assigned to this care team that are defined by business processes and/or used to refer to it when a direct URL reference to the performer or other systems which remain constant as the resource itself is not appropriate updated and propagates from server to server identifier : Identifier [0..*] Indicates the current state of the care team (this element modifies the meaning of other elements) status : code [0..1] « Indicates the status of the care team. (Strength=Required) CareTeamStatus ! » 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 category : CodeableConcept [0..*] « Indicates the type of care team. (Strength=Example) CareTeamCategory ?? » A label for human use intended to distinguish like teams. E.g. the "red" "red" vs. "green" "green" trauma teams name : string [0..1] Identifies the patient or group whose intended care is handled by the team subject : Reference [0..1] « Patient | Group » The encounter Encounter during which this CareTeam was created or episode of care that establishes to which the context for creation of this care team record is tightly associated context encounter : Reference [0..1] « Encounter | EpisodeOfCare » Indicates when the team did (or is intended to) come into effect and end period : Period [0..1] Describes why the care team exists reasonCode : CodeableConcept [0..*] « Indicates the reason for the care team. (Strength=Example) SNOMED CT Clinical Findings SNOMEDCTClinicalFindings ?? » Condition(s) that this care team addresses reasonReference : Reference [0..*] « Condition » The organization responsible for the care team managingOrganization : Reference [0..*] « Organization » A central contact detail for the care team (that applies to all members) telecom : ContactPoint [0..*] Comments made about the CareTeam note : Annotation [0..*] Participant Indicates specific responsibility of an individual within the care team, such as "Primary "Primary care physician", "Trained physician", "Trained social worker counselor", "Caregiver", counselor", "Caregiver", etc role : CodeableConcept [0..1] [0..*] « Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", "Primary physician", "Team coordinator", "Caregiver", etc. (Strength=Example) Participant Roles ParticipantRoles ?? » The specific person or organization who is participating/expected to participate in the care team member : Reference [0..1] « Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam » The organization of the practitioner onBehalfOf : Reference [0..1] « Organization » Indicates when the specific member or organization did (or is intended to) come into effect and end period : Period [0..1] Identifies all people and organizations who are expected to be involved in the care team participant [0..*]

XML Template 

<

<CareTeam xmlns="http://hl7.org/fhir"> doco

 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <</identifier>
 <

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

 <encounter><!-- 0..1 Reference(Encounter) Encounter created as part of --></encounter>

 <period><!-- 0..1 Period Time period team covers --></period>
 <participant>  <!-- ?? 0..* Members of the team -->
  <</role>
  <|
    </member>

  <role><!-- 0..* CodeableConcept Type of involvement --></role>
  <member><!-- 0..1 Reference(Practitioner|PractitionerRole|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>

Turtle Template 

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


[ 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:

  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:

  fhir:CareTeam.encounter [ Reference(Encounter) ]; # 0..1 Encounter created as part of

  fhir:CareTeam.period [ Period ]; # 0..1 Time period team covers
  fhir:CareTeam.participant [ # 0..* Members of the team
    fhir:
    fhir:

    fhir:CareTeam.participant.role [ CodeableConcept ], ... ; # 0..* Type of involvement
    fhir:CareTeam.participant.member [ Reference(Practitioner|PractitionerRole|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 Release 3

CareTeam
CareTeam.status
  • Change value set from http://hl7.org/fhir/ValueSet/care-team-status to http://hl7.org/fhir/ValueSet/care-team-status|4.0.1
CareTeam.encounter
  • Added Element
CareTeam.participant.role
  • Max Cardinality changed from 1 to *
CareTeam.participant.member
  • Type Reference: Added Target Type PractitionerRole
CareTeam.telecom
  • Added Element
CareTeam.context
  • deleted

This resource did not exist in Release 2 See the Full Difference for further information

This analysis is available as XML or JSON .

See R3 <--> R4 Conversion Maps (status = 1 test that all execute ok. All tests pass round-trip testing and 1 r3 resources are invalid (0 errors). )

 

Alternate See the Profiles & Extensions and the alternate definitions: Master Definition ( XML , + JSON ), , XML Schema / Schematron (for ) + 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", "Primary physician", "Team coordinator", "Caregiver", etc. Example Participant Roles ParticipantRoles
CareTeam.reasonCode Indicates the reason for the care team. Example SNOMED CT Clinical Findings SNOMEDCTClinicalFindings

9.7.3.2 Constraints

id Level Location Description Expression
ctm-1 : On CareTeam.participant: Rule 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) (member.resolve().iif(empty(), true, ofType(Practitioner).exists())) )

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.

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