Preparing for Oracle Health Patient Accounting starts with understanding how your organization gets paid today.
Revenue cycle leaders need to know where account information becomes incomplete. Clinical teams need to understand how documentation affects billing. Finance needs a plan for collecting outstanding balances during the transition.
Oracle Health Patient Accounting, commonly called OHPAC, supports billing and payment tracking across acute and ambulatory settings.
Evaluating the software also requires a careful review of your organization’s processes.
Healthcare IT Leaders has shared implementation lessons from a mature Oracle Health clinical environment. This checklist gives teams a practical way to organize their preparation.
For each item, record an owner and the evidence supporting readiness. Give unfinished work a due date.
Take a Quick Readiness Snapshot
Review the eight areas below and assign each one a status. Use Ready, In progress, At risk, or Not started.
A Ready rating requires approved evidence and a named operational owner.
Treat unfinished data, testing, legacy receivables, and transition work as immediate priorities.
Count the Ready ratings when you finish. Use every remaining item as an action list for the next planning meeting.
1. Review Data Dependencies Needed for Billing
Begin with your health plan and provider master files. Check identifiers, duplicate entries, and inactive records that still appear in operational workflows.
Review the charge description master (CDM) with revenue integrity leaders. Confirm who approves changes and maintains the CDM during implementation.
Establish owners for each department accountable for charge testing before go-live.
Evidence to collect: Approved mappings, documented corrections, and named data owners.
2. Document External Dependencies
Identify the organizations and applications involved in claim submission and payment processing.
Include clearinghouses, collection agencies, payment vendors, and reporting systems where applicable. Confirm each vendor’s responsibilities and testing schedule.
Document how staff will respond when a connection fails. Include responsibility for correcting rejected transactions and checking resubmissions.
Evidence to collect: An interface inventory with vendor commitments and escalation contacts.
3. Decide How to Manage Legacy Receivables
Agree on how outstanding accounts receivable will be handled after go-live.
Plan for additional staff capacity for old AR and new AR as your team learns the system.
Establish ownership for AR management vendors to ensure their needs are not overshadowed by broader go-live efforts.
Prepare organizational leadership for a possible 6-12 week reduction in cash.
Evidence to collect: An approved legacy receivables plan with ownership and staffing proposal.
4. Reserve Staff Time for Implementation
Identify the people who must make workflow decisions and validate the configuration.
Include patient access, health information management, revenue integrity, and finance. Clinical representatives should review changes affecting documentation or charge capture.
Estimate the time each person needs for testing and training. Arrange coverage for responsibilities they cannot continue during implementation.
Give department leaders a clear escalation process when decisions stall.
Evidence to collect: A staffing plan with protected project time and coverage arrangements.
5. Test Complete Financial Scenarios
Build test cases that follow an encounter through billing and payment posting.
Include corrected registration details, missing charges, and changes in insurance coverage. Test denied claims and transactions requiring manual review.
Validate applicable electronic claim submissions and remittance processing with your trading partners.
Reconcile expected results against actual results. Have operational owners review discrepancies before approving the workflow.
Evidence to collect: Completed test results, resolved defects, and operational approval.
6. Practice Daily Work Before Go-Live
Training should use the workflows staff will perform in their assigned roles.
Have billers practice correcting accounts and working exceptions. Ask supervisors to review queues and reassign work.
Confirm that staff have appropriate access. Update procedures so they explain how to handle problems and request help.
Include patient service teams in preparation. They need accurate information when patients ask about balances or statements.
Evidence to collect: Role-based training results, validated access, and updated procedures.
7. Create Cutover Transition Plan and Initial Support
Write down the sequence of activities required for go-live. Name the person responsible for each step.
Agree on downtime procedures and the conditions requiring a delay. Establish a contingency plan for interrupted billing or payment processing.
Staff the support team for expected operating hours. Define how it will prioritize problems affecting claims or cash collection.
Evidence to collect: A rehearsed cutover transition plan and an approved support schedule.
8. Establish Financial Measures Before the Change
Record current performance before implementation changes make comparisons difficult.
Agree on definitions for claim volumes, payment posting delays, and accounts receivable measures. Include operational indicators that help explain changes.
Assign owners to investigate unusual results. Finance and revenue cycle leaders should agree on when an issue needs escalation.
Evidence to collect: Baseline reports with agreed definitions and reporting owners.
Frequently Asked Questions
What should be complete before OHPAC testing begins?
Data owners, interface responsibilities, and test scenarios should be confirmed. Each scenario also needs specific charges, reimbursement and follow-up steps.
How should a health system manage legacy receivables?
Finance should approve a plan that addresses all legacy balances within 6 months. The plan should cover staffing, vendor utilization and expected yield for legacy AR.
Who should participate in an OHPAC readiness review?
Include revenue cycle, finance, patient access, health information management, technical teams, and clinical representatives.
Each group should approve the workflows and evidence within its area.
Use the Checklist in Your Next Planning Discussion
Review these items with your implementation team and Oracle Health representatives. Focus the discussion on unresolved dependencies and missing evidence.
When reviewing customer examples, ask how their starting environment compares with yours. Discuss staffing requirements and the problems encountered after go-live.
Use those answers to refine your own preparation. Set the implementation schedule around the work your organization can complete and validate.
Let’s Connect
Preparing for OHPAC? Healthcare IT Leaders can help assess readiness gaps and implementation priorities.