Automating Prior Authorization: eMDs Da Vinci PAS Integration

Streamlining Prior Authorization in eMDs with Da Vinci PAS

Klivira's platform leverages eMDs' CGM APIs to enable a modern, standards-based prior authorization workflow. This integration allows ambulatory practices to transition from fragmented, manual processes to an automated system that utilizes HL7 FHIR R4 and the Da Vinci PAS Implementation Guide, enhancing efficiency and data accuracy within the eMDs ecosystem.

The Operational Impact of Pre-PAS Workflows in eMDs Environments

• **Per-payer custom integration:** Prior authorization coordinators using eMDs must navigate disparate payer-specific portals (e.g., Availity, UHCprovider.com, CignaforHCP) or rely on fax, each requiring unique manual steps or custom API integrations.
• **Unstructured clinical attachments:** Clinical documentation is often submitted as PDFs or scanned documents rather than structured FHIR resources, limiting automated review by payers and slowing decision turnaround.
• **No standardized response semantics:** Approval, denial, and pending statuses vary by payer, requiring manual interpretation and mapping of decision codes back into eMDs.
• **Slow decision turnaround:** The reliance on unstructured documentation and manual processes for clinical-necessity reviews significantly extends the time to obtain PA decisions for eMDs patients.

Klivira's Automated Da Vinci PAS Workflow within eMDs

With Klivira, the prior authorization process within eMDs transforms into an end-to-end FHIR-based workflow. Klivira integrates with eMDs' order entry points via CGM APIs to initiate and manage PAs, ensuring structured data exchange and automated status updates directly within the EMR's order record.

End-to-End FHIR-Based Prior Authorization with eMDs and Klivira

• **Pre-PA coverage discovery via Da Vinci CRD:** At order entry within eMDs, Klivira's CDS-Hook integration can surface payer coverage requirements and PA rules, using structured `Claim` resources to inform providers before submission.
• **Documentation assembly via Da Vinci DTR:** Where payers support it, Klivira renders DTR questionnaires, populating clinical data directly from eMDs' FHIR resources (via CGM APIs) to assemble structured documentation.
• **PAS submission:** Klivira constructs a `Claim` resource per the Da Vinci PAS IG, including structured clinical documentation as `DocumentReference` and related FHIR resources, and submits it to the payer's PAS endpoint via the `$submit` operation.
• **Synchronous or asynchronous response:** The payer's PAS endpoint returns a `ClaimResponse` resource, which Klivira parses into a consistent workflow state taxonomy, regardless of payer-specific codes.
• **Status tracking:** Klivira monitors pending statuses via PAS inquiry operations or webhook events, providing real-time updates on PA decision states.
• **Response back into eMDs:** The `ClaimResponse` decision, including authorization numbers and any conditions, is written back to the eMDs order record as a structured outcome, ensuring the EMR reflects the latest PA status.

Navigating Payer Conformance and CMS-0057-F for eMDs Practices

Klivira helps eMDs users navigate the evolving landscape of payer compliance. We track payer conformance with Da Vinci PAS and CMS-0057-F requirements, which mandates FHIR-based Prior Authorization APIs for impacted payers (Medicare Advantage, Medicaid managed-care, CHIP managed-care, QHP-on-FFM) by January 1, 2027. Klivira ensures your eMDs workflow adapts as payers adopt these standards, leveraging both test and production endpoints.

Beyond PAS: Klivira's Comprehensive PA Strategy for eMDs

While Da Vinci PAS represents the future of prior authorization, Klivira provides a holistic solution for eMDs users. For payers not yet PAS-conformant, Klivira intelligently routes submissions via traditional X12 278 EDI transactions (often with X12 275 for attachments) or through existing provider portals. This hybrid approach ensures continuous PA automation for your eMDs practice, regardless of payer readiness, including handling FHIR-to-EDI mapping where payer-side systems still rely on X12.