|
|
||||||||
IHE Primer |
1 From the Department of Radiology, Northwestern University Medical Center, 448 E Ontario St, Suite 300, Chicago, IL 60611 (D.S.C.); Department of Diagnostic Imaging, University of Maryland School of Medicine, Baltimore (E.L.S.); Department of Informatics, Radiological Society of North America, Oak Brook, Ill (C.C.); and Department of Professional Services, Healthcare Information and Management Systems Society, Chicago, Ill (J.S.). Received August 24, 2001; accepted August 29. Address correspondence to D.S.C. (e-mail: dsc@radiology.northwestern.edu).
Index Terms: Information management Radiology and radiologists, departmental management
| Introduction |
|---|
|
|
|---|
| Structure of the IHE Initiative |
|---|
|
|
|---|
If you are a member or senior staff member of a professional healthcare-related society, you should be lobbying your society to become a sponsoring society of the IHE. Although there is a small financial burden to becoming a sponsoring society, there is a potential for a tremendous return on investment as the IHE expands to meet the particular needs of your society and its membership. Studying the lessons learned from the radiology examples and experience documented in these primer articles (1), as well as other reports, should help you identify analogous problem areas in your domain that could be addressed by expansion of the IHE initiative.
The IHE Executive Committee directs the Strategic Development Committee. This recently constituted committee consists of clinical and clinical informatics experts from radiology, pathology, nursing, and internal medicine. There are also technical representatives from the Electronic Communications Committee of the RSNA and the IHE Special Interest Group. The latter represents chief information officers of major healthcare institutions. The emeritus chairs of the IHE planning committee are also included. Staff from the RSNA and HIMSS round out the committee. The committee is charged with identifying steps in patient care work flow, recommending priorities of clinical and operational domains for IHE consideration, identifying integration needs and barriers (problems and solutions) within and across domains, and lastly, helping to populate the domain planning committees.
The domain planning committees (of which there is currently one [radiology] with others in formation) are responsible for filtering the problem and solution sets from the Strategic Development Committee down to those sets that can realistically be addressed by IHE. These committees consist of vendors and domain experts (eg, system users, administrators, hospital information system experts), and they direct parallel technical committees to develop the solutions identified.
The technical committees are typically, although not exclusively, made up of vendor experts. These experts are the unsung heroes of the IHE effort. These individuals spend (and their companies generously sponsor) an inordinate amount of time delving into the nitty-gritty detail of the integration to ensure that it works.
Last, and certainly not least, the IHE initiative has a technical project manager, Dr Steven Moore of the Mallinckrodt Institute of Radiology at Washington University in St Louis, Missouri. Dr Moore and his team, working under subcontract from the RSNA and HIMSS, develop the test software used by participants in the IHE connect-a-thon and demonstrations and manage these events. The software for the current year is available to only current participants in the connect-a-thon and demonstration. The small charge to participate is typically trivial in comparison to the value of the knowledge gained by the vendor, the value of participation in the connect-a-thon, and the value to the vendors products in complying with the IHE technical framework. The software used in previous years demonstrations is available at no charge to the general public from the IHE Web site, www.rsna.org/IHE.
| Educational Resources |
|---|
|
|
|---|
In addition to the current RadioGraphics series of primer articles (in the September-October 2001 and November-December 2001 issues), the IHE Web site (www.rsna.org/IHE) has numerous other documents and PowerPoint presentations that can be used as educational materials. This Web site is also home to the latest revision of the IHE technical framework (2), although some might consider the framework to be graduate-level educational material. An IHE presentation is available through the HIMSS Web University at www.himss.org. In addition, an IHE monograph of relevant articles describing IHE functionality, solutions, and future directions will be published by HIMSS in early 2002.
| Year 3 Demonstration: RSNA 2001 and HIMSS 2002 |
|---|
|
|
|---|
The demonstrations will be supplemented with educational workshops targeted to the specific need of clinicians, information technology and radiology administrators, systems implementers, and technical support staff. Of particular interest will be sessions on clinical problems and solutions, with use of IHE to acquire integrated systems, and on user perspectives from clinicians and administrators whose institutions have implemented IHE functionality. A kiosk that features an interactive video highlighting the IHE initiative will also be available.
A full schedule of the demonstrations and educational workshops at the RSNA annual meeting can be found at www.rsna.org/IHE/ihedemo2001/. A similar schedule for the IHE demonstration and related events at the HIMSS annual meeting can be found at www.himss.org.
Professional societies and other organizations interested in incorporating components of the demonstrations, workshops, and other presentations into their societal events should contact representatives of the IHE initiative (see below). A miniature speakers bureau is available, and there are numerous IHE experts available to speak at other meetings.
| How to Specify and Purchase IHE Functionality |
|---|
|
|
|---|
The IHE technical framework is a revision-controlled document that can be incorporated by reference into legal contracts. Although typically a purchase contract requires that equipment or services conform to standards, the contract can also specify compliance with the IHE technical framework. Thus, one can specify conformance to the HL7 and DICOM standards and additionally require compliance with the IHE technical framework.
The role of radiology executives, radiology department administrators, and senior management in advancing the efforts of IHE by specifying IHE compliance (and DICOM and HL7 conformance) in purchase contracts cannot be underestimated. Although altruistic to a point, most healthcare information system vendors are driven by marketing and sales organizations. Vendor engineering groups typically receive significant direction and guidance from these groups. If IHE compliance and adherence to standards is not loudly and clearly communicated as being of great importance to the user community, future IHE engineering efforts may be diluted by perceived need to develop other functionality.
Vendors, on the other hand, will be thrilled to receive uniform, loud and clear feedback from their customers, especially when it leads to significant overall improvement in their products; lowers the complexity (and therefore cost) of their interface development, deployment, and support; and allows them to operate in a larger arena of integrated heterogeneous systems.
An important note to buyers: Beware the notion of purchasing a system that conforms to standards (notably DICOM) and complies with IHE, yet in which these functionalities are not "turned on" or in which "turning on" these functionalities requires an additional cost. IHE, DICOM, and HL7 functionality should be on and running when the system is installed and should be included in the base price of the system.
| Future Directions |
|---|
|
|
|---|
| How to Contact the IHE |
|---|
|
|
|---|
Comments, questions, concerns, and ideas can be sent to the addresses above or electronically to IHE@rsna.org.
| Call to Action |
|---|
|
|
|---|
Chairmen should be studying the work flow in their departments and identifying new ways that IHE can assist them in improving these work flows by better integration of information. They should identify clinicians in their departments with technical backgrounds or interests and encourage and support them in participating in IHE committees. They should encourage students and residents in their departments to recognize healthcare informatics as a legitimate area of research so as to foster the next generation of clinicians capable of further advancing medical informatics technology. Together with department administrators and senior institution management including chief information officers, they should require standards conformance and IHE compliance in all relevant purchases.
Similarly, department administrators should constantly look for work-flow problems in their departments that IHE efforts could possibly remedy. These suggestions should be forwarded to the IHE committees. As stated, administrators should demand IHE compliance and standards conformance in all purchases. When purchasing new equipment, they should consider not only the chemistry or physics and functionality of the device but make a special effort to consider its informatics and how it fits into the work flow of and communicates with other systems in the department or institution.
In the trenches, technologists, radiologists, and clinicians should be documenting information and work-flow problems they encounter in daily practice. These problems should be forwarded to the IHE committees. These individuals should not be intimidated by a lack of technical expertise (remember, you dont need to know how to forge iron to use a hammer): The IHE initiative needs to identify clinically relevant problems to solve, and you can help. You should become active in your professional societies, and if they are not participants in the IHE initiative, lobby them to join. You can also participate directly in the IHE committees. It is extremely interesting, educational, rewarding, and even fun to participate in these efforts. It is especially rewarding to see the rapid incorporation of IHE efforts into real-world products and the immediate benefit of IHE technology in the clinical workplace.
Chief information officers and others in senior management should lobby their professional societies to join the IHE initiative. They should insist that all their information system vendors participate in the IHE effort, not just those involved in departmental or specialty systems. There can no longer be islands of information in a healthcare enterprise. All information systems must work synergistically to get the job of delivering optimal healthcare done.
Any vendor of a device that contains a computer of any sort should become involved in standards bodies related to their domain. In addition, they should participate in the IHE initiative and encourage the inclusion of the appropriate standards from their domain in the IHE toolbox.
There is a role for everyone in integrating the healthcare enterprise. Got IHE?
| Footnotes |
|---|
| References |
|---|
|
|
|---|
This article has been cited by other articles:
![]() |
N. Hara, M. Onoguchi, T. Nishida, M. Honda, O. Houjou, M. Yuhi, T. Takayama, and J. Ueda Considerations for Setting Up an Order Entry System for Nuclear Medicine Tests J. Nucl. Med. Technol., December 1, 2007; 35(4): 259 - 271. [Abstract] [Full Text] [PDF] |
||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| HOME | HELP | FEEDBACK | SUBSCRIPTIONS | ARCHIVE | SEARCH | TABLE OF CONTENTS |
| RADIOGRAPHICS | RADIOLOGY | RSNA JOURNALS ONLINE |