CareTeam resources play an important role in the eHealth Infrastructure:
at Practitioner login to the infrastructure
as entities encapsulating which Practitioners are involved in working with which EpisodeOfCare, CarePlan and associated Communication and Task resources
in access control for EpisodeOfCare, CarePlan, Communication and Task resources as well as related, other resources such as Observation, QuestionnaireResponse, Media and ClinicalImpression.
The following diagram describes the status transition flow for a CareTeam resource which is supported by the care team component within the Clinical Administrative Module. Be aware that this is more strict than the FUT infrastructure, which is not enforcing any restrictions on status transitions:
...
Preparing a CareTeam for use
A CareTeam is prepared by performing CareTeam Create.
Activating a CareTeam
The CareTeam is not eligible for use at Practitioner login until it is activated. If not set as active at time of creation, activate by CareTeam Update:
statusset toactiveperiodmust contain a start time or period which starts before the point of time intended for use at Practitioner login. Of course, the period must not have ended at point of time of last intended use either.
Updates to a CareTeam
If there is change in the focus areas of the CareTeam, these can be changed with CareTeam Update:
...
focus area(s) of the CareTeam is described in CareTeam.reasonCode which can be set to a number of CodeableConcept for conditions that the CareTeam takes care of, for instance Coding for COPD: { "system": "urn:oid:1.2.208.176.2.4", "code": "DJ44", "display": "Kronisk obstruktiv lungesygdom" }
...
Deactivating a CareTeam
Deactivation of a CareTeam prevents subsequent use at Practitioner login. Deactivate by CareTeam Update:
...
status set to any value other than active, for instance inactive
...
.
| Info |
|---|
Since the CareTeam model does not have an attribute for capturing the description of the care team, a |
The CareTeam.participant is automatically updated upon Practitioner login as described in https://ehealth-dk.atlassian.net/wiki/spaces/EDTW/pages/538935313/Behind+the+Scenes#Handling-at-Login. There is no effect and no need for an organization managing a CareTeam to add Practitioner type members.
Creating a CareTeam
A CareTeam is created by performing CareTeam Create. As noted below, there are requirements for a CareTeam to be eligible for use at Practitioner login.
Managing a CareTeam
Changes to a CareTeam can be performed by CareTeam Update.
Setting CareTeam Status
The CareTeam.status is changed by performing CareTeam Update.
| Info |
|---|
In order for a CareTeam to be eligible for use at Practitioner login, it must have:
This is the current behavior. Please note that the CareTeam status is cached for one hour, meaning that change of status in regards to login does not take effect immediately. |
| Info |
|---|
THIS IS FUTURE BEHAVIOR CURRENTLY BEING DISCUSSED. In order for a CareTeam to be eligible for use at Practitioner login, it must have:
Please note that the CareTeam status is cached for one hour, meaning that change of status in regards to login does not take effect immediately. |
The following diagram describes the status transition flow, for a CareTeam resource, which is implemented by the care team component within the Common Workplace. Be aware that this is more strict than the FUT infrastructure, which is not enforcing any restrictions on status transitions:
...
| Info |
|---|
In order to prevent use of a CareTeam at Practitioner login, update:
Please note that the CareTeam status is cached for one hour, meaning that change of status in regards to login does not take effect immediately. |
| Info |
|---|
There is currently no automated CareTeam inactivation upon reaching a |