Profiling AuditEvent seems to be an emerging need
Healthcare Exchange Standards
·
·
31 views
Watching the report outs for the CMS FHIR Connectathon. Many are mentioning that they see a need to profile AuditEvent for their use-case needs to support data access traceability, privacy tracking, and provenance. I very much agree with this. IHE has the starter kit with the Basic Audit Log Patterns (BALP) Implementation Guide defines the basics and has some profiles for common REST interactions.I often need to remind people that defining AuditEvent profiles can be supported purely as a Query interface. In this case the system keeps their audit log in their native format, but knows how to convert that into the FHIR Standard AuditEvent when queried.I would be glad to provide pointed and short-term consulting -- see Moehrke Research LLC
The Internet Protocol 
Slugger O'Toole 
Nyscinfo 
Goldfinch Blog 
Bloomberg Blog 
KevinMD.com 
