eHealth Infrastructure (v2020.4)

StructureDefinition: ehealth-careteam - Detailed Descriptions

Definitions for the ehealth-careteam Profile.

1. CareTeam
Definition

The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient.

Control0..*
InvariantsDefined on this element
dom-1: If the resource is contained in another resource, it SHALL NOT contain any narrative (: contained.text.empty())
dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources (: contained.contained.empty())
dom-3: 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())
dom-4: 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())
2. CareTeam.id
Definition

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Control0..1
Typeid
Comments

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

3. CareTeam.meta
Definition

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.

Control0..1
TypeMeta
4. CareTeam.implicitRules
Definition

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

Control0..1
Typeuri
Is Modifiertrue
Comments

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

5. CareTeam.language
Definition

The base language in which the resource is written.

Control0..1
BindingA human language.
The codes SHALL be taken from Common Languages; other codes may be used where these codes are not suitable
Max Binding: All Languages
Typecode
Comments

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

6. CareTeam.text
Definition

A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Control0..1 This element is affected by the following invariants: dom-1
TypeNarrative
Alternate Namesnarrative, html, xhtml, display
Comments

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.

7. CareTeam.contained
Definition

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

Control0..*
TypeResource
Alternate Namesinline resources, anonymous resources, contained resources
Comments

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.

8. CareTeam.extension
Definition

An Extension

Control0..*
TypeExtension
SlicingThis element introduces a set of slices on CareTeam.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
  • value @ url
9. CareTeam.extension:telecom
SliceNametelecom
Definition

An Extension

Control0..* This element is affected by the following invariants: ele-1
TypeExtension(telecom) (Extension Type: ContactPoint)
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
10. CareTeam.modifierExtension
Definition

May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Control0..*
TypeExtension
Is Modifiertrue
Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

11. CareTeam.identifier
Definition

This records identifiers associated with this care team that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate.

NoteThis is a business identifier, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
12. CareTeam.status
Definition

Indicates the current state of the care team.

Control1..1
BindingIndicates the status of the care team.
The codes SHALL be taken from CareTeamStatus
Typecode
Is Modifiertrue
Comments

This element is labeled as a modifier because the status contains the code entered-in-error that marks the care team as not currently valid.

13. CareTeam.category
Definition

Identifies what kind of team. This is to support differentiation between multiple co-existing teams, such as care plan team, episode of care team, longitudinal care team.

Control0..*
BindingIndicates the type of care team.
For example codes, see CareTeamCategory
TypeCodeableConcept
Requirements

Used for filtering what teams(s) are retrieved and displayed to different types of users.

Comments

There may be multiple axis of categorization and one team may serve multiple purposes.

14. CareTeam.name
Definition

A label for human use intended to distinguish like teams. E.g. the "red" vs. "green" trauma teams.

Control1..1
Typestring
Comments

The meaning/purpose of the team is conveyed in CareTeam.category. This element may also convey semantics of the team (e.g. "Red trauma team"), but its primary purpose is to distinguish between identical teams in a human-friendly way. ("Team 18735" isn't as friendly . ).

15. CareTeam.subject
Definition

Identifies the patient or group whose intended care is handled by the team.

Control0..0
TypeReference(Patient | Group)
Requirements

Allows the team to care for a group (e.g. marriage) therapy.

Alternate Namespatient
16. CareTeam.context
Definition

The encounter or episode of care that establishes the context for this care team.

Control0..0
TypeReference(Encounter | EpisodeOfCare)
Alternate Namesencounter
17. CareTeam.period
Definition

Indicates when the team did (or is intended to) come into effect and end.

Control0..1
TypePeriod
Requirements

Allows tracking what team(s) are in effect at a particular time.

18. CareTeam.participant
Definition

Identifies all people and organizations who are expected to be involved in the care team.

Control0..* This element is affected by the following invariants: ctm-1
TypeBackboneElement
InvariantsDefined on this element
ctm-1: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner (: onBehalfOf.exists() implies (member.resolve() is Practitioner))
ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count()))
19. CareTeam.participant.id
Definition

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control0..1
Typestring
20. CareTeam.participant.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

21. CareTeam.participant.modifierExtension
Definition

May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Control0..*
TypeExtension
Is Modifiertrue
Alternate Namesextensions, user content, modifiers
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

22. CareTeam.participant.role
Definition

Indicates specific responsibility of an individual within the care team, such as "Primary care physician", "Trained social worker counselor", "Caregiver", etc.

Control1..1
BindingFor example codes, see CareTeam Participant Role
TypeCodeableConcept
Comments

Roles may sometimes be inferred by type of Practitioner. These are relationships that hold only within the context of the care team. General relationships should be handled as properties of the Patient resource directly.

23. CareTeam.participant.member
Definition

The specific person or organization who is participating/expected to participate in the care team.

Control1..1
TypeReference(ehealth-practitioner | ehealth-relatedperson | ehealth-patient | ehealth-organization | ehealth-careteam)
Comments

Patient only needs to be listed if they have a role other than "subject of care".

Member is optional because some participants may be known only by their role, particularly in draft plans.

24. CareTeam.participant.onBehalfOf
Definition

The organization of the practitioner.

Control0..1
TypeReference(ehealth-organization)
Requirements

Practitioners can be associated with multiple organizations. This element indicates which organization they were acting on behalf of.

25. CareTeam.participant.period
Definition

Indicates when the specific member or organization did (or is intended to) come into effect and end.

Control0..1
TypePeriod
26. CareTeam.reasonCode
Definition

Describes why the care team exists.

Control1..*
BindingThe codes SHALL be taken from Conditions
TypeCodeableConcept
27. CareTeam.reasonReference
Definition

Condition(s) that this care team addresses.

Control0..0
TypeReference(Condition)
28. CareTeam.managingOrganization
Definition

The organization responsible for the care team.

Control0..*
TypeReference(ehealth-organization)
Requirements

Allows for multiple organizations to collaboratively manage cross-organizational, longitudinal care plan.

29. CareTeam.note
Definition

Comments made about the CareTeam.

Control0..*
TypeAnnotation
30. CareTeam.note.id
Definition

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control0..1
Typestring
31. CareTeam.note.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

SlicingThis element introduces a set of slices on CareTeam.note.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
  • value @ url
32. CareTeam.note.author[x]
Definition

The individual responsible for making the annotation.

Control0..1
TypeChoice of: Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson), string
[x] NoteSee Choice of Data Types for further information about how to use [x]
33. CareTeam.note.time
Definition

Indicates when this particular annotation was made.

Control0..1
TypedateTime
34. CareTeam.note.text
Definition

The text of the annotation.

Control1..1
Typestring