Developers

The ecosystem, mapped

Regulation → implementation guide → package → tool → explainer. Every edge on this page comes from a register with its own tests — the basis vocabulary, the dates, and the dead ends are the registers' own words, not this page's.

  1. CMS-0057-F

    by 2027-01-01CMS Interoperability & Prior Authorization Final Rule

    Patient Access, Provider Access, Payer-to-Payer, and Prior Authorization APIs. Operational provisions live since January 2026; API provisions land 2027-01-01 for MA and Medicaid/CHIP FFS (managed care and QHP variants follow by rating/plan year).

    CMS Interoperability & Prior Authorization Final Rule (CMS-0057-F) →The plain-language card →

  2. CMS-0053-F

    by 2028-05-26Claims attachments (adopted standards: X12N 275/277 v6020 + HL7 C-CDA)

    Adopts HIPAA claims-attachment standards. The adopted stack is X12 + C-CDA, not FHIR; CDex is the FHIR-side attachments pattern to watch.

    CMS-0053-F Claims Attachments fact sheet →The plain-language card →

  3. CMS-0062-P

    proposed — no adopted date2026 CMS Interoperability Standards and Prior Authorization for Drugs Proposed Rule

    PROPOSED, not adopted. Would make several currently-recommended HL7 FHIR IGs required. It carries NO compliance date this registry can state: the rule's own compliance clock runs from the date it is finalized, and it has not been finalized. Secondary commentary cites October 1 2027 for most implementation timelines and 60 days post-finalization for endpoint reporting; both are attributed readings, not adopted deadlines, which is why neither appears as a date field here. The rule names IGs but NOT versions, so no recommendedVersion is pinned below — any version pairing shown elsewhere in this product is ImOnFHIR's own reading of what is current, not the rule's. The IG list here is deliberately conservative: it holds only the guides the primary CMS material names directly.

    Federal Register: Interoperability Standards and Prior Authorization for Drugs (proposed rule) →CMS: 2026 Interoperability Standards and Prior Authorization for Drugs Proposed Rule (CMS-0062-P) →

Named by no current rule

6 packages

The larger half of the ecosystem. Regulation names a handful of guides; the rest exist because implementers need them — which is a fact about how this ecosystem actually works, not a gap in the map.

How to read this

The basis chips are the mandate register’s own vocabulary: recommended means the rule recommends that guide at a stated version; named means a proposal names it without adopting anything; supporting is underlying content profiles; and related is the honest outlier — a FHIR-side cousin of a rule whose adopted standard is not FHIR at all. One of the three rules on this page is exactly that case, and knowing it is worth more than a tidier diagram.