Automating Oracle Health (Cerner) Mobility Scooter Prior Authorization

The Challenge of Mobility Scooter Prior Authorization within Oracle Health (Cerner)

Mobility scooters, vital for patient independence, are subject to stringent medical necessity review across commercial, Medicare Advantage, and Medicaid managed care plans. Within Oracle Health (Cerner) environments, initiating these prior authorizations often forces clinicians and PA coordinators into inefficient workflows, including navigating away from PowerChart to external payer portals, managing fax submissions, and manually tracking complex requirements. This fragmented process exacerbates administrative overhead and can delay patient access to critical DME.

Klivira's Integration Approach for Oracle Health (Cerner) Mobility Scooter PA

• **SMART on FHIR Launch:** Klivira integrates as a SMART on FHIR application, launching directly from PowerChart to maintain patient and encounter context, minimizing context switching for mobility scooter orders (src: smart-app-launch).
• **FHIR R4 API Utilization:** We leverage Oracle Health's FHIR R4 APIs, including US Core resources and Cerner-specific extensions, to programmatically access patient demographics, diagnoses, and relevant clinical documentation for mobility scooter PAs (src: cerner-fhir, oracle-health-developer).
• **CDS Hooks for Order Entry:** Klivira can integrate via CDS Hooks at the point of order entry (e.g., `order-select`, `order-sign`) within Cerner to surface real-time prior authorization requirements for mobility scooter prescriptions (src: cds-hooks).
• **HL7 v2 Interoperability:** For legacy workflows, Klivira maintains HL7 v2 interface capabilities, ensuring compatibility with existing production Cerner deployments that rely on ADT or ORM/ORU messages for event triggers.

Streamlining Clinical Documentation for Mobility Scooter Medical Necessity

A critical aspect of mobility scooter prior authorization is demonstrating medical necessity, which requires comprehensive clinical documentation. Klivira automates the aggregation of relevant data points from PowerChart, including physician orders (ServiceRequest), patient conditions (Condition), physical therapy evaluations (DocumentReference), and functional assessments (Observation). This data is efficiently compiled into a structured PA packet, reducing manual chart review and ensuring all necessary evidence supports the mobility scooter request.

Automated Submission and Status Management for DME Prior Authorizations

Klivira automates the submission of mobility scooter prior authorizations through multiple channels, including X12 278 transactions, direct payer portal connectivity, and ePA platforms. Once submitted, Klivira continuously monitors the authorization status, capturing updates and integrating them back into the Cerner workflow. This can involve routing status changes to Cerner's Message Center or, where supported by customer configuration, writing back to specific patient chart sections via FHIR APIs, reducing manual follow-up calls and improving transparency.

Key Data Elements for Mobility Scooter PA from Oracle Health (Cerner)

• **ServiceRequest:** Physician orders for the mobility scooter (src: cerner-fhir).
• **Patient / Encounter:** Demographics and relevant visit context (src: cerner-fhir).
• **Condition:** Diagnoses supporting the medical necessity (src: cerner-fhir).
• **Observation:** Functional status, mobility assessments, and vital signs (src: cerner-fhir).
• **DocumentReference:** Clinical notes, physical therapy reports, and other supporting documentation (src: cerner-fhir).
• **Coverage:** Patient's insurance policy details (src: cerner-fhir).