Community pharmacy in 2026 looks very different from the prescription-collection counter of a decade ago. NHS England's expanded Pharmacy First scheme, the New Medicine Service, hypertension case-finding, and contraception consultations all need structured data capture that flows back into GP records and central reporting. A FHIR form tool that holds up here has to render quickly on a community pharmacy's shared workstation, integrate with dm+d for medication look-ups, and emit a QuestionnaireResponse that the patient's GP system can actually consume.
The tools below stand out in this setting. They are not necessarily the biggest names in the SDC market, but each one earns its place against the practical demands of a high-volume pharmacy counter. For the broader landscape of FHIR-aware form tooling, more healthcare interoperability notes is the right starting point.
What Community Pharmacy Asks of a FHIR Form Tool
Three demands matter most:
- dm+d medication look-ups that complete in under a second, because the pharmacist is mid-consultation and the patient is waiting.
- Concise rendering that fits a consultation flow on a workstation alongside the dispensary system.
- Clean serialisation into a QuestionnaireResponse the GP's clinical system can ingest, ideally referencing the same dm+d codes throughout.
A form tool that hits all three feels invisible. One that misses any of them adds friction the pharmacist will notice every single consultation.
The FHIR Form Tools for Community Pharmacy Services Worth Shortlisting
- Aehrc Smart Forms. Smart Forms render fast, integrate cleanly with an Ontoserver-style terminology layer, and serialise responses with discrete codes rather than free-text labels. UK pharmacy operators that have piloted this in 2025 report stable behaviour during peak counter periods.
- Medplum Form Renderer. Medplum's bundle suits pharmacy chains that want a single platform across multiple branches, with the renderer plugged into the same FHIR storage and identity layer used elsewhere. The draft persistence story works well when a consultation is interrupted by a queue and the pharmacist needs to resume later in the day.
- LHC-Forms in a Lightweight Web Shell. A surprising number of community pharmacy pilots in 2026 lean on LHC-Forms wrapped in a custom thin web shell, because the small renderer fits the shared-workstation environment and the source-available licensing removes vendor risk for smaller pharmacy groups. The styling and dm+d integration require investment, but the long-term cost story is attractive.
- Firely Forms. Firely Forms is the right pick for pharmacy groups that prefer a managed rendering service over a self-hosted stack. Operationally, the hosted approach is the lowest-effort way to keep the renderer current with SDC updates, and the SDK lets a development team customise where it matters.
- Open Health Foundation Form Engine. The community-maintained engine deserves a place here because the licensing model and governance structure suit charity-aligned and not-for-profit pharmacy groups. Feature pace lags the commercial options, but the SDC behaviour that pharmacy services depend on is stable.
- Smile CDR Forms. Smile CDR's commercial bundle is the natural pick for larger pharmacy chains already centralising on a single FHIR vendor. The managed terminology service handles dm+d well, and the support model fits operating teams that prefer to buy reliability rather than build it.
How to Pilot These in a Live Counter Setting
Two practical tests separate the candidates fast. First, run a Pharmacy First-style consultation form end to end on a representative workstation during a real busy period, and watch the time-to-render and the dm+d look-up latency. Second, ingest the resulting QuestionnaireResponse into the GP system the pharmacy expects to send back to, and check it lands as discrete coded data rather than a narrative blob.
For the broader build vs buy framing on FHIR form tooling, the complete guide to FHIR form builders for UK healthcare in 2026 covers the strategic picture. For an adjacent scenario where the same renderer choices matter differently, the 5 FHIR form builders that handle multi-provider referral forms is worth reading alongside this list.
Sources
- WHC introduction of HL7 FHIR in NHS Wales bodies - PDF, NHS Wales / GOV.WALES, 2023
- Dictionary of medicines and devices (dm+d) reference page - HTML, NHS England Digital
- Smart Forms React-based SDC renderer - GitHub, Aehrc CSIRO