LHC-Forms and Open Health Hub sit on opposite sides of the SDC form-builder market and they both win deals from telemedicine vendors regularly. LHC-Forms is the open-source SDC renderer from NIH; Open Health Hub is a commercial managed form product with clinical polish. The choice between them for a telemedicine deployment is rarely about which one renders better, because both render well. It is about how the vendor wants to spend its engineering time over the next three years. For broader context, see related FHIR product walkthroughs.
The FHIR form builders for medical software vendors reference guide covers the broader vendor selection picture.
What LHC-Forms Gives a Telemedicine Vendor
LHC-Forms is open source, broadly used in research and clinical settings, and battle-tested across patient-facing and clinician-facing workflows. The telemedicine vendor that adopts LHC-Forms inherits a working renderer, a community that already extends it, and zero licensing cost. The renderer is good at SDC item coverage, calculated expressions, and accessibility.
The honest cost of LHC-Forms is that the vendor team owns the integration layer. There is no managed hosting; the vendor stands up the renderer in its own application, wires it to a terminology server, handles partial-state persistence, and writes the extraction code that lands responses in the clinical store. For a vendor with one developer who likes form infrastructure, this is fine. For a vendor that wants forms to just work, the integration tail can be longer than it looks in the demo.
What Open Health Hub Gives a Telemedicine Vendor
Open Health Hub Forms is a commercial managed product. The vendor pays a license fee and gets a renderer that ships with clinical templates, a managed terminology integration, partial-state persistence handled at the platform level, and an extraction layer that already knows how to write Observations and Conditions. A support contract covers the inevitable edge cases that show up at scale.
The trade-off is freedom and cost. Customization beyond the supported extension surface gets harder, and the licensing fee scales with the customer count. For a telemedicine vendor whose forms are central to the product and whose team is small, this trade is usually worth it. For a vendor that wants to own the rendering stack as part of its competitive surface, it is not. The best FHIR form builders for specialty EHR vendors walkthrough covers vendors that chose Open Health Hub precisely because forms were not the differentiator.
How Telemedicine Vendors Should Pick
The selection comes down to engineering ownership and product roadmap. Vendors with a dedicated form-rendering developer pick LHC-Forms because the long-term cost of the integration work is lower than the recurring license fee. Vendors with smaller engineering teams or with a roadmap that puts forms in the supporting cast pick Open Health Hub because the time to first customer is shorter and the support contract carries the platform's failure modes.
For vendors evaluating the broader managed SDC landscape before settling, the best SDC tools for healthcare software teams shipping in 2026 walkthrough covers the production-ready commercial options alongside LHC-Forms. The defensible choice for a telemedicine vendor in 2026 is the one whose total three-year cost (engineering plus licensing) the vendor team can defend on a single slide.
The honest signal for telemedicine vendors picking between LHC-Forms and Open Health Hub is how much engineering capacity the team is willing to commit to the form layer in year two and three, not just year one. The right answer for year one often is not the right answer for the long-term product picture.
Sources
- LHC-Forms SDC Questionnaire App - HTML, SMART Health IT, evergreen
- Mastering FHIR Terminology Services - PDF slides, DevDays, 2023
- LHC-Forms research project page - HTML, NIH NLM, evergreen