Top 4 SDC Renderers for Tablet-Based Clinical Intake

Tablet-based clinical intake stresses an SDC renderer in ways desktop and patient-portal rendering do not. Touch input changes the form-control sizing assumptions, intake staff hand devices between patients, and the device often runs in kiosk mode without a keyboard. The four renderers below cover the realistic options for tablet-based SDC rendering in 2026. For broader context, see the FHIR engineering reference.

The 4 SDC Renderers to Know for Tablet Intake

LHC-Forms Web with Tablet Configuration. The NLM renderer in its mobile-optimized profile, paired with the touch-target sizing rules that intake tablets need. Where it shines is conformance and the zero-license cost; where it falls short is the kiosk-mode hardening, which intake teams build on top.

Open Health Hub Tablet Renderer. Designed around patient-facing tablet intake from the start, with explicit kiosk-mode support, idle timeout handling, and the inter-patient handoff workflow. Strong fit when intake runs entirely on shared tablets without per-patient device assignment.

Smile Digital Health Tablet Forms. A managed renderer with the Smile patient-portal codebase tuned for tablet form factors. Useful when intake is part of a broader Smile-anchored deployment and the operations team prefers a vendor-supported renderer.

Medplum Forms with Custom Tablet Wrapper. The Medplum form-rendering library embedded in a custom wrapper that handles the tablet-specific concerns (kiosk mode, idle handling, inter-patient handoff). Useful for engineering-heavy teams that want full control of the tablet UX.

Tablet-based intake shares renderer concerns with remote patient monitoring on patient-owned tablets and with pre-op screening in the surgical holding area. The FHIR form builders for remote patient monitoring roundup and the FHIR intake tools for pre-op screening roundup cover those adjacent surfaces.

How to Pick the Right Renderer

Three questions narrow the field. The first is the inter-patient handoff requirement. Shared intake tablets cycle through dozens of patients per day. Renderers without explicit handoff workflow leak patient data between sessions, which is a regulatory exposure that compounds quickly.

The second is the kiosk-mode hardening. Tablets running unattended in waiting areas need renderers that resist accidental navigation, prevent task switching, and recover cleanly from idle timeouts. The managed options (Open Health Hub, Smile) handle this out of the box; the open-source options need additional work to reach the same hardening.

The third is the integration depth with the rest of the intake workflow. Renderers that ship as standalone web apps integrate cleanly with any FHIR back end. Renderers tied to a specific platform (Smile tablet forms, Medplum-based wrappers) integrate better with that platform's Task and Subscription surfaces but bind the intake choice to the back-end choice.

A working tablet renderer fades into the patient intake experience. The wrong one shows up as data leakage between patients, intake staff coaching every patient through the form, and a backlog of incomplete submissions that intake has to reconcile manually. Selection ends up matching the renderer's strengths to the handoff requirement, the kiosk-mode hardening needed, and the back-end integration profile, not to the longest feature checklist on a vendor matrix. Tablet renderers that survive the first month of unattended waiting-area use usually had explicit handoff and idle handling from the start; the rest reveal the gaps in the first regulatory review that asks how patient data is isolated between sessions on a shared device.