Validated Healthcare Directory IG STU1 Draft for Comment

This page is part of the Validated Healthcare Directory FHIR IG (v0.1.0: STU 1 Draft) based on FHIR v3.2.0. . For a full list of available versions, see the Directory of published versions

1.0 - StructureDefinition: vhdir-careteam - Content

This profile sets minimum expectations for searching for and fetching information associated with a care team. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the CareTeam resource when using this profile.

Background & Scope

A care team consists of the providers and/or organizations responsible for the care of a patient. It is defined not as a collection of individuals and organizations, but as a collection of roles; each member of a care team is represented through an associated role. Therefore, this profile removes references to practitioner and organization resources in careTeam.member and adds references to practitionerRole and organizationRole. 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 or organizations. For example, a care team may be comprised of a primary care provider, care coordinator, and specialist without indicating the individuals filling those roles. This enables entities to describe existing care teams while masking the identity of the indivudals/organizations that are involved, or to represent standing care teams that are filled on an ad hoc basis in response to a condition/event.

This profile removes careTeam.subject, careTeam.context, careTeam.reasonReference, and references to patient and relatedPerson resources in careTeam.member because maintaining patient information is out of scope for this implementation guide. It also constrains the number of organizations responsible for managing a care team to one.

Examples:

The following are example uses for the vhdir-careteam profile:

  • TBD

Mandatory Data Elements

The following data-elements are mandatory (i.e data MUST be present). These are presented below in a simple human-readable explanation. The Formal Profile Definition below provides the formal summary, definitions, and terminology requirements.

Each CareTeam must have:

  1. At least one type of care team in careTeam.category
  2. A period for which the care team is active in careTeam.period

Profile specific implementation guidance:

  • TBD

Extensions:

  1. Restriction (0..*) - indicates restrictions on the use/release of information associated with the care team
  2. Alias (0..*) - indicates alternate names by which the care team is known
  3. Location (0..*) - reference(s) to the location resource, indicating the location(s) at which the care team operates or delivers services
  4. Service (0..*) - reference(s) to the healthcareService resource, indicating the services offered by the care team
  5. Endpoint (0..*) - reference(s) to the endpoint resource, indicating technical endpoints for the care team independent of its members, affiliated organizations, etc.
  6. Mode (0..1) - indicates whether the care team is an instance or kind of care team

Terminology

TBD

1.2 - Formal Views of Profile Content

The official URL for this profile is: 

http://hl7.org/fhir/ig/vhdir/StructureDefinition/vhdir-careteam

This profile builds on CareTeam.

This profile was published on Wed Oct 18 05:22:04 AEDT 2017 as a draft by null.

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

Complete Summary of the Mandatory Requirements

  1. At least one type of care team in careTeam.category
  2. A period for which the care team is active in careTeam.period
NameFlagsCard.TypeDescription & Constraintsdoco
.. CareTeam I0..*Planned participants in the coordination and delivery of care for a patient or group
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: Common Languages (extensible)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierExternal Ids for this team
... status ?!Σ0..1codeproposed | active | suspended | inactive | entered-in-error
Binding: CareTeamStatus (required)
... category Σ0..*CodeableConceptType of team
Binding: CareTeamCategory (example)
... name Σ0..1stringName of the team, such as crisis assessment team
... context Σ0..1Reference(Encounter), Reference(EpisodeOfCare)Encounter or episode associated with CareTeam
... period Σ0..1PeriodTime period team covers
... participant I0..*BackboneElementMembers of the team
ctm-1: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner
.... id 0..1stringxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... role Σ0..1CodeableConceptType of involvement
Binding: Participant Roles (example)
.... member Σ0..1Reference(Practitioner), Reference(RelatedPerson), Reference(Patient), Reference(Organization), Reference(CareTeam)Who is involved
.... onBehalfOf Σ0..1Reference(Organization)Organization of the practitioner
.... period 0..1PeriodTime period of participant
... reasonCode 0..*CodeableConceptWhy the care team exists
Binding: 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..*ContactPointA contact detail for the care team (that applies to all members)
... note 0..*AnnotationComments made about the CareTeam

doco Documentation for this format

Complete Summary of the Mandatory Requirements

  1. At least one type of care team in careTeam.category
  2. A period for which the care team is active in careTeam.period

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. CareTeam I0..*Planned participants in the coordination and delivery of care for a patient or group
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: Common Languages (extensible)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierExternal Ids for this team
... status ?!Σ0..1codeproposed | active | suspended | inactive | entered-in-error
Binding: CareTeamStatus (required)
... category Σ0..*CodeableConceptType of team
Binding: CareTeamCategory (example)
... name Σ0..1stringName of the team, such as crisis assessment team
... context Σ0..1Reference(Encounter), Reference(EpisodeOfCare)Encounter or episode associated with CareTeam
... period Σ0..1PeriodTime period team covers
... participant I0..*BackboneElementMembers of the team
ctm-1: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner
.... id 0..1stringxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... role Σ0..1CodeableConceptType of involvement
Binding: Participant Roles (example)
.... member Σ0..1Reference(Practitioner), Reference(RelatedPerson), Reference(Patient), Reference(Organization), Reference(CareTeam)Who is involved
.... onBehalfOf Σ0..1Reference(Organization)Organization of the practitioner
.... period 0..1PeriodTime period of participant
... reasonCode 0..*CodeableConceptWhy the care team exists
Binding: 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..*ContactPointA contact detail for the care team (that applies to all members)
... note 0..*AnnotationComments made about the CareTeam

doco Documentation for this format

Downloads: StructureDefinition: (XML, JSON, CSV), Schema: XML Schematron

 

1.3 - Quick Start

Below is an overview of the required search and read operations for this profile. See the Conformance requirements for the US Core Server for a complete list of supported RESTful operations and search parameters for this IG.

TBD