CareTeam resources play an important role in the eHealth Infrastructure:
...
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" }.
| Info |
|---|
A Since the CareTeam model does not have an attribute for capturing the description of the care team, a |
...
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 supported 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 |