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 - Destination Server

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

This CapabilityStatement describes the expected capabilities of an destination FHIR 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 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.

FHIR RESTful Capabilities

  • Destination server SHALL support the JSON source format.
  • Destination server SHOULD support the XML source format.

Security


Raw OpenAPI-Swagger Definition file | Download

ExchangeRoutingDestinationServerCapabilityStatement

This CapabilityStatement describes the expected capabilities of an destination FHIR 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 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.

Transaction
System History
System Search
Resource TypeProfileReadSearchUpdateCreate