type: resourceresource: CareTeam

CareTeam

Scope and Usage

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

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

Boundaries and Relationships

Care Team is distinct from the Group 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 participants within a 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.

CareTeam [0..*]: - Planned participants in the coordination and delivery of care
CareTeam.identifier [0..*]: Identifier External Ids for this team
CareTeam.status [0..1]: code required:care-team-status proposed | active | suspended | inactive | entered-in-error
CareTeam.category [0..*]: CodeableConcept example:care-team-category Type of team
CareTeam.name [0..1]: string Name of the team, such as crisis assessment team
CareTeam.subject [0..1]: [Reference(Patient](/Reference(Patient), Group)) Who care team is for
CareTeam.period [0..1]: Period Time period team covers
CareTeam.participant [0..*]: BackboneElement Members of the team
CareTeam.participant.role [0..1]: CodeableConcept example:participant-role Type of involvement
CareTeam.participant.member [0..1]: [Reference(Practitioner](/Reference(Practitioner), PractitionerRole, RelatedPerson, Patient, Organization, CareTeam, Group, HealthcareService)) Who is involved
CareTeam.participant.onBehalfOf [0..1]: [Reference(Practitioner](/Reference(Practitioner), PractitionerRole, RelatedPerson, Patient, Organization, CareTeam, Group, HealthcareService)) Entity that the participant is acting as a proxy of, or an agent of, or in the interest of, or as a representative of
CareTeam.participant.effective[x] [0..1]: Period, Timing When the member is generally available within this care team
CareTeam.participant.supportingInfo [0..*]: Reference(Resource) Basis for the member's participation
CareTeam.reason [0..*]: CodeableReference example:clinical-findings Why the care team exists
CareTeam.managingOrganization [0..*]: Reference(Organization) Organization responsible for the care team
CareTeam.telecom [0..*]: ContactPoint A contact detail for the care team (that applies to all members)
CareTeam.note [0..*]: Annotation Comments made about the CareTeam

Mappings

CareTeam Mappings — 19 mapping entries

Implementation Guide

implementationguide-CareTeam-core.xml

<?xml version="1.0" encoding="UTF-8"?>

<ImplementationGuide xmlns="http://hl7.org/fhir">
  <id value="CareTeam-core"/>
  <name value="CareTeamHL7Extensions"/>
  <title value="Care Team  H L7  Extensions"/>
  <status value="draft"/>
  <date value="2019-09-16T00:00:00.000"/>
  <publisher value="Health Level Seven, Inc. - Patient Care WG"/>
  <description value="Defines common extensions used with or related to the CareTeam resource"/>
</ImplementationGuide>

Resource Packs

list-CareTeam-packs.xml

<?xml version="1.0" encoding="UTF-8"?>

<List xmlns="http://hl7.org/fhir">
  <id value="CareTeam-packs"/>
  <status value="current"/>
  <mode value="working"/>
  <entry>
    <item>
      <reference value="ImplementationGuide/CareTeam-core"/>
    </item>
  </entry>
</List>

Search Parameters

category — token — Type of team — CareTeam.category
date — date — A date within the coverage time period. — -
identifier — token — External Ids for this team — CareTeam.identifier
name — string — Name of the team, such as crisis assessment team — CareTeam.name | CareTeam.extension('http://hl7.org/fhir/StructureDefinition/careteam-alias').value
participant — reference — Who is involved — CareTeam.participant.member
patient — reference — Who care team is for — CareTeam.subject.where(resolve() is Patient)
status — token — proposed | active | suspended | inactive | entered-in-error — CareTeam.status
subject — reference — Who care team is for — CareTeam.subject

Full Search Parameters

Examples

careteam-example — careteam-example
careteam-examples-header — careteam-examples-header
example — careteam-example — Care Team to address obesity

Full Examples

FiveWs.what — Unknown
FiveWs.recorded — Unknown
FiveWs.author — Unknown
FiveWs.cause — Unknown
FiveWs.version — Unknown
FiveWs.witness — Unknown
FiveWs.where — Unknown
FiveWs.context — Unknown
FiveWs.source — Unknown
FiveWs.who — Unknown
FiveWs.grade — Unknown
FiveWs.planned — Unknown
FiveWs.done — Unknown

careteam-participant-mapping-exceptions.xml

Divergent Elements

Participant.identifier → CareTeam.identifier
- shortUnmatched | reason=Unknown | pattern=Business Identifier for care team | resource=External Ids for this team
- definitionUnmatched | reason=Unknown | pattern=Business identifiers assigned to this care team by one of the applications involved. These identifiers remain constant as the resource is updated and propagates from server to server. | resource=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.
- commentsUnmatched | reason=Unknown | pattern=Note: This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number. | resource=This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.
Participant.active → CareTeam.status
- missingTypes | reason=Unknown | pattern=boolean
- extraTypes | reason=Unknown
- shortUnmatched | reason=Unknown | pattern=Whether the care team is currently active | resource=proposed | active | suspended | inactive | entered-in-error
- definitionUnmatched | reason=Unknown | pattern=Whether this care team record is in active use. | resource=Indicates the current state of the care team.
Participant.name → CareTeam.name
- shortUnmatched | reason=Unknown | pattern=A name for the care team | resource=Name of the team, such as crisis assessment team
- definitionUnmatched | reason=Unknown | pattern=Description of the care team as presented to a consumer while searching. | resource=A label for human use intended to distinguish like teams. E.g. the "red" vs. "green" trauma teams.

CareTeam

Introduction

Scope and Usage

Boundaries and Relationships

Background and Context

Notes

Notes

StructureDefinition

Elements (Simplified)