National Directory of Healthcare Providers & Services (NDH) Implementation Guide, published by HL7 International / Patient Administration. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-us-ndh/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.org/fhir/us/ndh/StructureDefinition/ndh-CareTeam | Version: 1.0.0 | |||
Standards status: Trial-use | Computable Name: NdhCareTeam | |||
Copyright/Legal: HL7 International |
Defines the basic constraints and extensions on the CareTeam resource for use in a National Directory of Healthcare Providers & Service (NDH)
A care team consists of the providers and/or organizations responsible for effectively delivering coordinated care. Care teams are conventionally associated with a specific patient. For example, a patient with diabetes may have a care team that consists of a physician, nurse, dietitian, certified diabetes educator, etc. Data about patients/caregivers, however, is out of scope for the National Directory of Healthcare Providers & Services (NDH). Therefore, this care team profile constrains out elements which reference or describe patient-level data. In general, the NDH is more likely to represent administrative teams, or teams that are relevant beyond the direct clinical care of specific patients.
Individuals participating on the NDH CareTeam SHALL be represented through an associated role. Therefore, this profile removes references to the Practitioner resource in CareTeam.participant.member. For example, Dr. Smith (an individual) does not participate on a care team. Rather, Dr. Smith in his role as a provider at Acme Hospital participates on a care team.
A care team may be functionally “empty,” i.e., the roles on the care team are not filled by individuals. For example, a care team may be comprised of a primary care provider role, care coordinator role, and specialist role without indicating the individuals filling those roles (i.e., by referencing a PractitionerRole resource that does not reference a Practitioner resource). This enables entities to describe existing care teams while masking the identity of the individuals/organizations that are involved, or to represent standing care teams that are filled by individuals on an ad hoc basis in response to a condition/event.
For all reasons above, this IG is using CareTeam Base profile, instead of US Core CareTeam profile. See variance Request ticket
Usage:
Description of Profiles, Differentials, Snapshots and how the different presentations work.
Other representations of profile: CSV, Excel, Schematron
SearchParameter Name | Type | Example |
---|---|---|
endpoint | reference | GET [base]/CareTeam?endpoint.indentifier=1234567 |
location | reference | GET [base]/CareTeam?location.addr-state=MD |
name | string | GET [base]/CareTeame?name=VA-Oncology |
organization | reference | GET [base]/CareTeam?organization.name=Hartford General Hospital |
service | reference | GET [base]/CareTeame?service.active=true |
verification-status | token | GET [base]/CareTeame?verification-status=complete |
Since there is no direct individual url for each Search Parameter defined by FHIR Serach Parameter Registry, we have provided the following links for you to access more information about them.
SearchParameter Name | Type | Example |
---|---|---|
category | token | GET [base]/CareTeam?category=behav |
identifier | token | GET [base]/CareTeam?identifier=http://hl7.org/fhir/R4/v2/0203/index.html|SB |
participant | reference | GET [base]/CareTeam?participant.name=Hamilton Clinic |
status | token | GET [base]/CareTeam?status=active |
_include | Example |
---|---|
CareTeam:location | GET [base]/CareTeam?_include=CareTeam:location |
CareTeam:organization | GET [base]/CareTeam?_include=CareTeam:organization |
CareTeam:participant | GET [base]/CareTeam?_include=&CareTeam:participant |
_revinclude | Example |
---|---|
VerifcationResult:target | GET [base]/CareTeam?_revinclude=VerifcationResult:target.type=CareTeam |
The search parameters outlined above are straightforward for basic scenarios but have limitations in handling complex combination queries. To enhance these capabilities, employing the special search parameters _filter is recommended.