Workflow GuideOracle Health (Cerner)

Oracle Health APCM Billing & Claims Submission Workflow

Master APCM billing in Oracle Health (Cerner). Learn to integrate HealtheIntent data and PowerChart workflows for accurate APCM claims submission.

Successfully billing for Advanced Primary Care Management (APCM) within the Oracle Health (Cerner) ecosystem requires a precise synchronization between clinical documentation in PowerChart and the revenue cycle management in Millennium. This guide details how to leverage HealtheIntent data and AI-powered call automation to ensure every minute of care coordination is captured, documented, and bi...

The Challenge

Many health systems using Oracle Health struggle with fragmented workflows where care management time spent on the phone is never captured in Millennium, leading to significant revenue leakage and compliance risks during APCM audits.

Step-by-Step Workflow

1

Configure APCM-Specific Encounter Types

Update the Cerner Millennium encounter hierarchy to include specific encounter types for APCM. This allows the system to distinguish between standard outpatient visits and longitudinal care management, facilitating cleaner claim grouping and reporting.

Best Practices
  • Consult with your Oracle Health representative to ensure encounter types align with your specific Millennium version.
Common Pitfalls
  • Using standard 'Office Visit' encounter types which complicates APCM minute aggregation.
2

Synchronize HealtheIntent for Patient Identification

Utilize the HealtheIntent population health platform to identify patients with multiple chronic conditions. Push these patient lists into PowerChart Care Management worklists to ensure staff are targeting the correct APCM-eligible population.

Best Practices
  • Automate the data refresh between HealtheIntent and Millennium to ensure real-time eligibility tracking.
Common Pitfalls
  • Manual patient identification which leads to missing eligible candidates for APCM billing.
3

Deploy AI Call Handling for Time Capture

Integrate AI-powered call center solutions to automate the logging of care coordination minutes. The AI identifies the patient via phone metadata and pushes a structured activity log directly into the Cerner clinical note, capturing billable time without manual staff entry.

Best Practices
  • Ensure the AI integration uses the Oracle Health API for secure, HIPAA-compliant data transmission.
Common Pitfalls
  • Relying on staff to manually stopwatch their coordination calls, which typically results in 30% under-reporting.
4

Optimize PowerChart Documentation Templates

Build standardized PowerNote or Dynamic Documentation templates specifically for APCM. These templates must include discrete data fields for the care plan, patient consent, and coordination activities to meet CMS audit requirements.

Best Practices
  • Use 'SmartText' or tokens to pull in patient data directly from the HealtheIntent longitudinal record.
Common Pitfalls
  • Using free-text notes that do not contain the specific data elements required for APCM G-code substantiation.
5

Configure Multi-Facility Provider Attribution

In the Cerner Patient Accounting module, configure the provider-to-location mapping to handle multi-facility billing. Ensure that APCM services are attributed to the correct NPI and clinic location to prevent denials related to 'Place of Service' errors.

Best Practices
  • Test the billing path for outpatient practices that operate under a larger hospital's Cerner instance.
Common Pitfalls
  • Incorrectly attributing APCM codes to the inpatient facility NPI in a shared Oracle Health environment.
6

Execute Pre-Bill Scrubbing in ProFit

Run automated claim scrubbing within Cerner ProFit or your integrated revenue cycle tool. Specifically check for the presence of the required G-codes and ensure that the cumulative minutes for the month meet the APCM threshold before submission.

Best Practices
  • Set up custom alerts in ProFit for APCM claims that lack the documented patient consent flag.
Common Pitfalls
  • Submitting APCM claims before the end of the calendar month without verifying total monthly minutes.
7

Submit via Cerner EDI Gateway

Transmit the finalized APCM claims through the Cerner Electronic Data Interchange (EDI). Monitor the 277CA clearinghouse responses daily to identify and resolve any technical rejections related to the new APCM code sets.

Best Practices
  • Establish a specific work queue in Cerner for APCM denials to expedite the appeal process.
Common Pitfalls
  • Ignoring 277CA rejections, assuming the claims were accepted by the payer.

Expected Outcomes

1

100% capture of all phone-based care coordination minutes via AI automation.

2

Elimination of manual data entry errors in PowerChart for APCM documentation.

3

Significant reduction in claim denials through automated multi-facility attribution.

4

Audit-ready clinical documentation stored directly within the Oracle Health record.

5

Increased APCM revenue by identifying more eligible patients through HealtheIntent.

Frequently Asked Questions

HealtheIntent aggregates data from across the health system to identify chronic conditions that might not be documented in the current Millennium encounter, ensuring all eligible patients are captured for APCM billing.

Yes, by using the Oracle Health API, AI call handling solutions can push structured data and time-stamped logs directly into the patient's chart, satisfying the documentation requirements for APCM.

Oracle Health's multi-facility billing configuration must be used to attribute the APCM service to the primary care provider of record, ensuring the claim is sent with the correct NPI and facility identifier.

Ready to transform your oracle health (cerner) practice?

See how Tile Healthcare's AI call center can handle scheduling, triage, and patient communication for your practice.

Schedule a Demo
Oracle Health APCM Billing & Claims Submission Workflow | Tile Health