STU 3 Ballot

This page is part of the FHIR Specification (v1.6.0: STU 3 Ballot 4). 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.4 Resource CareTeam - Content

Patient Care Work GroupMaturity Level: 0Compartments: 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.4.1 Scope and Usage

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.

9.4.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.) Care Team is about establishing a set of relationships and roles and is specific to a particular Patient. CareTeam can be acted upon (e.g. CommunicationRequest), but the CareTeam isn't an actor. The actors are the individual members within a CareTeam. 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

9.4.3 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. CareTeam DomainResourcePlanned participants in the coordination and delivery of care for a patient or group
... identifier Σ0..*IdentifierExternal Ids for this team
... status ?!Σ0..1CodeableConceptactive | suspended | inactive | entered in error
... type Σ0..*CodeableConceptType of team
... name Σ0..1stringName of the team, such as crisis assessment team
... subject Σ0..1Reference(Patient | Group)Who care team is for
... period Σ0..1PeriodTime period team covers
... participant 0..*BackboneElementMembers of the team
.... role Σ0..1CodeableConceptType of involvement
Participant Roles (Example)
.... member Σ0..1Reference(Practitioner | RelatedPerson | Patient | Organization)Who is involved
.... period 0..1PeriodTime period of participant
... managingOrganization Σ0..1Reference(Organization)Organization responsible for the care team

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 whether the care team is currently active, suspended, inactive, or entered in error (this element modifies the meaning of other elements)status : CodeableConcept [0..1]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 teamtype : CodeableConcept [0..*]Name of the care teamname : string [0..1]Identifies the patient or group whose intended care is handled by the teamsubject : Reference [0..1] « Patient|Group »Indicates when the team did (or is intended to) come into effect and endperiod : Period [0..1]The organization responsible for the care teammanagingOrganization : Reference [0..1] « Organization »ParticipantIndicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "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 »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><!-- 0..1 CodeableConcept active | suspended | inactive | entered in error --></status>
 <type><!-- 0..* CodeableConcept Type of team --></type>
 <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>
 <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) Who is involved --></member>
  <period><!-- 0..1 Period Time period of participant --></period>
 </participant>
 <managingOrganization><!-- 0..1 Reference(Organization) Organization responsible for the care team --></managingOrganization>
</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 [ CodeableConcept ]; # 0..1 active | suspended | inactive | entered in error
  fhir:CareTeam.type [ 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.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) ]; # 0..1 Who is involved
    fhir:CareTeam.participant.period [ Period ]; # 0..1 Time period of participant
  ], ...;
  fhir:CareTeam.managingOrganization [ Reference(Organization) ]; # 0..1 Organization responsible for the care team
]

Changes since DSTU2

This resource did not exist in Release 2

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. CareTeam DomainResourcePlanned participants in the coordination and delivery of care for a patient or group
... identifier Σ0..*IdentifierExternal Ids for this team
... status ?!Σ0..1CodeableConceptactive | suspended | inactive | entered in error
... type Σ0..*CodeableConceptType of team
... name Σ0..1stringName of the team, such as crisis assessment team
... subject Σ0..1Reference(Patient | Group)Who care team is for
... period Σ0..1PeriodTime period team covers
... participant 0..*BackboneElementMembers of the team
.... role Σ0..1CodeableConceptType of involvement
Participant Roles (Example)
.... member Σ0..1Reference(Practitioner | RelatedPerson | Patient | Organization)Who is involved
.... period 0..1PeriodTime period of participant
... managingOrganization Σ0..1Reference(Organization)Organization responsible for the care team

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 whether the care team is currently active, suspended, inactive, or entered in error (this element modifies the meaning of other elements)status : CodeableConcept [0..1]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 teamtype : CodeableConcept [0..*]Name of the care teamname : string [0..1]Identifies the patient or group whose intended care is handled by the teamsubject : Reference [0..1] « Patient|Group »Indicates when the team did (or is intended to) come into effect and endperiod : Period [0..1]The organization responsible for the care teammanagingOrganization : Reference [0..1] « Organization »ParticipantIndicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "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 »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><!-- 0..1 CodeableConcept active | suspended | inactive | entered in error --></status>
 <type><!-- 0..* CodeableConcept Type of team --></type>
 <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>
 <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) Who is involved --></member>
  <period><!-- 0..1 Period Time period of participant --></period>
 </participant>
 <managingOrganization><!-- 0..1 Reference(Organization) Organization responsible for the care team --></managingOrganization>
</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 [ CodeableConcept ]; # 0..1 active | suspended | inactive | entered in error
  fhir:CareTeam.type [ 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.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) ]; # 0..1 Who is involved
    fhir:CareTeam.participant.period [ Period ]; # 0..1 Time period of participant
  ], ...;
  fhir:CareTeam.managingOrganization [ Reference(Organization) ]; # 0..1 Organization responsible for the care team
]

Changes since DSTU2

This resource did not exist in Release 2

 

Alternate definitions: Master Definition (XML, JSON), XML Schema/Schematron (for ) + JSON Schema, ShEx (for Turtle)

9.4.3.1 Terminology Bindings

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

To do.

9.4.4 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPaths
datedateTime period team coversCareTeam.period
identifiertokenExternal Ids for this teamCareTeam.identifier
participantreferenceWho is involvedCareTeam.participant.member
(Practitioner, Organization, Patient, RelatedPerson)
patientreferenceWho care team is forCareTeam.subject
(Patient)
statustokenactive | suspended | inactive | entered in errorCareTeam.status
subjectreferenceWho care team is forCareTeam.subject
(Group, Patient)
typetokenType of teamCareTeam.type