Administrative Incubator, published by HL7 International / Patient Administration. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/admin-incubator/ and changes regularly. See the Directory of published versions

• Narrative Content
• XML
• JSON
• TTL

OperationDefinition: Fetch Encounter Record

Official URL: http://hl7.org/fhir/build/OperationDefinition/Encounter-everything				Version: 0.1.0
Standards status: Trial-use Draft as of 2021-01-05			Maturity Level: 2	Computable Name: Everything

This operation is used to return all the information related to an encounter described in the resource on which this operation is invoked. The response is a bundle of type "searchset". At a minimum, the encounter resource itself is returned, along with any other resources that the server has available for the given encounter for the user. The server also returns whatever resources are needed to support the records - e.g. linked practitioners, locations, organizations etc. The principle intended use for this operation is to provide a patient with access to their record, or to allow a client to retrieve everything for an encounter for efficient display).

The server SHOULD return all resources it has that:

• are included in the encounter compartment for the identified encounter (have a reference to the encounter)
• are referenced by the standard extenstion for associating an encounter (where no reference element exists) http://hl7.org/fhir/StructureDefinition/encounter-associatedEncounter
• the server believes are relevant to the context of the encounter for any other reason (internally defined/decided)
• any resource referenced by the above, including binaries and attachments (to make a more complete package)

Implementation guides may make additional rules about how much information that is returned.

Note that for many resources, the exact nature of the link to encounter can be ambiguous (e.g. for a DiagnosticReport, is it the encounter when it was initiated, or when it was reported?)