Release 5 Draft Ballot
Clinical SummaryThis page is part of the FHIR Specification (v4.6.0: R5 Draft Ballot - see ballot notes). 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
| Patient Care Work Group | Maturity Level: 2 | Trial Use | Security Category: Patient | Compartments: Patient, Practitioner, RelatedPerson |
The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care.
The CareTeam includes all the people and organizations who plan to participate in the coordination and delivery of care and is assigned to:
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, 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 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.
This resource is referenced by ActivityDefinition, AdverseEvent, CarePlan, itself, ChargeItem, Communication, CommunicationRequest, ConditionDefinition, Consent, Contract, DeviceRequest, DiagnosticReport, DocumentReference, EpisodeOfCare, Goal, ImagingStudy, MedicationDispense, MedicationRequest, NutritionIntake, Observation, PlanDefinition, Procedure, RequestGroup, ServiceRequest, SupplyRequest and Task.
This resource implements the Participant pattern.
Structure
| Name | Flags | Card. | Type | Description & Constraints |
|---|---|---|---|---|
  CareTeam | TU | DomainResource | Planned participants in the coordination and delivery of care 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 |
| 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 + Warning: CareTeam.participant.role or CareTeam.participant.member exists |
 role | Σ | 0..1 | 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 |
  coverage[x] | 0..1 | When the member is generally available within this care team | ||
 coveragePeriod | Period | |||
 coverageTiming | Timing | |||
| reason | 0..* | CodeableReference(Condition) | Why the care team exists SNOMED CT Clinical Findings (Example) | |
| 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> <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(CareTeam|Organization|Patient|Practitioner| PractitionerRole|RelatedPerson) Who is involved --></member> <onBehalfOf><!-- 0..1 Reference(Organization) Organization of the practitioner --></onBehalfOf> <coverage[x]><!-- 0..1 Period|Timing When the member is generally available within this care team --></coverage[x]> </participant> <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
{
"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" : [{ // 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
// coverage[x]: When the member is generally available within this care team. One of these 2:
"coveragePeriod" : { Period }
"coverageTiming" : { Timing }
}],
"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/> .
Changes since R3
| CareTeam | |
| CareTeam.status |
|
| CareTeam.participant.role |
|
| CareTeam.participant.coverage[x] |
|
| CareTeam.reason |
|
| CareTeam.encounter |
|
| CareTeam.participant.period |
|
| CareTeam.reasonCode |
|
| CareTeam.reasonReference |
|
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 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 |
| 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 + Warning: CareTeam.participant.role or CareTeam.participant.member exists |
| role | Σ | 0..1 | 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 |
| coverage[x] | 0..1 | When the member is generally available within this care team | ||
| coveragePeriod | Period | |||
| coverageTiming | Timing | |||
| reason | 0..* | CodeableReference(Condition) | Why the care team exists SNOMED CT Clinical Findings (Example) | |
| 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">
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
"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
// coverage[x]: When the member is generally available within this care team. One of these 2:
"coveragePeriod" : { Period }
"coverageTiming" : { Timing }
}],
"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/> .
Changes since Release 3
| CareTeam | |
| CareTeam.status |
|
| CareTeam.participant.role |
|
| CareTeam.participant.coverage[x] |
|
| CareTeam.reason |
|
| CareTeam.encounter |
|
| CareTeam.participant.period |
|
| CareTeam.reasonCode |
|
| CareTeam.reasonReference |
|
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 spreadsheet version & the dependency analysis a
| Path | Definition | Type | Reference |
|---|---|---|---|
| CareTeam.status | Required | CareTeamStatus | |
| CareTeam.category | Example | CareTeamCategory | |
| CareTeam.participant.role | Example | ParticipantRoles | |
| CareTeam.reason | 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() is Practitioner) |
| ctm-2 | Warning | CareTeam.participant | CareTeam.participant.role or CareTeam.participant.member exists | 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. 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 | A date within the coverage time period. | ||
| identifier | token | External Ids for this team | CareTeam.identifier | |
| name N | string | Name of the team, such as crisis assessment team | CareTeam.name | CareTeam.extension('http://hl7.org/fhir/StructureDefinition/careteam-alias') | |
| 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 N | token | proposed | active | suspended | inactive | entered-in-error | CareTeam.status | |
| subject | reference | Who care team is for | CareTeam.subject (Group, Patient) |
FHIR ®© HL7.org 2011+. FHIR R5 Draft Ballot hl7.fhir.core#4.6.0 generated on Thu, Apr 15, 2021 12:28+1000.
Links: Search |
Version History |
Table of Contents |
QA Page |
Compare to R4 |
|
Propose a change