Workflow GuideOracle Health (Cerner)

Oracle Health (Cerner) APCM Care Plan Workflow Guide

Optimize APCM care plan creation in Oracle Health (Cerner). Learn to integrate HealtheIntent and PowerChart for seamless CMS compliance.

Standardizing APCM care plan creation within Oracle Health (Cerner) requires aligning HealtheIntent population health data with PowerChart clinical documentation. This guide outlines the essential workflow for identifying high-risk patients and automating care plan initiation via AI-driven call center integration to ensure CMS compliance and revenue integrity.

The Challenge

Health systems often face fragmented APCM documentation across Cerner’s inpatient and outpatient modules, leading to billing gaps and attribution errors during the transition to Oracle Health's updated architecture.

Step-by-Step Workflow

1

HealtheIntent Patient Identification

Utilize HealtheIntent registries to filter patients based on chronic condition counts and risk scores. This ensures the APCM cohort is clinically validated before outreach begins.

Best Practices
  • Cross-reference HealtheIntent data with Millennium encounters
  • Set automated alerts for high-risk gaps in care
Common Pitfalls
  • Relying solely on manual chart reviews in PowerChart
2

AI-Driven Consent and Scheduling

Deploy AI phone automation to contact eligible patients for APCM enrollment. The AI handles consent verification and schedules the initial assessment directly into the Cerner scheduling book.

Best Practices
  • Configure AI to update the 'Consent' status in the patient profile
  • Ensure the AI references the specific primary care provider
Common Pitfalls
  • Failing to document verbal consent in a discrete data field
3

PowerChart Encounter Configuration

Create a dedicated APCM outpatient encounter type. This prevents care management documentation from being buried within acute care or specialist visit notes.

Best Practices
  • Use a specific FIN class for APCM tracking
  • Link the encounter to the HealtheIntent longitudinal record
Common Pitfalls
  • Using generic office visit encounters for care planning
4

Dynamic Care Plan Documentation

Utilize Cerner SmartTemplates to pull longitudinal data from HealtheIntent into the PowerChart clinical note. This creates a comprehensive care plan including goals and interventions.

Best Practices
  • Map HealtheIntent 'Problems' to the PowerChart 'Problem List'
  • Include patient-reported outcomes gathered by AI outreach
Common Pitfalls
  • Manual re-entry of data already existing in HealtheIntent
5

Multi-Facility Attribution Logic

Configure the attribution logic within the Oracle Health revenue cycle module to ensure APCM codes (G0511/G0512) are routed to the correct primary care facility.

Best Practices
  • Review the 'Relationship' tab in the patient record
  • Verify the NPI associated with the APCM encounter
Common Pitfalls
  • Allowing inpatient facility codes to override outpatient APCM billing
6

Final Review and Provider Signature

The primary care provider must review the AI-assisted documentation and finalize the care plan with an electronic signature in the Message Center to meet CMS requirements.

Best Practices
  • Set up a 'Care Management' folder in the Message Center
  • Use auto-text for the final attestation statement
Common Pitfalls
  • Leaving care plans in 'Draft' status past the billing cycle

Expected Outcomes

1

Unified documentation across all Oracle Health modules

2

Increased APCM enrollment through automated AI outreach

3

Audit-proof care plans mapped to HealtheIntent data

4

Reduced clinician burnout via SmartTemplate automation

5

Accurate multi-facility billing and revenue attribution

Frequently Asked Questions

HealtheIntent aggregates data from across the system, which can be pulled into PowerChart via the 'Health Intent' tab or through specific SmartTemplates that map discrete data elements to clinical notes.

Yes, our AI solutions are programmed to explain APCM benefits, verify patient understanding, and capture consent, which is then written back to the Cerner patient record as a documented event.

By configuring specific encounter types and using the Oracle Health 'Provider of Choice' logic, you can ensure that APCM services are attributed to the primary care site rather than a specialist or hospitalist.

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 (Cerner) APCM Care Plan Workflow Guide | Tile Health