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 X12 278 and attachment exchange 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
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
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 X12 278 and attachment exchange 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?