As EDITOR USER, I want to see an audit trail of a rule so that I can see a transactional history of changes made.

[chowsanthony]

Points for consideration:

• Depends on business requirements, this ticket may need to be broken up into manageable chunks.
• Audit trails stemmed from rule versioning discussion. The team recognizes not all changes require re-tests, e.g., cosmetic changes to rule message.
• An audit trail record may include, but not limited to information about who, when, what, how, and why a change is made.
• What is the retention policy?
• When does audit trail start for a rule? If it starts from drafting, we need to factor in volume of audit trail records.
• Can we leverage GitHub for solutioning this? For example, use it as a repo for rule files therefore commit tree is a form of audit trial.
• To whom is audit trail used by?
• How do we want the audit trail records to be accessed? Format, interface, etc.
• There is a crossover between audit trail and revision tracking. How do we leverage them to simplify the requirements, hence implementation?
• What does provenance mean to you?
• Use case: Management of FDA rules