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

9.7 Resource CareTeam - Content

Patient Care Work GroupMaturity Level: 2 Trial UseCompartments: 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.

The Care Team resource includes all the people and/or organizations who plan to participate in the coordination and delivery of care for a patient. 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.

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, CommunicationRequest, Consent and EpisodeOfCare

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. CareTeam DomainResourcePlanned 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
CareTeamCategory (Example)
... name Σ0..1stringName of the team, such as crisis assessment team
... subject Σ0..1Reference(Patient | Group)Who care team is for
... context Σ0..1Reference(Encounter | EpisodeOfCare)Encounter or episode associated with CareTeam
... period Σ0..1PeriodTime period team covers
... participant I0..*BackboneElementMembers of the team
+ CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner
.... role Σ0..1CodeableConceptType of involvement
Participant Roles (Example)
.... member Σ0..1Reference(Practitioner | 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
... note 0..*AnnotationComments made about the CareTeam

doco Documentation for this format

UML Diagram (Legend)

CareTeam (DomainResource)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 appropriateidentifier : 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 teamcategory : 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 teamsname : string [0..1]Identifies the patient or group whose intended care is handled by the teamsubject : Reference [0..1] Patient|Group The encounter or episode of care that establishes the context for this care teamcontext : Reference [0..1] Encounter|EpisodeOfCare 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..*] Indicates the reason for the care team. (Strength=Example)SNOMED CT Clinical Findings?? Condition(s) that this care team addressesreasonReference : Reference [0..*] Condition The organization responsible for the care teammanagingOrganization : Reference [0..*] Organization 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..1] Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. (Strength=Example)Participant Roles?? The specific person or organization who is participating/expected to participate in the care teammember : Reference [0..1] Practitioner|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(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>
 <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(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.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

NameFlagsCard.TypeDescription & Constraintsdoco
.. CareTeam DomainResourcePlanned 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
CareTeamCategory (Example)
... name Σ0..1stringName of the team, such as crisis assessment team
... subject Σ0..1Reference(Patient | Group)Who care team is for
... context Σ0..1Reference(Encounter | EpisodeOfCare)Encounter or episode associated with CareTeam
... period Σ0..1PeriodTime period team covers
... participant I0..*BackboneElementMembers of the team
+ CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner
.... role Σ0..1CodeableConceptType of involvement
Participant Roles (Example)
.... member Σ0..1Reference(Practitioner | 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
... note 0..*AnnotationComments made about the CareTeam

doco Documentation for this format

UML Diagram (Legend)

CareTeam (DomainResource)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 appropriateidentifier : 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 teamcategory : 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 teamsname : string [0..1]Identifies the patient or group whose intended care is handled by the teamsubject : Reference [0..1] Patient|Group The encounter or episode of care that establishes the context for this care teamcontext : Reference [0..1] Encounter|EpisodeOfCare 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..*] Indicates the reason for the care team. (Strength=Example)SNOMED CT Clinical Findings?? Condition(s) that this care team addressesreasonReference : Reference [0..*] Condition The organization responsible for the care teammanagingOrganization : Reference [0..*] Organization 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..1] Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. (Strength=Example)Participant Roles?? The specific person or organization who is participating/expected to participate in the care teammember : Reference [0..1] Practitioner|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(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>
 <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(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.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 (for ) + JSON Schema, ShEx (for Turtle)

PathDefinitionTypeReference
CareTeam.status Indicates the status of the care team.RequiredCareTeamStatus
CareTeam.category Indicates the type of care team.ExampleCareTeamCategory
CareTeam.participant.role Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.ExampleParticipant Roles
CareTeam.reasonCode Indicates the reason for the care team.ExampleSNOMED CT Clinical Findings

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

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

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
contextreferenceEncounter or episode associated with CareTeamCareTeam.context
(EpisodeOfCare, Encounter)
datedateTime period team coversCareTeam.period18 Resources
encounterreferenceEncounter or episode associated with CareTeamCareTeam.context
(Encounter)
identifiertokenExternal Ids for this teamCareTeam.identifier26 Resources
participantreferenceWho is involvedCareTeam.participant.member
(Practitioner, Organization, CareTeam, Patient, RelatedPerson)
patientreferenceWho care team is forCareTeam.subject
(Patient)
31 Resources
statustokenproposed | active | suspended | inactive | entered-in-errorCareTeam.status
subjectreferenceWho care team is forCareTeam.subject
(Group, Patient)