Hybrid / Intermediary Exchange
1.0.0 - STU 1 US

This page is part of the Hybrid / Intermediary Exchange (v1.0.0: STU1) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

CapabilityStatement: Exchange Routing CapabilityStatement - Intermediary

Official URL: http://hl7.org/fhir/us/exchange-routing/CapabilityStatement/exchange-routing-intermediary Version: 1.0.0
Active as of 2022-05-17 Computable Name: ExchangeRoutingIntermediaryCapabilityStatement

This CapabilityStatement describes the expected capabilities of an intermediary server that conforms to the conventions of the Hybrid / Intermediary Exchange FHIR implementation guide.

FHIR Resource Content

When participating in exchanges described in the Hybrid / Intermediary FHIR IG, the intermediary server SHALL pass FHIR resources returned by the destination server to the originator unchanged.

FHIR RESTful Capabilities

  • Intermediary server SHALL support the JSON source format.
  • Intermediary serer SHOULD support the XML source format.

Security

  • Communication security implemented by the intermediary server SHALL conform with the guidelines stated in FHIR Security for all exchanges covered in this IG.
  • When using TLS: the inbound gateway intermediary SHALL hold the TLS certificate for the destination’s public FHIR service base URL the certificates exchanged by the destination system, and any delegated intermediaries SHALL reflect their servers’ private URLs.
  • Intermediary server SHALL implement Transport Layer Security (TLS) for all exchanges covered in this IG.
  • Security tokens generated and returned by the destination SHALL be forwarded by the intermediary server to the originating client.
  • Intermediary server MAY implement the HL7 / UDAP Security for Scalable Registration, Authentication, and Authorization FHIR Implementation Guide.
  • For general security considerations refer to FHIR Security and Privacy Considerations.


Raw OpenAPI-Swagger Definition file | Download

ExchangeRoutingIntermediaryCapabilityStatement

This CapabilityStatement describes the expected capabilities of an intermediary server that conforms to the conventions of the Hybrid / Intermediary Exchange FHIR implementation guide.

ModeSERVER
Description

When participating in exchanges described in the Hybrid / Intermediary FHIR IG, the intermediary server SHALL pass FHIR resources returned by the destination server to the originator unchanged. 1. Implement RESTful behavior according to the FHIR specification. 1. Support the JSON source format. When participating in exchanges described in the Hybrid / Intermediary FHIR IG, the intermediary server, the intermediary server SHOULD: 1. Support the XML source format.

Transaction
System History
System Search
Resource TypeProfileReadSearchUpdateCreate