US telehealth has reshaped what a patient-facing form needs to do. A patient on a phone in their kitchen has to complete intake before the visit starts, then handle visit-of-care surveys after. Each form has to render cleanly on whatever device the patient brought, validate against US clinical value sets, and round-trip into the EHR without manual rework. These five tools are the ones US telehealth teams keep evaluating in 2026.
The cornerstone Complete Guide to FHIR Form Builders for US Clinics in 2026 covers the broader framing. For the rest of our FHIR reporting, the broader desk runs alongside.
NLM LHC-Forms
LHC-Forms is the open-source baseline most US telehealth projects start with. The renderer fits patient-facing contexts well: responsive layouts, value-set-backed dropdowns, and clean SDC handling. For US telehealth teams that want a credible default before evaluating commercial options, LHC-Forms is the right starting point.
Open Health Stack Patient Renderer
The Open Health Stack patient renderer is built around mobile-first patterns and offline-capable flows. For US telehealth that serves rural patients with weak connectivity, the offline support matters. Intake completes on the device, the QuestionnaireResponse syncs when the connection returns, and the visit does not stall on a dropped signal.
Smile Digital Health Patient Forms
Smile Digital Health offers patient-facing form rendering on top of its managed FHIR platform. For US telehealth vendors that want vendor-handled terminology, audit logging, and visit-of-care surveys in one stack, Smile is the most common commercial pick.
Custom React on a FHIR SDK
A pattern that has matured for US telehealth is a custom React patient app on top of a FHIR SDK. The telehealth team owns the patient brand and the visit flow, the SDK handles the FHIR mechanics, and a value-set-backed dropdown component pulls from a terminology service in the background. For US telehealth vendors with a strong front-end team, this pattern is more common than vendor scorecards reflect.
Firely Patient Forms
Firely's forms layer fits .NET-aligned US telehealth vendors. The SDC depth is strong, the FHIR fidelity is consistent, and the team has a long track record with US clinical projects. For US telehealth vendors with a Windows-shop pattern, Firely is worth a serious evaluation.
Picking for US Telehealth Intake
The shortlist for most US telehealth projects comes down to three questions. Does the vendor want vendor-handled operations? Then Smile Digital Health. Does the vendor want a credible open-source baseline? Then LHC-Forms or the Open Health Stack. Does the vendor want full ownership of the patient brand and flow? Then a custom React app on a FHIR SDK is the pattern that scales.
The FHIR Questionnaire vs REDCap for US research intake is the right next read if research-grade intake is a parallel priority. The right patient-facing FHIR form tool for US telehealth is the one that renders cleanly on the patient's actual phone, syncs through patchy networks, and round-trips into the EHR without manual cleanup.
Sources
- Android FHIR SDK for offline-first mobile healthcare apps - Documentation page, Google for Developers, 2025
- Open Health Stack overview for mobile-first FHIR apps - Documentation page, Google for Developers, 2025
- Android FHIR SDK Kotlin libraries for mobile healthcare - GitHub repository, OHS Foundation, 2025