LHC Forms vs NLM Form Builder for SDC Questionnaires

LHC Forms and the NLM Form Builder come from the same source, the National Library of Medicine, and they cover overlapping ground. Teams new to the SDC ecosystem often assume they have to pick one over the other, when in practice the two tools work together and answer different questions in the workflow. The comparison below covers what each one does, where each one earns its place, and how a healthcare team should think about using them.

For broader background, further FHIR reading on the site is a useful detour first.

The Quick Distinction

LHC Forms is the rendering and form-runtime library. It takes a Questionnaire resource and turns it into a working form that an end user fills in, returning a QuestionnaireResponse when the user submits. It runs in a browser, supports SDC features like skip logic and pre-population, and is widely embedded in healthcare apps that need standardized form rendering.

The NLM Form Builder is the authoring tool. It is a browser-based application that lets a clinical or technical author create a Questionnaire visually, preview it through LHC Forms, and export the result as Questionnaire JSON. The author works with a visual canvas instead of editing FHIR JSON by hand.

Most teams that use either one end up using both: the Form Builder for authoring, LHC Forms for rendering. The two together form a complete open-source SDC stack from authoring through user-facing rendering.

Where LHC Forms Wins

LHC Forms wins when the team needs a stable rendering layer they can embed inside their own application. The library handles the SDC IG carefully, including the trickier parts like nested groups, dynamic value sets pulled from a terminology server, and SDC expression evaluation. The rendering is deterministic enough for clinical-trial use and well documented enough to onboard new developers without a long ramp.

LHC Forms also wins on integration footprint. It is JavaScript, it works inside the team's existing frontend stack, and it does not pull in the rest of the NLM toolchain to operate. Teams that already have a form-authoring story but need a better renderer pick up LHC Forms without disrupting the rest of the application.

Where the NLM Form Builder Wins

The Form Builder wins when the bottleneck is authoring, not rendering. Clinical informatics teams that have to produce Questionnaires for many use cases find that hand-editing FHIR JSON is slow and error-prone. The Form Builder gives them a visual canvas with sensible defaults, a preview, and a clean export.

The Form Builder also wins for non-technical authors. Clinicians who own the content for a workflow can use the visual editor directly without learning the FHIR JSON shape. The exported Questionnaire is the same regardless of whether the author worked visually or in JSON, which keeps the long-term governance story simple.

Using Both Together

The pattern that most teams settle on is to use the Form Builder for the authoring step, push the exported Questionnaire into source control or a FHIR-backed content store, and have LHC Forms render the final form to end users. Both tools are maintained by the same group at the National Library of Medicine, and they are explicitly designed to work together.

The detailed top 7 SDC form builders for healthcare teams in 2026 shortlist covers commercial alternatives when the NLM stack is not the right fit. Teams new to the spec should start with the complete guide to FHIR form builders in 2026 before going further.

For clinical-trial use cases where the renderer is the bigger concern, best FHIR Questionnaire renderers for clinical trials in 2026 is a more focused read. The honest take in 2026 is that the LHC Forms plus NLM Form Builder pair remains the cleanest open-source baseline, and the question for most teams is whether their needs justify a heavier commercial layer on top of that baseline.

Sources

Related Posts