Jump to a section
A registration desk sees two encounters for the same person on Tuesday morning. One could be a duplicate created during check-in. The person could also have attended two departments. Merging on name and date alone creates as much uncertainty as leaving both records open.
Reconstruct the visit
Ask the registration lead to compare appointment references, location, check-in time and the service entries attached to each encounter. Suppose the records were opened four minutes apart, share one appointment and point to one attendance acknowledgement. That makes them candidates for review. A second department with its own booking and attendance record would lead the review in a different direction.
Give billing a decision it can use
Record which encounter may proceed, who made the decision and what happens to each attached entry. Leave a cross-reference on the resolved exception so a later claim query can be traced. If either encounter has already reached a billing batch, involve the batch owner before correcting it. Count open duplicates and the age of the oldest case to see whether registration issues are accumulating upstream.
More to discover in Numerish.
Explore related insights and practical enterprise workflows.



