FHIR Questionnaire vs HL7 v2 Forms for Modern Intake

Modern clinical intake in US healthcare still depends heavily on HL7 v2 messages that carry form-shaped data: ADT for registration, ORM for orders, MDM for documents that originated as intake forms. The FHIR Questionnaire path offers an alternative that ships the form's structure with the submission rather than burying it in OBX repetitions and free-text segments. The comparison below covers what each format gets right in 2026 intake deployments. For broader context, see the FHIR clinical workflow reference.

What HL7 v2 Intake Gets Right

HL7 v2 wins on the existing infrastructure. Every US EHR speaks v2, every interface engine routes v2, and the operational tooling for v2 has been hardened across decades. Intake forms expressed as v2 messages flow through pipelines that already work without any new investment.

V2 also wins on stability. Field positions are pinned by the spec, segment ordering is well-understood, and the customizations that every site adds are absorbed into the local v2 dictionary without requiring a global registry update. The pragmatic side of US healthcare interoperability runs on this stability.

Where v2 falls down is the structure. Intake forms with conditional logic, branching, or complex validation collapse into OBX repetitions that lose the form's intent. Downstream consumers reconstruct the form's shape from convention rather than from the message itself. The FHIR Questionnaire tools for chronic care roundup covers the workflows where the structure loss matters most.

What FHIR Questionnaire Gets Right

FHIR Questionnaire wins on submission fidelity. The QuestionnaireResponse carries the answers in their original typed form, linked back to the Questionnaire definition that the answers were given against. Downstream consumers know exactly what was asked, what was answered, and which rules applied at submission time.

Questionnaire also wins on the dynamic logic. SDC behaviors evaluated at submission catch invalid answers before they enter the system. Value-set bindings reject codes that downstream consumers cannot handle. Cross-field expressions validate consistency without forcing the consumer to recheck.

Where Questionnaire falls down is the legacy ecosystem. Few production EHRs accept Questionnaire submissions natively. Few intake pipelines route them. The investment to add Questionnaire support is real on both the producer side and the consumer side. The SDC questionnaires vs static PDF forms comparison covers the related migration friction in the prior-authorization case where the chicken-and-egg dynamic has been slowest to resolve.

How to Pick in Practice

Three questions decide between the formats. The first is the consumer ecosystem. Intake that flows into an existing v2 pipeline stays in v2 unless the migration has executive sponsorship. Greenfield intake without a v2 commitment can pick Questionnaire from the start.

The second is the form complexity. Simple intake (registration, demographics, basic history) survives the v2 round trip without losing structure. Complex intake (specialty assessments, scored screening instruments, multi-page conditional forms) loses too much in v2 and benefits clearly from Questionnaire.

The third is the regulatory trajectory. CMS interoperability rules and the 21st Century Cures Act have moved structured intake toward FHIR, which sets a floor on the long-term Questionnaire commitment. Programs with multi-year horizons benefit from starting the transition; programs with shorter horizons stay on v2.

Most production intake stacks in 2026 run both. The right balance depends on the consumer ecosystem, the form complexity, and the regulatory trajectory, not on the longest feature checklist on a vendor page.