Release 4B

This page is part of the FHIR Specification (v4.3.0: R4B - STU). 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 GroupMaturity Level: 2 Trial UseSecurity 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 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.

9.7.3 References

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

This resource does not implement any patterns.

9.7.4 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. CareTeam TUDomainResourcePlanned 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..*IdentifierExternal Ids for this team
... status ?!Σ0..1codeproposed | active | suspended | inactive | entered-in-error
CareTeamStatus (Required)
... category Σ0..*CodeableConceptType of team
Care Team category (Example)
... subject Σ0..1Reference(Patient | Group)Who care team is for
... encounter Σ0..1Reference(Encounter)Encounter created as part of
... period Σ0..1PeriodTime period team covers
... participant I0..*BackboneElementMembers of the team
+ Rule: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner
.... role Σ0..*CodeableConceptType of involvement
Participant Roles (Example)
.... member Σ0..1Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam)Who is involved
.... onBehalfOf Σ0..1Reference(Organization)Organization of the practitioner
.... period 0..1PeriodTime period of participant
... reasonCode 0..*CodeableConceptWhy 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..*ContactPointA contact detail for the care team (that applies to all members)
... note 0..*AnnotationComments 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 serveridentifier : Identifier [0..*]Indicates the current state of the care team (this element modifies the meaning of other elements)status : code [0..1] « null (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 teamcategory : CodeableConcept [0..*] « null (Strength=Example)CareTeamCategory?? »A label for human use intended to distinguish like teams. E.g. the "red" vs. "green" trauma teamsname : string [0..1]Identifies the patient or group whose intended care is handled by the teamsubject : Reference [0..1] « Patient|Group »The Encounter during which this CareTeam was created or to which the creation of this record is tightly associatedencounter : Reference [0..1] « Encounter »Indicates when the team did (or is intended to) come into effect and endperiod : Period [0..1]Describes why the care team existsreasonCode : CodeableConcept [0..*] « null (Strength=Example)SNOMEDCTClinicalFindings?? »Condition(s) that this care team addressesreasonReference : Reference [0..*] « Condition »The organization responsible for the care teammanagingOrganization : Reference [0..*] « Organization »A central contact detail for the care team (that applies to all members)telecom : ContactPoint [0..*]Comments made about the CareTeamnote : Annotation [0..*]ParticipantIndicates specific responsibility of an individual within the care team, such as "Primary care physician", "Trained social worker counselor", "Caregiver", etcrole : CodeableConcept [0..*] « null (Strength=Example)ParticipantRoles?? »The specific person or organization who is participating/expected to participate in the care teammember : Reference [0..1] « Practitioner|PractitionerRole| RelatedPerson|Patient|Organization|CareTeam »The organization of the practitioneronBehalfOf : Reference [0..1] « Organization »Indicates when the specific member or organization did (or is intended to) come into effect and endperiod : Period [0..1]Identifies all people and organizations who are expected to be involved in the care teamparticipant[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><!-- 0..1 Reference(Group|Patient) Who care team is for --></subject>
 <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><!-- 0..* 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><!-- 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: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(Group|Patient) ]; # 0..1 Who care team is for
  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:CareTeam.participant.role [ CodeableConcept ], ... ; # 0..* 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.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 R4

CareTeam
  • No Changes

See the Full Difference for further information

This analysis is available as XML or JSON.

Conversions between R3 and R4

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

NameFlagsCard.TypeDescription & Constraintsdoco
.. CareTeam TUDomainResourcePlanned 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..*IdentifierExternal Ids for this team
... status ?!Σ0..1codeproposed | active | suspended | inactive | entered-in-error
CareTeamStatus (Required)
... category Σ0..*CodeableConceptType of team
Care Team category (Example)
... subject Σ0..1Reference(Patient | Group)Who care team is for
... encounter Σ0..1Reference(Encounter)Encounter created as part of
... period Σ0..1PeriodTime period team covers
... participant I0..*BackboneElementMembers of the team
+ Rule: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner
.... role Σ0..*CodeableConceptType of involvement
Participant Roles (Example)
.... member Σ0..1Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam)Who is involved
.... onBehalfOf Σ0..1Reference(Organization)Organization of the practitioner
.... period 0..1PeriodTime period of participant
... reasonCode 0..*CodeableConceptWhy 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..*ContactPointA contact detail for the care team (that applies to all members)
... note 0..*AnnotationComments 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 serveridentifier : Identifier [0..*]Indicates the current state of the care team (this element modifies the meaning of other elements)status : code [0..1] « null (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 teamcategory : CodeableConcept [0..*] « null (Strength=Example)CareTeamCategory?? »A label for human use intended to distinguish like teams. E.g. the "red" vs. "green" trauma teamsname : string [0..1]Identifies the patient or group whose intended care is handled by the teamsubject : Reference [0..1] « Patient|Group »The Encounter during which this CareTeam was created or to which the creation of this record is tightly associatedencounter : Reference [0..1] « Encounter »Indicates when the team did (or is intended to) come into effect and endperiod : Period [0..1]Describes why the care team existsreasonCode : CodeableConcept [0..*] « null (Strength=Example)SNOMEDCTClinicalFindings?? »Condition(s) that this care team addressesreasonReference : Reference [0..*] « Condition »The organization responsible for the care teammanagingOrganization : Reference [0..*] « Organization »A central contact detail for the care team (that applies to all members)telecom : ContactPoint [0..*]Comments made about the CareTeamnote : Annotation [0..*]ParticipantIndicates specific responsibility of an individual within the care team, such as "Primary care physician", "Trained social worker counselor", "Caregiver", etcrole : CodeableConcept [0..*] « null (Strength=Example)ParticipantRoles?? »The specific person or organization who is participating/expected to participate in the care teammember : Reference [0..1] « Practitioner|PractitionerRole| RelatedPerson|Patient|Organization|CareTeam »The organization of the practitioneronBehalfOf : Reference [0..1] « Organization »Indicates when the specific member or organization did (or is intended to) come into effect and endperiod : Period [0..1]Identifies all people and organizations who are expected to be involved in the care teamparticipant[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><!-- 0..1 Reference(Group|Patient) Who care team is for --></subject>
 <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><!-- 0..* 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><!-- 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: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(Group|Patient) ]; # 0..1 Who care team is for
  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:CareTeam.participant.role [ CodeableConcept ], ... ; # 0..* 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.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 Release 4

CareTeam
  • No Changes

See the Full Difference for further information

This analysis is available as XML or JSON.

Conversions between R3 and R4

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

9.7.4.1 Terminology Bindings

PathDefinitionTypeReference
CareTeam.status RequiredCareTeamStatus
CareTeam.category ExampleCareTeamCategory
CareTeam.participant.role ExampleParticipantRoles
CareTeam.reasonCode ExampleSNOMEDCTClinicalFindings

9.7.4.2 Constraints

idLevelLocationDescriptionExpression
ctm-1Rule CareTeam.participantCareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a PractitioneronBehalfOf.exists() implies (member.resolve().iif(empty(), true, ofType(Practitioner).exists()))

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

NameTypeDescriptionExpressionIn Common
categorytokenType of teamCareTeam.category
datedateTime period team coversCareTeam.period
encounterreferenceEncounter created as part ofCareTeam.encounter
(Encounter)
identifiertokenExternal Ids for this teamCareTeam.identifier
participantreferenceWho is involvedCareTeam.participant.member
(Practitioner, Organization, CareTeam, Patient, PractitionerRole, RelatedPerson)
patientreferenceWho care team is forCareTeam.subject.where(resolve() is Patient)
(Patient)
statustokenproposed | active | suspended | inactive | entered-in-errorCareTeam.status
subjectreferenceWho care team is forCareTeam.subject
(Group, Patient)