This page is part of the FHIR Specification v4.3.0-snapshot1: R4B Snapshot to support the Jan 2022 Connectathon. About the R4B version of FHIR. The current officially released version is 4.3.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3
Patient Care Work Group | Maturity Level: 2 | Trial Use | Security 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.
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.
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, itself, ChargeItem, Communication, CommunicationRequest, Consent, Contract, DeviceRequest, DiagnosticReport, EpisodeOfCare, ImagingStudy, Media, MedicationRequest, Observation, ServiceRequest and Task.
This resource does not implement any patterns.
Structure
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
CareTeam | TU | 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 (Required) |
category | Σ | 0..* | CodeableConcept | Type of team Care Team category (Example) |
name | Σ | 0..1 | string | Name of the team, such as crisis assessment team |
subject | Σ | 0..1 | Reference(Patient | Group) | Who care team is for |
encounter | Σ | 0..1 | Reference(Encounter) | Encounter created as part of |
period | Σ | 0..1 | Period | Time period team covers |
participant | I | 0..* | BackboneElement | Members of the team + Rule: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner |
role | Σ | 0..* | CodeableConcept | Type of involvement Participant Roles (Example) |
member | Σ | 0..1 | Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam) | Who is involved |
onBehalfOf | Σ | 0..1 | Reference(Organization) | Organization of the practitioner |
period | 0..1 | Period | Time period of participant | |
reasonCode | 0..* | CodeableConcept | Why 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..* | ContactPoint | A contact detail for the care team (that applies to all members) | |
note | 0..* | Annotation | Comments made about the CareTeam | |
Documentation for this format |
UML Diagram (Legend)
XML Template
<CareTeam xmlns="http://hl7.org/fhir"> <!-- 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>
JSON Template
{ "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 "encounter" : { Reference(Encounter) }, // Encounter created as part of "period" : { Period }, // Time period team covers "participant" : [{ // C? Members of the team "role" : [{ CodeableConcept }], // Type of involvement "member" : { Reference(CareTeam|Organization|Patient|Practitioner| PractitionerRole|RelatedPerson) }, // Who is involved "onBehalfOf" : { Reference(Organization) }, // Organization of the practitioner "period" : { Period } // Time period of participant }], "reasonCode" : [{ CodeableConcept }], // Why the care team exists "reasonReference" : [{ Reference(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/> . [ 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 R3
CareTeam | |
CareTeam.status |
|
See the Full Difference for further information
This analysis is available as XML or JSON.
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
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
CareTeam | TU | 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 (Required) |
category | Σ | 0..* | CodeableConcept | Type of team Care Team category (Example) |
name | Σ | 0..1 | string | Name of the team, such as crisis assessment team |
subject | Σ | 0..1 | Reference(Patient | Group) | Who care team is for |
encounter | Σ | 0..1 | Reference(Encounter) | Encounter created as part of |
period | Σ | 0..1 | Period | Time period team covers |
participant | I | 0..* | BackboneElement | Members of the team + Rule: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner |
role | Σ | 0..* | CodeableConcept | Type of involvement Participant Roles (Example) |
member | Σ | 0..1 | Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam) | Who is involved |
onBehalfOf | Σ | 0..1 | Reference(Organization) | Organization of the practitioner |
period | 0..1 | Period | Time period of participant | |
reasonCode | 0..* | CodeableConcept | Why 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..* | ContactPoint | A contact detail for the care team (that applies to all members) | |
note | 0..* | Annotation | Comments made about the CareTeam | |
Documentation for this format |
XML Template
<CareTeam xmlns="http://hl7.org/fhir"> <!-- 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>
JSON Template
{ "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 "encounter" : { Reference(Encounter) }, // Encounter created as part of "period" : { Period }, // Time period team covers "participant" : [{ // C? Members of the team "role" : [{ CodeableConcept }], // Type of involvement "member" : { Reference(CareTeam|Organization|Patient|Practitioner| PractitionerRole|RelatedPerson) }, // Who is involved "onBehalfOf" : { Reference(Organization) }, // Organization of the practitioner "period" : { Period } // Time period of participant }], "reasonCode" : [{ CodeableConcept }], // Why the care team exists "reasonReference" : [{ Reference(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/> . [ 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 3
CareTeam | |
CareTeam.status |
|
See the Full Difference for further information
This analysis is available as XML or JSON.
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
Path | Definition | Type | Reference |
---|---|---|---|
CareTeam.status | Required | CareTeamStatus | |
CareTeam.category | Example | CareTeamCategory | |
CareTeam.participant.role | Example | ParticipantRoles | |
CareTeam.reasonCode | Example | SNOMEDCTClinicalFindings |
id | Level | Location | Description | Expression |
ctm-1 | Rule | CareTeam.participant | CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner | onBehalfOf.exists() implies (member.resolve().iif(empty(), true, ofType(Practitioner).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. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.
Name | Type | Description | Expression | In Common |
category | token | Type of team | CareTeam.category | |
date | date | Time period team covers | CareTeam.period | |
encounter | reference | Encounter created as part of | CareTeam.encounter (Encounter) | |
identifier | token | External Ids for this team | CareTeam.identifier | |
participant | reference | Who is involved | CareTeam.participant.member (Practitioner, Organization, CareTeam, Patient, PractitionerRole, RelatedPerson) | |
patient | reference | Who care team is for | CareTeam.subject.where(resolve() is Patient) (Group, Patient) | |
status | token | proposed | active | suspended | inactive | entered-in-error | CareTeam.status | |
subject | reference | Who care team is for | CareTeam.subject (Group, Patient) |