Mercury One product overview

Mercury One is a Medical Practice Management solution that allows easy access to fundamentals of Revenue Cycle Management. Mercury One is a stepping stone from intermediate billing to advanced billing. Mercury One is offered exclusively on the cloud, with the highest level of security and allows users to access data anywhere 24/7.

Pros of Mercury One

Fully Customizable
Complete Billing System
Automated Processes

Cons of Mercury One

High learning curve due to the many functions available
Customization requires support
Needs better structured and planned implementation

Breakdown of core features

PAYMENT MANAGEMENT

Strict accounting controls with batch edit and posting management
Apply payments, adjustments to specific services and direct any excess amount to unapplied – which is tracked in the LIP
Account status codes from insurance ERA or manual EOB
Balance to check amounts in the ERA and reconcile in the batch prior to posting
Look for payments that create a credit balance and start the refund management process
Mercury One assigns contract payment and adjustment codes based on the insurance company or payer
Find recoupments and start the process, these show up in the check balance reconciliation process
ERA response file (ANSI 835) automatically applies payments, credits, adjustments to patient account with edits, audits and timers.
View/ print prioritized Working List for collectors’ tool. Denials are prioritized.
Status/eligibility via website
Plan control, number of visits, amount caps
Review pay history from patient account, correct LIP from patient account (supervisor role access)
Use up to 37,000 fee schedules to monitor contract compliance by financial type, provider, or facility
Activate modifiers at charge input, track price changes

PATIENT RECORD MANAGEMENT

Multi-level patient record: Demographic, Account Type, Coverage. Open new account for separate injuries but same demographic record
Attach images/PDF to patient record, e.g., letters received, internal documents, insurance required forms
Contact History with date, timestamp, input clerk initials , create letters or memo notes
Track patient referral source with velocity
Systematically print letters by system configured relational demand processing

CLAIMS PROCESSING

Part A and Part B claims, 1500, UB04 and 837. Part A can be departmental or service line based.
Auto scripting by insurance type, financial type and more
HIPPA compliant electronic claims, ANSI 837 formats direct to insurance companies or to clearing-house
Demand claims and/or statements from patient account inquiry as part of RCM

(Last updated on 10/25/2019 by Pam Van Loon)