Prior authorization workflows in US healthcare still run heavily on PDF forms, faxed or emailed between provider and payer. The Da Vinci IGs and the SDC-based Documentation Templates and Rules pattern promise a structured alternative, but t

Immunization registry intake on FHIR turns Questionnaire submissions into Immunization resources that downstream IIS systems consume through HL7 v2 VXU or FHIR R4. The form builder has to honor the CDC IIS-related Questionnaire patterns, in

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 kio

A multi-site clinical trial runs the same SDC Questionnaire across sites that each have different EDC histories, different IRB protocols, and different operational constraints. The form engine has to honor the trial protocol, support cross-

Pre-op screening is a high-stakes intake workflow. The Questionnaire has to cover allergy, anticoagulation, airway, and anesthesia history; the answers feed clinical decisions made hours before incision; and the form has to handle both pati

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 offl

A prior authorization workflow on FHIR runs SDC Questionnaires at the boundary between provider and payer, with the Da Vinci Documentation Templates and Rules IG providing the spec-aligned shape. The form engine underneath has to honor SDC

A chronic care program runs the same FHIR Questionnaire against the same patient repeatedly over months or years. The Questionnaire tool underneath has to handle versioning, longitudinal answer comparison, and renderer consistency across th