HL7.FHIR.US.EXCHANGE-ROUTING\Exchange Routing CapabilityStatement - Destination Server

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. 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

Communication security implemented by the server SHALL conform with the guidelines stated in FHIR Security for all exchanges covered in this IG.
Destination 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

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.

Mode	SERVER
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 Type	Profile	Read	Search	Update	Create

IG © 2021+ HL7 International - FHIR Infrastructure. Package hl7.fhir.us.exchange-routing#1.0.0 based on FHIR 4.0.1. Generated 2022-09-26
Links: Table of Contents | QA Report | Version History | | Propose a change