Patient intake is the first place a FHIR-first clinic's architectural choices become visible to patients. The intake form has to render cleanly on every device a patient might use, capture the right level of clinical detail for the visit type, and round-trip into the patient record without manual reconciliation. The five builders below are the ones FHIR-first clinics pick most often in 2026, with notes on where each one fits. For broader context, see the FHIR implementation playbook.
The FHIR SDC form builders reference guide covers the architectural picture; this list narrows it to the clinic-intake use case.
The 5 Intake Builders to Know
- LHC-Forms. The open-source SDC renderer with strong mobile support, low operational cost, and a deep deployment history. The default for clinics that have in-house FHIR expertise and want to own the form layer.
- Formbox. Health Samurai's standalone SDC form builder, focused on rendering and extraction without coupling to a specific FHIR server, used by clinics that want a managed form service.
- Aidbox FHIR Forms. The form-builder layer of the Aidbox FHIR stack, used by clinics that have already standardized on Aidbox as their backing FHIR store.
- Medplum Questionnaire UI. The intake form layer of the Medplum platform-as-a-service, used by FHIR-first clinics that want a hosted intake stack from a single vendor.
- Beda EMR Forms. The form layer of the Beda EMR stack, with solid expression-evaluation handling and a deployment history in clinic intake workflows.
What Matters for Clinic Intake Specifically
Three factors are weighted more heavily in clinic intake than in other form-builder scenarios.
The first is mobile-first rendering. A non-trivial share of intake completion happens on a phone in a waiting room. A form builder that requires a desktop screen is the wrong builder, period. The second is branching depth. Intake forms branch on insurance type, visit reason, and prior history; the builder has to handle three or four levels of conditional logic without becoming unmaintainable. The third is persistence semantics on partial completion. Patients leave intake half-finished and come back later; the builder has to support resuming a QuestionnaireResponse cleanly.
The top SDC form tools that handle conditional logic walkthrough goes deeper into the branching side.
How FHIR-First Clinics Should Pick
Selection turns on the clinic's engineering profile and the existing FHIR stack. A clinic with a small engineering team and a preference for managed services usually picks Formbox or Medplum. A clinic running on Aidbox picks Aidbox FHIR Forms for the single-vendor relationship. A clinic running on Beda picks Beda Forms. A clinic with strong open-source preferences and an in-house FHIR engineer picks LHC-Forms.
For multi-clinic networks where the same intake stack has to serve several clinics with shared workflows, the best FHIR-native intake tools for multi-clinic networks walkthrough covers the patterns that scale across deployments.
The honest test of an intake form builder is whether patients complete the form. A builder that produces a clean mobile experience and a clinical record without a reconciliation step is doing its job. Everything else is feature detail. 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. Teams that get this right twice in a row tend to stop noticing the layer at all, which is exactly the goal.
Sources
- SDC Examples - IG, HL7, 2024
- LHC-Forms project - Project page, NLM LHNCBC, 2024
- SDC Introduction - IG, HL7, 2024