Profile: ehealth-careteam

StructureDefinition: ehealth-careteam

The intended usage is depicted here:

                        +---------------+
                        | EpisodeOfCare |                            ---> :  "References"
                        +-------------+-+
                           ^          |
                           |          v
                  +--------+-+      +---------+     
                  | CarePlan |----->| Patient |
                  +--------+-+      +---------+
                           |        
                           v         
                          +-----+---------+                              
                          |    CareTeam   |                              
                          +---------------+
                            |  |  |  |  |
                            |  |  |  |  +------------------------------------------------+
                            |  |  |  |                                                   |
      +---------------------+  |  |  +-------------------------------+                   |
      |                        |  |                                  |                   |
      |                +-------+  +-------------+                    |                   |
      v                v                        v                    v                   v
+----------+     +--------------+      +---------------+      +--------------+      +---------+
| CareTeam |     | Practitioner |      | RelatedPerson |      | Organization |      | Patient |
+----------+     +--------------+      +---------------+      +--------------+      +---------+

CareTeams

A 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.

In eHealth Infrastructure, CareTeam will not reference Patient or EpisodeOfCare as subject and context, respectively. Instead CareTeam is intended to be referenced from CarePlan. 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.

Composition of CareTeams

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.

Formal Views of Profile Content

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 Thu May 16 12:32:10 UTC 2019 as a draft by ehealth.sundhed.dk.

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

This structure is derived from CareTeam

Summary

Mandatory: 1 element (2 nested mandatory elements)

Structures

This structure refers to these other structures:

This structure is derived from CareTeam

Name	Card.	Type	Description & Constraints
CareTeam	0..*		People and organizations who plan to participate in the coordination and delivery of care for a patient.
name	1..1	string
subject	0..1	Reference(eHealth Patient \| Group) {r }
context	0..1	Reference(Encounter \| eHealth EpisodeOfCare) {r }
reasonReference	0..*	Reference(eHealth Condition) {r }
managingOrganization	0..*	Reference(eHealth Organization) {r }
Documentation for this format

This structure is derived from CareTeam

Name	Flags	Card.	Type	Description & Constraints
CareTeam	I	0..*		People and organizations who plan to participate in the coordination and delivery of care for a patient.
id	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: Common Languages (extensible)
text	I	0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional Content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	Σ	0..*	Identifier	External Ids for this team
status	?!Σ	0..1	code	proposed \| active \| suspended \| inactive \| entered-in-error Binding: CareTeamStatus (required)
category	Σ	0..*	CodeableConcept	Type of team Binding: CareTeamCategory (example)
name	Σ	1..1	string	Name of the team, such as crisis assessment team
subject	Σ	0..1	Reference(eHealth Patient \| Group) {r }	Who care team is for
context	Σ	0..1	Reference(Encounter \| eHealth EpisodeOfCare) {r }	Encounter or episode associated with CareTeam
period	Σ	0..1	Period	Time period team covers
participant	I	0..*	BackboneElement	Members of the team ctm-1: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner
id		0..1	string	xml:id (or equivalent in JSON)
extension		0..*	Extension	Additional Content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored
role	Σ	1..1	CodeableConcept	Type of involvement Binding: CareTeamParticipantRole (example)
member	Σ	1..1	Reference(eHealth Practitioner \| eHealth RelatedPerson \| eHealth Patient \| eHealth Organization \| eHealth CareTeam) {r }	Who is involved
onBehalfOf	Σ	0..1	Reference(eHealth Organization) {r }	Organization of the practitioner
period		0..1	Period	Time period of participant
reasonCode		0..*	CodeableConcept	Why the care team exists Binding: SNOMED CT Clinical Findings (example)
reasonReference		0..*	Reference(eHealth Condition) {r }	Why the care team exists
managingOrganization	Σ	0..*	Reference(eHealth Organization) {r }	Organization responsible for the care team
note		0..*	Annotation	Comments made about the CareTeam
id		0..1	string	xml:id (or equivalent in JSON)
extension		0..*	Extension	Additional Content defined by implementations Slice: Unordered, Open by value:url
author[x]	Σ	0..1	Reference(eHealth Practitioner \| eHealth Patient \| eHealth RelatedPerson), string	Individual responsible for the annotation
time	Σ	0..1	dateTime	When the annotation was made
text		1..1	string	The annotation - text content
Documentation for this format

This structure is derived from CareTeam

Summary

Mandatory: 1 element (2 nested mandatory elements)

Structures

This structure refers to these other structures:

Differential View

This structure is derived from CareTeam

Name	Card.	Type	Description & Constraints
CareTeam	0..*		People and organizations who plan to participate in the coordination and delivery of care for a patient.
name	1..1	string
subject	0..1	Reference(eHealth Patient \| Group) {r }
context	0..1	Reference(Encounter \| eHealth EpisodeOfCare) {r }
reasonReference	0..*	Reference(eHealth Condition) {r }
managingOrganization	0..*	Reference(eHealth Organization) {r }
Documentation for this format

Snapshot View

Name	Flags	Card.	Type	Description & Constraints
CareTeam	I	0..*		People and organizations who plan to participate in the coordination and delivery of care for a patient.
id	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: Common Languages (extensible)
text	I	0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional Content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	Σ	0..*	Identifier	External Ids for this team
status	?!Σ	0..1	code	proposed \| active \| suspended \| inactive \| entered-in-error Binding: CareTeamStatus (required)
category	Σ	0..*	CodeableConcept	Type of team Binding: CareTeamCategory (example)
name	Σ	1..1	string	Name of the team, such as crisis assessment team
subject	Σ	0..1	Reference(eHealth Patient \| Group) {r }	Who care team is for
context	Σ	0..1	Reference(Encounter \| eHealth EpisodeOfCare) {r }	Encounter or episode associated with CareTeam
period	Σ	0..1	Period	Time period team covers
participant	I	0..*	BackboneElement	Members of the team ctm-1: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner
id		0..1	string	xml:id (or equivalent in JSON)
extension		0..*	Extension	Additional Content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored
role	Σ	1..1	CodeableConcept	Type of involvement Binding: CareTeamParticipantRole (example)
member	Σ	1..1	Reference(eHealth Practitioner \| eHealth RelatedPerson \| eHealth Patient \| eHealth Organization \| eHealth CareTeam) {r }	Who is involved
onBehalfOf	Σ	0..1	Reference(eHealth Organization) {r }	Organization of the practitioner
period		0..1	Period	Time period of participant
reasonCode		0..*	CodeableConcept	Why the care team exists Binding: SNOMED CT Clinical Findings (example)
reasonReference		0..*	Reference(eHealth Condition) {r }	Why the care team exists
managingOrganization	Σ	0..*	Reference(eHealth Organization) {r }	Organization responsible for the care team
note		0..*	Annotation	Comments made about the CareTeam
id		0..1	string	xml:id (or equivalent in JSON)
extension		0..*	Extension	Additional Content defined by implementations Slice: Unordered, Open by value:url
author[x]	Σ	0..1	Reference(eHealth Practitioner \| eHealth Patient \| eHealth RelatedPerson), string	Individual responsible for the annotation
time	Σ	0..1	dateTime	When the annotation was made
text		1..1	string	The annotation - text content
Documentation for this format

Terminology Bindings

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

Constraints

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)