Document provenance and lineage
N
Nick Adams
I appreciate that Heidi is primarily for content generation, but as it evolves and expands in its functionality, it really needs more sophisticated methods for auditing the life cycle of a generated document. At the simplest level, there needs to be some simple visual method of determining when somebody within a group of users has, for example, emailed or printed a given letter/document within the Heidi environment, come and ideally with more comprehensive document access logs
Tom
Great to hear your perspective, Nick Adams! I have a few more questions for you:
- What specific types of document access logs would be most useful for your needs?
- How important is it for you to have real-time notifications when a document is accessed or modified?
- Are there any specific security or privacy concerns we should consider when implementing document auditing features?
N
Nick Adams
Tom access logs - who and when has last edited, printed, or emailed a document for a given encounter. I'm thinking mostly of just knowing as the clinician that say, a letter has been processed by a secretary (or me). On this note docs need to have an option to 'lock' them so flag that they are ready for processing (i.e. a method for an admin person to know "no further changes needed by me proceed") basically the same as proof reading and "signing off" before dispatch in standard dictation-transcription work flow. From an audit perspective its not so much about being able to forensically track a doc from generation to dispatch, but more to be able to say get logs of overall activity (number of pieces of correspondence processed by a given person or activity group/dept/division over a time period) to get a dashboard overview of work and throughput