Device Management Infrastructure White Paper Brief Profile Proposal for IHE Year Dan Trainor, John Rhoads, Axel Wirth PCD MEM Working Group

IT Infrastructure Planning Committee How Might We Address the Unique Problems of Devices?

IT Infrastructure Planning Committee Status Work launched in Dec 2011 (scope & outline)Work launched in Dec 2011 (scope & outline) Jan 2012 change in role of ITI Project SponsorJan 2012 change in role of ITI Project Sponsor Initial premise has not changed, but reality has:Initial premise has not changed, but reality has: –PCD MEM still sees this a priority, needs to address these issues –ITI is responsible for infrastructure and can contribute / influence this out of the gate. –These needs are not unique to PCD (e.g. RAD) –Excellent opportunity to demonstrate cross-domain cooperation

IT Infrastructure Planning Committee New Approach PCD will carry whitepaper projectPCD will carry whitepaper project Key issues:Key issues: –Reduced resources –Loss of subject matter expertise –Loss of ITI sponsorship Path forward:Path forward: –No reduction in scope, work on relaxed timeline (whitepaper not tied to profile annual rhythm) –Call for resources (ITI, PCD) –Rely on ITI for consulting (questions, review) Dan Trainor will remain the PCD/ITI liaisonDan Trainor will remain the PCD/ITI liaison Process:Process: –Quarterly update to ITI and PCD, deeper discussion at F2F

IT Infrastructure Planning Committee Current Whitepaper Scope Outline:Outline: –Definition and Architecture –Asset Management –Asset Tracking –Discovery –Automatic Configuration –Monitoring and Logging –Patch Management –Lifecycle Management –Risk Management Guidance –Event Communication—non-alarm, system-to-system –Cyber Security Status –Information Privacy (encryption and similar) –Key Management –User-to–Device and Device-To-Network Authentication Note: the topics outlined will be purely IT focused and not deal with clinical functionality or patient management aspects.

IT Infrastructure Planning Committee Notes from 2/7/2012 Review Patch management is a critical issue and may become a “hot button” relative to other profiles or regulations (e.g. FISMA).Patch management is a critical issue and may become a “hot button” relative to other profiles or regulations (e.g. FISMA). Some technical management aspects (e.g. equipment calibration, tracking, and logging) may require coordination with other groups (build reference, e.g. NEMA Security and Privacy Working Group, IHE Operations Domain).Some technical management aspects (e.g. equipment calibration, tracking, and logging) may require coordination with other groups (build reference, e.g. NEMA Security and Privacy Working Group, IHE Operations Domain). Need to pay attention to global vs. local requirements and standards (e.g. NIST relevant to US, but not ROW).Need to pay attention to global vs. local requirements and standards (e.g. NIST relevant to US, but not ROW). Clarify purpose of whitepaper:Clarify purpose of whitepaper: –Define status quo –Established best practices –Existing standards and regulations, including existing profiles –Recommendation of to be developed profiles (where appropriate)

IT Infrastructure Planning Committee THANK YOU