Preventive care practices selecting a FHIR form builder also face a deployment decision: cloud-hosted, where the form authoring and rendering live on the vendor's infrastructure, or self-hosted, where everything runs inside the practice's own environment. The fork has long-term implications for data residency, audit posture, and how reliably the form rendering performs during peak documentation windows.
For the wider context, see more on FHIR data exchange patterns and the parent FHIR form builders buyer's guide for wellness intake.
What Cloud-Hosted Looks Like in 2026
Cloud-hosted FHIR form builders usually mean Aidbox Forms running as a managed service, Formbox in its hosted tier, Medplum in its cloud tier, or vendor-managed deployments of LHC Forms. The operational burden moves to the vendor. The preventive care practice pays for usage and can focus on form authoring and downstream analytics rather than infrastructure.
The trade-offs show up in three places. First, vendor lock-in is real, since form definitions and QuestionnaireResponse storage portability between vendors varies. Second, data residency requirements occasionally push back against cloud hosting, especially for practices participating in state-funded programs with explicit on-premises mandates. Third, rendering performance during peak documentation windows depends on the vendor's capacity planning, which the practice has no visibility into.
What Self-Hosted Looks Like in 2026
Self-hosting usually means LHC Forms, MetaForms, or a self-hosted Medplum or Aidbox deployment. The cost model is more predictable, since hardware and operations are fixed-cost line items. Data residency is fully under practice control. Rendering performance is fully under practice control, which matters during peak documentation windows when every clinician is finalizing visit notes.
The cost lands on the operations team. A preventive care practice running self-hosted form-builder infrastructure needs a platform engineer who handles upgrades, monitoring, and form-definition deployment workflows. For smaller practices, this is usually not a full-time role, but it does require steady attention.
How the Decision Usually Goes
Three patterns are common in 2026:
- Single-location preventive care practices with limited engineering capacity pick cloud-hosted for operational simplicity
- Multi-location preventive care networks with platform engineering capacity pick self-hosted for cost control and data residency
- Preventive care practices embedded in larger health systems inherit the parent system's deployment posture
A few factors that often shift the decision:
- State-funded program participation pushes toward self-hosted, where data residency is explicit
- Heavy patient-facing form rendering pushes toward cloud-hosted, where the vendor handles autoscaling
- Strict consent and access-control requirements push toward self-hosted, where policy enforcement is transparent
- Multi-vendor form-builder evaluation pushes toward cloud-hosted during pilot, then migration to self-hosted if the vendor relationship continues
The form authoring workflow itself looks similar across both deployment models. The form definitions are the same FHIR Questionnaire resources, the SDC extension surface is identical, and the QuestionnaireResponse extraction logic does not change. The deployment decision affects operations and procurement, not the authoring UX.
For the upstream choice between FHIR Questionnaire and custom web forms, the FHIR Questionnaire vs Custom Web Forms for Wellness Clinic Intake comparison covers parallel ground.
Sources
- LHC-Forms Form-Rendering Widget - HTML, NIH NLM LHNCBC, evergreen
- Structured Data Capture documentation - HTML, CSIRO Smart Forms, evergreen
- SDC Implementations registry - HTML, HL7 Confluence, evergreen
