LHC-Forms and the NLM Form Builder share a common upstream provenance and a deceptively similar surface. Both come out of the National Library of Medicine ecosystem, both target FHIR-aligned form rendering, and both end up on the shortlist of teams building public-health or research-leaning workflows in 2026. The practical differences are not always obvious from the project pages, and the right choice depends on what your team is actually doing.
This piece walks through the comparison for a 2026 deployment. The wider buyer-side framing is in FHIR form builders for US hospitals: what you need to know in 2026; the static-vs-SDC question is in static forms vs SDC-driven FHIR forms for US practices. For the rest of the FHIR series, the broader coverage adds context.
What Each Tool Actually Is
LHC-Forms is the Lister Hill Center's open-source library for rendering Questionnaires in a browser, with strong SDC support and a deep library of validated instruments. It is a rendering layer plus a set of curated form content, used by clinical research projects, federal health initiatives, and a growing set of commercial deployments that want vetted free content.
The NLM Form Builder is the visual authoring tool that produces Questionnaire resources LHC-Forms (and other renderers) can consume. The Form Builder is the design-time companion to LHC-Forms's runtime, with a drag-and-drop authoring experience for non-developer users.
The honest framing is that the two are not competitors but complementary parts of the same ecosystem, used together in most deployments. The practical comparison is really about when each one fits your workflow.
Where the Form Builder Earns Its Keep
The NLM Form Builder shines when the form-authoring step needs to live with clinical informatics staff who do not write code. Drag-and-drop construction, immediate preview, and direct export to a valid Questionnaire resource lets a clinician or analyst produce a working form without involving an engineer.
The trade-off is that complex SDC expressions (calculated expressions referencing repeating groups, answer expressions against an external ValueSet) sometimes need a hand-edit of the produced Questionnaire. The tool covers the 80 percent case and points the team toward the remaining 20 percent.
Where LHC-Forms Earns Its Keep
LHC-Forms is the runtime that takes the produced Questionnaire and renders it for users. It handles enableWhen logic, the SDC expression set, value set expansion against an upstream terminology service, and QuestionnaireResponse capture. It also ships with a curated library of validated instruments (PHQ-9, GAD-7, AUDIT, and many more) that the team can drop into a deployment without authoring from scratch.
For research projects and public-health workflows, the validated-instrument library and the upstream provenance are the differentiators. For commercial deployments, the runtime quality is what shows up day to day.
The Realistic Deployment Pattern
Most teams that pick either one end up using both. Clinical informatics staff author or modify forms in the NLM Form Builder. The produced Questionnaire feeds into LHC-Forms or another SDC renderer at runtime. Engineering owns the runtime integration and the EHR-side extraction; informatics owns the form library.
The integration is well-trodden enough that the documentation is current, and the failure modes are mostly about either the authoring tool not handling a specific expression or the runtime not handling a specific edge case. Both projects have responsive maintainers.
How to Pick (and What to Pick Alongside)
If your form-authoring step needs to live outside engineering, NLM Form Builder is the natural authoring tool. If your runtime needs SDC support with validated instruments, LHC-Forms is the natural runtime. Most teams end up using both.
For the wider question of when SDC-driven Questionnaire authoring even fits the practice (versus simpler static-form approaches), the static forms vs SDC-driven FHIR forms for US practices breakdown is the right next read.
LHC-Forms and the NLM Form Builder are best read as the two halves of one well-considered toolkit. The comparison is mostly about understanding which half does which job, not picking one over the other.
Sources
- direct overview of LHC-Forms and NLM Form Builder - PDF slides, Ye Wang (NLM), DevDays 2024
- SDC Implementations registry (lists both LHC-Forms and related tools, evergreen) - HL7 Confluence
- Base Questionnaire spec (the produced artifact both tools consume, evergreen) - HL7 SDC IG