HL7 Belgium FHIR specifications
0.1 - QA review

This page is part of the HL7 Belgium FHIR Specifications (v2020May: QA Preview) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

StructureDefinition: BEPatientWill - Detailed Descriptions

Definitions for the be-model-patientwill Profile.

1. BEPatientWill
Definition

A patient will (a single entry in the patient will) - an individual statement of permission or refusal for care-related activities such as live organ donation, resuscitation, etc.

Control0..*
2. BEPatientWill.id
Definition

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

Control0..1
Typestring
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. BEPatientWill.meta
Definition

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

Control0..1
TypeMeta
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
4. BEPatientWill.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. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
5. BEPatientWill.language
Definition

The base language in which the resource is written.

Control0..1
BindingA human language.
The codes SHOULD be taken from CommonLanguages
Max Binding: AllLanguages
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).

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
6. BEPatientWill.identifier
Definition

The business identifier(s) for the patient will entry - This is an optional attribute, used for example to track an entry throughout its lifecycle, or across vaults.

NoteThis is a business identifier, not a resource identifier (see discussion)
Control0..1
TypeIdentifier
7. BEPatientWill.status
Control1..1
BindingThe codes SHALL be taken from http://hl7.org/fhir/valueset-consent-state-codes
Typecode(code)
8. BEPatientWill.dateTime
Definition

The date and/or time when the patient will has been declared - for example if this captures a physical document that was sgined by a patient on a given date, this element would correspond with that date

Control1..1
TypedateTime(dateTime)
9. BEPatientWill.reporter
Definition

The healthcare professional who takes responsibility for collecting content.

Control1..1
TypeReference(BePractitioner)
10. BEPatientWill.patient
Definition

The subject of the patient will.

Control1..1
TypeReference(BePatient)
11. BEPatientWill.source
Definition

Supporting evidence for the patient will (e.g. a paper signed by the patient to refuse a specific treatment)

Control0..1
TypeAttachment(Attachment)
12. BEPatientWill.directive
Definition

The patient will directive

Control1..1
TypeBackboneElement
13. BEPatientWill.directive.action
Definition

The detailed patient will directive (e.g. no hospitalization, bloodtransfusion refusal) (Valueset will be delivered by a working group of NIHDI)

Control1..1
TypeCodeableConcept(CodeableConcept)
14. BEPatientWill.directive.type
Definition

Whether the patient will action is explicitly permitted or explicitly denied

Control1..1
TypeCodeableConcept(CodeableConcept)
15. BEPatientWill.directive.category
Definition

The main types of patient will

Control0..1
BindingThe codes SHALL be taken from valueset-consent-category.html; other codes may be used where these codes are not suitable
TypeCodeableConcept(CodeableConcept)
16. BEPatientWill.directive.effectiveTime
Definition

The period of validity for the patient will directive

Control1..1
TypeBackboneElement
17. BEPatientWill.directive.effectiveTime.period
Definition

The time period of validity for the patient will directive

Control0..1
TypePeriod(Period)
18. BEPatientWill.directive.effectiveTime.time
Definition

A free-text indication of the period of validity for the patient will directive

Control0..1
TypePeriod(Period)