DSTU2 Ballot Source

This page is part of the FHIR Specification (v0.5.0: DSTU 2 Ballot 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

Operation-encounter-everything.xml

Raw XML (canonical form)

Operation Definition

Raw XML

<OperationDefinition xmlns="http://hl7.org/fhir">
  <id value="Encounter-everything"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><!-- Snipped for brevity --></div>
  </text>
  <url value="http://hl7.org/fhir/OperationDefinition/Encounter-everything"/>
  <name value="Fetch Encounter Record"/>
  <publisher value="HL7 (FHIR Project)"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://hl7.org/fhir"/>
    </telecom>
    <telecom>
      <system value="email"/>
      <value value="fhir@lists.hl7.org"/>
    </telecom>
  </contact>
  <description value="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 &quot;searchset
  &quot;. 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 rhis 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 that it has that are in
   the encounter compartment for the identified encounter, and any resource referenced from
   those, including binaries and attachments. In the US Realm, At a mimimum, the resources
   returned SHALL include all the data covered by the meaningful use common data elements
   (ref to be provided). Other applicable implementation guides may make additional rules
   about the 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?)"/>
  <status value="draft"/>
  <date value="2015-04-03T14:24:32+11:00"/>
  <kind value="operation"/>
  <code value="everything"/>
  <notes value="The key differences between this operation and simply searching the encounter compartment
   are:  * unless the client requests otherwise, the server returns the entire result set
   in a single bundle (rather than using paging) * the server is responsible for determining
   what resources to return as included resources (rather than the client specifying which
   ones)"/>
  <system value="false"/>
  <instance value="true"/>
  <parameter>
    <name value="return"/>
    <use value="out"/>
    <min value="1"/>
    <max value="1"/>
    <documentation value="The bundle type is &quot;searchset&quot;"/>
    <type value="Bundle"/>
  </parameter>
</OperationDefinition>

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.