SDC-based medical form builders replaced custom form-building solutions in most 2026 clinical settings. Understanding what they solve and what they don't shapes purchasing decisions.
What SDC builders solve well
1. Structured data capture. Answers land as structured FHIR resources (QuestionnaireResponse), not free-text. 2. Conditional logic. enableWhen and enableWhenExpression for dynamic forms. 3. Calculated fields. calculatedExpression for derived values. 4. Multi-language support. Designations for translated question labels. 5. Pre-population. Known Patient data pulled from FHIR. 6. $extract operation. Answers converted into Observation, Condition resources.
What they don't solve
1. Payment forms. Handle billing/insurance separately. 2. Non-clinical business forms. Not designed for administrative use. 3. Complex real-time CDS. Use CDS Hooks for that. 4. Legacy PDF migration. SDC forms are new; migrating PDFs to SDC is manual.
Common vendor categories
1. Open source reference. LHC-Forms, NLM Form Builder. Full SDC IG conformance. 2. Commercial bundled with FHIR server. Aidbox Formbox, Smile CDR SDC. Best for teams committed to that vendor. 3. Standalone commercial. Redox, Xealth. Integration wrappers. 4. EHR-native. Epic MyChart forms, Cerner PowerChart. Locked to vendor.
Selection checklist
1. Does it support all enableWhen variants? 2. Does it support calculatedExpression? 3. Does it support $extract to structured resources? 4. Does it work well on mobile? 5. Does it support save-and-resume? 6. Does it meet WCAG 2.1 AA? 7. Does it integrate with your FHIR store?
Deployment realities
1. Design phase — form authoring, testing, terminology binding. 2. Deployment — integration with FHIR store, SMART launch. 3. Operations — form updates, terminology refresh, monitoring. 4. Iteration — user feedback, form improvements.
Medical form builders are commodity tooling in 2026 for the SDC use case. Choose against real needs, not against demo polish.
