Encounter R5 (FHIR) at fhirtruck

Path

Encounter

Id

Encounter

Cardinality

0 - *

Definition

An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. Encounter is primarily used to record information about the actual activities that occurred, where Appointment is used to record planned activities.

Comment

Constraint

dom-2 [error]

If the resource is contained in another resource, it SHALL NOT contain nested Resources

dom-3 [error]

If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource

dom-4 [error]

If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated

dom-5 [error]

If a resource is contained in another resource, it SHALL NOT have a security label

dom-6 [warning]

A resource should have narrative for robust management

Path

Encounter.identifier

Id

Encounter.identifier

Type

Identifier

Cardinality

0 - *

Definition

Identifier(s) by which this encounter is known.

Comment

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

use

Summary: The element appears in the summary view

code

usual | official | temp | secondary | old (If known)

type

CodeableConcept

Description of identifier

coding

List: This element is a list and more than one value can be provided

Coding

Code defined by a terminology system

system

uri

Identity of the terminology system

version

string

Version of the system - if relevant

code

Symbol in syntax defined by the system

display

string

Representation defined by the system

userSelected

boolean

If this coding was chosen directly by the user

system

uri

The namespace for the identifier value

value

string

The value that is unique

period

Period

Time period when id is/was valid for use

start

dateTime

Starting time with inclusive boundary

end

dateTime

End time with inclusive boundary, if not ongoing

assigner

Reference

Organization that issued id (may be just text)

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.identifier.Identifier.assigner.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

use

code

usual | official | temp | secondary | old (If known)

type

CodeableConcept

Description of identifier

system

uri

The namespace for the identifier value

value

string

The value that is unique

period

Period

Time period when id is/was valid for use

assigner

Reference

Organization that issued id (may be just text)

display

string

Text alternative for the resource

Path

Encounter.status

Id

Encounter.status

Type

code

Cardinality

1 - 1

Definition

The current state of the encounter (not the state of the patient within the encounter - that is subjectState).

Comment

Note that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes).

Binding

Strength

required

Description

Current state of the encounter.

ValueSet

http://hl7.org/fhir/ValueSet/encounter-status|5.0.0

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Path

Encounter.class

Id

Encounter.class

Type

CodeableConcept

Cardinality

0 - *

Definition

Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations.

Comment

Binding

Strength

preferred

Description

Classification of the encounter.

ValueSet

http://terminology.hl7.org/ValueSet/encounter-class

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

coding

Coding

Code defined by a terminology system

system

uri

Identity of the terminology system

version

string

Version of the system - if relevant

code

Symbol in syntax defined by the system

display

string

Representation defined by the system

userSelected

boolean

If this coding was chosen directly by the user

Path

Encounter.priority

Id

Encounter.priority

Type

CodeableConcept

Cardinality

0 - 1

Definition

Indicates the urgency of the encounter.

Comment

Binding

Strength

example

Description

Indicates the urgency of the encounter.

ValueSet

http://terminology.hl7.org/ValueSet/v3-ActPriority

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

coding

Coding

Code defined by a terminology system

system

uri

Identity of the terminology system

version

string

Version of the system - if relevant

code

Symbol in syntax defined by the system

display

string

Representation defined by the system

userSelected

boolean

If this coding was chosen directly by the user

Path

Encounter.type

Id

Encounter.type

Type

CodeableConcept

Cardinality

0 - *

Definition

Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation).

Comment

Since there are many ways to further classify encounters, this element is 0..*.

Binding

Strength

example

Description

A specific code indicating type of service provided

ValueSet

http://hl7.org/fhir/ValueSet/encounter-type

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

coding

Coding

Code defined by a terminology system

system

uri

Identity of the terminology system

version

string

Version of the system - if relevant

code

Symbol in syntax defined by the system

display

string

Representation defined by the system

userSelected

boolean

If this coding was chosen directly by the user

Path

Encounter.serviceType

Id

Encounter.serviceType

Type

CodeableReference

Cardinality

0 - *

Definition

Broad categorization of the service that is to be provided (e.g. cardiology).

Comment

Binding

Strength

example

Description

Broad categorization of the service that is to be provided.

ValueSet

http://hl7.org/fhir/ValueSet/service-type

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

concept

CodeableConcept

Reference to a concept (by class)

coding

Coding

Code defined by a terminology system

system

uri

Identity of the terminology system

version

string

Version of the system - if relevant

code

Symbol in syntax defined by the system

display

string

Representation defined by the system

userSelected

boolean

If this coding was chosen directly by the user

reference

Reference

Reference to a resource (by instance)

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.serviceType.CodeableReference.reference.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

use

code

usual | official | temp | secondary | old (If known)

type

CodeableConcept

Description of identifier

system

uri

The namespace for the identifier value

value

string

The value that is unique

period

Period

Time period when id is/was valid for use

assigner

Reference

Organization that issued id (may be just text)

display

string

Text alternative for the resource

Path

Encounter.subject

Id

Encounter.subject

Type

Reference

Cardinality

0 - 1

Definition

The patient or group related to this encounter. In some use-cases the patient MAY not be present, such as a case meeting about a patient between several practitioners or a careteam.

Comment

While the encounter is always about the patient, the patient might not actually be known in all contexts of use, and there may be a group of patients that could be anonymous (such as in a group therapy for Alcoholics Anonymous - where the recording of the encounter could be used for billing on the number of people/staff and not important to the context of the specific patients) or alternately in veterinary care a herd of sheep receiving treatment (where the animals are not individually tracked).

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.subject.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

use

code

usual | official | temp | secondary | old (If known)

type

CodeableConcept

Description of identifier

system

uri

The namespace for the identifier value

value

string

The value that is unique

period

Period

Time period when id is/was valid for use

start

dateTime

Starting time with inclusive boundary

end

dateTime

End time with inclusive boundary, if not ongoing

assigner

Reference

Organization that issued id (may be just text)

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.subject.Reference.identifier.Identifier.assigner.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

display

string

Text alternative for the resource

display

string

Text alternative for the resource

Path

Encounter.subjectStatus

Id

Encounter.subjectStatus

Type

CodeableConcept

Cardinality

0 - 1

Definition

The subjectStatus value can be used to track the patient's status within the encounter. It details whether the patient has arrived or departed, has been triaged or is currently in a waiting status.

Comment

Different use-cases are likely to have different permitted transitions between states, such as an Emergency department could use `arrived` when the patient first presents, then `triaged` once has been assessed by a nurse, then `receiving-care` once treatment begins, however other sectors may use a different set of these values, or their own custom set in place of this example valueset provided.

Binding

Strength

example

Description

Current status of the subject within the encounter.

ValueSet

http://hl7.org/fhir/ValueSet/encounter-subject-status

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

coding

Coding

Code defined by a terminology system

system

uri

Identity of the terminology system

version

string

Version of the system - if relevant

code

Symbol in syntax defined by the system

display

string

Representation defined by the system

userSelected

boolean

If this coding was chosen directly by the user

Path

Encounter.episodeOfCare

Id

Encounter.episodeOfCare

Type

Reference

Cardinality

0 - *

Definition

Where a specific encounter should be classified as a part of a specific episode(s) of care this field should be used. This association can facilitate grouping of related encounters together for a specific purpose, such as government reporting, issue tracking, association via a common problem. The association is recorded on the encounter as these are typically created after the episode of care and grouped on entry rather than editing the episode of care to append another encounter to it (the episode of care could span years).

Comment

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.episodeOfCare.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

use

code

usual | official | temp | secondary | old (If known)

type

CodeableConcept

Description of identifier

system

uri

The namespace for the identifier value

value

string

The value that is unique

period

Period

Time period when id is/was valid for use

start

dateTime

Starting time with inclusive boundary

end

dateTime

End time with inclusive boundary, if not ongoing

assigner

Reference

Organization that issued id (may be just text)

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.episodeOfCare.Reference.identifier.Identifier.assigner.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

display

string

Text alternative for the resource

display

string

Text alternative for the resource

Path

Encounter.basedOn

Id

Encounter.basedOn

Type

Reference

Cardinality

0 - *

Definition

The request this encounter satisfies (e.g. incoming referral or procedure request).

Comment

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.basedOn.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

use

code

usual | official | temp | secondary | old (If known)

type

CodeableConcept

Description of identifier

system

uri

The namespace for the identifier value

value

string

The value that is unique

period

Period

Time period when id is/was valid for use

start

dateTime

Starting time with inclusive boundary

end

dateTime

End time with inclusive boundary, if not ongoing

assigner

Reference

Organization that issued id (may be just text)

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.basedOn.Reference.identifier.Identifier.assigner.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

display

string

Text alternative for the resource

display

string

Text alternative for the resource

Path

Encounter.careTeam

Id

Encounter.careTeam

Type

Reference

Cardinality

0 - *

Definition

The group(s) of individuals, organizations that are allocated to participate in this encounter. The participants backbone will record the actuals of when these individuals participated during the encounter.

Comment

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.careTeam.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

use

code

usual | official | temp | secondary | old (If known)

type

CodeableConcept

Description of identifier

system

uri

The namespace for the identifier value

value

string

The value that is unique

period

Period

Time period when id is/was valid for use

start

dateTime

Starting time with inclusive boundary

end

dateTime

End time with inclusive boundary, if not ongoing

assigner

Reference

Organization that issued id (may be just text)

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.careTeam.Reference.identifier.Identifier.assigner.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

display

string

Text alternative for the resource

display

string

Text alternative for the resource

Path

Encounter.partOf

Id

Encounter.partOf

Type

Reference

Cardinality

0 - 1

Definition

Another Encounter of which this encounter is a part of (administratively or in time).

Comment

This is also used for associating a child's encounter back to the mother's encounter. Refer to the Notes section in the Patient resource for further details.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.partOf.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

use

code

usual | official | temp | secondary | old (If known)

type

CodeableConcept

Description of identifier

system

uri

The namespace for the identifier value

value

string

The value that is unique

period

Period

Time period when id is/was valid for use

start

dateTime

Starting time with inclusive boundary

end

dateTime

End time with inclusive boundary, if not ongoing

assigner

Reference

Organization that issued id (may be just text)

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.partOf.Reference.identifier.Identifier.assigner.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

display

string

Text alternative for the resource

display

string

Text alternative for the resource

Path

Encounter.serviceProvider

Id

Encounter.serviceProvider

Type

Reference

Cardinality

0 - 1

Definition

The organization that is primarily responsible for this Encounter's services. This MAY be the same as the organization on the Patient record, however it could be different, such as if the actor performing the services was from an external organization (which may be billed seperately) for an external consultation. Refer to the colonoscopy example on the Encounter examples tab.

Comment

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.serviceProvider.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

use

code

usual | official | temp | secondary | old (If known)

type

CodeableConcept

Description of identifier

system

uri

The namespace for the identifier value

value

string

The value that is unique

period

Period

Time period when id is/was valid for use

start

dateTime

Starting time with inclusive boundary

end

dateTime

End time with inclusive boundary, if not ongoing

assigner

Reference

Organization that issued id (may be just text)

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.serviceProvider.Reference.identifier.Identifier.assigner.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

display

string

Text alternative for the resource

display

string

Text alternative for the resource

Path

Encounter.participant

Id

Encounter.participant

Type

BackboneElement

Cardinality

0 - *

Definition

The list of people responsible for providing the service.

Comment

Any Patient or Group present in the participation.actor must also be the subject, though the subject may be absent from the participation.actor for cases where the patient (or group) is not present, such as during a case review conference.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

enc-1 [error]

A type must be provided when no explicit actor is specified

enc-2 [error]

A type cannot be provided for a patient or group participant

Path

Encounter.participant.type

Id

Encounter.participant.type

Type

CodeableConcept

Cardinality

0 - *

Definition

Role of participant in encounter.

Comment

The participant type indicates how an individual actor participates in an encounter. It includes non-practitioner participants, and for practitioners this is to describe the action type in the context of this encounter (e.g. Admitting Dr, Attending Dr, Translator, Consulting Dr). This is different to the practitioner roles which are functional roles, derived from terms of employment, education, licensing, etc.

Binding

Strength

extensible

Description

Role of participant in encounter.

ValueSet

http://hl7.org/fhir/ValueSet/encounter-participant-type

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

enc-1

enc-2

coding

Coding

Code defined by a terminology system

system

uri

Identity of the terminology system

version

string

Version of the system - if relevant

code

Symbol in syntax defined by the system

display

string

Representation defined by the system

userSelected

boolean

If this coding was chosen directly by the user

Path

Encounter.participant.period

Id

Encounter.participant.period

Type

Period

Cardinality

0 - 1

Definition

The period of time that the specified participant participated in the encounter. These can overlap or be sub-sets of the overall encounter's period.

Comment

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

start

dateTime

Starting time with inclusive boundary

end

dateTime

End time with inclusive boundary, if not ongoing

Path

Encounter.participant.actor

Id

Encounter.participant.actor

Type

Reference

Cardinality

0 - 1

Definition

Person involved in the encounter, the patient/group is also included here to indicate that the patient was actually participating in the encounter. Not including the patient here covers use cases such as a case meeting between practitioners about a patient - non contact times.

Comment

For planning purposes, Appointments may include a CareTeam participant to indicate that one specific person from the CareTeam will be assigned, but that assignment might not happen until the Encounter begins. Hence CareTeam is not included in Encounter.participant, as the specific individual should be assigned and represented as a Practitioner or other person resource. Similarly, Location can be included in Appointment.participant to assist with planning. However, the patient location is tracked on the Encounter in the Encounter.location property to allow for additional metadata and history to be recorded. The role of the participant can be used to declare what the actor will be doing in the scope of this encounter participation. If the individual is not specified during planning, then it is expected that the individual will be filled in at a later stage prior to the encounter commencing.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

enc-1

enc-2

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.participant.actor.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

use

code

usual | official | temp | secondary | old (If known)

type

CodeableConcept

Description of identifier

system

uri

The namespace for the identifier value

value

string

The value that is unique

period

Period

Time period when id is/was valid for use

assigner

Reference

Organization that issued id (may be just text)

display

string

Text alternative for the resource

Path

Encounter.appointment

Id

Encounter.appointment

Type

Reference

Cardinality

0 - *

Definition

The appointment that scheduled this encounter.

Comment

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.appointment.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

use

code

usual | official | temp | secondary | old (If known)

type

CodeableConcept

Description of identifier

system

uri

The namespace for the identifier value

value

string

The value that is unique

period

Period

Time period when id is/was valid for use

start

dateTime

Starting time with inclusive boundary

end

dateTime

End time with inclusive boundary, if not ongoing

assigner

Reference

Organization that issued id (may be just text)

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.appointment.Reference.identifier.Identifier.assigner.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

display

string

Text alternative for the resource

display

string

Text alternative for the resource

Path

Encounter.virtualService

Id

Encounter.virtualService

Type

VirtualServiceDetail

Cardinality

0 - *

Definition

Connection details of a virtual service (e.g. conference call).

Comment

There are two types of virtual meetings that often exist: * a persistent, virtual meeting room that can only be used for a single purpose at a time, * and a dynamic virtual meeting room that is generated on demand for a specific purpose. Implementers may consider using Location.virtualService for persistent meeting rooms. If each participant would have a different meeting link, an extension using the VirtualServiceContactDetail can be applied to the Encounter.participant BackboneElement.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

channelType

Coding

Channel Type

system

uri

Identity of the terminology system

version

string

Version of the system - if relevant

code

Symbol in syntax defined by the system

display

string

Representation defined by the system

userSelected

boolean

If this coding was chosen directly by the user

address[x]

url

Contact address/number

additionalInfo

url

Address to see alternative connection details

maxParticipants

positiveInt

Maximum number of participants supported by the virtual service

sessionKey

string

Session Key required by the virtual service

Path

Encounter.actualPeriod

Id

Encounter.actualPeriod

Type

Period

Cardinality

0 - 1

Definition

The actual start and end time of the encounter.

Comment

If not (yet) known, the end of the Period may be omitted.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

start

dateTime

Starting time with inclusive boundary

end

dateTime

End time with inclusive boundary, if not ongoing

Path

Encounter.plannedStartDate

Id

Encounter.plannedStartDate

Type

dateTime

Cardinality

0 - 1

Definition

The planned start date/time (or admission date) of the encounter.

Comment

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Path

Encounter.plannedEndDate

Id

Encounter.plannedEndDate

Type

dateTime

Cardinality

0 - 1

Definition

The planned end date/time (or discharge date) of the encounter.

Comment

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Path

Encounter.length

Id

Encounter.length

Type

Duration

Cardinality

0 - 1

Definition

Actual quantity of time the encounter lasted. This excludes the time during leaves of absence. When missing it is the time in between the start and end values.

Comment

If the precision on these values is low (e.g. to the day only) then this may be considered was an all day (or multi-day) encounter, unless the duration is included, where that amount of time occurred sometime during the interval. May differ from the time in `Encounter.period` due to leave of absence(s).

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

value

decimal

Numerical value (with implicit precision)

comparator

code

< | <= | >= | > | ad - how to understand the value

unit

string

Unit representation

system

uri

System that defines coded unit form

code

Coded form of the unit

Path

Encounter.reason

Id

Encounter.reason

Type

BackboneElement

Cardinality

0 - *

Definition

The list of medical reasons that are expected to be addressed during the episode of care.

Comment

The reason communicates what medical problem the patient has that should be addressed during the episode of care. This reason could be patient reported complaint, a clinical indication that was determined in a previous encounter or episode of care, or some planned care such as an immunization recommendation. In the case where you have a primary reason, but are expecting to also address other problems, you can list the primary reason with a use code of 'Chief Complaint', while the other problems being addressed would have a use code of 'Reason for Visit'. Examples: * pregnancy would use HealthcareService or a coding as the reason * patient home monitoring could use Condition as the reason

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Path

Encounter.reason.use

Id

Encounter.reason.use

Type

CodeableConcept

Cardinality

0 - *

Definition

What the reason value should be used as e.g. Chief Complaint, Health Concern, Health Maintenance (including screening).

Comment

Binding

Strength

example

Description

ValueSet

http://hl7.org/fhir/ValueSet/encounter-reason-use

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

coding

Coding

Code defined by a terminology system

system

uri

Identity of the terminology system

version

string

Version of the system - if relevant

code

Symbol in syntax defined by the system

display

string

Representation defined by the system

userSelected

boolean

If this coding was chosen directly by the user

Path

Encounter.reason.value

Id

Encounter.reason.value

Type

CodeableReference

Cardinality

0 - *

Definition

Reason the encounter takes place, expressed as a code or a reference to another resource. For admissions, this can be used for a coded admission diagnosis.

Comment

Binding

Strength

preferred

Description

Reason why the encounter takes place.

ValueSet

http://hl7.org/fhir/ValueSet/encounter-reason

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

concept

CodeableConcept

Reference to a concept (by class)

reference

Reference

Reference to a resource (by instance)

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.reason.value.CodeableReference.reference.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

display

string

Text alternative for the resource

Path

Encounter.diagnosis

Id

Encounter.diagnosis

Type

BackboneElement

Cardinality

0 - *

Definition

The list of diagnosis relevant to this encounter.

Comment

Also note that for the purpose of billing, the diagnoses are recorded in the account where they can be ranked appropriately for how the invoicing/claiming documentation needs to be prepared.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Path

Encounter.diagnosis.condition

Id

Encounter.diagnosis.condition

Type

CodeableReference

Cardinality

0 - *

Definition

The coded diagnosis or a reference to a Condition (with other resources referenced in the evidence.detail), the use property will indicate the purpose of this specific diagnosis.

Comment

Binding

Strength

example

Description

ValueSet

http://hl7.org/fhir/ValueSet/condition-code

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

concept

CodeableConcept

Reference to a concept (by class)

reference

Reference

Reference to a resource (by instance)

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.diagnosis.condition.CodeableReference.reference.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

display

string

Text alternative for the resource

Path

Encounter.diagnosis.use

Id

Encounter.diagnosis.use

Type

CodeableConcept

Cardinality

0 - *

Definition

Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …).

Comment

Binding

Strength

preferred

Description

The type of diagnosis this condition represents.

ValueSet

http://hl7.org/fhir/ValueSet/encounter-diagnosis-use

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

coding

Coding

Code defined by a terminology system

system

uri

Identity of the terminology system

version

string

Version of the system - if relevant

code

Symbol in syntax defined by the system

display

string

Representation defined by the system

userSelected

boolean

If this coding was chosen directly by the user

Path

Encounter.account

Id

Encounter.account

Type

Reference

Cardinality

0 - *

Definition

The set of accounts that may be used for billing for this Encounter.

Comment

The billing system may choose to allocate billable items associated with the Encounter to different referenced Accounts based on internal business rules.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.account.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

use

code

usual | official | temp | secondary | old (If known)

type

CodeableConcept

Description of identifier

system

uri

The namespace for the identifier value

value

string

The value that is unique

period

Period

Time period when id is/was valid for use

start

dateTime

Starting time with inclusive boundary

end

dateTime

End time with inclusive boundary, if not ongoing

assigner

Reference

Organization that issued id (may be just text)

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.account.Reference.identifier.Identifier.assigner.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

display

string

Text alternative for the resource

display

string

Text alternative for the resource

Path

Encounter.dietPreference

Id

Encounter.dietPreference

Type

CodeableConcept

Cardinality

0 - *

Definition

Diet preferences reported by the patient.

Comment

For example, a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive).

Requirements

Used to track patient's diet restrictions and/or preference. For a complete description of the nutrition needs of a patient during their stay, one should use the nutritionOrder resource which links to Encounter.

Binding

Strength

example

Description

Medical, cultural or ethical food preferences to help with catering requirements.

ValueSet

http://hl7.org/fhir/ValueSet/encounter-diet

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

coding

Coding

Code defined by a terminology system

system

uri

Identity of the terminology system

version

string

Version of the system - if relevant

code

Symbol in syntax defined by the system

display

string

Representation defined by the system

userSelected

boolean

If this coding was chosen directly by the user

Path

Encounter.specialArrangement

Id

Encounter.specialArrangement

Type

CodeableConcept

Cardinality

0 - *

Definition

Any special requests that have been made for this encounter, such as the provision of specific equipment or other things.

Comment

Binding

Strength

preferred

Description

Special arrangements.

ValueSet

http://hl7.org/fhir/ValueSet/encounter-special-arrangements

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

coding

Coding

Code defined by a terminology system

system

uri

Identity of the terminology system

version

string

Version of the system - if relevant

code

Symbol in syntax defined by the system

display

string

Representation defined by the system

userSelected

boolean

If this coding was chosen directly by the user

Path

Encounter.specialCourtesy

Id

Encounter.specialCourtesy

Type

CodeableConcept

Cardinality

0 - *

Definition

Special courtesies that may be provided to the patient during the encounter (VIP, board member, professional courtesy).

Comment

Although the specialCourtesy property can contain values like VIP, the purpose of this field is intended to be used for flagging additional `benefits` that might occur for the patient during the encounter. It could include things like the patient is to have a private room, special room features, receive a friendly visit from hospital adminisitration, or should be briefed on treatment by senior staff during the stay. It is not specifically intended to be used for securing the specific record - that is the purpose of the security meta tag, and where appropriate, both fields could be used.

Binding

Strength

preferred

Description

Special courtesies.

ValueSet

http://hl7.org/fhir/ValueSet/encounter-special-courtesy

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

coding

Coding

Code defined by a terminology system

system

uri

Identity of the terminology system

version

string

Version of the system - if relevant

code

Symbol in syntax defined by the system

display

string

Representation defined by the system

userSelected

boolean

If this coding was chosen directly by the user

Path

Encounter.admission

Id

Encounter.admission

Type

BackboneElement

Cardinality

0 - 1

Definition

Details about the stay during which a healthcare service is provided. This does not describe the event of admitting the patient, but rather any information that is relevant from the time of admittance until the time of discharge.

Comment

An Encounter may cover more than just the inpatient stay. Contexts such as outpatients, community clinics, and aged care facilities are also included. The duration recorded in the period of this encounter covers the entire scope of this admission record.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Path

Encounter.admission.preAdmissionIdentifier

Id

Encounter.admission.preAdmissionIdentifier

Type

Identifier

Cardinality

0 - 1

Definition

Pre-admission identifier.

Comment

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

use

code

usual | official | temp | secondary | old (If known)

type

CodeableConcept

Description of identifier

system

uri

The namespace for the identifier value

value

string

The value that is unique

period

Period

Time period when id is/was valid for use

start

dateTime

Starting time with inclusive boundary

end

dateTime

End time with inclusive boundary, if not ongoing

assigner

Reference

Organization that issued id (may be just text)

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.admission.preAdmissionIdentifier.Identifier.assigner.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

display

string

Text alternative for the resource

Path

Encounter.admission.origin

Id

Encounter.admission.origin

Type

Reference

Cardinality

0 - 1

Definition

The location/organization from which the patient came before admission.

Comment

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.admission.origin.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

use

code

usual | official | temp | secondary | old (If known)

type

CodeableConcept

Description of identifier

system

uri

The namespace for the identifier value

value

string

The value that is unique

period

Period

Time period when id is/was valid for use

assigner

Reference

Organization that issued id (may be just text)

display

string

Text alternative for the resource

Path

Encounter.admission.admitSource

Id

Encounter.admission.admitSource

Type

CodeableConcept

Cardinality

0 - 1

Definition

From where patient was admitted (physician referral, transfer).

Comment

Binding

Strength

preferred

Description

From where the patient was admitted.

ValueSet

http://hl7.org/fhir/ValueSet/encounter-admit-source

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

coding

Coding

Code defined by a terminology system

system

uri

Identity of the terminology system

version

string

Version of the system - if relevant

code

Symbol in syntax defined by the system

display

string

Representation defined by the system

userSelected

boolean

If this coding was chosen directly by the user

Path

Encounter.admission.reAdmission

Id

Encounter.admission.reAdmission

Type

CodeableConcept

Cardinality

0 - 1

Definition

Indicates that this encounter is directly related to a prior admission, often because the conditions addressed in the prior admission were not fully addressed.

Comment

Binding

Strength

example

Description

The reason for re-admission of this admission encounter.

ValueSet

http://terminology.hl7.org/ValueSet/v2-0092

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

coding

Coding

Code defined by a terminology system

system

uri

Identity of the terminology system

version

string

Version of the system - if relevant

code

Symbol in syntax defined by the system

display

string

Representation defined by the system

userSelected

boolean

If this coding was chosen directly by the user

Path

Encounter.admission.destination

Id

Encounter.admission.destination

Type

Reference

Cardinality

0 - 1

Definition

Location/organization to which the patient is discharged.

Comment

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.admission.destination.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

use

code

usual | official | temp | secondary | old (If known)

type

CodeableConcept

Description of identifier

system

uri

The namespace for the identifier value

value

string

The value that is unique

period

Period

Time period when id is/was valid for use

assigner

Reference

Organization that issued id (may be just text)

display

string

Text alternative for the resource

Path

Encounter.admission.dischargeDisposition

Id

Encounter.admission.dischargeDisposition

Type

CodeableConcept

Cardinality

0 - 1

Definition

Category or kind of location after discharge.

Comment

Binding

Strength

example

Description

Discharge Disposition.

ValueSet

http://hl7.org/fhir/ValueSet/encounter-discharge-disposition

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

coding

Coding

Code defined by a terminology system

system

uri

Identity of the terminology system

version

string

Version of the system - if relevant

code

Symbol in syntax defined by the system

display

string

Representation defined by the system

userSelected

boolean

If this coding was chosen directly by the user

Path

Encounter.location

Id

Encounter.location

Type

BackboneElement

Cardinality

0 - *

Definition

List of locations where the patient has been during this encounter.

Comment

Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual".

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Path

Encounter.location.location

Id

Encounter.location.location

Type

Reference

Cardinality

1 - 1

Definition

The location where the encounter takes place.

Comment

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

reference

string

Literal reference, Relative, internal or absolute URL

type

uri

Type the reference refers to (e.g. "Patient") - must be a resource in resources

identifier

Identifier

Logical reference, when literal reference is not known

Path

Encounter.location.location.Reference.identifier

Id

Reference.identifier

Type

Identifier

Cardinality

0 - 1

Definition

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

Comment

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Condition

ref-2

use

code

usual | official | temp | secondary | old (If known)

type

CodeableConcept

Description of identifier

system

uri

The namespace for the identifier value

value

string

The value that is unique

period

Period

Time period when id is/was valid for use

assigner

Reference

Organization that issued id (may be just text)

display

string

Text alternative for the resource

Path

Encounter.location.status

Id

Encounter.location.status

Type

code

Cardinality

0 - 1

Definition

The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time.

Comment

When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed.

Binding

Strength

required

Description

The status of the location.

ValueSet

http://hl7.org/fhir/ValueSet/encounter-location-status|5.0.0

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

Path

Encounter.location.form

Id

Encounter.location.form

Type

CodeableConcept

Cardinality

0 - 1

Definition

This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query.

Comment

This information is de-normalized from the Location resource to support the easier understanding of the encounter resource and processing in messaging or query. There may be many levels in the hierachy, and this may only pic specific levels that are required for a specific usage scenario.

Binding

Strength

example

Description

Physical form of the location.

ValueSet

http://hl7.org/fhir/ValueSet/location-form

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

coding

Coding

Code defined by a terminology system

system

uri

Identity of the terminology system

version

string

Version of the system - if relevant

code

Symbol in syntax defined by the system

display

string

Representation defined by the system

userSelected

boolean

If this coding was chosen directly by the user

Path

Encounter.location.period

Id

Encounter.location.period

Type

Period

Cardinality

0 - 1

Definition

Time period during which the patient was present at the location.

Comment

Constraint

ele-1 [error]

All FHIR elements must have a @value or children

start

dateTime

Starting time with inclusive boundary

end

dateTime

End time with inclusive boundary, if not ongoing