Automated Experian Health Duplicate MRN Detection
Every night, WebRun opens Experian Health, runs its identity matching across your patient population, finds probable duplicate medical record numbers referencing the same person in Epic, logs each candidate pair to Airtable with a match confidence score and the conflicting fields, and leaves the actual merge for your health information management team to confirm.
How do I find duplicate patient records before they cause a mix-up?
Every night, WebRun runs Experian Health's identity matching to find probable duplicate medical record numbers referencing the same patient across your Epic records. It logs each candidate pair to Airtable with a confidence score and the conflicting fields, and never merges anything itself, leaving the actual merge for your health information management team to confirm.
- Duplicate records are caught overnight instead of during an active visit
- HIM reviews a scored, documented queue instead of hunting for duplicates manually
- No record is ever merged automatically, only flagged for a human to confirm
Built for health information management teams · HIM directors · patient access departments · hospital data quality teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.experian.com/healthcarein a real browser with your saved login - no setup, no API keys. -
1
Experian Health - find probable duplicate patient records
experian.com
WebRun opens Experian Health to find probable duplicate patient records. - Open Experian Health and run the identity matching report across recent registrations
- Filter to pairs above your confidence threshold, typically a high-probability match
- Capture both medical record numbers and the confidence score for each pair
Done when Every probable duplicate pair above threshold is listed with its confidence score.
-
2
Epic - pull both records' conflicting details
epic.com
WebRun opens Epic to pull both records' conflicting details. - Open both records in Epic for each candidate pair
- Note which fields conflict, such as address, phone, or insurance on file, and which fields match exactly
- Flag any pair with an active inpatient stay or same-day appointment as needing faster review
Done when Each candidate pair has its conflicting and matching fields documented from Epic.
-
3
Airtable - log the merge candidate for HIM review
airtable.com
WebRun opens Airtable to log the merge candidate for HIM review. - Log each candidate pair to the duplicate record base with both MRNs, the confidence score, and the conflicting fields
- Mark the status as pending HIM review
- Never mark a pair as merged. That step is completed only by HIM staff inside Epic
Done when The Airtable base lists every new candidate pair as pending review, with none marked merged by WebRun.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does WebRun merge the duplicate records?
No. It never merges records or writes anything back to Epic. It only logs probable duplicate pairs for your health information management team to confirm and merge themselves.
How confident does a match need to be before it is logged?
Only pairs above your chosen confidence threshold are logged, typically a high-probability match, so HIM reviews a short, meaningful queue instead of every loose possibility.
What if a duplicate pair has an active inpatient stay?
It is flagged for faster review, since an unresolved duplicate is more likely to cause a mix-up while both records are actively being used.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.