Understanding the subject diagnostic report

The subject diagnostic report is a text listing, with header lines giving the timestamp of the report and the subject specification. The next line is one of the following:

*** Data inconsistencies found – one or more errors were found in the subject's data

No Problems Found

For a subject in which no data inconsistencies are detected, the diagnostic report simply lists counts of various items. For example:

Data inconsistencies found

If any inconsistencies are found they will be reported in the following categories:

If an active visit or eForm has been deleted from the study definition since the subject was saved, this will be reported as follows:

18/04/2012 16:01:27

SUBJECT: DUTest_2/balham/1 tr1

*** Data inconsistencies found

Visit instance count = 3

eForm instance count = 10

Expected Arezzo task instances = 24

Arezzo task instance count = 24

Responses count = 26 (24 non-empty values)

9 responses with invalid references

MACRO eForm definition not found, task ID = 10006, eForm ID = 10014, name = F3

18/04/2012 16:01:27

The visit or eForm IDs are given, and the name if known. If any responses have been saved in this visit or eForm, they will contain invalid references to the deleted item, and the number of such responses is reported.

If an active eForm has been removed from a visit since the subject was saved, this will be reported as follows:

18/04/2012 15:45:17

SUBJECT: DUTest_2/balham/3 tr3

*** Data inconsistencies found

Visit instance count = 3

eForm instance count = 10

Expected Arezzo task instances = 24

Arezzo task instance count = 24

Responses count = 26 (24 non-empty values)

eForm F3 not found in visit V2 for eForm task ID 10027

18/04/2012 15:45:17

If any responses have been saved on this eForm, they will be reported as responses with invalid references.

If a question has been deleted from the study definition since the subject was saved, response data will contain invalid references.

18/04/2012 17:02:11

SUBJECT: DUTest_2/balham/2 GHT2

*** Data inconsistencies found

Visit instance count = 2

eForm instance count = 7

Expected Arezzo task instances = 17

Arezzo task instance count = 17

Responses count = 13 (13 non-empty values)

3 responses with invalid references

Question definition for ID 10005 not found, ResponseTaskId 100020003, repeat 1, question code Not Known, value Aspirin, user INFOC, timestamp 2012/02/27 15:38:24

18/04/2012 17:02:11

The DataItemId and ResponseTaskID are given, and also the value and timestamp of the response. Only the first response for each deleted question is listed, but there may be more if the question is used on other eForms - the total number of invalid responses is given.

If a question has been removed from an eForm since the subject was saved, response data will contain invalid references.

18/04/2012 16:57:34

SUBJECT: Demostudy40/barbados/3 ADG 482X

*** Data inconsistencies found

Visit instance count = 8

eForm instance count = 54

Expected Arezzo task instances = 117

Arezzo task instance count = 117

Responses count = 65 (55 non-empty values)

1 responses with invalid references

Question does not exist on eForm cover, ResponseTaskId 100220022, repeat 1, question code clinname1, value Fenella, user INFNJ, timestamp 2012/03/21 09:28:46

18/04/2012 16:57:34

If a question is removed from an eForm and then replaced, it may have a different "CRFElementID" (which identifies the question on that particular eForm) and this causes invalid references.

18/04/2012 17:08:21

SUBJECT: DUTest_2/balham/4 JHS4

*** Data inconsistencies found

Visit instance count = 2

eForm instance count = 7

Expected Arezzo task instances = 17

Arezzo task instance count = 17

Responses count = 13 (13 non-empty values)

1 responses with invalid references

Question's element ID has changed from 2 to 6 on eForm F2, ResponseTaskId 100040002, repeat 1, question code q2, value leg, user PQR, timestamp 2011/12/28 18:43:16

18/04/2012 17:08:21

If no rows in the Arezzo tables are found for a subject, or if the "Arezzo Key" is missing or invalid, the report will contain a message saying that the Arezzo data was not found. No checks can be made against Arezzo, although the MACRO data integrity will still be checked. Note that this situation will be rare, and is only likely to arise through an unexpected software error or an unsuccessful upgrade from MACRO v3 to MACRO v4.

18/04/2012 13:28:57

SUBJECT: DUTest_2/balham/12

*** Data inconsistencies found

Visit instance count = 2

eForm instance count = 7

Expected Arezzo task instances = 17

ERROR - Subject's Arezzo data not found (no Arezzo Key)

Responses count = 13 (13 non-empty values)

Question's element ID has changed from 5 to 6 on eForm F6, ResponseTaskId 100080005, repeat 1, question code q3, value yes, user npd, timestamp 2012/03/10 17:20:16

18/04/2012 13:28:57

Arezzo task inconsistencies will be rare, and are only likely to arise through an unexpected software error or an unsuccessful upgrade from MACRO v3 to MACRO v4.

The following errors may be reported:

The Arezzo task for a MACRO eForm or visit is missing
An Arezzo "plan" task for a MACRO eForm does not contain its expected "action" task
An Arezzo task for a MACRO eForm or visit has the wrong task type
The name of an Arezzo task for a MACRO eForm or visit does not match the MACRO name
The cycle number of an Arezzo task does not match the MACRO eForm or visit cycle number
Arezzo contains extra tasks not recognised as MACRO visits or eForms

2/04/2012 13:28:57

SUBJECT: DUTest_3/balham/16

*** Data inconsistencies found

Visit instance count = 2

eForm instance count = 7

Expected Arezzo task instances = 17

Arezzo task instance count = 17

Responses count = 10 (10 non-empty values)

Arezzo task type is incorrect for F2, task key 10004, expected plan, found keystone

Arezzo task name F6x does not match MACRO name F6, task Id 10008

MACRO name F6 does not match Arezzo task name F6x, task Id 10008

Arezzo cycle number is incorrect for F4, task Id 10020, expected 1, found 2

MACRO cycle number is incorrect for F4, task Id 10020, expected 2, found 1

2/04/2012 13:28:57

If new Arezzo tasks have been added to a MACRO study by the study designer, these will be reported as "unrecognised" tasks. It is up to the study designer to verify that these tasks have been intentionally added to the study, or whether this represents a data problem.

19/04/2012 11:11:32

SUBJECT: FLUTE/tooting/9

*** Data inconsistencies found

Visit instance count = 1

eForm instance count = 2

Expected Arezzo task instances = 6

Arezzo task instance count = 7

WARNING - Arezzo task count does not match MACRO visits and eForms

Responses count = 4 (3 non-empty values)

Unrecognised Arezzo action task found, MyAction, task key 10006

19/04/2012 11:11:32