PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 05 Apr 2011 12:00 AM by  SuperUser Account
Suggestions/Questions for HICDEP Quality Assurance Checks
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages

SuperUser Account



Basic Member


Posts:289
Basic Member


--
01 Apr 2011 12:00 AM

    The Quality Assurance check named ATC006 (AllTables/CrossTable/"Any fields not coded as coding lists on the table definition") I think needs to be more specific for the field being tested.

    I was sitting with the DAD checks for the ART table– and we test both ART_RS and ART_ID for valid codes according to the table definitions. If a given record fails at least one of these checks then the error code ‘ATC006’ would not indicate which field failed.

    Perhaps it could be named ATC006_<fieldname> or something - or some other way of indicating we are talking of wrong code according to the table def. I think this could need further discussion.


    SuperUser Account



    Basic Member


    Posts:289
    Basic Member


    --
    04 Apr 2011 12:00 AM


    Thanks for your suggestions!

    So far I understood the error codes as a more formal 'problem description' in the sense that it gives the information about which aspect of the data is wrong but not what data is wrong. I agree that the error codes alone are not very helpful, however, I would envision a QA tool to report back error messages such as:

    tblART - ART_RS: [ATC006] field not encoded as coding lists on the table definition

    This has the advantage that it is easy to see if multiple variables suffer from the same problem.

    SuperUser Account



    Basic Member


    Posts:289
    Basic Member


    --
    05 Apr 2011 12:00 AM


    Yes I agree with Simon
    You are not authorized to post a reply.