5 SDC Form Builders That Actually Handle Repeating Groups

Repeating groups are the part of the SDC spec where most form builders quietly fall apart. The pattern is simple on paper: a Questionnaire item that the user can add several copies of, like a list of medications, a list of family-history conditions, or a list of past surgical procedures. The implementation is harder than it sounds, because the renderer has to handle dynamic add and remove, the back-extraction has to map cleanly to multiple discrete resources, and the QuestionnaireResponse has to keep the audit trail clear even when the user reorders items mid-form.

The five tools below actually handle this case in production. For broader background on form tooling, the patient-data interoperability series is a useful detour.

What Repeating Groups Demand from a Form Builder

A working repeating-group implementation has to handle three concerns at once. The first is the visual UX: an add button, a remove control, sensible defaults for the new instance, and clean handling of the layout when the list grows past a screen height. The second is the data shape: every instance has to carry its own answer values, link identifiers, and any nested items. The third is downstream: when the user submits, the QuestionnaireResponse has to round-trip back through any extraction logic the team relies on without losing the relationship between the response items and the resources they map to.

A tool that handles only the visual part is not a serious option. A tool that handles all three is rare enough to be worth highlighting.

The Five Worth Trying

  1. LHC Forms. The National Library of Medicine's reference renderer handles repeating groups cleanly, including nested repeating items. The QuestionnaireResponse it produces preserves the linkId structure so downstream extraction stays predictable. Free to use and well-documented enough that teams can build confidence quickly.
  1. MetaForm Studio. The commercial authoring tool from MetaForm Systems has strong repeating-group support both in the authoring UX and in the runtime. The authoring side gives clinical authors a clear way to define the repeating pattern, and the runtime handles add and remove without surprising behavior.
  1. Firely Forms Runtime. The Firely runtime layer is solid on repeating groups, particularly when paired with the rest of the Firely stack for extraction. The integration story keeps the extraction logic close to the form definition, which reduces the chance of a quiet mismatch between what the form captures and what downstream systems expect.
  1. Smile Digital Health Forms. The Smile forms layer handles repeating groups well, especially in tandem with Smile's broader HAPI-based stack. The add and remove controls work as expected, and the runtime keeps QuestionnaireResponse structure consistent.
  1. KaiKu Health Forms Layer. The specialty oncology and chronic-care option handles the repeating patterns common in patient-reported outcomes well. The visual UX is polished, and the data shape stays clean across long sessions, which matters for patients reporting symptoms over weeks.

How to Decide Between Them

The first cut is whether the team needs an open-source or commercial baseline. LHC Forms is the clear open-source pick. The four commercial options shine when they fit a broader stack the team is already standardized on.

The second cut is the back-extraction story. Repeating groups are not useful in isolation; they are useful because they map to a list of discrete resources downstream. Tools that integrate extraction cleanly with the runtime are more valuable than tools that hand off the extracted resources to a separate process.

The detailed top 7 SDC form builders for healthcare teams in 2026 shortlist covers the broader field. For clinical-trial use cases specifically, best FHIR Questionnaire renderers for clinical trials in 2026 is a more focused read. Teams new to the spec should start with the complete guide to FHIR form builders in 2026 and work back from there. The pattern in 2026 is that two of these five fit any given team, and the right pick usually shows up after a short pilot on the team's most complex repeating-group case.

Sources