Release 4 5 Preview #1

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

9.7.1 Scope and Usage

The CareTeam includes all the people, teams, people and organizations who plan to participate in the coordination and delivery of care for and is assigned to:

  • a single patient patient, or
  • a group (such as a married couple in therapy or a support group). CareTeam can also be organizationally assigned without group), or
  • an event, prior to a subject in context, such being identified (such as a code blue team or emergency response team. This team)

Care Team 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.

9.7.3 References

This resource is referenced by AdverseEvent , CarePlan , itself, ChargeItem , Communication , CommunicationRequest , ConditionDefinition , Consent , Contract , DeviceRequest , DiagnosticReport , DocumentReference , EpisodeOfCare , ImagingStudy , Media , MedicationRequest , Observation , Procedure , ServiceRequest and Task .

This resource implements the Participant pattern.

9.7.3 9.7.4 Resource Content

Structure

0..*
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
Care Team category ( Example )
. . . subject Σ 0..1 Reference ( Patient | Group ) Who care team is for
. . encounter Σ 0..1 Reference ( Encounter ) Encounter 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..1 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 . coverage[x] 0..1 When the member is generally available within this care team
..... coveragePeriod 0..1 Period Time period of participant
. . reasonCode . . . coverageTiming 0..* CodeableConcept Timing Why the care team exists SNOMED CT Clinical Findings ( Example )
. . . reasonReference reason 0..* Reference CodeableReference ( Condition ) Why the care team exists
SNOMED CT Clinical Findings ( Example )
. . . 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 ) 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 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" vs. "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 during which this CareTeam was created or to which the creation of this record is tightly associated encounter : Reference [0..1] « Encounter » 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 reason : CodeableConcept DataType [0..*] « Condition ; Indicates the reason for the care team. (Strength=Example) 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 care physician", "Trained social worker counselor", "Caregiver", etc role : CodeableConcept [0..*] [0..1] « Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. (Strength=Example) 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 When the specific member or organization did (or is intended to) come into effect and end generally available within this care team period coverage[x] : Period DataType [0..1] « Period | Timing » 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><!-- 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>
 <</encounter>

 <subject><!-- 0..1 Reference(Group|Patient) Who care team is for --></subject>

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

  <role><!-- 0..1 CodeableConcept Type of involvement --></role>
  <member><!-- 0..1 Reference(CareTeam|Organization|Patient|Practitioner|
    PractitionerRole|RelatedPerson) Who is involved --></member>
  <onBehalfOf><!-- 0..1 Reference(Organization) Organization of the practitioner --></onBehalfOf>
  <</period>

  <coverage[x]><!-- 0..1 Period|Timing When the member is generally available within this care team --></coverage[x]>

 </participant>
 <</reasonCode>
 <</reasonReference>

 <reason><!-- 0..* CodeableReference(Condition) Why the care team exists --></reason>

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

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

  fhir:CareTeam.subject [ Reference(Group|Patient) ]; # 0..1 Who care team is for

  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..1 Type of involvement
    fhir:CareTeam.participant.member [ Reference(CareTeam|Organization|Patient|Practitioner|PractitionerRole|RelatedPerson) ]; # 0..1 Who is involved

    fhir:CareTeam.participant.onBehalfOf [ Reference(Organization) ]; # 0..1 Organization of the practitioner
    fhir:

    # CareTeam.participant.coverage[x] : 0..1 When the member is generally available within this care team. One of these 2
      fhir:CareTeam.participant.coveragePeriod [ Period ]
      fhir:CareTeam.participant.coverageTiming [ Timing ]

  ], ...;
  fhir:
  fhir:

  fhir:CareTeam.reason [ CodeableReference(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 R3

CareTeam
CareTeam.status
  • Change value set from http://hl7.org/fhir/ValueSet/care-team-status http://hl7.org/fhir/ValueSet/care-team-status|4.0.0 to http://hl7.org/fhir/ValueSet/care-team-status|4.0.1 http://hl7.org/fhir/ValueSet/care-team-status|4.2.0
CareTeam.participant.role
  • Max Cardinality changed from * to 1
CareTeam.encounter CareTeam.participant.coverage[x]
  • Added Element
CareTeam.participant.role CareTeam.reason
  • Max Cardinality changed from 1 to * Added Element
CareTeam.participant.member CareTeam.encounter
  • Type Reference: Added Target Type PractitionerRole deleted
CareTeam.telecom CareTeam.participant.period
  • Added Element deleted
CareTeam.context CareTeam.reasonCode
  • deleted
CareTeam.reasonReference
  • deleted

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..*
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
Care Team category ( Example )
. . . subject Σ 0..1 Reference ( Patient | Group ) Who care team is for
. . encounter Σ 0..1 Reference ( Encounter ) Encounter 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..1 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 . coverage[x] 0..1 When the member is generally available within this care team
..... coveragePeriod 0..1 Period Time period of participant
. . reasonCode . . . coverageTiming 0..* CodeableConcept Timing Why the care team exists SNOMED CT Clinical Findings ( Example )
. . . reasonReference reason 0..* Reference CodeableReference ( Condition ) Why the care team exists
SNOMED CT Clinical Findings ( Example )
. . . 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 ) 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 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" vs. "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 during which this CareTeam was created or to which the creation of this record is tightly associated encounter : Reference [0..1] « Encounter » 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 reason : CodeableConcept DataType [0..*] « Condition ; Indicates the reason for the care team. (Strength=Example) 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 care physician", "Trained social worker counselor", "Caregiver", etc role : CodeableConcept [0..*] [0..1] « Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. (Strength=Example) 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 When the specific member or organization did (or is intended to) come into effect and end generally available within this care team period coverage[x] : Period DataType [0..1] « Period | Timing » 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><!-- 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>
 <</encounter>

 <subject><!-- 0..1 Reference(Group|Patient) Who care team is for --></subject>

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

  <role><!-- 0..1 CodeableConcept Type of involvement --></role>
  <member><!-- 0..1 Reference(CareTeam|Organization|Patient|Practitioner|
    PractitionerRole|RelatedPerson) Who is involved --></member>
  <onBehalfOf><!-- 0..1 Reference(Organization) Organization of the practitioner --></onBehalfOf>
  <</period>

  <coverage[x]><!-- 0..1 Period|Timing When the member is generally available within this care team --></coverage[x]>

 </participant>
 <</reasonCode>
 <</reasonReference>

 <reason><!-- 0..* CodeableReference(Condition) Why the care team exists --></reason>

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

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

  fhir:CareTeam.subject [ Reference(Group|Patient) ]; # 0..1 Who care team is for

  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..1 Type of involvement
    fhir:CareTeam.participant.member [ Reference(CareTeam|Organization|Patient|Practitioner|PractitionerRole|RelatedPerson) ]; # 0..1 Who is involved

    fhir:CareTeam.participant.onBehalfOf [ Reference(Organization) ]; # 0..1 Organization of the practitioner
    fhir:

    # CareTeam.participant.coverage[x] : 0..1 When the member is generally available within this care team. One of these 2
      fhir:CareTeam.participant.coveragePeriod [ Period ]
      fhir:CareTeam.participant.coverageTiming [ Timing ]

  ], ...;
  fhir:
  fhir:

  fhir:CareTeam.reason [ CodeableReference(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 Release 3

CareTeam
CareTeam.status
  • Change value set from http://hl7.org/fhir/ValueSet/care-team-status http://hl7.org/fhir/ValueSet/care-team-status|4.0.0 to http://hl7.org/fhir/ValueSet/care-team-status|4.0.1 http://hl7.org/fhir/ValueSet/care-team-status|4.2.0
CareTeam.participant.role
  • Max Cardinality changed from * to 1
CareTeam.encounter CareTeam.participant.coverage[x]
  • Added Element
CareTeam.participant.role CareTeam.reason
  • Max Cardinality changed from 1 to * Added Element
CareTeam.participant.member CareTeam.encounter
  • Type Reference: Added Target Type PractitionerRole deleted
CareTeam.telecom CareTeam.participant.period
  • Added Element deleted
CareTeam.context CareTeam.reasonCode
  • deleted
CareTeam.reasonReference
  • deleted

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

 

See the Profiles & Extensions and the alternate definitions: Master Definition XML + JSON , XML Schema / Schematron + JSON Schema , ShEx (for Turtle ) + see the extensions , the spreadsheet version & the dependency analysis a

9.7.3.1 9.7.4.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 ParticipantRoles
CareTeam.reasonCode CareTeam.reason Indicates the reason for the care team. Example SNOMEDCTClinicalFindings

9.7.3.2 9.7.4.2 Constraints

id Level Location Description Expression
ctm-1 Rule CareTeam.participant 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)

9.7.3.3 9.7.4.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 9.7.5 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
date date Time period team covers A date within the coverage time period. CareTeam.period 17 Resources
encounter identifier reference token Encounter created as part of External Ids for this team CareTeam.encounter ( Encounter ) CareTeam.identifier 30 Resources
identifier name N token string External Ids for this Name of the team, such as crisis assessment team CareTeam.identifier CareTeam.name 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.where(resolve() is Patient)
( Patient ) 		33 Resources
status N token proposed | active | suspended | inactive | entered-in-error CareTeam.status
subject reference Who care team is for CareTeam.subject
( Group , Patient )