Define the operating boundary
A useful definition names the triggering event, required inputs, governing source, accountable owner, decision or action, exception path, evidence retained, and downstream handoff. Buyers should adapt those elements to their own population, jurisdictions, policies, systems, and control model before writing requirements.
The most important distinction is between a label and an operational capability. A provider may document medical-service electronic submission while depending on customer-supplied policy, licensed content, third-party data, integration partners, manual review, or services. The demonstration should expose those dependencies rather than hiding them behind a completed interface.
What a demonstration should prove
- Begin with representative source records and a named policy, standard, or controlled rule.
- Show the normal path, an ambiguous case, missing data, an exception, an override, and a material source change.
- Identify who can change rules, who can approve or reject, and how accountability is preserved.
- Trace every output back to inputs, versions, timestamps, user actions, and governing evidence.
- Export the resulting record and reconcile it with downstream systems and retained obligations.
Authority and operating context
CMS-0057-F
The rule requires impacted payers to improve prior authorization decision timeframes and denial reasons, publish aggregated prior authorization metrics, and implement FHIR-based Prior Authorization and other interoperability APIs. The prior authorization API provisions addressed by the final rule exclude drugs. It changes prior authorization from a mainly plan-specific operational process into a federally time-bounded, reportable, and API-enabled workflow for impacted non-drug items and services. It also creates concrete buyer requirements for denial reasons, metrics lineage, and CRD, DTR, and PAS implementation.
CMS-0062-P
The proposal would extend many electronic prior authorization, decision-time, transparency, API, and reporting policies to drugs and would adopt or update FHIR-based standards and implementation specifications for prior authorization transactions. The proposals are not final policy. It could materially reduce the current boundary between medical-service and drug prior authorization regulation while changing standards, response times, and metrics. Buyers must plan for the possibility without treating proposed provisions as current obligations.
HL7 Da Vinci PAS v2.2.1
PAS defines a FHIR R4 mechanism for submitting prior authorization requests, responses, status, updates, and supporting context in a way designed to map to applicable X12 transactions. It is one part of the Da Vinci burden-reduction workflow. PAS governs the request-and-response exchange after requirement discovery and documentation preparation. Claiming FHIR support without specifying PAS version, trading-partner workflow, X12 handling, and testing evidence is insufficient.
X12 278 Version 5010
The 278 implementation guide defines request and response transactions for admission certification, referrals, service certification, extensions, appeals, reservations, and cancellations between providers, utilization-management organizations, and intermediaries. Most current electronic medical-service prior authorization environments must account for the HIPAA transaction baseline even as CMS and Da Vinci workflows accelerate FHIR adoption. A credible architecture explains whether and where translation, enforcement discretion, or direct FHIR exchange applies.
Operating domains
Timeliness and access to care
Risk that authorization requirements, incomplete requests, review queues, handoffs, or unclear decisions delay or prevent clinically appropriate care beyond required or operationally acceptable timeframes.
Documentation completeness and burden
Risk that payer requirements are unclear or unavailable, relevant clinical evidence is missing or duplicated, and clinicians or staff must re-enter information across incompatible forms, portals, calls, or transactions.
Interoperability and transaction reliability
Risk that FHIR, X12, NCPDP, portal, fax, voice, identity, attachment, or legacy-system handoffs fail, lose meaning, duplicate work, or leave no reliable status and audit record.
Evidence and comparison limits
Official provider documentation can establish product positioning. Provider confirmation can clarify package or availability. Independent observation requires a disclosed scenario, environment, date, inputs, and reproducible result. None of those sources alone establishes buyer-specific legal, clinical, regulatory, quality, or operational fitness.
Buyer questions
- What exact outcome and evidence should medical-service electronic submission produce?
- Which source, version, and customer facts govern the workflow?
- Which decisions remain human and who is accountable for them?
- What is native, configured, integrated, service-delivered, or planned?
- How does a changed source affect open and historical records?
Recent changes
EviCore begins handling additional Cigna authorization categories — Provider routing logic and training materials must reflect service, plan, date, and exclusion details rather than a generic payer-to-delegate relationship.
HL7 publishes updated CRD, DTR, and PAS implementation guides — Vendor and payer conformance claims should identify the exact guide, version, workflow stage, test evidence, and production counterparty coverage.
Availity and Onyx launch a joint CMS-0057 platform — Health plans can source infrastructure and network reach together, but must still validate component ownership, conformance, production participation, and update responsibilities.