This wiki has undergone a migration to Confluence found Here
Difference between revisions of "HL7 FHIR AuditEvent Resource"
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
=[[AuditEvent Change Proposals from Gforge]]= | =[[AuditEvent Change Proposals from Gforge]]= | ||
| − | |||
| − | |||
| − | |||
=References= | =References= | ||
Revision as of 21:47, 15 November 2015
Back to HL7 FHIR security topics
Contents
Work Plan
AuditEvent Resource Current Build
- Address outstanding AuditEvent CPs from January 2015 FHIR Ballot mistakenly assigned to FHIR Infrastructure
- harmonize the structure, element names, and vocabulary as much as possible with Provenance.
- document use cases for interoperable FHIR AuditEvent - e.g., federated system with central AuditEvent Service - intra- and inter-enterprise.
- address the thought experiment of why do we have both Provenance and AuditEvent. (motivation vs consequence) (medical records vs security surveillance)
- See http://hl7-fhir.github.io/auditevent-mappings.html#w3c.prov
- See http://hl7-fhir.github.io/auditevent-mappings.html#fhirprovenance
- See http://hl7-fhir.github.io/provenance-mappings.html#w3c.prov
- See http://hl7-fhir.github.io/provenance-mappings.html#fhirauditevent
- See http://hl7-fhir.github.io/w5
AuditEvent Change Proposals from Gforge
References
FHIR AuditEvent Foundational Standards
- DICOM PS3.15 2015c - Security and System Management Profiles
- Digital Imaging and Communications in Medicine (DICOM)Part 16: Content Mapping Resource
- DICOM Data Dictionary
- IHE ATNA FAQ
- IHE ATNA Profile FAQ
- RFC 3881 Security Audit and Access Accountability MessageXML Data Definitions for Healthcare Applications
