Streamlining Prior Authorizations with CompuGroup (Aprima) Da Vinci PAS Integration

Klivira integrates seamlessly with CompuGroup (Aprima) to implement Da Vinci PAS, transforming prior authorization submission for ambulatory practices by leveraging structured FHIR data exchange.

Revenue cycle directors and prior authorization coordinators at ambulatory practices using CompuGroup (Aprima) face mounting administrative burdens. Manual PA processes, reliance on disparate payer portals, and the submission of unstructured clinical documentation contribute to delays and denials. Klivira's platform automates and standardizes these workflows, integrating directly with Aprima to streamline prior authorizations.

Klivira's Da Vinci PAS Workflow within CompuGroup (Aprima)

Klivira's integration with CompuGroup (Aprima) leverages the EMR's CGM APIs to embed a Da Vinci PAS-conformant workflow directly into the practice's existing processes. This enables a standardized, FHIR-native approach to prior authorization, from initial order entry through decision tracking and documentation.

End-to-End Prior Authorization Steps in Aprima

**Coverage Requirements Discovery (Da Vinci CRD):** At the point of order entry in Aprima, Klivira's CDS-Hook integration triggers a Da Vinci CRD query via CGM APIs, identifying payer-specific prior authorization requirements before the service is even ordered.
**Structured Documentation Assembly (Da Vinci DTR):** When a PA is required, Klivira renders payer-specific Da Vinci DTR questionnaires, populating them with relevant clinical data directly from Aprima's FHIR resources via CGM APIs, eliminating manual data entry.
**PAS Submission:** Klivira constructs a FHIR `Claim` resource with structured clinical documentation (e.g., `DocumentReference` resources) and submits it to the payer's Da Vinci PAS endpoint using the `$submit` operation.
**Automated Status Tracking:** Klivira tracks the `ClaimResponse` decision, parsing synchronous or asynchronous responses into a consistent workflow state taxonomy, and supports inquiry operations for pending statuses.
**Decision Write-Back to Aprima:** The final authorization decision, including the authorization number and any conditions, is written back to the relevant order record within Aprima as a structured outcome via CGM APIs.

Leveraging Aprima's CGM APIs for FHIR-Native Data Exchange

Klivira utilizes CompuGroup (Aprima)'s CGM APIs to facilitate a robust, FHIR-native data exchange. This direct integration allows for the extraction of structured patient demographics, clinical notes, and order details from Aprima, and the subsequent write-back of prior authorization decisions. This approach minimizes the need for manual data abstraction and ensures that the EMR remains the single source of truth for patient care and administrative data.

Addressing Prior Authorization Challenges for Ambulatory Practices

For ambulatory practices, the complexity of prior authorizations can divert significant staff time from patient care. Klivira's Da Vinci PAS integration with Aprima directly addresses common pain points: replacing per-payer custom integrations with a uniform FHIR interface, submitting structured clinical data instead of unstructured PDFs, and standardizing response semantics across diverse payers. This enables faster decision turnaround and reduces administrative overhead.

Navigating Evolving Standards and Payer Conformance

Klivira's platform is designed to adapt to the evolving landscape of prior authorization standards, including the requirements of CMS-0057-F. While many payers are progressing towards Da Vinci PAS conformance, Klivira ensures continuity by routing requests via PAS-first for conformant payers and falling back to X12 278, clearinghouse, or payer portal submissions for those not yet fully transitioned. This hybrid approach guarantees comprehensive coverage for Aprima users.

Key Benefits of Klivira's Aprima + Da Vinci PAS Integration

**Reduced Manual Effort:** Automates data extraction and submission, reducing staff time spent on administrative tasks.
**Improved Data Accuracy:** Submits structured FHIR data directly from Aprima, minimizing errors associated with manual entry.
**Faster Decision Turnaround:** Enables payers to process requests more efficiently due to structured data, potentially accelerating approvals.
**Standardized Workflows:** Provides a consistent prior authorization process across multiple payers, regardless of their specific portal or API.
**Enhanced Compliance:** Supports evolving regulatory requirements like CMS-0057-F through FHIR-based API conformance.
**Better Visibility:** Centralized tracking and status updates provide clear insights into all prior authorization requests.

Frequently asked questions

How does Klivira integrate with CompuGroup (Aprima) for prior authorizations?

Klivira integrates with CompuGroup (Aprima) through its CGM APIs, enabling direct, secure exchange of FHIR-based data. This allows Klivira to pull necessary clinical information from Aprima for prior authorization requests and write back authorization decisions directly into the EMR.

What is Da Vinci PAS, and how does it benefit Aprima users?

Da Vinci PAS (Prior Authorization Support) is an HL7 FHIR-based implementation guide that standardizes the electronic submission and response for prior authorizations. For Aprima users, it means moving from disparate, manual processes to a consistent, automated workflow that uses structured data, leading to faster decisions and reduced administrative burden.

Does Klivira's integration support all payers, even those not fully Da Vinci PAS conformant?

Yes, Klivira's platform is designed for comprehensive payer coverage. While we prioritize Da Vinci PAS for conformant payers, our system intelligently routes requests via X12 278, clearinghouses, or payer portals for those not yet supporting the Da Vinci PAS standard, ensuring all prior authorizations are processed efficiently.

How does Klivira handle clinical documentation from Aprima for PA submissions?

Klivira leverages Da Vinci DTR (Documentation Templates and Rules) where supported by payers, to guide the assembly of structured clinical documentation directly from Aprima's FHIR data via CGM APIs. This replaces the submission of unstructured PDFs with discrete, machine-readable data, enabling more efficient payer-side review.

What kind of data is exchanged between Aprima and Klivira for prior authorizations?

Klivira exchanges patient demographics, clinical notes, diagnoses, procedure codes, and order details from Aprima. In return, Klivira writes back the prior authorization decision, authorization number, and any specific conditions or denial reasons into the relevant patient records within Aprima, ensuring complete documentation.