US Core Implementation Guide
9.0.0 - STU 9 US

US Core Implementation Guide - Downloaded Version 9.0.0 See the Directory of published versions

## Resource Profile: US Core CareTeam Profile

Official URL: http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam | Version: 9.0.0
Standards status: Trial-use | Maturity Level: 5 | Computable Name: USCoreCareTeam
Other Identifiers: OID:2.16.840.1.113883.4.642.40.2.42.16

The US Core CareTeam Profile inherits from the FHIR CareTeam resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the CareTeam resource for identifying the Care Team members associated with a patient to promote interoperability and adoption through common implementation. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption.

Example Usage Scenarios:

The following are example usage scenarios for this profile:

- Query for a Patient's CareTeam
- Record or update a Patient's CareTeam

### Mandatory and Must Support Data Elements

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 Views below provides the formal summary, definitions, and terminology requirements.

Each CareTeam Must Have:

1. a patient
2. a participant role for each careteam member
3. a reference to each careteam member, which can be:
   - a practitioner or practitioner type (doctor, nurse, therapist)1
   - a relative, friend, or guardian

1See below for how practitioner members are represented in this Profile.

Each CareTeam Must Support:

1. a status code

### Profile Specific Implementation Guidance

This section provides detailed implementation guidance for the US Core Profile to support implementation and certification.

In order to access care team member's names, identifiers, locations, and contact information, the CareTeam profile supports several types of care team participants. They are represented as references to other profiles and include the following three profiles, which are marked as Must Support:

1. US Core Practitioner Profile
2. US Core PractitionerRole Profile
3. US Core RelatedPerson Profile

- Although both US Core Practitioner Profile and US Core PractitionerRole are Must Support, the Server system is not required to support references to both, but SHALL support at least one of them.§
- The Client application SHALL support all three profile references.§,§,§
- Because the US Core PractitionerRole Profile supplies the provider's location and contact information and a reference to the Practitioner, Server systems SHOULD reference it instead of the US Core Practitioner Profile. The quick start section below shows an example of how to access the practitioner name and identifier.§
- Servers that support only US Core Practitioner Profile and do not support the US Core PractitionerRole Profile SHALL provide implementation-specific guidance on how to access a provider's location and contact information using only the Practitioner resource.§,§

Usages:

- Refer to this Profile: US Core Average Blood Pressure Profile, US Core Care Experience Preference Profile, US Core CarePlan Profile, US Core CareTeam Profile... Show 12 more, US Core DiagnosticReport Profile for Laboratory Results Reporting, US Core DiagnosticReport Profile for Report and Note Exchange, US Core Observation ADI Documentation Profile, US Core Observation Clinical Result Profile, US Core Observation Occupation Profile, US Core Observation Pregnancy Intent Profile, US Core Observation Pregnancy Status Profile, US Core Observation Screening Assessment Profile, US Core Simple Observation Profile, US Core Smoking Status Observation Profile, US Core Treatment Intervention Preference Profile and US Core Vital Signs Profile
- Examples for this Profile: US-Core example CareTeam and US-Core example CareTeam
- CapabilityStatements using this Profile: US Core Client CapabilityStatement and US Core Server CapabilityStatement

You can also check for usages in the FHIR IG Statistics

Changes since version 8.0.1:

- The resource metadata has changed (copyright)
- One or more text definitions, invariants or bindings have changed

### Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

- Key Elements Table
- Differential Table
- Snapshot Table
- Statistics/References
- All

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
CareTeam |  | 0..* | CareTeam | Planned participants in the coordination and delivery of care for a patient or group
implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created
modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored
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 S | Group) | Who care team is for
participant | S C | 1..* | BackboneElement | Members of the team Constraints: ctm-1
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 S | US Core CareTeam Profile | US Core RelatedPerson Profile S) | Who is involved
Documentation for this format

#### Terminology Bindings

Path | Status | Usage | ValueSet | Version | Source
CareTeam.status | Base | required | CareTeamStatus | 📦4.0.1 | FHIR Std.
CareTeam.participant.​role | Base | extensible | Care Team Member Function | ⏿20240605 | tx.fhir.org

#### Constraints

Id | Grade | Path(s) | Description | Expression
ctm-1 | error | 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()))`
dom-2 | error | CareTeam | If the resource is contained in another resource, it SHALL NOT contain nested Resources | `contained.contained.empty()`
dom-3 | error | CareTeam | If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource | `contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()`
dom-4 | error | CareTeam | If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated | `contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()`
dom-5 | error | CareTeam | If a resource is contained in another resource, it SHALL NOT have a security label | `contained.meta.security.empty()`
dom-6 | best practice | CareTeam | A resource should have narrative for robust management | `text.`div`.exists()`
ele-1 | error | **ALL** elements | All FHIR elements must have a @value or children | `hasValue() or (children().count() > id.count())`
ext-1 | error | **ALL** extensions | Must have either extensions or value[x], not both | `extension.exists() != value.exists()`

This structure is derived from CareTeam

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
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 S | Group) | 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 S | US Core CareTeam Profile | US Core RelatedPerson Profile S) | Who is involved
Documentation for this format

#### Terminology Bindings (Differential)

Path | Status | Usage | ValueSet | Version | Source
CareTeam.status | Base | required | CareTeamStatus | 📦4.0.1 | FHIR Std.
CareTeam.participant.​role | Base | extensible | Care Team Member Function | ⏿20240605 | tx.fhir.org

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
CareTeam |  | 0..* | CareTeam | Planned participants in the coordination and delivery of care for a patient or group
id | Σ | 0..1 | id | 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): A human language.
Additional Bindings | Purpose
AllLanguages | Max Binding
text |  | 0..1 | Narrative | Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements
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 S | 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 | S C | 1..* | BackboneElement | Members of the team Constraints: ctm-1
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 S | US Core CareTeam Profile | US Core RelatedPerson Profile S) | 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

#### Terminology Bindings

Path | Status | Usage | ValueSet | Version | Source
CareTeam.language | Base | preferred | Common Languages | 📍4.0.1 | FHIR Std.
CareTeam.status | Base | required | CareTeamStatus | 📦4.0.1 | FHIR Std.
CareTeam.category | Base | example | Care Team category | 📍4.0.1 | FHIR Std.
CareTeam.participant.​role | Base | extensible | Care Team Member Function | ⏿20240605 | tx.fhir.org
CareTeam.reasonCode | Base | example | SNOMED CT Clinical Findings | 📍4.0.1 | FHIR Std.

#### Constraints

Id | Grade | Path(s) | Description | Expression
ctm-1 | error | 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()))`
dom-2 | error | CareTeam | If the resource is contained in another resource, it SHALL NOT contain nested Resources | `contained.contained.empty()`
dom-3 | error | CareTeam | If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource | `contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()`
dom-4 | error | CareTeam | If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated | `contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()`
dom-5 | error | CareTeam | If a resource is contained in another resource, it SHALL NOT have a security label | `contained.meta.security.empty()`
dom-6 | best practice | CareTeam | A resource should have narrative for robust management | `text.`div`.exists()`
ele-1 | error | **ALL** elements | All FHIR elements must have a @value or children | `hasValue() or (children().count() > id.count())`
ext-1 | error | **ALL** extensions | Must have either extensions or value[x], not both | `extension.exists() != value.exists()`

This structure is derived from CareTeam

Summary

Mandatory: 4 elements
Must-Support: 5 elements

Structures

This structure refers to these other structures:

- US Core Patient Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient)
- US Core Practitioner Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner)
- US Core Organization Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization)
- US Core PractitionerRole Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole)
- US Core CareTeam Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam)
- US Core RelatedPerson Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-relatedperson)

Maturity: 5

Key Elements View

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
CareTeam |  | 0..* | CareTeam | Planned participants in the coordination and delivery of care for a patient or group
implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created
modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored
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 S | Group) | Who care team is for
participant | S C | 1..* | BackboneElement | Members of the team Constraints: ctm-1
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 S | US Core CareTeam Profile | US Core RelatedPerson Profile S) | Who is involved
Documentation for this format

#### Terminology Bindings

Path | Status | Usage | ValueSet | Version | Source
CareTeam.status | Base | required | CareTeamStatus | 📦4.0.1 | FHIR Std.
CareTeam.participant.​role | Base | extensible | Care Team Member Function | ⏿20240605 | tx.fhir.org

#### Constraints

Id | Grade | Path(s) | Description | Expression
ctm-1 | error | 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()))`
dom-2 | error | CareTeam | If the resource is contained in another resource, it SHALL NOT contain nested Resources | `contained.contained.empty()`
dom-3 | error | CareTeam | If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource | `contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()`
dom-4 | error | CareTeam | If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated | `contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()`
dom-5 | error | CareTeam | If a resource is contained in another resource, it SHALL NOT have a security label | `contained.meta.security.empty()`
dom-6 | best practice | CareTeam | A resource should have narrative for robust management | `text.`div`.exists()`
ele-1 | error | **ALL** elements | All FHIR elements must have a @value or children | `hasValue() or (children().count() > id.count())`
ext-1 | error | **ALL** extensions | Must have either extensions or value[x], not both | `extension.exists() != value.exists()`

Differential View

This structure is derived from CareTeam

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
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 S | Group) | 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 S | US Core CareTeam Profile | US Core RelatedPerson Profile S) | Who is involved
Documentation for this format

#### Terminology Bindings (Differential)

Path | Status | Usage | ValueSet | Version | Source
CareTeam.status | Base | required | CareTeamStatus | 📦4.0.1 | FHIR Std.
CareTeam.participant.​role | Base | extensible | Care Team Member Function | ⏿20240605 | tx.fhir.org

Snapshot View

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
CareTeam |  | 0..* | CareTeam | Planned participants in the coordination and delivery of care for a patient or group
id | Σ | 0..1 | id | 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): A human language.
Additional Bindings | Purpose
AllLanguages | Max Binding
text |  | 0..1 | Narrative | Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements
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 S | 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 | S C | 1..* | BackboneElement | Members of the team Constraints: ctm-1
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 S | US Core CareTeam Profile | US Core RelatedPerson Profile S) | 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

#### Terminology Bindings

Path | Status | Usage | ValueSet | Version | Source
CareTeam.language | Base | preferred | Common Languages | 📍4.0.1 | FHIR Std.
CareTeam.status | Base | required | CareTeamStatus | 📦4.0.1 | FHIR Std.
CareTeam.category | Base | example | Care Team category | 📍4.0.1 | FHIR Std.
CareTeam.participant.​role | Base | extensible | Care Team Member Function | ⏿20240605 | tx.fhir.org
CareTeam.reasonCode | Base | example | SNOMED CT Clinical Findings | 📍4.0.1 | FHIR Std.

#### Constraints

Id | Grade | Path(s) | Description | Expression
ctm-1 | error | 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()))`
dom-2 | error | CareTeam | If the resource is contained in another resource, it SHALL NOT contain nested Resources | `contained.contained.empty()`
dom-3 | error | CareTeam | If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource | `contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()`
dom-4 | error | CareTeam | If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated | `contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()`
dom-5 | error | CareTeam | If a resource is contained in another resource, it SHALL NOT have a security label | `contained.meta.security.empty()`
dom-6 | best practice | CareTeam | A resource should have narrative for robust management | `text.`div`.exists()`
ele-1 | error | **ALL** elements | All FHIR elements must have a @value or children | `hasValue() or (children().count() > id.count())`
ext-1 | error | **ALL** extensions | Must have either extensions or value[x], not both | `extension.exists() != value.exists()`

This structure is derived from CareTeam

Summary

Mandatory: 4 elements
Must-Support: 5 elements

Structures

This structure refers to these other structures:

- US Core Patient Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient)
- US Core Practitioner Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner)
- US Core Organization Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization)
- US Core PractitionerRole Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole)
- US Core CareTeam Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam)
- US Core RelatedPerson Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-relatedperson)

Maturity: 5

Other representations of profile: CSV, Excel, Schematron

### Notes:

Quick Start

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.

- See the Scopes Format section for a description of the SMART scopes syntax.
- See the Search Syntax section for a description of the US Core search syntax.
- See the General Requirements section for additional rules and expectations when a Server requires status parameters.
- See the General Guidance section for additional guidance on searching for multiple patients.

#### US Core Scopes

Servers providing access to careteam data SHALL support these US Core SMART Scopes:

- resource level scopes: `<patient|user|system>/CareTeam.rs` §

#### Mandatory Search Parameters:

The following search parameters and search parameter combinations SHALL be supported:

1. SHALL support searching using the combination of the patient and status search parameters

   - Including optional support for these `_include` parameters: `CareTeam:participant:PractitionerRole`, `CareTeam:participant:Practitioner`, `CareTeam:participant:Patient`, `CareTeam:participant:RelatedPerson`
   - Including optional support OR search on `status` (e.g.`status={system|}[code],{system|}[code],...`)

   `GET [base]/CareTeam?patient={Patient/}[id]&status={system|}[search_code]{,{system|}[code],...}`

   Examples:

   > 1. GET [base]/CareTeam?patient=Patient/1137192&status=active

   > 2. GET [base]/CareTeam?patient=Patient/1137192&status=active&_include=CareTeam:participant:RelatedPerson&_include=CareTeam:participant:Patient&_include=CareTeam:participant:Practitioner&_include=CareTeam:participant:PractitionerRole

   Implementation Notes: Fetches a bundle of all resources for the specified patient and status ="active" and may include Patient, RelatedPerson and Practitioner and PractitionerRole participants. To get Practitioner name and identifier using PractitionerRole: 1) Search for the careteam PractitionerRole: GET [base]/status=active&_include=:participant:PractitionerRole 2) using the FHIR _id from the PractitionerRole.practitioner element resource, fetch the Practitioner resources using GET [base]/Practitioner?_id=[id] ( see how to search by reference and how to search by token).

#### Optional Search Parameters:

The following search parameters and search parameter combinations SHOULD be supported

1. SHOULD support searching a careteam by participant role using the role search parameter
   - Including optional support OR search on `role` (e.g.`role={system|}[code],{system|}[code],...`)

   `GET [base]/CareTeam?role={system|}[search_code]{,{system|}[code],...}`

   Example:

   > 1. GET [base]/CareTeam?role=http://snomed.info/sct|17561000

   Implementation Notes: Fetches a bundle of all resources for the specified role ( see how to search by token).

2. SHOULD support searching using the combination of the patient and role search parameters

   - Including optional support for these `_include` parameters: `CareTeam:participant:PractitionerRole`, `CareTeam:participant:Practitioner`, `CareTeam:participant:Patient`, `CareTeam:participant:RelatedPerson`
   - Including optional support OR search on `role` (e.g.`role={system|}[code],{system|}[code],...`)

   `GET [base]/CareTeam?patient={Patient/}[id]&role={system|}[search_code]{,{system|}[code],...}`

   Example:

   > 1. GET [base]/CareTeam?patient=Patient/1137192&role=http://snomed.info/sct|17561000

   Implementation Notes: Fetches a bundle of all resources for the specified patient and participant role ( see how to search by reference and how to search by token).