臺灣博碩士論文加值系統

隨著醫院成長，資訊系統林立，包括自行開發、委外、以及套裝軟體等系統，然而在系統建置之初因急忙上線或沒有整合概念，導致許多系統不互相連形成大量的資訊孤島。使用者要完成一項工作任務，必須花費許多時間去操作多個系統上，有時常常因為忙碌不小心造成錯誤，嚴重的話可能會危及病人的生命安全。因此，系統整合成為醫院資訊化的重要議題。
由於醫院引進資訊系統的方式多樣化，造成系統架構非常的複雜，在整合上極為困難，且維護成本也很高。為了解決系統整合的痛楚，與提供一個更具彈性的系統架構，因此孕育出Service-Oriented Architecture(SOA)，它是一個鬆散耦合的元件模型，將原有的系統架構中的功能模組，改以服務的方式提供對外服務介面，在服務之間定義良好的介面而連接起來，讓不同的硬體平台、作業系統和程式語言都可以採用一種統一和通用的方式進行溝通與整合。
有鑑於此，本研究採用SOA為基礎來重新塑造醫院資訊系統，並以循序漸進的方式導入，以降低整合過程中所產生的風險。首先，透過舊有系統處理之決策矩陣理論來分析出屬於強化(Enhance)與改造(Reengineering)特性的系統；接著，藉由，本研究所提Adapter Service 重新塑造成鬆散耦合的服務介面；最後，再透過SOA架構中的Enterprise Service Bus與其他系統相互溝通整合。
最後，本研究也以SOA為基礎，分別實作健保IC卡服務與RFID應用整合兩個案例來實際做說明。經實例驗證，透過Adapter Service以統一標準的服務介面，大量減少不同介面連接數，進而提高系統的敏捷度及降低系統整合成本。另外，以服務導向方式，顛覆傳統應用導向的思維，強調的服務是以業務為主軸提供各項服務元件，以拉近資訊系統與業務之間的距離，不但可以滿足現在的業務需求，並且可以適應未來瞬息萬變的業務需求。

As the scale of hospitals has been expanded, information systems including self-developed system, outsourcing system, and packaged software, need to be purchased or developed. However, there are numbers of isolated information islands, which generally stay resident in the facility and are not available timely on the enterprise network due to the lack of integration in early system establishment. For medical staff, it is time-consuming to accomplish a task by operating multiple systems, which might lead to mishaps and distraction, thereby endangering patients’ lives and safety. Therefore, system integration has become a critical issue on hospital computerization.
The fact exists that diversified methods have been applied to construct HISs. It undoubtedly results in highly complicated structures, considerable difficulty in system integration, as well as huge maintenance costs. In order to provide a more flexible system framework, this study introduces a Service-Oriented Architecture (SOA). It is a loosely-coupled component model, which transforms the functional modules of legacy systems to service-oriented interfaces with ability to provide services externally. The interfaces are very well defined so that as they are linked together, they make possible for different platforms, operating systems and programming languages to intercommunicate and integrate in a coherent and universal way. This study is based on applying SOA to re-shape the Hospital Information System (HIS), and to adopt it step-by-step in order to reduce risks during the integration process. At first, the legacy HIS is re-evaluated by applying Jacobson and Lindstrom’s decision matrix theory to determine which systems need to be “Enhanced” and “Reengineered.” Then the legacy HIS is reconstructed with Adapter Service presented in the study as loosely coupled service interfaces. Finally, each interface is able to communicate to others through the Enterprise Service Bus (ESB) of the SOA framework.
Consequently, the proposed architecture based on SOA theory provides two case studies including implementations of the NHI IC Card Service and RFID integrated application for real practices. Accordingly, in terms of Adapting Service technology, a hospital can effectively reduce the number of connections among different interfaces, increase the system’s agility, and lower the maintenance cost. A hospital keeps its usual operation as the reengineering processes go on. By adding SOA on existing infrastructure would effectively accelerate delivery of information services to meet the business demands and protect IT investments. It is obvious that benefits of service-oriented architecture can be delivered today and in the future.

Table of Content

CHAPTER 1. Introduction.....................................................1
1.1 Background and Motivations of the Study...............................1
1.2 The Research Objectives...............................................4
CHAPTER 2. Literature Review...............................................10
2.1 Evolution of Hospital Information System.............................10
2.2 Issues Exist in Hospital Information System..........................13
2.3 Upgrade Policy for Legacy Hospital Information System................16
2.4 A Service-Oriented Integrating Architecture..........................19
2.4.1 Service-Oriented Architecture Concepts.............................20
2.4.2 SOA and Web Services...............................................24
2.4.3 Relationship between SOA and ESB...................................26
CHAPTER 3. Migrating to an SOA for Adapter Service.........................30
3.1 Adapter Service Concepts.............................................30
3.2 Adapter Service Architecture.........................................31
3.3 Adapter Service Processes............................................35
CHAPTER 4. An SOA Case Study—Taking the NHI IC Card as an Example.........42
4.1 Methods to Access Information in the NHI IC Card.....................43
4.2 Problems Exist on Accessing the NHI IC Card..........................45
4.3 Access to the NHI IC Card based on SOA...............................47
4.4 System Evaluation....................................................54
CHAPTER 5. An SOA Case Study—The RFID Application System Integration......58
5.1 Introduction to RFID Application System..............................58
5.2 Evolution Trends for RFID Middleware.................................61
5.3 The RFID Middleware Based on SOA.....................................64
5.4 System Examples－Wisely Aware RFID Dosage (WARD).....................68
5.5 System Evaluation....................................................73
CHAPTER 6. Conclusion and Future Work......................................76
6.1 Conclusion...........................................................76
6.2 Future Work..........................................................79
References.................................................................80


List of Figures

Figure 1-1 Peer-to-Peer Data Exchange.......................................2
Figure 1-2 Middleware-based Data Exchange...................................3
Figure 2-1 Information System Computing Model..............................11
Figure 2-2 Decision Matrixes for Legacy Systems............................17
Figure 2-3 Interactions of Services in SOA.................................21
Figure 2-4 Integration Model...............................................27
Figure 2-5 Interacting Processes among Requester, Provider and ESB.........28
Figure 3-1 System Integration among legacy systems and SOA-based systems...31
Figure 3-2 Adapter Service Logic Architecture..............................32
Figure 3-3 SOAP Message Architecture.......................................33
Figure 3-4 The Handling of Lost Packages for Service Layer.................34
Figure 3-5 Adapter Service Architecture Pattern............................36
Figure 3-6 Procedure for Adapter Service...................................37
Figure 3-7 SOAP Message for Service Request................................39
Figure 3-8 SOAP Message for Result of Service Request......................40
Figure 4-1 Architecture for Standalone Card Reader.........................43
Figure 4-2 Architecture for PC Online Card Reader..........................43
Figure 4-3 System Architecture for PC Online Card Reader...................44
Figure 4-4 Web-based HIS is Incapable to Bind to the CS API................46
Figure 4-5 SOA System Architecture for Access to the NHI IC Card...........48
Figure 4-6 Detailed Framework for Card Reader Service Requester............49
Figure 4-7 A Service Request for Card Reading As an SOAP Message...........50
Figure 4-8 An Executed Result for Card Reading As an SOAP Message..........51
Figure 4-9 Detailed Framework for Card Reader Service Provider.............52
Figure 4-10 A Comparison of NHI IC Card Reading Efficiency.................56
Figure 5-1 The Framework of RFID Application System........................59
Figure 5-2 One-to-one RFID Middleware......................................62
Figure 5-3 One-to-many RFID Middleware.....................................63
Figure 5-4 Many-to-many RFID Middleware....................................64
Figure 5-5 RFID Reader Service Architecture................................65
Figure 5-6 RFID Service Provider...........................................66
Figure 5-7 WARD system framework...........................................69
Figure 5-8 A Comparison of RFID Middlewares Reading Efficiency.............74

[1] Geet, J.V., "Reverse Engineering in the World of Enterprise SOA." Antwerp, Belgium : 2008 15th Working Conference on Reverse Engineering, 2008, Pages: 311-314 .
[2] Omar, W. M. and Taleb-Bendiab, A., "E-health Support Services Based on Service-oriented Architecture." IT Professional. 2006, Vol. 8, 2., Pages: 35 – 41.
[3] Simpson, L., "Patient and nurse safety: How information technology makes a difference." Nursing Administration Quarterly . 2005, Vol. 29., Pages: 97-101.
[4] Unruh, K. and Pratt, W., "Patients as actors: the patient''s role in detecting, preventing, and recovering from medical errors." International Journal of Medical Informatics. 2007, Vol. 76., Pages: 235-244.
[5] Sun, P.R., Huang, C.F. and Wu, F., "A Study of Referral Information Management Systems Based on HL7 and XML." The Journal of Taiwan Association for Medical Informatics. 2004, Vol. 13, 2., Pages: 47-61.
[6] Steiert, H.P., "Towards a Component-based n-Tier C/S-Architecture." Orlando, FL USA: In Proceedings of the Third International Workshop on Software Architecture, 1998, Pages: 137 - 140.
[7] Wong, S. H. and Swartz, S. L., "A middleware architecture for open and interoperable GISs." IEEE Multimedia. 2002, Vol. 9, 2., Pages: 62 - 76.
[8] Pasley, J., "Avoid XML Schema Wildcards For Web Service Interfaces." IEEE Internet Computing. 2006, Vol. 10, 3. , Pages: 72-79.
[9] Arsanjani, A., How to Identify, Specify and Realize Services for your SOA(Part I). New York, USA: IBM, 2005.
[10] Erl, T., Service-Oriented Architecture: A Field Guide to Integrating Xml and Web Services. New Jersey, USA: Prentice Hall, 2004.
[11] Holland, P., "Building Web Services From Existing Application." eAI Journal. 2002.
[12] Katehakis, D.G., Sfakianakis, S.G., Kavlentakis, G., Anthoulakis, D.N. and Tsiknakis, M., "Delivering a Lifelong Integrated Electronic Health Record Based on a Service Oriented Architecture." IEEE Transactions on Information Technology in Biomedicine. 2007, Vol. 11, 6., Pages: 639-650.
[13] Jacobson, I. and Lindstrom, F., "Reengineering of Old systems to an Object-oriented Architecture." ACM. 1991, Vol. 26, 11., Pages: 340 - 350.
[14] Hwang, H.G., Chang, I.C. and Liu, C.F., "Current states of development of electronic medical record in health care." 2005 Annual Report, Department of Health (Taiwan). 2005.
[15] Haux, R., "Health information systems－past, present, future." International Journal of Medical Informatics. 2006, Vol. 75., Pages: 268-281.
[16] Hwang, H.G., "Research issues in Healthcare Information Systems." Journal of Information Management. 2002, Vol. 9, S., Pages: 101-116.
[17] Chu, S. and Cesnik, B., "A three-tier Clinical Information Systems design model." International Journal of Medical Informatics. 2000, Vol. 57, 2., Pages: 91–107.
[18] Petrou, C., Hadjiefthymiades, S. and Martakos, D., "An XML-base, 3-tier Scheme for Interacting Heterogeneous Information Sources to the WWW." Florence, Italy : 10th International Workshop on Database & Expert Systems Applications, 1999., Pages: 706.
[19] Omar, W. M. and Taleb-Bendiab, A., "Service oriented architecture for e-health support services based on grid computing." Chicago: Proceedings of the IEEE International Conference on Services Oriented Computing, 2006.,Page: 135 – 142.
[20] Sneed, H. M., "Integrating Legacy Software into a Service Oriented Architecture." Software Maintenance and Reengineering. 2006., Pages: 22-24.
[21] Seals, M., "The Use of XML in Healthcare Information Management." Journal of the Health Information and Management System Society. 2000, Vol. 14, 2., Pages: 85-95.
[22] Banker, R. D. and Kauffman, R. J., "Reuse and productivity in integrated computer-aided software engineering: an empirical study." MIS Quarterly. 1991, Vol. 15, 3., Pages: 375 - 401.
[23] Bisbal, J., Lawless, D., Bing Wu, Grimson, J., Trinity Coll. and Dublin, "Legacy information systems: issues and directions." Software, IEEE. 1999, Vol. 16, 5., Pages: 103-111.
[24] Tsai, W. T., "Service-Oriented System Engineering: A New Paradigm." Washington, DC, USA : IEEE International Workshop on Service-Oriented System Engineering (SOSE), 2005., Pages: 3- 6.
[25] Basili, V. R. and Freburger, K., "Programming Measurement and Estimation in the Software Engineering Laboratory." The Journal of Systems and Software. 1981, Vol. 2, 1., Pages:47-57.
[26] Frakes, W. and Terry, C., "Software reuse: metrics and models." ACM Computing Surveys. 1996, Vol. 28, 2., Pages: 415 - 435.
[27] Erlikh, L., "Integrating Legacy Systems Using Web Services." eAI Journal. 2002.
[28] Chappel, D., Enterprise Service Bus: Theory in Practice. Sebastopol, CA: O''Reilly, 2004.
[29] Bichler, M and Lin, K.J., "Service-Oriented Computing." IEEE Computer. 2006, Vol. 39, 3., Pages: 99-101.
[30] Chen, R., Shen, V., Wrobel,T. and Lin, C., "Applying SOA and Web 2.0 to Telecom: Legacy and IMS Next-Generation Architectures." Xi''an, China: 2008 IEEE International Conference on e-Business Engineering, 2008, Pages: 374-379
[31] Erl, T., Service Oriented Architecture, Concepts, Technology and Design. Ontario, Canada: Prentice Hall Professional Technical Reference, 2005.
[32] Krafzig, D., Banke, K. and Slama, D., Enterprise SOA: Service-Oriented Architecture Best Practices. New Jersey, USA: Prentice Hall, 2004.
[33] Malloy, B.A., Kraft, N.A., Hallstrom, J.O. and Voas, J.M., "Improving the predictable assembly of Service-Orien ted Architectures." IEEE Software. 2006, Vol. 23, 2., Pages: 12-15.
[34] Huhns, M. N. and Singh, M. P., "Service-oriented computing: Key concepts and principles." IEEE Internet Computing. 2005, Vol. 9, 1. , Pages: 75-81.
[35] Hammer, K., "Web Services and Enterprise integration." eAI Journal. 2001. Pages: 12-14.
[36] Deitel, H. M., Deitel, P. J., DuWaldt, B. and Trees, L.K., Web Services A Technical Introduction. New Jersey, USA: Prentice Hall, 2003.
[37] Liu, S., Service Oriented Architecture Overview. New York, USA: IBM developerWorks, 2005.
[38] Papazoglou, M., "Service-oriented computing: Concepts, characteristics and directions." Rome, Italy : The Fourth International Conference on Web Information Systems Engineering, 2003., Pages: 3- 12.
[39] Bieberstein, N., Bose, S.,Walker, L. and Lynch, A., "Impact of service-oriented architecture on enterprise systems, organizational structures, and individuals." IBM Systems Journal. 2005, Vol. 44, 4.,Pages: 691 – 708.
[40] Cox, D.E. and Kreger, H., "Management of the service-oriented-architecture life cycle." IBM Systems Journal. 2005, Vol. 44, 4., pp: 709 - 726.
[41] Tidwell, D., Snell, J. and Kulchenko, P., Programming Web Services with SOAP. Sebastopol, CA: O''reilly, 2001.
[42] Younas, M., Awan, I. and Duce, D., "An Efficient Composition of Web Services with Active Network Support." Expert Systems with Applications. 2006, Vol. 31, 4.,Pages: 859-869.
[43] Darwish, N., "COPS：cooperative problem solving Using DCOM." Journal of System and Software. 2002, Vol. 63, 2., Pages: 79-90.
[44] Curbera, F., Duftler, M., Khalaf, R., Nagy, W., Mukhi, N. and Weerawarana, S., "Unraveling the Web Service Web. An Introductionto SOAP WSDL and UDDI." IEEE Internet Computing. 2002, Vol. 6., Pages: 86 – 93.
[45] Newcomer, E. and Lomow, G., Understanding SOA with Web Services. Boston, MA: Addison-Wesley, 2004.
[46] Hightower, J. and Borriello, G., "Location systems for ubiquitous computing." IEEE Computer Magazine. 2001, Vol. 34.,Pages: 57-66.
[47] Pasley, J., "How BPEL and SOA are Changing Web Service Development." IEEE Internet Computing. 2005, Vol. 9, 3, Pages: 60-67.
[48] Vogels, W., "Web Services Are Not Distributed Objects." IEEE Internet Computing. 2003, Vol. 7., Pages: 59-66.
[49] Roy, J. and Ramanujan, A., "Understanding Web Service." IEEE IT Professional. 2001, Vol. 3.no. 6., Pages: 69-73.
[50] Kramer, J. R., "Importance of an open system architecture in the semiconductor industry." Technology Review Journal. 2002, Vol. 10, 1., Pages: 123–136.
[51] Lee, Y., "Quality Context Composition for Management of SOA Quality." Hunan, China: 2008 The 9th International Conference for Young Computer Scientists, 2008., Pages: 117 – 122.
[52] Lee, L. L., "Anthology of the Plan for the National Health Insurance IC Card and Promotion for Networking Government and Digital Administration." A Bimonthly Report for Research, Development, and Evaluation Commission. 2001.
[53] Insurance, Bureau of National Health., Control Software API for Windows Reference Manual V1.4. Taiwan, Taipei : Bureau of National Health Insurance, 2002.
[54] Insurance, Bureau of National Health., Control Software for Linux & Solaris Instructions V1.0. Taiwan, Taipei: Bureau of National Health Insurance, 2002.
[55] Insurance, Bureau of National Health., A Project of Implementation of the National Health Insurance IC Card for Citizen of R.O.C - PC Online Card Reader Specifications, V2.1. Taipei, Taiwan: Bureau of National Health Insurance, 2001.
[56] Sun, P.R., Huang, C.F. and Wu, F., "Mechanism to Access the National Health Insurance IC Card for Web-Based Health Information Systems." Journal of Information Management. 2006, Vol. 13, 2., Pages: 145–170.
[57] Ministry of Interior Affairs, Executive Yuan., Digital Citizen Certificate IC Card Issued by the Interior Ministry Certificate Authority-Customer Service Common Questions and Answers. Taiwan, Taipei: Ministry of Interior Affairs, Executive Yuan, 2003.
[58] Johnson, D., "RFID tags improve tracking, quality on Ford line in Mexico." Control Engineering. Vol. 49, 11.Pages: 16.
[59] Costlow, T., "RFID Extends to Medical Applications." Design News. Vol. 59, 9., Pages: 43–44.
[60] Perrin, R. A. and Simpson, N., "RFID and bar codes: Critical importance in enhancing safe patient care." Journal of healthcare information management. 2004, Vol. 18., Pages: 433-439.
[61] Bonnabry, P., "Information technologies for the prevention of medication errors." Chimia. 2005, Vol. 59, 6.,Pages: 359–361.
[62] Cline, J., "The RFID Privacy Scare Is Overblown." Computer world. 2004, Vol. 38, 11., Pages: 44.
[63] Glidden, R., "Design of Ultra-Low-Cost UHF RFID Tags for Supply Chain Applications." 2004, Issue 8, Vol. 42., Pages: 140 – 151.
[64] Shimizu, M., Hayashi, H. and Umehira, M., "Ubiquitous applications using RFID tags." Ntt Review. 2002, Vol. 14, 5., Pages: 22-26.
[65] Kohn, C. and Henderson, C.W., "RFID-enabled medical equipment management programs to reduce costs." Managed Care Weekly Digest. 2004., Pages: 94–95.
[66] Kim, T. and Kim, H., "Authorization Policy for Middleware in RFID System." Proceedings of the IEEE Tenth International Symposium on Consumer Electronics. 2006., Pages: 1-4.
[67] Hong, J.E. and Thompson, C.W., "Architecting RFID Middleware." Journal of the IEEE Internet Computing. 2006, Vol. 10, 5.,Pages: 88 – 92.
[68] Huzaifa, N. and Jitender, D., "Radio frequency identification applications in smart hospitals." Twentieth IEEE International. 2007.,Pages: 337-342.
[69] Sun, P.R., Wu, F. and Wang, B.H., "A New Method to Guard Inpatient Medication Safety by the Implementation of RFID." Journal of Medical Systems. 2008, Vol. 32., Pages: 327-332.
[70] Roark, D.C. and Miguel, K., "RFID: Bar coding''s replacement?" Nursing Management. 2006, Vol. 37, 2., Pages: 28-31.