CMS ACCESS Model API
0.9.8 - draft
US
This page is part of the ACCESS Model IG v0.9.8 DRAFT (v0.9.8: Releases Draft) based on FHIR (HL7® FHIR® Standard) R4. No current official version has been published yet. For a full list of available versions, see the Directory of published versions
| Official URL: https://dsacms.github.io/cmmi-access-model/CapabilityStatement/ACCESSUnalignmentAPICapabilityStatement | Version: 0.9.8 | ||||
| Active as of 2026-01-23 | Computable Name: ACCESSUnalignmentAPICapabilityStatement | ||||
Describes the expected capabilities of systems implementing the ACCESS Unalignment API for removing patient alignments from ACCESS participants.
Raw OpenAPI-Swagger Definition file | Download
Language: en
json, xmlNote 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.
serverThe ACCESS Unalignment API supports the voluntary removal of patient alignments from ACCESS participants and tracks.
Implementations SHALL use TLS 1.3 and implement OAuth 2.0 Client Credentials flow for authentication. MBI and other PHI must be protected according to HIPAA requirements.
The summary table lists the resources that are part of this configuration, and for each resource it lists:
_include_revinclude| Resource Type | Profile | R | S | U | C | Searches | _include | _revinclude | Operations |
|---|---|---|---|---|---|---|---|---|---|
| Patient | $unalign, $submission-status |
Patient resource for ACCESS unalignment operations
| Conformance | Operation | Documentation |
|---|---|---|
| SHALL | $unalign | Remove a patient's alignment from an ACCESS participant. This operation requires the |
| SHALL | $submission-status | Poll the status of a previously submitted unalignment request. Returns HTTP 202 while processing or HTTP 200 with result when complete. |