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 audit trail and decision provenance 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.
HL7 Da Vinci CRD v2.2.1
CRD enables a provider workflow to query a payer for patient- and service-relevant coverage expectations such as whether prior authorization is required, documentation expectations, first-line treatments, or related instructions. It does not itself submit the authorization request. Requirement discovery is a distinct workflow stage. A provider should know that authorization is required and what comes next before assembling or submitting a case; CRD addresses that stage rather than final determination.
HL7 Da Vinci DTR v2.2.0
DTR lets payers express documentation requirements computably and allows provider systems or SMART applications to retrieve existing clinical data, prompt for missing information, and create structured responses for downstream authorization or claims workflows. DTR addresses one of the principal causes of authorization delay: incomplete or incorrectly structured clinical information. Buyers should evaluate computable policy governance and user review, not only form rendering.
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.
NCPDP SCRIPT v2023011
SCRIPT is the core U.S. e-prescribing standard and includes transactions for electronic prior authorization and medication history. Version 2023011 adds required ePA transactions and other prescribing enhancements. Pharmacy ePA follows a distinct NCPDP transaction path from medical-service prior authorization. Buyers must confirm supported SCRIPT versions, network participants, attachments, renewals, and transition readiness.
NCQA UM Accreditation
NCQA UM Accreditation evaluates organizations that make utilization decisions against a framework for objective, evidence-based, fair, and timely operations. Detailed standards cover clinical information, review processes, timeliness, appeals, and related controls. Accreditation changes the evaluation from feature presence to controlled operation. Technology can support evidence, timelines, reviewer qualification, and audit trails, but the organization—not the software—holds accreditation.
URAC Health UM Accreditation
URAC accredits health utilization-management organizations against standards intended to support effective, transparent, and efficient UM functions, including organizational accountability and consumer protections. URAC status can be relevant evidence about an organization's operating controls, but accreditation scope and expiration must be checked. A technology platform cannot inherit the accreditation of a service organization merely through integration.
CMS Part C UM Annual Data Submission
The collection requires Medicare Advantage organizations to submit information about internal coverage criteria used by the organization or delegated entities to process Part C prior authorizations, increasing oversight of policy and delegation practices. The submission creates a separate evidence requirement around the criteria used to make Part C authorization decisions. Buyers need policy provenance, delegation visibility, and extractable records in addition to transaction throughput.
Operating domains
Clinical appropriateness and decision integrity
Risk that clinical criteria, benefit rules, extracted evidence, reviewer qualifications, automation, or escalation logic produce inconsistent, unsupported, biased, or clinically inappropriate authorization recommendations or determinations.
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.
Delegation, governance, and accountability
Risk that a health plan cannot demonstrate who owns policy, clinical review, decision authority, notices, appeals, metrics, accreditation, and oversight when work crosses internal teams and delegated organizations.
Denials, appeals, and member rights
Risk that adverse determinations lack specific, understandable reasons; appeal rights and peer review are hard to access; deadlines are missed; or later reversals cannot be analyzed without compromising member protections.
Transparency, metrics, and comparability
Risk that authorization counts, approval rates, denial rates, appeal outcomes, response times, and automation claims use incompatible populations, definitions, periods, or denominators and therefore mislead buyers or the public.
Policy, benefit, and change management
Risk that authorization lists, benefit rules, medical policies, clinical criteria, coding, service-line scope, or delegated arrangements change without accurate versioning, implementation, provider notice, and downstream testing.
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 audit trail and decision provenance 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
NCPDP SCRIPT 2023011 becomes the required e-prescribing version — Pharmacy ePA stakeholders need a version-specific migration, testing, and trading-partner readiness plan distinct from medical-service FHIR implementation.
First Medicare Part C UM annual data submission becomes due — Coverage-criteria provenance, delegation records, version control, and regulator-ready exports become more explicit enterprise requirements.
Seven additional DMEPOS codes enter nationwide required prior authorization — DME suppliers and patient-access teams need code-level, date-specific requirement discovery and must also track supplier exemption status.
Initial CMS-0057 prior-authorization metrics become due — Plan-level public disclosures create a new benchmarking input, but files require normalization by entity, population, period, request type, and denominator before comparison.
GuidingCare adds a multi-vendor Decision Intelligence Ecosystem — Health plans can evaluate a modular core-platform-plus-intelligence architecture, increasing the importance of interface ownership, policy location, reasoning provenance, and override records.