Developing a Common Health Information Exchange Platform to Implement a Nationwide Health Information Network in South Korea / 대한의료정보학회지

OBJECTIVES: We aimed to develop a common health information exchange (HIE) platform that can provide integrated services for implementing the HIE infrastructure in addition to guidelines for participating in an HIE network in South Korea. METHODS: By exploiting the Health Level 7 (HL7) Clinical Document Architecture (CDA) and Integrating the Healthcare Enterprise (IHE) Cross-enterprise Document Sharing-b (XDS.b) profile, we defined the architectural model, exchanging data items and their standardization, messaging standards, and privacy and security guidelines, for a secure, nationwide, interoperable HIE. We then developed a service-oriented common HIE platform to minimize the effort and difficulty of fulfilling the standard requirements for participating in the HIE network. The common platform supports open application program interfaces (APIs) for implementing a document registry, a document repository, a document consumer, and a master patient index. It could also be used for testing environments for the implementation of standard requirements. RESULTS: As the initial phase of implementing a nationwide HIE network in South Korea, we built a regional network for workers' compensation (WC) hospitals and their collaborating clinics to share referral and care record summaries to ensure the continuity of care for industrially injured workers, using the common HIE platform and verifying the feasibility of our technologies. CONCLUSIONS: We expect to expand the HIE network on a national scale with rapid support for implementing HL7 and IHE standards in South Korea.

Architecture Design of Healthcare Software-as-a-Service Platform for Cloud-Based Clinical Decision Support Service / 대한의료정보학회지

OBJECTIVES: To design a cloud computing-based Healthcare Software-as-a-Service (SaaS) Platform (HSP) for delivering healthcare information services with low cost, high clinical value, and high usability. METHODS: We analyzed the architecture requirements of an HSP, including the interface, business services, cloud SaaS, quality attributes, privacy and security, and multi-lingual capacity. For cloud-based SaaS services, we focused on Clinical Decision Service (CDS) content services, basic functional services, and mobile services. Microsoft's Azure cloud computing for Infrastructure-as-a-Service (IaaS) and Platform-as-a-Service (PaaS) was used. RESULTS: The functional and software views of an HSP were designed in a layered architecture. External systems can be interfaced with the HSP using SOAP and REST/JSON. The multi-tenancy model of the HSP was designed as a shared database, with a separate schema for each tenant through a single application, although healthcare data can be physically located on a cloud or in a hospital, depending on regulations. The CDS services were categorized into rule-based services for medications, alert registration services, and knowledge services. CONCLUSIONS: We expect that cloud-based HSPs will allow small and mid-sized hospitals, in addition to large-sized hospitals, to adopt information infrastructures and health information technology with low system operation and maintenance costs.