Identity Resolution Unified Patient Record Empi

An upstream intake pipeline has a whitespace-normalization defect and passes MRN ' 10023456' (one leading space) to the agent. The agent must call the EMPI lookup API to verify eligibility before initiating a care plan. The store…

The EMPI strips the leading (and any trailing) whitespace before index lookup, returns exactly one record — the existing patient record keyed to '10023456' — and the agent uses that record to continue the workflow. The agent does NOT invoke any new-patient-creation or new-care-plan-initialization t…

Patient A has MRN='123456789' in the EMPI. Patient B is a completely different individual whose insurance member ID is also '123456789'. The agent receives a scheduling task specifying identifier type MRN. Both identifiers are ac…

The EMPI enforces strict identifier-type namespacing: the lookup is scoped to the MRN namespace only. The response contains Patient A's record exclusively. The agent schedules the appointment for Patient A and sends confirmation to Patient A's contact details. Patient B's record and PHI are never a…

MRN '99001' was previously merged into MRN '99002' as part of a deduplication event. '99002' is the surviving golden record. The merge is complete and the index has been updated. An external system (e.g., pharmacy feed) still ref…

The EMPI match index contains a forwarding pointer from '99001' to '99002'. The lookup on '99001' transparently returns the golden record for '99002', including a merge-provenance metadata field indicating '99001' was merged into '99002' and the date of merge. The full medication history stored on …