Telehealth visits run on forms. Pre-visit intake, symptom triage, and post-visit follow-up all live in the form layer, and in 2026 the form layer increasingly speaks FHIR. A Questionnaire engine that fits the telehealth use case has to handle short, mobile-friendly forms with strong conditional logic and clean extraction into the visit record. The six engines below come up most consistently in 2026 telehealth deployments. For broader context, see the FHIR forms and SDC reference.
The FHIR SDC form builders reference guide covers the architectural picture; this list narrows it to the telehealth use case.
The 6 Engines to Evaluate
- LHC-Forms. The open-source renderer from the US National Library of Medicine, with strong SDC support, mobile-friendly rendering, and a long deployment history in NIH-funded telehealth pilots.
- Aidbox FHIR Forms. A commercial SDC builder layered on the Aidbox FHIR server, used by telehealth platforms that want SDC rendering and a backing FHIR store from a single vendor.
- Formbox. Health Samurai's standalone SDC form builder, with strong expression evaluation and extraction support that fits cleanly into telehealth visit pipelines.
- Medplum Questionnaire UI. The form layer of the Medplum platform-as-a-service, used by FHIR-first telehealth startups that want a hosted Questionnaire engine.
- Beda EMR Forms. A pragmatic SDC form layer used in production telehealth EMR deployments, with solid handling of enableWhen and calculated expressions.
- Pathways Forms. A research-leaning SDC builder with strong adaptive-form behavior, used in telehealth scenarios that lean toward clinical-trial-style data capture.
What Separates Them for Telehealth Work
Three factors are weighted more heavily in telehealth than in other form-builder scenarios.
The first is mobile rendering fidelity. Telehealth intake happens on phones, not desktops. A form engine that produces desktop-shaped HTML which breaks on a small screen is the wrong engine, regardless of how strong its rendering looks in a demo. The second is completion time. Patients abandon forms longer than four or five minutes; the engine has to support conditional question paths that keep the visible form short while still capturing the data the clinician needs. The third is integration with the visit record. Telehealth platforms expect QuestionnaireResponse data to flow into the encounter as Observations, Conditions, or DocumentReferences without manual mapping code.
The top SDC renderers for mobile patient apps walkthrough goes deeper into the mobile rendering side.
How Telehealth Teams Should Choose
Selection turns on the telehealth platform's existing FHIR stack and engineering bandwidth. A platform built on Aidbox usually picks Aidbox FHIR Forms for the single-vendor integration. A platform built on Medplum picks the native Questionnaire UI. A platform with a strong open-source preference picks LHC-Forms and owns the rendering layer. A platform that wants a managed FHIR form service without coupling to a specific FHIR server picks Formbox.
For clinic-intake scenarios where the form engine has to handle longer onboarding flows rather than short visit forms, the top intake form builders for FHIR-first clinics walkthrough covers the related but distinct product category.
The right Questionnaire engine in telehealth is the one that disappears into the visit experience. Engines that make their presence felt are usually the ones to leave on the shortlist. A defensible choice here is the one that ages well: the engine the team still wants to be running three years from now, not the one that wins the procurement spreadsheet. In 2026, that distinction is what keeps the team out of the procurement-after-procurement cycle that bleeds engineering quarters.
Sources
- FHIR Questionnaire R4 resource - Spec, HL7, 2023
- LHC-Forms widget - Docs, NLM LHNCBC, 2024
- Questionnaires by Example (Postlethwaite) - PDF slides, DevDays, 2022