eHealth Infrastructure
3.0.0 - release

eHealth Infrastructure - Local Development build (v3.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Resource Profile: ehealth-careteam

Official URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-careteam Version: 3.0.0
Active as of 2024-05-16 Computable Name: ehealth-careteam

Introduction

The CareTeam includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient. A CareTeam can be constructed for a single patient but typically handles more patients.

Scope and Usage

In the eHealth Infrastructure, a CareTeam has a lifecycle independent of Patients and consists of a group of Practitioners. Typically the group of Practitioners are affiliated with a real-world organizational unit such as a hospital department/care unit, but a CareTeam can also be representing a “virtual” unit comprised of
Practitioners from more sectors or several real-world organizational units.

The core FHIR CareTeam has subject and context which can reference a Patient and EpisodeOfCare, respectively, which when used ties a CareTeam to a Patient context. Similarly, use of element reasonReference would indirectly tie the CareTeam to a Patient. As this is not used in the eHealth Infrastructure and to prevent such tying, these elements have been set to 0..0.

Instead CareTeam is intended to be referenced from CarePlan and EpisodeOfCare. A CareTeam can be referenced from a single CarePlan but the typical scenario is that it is referenced by multiple CarePlan and/or EpisodeOfCare instances crossing multiple Patient instances.

Composition of CareTeams

In the eHealth Infrastructure, the possibility to add CareTeam participant members other than Practitioner is not used, but the other types (Organization, CareTeam etc) have been retained for possible future use.

There are currently no restrictions on the composition of CareTeams. The intended usage is to establish a few layers of CareTeams, but it is important to make sure that the CareTem member graph contains no cycles.

CareTeam Identifier

At least one identifier for the CareTeam shall use system set to urn:ietf:rfc:3986 and contain a value which is a UUID.

Condition types handled by the CareTeam

In order to ease selection of CareTeam appropriate for a given CarePlan, at least one Condition type handled by a CareTeam must be stated in reasonCode. This is used as criteria for suggesting CareTeams in the operation suggest-care-teams.

Usage:

Formal Views of Profile Content

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

This structure is derived from CareTeam

NameFlagsCard.TypeDescription & Constraintsdoco
.. CareTeam CareTeam
... status 1..1codeproposed | active | suspended | inactive | entered-in-error
... category 0..*CodeableConceptType of team
Binding: CareTeam Category (required)
... name 1..1stringName of the team, such as crisis assessment team
... participant
.... role 1..*CodeableConceptType of involvement
Binding: CareTeam Participant Role (required)
.... member 1..1Reference(ehealth-practitioner | ehealth-practitionerrole | ehealth-relatedperson | ehealth-patient | ehealth-organization | ehealth-careteam) {r}Who is involved
.... onBehalfOf 0..1Reference(ehealth-organization) {r}Organization of the practitioner
... reasonCode 1..*CodeableConceptWhy the care team exists
Binding: Conditions (required)
... reasonReference 0..0
... managingOrganization 0..*Reference(ehealth-organization) {r}Organization responsible for the care team
... telecom
.... value 1..1stringThe actual contact point details
... note
.... Slices for author[x] 0..1Reference(Practitioner | Patient | RelatedPerson | Organization), stringIndividual responsible for the annotation
Slice: Unordered, Open by type:$this
..... author[x]:authorReference 0..1Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson)Individual responsible for the annotation
..... author[x]:authorString 0..1stringIndividual responsible for the annotation

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
CareTeam.categoryrequiredCareTeamCategory (a valid code from CareTeam Category)
http://ehealth.sundhed.dk/vs/careteam-category
from this IG
CareTeam.participant.rolerequiredCareTeamParticipantRole (a valid code from CareTeam Participant Role)
http://ehealth.sundhed.dk/vs/careteam-participant-role
from this IG
CareTeam.reasonCoderequiredConditions
http://ehealth.sundhed.dk/vs/conditions
from this IG

 

Other representations of profile: CSV, Excel, Schematron