Hybrid / Intermediary Exchange
0.1.0 - STU 1 Ballot

This page is part of the Hybrid / Intermediary Exchange (v0.1.0: STU1 Ballot 1) based on FHIR R4. The current version which supercedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions

: Exchange Routing CapabilityStatement - Destination Server - XML Representation

Raw xml | Download



<CapabilityStatement xmlns="http://hl7.org/fhir">
  <id value="exchange-routing-destination-server"/>
  <text>
    <status value="extensions"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><h2>ExchangeRoutingDestinationServerCapabilityStatement</h2><div><p>This CapabilityStatement describes the expected capabilities of an destination FHIR server that conforms to the conventions of the Hybrid / Intermediary Exchange FHIR implementation guide.</p>
</div><table><tr><td>Mode</td><td>SERVER</td></tr><tr><td>Description</td><td><div><p>When participating in exchanges described in the Hybrid / Intermediary FHIR IG, the destination server <strong>SHALL</strong> populate references to itself within FHIR resources it returns (e.g., in the Bundle.entry.fullUrl element) and in HTTP header parameters (e.g., Content-Location within the FHIR Asynchronous Pattern) with its public FHIR service base URL. 1. Implement RESTful behavior according to the FHIR specification. 1. Support the JSON source format.
When participating in exchanges involving an intermediary as described in the Hybrid / Intermediary FHIR IG, the server <strong>SHOULD</strong>: 1. Support the XML source format.</p>
</div></td></tr><tr><td>Transaction</td><td></td></tr><tr><td>System History</td><td></td></tr><tr><td>System Search</td><td></td></tr></table><table><tr><th><b>Resource Type</b></th><th><b>Profile</b></th><th><b title="GET a resource (read interaction)">Read</b></th><th><b title="GET all set of resources of the type (search interaction)">Search</b></th><th><b title="PUT a new resource version (update interaction)">Update</b></th><th><b title="POST a new resource (create interaction)">Create</b></th></tr></table></div>
  </text>
  <url
       value="http://hl7.org/fhir/us/exchange-routing/CapabilityStatement/exchange-routing-destination-server"/>
  <version value="0.1.0"/>
  <name value="ExchangeRoutingDestinationServerCapabilityStatement"/>
  <title value="Exchange Routing Destination Server Capability Statement"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2021-11-15T00:00:00-05:00"/>
  <publisher value="HL7 International - FHIR Infrastructure"/>
  <contact>
    <name value="HL7 International - FHIR Infrastructure"/>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/fiwg"/>
    </telecom>
  </contact>
  <contact>
    <name value="Frank McKinney"/>
    <telecom>
      <system value="email"/>
      <value value="frank.mckinney@pocp.com"/>
    </telecom>
  </contact>
  <description
               value="This CapabilityStatement describes the expected capabilities of an destination FHIR server that conforms to the conventions of the Hybrid / Intermediary Exchange FHIR implementation guide."/>
  <jurisdiction>
    <coding>
      <system value="urn:iso:std:iso:3166"/>
      <code value="US"/>
      <display value="United States of America"/>
    </coding>
  </jurisdiction>
  <kind value="requirements"/>
  <fhirVersion value="4.0.1"/>
  <format value="xml"/>
  <format value="json"/>
  <patchFormat value="application/json-patch+json"/>
  <implementationGuide
                       value="http://hl7.org/fhir/us/exchange-routing/ImplementationGuide/exchange-routing"/>
  <rest>
    <mode value="server"/>
    <documentation
                   value="When participating in exchanges described in the Hybrid / Intermediary FHIR IG, the destination server **SHALL** populate references to itself within FHIR resources it returns (e.g., in the Bundle.entry.fullUrl element) and in HTTP header parameters (e.g., Content-Location within the FHIR Asynchronous Pattern) with its public FHIR service base URL. 1. Implement RESTful behavior according to the FHIR specification. 1. Support the JSON source format. 
When participating in exchanges involving an intermediary as described in the Hybrid / Intermediary FHIR IG, the server **SHOULD**: 1. Support the XML source format."/>
    <security>
      <description
                   value="The server SHALL implement Transport Layer Security (TLS) for all exchanges covered in this IG. 
1. The server MAY implement the [HL7 / UDAP Security for Scalable Registration, Authentication, and Authorization FHIR Implementation Guide](http://hl7.org/fhir/us/udap-security/2021Sep). 1. For general security considerations refer to [FHIR Security and Privacy Considerations](https://www.hl7.org/fhir/secpriv-module.html). 
1. For additional security guidance, refer to the [core FHIR Security guidance page](https://www.hl7.org/fhir/security.html)."/>
    </security>
  </rest>
</CapabilityStatement>