This wiki has undergone a migration to Confluence found Here
Difference between revisions of "HL7 FHIR AuditEvent Resource"
Jump to navigation
Jump to search
(Created page with "Back to Security Main Page Back to HL7 FHIR security topics ==FHIR AuditEvent Foundational Standards== *[") |
|||
| (13 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
[[HL7 FHIR security topics|Back to HL7 FHIR security topics]] | [[HL7 FHIR security topics|Back to HL7 FHIR security topics]] | ||
| + | |||
| + | = Work Plan= | ||
| + | [http://hl7-fhir.github.io/auditevent.html 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]]= | ||
==FHIR AuditEvent Foundational Standards== | ==FHIR AuditEvent Foundational Standards== | ||
| − | *[ | + | *[http://dicom.nema.org/medical/dicom/current/output/html/part15.html#sect_A.5.3.3 DICOM PS3.15 2015c - Security and System Management Profiles] |
| + | *[http://dicom.nema.org/dicom/2001/01_16PU.PDF Digital Imaging and Communications in Medicine (DICOM)Part 16: Content Mapping Resource] | ||
| + | *[http://dicom.nema.org/dicom/2003/03_06PU.PDF DICOM Data Dictionary] | ||
| + | *[http://wiki.ihe.net/index.php?title=ATNA_FAQ IHE ATNA FAQ] | ||
| + | *[http://wiki.ihe.net/index.php?title=ATNA_Profile_FAQ IHE ATNA Profile FAQ] | ||
| + | *[http://tools.ietf.org/html/rfc3881#page-8 RFC 3881 Security Audit and Access Accountability MessageXML Data Definitions for Healthcare Applications] | ||
Latest revision as of 21:47, 15 November 2015
Back to HL7 FHIR security topics
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
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
