Pediatric cardiology intake is a special case for FHIR form builders. Parents fill out part of the form, the clinic completes another part during the visit, and the result has to feed both growth-curve charting and congenital-defect registry reporting. A form tool that does not model that split workflow tends to break in the second week of production use. The five form builders below have stood up to the workload in 2026 deployments. For more on FHIR API patterns, the broader walkthroughs cover the linked topics.
The Five Form Builders Pediatric Cardiology Teams Are Actually Using
- LHC-Forms by NLM. The open-source standard for SDC Questionnaire rendering. Handles parent-completed sections via separate Questionnaire instances tied to the same Encounter. Strong calculated-expression support for things like BSA-indexed measurements. The main trade-off is a Spartan default UI, which most teams skin themselves.
- Smile Digital Health Forms Engine. Bundled inside the Smile CDR, so the terminology lookups for LOINC and SNOMED CT congenital-defect value sets happen against the same server that stores the responses. Best fit for clinics already on the Smile stack.
- Form.io with FHIR plugins. A general-purpose form platform that has earned a place in healthcare by being scriptable and easy to embed in parent-facing portals. Pediatric cardiology teams use it for the at-home symptom-tracking forms that feed into the clinic-side Questionnaire.
- MedicalMine SDC. A newer commercial offering with strong support for the answerExpression and itemContext extensions, which matter for the calculated-fields heavy world of pediatric cardiology growth tracking.
- Vermonster Healthcare Forms. Used by a handful of academic medical centers for trial-data capture. Notable for clean QuestionnaireResponse extraction into Observation and Procedure resources, which keeps registry submission workflows simple.
Each of these has been deployed against real pediatric cardiology data; the demos all look similar, but the production stories diverge.
What to Test Before Committing in 2026
A pediatric cardiology team evaluating a form builder should test four things specifically. Parent-portal flow: the form has to be filled out partly at home and partly in clinic, with no data loss across that hand-off. Growth-indexed calculations: BSA, height-Z-scores, and indexed valve measurements have to flow through calculatedExpression without manual reentry. Registry alignment: the tool should map cleanly to the IMPACT congenital-heart registry submission format. Multi-language intake: roughly a quarter of pediatric cardiology patients in US practice come from Spanish-first households, and the Questionnaire renderer has to switch languages without forking the form definition.
A short proof-of-concept against the team's own Questionnaire profiles is the only way to surface which of these stumble in practice. The cardiology practice cornerstone covers the broader selection framework, and the cancer center PRO walkthrough shows the same selection logic applied to a different specialty.
A Note on Long-Term Fit
The pediatric cardiology cohort is small relative to adult cardiology, which means the form-builder team supporting the tool matters more than the feature checklist on day one. A vendor that responds to a registry-format change in two weeks is worth more than one that ships fancier widgets but lags on regulatory updates. The five tools above all have multi-year track records in pediatric cardiology specifically, which is the main reason they made the list.
A practical evaluation across these five tools usually surfaces clear winners within the first month of pilot. Pediatric cardiology programs that take the time to test the parent-portal flow and the calculated-expressions layer specifically end up with a stack that holds up across the next three years of intake volume.