7 Feb 2018 (Brian Postlethwaite, Louis Bedor 3-0-0)
The VerificationResult resource records the details and results of a resource that needs to be, or has been verified by multiple parties. It does not represent the workflows or tasks related, but does cover the who did what when, why, and when it needs to be done again.
This is in contrast to the AuditEvent which could record that a resource was received from someone, and the Provenance that records who it came from.
It was considered to be implemented as a profile on Provenance, however this seems to be different in scope in that its includes details of the verification.
(A similar concept exists outside of healthcare in Art/Musical Equipment in Appraisals vs Provenance, the provenance of the piece covers its chain of ownership, where an appraisal covers how it was check for its authenticity)
When receiving content from a 3rd party system (such as a directory) it is important to be able to determine the quality of that data. This resource provides a receiver of the content the knowledge of where the data came from (especially where content was aggregated from multiple sources)
This is to be stored external to the resource, instead of within it, so that where not required, the additional content of the verification (which could be quite extensive) does not need to be loaded.
The ONC has indicated that they desire to create a service that uses this capability where they will be distributing aggregated healthcare directory data from a central service to Organizations for local usage (based on a specific data usage agreement)
Reference(any) - Our initial requirements are needed against:
We do not currently expect other resources to specifically reference VerificationResult
May Ballot 2018 - draft is in the build that went to the Jan 2018 Comment ballot
When you have completed your proposal, please send an email to FMGcontact@HL7.org