5 FHIR Form Builders That Handle Multi-Provider Referral Forms

Multi-provider referral forms are an underrated stress test for any FHIR form builder. A referral that starts in primary care and lands at a community service, a hospital outpatient department, and an allied-health provider has to carry consistent data through every hop without anyone hand-mapping fields between systems. The renderer is only half of the job. The other half is making sure the QuestionnaireResponse can be consumed cleanly by every receiving provider, ideally as referencable FHIR resources rather than blobs of free text.

The five form builders below have shown up well in 2026 against this workflow. The shortlist favours tools that take the receiving provider's downstream pipeline as seriously as the originating clinician's user interface. For broader background on how these tools fit into a wider FHIR stack, the rest of the FHIR coverage provides the supporting context.

What a Referral Form Has to Carry

A typical multi-provider referral form needs to carry patient demographics, the originating clinician's identifiers, the referral reason coded against SNOMED CT, any relevant observations as discrete resources, supporting documents, and the receiving service identifier. The form builder has to render this without overwhelming the originating clinician and serialise the response in a way that every downstream system can ingest with zero manual mapping.

A renderer that handles the rendering side well but produces a flat blob of answers on the response side fails the practical test.

The 5 FHIR Form Builders That Handle Multi-Provider Referral Forms Worth Shortlisting

  1. Aehrc Smart Forms. Smart Forms handles the FHIR-resource extraction story well, particularly the conversion of QuestionnaireResponse items into Observation, Condition, and ServiceRequest resources that downstream providers can consume directly. The native fit with Ontoserver-style terminology makes SNOMED CT-coded referral reasons behave predictably.
  1. Medplum Form Renderer. The bundled platform helps here, because the referral response can land in a structured FHIR store immediately and become available to downstream systems through standard FHIR API calls. Operators standardising on a single FHIR backbone for the referral graph tend to ship faster with this stack.
  1. LHC-Forms with a Custom Extraction Layer. LHC-Forms by itself does not extract responses into discrete resources, but its predictable rendering behaviour makes it a popular base for teams that prefer to own the extraction pipeline. Several UK GP federations have built a clean QuestionnaireResponse-to-resource translator on top of LHC-Forms and run multi-provider referral workflows through it for years.
  1. Firely Forms. Firely Forms is worth considering when the originating clinician's user experience matters more than the receiving end's integration story, because the hosted SDC service gives polished rendering with little effort. The trade-off is that downstream extraction usually needs a separate component, which adds a moving part to the architecture.
  1. Smile CDR Forms. Smile CDR's commercial bundle handles the referral graph as a first-class scenario, with managed terminology, structured response extraction, and the routing logic that pushes the referral to the right receiving service. Larger Integrated Care Systems often pick this when the operating model favours a single vendor across the referral pipeline.

Tests Worth Running Before Picking One

Three tests separate the candidates fast. First, build a referral form where the reason is coded against a SNOMED CT subset that the receiving service expects, and check the response actually carries the code, not a label. Second, run the QuestionnaireResponse through the receiving service's ingest and confirm it lands as discrete resources, not as a single blob. Third, simulate a partial referral where the originating clinician cannot finish in one session, and check that the receiving service does not receive a half-formed payload before the form is submitted.

For the broader context on how a FHIR form builder choice fits into a UK clinical stack, the complete guide to FHIR form builders for UK healthcare in 2026 is the right back-reference. For a related shortlist tuned to community pharmacy workflows that often sit at the receiving end of referrals, the best FHIR form tools for community pharmacy services in 2026 is worth reading alongside.

Sources

Top 6 SDC Form Engines for Care-Home Resident Assessments

Best FHIR Form Tools for Community Pharmacy Services in 2026