Date validation (sequence)

[AndyRae]

Is this the right issue type?

• Yes, I'm planning work for this project team.

Summary

A lot of QA is often to do with the sequence of dates across a CDM.

For example, the test date is before the diagnosis date, the surgery date should be after, but all of which should be before the death date.

Currently a human checks and is up to error, and hard to scale. It's also not always intuitive for a non-expert to understand what the sequence even should be.

We should make this easier - and require a user to outline the sequence they expect, and warn if there are inconsistencies. Some of this logic is often available in a CDM documentation.

This is a fairly straightforward ruleset to build up, so we need to design how the input structure would be - likely similar to the current date shift dictionary.

Acceptance Criteria

• User can outline their expected sequence of dates
• Tool should warn if the sequence is inconsistent with data
• Documentation added.

Tasks

• Task A.
• Task B.
• Unit tests.
• Documentation.

Confirm creation

• Ready to create this deliverable?