For a full list of available versions, see the Directory of published versions

2.3. Use Cases

This page provides high-level use cases supported by this Implementation Guide. These use cases describe generic capabilities that are independent of specific clinical workflows.

Out of scope: This IG does not define where forms are located, how users are notified to complete forms, prioritization/timeframes, or what happens to completed forms after completion (including packaging with other clinical/workflow content). Those workflow aspects are expected to be defined by use-case specific Ontario Health IGs.

2.3.1. UC1: Render an Ontario Health Questionnaire

A system retrieves and renders an Ontario Health-supplied Questionnaire in a user-facing interface.

Expected capability:

• Render Questionnaire structure (groups, questions, display items)
• Apply rendering instructions (e.g., item control codes, choice orientation, styling, rich XHTML content)
• Support conditionality rules (enableWhen / enableWhenExpression) to drive what the user sees

2.3.2. UC2: Capture a completed QuestionnaireResponse

A user completes the form and the system produces a conformant QuestionnaireResponse.

Expected capability:

• Preserve the Questionnaire’s item structure and linkId alignment in the QuestionnaireResponse
• Represent repeats correctly (repeated groups vs repeated answers)
• Capture answers using appropriate value data types
• Capture required response metadata as specified by the profile obligations

2.3.3. UC3: Validate responses during form filling

A system supports validation and flow control to reduce errors and ensure higher-quality data capture.

Expected capability:

• Enforce input-time constraints feasible in a form-filling context (e.g., min/max value, length, required/repeats)
• Apply rule-based constraints where declared (e.g., targetConstraint)

2.3.4. UC4: Pre-populate form answers

A system pre-fills form answers prior to user review using Questionnaire-defined expressions and available context.

Expected capability:

• Process Questionnaire population metadata (launch context, variables, initialExpression, itemPopulationContext)
• Populate answers into QuestionnaireResponse in a predictable and consistent manner

2.3.5. UC5: Extract structured data from a completed form

A system can perform definition-based extraction to transform QuestionnaireResponse content into derived resources for downstream use.

Expected capability:

• Process extraction metadata in the Questionnaire (definitionExtract, definitionExtractValue, extractAllocateId)
• Transform responses into derived resources as applicable to the use case

2.3.6. UC6: Generate a narrative summary of a completed form

A system generates a human-readable narrative for the completed QuestionnaireResponse.

Expected capability:

• Use Liquid templates (when provided) referenced by the Questionnaire to generate QuestionnaireResponse.text
• Produce a summary that supports quick clinical/administrative consumption of the captured information

2.3.7. UC7: Support interactive image-based answering

Some forms may support image-based interactions (e.g., clicking regions of an image to select/deselect answers).

Expected capability:

• Render interactive diagram content when declared by the Questionnaire
• Translate user interactions into the underlying QuestionnaireResponse answer structure