An Application Research on the Workflow-based Large-scale Hospital Information System Integration

106 JOURNAL OF COMPUTERS, VOL. 6, NO. 1, JANUARY 2011 An Application Research on the Workflow-based Large-scale Hospital Inforation Syste Integration Yang Guojun School of Coputer, Neijiang Noral University, Neijiang, China; Ygj_8383@163.co Zheng Ying and Wang Gang Departent of Inforation Engineering, Neijiang Vocational & Technical College, Neijiang, China Inforation Center, The First Neijiang People's Hospital, Neijiang, China Zying_0005@163.co,404510815@qq.co Abstract At present large-scale hospital inforation syste has ore than nodes, independent, extended strong and inforative and so on, and it is difficult for the syste to achieve a unified integration issues. In view of this, the article proposed a large-scale hospital inforation syste integration solutions, which use the workflow-based echanis for MIS developent tools as the integration platfor, custoize and control the ain line flow to achieve strong connection to the node and work independently as a loosely coupled business systes interface. Index Ters Workflow; Hospital Inforation Syste; Integration Platfor; Process control; Integrated progra I. INTRODUCTION The construction and developent of the hospital inforation syste is an iportant indicator of the developent of large hospitals under the inforation age. With the expanding of hospital scale, increasing of the business, and the gradually increasing of the expert syste and the increasing of the flow of inforation,it s the ost urgent proble for all sorts systes of hospitals to ipleent syste integration. On the other hand, the traditional point to point, essage-based integration, coponent-based integration or iddleware-based integration schee see powerless to the current hospital inforation systes which exist ultiple heterogeneous systes, data structure, essage forat, counication protocol inconsistencies and other issues. So, we need a solutions Considering all aspects and Using a variety of integrated approach cobination. To solve the above issue, the author use the idea of workflow technology as the ain line to play process custoization and process control advantages, proposed a new echanis based on workflow developent tools Foundation Ite: Youth Fund of Neijiang Noral University(07NJZ- 09) for MIS integration platfor to eet the hospital internal syste process control, data exchange and sealess sharing, which can achieve the effective control of the hospital syste processes, and achieve sealess integration of hospital inforation syste. II. BACKGROUND SYSTEM This article bases on the Research projects in " the research and developent of a new type of MIS developent tools based on workflow echanis " and takes the First Neijiang People's Hospital Inforation Syste as the research background.the hospital proposes to establish a unified integration platfor.and with the process of custoization and process control for the line, the existing software syste of the hospital can be fully integrated. It s coplicated to realize this large syste whose goal is integration, digitization, patientcentered, with the openness, scalability and aintainability, and which can realize the process custoization and control of hospital business. The reasons as follow: First,large-scale ulti-hospital syste has any subsystes, such as HIS (Hospital Inforation Syste), LIS (Laboratory Inforation Syste), RIS (Radiation Inforation Syste), PACS (Picture Archiving and Counication Syste) and so on; Second, the general hospital has a nuber of legacy applications and general edical equipent has its own unique software systes, but these systes do not have source code except soe interface available to the Third, a variety of data forats is involved in hospital, for exaple,coon data, graphics and iages and so on. Fourth, with the realization of electronic edical records. A good inforation exchange can be achieved aong Hospitals (for exaple, when the patient transfers). We ust abide the international standards and nors about the existing edical syste, such as the doi:10.4304/jcp.6.1.106-113

JOURNAL OF COMPUTERS, VOL. 6, NO. 1, JANUARY 2011 107 HL7 standard, DICOM standards, IHE nors. Although the various criteria of the interaction between various systes need to pass the essage forat, they do not include the realization technology. So integrating the various business systes is technically difficult. Fifth, the hospital s business processes is coplex and changing. Many of the existing systes are eliinated because they can t adapt to the changing of the hospitals business processes. Although the Existing large-scale hospital software systes achieve the integration of various subsystes, ost just put together a siple subsystes and The connections between the are achieved only by using peer-to-peer ode (Message-Oriented Middleware, or direct access database, etc.). So not only the developent and aintenance are very difficult, but also the degree integration are not high and the support of the hospital s business processes are inadequate. There are any inconveniences to Doctors of inforation sharing and anageent of hospital anageent.and the hospital s needing of new business processes usually lead to largescale changing to source code and ake the aintenance price high. In addition, they support only part of the international standard. This paper presents a workflow-based echanis as the new developent tool of MIS integration platfor for large hospital syste integration progra, which is not only easy to achieve integration in the developent and aintenance, easy to support the international standards, but also allows hospitals to coply with the Business Process IHE nors. Besides, the doctor can get ore coprehensive inforation of patients.and the ipleentation of doctor's advice will be even ore autoation and sooth. Therefore, this progra is not only for the convenience of doctors, but also is conducive to the patient. And it realizes the unity of the process design and anageent, even when the process changes, as long as the anagers siply re-design the workflow and do a sall nuber of changes in the application will be ok.so it has a lot of help for anagers. Therefore, the integration which based on workflow echanis as the developent tool of MIS is a feasible option to optiize. A. Hospital Syste III. SYSTEM ANALYSIS AND DESIGN Large-scale hospital inforation syste as a whole syste of vast, has coplex structure, and has strong independence of the syste, and ainly has the following categories: Hospital Inforation Syste (HIS) is to achieve the hospital's core business syste, which includes the registered subsystes, doctors workstations, reproductive center anageent syste, health-check anageent syste, blood transfusion anageent syste, surgery, anesthesia anageent systes, subclinical experts syste, drug anageent syste, econoic anageent syste, integrated anageent and statistical analysis systes and data security anageent systes Laboratory and central laboratory inforation syste (LIS) is ainly responsible for dealing with the inspection of report and the anageent of the laboratory inforation business. Picture archiving and counication syste (PACS) is ainly responsible for iage acquisition, transission, storage, processing, display and print anageent. In addition, the current Full PACS systes typically including a radiology inforation syste (Radiation Inforation Syste, RIS), is responsible for a variety of radiation treatent equipent inspection reports, as well as the association with PACS systes for iages access and in accordance with HL7 standards and the external syste ( For exaple, HIS) to interact. Office Autoation Syste (OAS) is ainly responsible for a nuber of routine office functions. External syste ainly refers to the banking syste, edical insurance syste, drug supply systes. Because a large hospital syste can not be a closed syste, its interaction with the outside world is inevitable, but also is the future developent trend. B Design Principles The contents of a large hospital syste involves in any deanding syste integration. In the design of the syste would have to consider the feasibility, flexibility, robustness and scalability, and aintenance which are the basic design principles of the syste integration. Feasibility.Because the syste is a real syste used in large 3 B hospital, the feasibility of the technical and tie becoes a proble that needs to be considered first. Business processes of large hospital syste are not only coplex and changeable, so flexibility is a question need to focus on the design of the syste. Whether the hospital can adapt to the coplex processes of existing and future process changes, and whether the procedure can be changed as little as possible when deand changes is a anifestation of syste flexibility. Robustness. To the hospitals using this syste of, their average daily outpatient aount is nearly 2,500, and their average annual outpatient aount is approxiately 65 illion. So, whether the syste is able to withstand the high load, high flow, that is, the syste robustness is also the proble of the design of the syste needing to focus on. Maintainability.The aintenance cost of the Syste take up a large part of the whole cost of the syste. So, the aintainability of the syste is also crucial. Scalability. After referring to syste integration, a with the hospital syste continue to increase and expand, the business continues to expand and the external syste becoes ore and ore standardized, the syste provides an extension interface. C. Technical Difficulties The realization of a large hospital syste integration need to consider and resolve any technical difficulties that were described in the following.: Multi-subsyste.Because of the any subsystes included in the hospital syste, the independence aong the subsystes,and the interaction between subsystes

108 JOURNAL OF COMPUTERS, VOL. 6, NO. 1, JANUARY 2011 ore, if using the traditional ethods to achieve pointto-point interconnection, it will for a network structure,.but that will ake the syste alost not scalable. Because,if the syste adds a subsyste,other subsystes and its all connected will need to be added, so that was the poor aintenance caused by. Data forat conversion. The realization of this syste is not only the realization of the connection of its own subsyste siply by sharing the database with the Internet, but also bring other hospital syste suppliers products (such as: PACS) integrated into the hospital syste. But directly accessing the database of other vendors products is unsafe and not feasible. Because relating to a specific data structure ay have a product of a dependent, and runs counter to the interaction standard defined by the edical profession between the syste. In short, in order to reach the Internet, we need to address different suppliers in different systes of the unification of data forats. Changing business processes.the business processes of hospital are coplex and changing. For exaple, to fill the orders of doctors belonging to the original task, but it ay be fill out the task to the nurses because the change of process. For another exaple, the year-end assessent of the indicators of edical personnel, ay be different as tie changing,ay also add new content. To adapt to changes in the process is all along the ost intractable probles in the syste been running. IV.DESIGN OF THE WORKFLOW-BASED NEW MIS DEVELOPMENT TOOL As enterprises of inforation technology, any local enterprises establish an MIS syste to iprove efficiency and reduce costs. However, the existing MIS developent tools for sector-specific functions adopt object-oriented developent odel, and it does not support the custoization and control of MIS in the process of ipleentation. Most of the MIS syste is only a siple integration of features that enterprises need,and business process has been solidified in the syste, any sall changes ay force the syste to odify or re-developed, resulting in a lot of syste aintenance overhead. At the sae tie, enterprises in order to iprove arket copetitiveness, ust constantly odify their business processes to adapt to arket changes. Clearly, for the MIS syste to better serve the enterprise, fro enterprise reality, it is necessary to give full advantage of existing features (ERP systes), and also achieve process custoization and control. According to the above probles, this paper presents a new type of MIS developent tools based on workflow echanis to eet the flexibility to custoize and control the process, supporting features of the platfor. It has far-reaching significance to integration of heterogeneously inforation systes of enterprise or hospital. A. workflow teconology Workflow: (Workflow Manageent Coalition Workflow Manageent Coalition, SFMC defined) work flow is a business processes which is defined,ipleented and onitored by coputer software, that is a workflow syste, which is different fro the general working process, and need to rely on coputer software, and fully under the control of the software syste to coplete. Workflow syste: A coplete workflow syste includes workflow anageent systes, process odels and applications. Workflow anageent syste is a workflow syste infrastructure, which is responsible for storage, interpretation and ipleentation of process odels; process odel establish service through the flow custoization tool to describe and definite the control and data dependence aong a variety of business processes; applications are specific operational processing activities, and the ipleentation of an application corresponds to a task, and a nuber of interrelated tasks for a process. Workflow anageent syste based on process odel to create and start the process, and choose process routing according to the ipleentation of the task in process; application are tightly integrated with workflow syste, and execute the schedule according to the results of the ipleentation of the routing process, after ipleentation copleted, it will return results to the ipleentation workflow anageent syste as basis for its process route. B. WFS fraework According to its features WF-MIS ake workflow echanis ebed MIS found process to set up a structure platfor for the en who develop the software, thus they concentrate to developing transactional logical and active MIS of process control. The generated MIS support rebuilding-up of enterprise transactional and support recopsiting construction and software s reusing in Distributed heterogeneous environent, and it supports syste scale s expanding. In a word, it is a RRS(Reconfigurable Reusable Scalable)syste[1], which optiizes enterprise transactional process especially key process and strengthens enterprise works cooperation and counication. The syste adopts botto fraework of CORBA counication echanis syste and is shown as Figure 1. [2]

JOURNAL OF COMPUTERS, VOL. 6, NO. 1, JANUARY 2011 109 Workflow Client Workflow Server BAL Workflow database Application client Application Service docuents Application database Figure 1. WFS fraework structure According to above analysis, we can know that if MIS function coponents are encapsulated and integrated with workflow anageent syste, the syste can not only accoplish enterprise s MIS function but custoize and control process flexibly. The workflow syste is a Work flow Mana gee nt Syste Workflow-based for the developent of new tools for MIS The defini tion of proce ss Workflow syste Syste Moni tor Work Work Work Node Node Node 1 2 N kind of MIS which supports process custoization Data and control and supports current function coponent platfor. base And it can sooth over the shortage of current MIS. Custo-process Coon features coponents Menu Gene rator State ent Gene rator Figure 2. WFS Functional Architecture For Figur proce e 3. ssor Wor kflo w Syste Arch itect ure Syste Monitor acces s cop onent s Therefore, we consider using workflow technology to support the ipleentation of flow custoization and flow control, which contents soe parts: workflow which is the core part and used to explain and control process executing; flow custoization tool which is used to build the odel to aintain process and syste onitor tool which is used to the running of workflow syste; work point which integrate workflow syste with application soothly via supplied interface. And function coponent can use current developent tools. For accelerating the developent of MIS function coponents, WF-MIS gives soe coon function coponents which can be used after siply custoized. [3] C. WFS syste structure WF-MIS which is coposed of coonly function coponents and workflow syste is described as Figure 2. The forer assist to developing MIS function coponents ; the latter is used to build process odel and control process being correctly carrying out and call transactional process application and accoplish integrating application with workflow syste soothly. [4] 1. Workflow syste Workflow is coposed of custoization tool, syste onitor, workflow anageent and several work points. Process custoization tool is responsible of custoizing process odel and offer it for workflow anageent syste. Syste onitor reads workflow syste running data and show syste running situation. Workflow anageent syste starts process according to process odel and controls it running correctly to build the MIS fit to transactional process. Work point is the carrier of transaction process application, which accept task and carry out related transactional process application. The architecture of can be shown as Figure 3. [4] [5] Business processing applications Workflow Model Base User Manager Application Interface Model interpreter XML processor Task scheduler Workflow Manageent Syste Rules Interpreter Workflow run database Workflow interface counication Node configuration files Task processor Workflow interface counication Task list XML processor Workflow interface Workflow Control Server Data Access Working node Call and Trigger Figure 3. Workflow Syste Architecture Database access coponents

110 JOURNAL OF COMPUTERS, VOL. 6, NO. 1, JANUARY 2011 Process custoization tool: It runs in workflow server as independent application, which is used to build aintain process and write process data to workflow odel base. A group of basic eleents such as work point, incident, condition, connection are supplied, in order to give the rout describing process. In addition, it perits several child processes ebedded in process to support process reused. Syste onitor: It runs in workflow control severer, which analyzes and calculates workflow running data and onitor process running situation in syste and shows it with digraph to adinister. Workflow anageent syste: It runs in workflow control severer which is coposed of workflow counication interface, task anageent, XML processor, odel explainer and procedure explainer. Workflow counication interface accept the XML docuent which is result fro work point, and hand it to task anager. Task anager call XML processor to process application running result, XML docuent, and hand the result to odel explainer to process. According to the result of application running and process odel, odel explainer found appropriate procedure and calculate it to decide the next work point. work point: It is the carrier of transactional process application, which carry out correctly according to workflow anageent syste calling,setting up work interface in it to ipleent integrating application with workflow. Workflow interface is coposed of workflow counication interface, task anageent, XML process, odel explanation, rule explanation. Workflow counication accepts task data, XML docuent, and hand It to task process to deal with. Task process call XML process to process task data, XML docuent, to get task data and integrate it with relevant data in point disposition docuent to ake a whole task calling data, and store it to task table. XML process explains the task data that is got by XML docuent. User interface calls application according to point user s choice and corresponding task data, and sends the executive result to workflow anageent syste through task process and counication interface. 3. Coon function coponents Coon function coponents are relevant with MIS application closely, assisting to the developent of MIS function coponent. WF-MIS gives four coponents. Menu aker: It supplies convenient visual enu ake tools. The developer can draw needed enu and set relevant attribute to adjust the display style of enu. After drawing enu, the tool generates the corresponding progra code (including VB, Delphi, Java, PowerBuilder), and it can be added to progra. Table aker: It is the ultiate for, which supply with data to anager, and it needs strict data show. The function coponent give a table aker in the for of JavaBean, which can ake sure the data source, assign the table layout, and get initial table which is odified to satisfy needs. The ultiate table is outputted in the for of PDF, HTML, and Excel. Data table processor: It is the coon for of transactional data, which operator use to get data. It has three functions: auto generating data table, controlling authority, and controlling process. Fist, we can assign the source of table data and it relevant attributes to generate data table. Second, it decides who can see relevant table and generates relevant table according to the authority to relevant field. And it control tables running in relevant transactional process according to the relation of the transaction in table and other transaction process. [6] Database access coponent: Most MIS access functions are based on the operation of accessing database. The coponent encapsulates coon operation of accessing database to for JavaBean coponent which can be integrated to progra. It can pass not only the signal of database odel, password but also operate database with the ethod it give. 2. Workflow-based WFS developent tools ipleentation WFS is developed with Java, so workflow syste can integrate transactional process application in different platfors. It describes syste data with XML. With the aid of its powerful capacity of describing data, syste data is convenient read and used by other systes, and syste s extension is raised. Workflow syste integrate with transactional process application soothly to ake sure process carried out correctly. The application interface in workflow interface is used to application integration. But owning to the coplex situation of transactional process application, the ipleent of application integration is very coplex. (1).If it is coon executive progra, it can be called. (2).If it is WEB application, it use Repuest object to pass start paraeters to application. (3).If it is coponent progra, it should be integrated as possible. If necessary it can be integrated as WEB serve and ipleent WEB serve client. Developent worker use Jobuilder 9 to develop relevant coponent and ipleent relevant integration [7] V. STUDY OF LARGE-SCALE HOSPITAL INFORMATION SYSTEM INTEGRATION A. Large-scale hospital inforation syste integration syste Hospital inforation syste integration using process custoization and process control as the ain line is a new MIS workflow-based developent tools for the integration platfor. Any other business subsystes are based on this platfor to achieve interconnection and inforation exchange, as well as the application and data integration. The platfor is divided into three layers, naely, business process layer, business layer and business agent syste layer. The ain features of this progra is based on the business process workflow anageent, syste architecture for the platfor through standard adapters, application systes across the counications and XML-based unified data odel 1. Overall syste architecture

JOURNAL OF COMPUTERS, VOL. 6, NO. 1, JANUARY 2011 111 In order to achieve heterogeneous integration of hospital inforation syste,the overall structure of the Registered subsyste J2EEplatfor Re ote docts Workflow API end Adapter Doctor/nu rse workstatio ns XML Web Service activityc start J2EE Copone nt XML XML activityb MIS Tools (Business Process Layer) Hospital Portal Syste Firewall patie nt Othe r hospi tals Workflow Manageent Syste Business agent layer Supp liers activity A XML JMS J2EEplatfor Adapter syste is designed as Figure 4.The business process layer is in the center, and the realization of process anageent is the core of the syste. The business syste layer through the various agents of the business agent layer achieves the business syste interaction to achieve the hospital's business processes. Layer of its business agents using various agents J2CA based on the Adapter, Web Services, Workflow API J2EE Coponent, such as technology or JMS. Our platfor is based on J2EE, in which the business process layer and business proxy layer run on the J2EE Server and share services such as security and Services provided by J2EE Server. 2. Business Process Layer The ain function of the Business process layer is the design of business processes,to explain the ipleentation of business processes, and the use of XML forat data to achieve all of the inforation transission subsyste, thereby to accoplish the hospital's business. In addition, it has to process onitoring and statistical functions for the hospital anageent to provide process data to help the find the bottleneck of the syste in order to optiize the process. Business process layer by the workflow anageent syste to achieve, that is a software syste used to define, achieve and anage the workflow and interact with the workflow actors (people, applications) to proote the ipleentation of workflow instances and onitor the work of running strea. A workflow, including a set of activities and the order of their utual LIS... Financial syste... Figure 4. Syste architecture diagra RIS OAS relations and activities also include the process of start-up and terination conditions, as well as a description of each activity. For coonly used business processes, can use in the future in "teplate" for of preservation. The introduction of workflow anageent syste akes the syste can be configured to provide a flexible link, process custoization and scheduling algorith to choose the functions and carry out in accordance with the configuration of various business processes custoized requests and scheduling. It can achieve the various business processes of a unified planning and processing, fro the point of entire syste view. On the one hand, a variety of requests to ensure that all aspects of the syste's sooth handling, on the other hand, to ensure that these operations can be the best allocation process. Operational requests ay be ade fro the patient for treatent, but also can coe fro doctors, nurses and anagers. The syste of workflow anageent syste is running on the J2EE platfor as part of the J2EE Server. The developent of workflow anageent itself is not a hospital syste. To a large extent, workflow anageent syste provides a software support environent for the integration and operation of the hospital syste. In the workflow anageent syste, supported by developent tools, it is able to coplete a good run of the supporting and the control of hospital business process through the integration of specific business systes and associated interface operation use of personal. 3. Business agent layer Acting through the following business layer technology to achieve a variety of business systes in each layer with the business process layer interaction, and business processes through the various layers to achieve the interaction between business systes and achieve specific business processes of hospitals. We use the J2EE platfor, so each agent business agent layer are J2EEbased technology, which is based on J2CA the Adapter, JMS, Web Services, Workflow API, or a J2EE Coponent Technology. Based on J2CA the Adapter J2EE Connector Architecture defines a different types of inforation syste (EIS) to connect to the J2EE platfor, the standard architecture. J2CA also defines a series of scalable, secure, transactional echaniss to connect the heterogeneous EIS with the application and systes.j2ca also defines the CCI (Coon Client Interface) to be accessed on the EIS. J2CA allows EIS suppliers to provide a standard resource adapter for their EIS. The resource adapter can be ebedded application server, in order to achieve the EIS application servers and enterprise application connectivity. JMS (Java Message Service) essage-oriented iddleware (MOM) is increasingly becoing the ain coponent of application integration. It is critical for systes to exchange data and events to trigger the provision of a reliable and flexible service. In order to enhance its portability, J2EE platfor gives a JMS (Java Message Service), and JMS enables Java code to create,

112 JOURNAL OF COMPUTERS, VOL. 6, NO. 1, JANUARY 2011 send and receive essages in a coon way, which akes Java code written in JMS adapt to different essage iddleware products. Web Services is a new SOAP-based service delivery odel. The basic eleents of the odel is a SOAP / HTTP, XML, WSDL and UDDI. Web Services use a loose bundle of services for to develop, publish, discovery and achieve dynaic binding application fast and with a low cost, but also can achieve the applicationlevel functions or ethods of integration. They are not natural-based services, while providing a basic "request / response" feature. The current version of Web Services exists a perforance, coplexity and security issues, but it is still quite useful for interactive cross-platfor. The interaction between Coponents under different platfors can be achieved as long as the realization of a Web Services interface for the. In order to ore flexibly control the process, we ake use of the Workflow API provided by the Workflow Manageent Syste to achieve direct control of the process.by using it,we can custoize the functionality that workflow anageent syste provides to the custoer, which akes the work flow anageent and Control easy to elt in our business systes. For exaple, expanding the worklist of workflow capabilities and adding features in business systes, can ake it ore in line with our request. J2EE Coponent (J2EE coponents)j2ee Coponent refers to the deployent of J2EE Server in the EJB coponent. EJB coponent J2EE Server to provide access to various services, aking the preparation of EJB coponents siple. Various business systes through the deployent of the J2EE Server's EJB coponent provide services to other business systes in order to achieve the interconnection. 4. Business syste layer Business syste layer is to achieve specific business operational hospital level, including the registration syste, doctors workstations, reproductive center anageent syste, anageent syste for physical exaination, blood transfusion anageent syste, surgery, anesthesia anageent systes, subsystes clinical experts, edicines anageent syste and econoic anageent syste, integrated anageent and statistical analysis systes, data security anageent syste, laboratory and central laboratory inforation systes, picture archiving and counication syste, office autoation systes and external systes and so on. Business syste layer that is the layer of the ost iportant task is to provide the agent of the business agent layer.because the business syste layer of the business systes is achieved by different vendors, and other suppliers can not know how to ipleent the technology with the Internet, so it can only be ade by all suppliers of business systes business systes to provide their own agents. Workflow syste is running in the process, through a proxy to achieve with the various business sub-systes interact to achieve the entire process fro. B. large-scale hospital inforation syste integration Case During the syste integration, Registered patients is the function of the patient registration syste, doctor's orders belongs to the functions of the workstation, fees and charges are charging function of the syste, checked under the PACS syste function, testing is the function of LIS syste, edicine is edicine anageent syste. Subsystes realize agents by the various techniques described in the integrating progra,and access business processes layer through a proxy. In this case a siplified outpatient procedures are used as an exaple to discuss the workflow-based large-scale hospital inforation syste integration process. Each activity in the Figure through a proxy to interact with various subsystes in order to coplete the business process. The workflow odel is shown in Figure 5. And Exaine Check Reove Medicine Start Patientsre gistered Diagnosis Doctors told Hospital billing Charge Figure 5 out-patient flow chart VI. CONCLUSION Practice has proved that: This paper presents a workflow-based large-scale hospital inforation syste integration solutions using WFS developent tools as the integration platfor, using each business expert syste as working nodes, which allows developers to only use WFS provides application integration coponents to do soe appropriate prograing to achieve the strong coupling links of the application interface of the working nodes. Service Agent-layer technology achieves the various subsystes into the business process layer of the hook, the running of process fully descript that inforation in various subsystes has a good transission. Inforation adopts a unified XML forat, which is a good way to achieve a unified data forat and conversion. Through this integrated platfor we can integrate inforation resources inside and outside the hospital Out End

JOURNAL OF COMPUTERS, VOL. 6, NO. 1, JANUARY 2011 113 achieve the hospital business nors, strealine and accelerate hospital business processes, and achieve high efficiency and low-cost operation. At the sae tie, we can increase efficiency and anageent of hospital clinics to provide patients with ore convenient edical services. Therefore, to achieve large-scale hospital inforation syste integration is a guarantee of sustainable developent to hospital inforation syste. ACKNOWLEDGMENT This work is supported by Youth Fund of Sichuan Education Departent (NO.2007B021) and Youth Fund of Neijiang Noral University (No. 07NJZ-09) REFERENCES [1] D. Hollingsworth, The Workflow Reference Mode, Workflow Manageent Coalition, 1994, pp.11-35 [2] F. Casati, S. Ceri, and B. Pernici etc, Workflow evolution Data Knowledge Engineering, 1998, pp.211-238 [3] F. Leyann, D. Roller, Workflow-based applicaion, IBM Systes Journal, 1997, pp.102-123 [4] S. Khodakara, W. Mike, Petri net-based odeling of workflow systes An overview, European Journal of Operational Research, 2001, pp.664-676 [5] C. Prior, Workflow and process anageent, Workflow Manageent Coalition Handbook, 2002, pp.34-45 [6] G. F. Paul, R. R. Vries, A Reference arochitecture for Workflow Manageent Syste, Data & Konwledge Engineering, 1998,27pp.32~34,38~42 [7] ] R. Agarwal, G. Bruno, and M. Torchiano, An Operational Approach to the Design of Workflow Syste, Inforation and Software Technology, 2000, 42, pp.549~553 [8] Karl R.P.H Leung et al. The Liaision Workflow Engine Architecture. Proceedings of the 32 Hawaii international conference on Syste Sciences, Hawaii, Jan 1999 [9] R. Tagg et al. Preliinary Design of a Lightweight Workflow Server.Australasian conference Inforation Systes, Australia, 1997 [10] ] Y anbo Han, Ait Sheth, Christoph Bussler. A Taxonoy of Adaptive Work(CSCW 98),Towards Adaptive workflow Systes Workshop,Seattle,1998 [11] ] M. Kang, J. Froscher, A. Sheth, et al. A Multilevel Secure Workflow Manageent Syste. Proceedings of the 11th Conference on Advanced Inforation Systes Engineering(CaiSE 99),Heidelberg, Gerany, 1999 [12] Mathias Weskel, Thoas Goesann, Roland Holtenl, et al. A Reference Model for Workflow Application Developent Processes. Proceedings of the ACM 1999 Conference on Work Activities Coordination and Collaboration, San Francisco, 1999 [13] K. R. Abbott, S. K. Sarin. Experiences With Workflow Manageent: Issues for the Next Generation. Proceeding of the ACM 1994 Conference on Coputer Supported Cooperative Work (CSCW 94), 1994