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

• 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.
• For additional security guidance, refer to the core FHIR Security guidance page.

The HL7 / UDAP Security for Scalable Registration, Authentication, and Authorization FHIR Implementation Guide referenced above is currently in ballot reconciliation and has not yet been published by HL7. This reference will be updated to the published version of the referenced security guide prior to this guide's publication