The Health Information System of NTUH.pptVIP

The Health Information System of NTUH Feipei Lai 賴飛羆 National Taiwan University Hospital flai@.tw Why rightsizing? Heavy Loading (90%) and the performance is poor Expensive The user interface is unfriendly Difficult to integrate with other systems Difficult to maintain the system and satisfy the requirements. Goals Replace IBM PCS Same platform and technology for all applications. Same system for the headquarter and the branch hospitals. Outline History New System Platform SOA, HL7 Roadmap PACS Conclusion History Old HIS based on IBM PCS (Patient Care System) 1983 Outpatient Information System 1987 Inpatient Information System COBOL IMS (Information Management System) 1991 Emergency Information System 1999 Client/server (Sybase, PowerBuilder) HIS servers (1) New System Platform Microsoft VS.NET v.1.1, C#.NET, ASP.NET Relational Database Oracle 9i RAC Web-based user interfaces (4-tier) mix with embedded Windows Control components (3-tier) Solaris Operating System Scalable Architecture Service-Oriented Architecture (SOA) Divide the whole system into several subsystems communicated via SOAP protocol with each other and with the legacy systems SOA Why SOA? Facilitate Communication between Heterogeneous platforms Data exchange standard XML, SOAP Workflow improvement Multi-Tier Architecture Multi-Tier Architecture Security server Single sign-on Web server Access right control UI Application server Web services 4-tier mixed with 3-tier 4 tier architecture Web-based Embed HL7 message in SOAP Exchange messages by Web service call The advantage of web service Transmit through standard 80 port Accessible by multiple protocol SOAP HTTP Language independent 3 tier architecture Windows control components For some security reasons of the browser, we have to embed user components (trusted client). Traditional ActiveX component Smart Client Local print Read/Write NHI (National Health Insurance) card. Teamwork Enterprise architects Consistency acro