Attachment Reference Exchange (ARex)
0.1.0 - ci-build United States of America flag

Attachment Reference Exchange (ARex) - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

CapabilityStatement: ARex Content Server (Experimental)

Official URL: https://fhir.onyxhealth.io/us/arex/CapabilityStatement/ARexContentServer Version: 0.1.0
Draft as of 2026-08-10 Computable Name: ARexContentServer

The party that publishes a manifest and serves the content it references. In an escrow-hosted deployment this is an intermediary or neutral escrow; in a source-hosted deployment it is the originating organization.

Raw OpenAPI-Swagger Definition file | Download

ARex Content Server

  • Implementation Guide Version: 0.1.0
  • FHIR Version: 4.0.1
  • Supported Formats: json, xml
  • Published on: 2026-08-10
  • Published by: Onyx Technology, LLC

Note to Implementers: FHIR Capabilities

Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

FHIR RESTful Capabilities

Mode: server

Servers SHALL require an OAuth 2.0 access token for all interactions unless a capability-URL downgrade has been agreed under a trading partner agreement. Servers SHALL verify that the authenticated client corresponds to the requesting organization named in the manifest transaction context.

Security

SMART Backend Services or UDAP B2B. No new mutual-TLS trust relationships are established for ARex purposes.

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

  • The relevant profiles (if any)
  • The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
  • The required, recommended, and some optional search parameters (if any).
  • The linked resources enabled for _include
  • The other resources enabled for _revinclude
  • The operations on the resource (if any)
Resource TypeProfileRSUCSearches_include_revincludeOperations
Listhttps://fhir.onyxhealth.io/us/arex/StructureDefinition/arex-manifestyytransaction-identifier
DocumentReferencehttps://fhir.onyxhealth.io/us/arex/StructureDefinition/arex-content-entryy
Binaryhttps://fhir.onyxhealth.io/us/arex/StructureDefinition/arex-binaryy
Provenancehttps://fhir.onyxhealth.io/us/arex/StructureDefinition/arex-provenanceyy
Base System Profile
ARex Manifest
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports read, search-type.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLtransaction-identifiertoken
 
Base System Profile
ARex Content Entry
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports read.

Base System Profile
ARex Binary
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports read.

Documentation

Servers SHALL honour a non-FHIR Accept header on Binary read and return the native octets with the native content type.

Base System Profile
ARex Provenance
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports read, search-type.