Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

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 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" }.

A CareTeam.note.text without CareTeam.note.authorReference and with CareTeam.note.time set to January 1st 1970 is used for capturing a description of the CareTeam by the application for managing CareTeam (see https://ehealth-dk.atlassian.net/wiki/spaces/EDTW/pages/2063892483/eHealth+Applications#Clinical-Administration-Application-(Danish%3A-KAM-for-Klinisk-administrativ-modul)).

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.

In order for a CareTeam to be eligible for use at Practitioner login, it must have:

  • status set to active

  • period which is set where:

    • period.start is before or equal to datetime of login

The following diagram describes the status transition flow for a CareTeam resource which is supported 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:

In order to prevent use of a CareTeam at Practitioner login, update:

  • status to inactive

  • possibly set period.end to the current datetime

  • No labels