Move money from your bank to a stranger's bank and it arrives in seconds. Switch doctors across the street and your records arrive by fax, by CD, or not at all. Same you, same decade. The difference isn't technology —…

CMS-0053-F (finalized March 24, 2026; Federal Register 2026-05676) adopts HIPAA standards for health care claims attachments and electronic signatures. The adopted stack pairs **X12N 275/277 (v6020)** for the transact…

CMS-0057-F is the mandate that turns payer FHIR from "nice directory" into operational APIs. Operational provisions around prior-auth decision timing and denial reasons are already live (since January 2026). The API p…

Da Vinci Payer Data Exchange (PDex, `hl7.fhir.us.davinci-pdex`) defines how payers expose a member's health history as US Core-shaped clinical FHIR: payer→provider (CDS Hooks + SMART), payer→payer (member-authorized),…

HL7's Payer/Provider Information Exchange Work Group (PIE) — formerly the Attachments WG; the public URL still says "claims" — owns provider↔payer supplemental-information exchange: claims attachments and attachment p…

This is a curated, dated list — not an automated feed. We review it monthly. Items graduate into library cards or lab work when their trigger fires.

If you run technology at a health plan, three federal rules define your next 24 months. This card is the one-page version.

The FHIR world looks sprawling until you see that it's five things. Here's the map, with the doors we actually use.

[chat.fhir.org](https://chat.fhir.org) is the FHIR community's Zulip: the de facto real-time brain of the standards world. Public read without login; free account to post. Streams that matter for ImOnFHIR builders: **…

Da Vinci Unsolicited Notifications (`hl7.fhir.us.davinci-alerts`) is a FHIR **messaging** framework for event notifications. The shipped use case is admit/transfer/discharge; the IG's future scenario list explicitly i…

HL7 ships a paid on-demand bundle — "Da Vinci Provider/Payer FHIR Implementation Guide Essentials" — in three modules: FHIR core technologies, Burden Reduction / prior auth (explicitly CMS-0057-aligned), and Payer Dat…

The FHIR package registry is the npm-style ecosystem for Implementation Guides. Packages are tarballs of an IG's conformance resources, semver-versioned (`hl7.fhir.us.davinci-pas#2.1.0`). You can query and download fo…

The FHIR Tooling Extensions IG (`hl7.fhir.uv.tools`) is not a patient-facing clinical guide. It is the extensions, code systems, and logical models used *inside* the FHIR toolchain — the official validator, code gener…

Every published FHIR Implementation Guide is supposed to maintain a `package-list.json` at its canonical URL: a machine-readable version history with `package-id`, `canonical`, and a `list[]` of versions. Each entry c…

Parameterized ValueSets are a mechanism (documented in the FHIR Tools IG) for value sets whose expansion depends on a runtime parameter — choose country, then the state list narrows. The pattern is built from extensio…

HL7's Orchestration, Services, and Architecture Work Group (renamed from "Services Oriented Architecture") historically owns service functional models — identification / MPI-style services, de-identification service c…