Ambulatory surgery centers have an MPI shape with one specific stress point. The same patient is touched by the referring physician's office, the ASC's pre-op intake, the anesthesia provider, the surgical team, the post-op recovery, and the discharge follow-up. Each of these touchpoints often runs in a different system. The patient's pre-op labs from a hospital reference lab, their imaging from a separate radiology group, and their referring physician's clinical notes all arrive in different formats. An MPI for an ASC either resolves this multi-source identity in real time or quietly forces the front desk into manual reconciliation on the morning of surgery.
This is the MPI products that come up most often in real ASC deployments in 2026, with the rough sense of where each one fits. For more on healthcare data exchange covering the wider context, the broader catalog is the place to start.
For the upstream picture, the complete guide to FHIR master patient index for payers in 2026 is a useful adjacent reference.
The MPI Products Worth Knowing for ASCs
The shortlist:
- MDMbox. Health Samurai's MPI product, picked by mid-size ASC groups that want a FHIR-native Patient match endpoint with low operational overhead.
- Smile Digital Health MPI. A commercial FHIR-native MPI common in ASCs that have settled on Smile for the underlying FHIR server.
- NextGate Match. A mature commercial MPI used by larger multi-site ASC chains that need depth across multiple practice management vendors.
- Verato Universal MDM. A reference-based MPI that uses an external identity graph, picked by ASCs that want lower false-positive rates on the morning of surgery.
- InterSystems IRIS for Health. A commercial offering picked by ASCs that are part of a hospital system already running IRIS.
What Matters Most for ASCs
Three things tend to drive the choice:
- Morning-of-surgery reconciliation. The MPI has to resolve a patient identity from the referring physician's record, the pre-op lab feed, and the ASC's own intake in a window of minutes, not hours.
- Multi-source data fusion. The MPI has to absorb records from labs, imaging groups, and referring physicians without forcing a per-source mapping.
- Insurance verification timing. The MPI has to support insurance verification at the moment of identity resolution, not as a separate batch step.
Most MPIs handle a baseline match. Fewer get the morning-of-surgery latency right. The multi-source data fusion done well is where the field thins out.
Which One Fits Which ASC
A mid-size single-location ASC with developer capacity often lands on MDMbox or Smile for the FHIR-native speed of deployment. A larger multi-site ASC chain tends to pick NextGate for the depth. An ASC that wants to reduce false-positive rates on the morning of surgery leans toward Verato. An ASC inside a larger hospital system usually inherits the IRIS MPI from the parent.
How to Run a Real ASC Evaluation
Vendor demos rarely include a real morning-of-surgery reconciliation with a delayed lab feed. Ask each product to ingest a cohort of real ASC patient records, absorb referrals from three different referring physician practices, resolve identity in under fifteen minutes from intake to surgery, and serve real-time lookups for the day-of-surgery workflow. The output of that exercise tells you more than any feature spec sheet.
For nearby setting profiles where similar capabilities matter, the best MPI tools for long-term care facilities in 2026 and top 4 MPI engines for school health program rosters walk through how the same vendors stack up.
Sources
- [PDQm Patient Demographics Match [ITI-119]](https://profiles.ihe.net/ITI/PDQm/ITI-119.html) - IHE Profiles
- $Match OperationDefinition - IHE PDQm build
- What is EMPI in Healthcare (referential matching for procedural settings) - Verato