Patient-facing SDC form rendering has a different set of constraints than clinician-facing rendering. The user is on a phone half the time, the literacy assumptions are different, and the form has to be tolerant of partial completion, accidental back-button taps, and unreliable mobile network. A FHIR-shaped form that renders fine in a clinical UI can fall apart in a patient intake context if the renderer was not designed for it.
This piece looks at six SDC form renderers worth shortlisting for patient-facing deployments. The wider buyer's-guide framing is in FHIR form builders for US hospitals: what you need to know in 2026; for the FHIR-native EHR side, top 5 SDC form builders for FHIR-native EHRs covers the parallel question. For more on the FHIR coverage hub, the rest of the series fills in.
What Patient-Facing Rendering Demands
Patient-facing rendering has four properties that clinical rendering often does not test together. Mobile-first responsive layout that works on a small phone screen without a separate UI. Resilience to partial saves and offline submission, so a half-filled intake form does not vanish when the connection drops. Plain-language presentation, so SDC's expression-driven dynamic behavior does not produce questions that read like database fields. And accessibility that meets WCAG 2.1 AA at minimum.
A renderer that handles all four is rare. Most handle two or three well and require workarounds for the rest.
The Six Renderers to Know
The list below leans on what shows up in real patient-facing deployments. Order reflects fit-for-purpose, not raw feature count.
- LHC LForms. The Lister Hill team's open-source renderer is the closest thing to a reference implementation for SDC, with strong patient-facing patterns and active maintenance. It handles enableWhen logic and answer-list lookups against an NLM value set service out of the box.
- Aidbox SDC IDE. The Aidbox project's SDC IDE supports patient-facing rendering with theming hooks and a mobile-friendly default layout. Integration with the rest of an Aidbox stack is straightforward, and the rendering layer can be embedded into a patient portal without a heavy framework dependency.
- Formbox. Positioned as a FHIR-native SDC form-rendering layer designed to embed into patient-facing apps, with a focus on mobile responsiveness and offline resilience. The trade-off is operational integration: it expects to sit alongside a FHIR server, not replace it.
- Smile Digital Health Form Renderer. Smile bundles a form renderer with its broader FHIR platform. The strength is end-to-end integration: the form renders against a Smile-hosted Questionnaire and submits to a Smile-hosted endpoint, with terminology lookups going through the same vendor.
- Open SDC Renderer (community). A community-maintained reference renderer with broad SDC coverage and a permissive license. The honest trade-off is maturity: features land, but production-grade mobile patterns require some additional work.
- Cerner Open Forms. Part of the Oracle Health FHIR ecosystem, this renderer is purpose-built for patient-facing intake in EHR-integrated workflows. The fit is narrow but strong for organizations already on Cerner.
What Goes Wrong in Patient-Facing Rendering
A handful of failures recur across teams that built patient-facing intake on top of a renderer not designed for it.
- The mobile layout was an afterthought, and 6-inch screens showed truncated questions and overlapping radio buttons.
- Partial saves were not handled, so users who answered half the form and tapped back lost their work.
- Accessibility was bolted on, not built in, and the form did not pass a basic screen-reader test.
- Conditional logic referred to terminology lookups that timed out on slow mobile networks, causing the renderer to hang.
The fix is to test the renderer on a 4G connection, on a real phone, with a real screen reader, against a form that exercises the hard capabilities. That test usually exposes the issues before procurement.
How to Pick
For mostly-mobile patient intake, prioritize LForms, Aidbox SDC IDE, or Formbox. For end-to-end EHR-integrated workflows, Smile or Cerner Open Forms fit the contract-and-vendor model better. For greenfield deployments with engineering capacity, the open community renderer is a credible starting point.
Patient-facing rendering is where the differences between SDC tools become visible to actual users. The right pick is the one that handles all four properties (mobile-responsive, partial-save-tolerant, plain-language, accessible) without your team having to reinvent them.
Sources
- Android FHIR SDC Library (patient-facing mobile, evergreen) - Google Open Health Stack
- PRO Data Collection Via Web/Mobile Using FHIR (peer-reviewed patient-facing deployment) - JMIR 2024
- real-world SDC patient-facing pathway - PDF slides, Martijn Verhoeven, DevDays 2025