Specialty outpatient clinics, whether they focus on dermatology, orthopedics, GI, or another single line, have intake needs that look generic on the surface and turn surprisingly specific the moment you build a real form. The right FHIR intake tool for this setting has to handle the standard demographic and history workflow without making the specialty-specific parts feel like an afterthought.
The five tools below are the ones that consistently show up on specialty rollouts in 2026. They all support FHIR Questionnaire and QuestionnaireResponse natively, and they all have reference deployments outside the demo environment. For the FHIR field guide here on the site, the rest of the section drills into surrounding topics.
What Specialty Clinics Need Out of FHIR Intake
Before naming names, the capabilities that matter most for a specialty outpatient clinic are:
- A clean way to add specialty-specific intake sections without forking the codebase.
- Solid terminology integration for ICD-10 and CPT lookup at the point of capture.
- Conditional logic that hides irrelevant questions, so a derm patient never sees an orthopedic history block.
- Real-world support for tablet-based check-in, not just a desktop preview.
A tool that nails all four can stay in your stack for years. A tool that nails three usually gets replaced within eighteen months.
The Five Tools That Hold Up in 2026
- LHC-Forms. NLM's open-source renderer, with strong SDC support and a fairly mature library of specialty-relevant templates. The work is in the integration, not the rendering.
- Aidbox Forms. A FHIR-native commercial platform that includes a builder UI and a managed terminology server. Specialty clinics that want to skip the backend work tend to land here.
- Medplum. Ships an end-to-end SDC stack, including form rendering, FHIR storage, and a workflow layer. Newer than the others, but the specialty deployment count has climbed through 2026.
- Smile Digital Health Forms. Has the heaviest enterprise pedigree on the list, but ships a perfectly serviceable specialty-clinic tier. Worth a pilot if your practice belongs to a larger group.
- Google Open Health Stack SDC Library. Best on mobile and tablet rendering, especially if your specialty clinic has a patient-facing app for pre-visit intake. Android-first by design.
How to Choose Between Them
The trade-off is the same as in most outpatient FHIR decisions: how much of the integration work can your team realistically own? Open source means more control and lower license cost, but somebody has to write the connectors. Commercial means a faster path live, at a recurring fee that scales with patient volume.
A practical way to settle it is to size the form-building effort directly. If you can build one specialty intake template in the candidate tool inside half a day, you have a tool that will not collapse under the second and third template. If it takes longer than a day for one form, the tool will be the bottleneck once you scale beyond a single specialty.
The complete guide to FHIR intake forms for outpatient practices in 2026 goes deeper on what the intake layer should actually do across outpatient settings.
Where Specialty Clinics Tend to Trip Up
Three traps show up over and over on specialty rollouts. The first is treating intake as paperwork rather than as the start of the clinical record. The second is choosing a tool with no real handoff to the EHR, so the structured response ends up archived as a PDF anyway. The third is overbuilding the first form, with every conditional branch a clinician could ever ask for, before testing how patients actually fill it on a tablet.
For smaller specialty groups, the top 5 FHIR form engines for solo and small-group practices covers more of the budget end of the field.
The tool that wins is usually the one that gets out of the way after the first quarter, not the one with the most boxes ticked in the RFP.
Sources
- Screening and Assessments overview - HTML, HL7 US Core
- Questionnaires by Example - PDF slides, Brian Postlethwaite, DevDays 2022
- Android FHIR SDC Library docs (evergreen) - HTML, Google Open Health Stack
