Important: This is a draft IG for trial use. Click here to give feedback.

EN NL FR

HdBe-AdvanceDirective

CBBDescriptionStatus
HdBe-AdvanceDirective

A living will is a verbal or written description of the patient’s wishes with regard to future medical action or end of their life. A living will is mainly used for situations in which the patient is no longer able to speak about these decisions with their healthcare professional.

Purpose

A good overview of the patient’s wishes is important. A healthcare professional can use the living will to discuss the existing wishes with the persons involved and to incorporate these wishes in their own policy. A concise, orderly list is of particular importance in acute care situations.

active

id0..1string
extensionI0..*Extension
LivingWillType1..1CodeableConceptBinding
LivingWillDate1..1dateTime
DisorderI0..*Reference(HdBe-Problem)
RepresentativeI0..*Reference(HdBe-ContactPerson)
LivingWillDocument0..1base64Binary
Comment0..1string

AdvanceDirective0..*
AdvanceDirective.LivingWillTypeCodeableConcept1..1
AdvanceDirective.LivingWillDatedateTime1..1
AdvanceDirective.DisorderReference(HdBe-Problem)0..*
AdvanceDirective.RepresentativeReference(HdBe-ContactPerson)0..*
AdvanceDirective.LivingWillDocumentbase64Binary0..1
AdvanceDirective.Commentstring0..1


AdvanceDirective
DefinitionRoot concept of the AdvanceDirective information model. This concept contains all data elements of the AdvanceDirective information model.
Cardinality0...*
Invariants
  • ele-1: All FHIR elements must have a @value or children
    hasValue() or (children().count() > id.count())
Mappings
  • rim: n/a
AdvanceDirective.id
DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Cardinality0...1
Typestring
Mappings
  • rim: n/a
AdvanceDirective.extension
DefinitionMay 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.
Cardinality0...*
TypeExtension
Aliasextensions, 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.

SlicingUnordered, Open, by url(Value)
Invariants
  • 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()
Mappings
  • rim: n/a
  • rim: N/A
AdvanceDirective.LivingWillType
DefinitionList of the different types of living wills.
Cardinality1...1
TypeCodeableConcept
Binding

LivingWillType codes

TypeOfLivingWill (extensible)
Comments

Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.

Invariants
  • ele-1: All FHIR elements must have a @value or children
    hasValue() or (children().count() > id.count())
Mappings
  • rim: n/a
  • v2: CE/CNE/CWE
  • rim: CD
  • orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
AdvanceDirective.LivingWillDate
DefinitionThe date on which the living will was recorded.
Cardinality1...1
TypedateTime
Invariants
  • ele-1: All FHIR elements must have a @value or children
    hasValue() or (children().count() > id.count())
Mappings
  • rim: n/a
AdvanceDirective.Disorder
DefinitionThe problem or disorder to which the living will applies.
Cardinality0...*
TypeReference(HdBe-Problem)
Comments

References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.

Invariants
  • ele-1: All FHIR elements must have a @value or children
    hasValue() or (children().count() > id.count())
  • ref-1: SHALL have a contained resource if a local reference is provided
    reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
  • rim: n/a
  • rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity)
AdvanceDirective.Representative
DefinitionThe person who is the legal representative or is appointed as the authorized representative in the signed authorization.
Cardinality0...*
TypeReference(HdBe-ContactPerson)
Comments

References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.

Invariants
  • ele-1: All FHIR elements must have a @value or children
    hasValue() or (children().count() > id.count())
  • ref-1: SHALL have a contained resource if a local reference is provided
    reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
Mappings
  • rim: n/a
  • rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity)
AdvanceDirective.LivingWillDocument
DefinitionScanned source document with the living will and the patient's signature, such as a PDF.
Cardinality0...1
Typebase64Binary
Comments

A stream of bytes, base64 encoded

Invariants
  • ele-1: All FHIR elements must have a @value or children
    hasValue() or (children().count() > id.count())
Mappings
  • rim: n/a
AdvanceDirective.Comment
DefinitionComment on the living will: the form, such as a medallion, tattoo, etc., or where the living will can be found.
Cardinality0...1
Typestring
Comments

Note that FHIR strings SHALL NOT exceed 1MB in size

Invariants
  • ele-1: All FHIR elements must have a @value or children
    hasValue() or (children().count() > id.count())
Mappings
  • rim: n/a

Example instances

AdvanceDirective
LivingWillType 186065003 - Power of attorney medical report (code by SNOMED CT)
LivingWillDate 2010-05-06
disorder Reference to Problem (Listeriosis)
representative Reference to ContactPerson (Berend Ulijn)
LivingWillDocument Power of attorney medical report.Pdf
Comment Power of attorney granted to partner

zib AdvanceDirective-v3.1.1 difference

Concept Category Description
description textual Replaced LivingWill with AdvanceDirective where appopriate (zib-1597).
AdvanceDirective (root) textual Improved text (zib-1587).
LivingWillType terminology Included NL SNOMED codes based on the codes found in the AdvanceDirective-v4.1(2022EN) LivingWillTypeSnomedCodelist. This needs to become International codes or codes available in the BE edition. Also made the ValueSet binding strenght Extensible instead of Required which is inline with the future version of the zib as well (zib-1683)).
LivingWillType textual Improved text (zib-1587).
Representative cardinality Loosened the cardinality from 0..1 to 0..* (zib-1557).
Representative.ContactPerson naming Renamed contact to contactPerson to be consistent with the contactPerson zib (zib-1587).



Terminology Bindings

PathNameStrengthURL
LivingWillTypeTypeOfLivingWillextensiblehttps://fhir.healthdata.be/ValueSet/TypeOfLivingWill