eHealth Infrastructure (v1.0.0)
CareTeam exist in two variants:
The intended usage is depicted here:
+---------------+
| EpisodeOfCare | ---> : "References"
+-------------+-+
^ ^ |
| | v
+--------+-+ | +---------+
| CarePlan |--+-->| Patient |
+--------+-+ | +---------+
| | ^
v | |
+-----+------+ CareTeam type 2
| CareTeam | (Patient CareTeam)
+------------+
| | | |
+---------------------+ | | +---------------------+
| | | |
| +-------+ +------+ |
v v v v
+----------+ +----------+ +----------+ +----------+ CareTeam type 1
| CareTeam | | CareTeam | | CareTeam | | CareTeam | (Organizational CareTeam)
+----------+ +----------+ +----------+ +----------+
An Organizational CareTeam has a lifecycle independent of Patients. It represents an organizational unit; either a “real-world” unit such as a hospital department/care unit or a “virtual” unit spanning sectors or several real-world organizational units.
This type of CareTeam does not need to have references to either Patient or EpisodeOfCare. Instead it is intended to be referenced by type 2 CareTeams which perform the actual Patient care. It can be used to group Practitioners from different organizations into a single CareTeam. It can also be used to assign practitioners from the same organization to more specific teams. For example based on role: e.g. a CareTeam consisting of monitoring responsible Practitioners.
A Patient CareTeam is created together with the EpisodeOfCare and shares the same life-cycle as the EpisodeOfCare. It has reference to both the Patient and the EpisodeOfCare. It contains a list of Practitioners, Organizations, and type 1-CareTeams currently involved in treating the Patient in context of this EpisodeOfCare.
A Patient CareTeam will typically not specify Practitioners directly. Instead it will add other CareTeams and Organizations as members. Each of these members can be assigned a role in this specific context. The Patient Careteam can be relatively static while the members of underlying CareTeams and Organizations will likely change often as Practitioners change work context.
There are currently no restrictions on the composition of CareTeams. The intended usage is to establish a few layers of CareTeams (type 1 and type 2 CareTeams), but it is important to make sure that the CareTem member graph doesn’t contain any cycles.
The official URL for this profile is:
http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-careteam
This profile builds on CareTeam.
This profile was published on Wed Mar 06 14:43:56 UTC 2019 as a draft by ehealth.sundhed.dk.
Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.
| Path | Name | Conformance | ValueSet |
| CareTeam.language | Common Languages | extensible | Common Languages |
| CareTeam.status | CareTeamStatus | required | CareTeamStatus |
| CareTeam.category | CareTeamCategory | example | CareTeamCategory |
| CareTeam.participant.role | CareTeamParticipantRole | example | CareTeamParticipantRole |
| CareTeam.reasonCode | SNOMED CT Clinical Findings | example | SNOMED CT Clinical Findings |
| Id | Path | Details | Requirements |
| dom-2 | CareTeam | If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty() | |
| dom-1 | CareTeam | If the resource is contained in another resource, it SHALL NOT contain any narrative : contained.text.empty() | |
| dom-4 | 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-3 | CareTeam | If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource : contained.where(('#'+id in %resource.descendants().reference).not()).empty() | |
| ele-1 | CareTeam.participant | All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count()) | |
| ctm-1 | CareTeam.participant | CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner : onBehalfOf.exists() implies (member.resolve() is Practitioner) |
