Overcoming IHE Implementation Hurdles. Paul Nagy, PhD Director, Quality and Informatics Research Department of Radiology University of Maryland School of Medicine. Outline. What other industries call IHE IOM and the redesign of healthcare Obstacles when implementing IHE
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Paul Nagy, PhD
Director, Quality and Informatics Research
Department of Radiology
University of Maryland School of Medicine
Align to the patient
Source: Institute of Medicine, Crossing the Chasm
Berwick D. Escape Fire. Jossey-Bass, San Francisco 2004
A. Gauvin, SCAR 2004, To be published (University of Montreal)
Write in: IHE Integration
“People don’t plan to fail,
they fail to plan”
IHE is a marriage between business objectives and technical architectural policies.
Making all the domains of healthcare transparent to the patient and the bedside.
Standards (DICOM, HL7, IHE, SNIA…) 25- 50 years
Infrastructure (IP, SAN,…) 10- 20 years
Programming Languages (PL/1, Pascal, C, C++, Java, …) 5-10 years
Software (data formats, compatibility, …)2-5 years
Hardware (Network cards, video cards, processors, …) 1-2 years