LHC-Forms and Open Health Hub Forms keep showing up on the same shortlist for US practices that want an open-source FHIR form builder. The two products have different design centers, and the decision between them ends up being less about feature count and more about what the practice intends to use the form engine for. A practical comparison saves a lot of evaluation time later.
This walkthrough lays out the trade-offs between LHC-Forms and Open Health Hub Forms for a 2026 US healthcare deployment. For our digital health coverage, the homepage links to the wider form-engine landscape.
What Each Tool Is Built For
LHC-Forms is maintained by the US National Library of Medicine. The design center is clinical SDC rendering with full coverage of the SDC specification: initialExpression, calculatedExpression, enableWhen, value set binding, and QuestionnaireResponse extraction. It is the closest thing to a reference implementation of SDC in the open-source world.
Open Health Hub Forms is built explicitly around patient-administered surveys. The design center is the respondent experience: offline support, multi-page navigation, score calculation patterns for behavioral health and patient-reported outcome measures, and mobile-first rendering. The SDC coverage is narrower but the parts the product covers are polished.
For the broader picture of what to look for in any FHIR form engine, the medical form builders buyer's guide is the right primer.
SDC Coverage and Capability Set
LHC-Forms covers SDC more completely. EnableWhen chains across linked items, calculatedExpression with terminology-aware evaluation, and value set expansion against an external terminology server all work as the spec intends. For a practice that wants the form engine to be a long-term FHIR investment, that completeness matters.
Open Health Hub Forms covers the parts of SDC that matter for surveys: branching, scoring, and clean QuestionnaireResponse output. The pieces it does not cover are calculatedExpression edge cases and runtime value set binding against a separate terminology server. For a practice running a behavioral health PROM library, that is fine. For a practice that wants the form engine to be the data capture layer for a wider clinical system, the gap is real.
Respondent and Operational Experience
Open Health Hub Forms has a clear edge on respondent experience. The mobile-first rendering is mature, the offline mode is the strongest of any open-source FHIR form engine, and the multi-page navigation has been tuned for surveys with high item counts. The trade-off is the operational learning curve for self-hosting.
LHC-Forms is plainer on the respondent side. The default styling is workable but not polished, and the offline support is workable but not the centerpiece. The operational story is easier in some respects because the codebase is smaller and more focused on the core SDC rendering job.
How to Decide
A practical decision usually comes down to four questions.
- Is the primary use case clinical data capture or patient-administered surveys?
- How complete does the SDC coverage need to be to support future form designs?
- How much engineering time is available to polish the respondent experience?
- Does the form engine need to integrate with a separate terminology server at runtime?
If the answers point at clinical SDC with a full feature set and an in-house engineering team, LHC-Forms is usually the right pick. If the answers point at patient-administered surveys with a strong respondent experience and limited theming time, Open Health Hub Forms comes out ahead.
For some teams the answer is to run both: LHC-Forms for clinical intake and Open Health Hub Forms for the patient-reported outcomes library. The shared FHIR Questionnaire format makes that pairing cleaner than it sounds.
Where to Go Next
Once the open-source story is clear, the next question is often whether to stay open-source or step up to a managed product. The SDC vs native EHR forms guide is the right read for that next decision.
Sources
- LHC-Forms project documentation - HTML docs, NLM Lister Hill Center
- LForms source and feature docs - GitHub repo, NLM LHNCBC
- Open Source Implementations index on Confluence - HTML wiki, HL7 FHIR community