US telehealth visits in 2026 depend on a FHIR Questionnaire engine in a way that traditional in-person visits never quite did. The intake form replaces the receptionist conversation, the screening instrument replaces the paper handout in the waiting room, and the post-visit follow-up replaces the discharge sheet. If the Questionnaire engine misbehaves, the entire telehealth flow has a visible gap.
This list covers the FHIR Questionnaire engines US telehealth providers most often pick in 2026. For the healthcare interoperability hub, the broader catalog covers the surrounding topics.
For the architectural context first, the complete guide to FHIR-driven intake forms for US health systems in 2026 frames the field this list narrows into.
Four FHIR Questionnaire Engines for US Telehealth
Order tracks how often each shows up in active US telehealth Questionnaire deployments in 2026.
- Medplum Forms. TypeScript-friendly Questionnaire engine that fits the modern telehealth product stack and ships with strong mobile rendering.
- Smart Forms. Open-source SDC renderer used by US telehealth vendors that want full control over the form layer and have engineering capacity to operate it.
- Formbox. Commercial Questionnaire engine with managed terminology integration, common in US telehealth platforms that want a packaged forms story.
- Aidbox Forms. Commercial Questionnaire engine paired with the Aidbox FHIR backend, used by US telehealth vendors that want a single-vendor data and forms story.
What "Built for Telehealth" Means
Three concrete behaviors separate a telehealth-ready Questionnaire engine from a generic one:
- Strong mobile rendering, because US telehealth patients almost always complete pre-visit Questionnaires on a phone.
- Resume-from-where-you-left-off behavior, because telehealth Questionnaires are often abandoned mid-flow and finished later.
- Real-time validation that does not block the user when the network briefly drops, because telehealth users are on consumer-grade home networks.
The four above all clear those bars in production. Several other Questionnaire engines handle the spec letter-perfect but stumble on the abandoned-flow recovery or the network-tolerance pattern that telehealth needs.
Which Engine for Which US Telehealth Pattern
US telehealth startups going fast lean toward Medplum or Aidbox for the integrated story. US telehealth networks built on a self-hosted FHIR stack tend to pick Smart Forms for control. US telehealth platforms that want a packaged terminology layer alongside the forms engine choose Formbox.
For US patient-portal-driven Questionnaires in non-telehealth contexts, Top 5 SDC renderers for US patient portal modernization in 2026 is the more useful adjacent reference. For clinical research running through telehealth-style remote intake, FHIR Questionnaire vs REDCap for US clinical research covers the comparison clinical research teams keep facing.
How to Pilot a Telehealth Questionnaire Engine
Build the actual pre-visit intake and post-visit follow-up Questionnaires for a real US telehealth program. Render them in the candidate engine on a phone, on a mid-tier laptop, and on a budget Chromebook, because telehealth patients use all three. Test the resume-from-abandoned flow by closing the browser mid-form and reopening it. Drop the network for ten seconds during a Questionnaire and watch the recovery behavior.
The candidate that handles all three device profiles, the abandoned-flow case, and the network-drop case cleanly is the one to short-list. The one that loses progress on the abandoned-flow test is the one to drop before telehealth patients prove the point in production.
Sources
- LHC-Forms Questionnaire SMART on FHIR app - demo, NLM / LHNCBC, 2024
- SMART on FHIR app using lforms widget - repo, NLM / LHNCBC, 2024
- SDC implementation guide - IG, HL7 International, 2024