Minutes meeting: Working Group 14 (Security) of the dicom standards Committee Place

of the DICOM Standards Committee

Members Present:

Merge Technologies John Fehrenbach

Siemens Medical Solutions Lawrence Tarbox

Toshiba Hidenori Shinoda

Members Absent:

JIRA Isao Ohbayashi

Konica Medical Imaging Hitoshi Yoshimura

Philips Medical Systems Cor Loef

RadPharm David Clunie

Others Present:

Ed Larsen, Inc. Ed Larsen

ETIAM Emmanuel Cordonnier

GE Medical Systems John Moehrke

Kaiser Permanente Greg Thomas

Medifacts Systems Cheryl Tyus

Philips Research K. P. Lee

Siemens Medical Solutions Mike Cassidy

Siemens Medical Solutions Helmut Koenig

Siemens Medical Solutions Glen Marshall

Siemens Medical Solutions Jim Schiel

University of Magdeburg Bernd Blobel

University of Washington Blair Cockerline

Veterans Health Administration Amy Page

Veterans Health Administration Mike Davis

NEMA Staff Howard Clark

1. 
   Preliminary Events
   

2. 
   Approval of Previous Minutes
   

3. 
   Security in IHE
   

4. 
   Audit Trails Remote Logging Protocol
   

• 
  HL7 Security & Accountability SIG has balloted an informative document for an audit message. Planning to create an HL7 v3 standard.
  
• 
  DICOM WG 14 has been tasked with developing methodologies for sending audit trail information to a central repository.
  
• 
  ASTM has balloted and adopted a standard specification for audit and disclosure logs for use in healthcare information systems.
  

• 
  Commonality between DICOM and HL7 work exist for these use cases and the associated data:
  
  • 
    Access and modifications to the security database, e.g., adding user accounts, changing privileges, etc.
    
  • 
    Access and modification to the audit data
    
  • 
    Application domain security-relevant use cases that do not require knowledge of the application data or business rules, e.g., user logins and directory/file level access.
    
  • 
    Security-relevant event data arising from the underlying messaging and transport infrastructure.
    
• 
  Application domain security-relevant uses cases that do require knowledge of the application data or business rules may lack data commonality. If there are common data among such events, the vocabularies for such data may be distinct among application domains.
  
• 
  We should jointly agree on the common use cases and data. This would be best reflected in an XML schema.
  
• 
  The audit data payload should be independent of the underlying message framing and transport. For example, we see that ebXML may be appropriate in the HL7 implementations but Reliable Syslog (RFC 3195) may be appropriate for DICOM.
  
• 
  A standard specification for controlling detail-level of audit data is highly desirable.
  
• 
  A standard specification for audit data retention and purging is highly desirable.
  
• 
  We should explicitly exclude forensic data-gathering, e.g., before/after data change logs, from the scope of the work.
  
• 
  A follow-up joint meeting [this one] will occur during the HL7 meeting in January. This will refine the work and detail direction we will take.
  

5. 
   Adding Digital Signatures to Structured Reports
   

6. 
   New Business
   

7. 
   Date for Next Meeting
   

Various other, related groups are expected to meet in conjunction with the SPIE Conference in San Diego in February of 2002. The chair will consult with leaders of these groups to determine whether there would be sufficient benefit for WG-14 to meet at that time also.

Beyond February of 2002, the next meeting will be held at NEMA headquarters on April 23, 2002.

8. 
   Adjournment
   

Reported by: Howard E. Clark

Secretary

January 23, 2002

Reviewed by Counsel:

Appendix One

JOINT MEETING

HL7 Security & Accountability SIG

with

Imaging Integration SIG

and

DICOM’s WG-14 and WG-20

By Glen Marshall, Siemens

1. 
   Note: We need to ensure that selective audit & selective reporting is formalized more clearly.
   
2. 
   Tasking –
   

1. 
   HL7 to handle
   

1. 
   Session & transport (neutral as to underlying transport)
   
2. 
   Security admin audits
   
3. 
   Audit trail management audits
   
4. 
   User login/logoff
   
5. 
   Specification of mandatory minimum auditing (non-normative guidelines, normative references?)
   
6. 
   Draft of mapping between cross-industry security logs to HL7 spec. (normative vs. guidance?), noting that this will uncover a lot of dragons. This does NOT substitute for system audit & its purposes for security assurance. Think of this effort as application domain audits with a digest of relevant system-level events.
   

2. 
   Application groups (DICOM, etc., including HL7) need to handle application specific data
   
3. 
   ASTM to handle
   

1. 
   ID of commonalities between HL7 & ASTM work
   
2. 
   Selective audit & selective reporting is formalized more clearly
   

4. 
   HL7, DICOM, ASTM to jointly cover vocabulary
   

1. 
   ID of external references, e.g., ISO/TC 215 WG 4 glossary
   

5. 
   Explicitly not in scope: Further use cases, trigger events, coverage of national & organizational requirements for … (perhaps non-normative notes & references?)
   

1. 
   Rules for production of audit (excl emergency access, which is covered by ASTM?)
   
2. 
   Rules for consumption of audit – reporting, heuristics, alarms
   
3. 
   Rules for archiving
   
4. 
   Rules for purging
   
5. 
   Backup/recovery (guarantee of audit availability)
   

6. 
   Non-Normative references/guidance/appendix: Scalability (joint HL7, ASTM, DICOM)
   

1. 
   Scale-up
   
2. 
   Scale-down
   
3. 
   Guidance on efficient use of computing resources
   

7. 
   ASTM covers (guidelines or normative?) Systems Management
   

1. 
   Actions in case of audit unavailability
   

3. 
   Logistics
   

1. 
   Minutes –
   

1. 
   HL7 – www.hl7.org
   
2. 
   NEMA/DICOM/SPC – medical.nema.org
   

2. 
   Meetings (joint will occur somewhere within this)
   

1. 
   DICOM WG 14: April 23 @ NEMA, June 26 In Paris, Sept 25 at NEMA, December 6 @ RSNA
   
2. 
   HL7: April in Atlanta, Oct in Baltimore, Jan in San Antonio
   
3. 
   ASTM: Seattle @ TEPR, November @ ?
   
4. 
   Conf calls: vocabulary, monthly synch? TBD – first one needs to cover use cases & vocab. – time to be determined based on national participation requirements.
   

3. 
   Listserve
   

1. 
   www.hl7.org, Security & Accountability SIG listserve
   
2. 
   DICOM WG 14, imaging domain only
   

4. 
   Document repository
   
   1. 
      GFM to set this up
      

4. 
   Work schedule
   

1. 
   HL7 – target is normative v3 spec for CQ committee ballot in Oct. – Aug 1 completion for publication.
   

1. 
   Intermediate drafts to be placed on doc repository & notice via listserv
   
2. 
   First item is use cases – Tentative first pass due 2/9.
   
3. 
   Other artifacts TBD
   

2. 
   DICOM
   

1. 
   Draft of Imaging specific portion, referencing HL7 base, public comment target is approx same as HL7 doc.
   
2. 
   Use cases - Tentative first pass due 2/9.
   

3. 
   ASTM
   

1. 
   Cross-ref with HL7 S&A informative document – Tentative first pass due 2/9.