FHIR Questionnaire troubleshooting

FHIR enableWhen not working? Compare the answer code with the inline options.

A Questionnaire can be structurally valid while an enabled item never appears. One quiet cause is an enableWhen answerCoding code that does not match any inline answerOption code on the referenced item.

FormPath translates supported Questionnaire conditions into a finite model. It can inspect bare inline codes, but it does not resolve external ValueSets or reduce Coding system and version semantics to a string comparison.

Diagnostic checklist

Work from the stored answer outward.

  1. 01

    Resolve the question linkId

    The enableWhen question value must identify an existing source item. Check the exact linkId before inspecting its options.

  2. 02

    Compare machine codes

    Match answerCoding.code against valueCoding.code. Display text can be identical while the code differs.

  3. 03

    Identify the answer universe

    Inline answerOption values create a finite choice set FormPath can model. answerValueSet and choices supplied at runtime remain external.

  4. 04

    Preserve terminology semantics

    If the condition depends on Coding.system or Coding.version, confirm it in the intended terminology and renderer environment.

Example

One missing letter creates an unavailable code

With an inline, non-repeating choice source and a bare code comparison, the first condition has no supplied answer that can satisfy it. The conclusion applies to FormPath's translated model, not to external terminology or renderer behavior.

Condition expects a code not offered
"answerOption": [{"valueCoding":{"code":"residential"}}],
"enableWhen": [{"question":"property-use","operator":"=","answerCoding":{"code":"residental"}}]
Condition uses the inline option code
"answerOption": [{"valueCoding":{"code":"residential"}}],
"enableWhen": [{"question":"property-use","operator":"=","answerCoding":{"code":"residential"}}]

Honest boundary

What this guide and analyzer do not establish.

  • FormPath is not a general FHIR validator and does not claim conformance of the Questionnaire resource.
  • External answerValueSet content, Coding system/version semantics, FHIRPath, CQL, launch context, and renderer behavior are not resolved.
  • Requiredness, data capture, and navigation behavior must be confirmed in the target Questionnaire implementation.

No signup · no upload

Ask which supported answer states are actually possible.

FormPath runs locally and exports each finding, how it was checked, and any important limits as JSON or Markdown.

Check a FHIR Questionnaire