Best FHIR Profiling Tools for US EHR Vendors in 2026

• • 4 Min Read

FHIR profiling is the work of constraining the FHIR base specification with project- or jurisdiction-specific rules: which fields must be supported, which value sets are bound, which slicing patterns apply. For US EHR vendors, profiling work is dominated by US Core, USCDI alignment, and the long tail of per-implementation profiles a vendor accumulates over years of customer projects. The tools below are the ones that handle profiling well at vendor scale in 2026.

For the FHIR resource library, the rest of the site has surrounding material. The complete guide to FHIR-based EHR development for US healthcare in 2026 cornerstone is the right background to read first.

What Profiling Work Looks Like for a US EHR Vendor

A US EHR vendor's profiling work has three layers. The first is staying current with US Core releases, which means absorbing the new must-support requirements, the new value-set bindings, and the changed slicing rules each release brings. The second is publishing the vendor's own implementation guide that documents how the EHR fulfills US Core, plus any additional constraints the vendor's customers depend on. The third is validating every release of the EHR's outputs against the profile pack, ideally continuously.

That is a lot of structured work. Tools that fit vendor scale have to handle authoring, publishing, and validation cleanly, and they have to play nicely with whatever build pipeline the EHR's release process uses.

The Tools That Handle Vendor-Scale Profiling Well

These are the profiling tools US EHR vendors actually use in 2026:

HL7 FHIR Shorthand (FSH) and SUSHI, the canonical authoring tool for FHIR profiles, used by US Core itself.
IG Publisher, the official HL7 tool that builds implementation guides from FSH or StructureDefinition inputs.
HL7 FHIR Validator, the standard runtime validation tool that checks resources against published profiles.
Simplifier.net, the commercial profiling and IG publishing platform with collaborative editing and vendor-friendly governance features.
Forge, the commercial profile authoring desktop tool from Firely, often used by teams that prefer a UI to FSH.
Trifolia-on-FHIR, the open-source profile authoring tool maintained by Lantana Consulting Group.

Each fits a different team profile. FSH and IG Publisher are the canonical open-source pair, used by US Core and the broader HL7 ecosystem. Simplifier and Forge fit vendors that want a more polished authoring experience and collaboration features. Trifolia-on-FHIR fits open-source-leaning teams that want a UI without committing to a commercial product.

Where the Tools Differ in Practice

Authoring ergonomics is the dimension where the spread is widest. FSH is text-based and version-controllable, which fits engineering-centric teams well. Forge and Simplifier offer graphical authoring, which fits teams with more clinical or content authors. Trifolia-on-FHIR is somewhere in the middle.

Validation is more uniform. The HL7 FHIR Validator is the canonical runtime tool, used by every serious US FHIR pipeline. It validates against profiles regardless of which authoring tool produced them, which means the choice of authoring tool does not lock the team out of any particular validation path.

Publishing depth is the third dimension. IG Publisher is the canonical tool for full implementation guide builds. Simplifier ships its own publishing pipeline that handles the IG output and the surrounding governance. Vendors that want to publish their IGs publicly almost always end up using one of these two.

How Profiling Tools Fit Alongside the Rest of the Stack

Profiling work touches everything else. The 7 FHIR tools for 21st Century Cures Act EHR work piece covers the certification tooling that depends on accurate profiles. The 6 FHIR bulk data tools for EHR reporting pipelines explainer covers the bulk data tooling that validates against profiles on the way out.

A vendor whose profile authoring is clean and continuous tends to have smoother conformance testing and smoother customer integrations. A vendor whose profiles drift tends to find both painful.

Making the Tooling Pick

A short filter sorts most vendors. Engineering-centric teams that prefer version control and code review pick FSH and IG Publisher. Teams with significant clinical or content-author involvement pick Simplifier or Forge. Open-source-leaning teams with a desktop preference pick Trifolia-on-FHIR. The HL7 FHIR Validator is universal regardless of which path you take.

Whichever authoring path you pick, wire validation into your build pipeline so profile drift is caught at build time, not at the customer's integration meeting. That single practice is what separates US EHR vendors who ship cleanly on profiles from the ones who do not.