Security Audit and Access Accountability Message XML Data Definitions for Healthcare Applications
RFC 3881

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: RFC Editor <rfc-editor@rfc-editor.org>
Cc: The IESG <iesg@ietf.org>, <iana@iana.org>, ietf-announce@ietf.org
Subject: Re: Informational RFC to be: 
         draft-marshall-security-audit-13.txt 

The IESG has no problem with the publication of 'Security Audit and 
Access Accountability Message XML Data Definitions for Healthcare 
Applications' <draft-marshall-security-audit-13.txt> as an Informational 
RFC. 

The IESG would also like the IRSG or RFC-Editor to review the comments in 
the datatracker 
(https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=9730&rfc_flag=0) 
related to this document and determine whether or not they merit 
incorporation into the document. Comments may exist in both the ballot 
and the comment log. 

The IESG contact person is Scott Hollenbeck.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-marshall-security-audit-13.txt


The process for such documents is described at http://www.rfc-editor.org/indsubs.html.

Thank you,

The IESG Secretary

Technical Summary
 
This document defines the format of data to be collected, and minimum 
set of attributes that need to be captured, for security auditing in 
healthcare application systems.  The format is defined as an XML 
schema, which is intended as a reference for healthcare standards 
developers and application designers.  It consolidates several 
previous documents on security auditing of healthcare data.
 
Working Group Summary
 
This document is not the product of an IETF working group.  Publication
for the information of the IETF community has been requested through the
RFC Editor.
 
Protocol Quality
 
Scott Hollenbeck has reviewed this specification for the IESG.

RFC Editor, please include this IESG Note:

This RFC is not a candidate for any level of Internet Standard.  The 
IETF disclaims any knowledge of the fitness of this RFC for any purpose, 
and notes that it has not had IETF review. The RFC Editor has chosen to 
publish this document at its discretion.