Translate patient IDs between two hospitals
Goal: a partner hospital sends studies with its own MRNs. They should arrive in your PACS under your enterprise IDs, and the partner’s PACS, when it searches yours through the router, should see its own IDs.
1. The map
Section titled “1. The map”Configuration › Patient IDs › Add map: name North Hospital.
- From issuer
NORTH, To issuerENTERPRISE; - IDs not in the map: refused if every patient must be known (unknown ones go to the quarantine), or kept;
- keep the original ID in Other Patient IDs Sequence (on).
Then add the entries: Import a CSV of north-id,enterprise-id lines from the partner’s or your MPI, or add them one
at a time. Keep it up to date the same way; every change reaches the nodes within seconds.
2. Studies from the partner
Section titled “2. Studies from the partner”On the partner’s source, add a tag modification: PatientID MapPatientId, the map North Hospital. Their studies
arrive under your IDs; the original stays in Other Patient IDs Sequence.
3. The partner searching your archive
Section titled “3. The partner searching your archive”If the partner’s PACS searches and retrieves your studies through the router (its source has May query and retrieve), the same edit on its source makes the router translate both ways: its queries are mapped to your IDs, and the answers and instances back to its own.
4. Sending to the partner
Section titled “4. Sending to the partner”On a destination for the partner, the reverse needs a second map (enterprise → North), used by a MapPatientId edit on
that destination.
See Patient ID maps.
