TrialGrid manages Standard Libraries in a hierarchy of linked Drafts:
A Standards Library is simply a Draft inside a Project which has the “Is Standards Library” checkbox set. Every Draft can have one Standard Library set making a chain of standard libraries back to a root or top-level library.
The Standard Draft tree is a mechanism for determining compliance to the standard. For each object in a Draft ( a Form, Edit Check etc) TrialGrid follows the tree “up” back to the root looking for an object of the same name to compare to.
In the following example, Draft 1 uses the AE form but its direct parent CNS Standards does not contain the AE form. The AE form is originally defined in the Core Standards:
For every object in the Draft TrialGrid can determine if it is:
- Not found in the standard tree
- Found in the standard tree and is an exact match to the standard definition
- Found in the standard tree but is different to the standard definition
If the object is not found or if it is different from the standard definition then this should be explained.
Note that TrialGrid does not enforce copying objects from the Standard library. It is often convenient for the Study Builder to copy definitions for Forms or Edit Checks from a previous study. TrialGrid provides assurance that whatever the source, the object matches the selected Standard library. This approach provides the Study Builder with freedom to design in the most efficient way for them while also tracking standards compliance with no extra effort.
If an object has been changed from the standard definition then it is helpful to understand what the changes are so that these can be explained and approved for the study. TrialGrid provides a side-by-side color-coded comparison of objects in text form so that the differences can be quickly identified. Changes are highlighted in yellow, deletions are highlighted in red and additions in green.
Explaining and Approving Differences¶
When an object is not found in the Standard Library or is different from the standard definition, the Study Builder must explain this difference via a pop-up in the object listing. Once explained this difference can be Approved. If the object changes again (e.g. to add a new Field to a Form, or a change in an Query message in an Edit Check) then this approval is automatically removed and the difference must be approved again. The states of objects can therefore be:
- Not Found
- Not Found : Explained
- Not Found : Approved
- Deviation : Explained
- Deviation : Approved
An audit trail is kept of the explanations and approvals for deviations from the standards.
Reporting on Compliance¶
A summary of compliance metrics is available on the Standard Compliance page. This page shows the overall counts of objects found in the Standard Library Drafts vs how many were not found because they were new or were changed.
A PDF report of the summary can be generated from the same page.