CMS's Prior Authorization API Mandate Hits January 2027: What It Changes for OB

Two federal deadlines land on January 1, 2027, and most obstetric practices are tracking only one of them. The CPT 2027 maternity code set gets all the attention. The other is CMS’s Interoperability and Prior Authorization rule, CMS-0057-F, which requires impacted payers to stand up FHIR-based prior authorization APIs on that same date.

For obstetrics, this one is quietly good news. But only if you know what is arriving and ask your vendors the right questions before it does.

What the Rule Actually Requires

CMS-0057-F applies to Medicare Advantage organizations, state Medicaid and CHIP fee-for-service programs, Medicaid and CHIP managed care plans, and qualified health plans on the federally facilitated exchanges. It does not directly cover commercial group plans, though history suggests they follow.

The rule has two halves. The first half, operational turnaround standards, took effect January 1, 2026: expedited prior authorization decisions within 72 hours, standard decisions within seven calendar days, and a specific reason required on every denial. The second half is the technical build, due January 1, 2027:

• Prior Authorization API: payers must expose, through a FHIR API, which items and services require prior authorization, what documentation is needed, and the ability to submit a request and receive a response.
• Patient Access API: extended to include prior authorization status and decisions.
• Provider Access API: lets providers pull claims, encounter, and prior authorization data for patients attributed to them.
• Payer-to-Payer API: moves a member’s history when they change plans.

The technical foundation is the HL7 Da Vinci family of implementation guides: Coverage Requirements Discovery to ask whether authorization is needed, Documentation Templates and Rules to collect exactly what the payer wants, and Prior Authorization Support to submit it. These are not new standards invented for the rule; they are existing guides the rule finally gives payers a reason to implement.

The Part That Matters Clinically

The interesting piece is not faster faxes. It is that Coverage Requirements Discovery and Documentation Templates and Rules can fire inside the EHR at the moment of ordering. When an obstetrician orders serial growth scans, the workflow can, in principle, check coverage rules, surface the payer’s documentation requirements, pull the answers that already exist in the chart, and submit the request without the clinician leaving the order.

That collapses a multi-day administrative loop into a single interaction. It also moves the documentation burden from a coordinator reconstructing the chart after the fact to a system reading the chart in real time.

The catch is that this only works if the clinical data is structured and current. A payer rule that needs the estimated fetal weight percentile, the last three blood pressures, and the gestational age at the time of order can be answered automatically only if those values exist as data rather than as prose in a narrative note.

Questions to Ask Before January

Ask your EHR vendor

• Which Da Vinci implementation guides are supported in the version we are running, and which require an upgrade?
• Is Coverage Requirements Discovery wired into our order entry workflow, or only available as a standalone lookup?
• What is the go-live sequence, and what configuration work falls on us?

Ask your payers

• Which maternity services will remain subject to prior authorization after January 1, 2027?
• Will your Prior Authorization API be live on the deadline, or are you planning an enforcement-discretion posture?
• Are your documentation requirements published as machine-readable rules or as PDFs?

Ask yourself

• How many staff hours per month does maternity prior authorization consume today? Without that baseline you cannot tell whether 2027 improved anything.
• Which of our authorization denials are documentation failures rather than coverage decisions? Those are the ones the new plumbing actually fixes.

The Overlap Nobody Planned

Both deadlines land on the same day, and both depend on the same underlying capability: structured, complete, retrievable clinical data about the pregnancy. The practices that invest in that once will satisfy both requirements. The practices that treat them as two unrelated IT projects will do the work twice.