Open-source Master Patient Index tooling for outpatient EHR integration in 2026 is more mature than it gets credit for. The tools have stabilized, the documentation has caught up, and the integration patterns are well-trodden enough that a small outpatient team can stand up a working MPI without buying a commercial license. The trade-off is the operations work, which never goes away on the open-source side.

The five tools below are the open-source options that hold up in outpatient EHR integrations. Each one supports FHIR Patient operations and has a credible reference deployment outside the demo environment. For the FHIR walkthrough archive on this site, the surrounding write-ups continue the picture.

What Open-Source Outpatient MPI Setups Need

A short list of capabilities matters most:

• A FHIR-conformant Patient API, including search, match, and merge operations.
• A matching engine that can be tuned without forking the codebase.
• An audit and merge history model that can survive without a vendor's support.
• Documentation good enough that the practice's IT can keep the deployment alive.

The five tools below clear most of those criteria, with varying levels of polish on the admin side.

The Five Tools

OpenEMPI is the most established open-source MPI in 2026. The matching engine is configurable, the data model is well-documented, and the deployment patterns are clear. Suitable for outpatient practices with someone who can own the operations work.

HAPI FHIR with the patient-matching module covers the basic MPI use cases as part of the broader HAPI ecosystem. The matching is simpler than OpenEMPI, but the integration with the rest of HAPI is seamless. A common pick for practices already running HAPI for storage.

JEMPI from the OpenHIE community is a newer entrant focused on FHIR-native matching at scale. The architecture is more modern than OpenEMPI, and the FHIR API is first-class. Picked up adoption through 2025 and 2026.

Synthea Patient Matching tooling, while primarily a research and benchmarking effort, ships matching components that hold up in real outpatient deployments when paired with a FHIR backend. A reasonable budget option for practices that need a simple matching layer.

LinkPlus from CDC handles deterministic patient matching with a strong public-health pedigree. Not a complete MPI on its own, but a credible matching component when paired with a FHIR-conformant patient store. The FHIR Master Patient Index for outpatient practices: a 2026 field guide covers the broader decision frame.

How to Stitch an Open-Source MPI Into an Outpatient Stack

The pragmatic outpatient open-source MPI stack tends to look like this:

• A FHIR server like HAPI as the patient store.
• An MPI engine like OpenEMPI or JEMPI for the matching logic.
• A thin admin UI layered on top, either built in-house or borrowed from the MPI project.
• Integration points into the EHR and the form layer through the FHIR Patient API.

Each piece is well-documented on its own. The integration is where small teams spend their time, and is also where the operations cost shows up. The top 4 MPI APIs for outpatient EHR modernization projects goes deeper on the API-driven side.

Where Open-Source MPI Falls Short

The honest gaps in 2026 are around managed support and polished admin UIs. Those are exactly the features that commercial vendors charge for. If the practice has IT capacity that wants to own the stack, the open-source path works well. Otherwise, a managed commercial product is usually the cheaper overall option.

Open-source MPI pays off when someone in the practice treats it as their own.

Sources

• Patient $match operation spec - HTML, HL7 FHIR v6.0.0-ballot4
• PMAL Final Report (foundational) - PDF, ASPE (HHS), 2019
• Interoperable Digital Identity and Patient Matching IG v2.0.0 - HTML, HL7