Most US pediatric practices that try to modernize their intake stack hit the same fork in the road. They can adopt Structured Data Capture (SDC) and use a FHIR-native form builder, or they can write a custom React form layer with a FHIR mapping behind it. Both work for some teams and fail for others. The notes below cover what actually decides the outcome.
You can step back to the FHIR reference shelf first if you want context.
What SDC Forms Bring
SDC takes the FHIR Questionnaire and QuestionnaireResponse resources and adds a spec-defined extension layer for expressions, dependent items, variable definitions, and value-set bindings. A pediatric form authored in SDC is a structured artifact that travels well between systems: a Questionnaire authored at one institution can render at another, and a QuestionnaireResponse can be read by any tool that understands the spec.
For pediatric workflows, the SDC approach pays off in three places: age-dependent question logic comes built in, screening instruments like ASQ-3 and M-CHAT-R have publicly available SDC Questionnaire definitions, and parent-as-respondent flows can be expressed within the spec rather than as a custom layer.
For broader context, the complete FHIR form builders guide for US pediatric practices lays out the surrounding stack.
What Custom React Forms Bring
A custom React form layer gives a development team full control. The form is a UI component, the data model is whatever the team defines, and the FHIR submission is a translation step at the end. For practices with a strong front-end team, this approach can produce a faster, more polished patient experience than any off-the-shelf SDC renderer.
The trade-off is maintenance. A custom React layer has to be rebuilt every time a screening instrument updates, every time the EHR vendor changes its API, and every time the team adds a new conditional rule. Over five years, the maintenance burden adds up to roughly what a small team would have spent on an SDC builder license.
Where They Diverge in Practice
Five practical factors decide which approach fits a pediatric practice.
- Authoring cadence. If your forms change once a year, custom React holds up; if they change quarterly, SDC wins.
- Cross-system portability. A Questionnaire-as-artifact travels; a custom React form does not.
- Front-end polish. A skilled React team can outperform any off-the-shelf renderer on UX.
- Team shape. If you have a clinical informaticist who can edit SDC and a small dev team, SDC is the right choice. If you have a strong React team and a backlog of UX issues with off-the-shelf renderers, custom is the choice.
- Audit and compliance. SDC's structured-artifact model is easier to defend in an audit; custom React forms put the burden of proof on the team.
For overlapping urgent care decisions, the top 5 SDC form builders for urgent care intake write-up covers a related setting. For teams weighing two specific SDC tools, the LHC-Forms vs Form.io comparison is the right neighbor.
How to Pick for Your Practice
Run two parallel four-week builds. Have your team model a pediatric well-child intake plus an ASQ-3 in an SDC renderer, and in parallel have the front-end team build the same in React with a FHIR mapping. Compare the time-to-ship, the FHIR data quality, and the patient experience at the end. Whichever approach lands cleaner data with less ongoing maintenance is the one to keep. The honest answer for most US pediatric practices in 2026 is SDC; for a handful of practices with strong product teams, custom React still wins.
Sources
- Questionnaire resource spec - HTML, HL7 FHIR R5, evergreen
- SDC IG Release 3 product brief - HTML, HL7, evergreen
- SDC Extract / Pre-populate - PDF slides, DevDays, 2023