This page is part of the US Core (v4.0.0: STU4) based on FHIR R4. The current version which supercedes this version is 5.0.1. For a full list of available versions, see the Directory of published versions
Defining URL: | http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam |
Version: | 4.0.0 |
Name: | USCoreCareTeam |
Title: | US Core CareTeam Profile |
Status: | Active as of 2020-06-26 |
Definition: | Defines constraints and extensions on the CareTeam resource for the minimal set of data to query and retrieve a patient's Care Team. |
Publisher: | HL7 International - US Realm Steering Committee |
Copyright: | Used by permission of HL7 International, all rights reserved Creative Commons License |
Source Resource: | XML / JSON / Turtle |
The official URL for this profile is:
http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam
This profile sets minimum expectations for the CareTeam resource for identifying the Care Team members associated with a patient. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile.
Example Usage Scenarios:
The following are example usage scenarios for the US Core-CareTeam profile:
The following data-elements must always be present (Mandatory definition]) or must be supported if the data is present in the sending system (Must Support definition). They are presented below in a simple human-readable explanation. Profile specific guidance and examples are provided as well. The Formal Profile Definition below provides the formal summary, definitions, and terminology requirements.
Each CareTeam must have:
Each Condition must support:
Profile specific implementation guidance:
Description of Profiles, Differentials, Snapshots and how the different presentations work.
This structure is derived from CareTeam
Summary
Mandatory: 4 elements
Must-Support: 5 elements
Structures
This structure refers to these other structures:
This structure is derived from CareTeam
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
CareTeam | 0..* | CareTeam | Planned participants in the coordination and delivery of care for a patient or group | |
status | S | 0..1 | code | proposed | active | suspended | inactive | entered-in-error Binding: CareTeamStatus (required): Indicates whether the team is current , represents future intentions or is now a historical record. |
subject | S | 1..1 | Reference(US Core Patient Profile) | Who care team is for |
participant | S | 1..* | BackboneElement | Members of the team |
role | S | 1..1 | CodeableConcept | Type of involvement Binding: Care Team Member Function (extensible): Indicates specific responsibility of an individual within the care team, such as Primary physician, Team coordinator, Caregiver, etc. |
member | S | 1..1 | Reference(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | US Core PractitionerRole Profile | US Core CareTeam Profile | RelatedPerson) | Who is involved |
Documentation for this format |
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
CareTeam | 0..* | CareTeam | Planned participants in the coordination and delivery of care for a patient or group | |
id | Σ | 0..1 | string | Logical id of this artifact |
meta | Σ | 0..1 | Meta | Metadata about the resource |
implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created |
language | 0..1 | code | Language of the resource content Binding: CommonLanguages (preferred) Max Binding: AllLanguages: A human language. | |
text | 0..1 | Narrative | Text summary of the resource, for human interpretation | |
contained | 0..* | Resource | Contained, inline Resources | |
extension | 0..* | Extension | Additional content defined by implementations | |
modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored |
identifier | Σ | 0..* | Identifier | External Ids for this team |
status | ?!SΣ | 0..1 | code | proposed | active | suspended | inactive | entered-in-error Binding: CareTeamStatus (required): Indicates whether the team is current , represents future intentions or is now a historical record. |
category | Σ | 0..* | CodeableConcept | Type of team Binding: CareTeamCategory (example): Indicates the type of care team. |
name | Σ | 0..1 | string | Name of the team, such as crisis assessment team |
subject | SΣ | 1..1 | Reference(US Core Patient Profile) | Who care team is for |
encounter | Σ | 0..1 | Reference(Encounter) | Encounter created as part of |
period | Σ | 0..1 | Period | Time period team covers |
participant | SI | 1..* | BackboneElement | Members of the team |
id | 0..1 | string | Unique id for inter-element referencing | |
extension | 0..* | Extension | Additional content defined by implementations | |
modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized |
role | SΣ | 1..1 | CodeableConcept | Type of involvement Binding: Care Team Member Function (extensible): Indicates specific responsibility of an individual within the care team, such as Primary physician, Team coordinator, Caregiver, etc. |
member | SΣ | 1..1 | Reference(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | US Core PractitionerRole Profile | US Core CareTeam Profile | RelatedPerson) | 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 Binding: SNOMEDCTClinicalFindings (example): Indicates the reason for the care team. | |
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 |
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
CareTeam | 0..* | CareTeam | Planned participants in the coordination and delivery of care for a patient or group | |
status | ?!Σ | 0..1 | code | proposed | active | suspended | inactive | entered-in-error Binding: CareTeamStatus (required): Indicates whether the team is current , represents future intentions or is now a historical record. |
subject | Σ | 1..1 | Reference(US Core Patient Profile) | Who care team is for |
participant | I | 1..* | BackboneElement | Members of the team |
role | Σ | 1..1 | CodeableConcept | Type of involvement Binding: Care Team Member Function (extensible): Indicates specific responsibility of an individual within the care team, such as Primary physician, Team coordinator, Caregiver, etc. |
member | Σ | 1..1 | Reference(US Core Practitioner Profile) | Who is involved |
Documentation for this format |
This structure is derived from CareTeam
Summary
Mandatory: 4 elements
Must-Support: 5 elements
Structures
This structure refers to these other structures:
Differential View
This structure is derived from CareTeam
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
CareTeam | 0..* | CareTeam | Planned participants in the coordination and delivery of care for a patient or group | |
status | S | 0..1 | code | proposed | active | suspended | inactive | entered-in-error Binding: CareTeamStatus (required): Indicates whether the team is current , represents future intentions or is now a historical record. |
subject | S | 1..1 | Reference(US Core Patient Profile) | Who care team is for |
participant | S | 1..* | BackboneElement | Members of the team |
role | S | 1..1 | CodeableConcept | Type of involvement Binding: Care Team Member Function (extensible): Indicates specific responsibility of an individual within the care team, such as Primary physician, Team coordinator, Caregiver, etc. |
member | S | 1..1 | Reference(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | US Core PractitionerRole Profile | US Core CareTeam Profile | RelatedPerson) | Who is involved |
Documentation for this format |
Snapshot View
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
CareTeam | 0..* | CareTeam | Planned participants in the coordination and delivery of care for a patient or group | |
id | Σ | 0..1 | string | Logical id of this artifact |
meta | Σ | 0..1 | Meta | Metadata about the resource |
implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created |
language | 0..1 | code | Language of the resource content Binding: CommonLanguages (preferred) Max Binding: AllLanguages: A human language. | |
text | 0..1 | Narrative | Text summary of the resource, for human interpretation | |
contained | 0..* | Resource | Contained, inline Resources | |
extension | 0..* | Extension | Additional content defined by implementations | |
modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored |
identifier | Σ | 0..* | Identifier | External Ids for this team |
status | ?!SΣ | 0..1 | code | proposed | active | suspended | inactive | entered-in-error Binding: CareTeamStatus (required): Indicates whether the team is current , represents future intentions or is now a historical record. |
category | Σ | 0..* | CodeableConcept | Type of team Binding: CareTeamCategory (example): Indicates the type of care team. |
name | Σ | 0..1 | string | Name of the team, such as crisis assessment team |
subject | SΣ | 1..1 | Reference(US Core Patient Profile) | Who care team is for |
encounter | Σ | 0..1 | Reference(Encounter) | Encounter created as part of |
period | Σ | 0..1 | Period | Time period team covers |
participant | SI | 1..* | BackboneElement | Members of the team |
id | 0..1 | string | Unique id for inter-element referencing | |
extension | 0..* | Extension | Additional content defined by implementations | |
modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized |
role | SΣ | 1..1 | CodeableConcept | Type of involvement Binding: Care Team Member Function (extensible): Indicates specific responsibility of an individual within the care team, such as Primary physician, Team coordinator, Caregiver, etc. |
member | SΣ | 1..1 | Reference(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | US Core PractitionerRole Profile | US Core CareTeam Profile | RelatedPerson) | 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 Binding: SNOMEDCTClinicalFindings (example): Indicates the reason for the care team. | |
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 |
Other representations of profile: CSV, Excel, Schematron
Path | Conformance | ValueSet |
CareTeam.language | preferred | CommonLanguages Max Binding: AllLanguages |
CareTeam.status | required | CareTeamStatus |
CareTeam.category | example | CareTeamCategory |
CareTeam.participant.role | extensible | Care Team Member Function |
CareTeam.reasonCode | example | SNOMEDCTClinicalFindings |
Below is an overview of the required Server RESTful FHIR interactions for this profile - for example, search and read operations - when supporting the US Core interactions to access this profile’s information (Profile Support + Interaction Support). Note that systems that support only US Core Profiles (Profile Only Support) are not required to support these interactions. See the US Core Server CapabilityStatement for a complete list of supported RESTful interactions for this IG.
The following search parameters and search parameter combinations SHALL be supported:
patient
and status
search parameters:
status
(e.g.status={system|}[code],{system|}[code],...
)GET [base]/CareTeam?patient={Type/}[id]&status=active
Example:
Implementation Notes: Fetches a bundle of all CareTeam resources for the specified patient and status =active
(how to search by reference and how to search by token)