Medicare Beneficiary ID (MBI) Lookup - UHC and Palmetto eServices
Use Epic workqueue exports and an API to pull patient demographics, retrieve Medicare Beneficiary Id's from UHC and Palmetto eServices, and stage the values for Epic import.
DOMAIN
Revenue Cycle Front
FUNCTION
Insurance Verification & Eligibility
Category
Eligibility Verification
Status
Live
AUTHORING ORGANIZATION
Duke
PERFORMANCE METRIC
Insurance Verification Rate
Automation Tool
Blue Prism
TECHNOLOGIES
RPA
API
Applications
EPIC
UHC Portal
HB | PB
N/A
Automation value
(as reported)
23310
Problem Statement
Coverage and benefit details must be confirmed and entered accurately before billing, and doing this manually at volume is slow and error-prone. Medicare claims require the patient's Medicare Beneficiary ID, but it isn't always on file, so staff have to take each patient's demographics, look the patient up on a payer site, and retrieve the MBI before the claim can go out. Doing this lookup by hand across a workqueue is repetitive, and a missing MBI holds up the claim.
Automation Solution
This automation uses an Epic workqueue export and an API to pull patient demographics, retrieves Medicare Beneficiary IDs from UHC and Palmetto eServices, and stages the values on an import spreadsheet for loading into Epic.
Automation Resources
PDDs, Process Flows, Presentations, and Assessments
Design Document - MBI
PDD
This is some text inside of a div block.
Related Automations
No related automations
Comments
Loading
Someone is typing
No Name
Set
4 years ago
This is the actual comment. It's can be long or short. And must contain only text information.
Problem Statement
Coverage and benefit details must be confirmed and entered accurately before billing, and doing this manually at volume is slow and error-prone. Medicare claims require the patient's Medicare Beneficiary ID, but it isn't always on file, so staff have to take each patient's demographics, look the patient up on a payer site, and retrieve the MBI before the claim can go out. Doing this lookup by hand across a workqueue is repetitive, and a missing MBI holds up the claim.
Automation Solution
This automation uses an Epic workqueue export and an API to pull patient demographics, retrieves Medicare Beneficiary IDs from UHC and Palmetto eServices, and stages the values on an import spreadsheet for loading into Epic.
Automation Resources
Design Document - MBI
Related Automations
Comments