FHIR Belgium Base IG
0.1.0 -

FHIR Belgium Base IG - Local Development build (v0.1.0). See the Directory of published versions

StructureDefinition: BECareTeamModel - Detailed Descriptions

Definitions for the model-careteam Profile.

1. BECareTeamModel
Definition

The CareTeam represents a set of professionals or sub-teams that participate in the context of care.

Control0..* This element is affected by the following invariants: ele-1
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
2. BECareTeamModel.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
3. BECareTeamModel.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
SlicingThis element introduces a set of slices on BECareTeamModel.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
  • value @ url
4. BECareTeamModel.identifier
Definition

A unique business identifier for this care team. This is not a technical system-wide identifier such as primary key or REST resource id, but rather an identifier that can be used across systems to represent the same care team.

NoteThis is a business identifier, not a resource identifier (see discussion)
Control0..*
TypeIdentifier(Identifier)
Example
550301-005.22-diabetescare2020-02:null
550301-005.22-postopcare2020-09:null
5. BECareTeamModel.status
Definition

The status of this care team - whether it is active or just being proposed (drafted), or if it is no longer active.

Control1..1
Typecode(code)
Example
active:null
draft:null
6. BECareTeamModel.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. It may also be specialised categories such as

Control0..*
BindingCare Team Category
For example codes, see CareTeamCategory
TypeCodeableConcept(CodeableConcept)
Example
:home-care
:specialists
7. BECareTeamModel.name
Definition

A label for human use intended to distinguish between teams. E.g. the "red" vs. "green" trauma teams. Note that this is NOT a type of team, but a name for an actual team. For example team name is not "diabetes team" but "patient Pia Peters's diabetes care team"

Control0..1
Typestring
Example
:Pia's diabetes care team
8. BECareTeamModel.subject
Definition

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

Control0..1
TypeReference
9. BECareTeamModel.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.

10. BECareTeamModel.participant
Definition

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

Control0..*
TypeBackboneElement
11. BECareTeamModel.participant.role
Definition

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

Control0..*
BindingIndicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.
For example codes, see ParticipantRoles
TypeCodeableConcept
12. BECareTeamModel.participant.member
Definition

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

Control0..1
TypeReference(Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | 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.

13. BECareTeamModel.justification
Definition

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

Control0..*
TypeBackboneElement
14. BECareTeamModel.justification.reasonCode
Definition

Describes why the care team exists.

Control0..*
TypeCodeableConcept
15. BECareTeamModel.justification.reasonReference
Definition

Describes why this care team addresses.

Control0..*
16. BECareTeamModel.managingOrganization
Definition

The organization responsible for the care team.

Control0..*
TypeReference(Organization)
17. BECareTeamModel.telecom
Definition

A central contact detail for the care team (that applies to all members).

Control0..*
TypeContactPoint
18. BECareTeamModel.note
Definition

Comments made about the CareTeam.

Control0..*
TypeAnnotation