Attachment Reference Exchange (ARex)
0.1.0 - ci-build
Attachment Reference Exchange (ARex)
0.1.0 - ci-build
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
| Official URL: https://fhir.onyxhealth.io/us/arex/ValueSet/arex-manifest-type | Version: 0.1.0 | |||
| Draft as of 2026-08-12 | Computable Name: ARexManifestTypeVS | |||
Categories of content set conveyed by an ARex manifest.
References
https://fhir.onyxhealth.io/us/arex/CodeSystem/arex-manifest-type version 📦0.1.0
Expansion performed internally based on codesystem ARex Manifest Type Code System v0.1.0 (CodeSystem)
This value set contains 2 concepts
| System | Code | Display (en) | Definition | JSON | XML |
https://fhir.onyxhealth.io/us/arex/CodeSystem/arex-manifest-type | attachment-set | Attachment Set | A set of documents or binary objects supporting a business transaction, such as a prior authorization or a claim. | ||
https://fhir.onyxhealth.io/us/arex/CodeSystem/arex-manifest-type | record-set | Record Set | A set of clinical records assembled in response to a data request. |
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
| Code | The code (used as the code in the resource instance) |
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
| Definition | An explanation of the meaning of the concept |
| Comments | Additional notes about how to use the code |