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.

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

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

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

An Extension

R5: EncounterHistory.encounter (new:Reference(Encounter))

Element EncounterHistory.encounter has a context of Encounter based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.encounter has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

R5: EncounterHistory.serviceType (new:CodeableReference(HealthcareService))

Element EncounterHistory.serviceType has a context of Encounter based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.serviceType has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: EncounterHistory.subjectStatus (new:CodeableConcept)

Element EncounterHistory.subjectStatus has a context of Encounter based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.subjectStatus has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: EncounterHistory.actualPeriod (new:Period)

Element EncounterHistory.actualPeriod has a context of Encounter based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.actualPeriod has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: EncounterHistory.plannedStartDate (new:dateTime)

Element EncounterHistory.plannedStartDate has a context of Encounter based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.plannedStartDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: EncounterHistory.plannedEndDate (new:dateTime)

Element EncounterHistory.plannedEndDate has a context of Encounter based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.plannedEndDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

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

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

planned | arrived | triaged | in-progress | onleave | finished | cancelled +.

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

This element is labeled as a modifier because the status contains codes that mark the encounter as not currently valid.

The codes SHALL be taken from EncounterStatus http://hl7.org/fhir/ValueSet/encounter-status|3.0.2
(required to http://hl7.org/fhir/ValueSet/encounter-status|3.0.2)

Current state of the encounter

An Extension

R5: EncounterHistory.status

Element EncounterHistory.status is mapped to FHIR STU3 element Encounter.status as SourceIsBroaderThanTarget. The target context Encounter.status is a modifier element, so this extension does not need to be defined as a modifier. Note that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes).

R5: EncounterHistory.encounter (new:Reference(Encounter))

Element EncounterHistory.encounter has a context of Encounter based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.encounter has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

R5: EncounterHistory.serviceType (new:CodeableReference(HealthcareService))

Element EncounterHistory.serviceType has a context of Encounter based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.serviceType has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: EncounterHistory.subjectStatus (new:CodeableConcept)

Element EncounterHistory.subjectStatus has a context of Encounter based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.subjectStatus has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: EncounterHistory.actualPeriod (new:Period)

Element EncounterHistory.actualPeriod has a context of Encounter based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.actualPeriod has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: EncounterHistory.plannedStartDate (new:dateTime)

Element EncounterHistory.plannedStartDate has a context of Encounter based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.plannedStartDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: EncounterHistory.plannedEndDate (new:dateTime)

Element EncounterHistory.plannedEndDate has a context of Encounter based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.plannedEndDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: EncounterHistory.status

Element EncounterHistory.status is mapped to FHIR STU3 element Encounter.status as SourceIsBroaderThanTarget. The target context Encounter.status is a modifier element, so this extension does not need to be defined as a modifier. Note that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes).

R5: EncounterHistory.class additional types (CodeableConcept) additional types from child elements (text)

Element EncounterHistory.class is mapped to FHIR STU3 element Encounter.class as SourceIsBroaderThanTarget. The mappings for EncounterHistory.class do not cover the following types: CodeableConcept. The mappings for EncounterHistory.class do not cover the following types based on type expansion: text.

R5: EncounterHistory.subject additional types from child elements (display, identifier, reference, type)

Element EncounterHistory.subject is mapped to FHIR STU3 element Encounter.subject as SourceIsBroaderThanTarget. The mappings for EncounterHistory.subject do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element EncounterHistory.subject with unmapped reference targets: Group, Patient. 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).

R5: EncounterHistory.location.form (new:CodeableConcept)

Element EncounterHistory.location.form has a context of Encounter.location based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.location.form has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

R5: EncounterHistory.location.location additional types from child elements (display, identifier, reference, type)

Element EncounterHistory.location.location is mapped to FHIR STU3 element Encounter.location.location as SourceIsBroaderThanTarget. The mappings for EncounterHistory.location.location do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element EncounterHistory.location.location with unmapped reference targets: Location.

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.

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

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

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

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

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

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

The base language in which the resource is written.

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

Unless not suitable, these codes SHALL be taken from Common Languages
(extensible to http://hl7.org/fhir/ValueSet/languages|3.0.2)

A human language.

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

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

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

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

An Extension

R5: EncounterHistory.encounter (new:Reference(Encounter))

Element EncounterHistory.encounter has a context of Encounter based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.encounter has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

R5: EncounterHistory.serviceType (new:CodeableReference(HealthcareService))

Element EncounterHistory.serviceType has a context of Encounter based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.serviceType has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: EncounterHistory.subjectStatus (new:CodeableConcept)

Element EncounterHistory.subjectStatus has a context of Encounter based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.subjectStatus has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: EncounterHistory.actualPeriod (new:Period)

Element EncounterHistory.actualPeriod has a context of Encounter based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.actualPeriod has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: EncounterHistory.plannedStartDate (new:dateTime)

Element EncounterHistory.plannedStartDate has a context of Encounter based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.plannedStartDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: EncounterHistory.plannedEndDate (new:dateTime)

Element EncounterHistory.plannedEndDate has a context of Encounter based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.plannedEndDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

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

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

Identifier(s) by which this encounter is known.

planned | arrived | triaged | in-progress | onleave | finished | cancelled +.

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

This element is labeled as a modifier because the status contains codes that mark the encounter as not currently valid.

The codes SHALL be taken from EncounterStatus
(required to http://hl7.org/fhir/ValueSet/encounter-status|3.0.2)

Current state of the encounter

unique id for the element within a resource (for internal references)

An Extension

R5: EncounterHistory.status

Element EncounterHistory.status is mapped to FHIR STU3 element Encounter.status as SourceIsBroaderThanTarget. The target context Encounter.status is a modifier element, so this extension does not need to be defined as a modifier. Note that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes).

Primitive value for code

The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them.

The current status is always found in the current version of the resource, not the status history.

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

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

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

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

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

planned | arrived | triaged | in-progress | onleave | finished | cancelled +.

The codes SHALL be taken from EncounterStatus
(required to http://hl7.org/fhir/ValueSet/encounter-status|3.0.2)

Current state of the encounter

The time that the episode was in the specified status.

inpatient | outpatient | ambulatory | emergency +.

Classification of the encounter

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

An Extension

R5: EncounterHistory.class additional types (CodeableConcept) additional types from child elements (text)

Element EncounterHistory.class is mapped to FHIR STU3 element Encounter.class as SourceIsBroaderThanTarget. The mappings for EncounterHistory.class do not cover the following types: CodeableConcept. The mappings for EncounterHistory.class do not cover the following types based on type expansion: text.

The identification of the code system that defines the meaning of the symbol in the code.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of the system.

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

The class history permits the tracking of the encounters transitions without needing to go through the resource history.

This would be used for a case where an admission starts of as an emergency encounter, then transisions into an inpatient scenario. Doing this and not restarting a new encounter ensures that any lab/diagnostic results can more easily follow the patient and not require re-processing and not get lost or cancelled during a kindof discharge from emergency to inpatient.

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

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

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

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

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

inpatient | outpatient | ambulatory | emergency +.

Classification of the encounter

The time that the episode was in the specified class.

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

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

The type of encounter

Indicates the urgency of the encounter.

Indicates the urgency of the encounter.

The patient ro group present at the encounter.

While the encounter is always about the patient, the patient may 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).

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

An Extension

R5: EncounterHistory.subject additional types from child elements (display, identifier, reference, type)

Element EncounterHistory.subject is mapped to FHIR STU3 element Encounter.subject as SourceIsBroaderThanTarget. The mappings for EncounterHistory.subject do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element EncounterHistory.subject with unmapped reference targets: Group, Patient. 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).

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity 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.

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.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

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).

The referral request this encounter satisfies (incoming referral).

The list of people responsible for providing the service.

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

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

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

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

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

Role of participant in encounter.

The participant type indicates how an individual partitipates 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.

Role of participant in encounter

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.

Persons involved in the encounter other than the patient.

The appointment that scheduled this encounter.

The start and end time of the encounter.

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

Quantity of time the encounter lasted. This excludes the time during leaves of absence.

May differ from the time the Encounter.period lasted because of leave of absence.

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

For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).

Reason why the encounter takes place.

The list of diagnosis relevant to this encounter.

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

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

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

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

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

Reason the encounter takes place, as specified using information from another resource. For admissions, this is the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure.

For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).

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

The type of diagnosis this condition represents

Ranking of the diagnosis (for each role type).

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

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

Details about the admission to a healthcare service.

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 hospitalization record.

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

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

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

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

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

Pre-admission identifier.

The location from which the patient came before admission.

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

From where the patient was admitted.

Whether this hospitalization is a readmission and why if known.

The reason for re-admission of this hospitalization encounter.

Diet preferences reported by the patient.

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

Medical, cultural or ethical food preferences to help with catering 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.

Special courtesies (VIP, board member).

Special courtesies

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

Special arrangements

Location to which the patient is discharged.

Category or kind of location after discharge.

Discharge Disposition

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

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".

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

An Extension

R5: EncounterHistory.location.form (new:CodeableConcept)

Element EncounterHistory.location.form has a context of Encounter.location based on following the parent source element upwards and mapping to Encounter. Element EncounterHistory.location.form has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

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

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

The location where the encounter takes place.

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

An Extension

R5: EncounterHistory.location.location additional types from child elements (display, identifier, reference, type)

Element EncounterHistory.location.location is mapped to FHIR STU3 element Encounter.location.location as SourceIsBroaderThanTarget. The mappings for EncounterHistory.location.location do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element EncounterHistory.location.location with unmapped reference targets: Location.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity 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.

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.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

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

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.

The status of the location.

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

An organization that is in charge of maintaining the information of this Encounter (e.g. who maintains the report or the master service catalog item, etc.). This MAY be the same as the organization on the Patient record, however it could be different. This MAY not be not the Service Delivery Location's Organization.

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

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.