Patient-reported outcomes drive a lot of how a modern cancer center measures care quality, and the form engine sitting underneath that capture pipeline is the unsung middle layer. PROMIS short forms, EORTC QLQ-C30, FACT-G, symptom-tracking diaries, and survivorship follow-ups all run through a Questionnaire renderer that has to be both spec-conformant and patient-friendly. The seven form engines below have shipped against real PRO workloads in 2026. For the FHIR comparison index, the broader walkthroughs round out the comparison.
The Seven Engines Cancer Centers Are Actually Running
- LHC-Forms. The default reference renderer from the National Library of Medicine. Handles PROMIS adaptive-test patterns via initialExpression and answerOption value-set bindings. Most academic cancer centers start here.
- Smile Digital Health Forms. Tightly bundled with the Smile CDR. The advantage in a cancer-center deployment is that the FHIR ValueSets for symptom severity, performance status, and toxicity grading sit in the same server that stores QuestionnaireResponses.
- Form.io with FHIR adapters. Wins on patient-facing UX for at-home symptom diaries. Cancer survivorship programs use it for the multi-month follow-up cadence where engagement matters more than schema purity.
- InterSystems IRIS for Health Forms. Enterprise stack, well-suited to integrated cancer centers that already run IRIS for their broader EHR data layer. Strong on Subscription-driven workflows where a PRO score crossing a threshold triggers a clinician alert.
- MedicalMine SDC. Newer, but has gained adoption in mid-sized cancer centers for its handling of calculated-score logic. PROMIS T-score conversion happens inline rather than in a downstream job.
- HAPI FHIR with custom form layer. The DIY route. Most useful when the cancer center has dedicated FHIR engineering capacity and wants total control over the rendering layer.
- Vermonster Healthcare Forms. Picked by several NCI-designated cancer centers for trial-aligned PRO capture, where the form has to match the protocol-mandated instrument exactly.
The seven cover the practical spectrum from pure-open-source through fully managed commercial.
The Three Capabilities That Matter Most for PRO
PRO workflows put pressure on three specific capabilities. Adaptive-test handling: PROMIS computerized adaptive tests need the next item to depend on the score so far, which means the engine has to evaluate logic between items, not just at submit. Multi-instrument bundling: a single PRO visit might include FACT-G, ESAS, and a custom symptom diary, all submitted as a single Bundle of QuestionnaireResponses. Score-to-Observation extraction: the form engine should produce a typed Observation per scored instrument, not just store the raw responses, so the oncology team can query trends without writing extraction code.
A cancer center evaluating engines should run a proof-of-concept against its own PRO instruments before signing. The cardiology practice cornerstone walks through the broader evaluation framework, and the open-source SDC vs EHR-native comparison compares the staffing trade-offs specifically for oncology.
Why the Long Tail Matters Here
Cancer centers run PRO programs over years, not quarters. The instrument set evolves, the patient cohort shifts, and the regulatory expectations around real-world evidence get tighter. A form engine that is easy to extend without breaking historical responses is worth more than one with a shinier launch demo. All seven of the engines above clear that bar in 2026 deployments.
Cancer-center PRO programs that pilot two or three of these engines side by side, with real instruments and real patients, end up with a defensible choice within a quarter. The instrument set will keep evolving past 2026, and the engine that handles change cleanly is worth more than the one with the prettier launch demo.
The cancer-center adoption pattern in 2026 leans toward bundling one engine for clinician-side capture and another for patient-facing diaries, with both feeding the same FHIR store. That split is worth designing for from day one rather than retrofitting it after the first year.