Building a Distributed E-Healthcare System Using SOA

1. Firat Kart, Louise E. Moser, and P. Michael Melliar-Smith University of California, Santa Barbara Building a DistributedE-Healthcare System Using SOA Report：Ting-Huan Kuo Date: 2009/05/18 P u b l i s h e d by t h e I E E E Comp u t e r S o c i e t y

2. Outline • Introduction • The Quality of Healthcare in the US • The Development of Healthcare Standard • SOA • Distributed E-healthcare System • Conclusion

3. Introduction This article describes a distributed e-healthcare system that uses the service-oriented architecture as a means of designing, implementing,and managing healthcare services

4. The Quality of Healthcare in the US • A Washington Post article indicates that as much as 5 percent of the three billionprescriptions filled each year are incorrect. • US National Association of Boards of Pharmacy reports that as many as 7,000 deaths occur in the US each year because of incorrect prescriptions.

5. The Development of Healthcare Standards • HL7 • DICOM • National Council for Prescription Drug Programs, • Current Procedural Terminology, • International Classification of Diseases, • Logical Observation Identifiers, Names, and Codes, • National Drug Codes, and Systematized Nomenclature of Medicine.

6. SOA (Service-oriented Architecture) • SOA, along with Web services and Atom and RSS feeds, provides the opportunity for diverse systems to interoperate without requiring the use of a particular kind of computer system. • SOA use open standards, such as XML and SOAP .

7. SOA Architecture

8. Distributed E-healthcare System • This system uses SOA. • The clinic,pharmacy, and patient modules provide the actual services for the distributed e-healthcare system. • we designed the prototype with security and privacy. • This system only privileged users can view or modify the data.

9. Clinic Module

10. Physician’s handheld displaying Physician input the prescription Medication list graphical

11. Pharmacy module

12. the pharmacy module forthe pharmacist Prescription to deal with

13. Patient interfaces • The Web server interface to the clinic module lets a patient request an appointment with a physician for a specific date and time using the clinic Web server.

14. the pharmacy module forthe patient Record

15. patient’s desktop interface

16. patient’s blood pressure history

17. Underlying Information Technology • prototype in Java and use of its ability to be deployed on small wireless devices as well as on powerful servers. • System uses Plain Old Java Objects (POJO) based on Framework • Web services • Speech Software • Atom and RSS

18. Prescription grammar,

19. use on a physician’s handheld device

20. Conclusion • A distributed e-healthcare system can solve that exists only within the physician’s office. • The e-healthcare system described here can be readily extended to other healthcare professionals. • This system can be interfaced to drug-delivery devices that prompt and monitor the regular and timely consumption of medications.