Top 6 FHIR Form Builders for Remote Patient Monitoring

Remote patient monitoring puts a FHIR form builder against constraints that clinic-only deployments rarely face. The forms run on patient-owned phones and tablets, network conditions are unreliable, and answer submission has to survive offline periods without losing data. The six tools below cover the realistic options for RPM-grade form building in 2026. For broader context, see more on FHIR workflow patterns.

The 6 Form Builders to Know for RPM

LHC-Forms Mobile. The NLM renderer in its mobile-optimized configuration. Where it shines is the zero licensing footprint and the conformance to SDC behavior; where it falls short is the offline support, which RPM programs typically build on top.

Open Health Hub Forms. Designed around the RPM use case from the start, with offline-first patient-facing rendering and explicit support for patient-reported outcomes. Strong fit for RPM programs that need a managed mobile surface without writing their own renderer.

Smile Digital Health Forms with Patient Portal. The Smile patient-portal rendering option, with form persistence and replay tied into Smile CDR. The right answer when RPM is run inside an existing Smile deployment.

Medplum Forms with Bot-Driven Threshold Alerts. Bots subscribe to QuestionnaireResponse submissions and trigger threshold-based clinical alerts in TypeScript. Useful when the RPM program needs custom alerting logic and the engineering team prefers code to configuration.

Firely Forms Mobile. The .NET-aligned option with Xamarin and MAUI renderer support for cross-platform mobile deployment. The right answer for Microsoft-aligned shops running RPM on Azure-hosted infrastructure.

Aidbox Forms with Custom Mobile Renderer. The FHIR-native multi-tenant option, typically paired with a custom mobile renderer per program. Where it shines is the tenancy model for RPM platforms serving multiple sponsors; where it falls short is the renderer requirement, which is the program's responsibility.

RPM Questionnaire administration shares its longitudinal characteristics with chronic care Questionnaire programs. The FHIR Questionnaire tools for chronic care roundup covers the longitudinal-analysis trade-offs in detail. RPM also borrows tablet-rendering patterns from clinical intake, which the SDC renderers for tablet-based clinical intake roundup covers.

How to Pick the Right Builder

Three questions narrow the field. The first is the patient-device footprint. Programs that issue devices to patients (BYOD-free) get more flexibility in renderer choice. Programs that depend on patient-owned devices need cross-platform renderers with strong offline support, which narrows the field considerably.

The second is the alert-and-escalation profile. RPM programs that trigger clinician alerts on threshold breaches need form builders with integrated workflow triggering through Subscription, Task, or bot frameworks. Programs that only collect data for retrospective review have lighter requirements.

The third is the program's existing operational footprint. Programs already running on Smile CDR or Aidbox benefit from staying in those footprints rather than introducing a separate form-builder platform. Greenfield programs can pick the form builder that best fits the patient-device and alert profiles independently.

A working RPM form builder fades into the patient experience and supports the clinical team without daily intervention. The wrong one shows up as missed submissions, data loss across offline periods, and alert latency that defeats the RPM program's purpose. Selection ends up matching the builder's strengths to the device footprint, the alert profile, and the existing operational stack, not to the longest feature checklist.