FHIR Release 3 (STU) CI-Build

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 Continuous Integration Build of available versions, see FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon . Page versions: R5 R4B R4 R3

9.7 Resource CareTeam - Content

Responsible Owner: Patient Care icon Work Group   Normative Maturity Level : 2   Trial Use Security Category : Patient Compartments : Group , Patient , Practitioner , RelatedPerson

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

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

  • a patient. This single patient, or
  • a group (such as a married couple in therapy or a support group), or
  • an event, prior to a subject being identified (such as a code blue team or emergency response 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, episode of care, an encounter, or may reflect all known team members across these perspectives. A CareTeam can be dynamic over time, such that there can be transience of team members, such as a rehabilitation team.

Care Team is distinct from Group. the Group is patient-independent and resource. The Group resource 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 participants within a particular Patient. The actors CareTeam 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

Structure

Organization of Why Σ
Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . CareTeam N 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 Binding: Care Team Status ( Required )
. . . category Σ 0..* CodeableConcept Type of team
CareTeamCategory Binding: Care Team category ( Example )

. . . 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 C 0..* BackboneElement Members of the team
+ CareTeam.participant.onBehalfOf can only be populated when Warning: CareTeam.participant.role or CareTeam.participant.member is a Practitioner exists

. . . . role Σ C 0..1 CodeableConcept Type of involvement
Binding: Participant Roles ( Example )
. . . . member Σ C 0..1 Reference ( Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam | Group | HealthcareService ) Who is involved
. . . . onBehalfOf Σ 0..1 Reference ( Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam | Group | HealthcareService ) Entity that the practitioner participant is acting as a proxy of, or an agent of, or in the interest of, or as a representative of
. . . period . effective[x] 0..1 When the member is generally available within this care team
..... effectivePeriod Period Time period of participant
. . reasonCode . . . effectiveTiming Timing
. . . . supportingInfo Σ 0..* Reference ( Any ) Basis for the member's participation
CodeableConcept
. . . reason 0..* CodeableReference ( Condition ) Why the care team exists
Binding: SNOMED CT Clinical Findings ( Example )

. . . reasonReference managingOrganization Σ 0..* Reference ( Condition Organization ) Organization responsible for the care team exists

. . managingOrganization . telecom 0..* Reference ( Organization ContactPoint ) Organization responsible 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 icon

See the Extensions for this resource

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. 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 team category : CodeableConcept [0..*] « Indicates the type of care team. null (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 or episode of care that establishes the context for this care team context : 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 reason : CodeableConcept CodeableReference [0..*] « Condition ; Indicates the reason for the care team. null (Strength=Example) SNOMED CT Clinical Findings SNOMEDCTClinicalFindings ?? » Condition(s) that this The organization responsible for the care team addresses reasonReference managingOrganization : Reference [0..*] Condition « Organization » The organization responsible A central contact detail for the care team (that applies to all members) managingOrganization telecom : Reference ContactPoint [0..*] Organization 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] « Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. null (Strength=Example) Participant Roles ParticipantRoles ?? » « This element has or is affected by some invariants C » 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 | Group | HealthcareService » « This element has or is affected by some invariants C » The organization of Entity that the practitioner participant is acting as a proxy of, or an agent of, or in the interest of, or as a representative of onBehalfOf : Reference [0..1] « Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam | Group | HealthcareService » 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 effective[x] : Period DataType [0..1] « Period | Timing » The basis for the member's role participation in care team. For example, supporting documentation that establishes legal power of attorney or court ordered guardianship supportingInfo : Reference [0..*] « Any » 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>
 <
 <</subject>
 <</context>

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

 <period><!-- 0..1 Period Time period team covers --></period>
 <
  <</role>
  <|
    </member>
  <</onBehalfOf>
  <</period>

 <participant>  <!-- 0..* Members of the team -->
  <role><!-- I 0..1 CodeableConcept Type of involvement --></role>
  <member><!-- I 0..1 Reference(CareTeam|Group|HealthcareService|Organization|
    Patient|Practitioner|PractitionerRole|RelatedPerson) Who is involved --></member>

  <onBehalfOf><!-- 0..1 Reference(CareTeam|Group|HealthcareService|Organization|
    Patient|Practitioner|PractitionerRole|RelatedPerson) Entity that the participant is acting as a proxy of, or an agent of, or in the interest of, or as a representative of --></onBehalfOf>

  <effective[x]><!-- 0..1 Period|Timing When the member is generally available within this care team --></effective[x]>
  <supportingInfo><!-- 0..* Reference(Any) Basis for the member's participation --></supportingInfo>

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

JSON Template

{doco
  "resourceType" : "",

  "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(Group|Patient) }, // Who care team is for
  "period" : { Period }, // Time period team covers
  "participant" : [{ // Members of the team
    "role" : { CodeableConcept }, // I Type of involvement
    "member" : { Reference(CareTeam|Group|HealthcareService|Organization|
    Patient|Practitioner|PractitionerRole|RelatedPerson) }, // I Who is involved

    "onBehalfOf" : { Reference(CareTeam|Group|HealthcareService|Organization|
    Patient|Practitioner|PractitionerRole|RelatedPerson) }, // Entity that the participant is acting as a proxy of, or an agent of, or in the interest of, or as a representative of
    // effective[x]: When the member is generally available within this care team. One of these 2:

    "effectivePeriod" : { Period },
    "effectiveTiming" : { Timing },
    "supportingInfo" : [{ Reference(Any) }] // Basis for the member's participation

  }],
  "
  "
  "
  "

  "reason" : [{ CodeableReference(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/> .doco


[ a fhir:;

[ a fhir:CareTeam;

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

  # from 
  # from 
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
    fhir:
    fhir:
    fhir:
    fhir:
  ], ...;
  fhir:
  fhir:
  fhir:
  fhir:

  # from Resource: fhir:id, fhir:meta, fhir:implicitRules, and fhir:language
  # from DomainResource: fhir:text, fhir:contained, fhir:extension, and fhir:modifierExtension
  fhir:identifier  ( [ Identifier ] ... ) ; # 0..* External Ids for this team
  fhir:status [ code ] ; # 0..1 proposed | active | suspended | inactive | entered-in-error
  fhir:category  ( [ CodeableConcept ] ... ) ; # 0..* Type of team
  fhir:name [ string ] ; # 0..1 Name of the team, such as crisis assessment team
  fhir:subject [ Reference(Group|Patient) ] ; # 0..1 Who care team is for
  fhir:period [ Period ] ; # 0..1 Time period team covers
  fhir:participant ( [ # 0..* Members of the team
    fhir:role [ CodeableConcept ] ; # 0..1 I Type of involvement
    fhir:member [ Reference(CareTeam|Group|HealthcareService|Organization|Patient|Practitioner|
  PractitionerRole|RelatedPerson) ] ; # 0..1 I Who is involved

    fhir:onBehalfOf [ Reference(CareTeam|Group|HealthcareService|Organization|Patient|Practitioner|
  PractitionerRole|RelatedPerson) ] ; # 0..1 Entity that the participant is acting as a proxy of, or an agent of, or in the interest of, or as a representative of

    # effective[x] : 0..1 When the member is generally available within this care team. One of these 2
      fhir:effective [  a fhir:Period ; Period ]
      fhir:effective [  a fhir:Timing ; Timing ]
    fhir:supportingInfo  ( [ Reference(Any) ] ... ) ; # 0..* Basis for the member's participation
  ] ... ) ;
  fhir:reason  ( [ CodeableReference(Condition) ] ... ) ; # 0..* Why the care team exists
  fhir:managingOrganization  ( [ Reference(Organization) ] ... ) ; # 0..* Organization responsible for the care team
  fhir:telecom  ( [ ContactPoint ] ... ) ; # 0..* A contact detail for the care team (that applies to all members)
  fhir:note  ( [ Annotation ] ... ) ; # 0..* Comments made about the CareTeam

]

Changes since DSTU2 from both R4 and R4B

CareTeam
CareTeam.participant.role
  • Max Cardinality changed from * to 1
CareTeam.participant.member
  • Type Reference: Added Target Types Group, HealthcareService
CareTeam.participant.onBehalfOf
  • Type Reference: Added Target Types Practitioner, PractitionerRole, RelatedPerson, Patient, CareTeam, Group, HealthcareService
CareTeam.participant.effective[x]
  • Added Element
CareTeam.participant.supportingInfo
  • Added Element
CareTeam.reason
  • Added Element
CareTeam.encounter
  • Deleted (Avoid circular references since Encounter references CareTeam)
CareTeam.participant.period
  • Deleted
CareTeam.reasonCode
  • Deleted (-> CareTeam.reason)
CareTeam.reasonReference
  • Deleted (-> CareTeam.reason)

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

This analysis is available for R4 as XML or JSON and for R4B as XML or JSON .

Structure

Organization of Why Σ
Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . CareTeam N 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 Binding: Care Team Status ( Required )
. . . category Σ 0..* CodeableConcept Type of team
CareTeamCategory Binding: Care Team category ( Example )

. . . 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 C 0..* BackboneElement Members of the team
+ CareTeam.participant.onBehalfOf can only be populated when Warning: CareTeam.participant.role or CareTeam.participant.member is a Practitioner exists

. . . . role Σ C 0..1 CodeableConcept Type of involvement
Binding: Participant Roles ( Example )
. . . . member Σ C 0..1 Reference ( Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam | Group | HealthcareService ) Who is involved
. . . . onBehalfOf Σ 0..1 Reference ( Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam | Group | HealthcareService ) Entity that the practitioner participant is acting as a proxy of, or an agent of, or in the interest of, or as a representative of
. . . period . effective[x] 0..1 When the member is generally available within this care team
..... effectivePeriod Period Time period of participant
. . reasonCode . . . effectiveTiming Timing
. . . . supportingInfo Σ 0..* Reference ( Any ) Basis for the member's participation
CodeableConcept
. . . reason 0..* CodeableReference ( Condition ) Why the care team exists
Binding: SNOMED CT Clinical Findings ( Example )

. . . reasonReference managingOrganization Σ 0..* Reference ( Condition Organization ) Organization responsible for the care team exists

. . managingOrganization . telecom 0..* Reference ( Organization ContactPoint ) Organization responsible 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 icon

See the Extensions for this resource

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. 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 team category : CodeableConcept [0..*] « Indicates the type of care team. null (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 or episode of care that establishes the context for this care team context : 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 reason : CodeableConcept CodeableReference [0..*] « Condition ; Indicates the reason for the care team. null (Strength=Example) SNOMED CT Clinical Findings SNOMEDCTClinicalFindings ?? » Condition(s) that this The organization responsible for the care team addresses reasonReference managingOrganization : Reference [0..*] Condition « Organization » The organization responsible A central contact detail for the care team (that applies to all members) managingOrganization telecom : Reference ContactPoint [0..*] Organization 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] « Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. null (Strength=Example) Participant Roles ParticipantRoles ?? » « This element has or is affected by some invariants C » 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 | Group | HealthcareService » « This element has or is affected by some invariants C » The organization of Entity that the practitioner participant is acting as a proxy of, or an agent of, or in the interest of, or as a representative of onBehalfOf : Reference [0..1] « Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam | Group | HealthcareService » 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 effective[x] : Period DataType [0..1] « Period | Timing » The basis for the member's role participation in care team. For example, supporting documentation that establishes legal power of attorney or court ordered guardianship supportingInfo : Reference [0..*] « Any » 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>
 <
 <</subject>
 <</context>

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

 <period><!-- 0..1 Period Time period team covers --></period>
 <
  <</role>
  <|
    </member>
  <</onBehalfOf>
  <</period>

 <participant>  <!-- 0..* Members of the team -->
  <role><!-- I 0..1 CodeableConcept Type of involvement --></role>
  <member><!-- I 0..1 Reference(CareTeam|Group|HealthcareService|Organization|
    Patient|Practitioner|PractitionerRole|RelatedPerson) Who is involved --></member>

  <onBehalfOf><!-- 0..1 Reference(CareTeam|Group|HealthcareService|Organization|
    Patient|Practitioner|PractitionerRole|RelatedPerson) Entity that the participant is acting as a proxy of, or an agent of, or in the interest of, or as a representative of --></onBehalfOf>

  <effective[x]><!-- 0..1 Period|Timing When the member is generally available within this care team --></effective[x]>
  <supportingInfo><!-- 0..* Reference(Any) Basis for the member's participation --></supportingInfo>

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

JSON Template

{doco
  "resourceType" : "",

  "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(Group|Patient) }, // Who care team is for
  "period" : { Period }, // Time period team covers
  "participant" : [{ // Members of the team
    "role" : { CodeableConcept }, // I Type of involvement
    "member" : { Reference(CareTeam|Group|HealthcareService|Organization|
    Patient|Practitioner|PractitionerRole|RelatedPerson) }, // I Who is involved

    "onBehalfOf" : { Reference(CareTeam|Group|HealthcareService|Organization|
    Patient|Practitioner|PractitionerRole|RelatedPerson) }, // Entity that the participant is acting as a proxy of, or an agent of, or in the interest of, or as a representative of
    // effective[x]: When the member is generally available within this care team. One of these 2:

    "effectivePeriod" : { Period },
    "effectiveTiming" : { Timing },
    "supportingInfo" : [{ Reference(Any) }] // Basis for the member's participation

  }],
  "
  "
  "
  "

  "reason" : [{ CodeableReference(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/> .doco


[ a fhir:;

[ a fhir:CareTeam;

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

  # from 
  # from 
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
    fhir:
    fhir:
    fhir:
    fhir:
  ], ...;
  fhir:
  fhir:
  fhir:
  fhir:

  # from Resource: fhir:id, fhir:meta, fhir:implicitRules, and fhir:language
  # from DomainResource: fhir:text, fhir:contained, fhir:extension, and fhir:modifierExtension
  fhir:identifier  ( [ Identifier ] ... ) ; # 0..* External Ids for this team
  fhir:status [ code ] ; # 0..1 proposed | active | suspended | inactive | entered-in-error
  fhir:category  ( [ CodeableConcept ] ... ) ; # 0..* Type of team
  fhir:name [ string ] ; # 0..1 Name of the team, such as crisis assessment team
  fhir:subject [ Reference(Group|Patient) ] ; # 0..1 Who care team is for
  fhir:period [ Period ] ; # 0..1 Time period team covers
  fhir:participant ( [ # 0..* Members of the team
    fhir:role [ CodeableConcept ] ; # 0..1 I Type of involvement
    fhir:member [ Reference(CareTeam|Group|HealthcareService|Organization|Patient|Practitioner|
  PractitionerRole|RelatedPerson) ] ; # 0..1 I Who is involved

    fhir:onBehalfOf [ Reference(CareTeam|Group|HealthcareService|Organization|Patient|Practitioner|
  PractitionerRole|RelatedPerson) ] ; # 0..1 Entity that the participant is acting as a proxy of, or an agent of, or in the interest of, or as a representative of

    # effective[x] : 0..1 When the member is generally available within this care team. One of these 2
      fhir:effective [  a fhir:Period ; Period ]
      fhir:effective [  a fhir:Timing ; Timing ]
    fhir:supportingInfo  ( [ Reference(Any) ] ... ) ; # 0..* Basis for the member's participation
  ] ... ) ;
  fhir:reason  ( [ CodeableReference(Condition) ] ... ) ; # 0..* Why the care team exists
  fhir:managingOrganization  ( [ Reference(Organization) ] ... ) ; # 0..* Organization responsible for the care team
  fhir:telecom  ( [ ContactPoint ] ... ) ; # 0..* A contact detail for the care team (that applies to all members)
  fhir:note  ( [ Annotation ] ... ) ; # 0..* Comments made about the CareTeam

]

Changes since DSTU2 from both R4 and R4B

CareTeam
CareTeam.participant.role
  • Max Cardinality changed from * to 1
CareTeam.participant.member
  • Type Reference: Added Target Types Group, HealthcareService
CareTeam.participant.onBehalfOf
  • Type Reference: Added Target Types Practitioner, PractitionerRole, RelatedPerson, Patient, CareTeam, Group, HealthcareService
CareTeam.participant.effective[x]
  • Added Element
CareTeam.participant.supportingInfo
  • Added Element
CareTeam.reason
  • Added Element
CareTeam.encounter
  • Deleted (Avoid circular references since Encounter references CareTeam)
CareTeam.participant.period
  • Deleted
CareTeam.reasonCode
  • Deleted (-> CareTeam.reason)
CareTeam.reasonReference
  • Deleted (-> CareTeam.reason)

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

This analysis is available for R4 as XML or JSON and for R4B as XML or JSON .

 

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

Path Definition ValueSet Type Reference Documentation
CareTeam.status Indicates the status of the care team. CareTeamStatus Required CareTeamStatus

Indicates the status of the care team.

CareTeam.category Indicates the type of care team. CareTeamCategory Example CareTeamCategory

Indicates the type of care team.

CareTeam.participant.role Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. ParticipantRoles Example Participant

Roles of participants that may be included in a care team. Defined as: Healthcare professional (occupation) or Services (qualifier value).

CareTeam.reasonCode CareTeam.reason Indicates the reason for the care team. SNOMEDCTClinicalFindings Example

This value set includes all the "Clinical finding" SNOMED CT Clinical Findings icon codes - concepts where concept is-a 404684003 (Clinical finding (finding)).

UniqueKey Level Location Description Expression
ctm-1 : On CareTeam.participant: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner ( expression img  ctm-2 Warning on CareTeam.participant: CareTeam.participant CareTeam.participant.role or CareTeam.participant.member exists onBehalfOf.exists() implies (member.resolve() is Practitioner) role.exists() or member.exists() )

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. See also the full list of search parameters for this resource , and check the Extensions registry for search parameters on extensions related to this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

reference Encounter or episode associated with CareTeam CareTeam.context ( EpisodeOfCare , Encounter )
Name Type Description Expression In Common
category token Type of team CareTeam.category context
date date Time period team covers A date within the coverage time period. CareTeam.period 18 22 Resources
identifier encounter reference token Encounter or episode associated with CareTeam External Ids for this team CareTeam.context ( Encounter ) CareTeam.identifier 58 Resources
name identifier token string External Ids for this Name of the team, such as crisis assessment team CareTeam.identifier CareTeam.name | CareTeam.extension('http://hl7.org/fhir/StructureDefinition/careteam-alias').value 26 Resources
participant reference Who is involved CareTeam.participant.member
( Practitioner , Group , Organization , CareTeam , Patient , HealthcareService , PractitionerRole , RelatedPerson )
patient reference Who care team is for CareTeam.subject CareTeam.subject.where(resolve() is Patient)
( Patient )
31 60 Resources
status token proposed | active | suspended | inactive | entered-in-error CareTeam.status
subject reference Who care team is for CareTeam.subject
( Group , Patient )