When adding a condition or disability to a person record, leaving the Age Diagnosed field blank causes forms that rely on health conditions data to fail to populate. This affects all conditions on the record, not just the one where Age Diagnosed was left blank. Forms such as assessments and reviews will appear empty or fail to display previously recorded conditions.

This article explains the issue, who is affected, the impact on your records, and a workaround to use until a fix is released.

Affected versions: 25.1.0 and 25.2.1.

Affected area: Person record > Health > Conditions/Disability.

The Age Diagnosed field in the condition or disability dialog is not mandatory. However, a recent change made the field optional without updating the underlying code that builds condition data for forms. When the system encounters a blank Age Diagnosed value, it causes an error that prevents all condition data from being returned to the form.

This means that if even one condition on a person record has a blank Age Diagnosed field, all conditions on that record will fail to appear in any form that relies on the health conditions data.

Any user adding or editing conditions or disabilities on a person record where Age Diagnosed is not completed.

Forms that use condition or disability data, such as assessments and reviews, will appear empty or fail to display previously recorded conditions. This can affect statutory returns and case recording.

Until a fix is released, ensure you enter a value in the Age Diagnosed field when adding or editing a condition or disability.

To apply the workaround to existing records:

Once all conditions have a value in the Age Diagnosed field, forms will populate correctly.

Bug 2210764 has been raised and is awaiting development. The fix will update the system to correctly handle a blank Age Diagnosed value so that forms populate as expected.