IMPAX 6.5.1 Server Knowledge Base home > Understanding IMPAX Server > IMPAX single-cluster architecture
The following describes one way in which GPI (global patient identifier) can be propagated to IMPAX with a direct integration with an MPI (master patient index) system. It is just an example, not meant to represent the only way in which an MPI system can be implemented.

The HL7 ADT order transaction is sent to Connectivity Manager. The transaction does not include a GPI.
Connectivity Manager forwards the ADT order transaction to the MPI system.
Connectivity Manager does not send an N-Event notification to IMPAX at this point.
The MPI matches the patient and sends the HL7 ADT order transaction, now including a GPI, back to Connectivity Manager.
If a match cannot be made automatically, a temporary GPI is assigned.
Connectivity Manager now sends an N-Event notification to IMPAX. IMPAX updates the GPI for all records matching the local PID (patient identifier).
If configured to do so, IMPAX now performs enterprise prefetching based on that GPI.
See also
Prefetching studies from linked clusters
Supporting multiple patient domains in IMPAX using GPI
Topic number: 11524 Applies to: IMPAX 6.5.1 Server Knowledge Base |