Medical Form Builder

7 SDC Form Tools That Handle Repeating Groups Well

Repeating groups are where most SDC renderers quietly fall apart. The pattern is unavoidable in any non-trivial clinical intake, since medication lists, allergy lists, prior surgeries, and family-history entries are all open-ended repeating structures. A renderer that handles them cleanly disappears into the workflow; one that does not turns each form fill into a guessing game. The seven tools below are the ones that consistently get repeating groups right in 2026 production deployments. The FHIR form builder buyer's guide covers the broader procurement frame.

For more reviews of this kind, the FHIR review hub gathers the rest of the shortlists.

The Seven That Handle Repeats Cleanly

  1. LHC-Forms. The NLM renderer treats repeats=true items as first-class and renders the add and remove controls without surprises. The reference behavior most other renderers measure against.
  1. Formbox. The repeating-group authoring UI is one of the cleanest in the category; clinical informaticists can model a medication list with conditional sub-fields without writing any code.
  1. Aidbox Forms. Strong on the response side; nested QuestionnaireResponse items round-trip without losing structure, which matters when the responses feed downstream FHIR resources.
  1. Smile Digital Health Forms. Combines a working repeating-group renderer with the vendor-support contract that hospital IT teams want for a workflow this central.
  1. Open Health Hub. Repeats are well-handled in the PROM context, where a longitudinal survey asks the same nested-question block multiple times across follow-up windows.
  1. Pathways CareCentric Forms. A lesser-known commercial option with a particularly strong story on dynamic repeating groups for behavioral-health intake.
  1. NLM CDE Repository Renderer. Built on top of LHC-Forms with extensions for common-data-element libraries; the repeats handling inherits the LHC-Forms baseline and adds CDE-aware authoring.

Why Repeating Groups Are the Hard Part

A flat questionnaire is straightforward; the renderer paints fields and collects values. Repeating groups break two assumptions at once. The first is the rendering model, which now has to accept a variable number of sibling field clusters and let the user add and remove them mid-form. The second, and harder, is the response model, where the QuestionnaireResponse has to carry that nested structure back to the server in a shape the EHR can actually map. Tools that handle the rendering but flatten the response on submit cause a silent data-loss problem that only shows up in downstream reporting.

A second pitfall is enableWhen inside a repeating group. Conditional display logic that depends on a sibling answer inside the same repeating instance is allowed by the SDC spec but supported inconsistently across renderers. The best SDC form tools for pre-op patient intake review covers a workflow where this combination is the difference between a usable form and a frustrating one.

How to Pilot for Repeats Specifically

A 30-minute pilot can answer the question. Author a Questionnaire with a single repeating group of three nested items, one of which has an enableWhen clause that depends on the value of a sibling field. Submit a response with two instances, both with the conditional field triggered differently. Then read the QuestionnaireResponse back and check whether the structure round-tripped intact. For a broader procurement frame after the repeats pilot, the top 6 FHIR form builders reviewed for 2026 covers the rest of the evaluation criteria.

That single test eliminates most of the candidate pool faster than any feature-list comparison can.

Sources

— Bernard Kowalczyk