CMS ACCESS Model API
0.9.0 - ci-build
CMS ACCESS Model API - Local Development build (v0.9.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://globalalliantinc.com/access/ValueSet/ACCESSUnalignmentResultVS | Version: 0.9.0 | |||
| Draft as of 2026-03-06 | Computable Name: ACCESSUnalignmentResultVS | |||
Copyright/Legal: Copyright (c) 2026 Centers for Medicare and Medicaid Services (CMS). |
||||
This value set includes all codes from the ACCESS Unalignment Result code system.
References
https://globalalliantinc.com/access/CodeSystem/ACCESSUnalignmentResultCS version 📍0.9.0
Expansion performed internally based on codesystem ACCESS Unalignment Request Result Codes v0.9.0 (CodeSystem)
This value set contains 3 concepts
| System | Code | Display (en) | Definition | JSON | XML |
https://globalalliantinc.com/access/CodeSystem/ACCESSUnalignmentResultCS | unaligned | Unaligned | The request to unalign the patient has been accepted and the patient has been successfully unaligned. | ||
https://globalalliantinc.com/access/CodeSystem/ACCESSUnalignmentResultCS | unalignment-pending | Unalignment pending further review | Additional review is needed and you will receive further information once the manual review of the unalignment request is complete. | ||
https://globalalliantinc.com/access/CodeSystem/ACCESSUnalignmentResultCS | patient-not-aligned | Patient not aligned | Patient is not currently aligned to this participant in the specified track and therefore cannot be unaligned. |
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 |