FormPathPUBLIC BETA

REDCap change control

Changed a REDCap choice code? Check every branch that still expects the old value.

Changing a choice label is visible. Changing its stored code is structural: every branching rule, calculation, import, and downstream process that expects the earlier code may now describe a value respondents cannot produce.

FormPath can compare two exported dictionaries and analyze supported branches against the inline choices in each version. That makes code drift inspectable before the amended project is trusted with new data.

Compare REDCap dictionaries All guides

Diagnostic checklist

Work from the stored answer outward.

  1. 01

    Diff codes separately from labels

    A label can remain “Phone” while its code changes from 2 to 20. Review both columns rather than treating unchanged display text as unchanged behavior.

  2. 02

    Search every logic-bearing column

    Branching logic is the immediate risk. Calculations and runtime-dependent expressions may also retain the old code and require separate review.

  3. 03

    Analyze the candidate definition

    A stale code can make a supported branch impossible in the translated finite model. A working answer example shows when the new rule can be satisfied.

  4. 04

    Retest the amendment in REDCap

    Use native test records to exercise the affected instruments, events, calculations, and downstream workflows after updating the dictionary.

Example

The label stayed the same; the code did not

The stale branch asks for code 2, but the amended field offers only 10 or 20. For a supported finite condition, FormPath can establish that mismatch in the translated model rather than relying on someone to notice the hidden field during manual clicking.

Stale branch after recoding
contact_method,radio,"10, Email | 20, Phone",
phone_details,text,,"[contact_method] = '2'"
Branch aligned with the new code
contact_method,radio,"10, Email | 20, Phone",
phone_details,text,,"[contact_method] = '20'"

Honest boundary

What this guide and analyzer do not establish.

  • FormPath does not infer whether two different codes have the same clinical or operational meaning.
  • Only supported dictionary logic is compared semantically; runtime calculations, events, smart variables, and external systems still need project-specific review.
  • Updating an exported CSV does not update or validate the live REDCap project.

Keep debugging

Related REDCap guides.

REDCap branching logic not workingCheck a REDCap dictionary before launch

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.

Compare REDCap dictionaries