The amount of medical information is rapidly increasing in accordance with the development of medical technology. Therefore, developing efficient ways of management, exchange and sharing of medical information is becoming an important issue. A variety of models and tools introduced in hospitals, departments and clinics became obstacles in the reproduction and utilization of information. A proficient means of exchanging this medical information, known as an Application Program Interface (API) has been designed in the present study. A discharge summary which contains major description of medical care has been chosen as the source for this exchange. The API translated the information on the discharge summary into Health Level Seven (HL7) messages, which is the standard protocol for exchanging information. Users could send and/or receive a discharge summary using a web browser using this API. For the security of a web-server, we used a freeware, Mr.Flux, to control access to the server. Time to input data was significantly different according to the traffic of network, which was 341+/-55 seconds and 131+/-15 seconds at 10 p.m at 10 a.m. In summary, HL7 based on an API for the exchange of information on nuclear medical care could be used in different computing environments such as an internet based system that is convenient to use for most users.
Health Level Seven ; Internet ; Reproduction ; Web Browser

OBJECTIVE: HL7(Health Level 7) develops standards for the representation of clinical documents like discharge and consultation notes. The goal of the present study is to develop XML(eXtensible Markup Language)-based communication standard for discharge note. METHODS: This paper presents the use of XML for electronic communication in a document-based EMR, first, as a format for the exchange of structured message, and second, as a comprehensible way to represent patient document. A retrospective analysis of 1165 discharge notes, from the department Seoul National University Hospital, were extracted by querying OCS(Order Communication System) and taking every discharge note of main disease issued over one year period (2003.01.01~2003.12.31). RESULTS: An XML-based prototype for discharge note has been put into place representing the required "section" and "specific instance". In addition, a subset of the CDA(Clinical Document Architecture) Level One details has been described and integrated. CONCLUSION: Through the introduction of definitions for sections and specific instances, progress in the development of CDA Level Two and Three might be realized. An XML-based prototype was implemented, allowing a special view on XML data to generate this document type.
Electronic Health Records ; Health Level Seven ; Humans ; Retrospective Studies ; Seoul

Integrating medical instruments with medical information systems becomes more and more important in healthcare industry. To make medical instruments without standard communication interface possess the capability of interoperating and sharing information with medical information systems, we developed a medical instrument integration gateway based on Integrating the Healthcare Enterprise Patient Care Device (IHE PCD) integration profiles in this research. The core component is an integration engine which is implemented according to integration profiles and Health Level Seven (HL7) messages defined in IHE PCD. Working with instrument specific Javascripts, the engine transforms medical instrument data into HL7 ORU message. This research enables medical instruments to interoperate and exchange medical data with information systems in a standardized way, and is valuable for medical instrument integration, especially for traditional instruments.
Equipment and Supplies ; Health Level Seven ; Humans ; Information Systems ; Software

OBJECTIVES: Due to the increasing use of electronic patient records and other health care information technology, we see an increase in requests to utilize these data. A highly level of standardization is required during the gathering of these data in the clinical context in order to use it for analyses. Detailed Clinical Models (DCM) have been created toward this purpose and several initiatives have been implemented in various parts of the world to create standardized models. This paper presents a review of DCM. METHODS: Two types of analyses are presented; one comparing DCM against health care information architectures and a second bottom up approach from concept analysis to representation. In addition core parts of the draft ISO standard 13972 on DCM are used such as clinician involvement, data element specification, modeling, meta information, and repository and governance. RESULTS: Six initiatives were selected: Intermountain Healthcare, 13606/OpenEHR Archetypes, Clinical Templates, Clinical Contents Models, Health Level 7 templates, and Dutch Detailed Clinical Models. Each model selected was reviewed for their overall development, involvement of clinicians, use of data types, code bindings, expressing semantics, modeling, meta information, use of repository and governance. CONCLUSIONS: Using both a top down and bottom up approach to comparison reveals many commonalties and differences between initiatives. Important differences include the use of or lack of a reference model and expressiveness of models. Applying clinical data element standards facilitates the use of conceptual DCM models in different technical representations.
Delivery of Health Care ; Electronic Health Records ; Electronics ; Electrons ; Health Level Seven ; Humans ; Semantics

OBJECTIVE: This is designing the part of Electronic Medical Record using HL7 Development Framework and Reference Information Model to realize the building medical standard data model for sharing medical record between heterogeneous hospital systems. METHODS: The process used development of HL7 specifications consists of the following seven activities: 1.Project initiation. 2.Requirements Documentation. 3.Specification Modeling. 4.Specification Documentation. 5.Specification Approval. 6. Specification Publication. 7.Implementation Profiling. Each activity is briefly described in the subsections that follow and described in detailed in the methodology chapters that follow this introduction.3. Result. The steps, after 4 step, needs to standardized the results. So we didn't followed that steps1). RESULTS: We got the diagrams at each steps of the HDF methodology: 1.A dynamic description. 2.A static description of the concepts involved in the business process. 3.A Use Case model which identifies the system involved in the actual HL7 data/information exchange1). CONCLUSION: It was confirmed that HL7 RIM could take in the domestic demands of medical records, and concrete methodology was applied in practice. It can be a good reference for the hospitals constructing new information system and for the enterprises developing medical information systems to apply the HL7 version 3 to their works.
Commerce ; Electronic Health Records* ; Health Level Seven* ; Health Status* ; Information Systems ; Medical Records ; Publications

OBJECTIVES: To present the technical background and the development of a procedure that enriches the semantics of Health Level Seven version 2 (HL7v2) messages for software-intensive systems in telemedicine trauma care. METHODS: This study followed a multilevel model-driven approach for the development of semantically interoperable health information systems. The Pre-Hospital Trauma Life Support (PHTLS) ABCDE protocol was adopted as the use case. A prototype application embedded the semantics into an HL7v2 message as an eXtensible Markup Language (XML) file, which was validated against an XML schema that defines constraints on a common reference model. This message was exchanged with a second prototype application, developed on the Mirth middleware, which was also used to parse and validate both the original and the hybrid messages. RESULTS: Both versions of the data instance (one pure XML, one embedded in the HL7v2 message) were equally validated and the RDF-based semantics recovered by the receiving side of the prototype from the shared XML schema. CONCLUSIONS: This study demonstrated the semantic enrichment of HL7v2 messages for intensive-software telemedicine systems for trauma care, by validating components of extracts generated in various computing environments. The adoption of the method proposed in this study ensures the compliance of the HL7v2 standard in Semantic Web technologies.
Compliance ; Health Information Systems ; Health Level Seven* ; Health Status* ; Semantics* ; Telemedicine*

The amount of medical information is rapidly increasing in accordance to the development of medical technology. Therefore, it is an important issue to develop the efficient ways of management, exchange and sharing of medical informations. Though the variable models and tools have been introduced to hospitals, departments and clinics, those became obstacles in the production and utilization of informations. A proficient mean of exchanging this medical informations, known as an Application Program Interface(API) has been designed and introduced in the study. A discharge summary has been chosen as the source for this exchange of medical information, because it contains major description of medical or surgical care. API translated the information as Health Level Seven(HL7) messages, which is the standard protocol for exchanging informations. Users could send or receive a discharge summary using a web browser in this API. In summary, HL7 based on an API for the exchange of information of the plastic surgical care can be used in different computing environments such as an internet based system and is convenient to use for most doctors.
Health Level Seven ; Health Status ; Internet ; Medical Informatics Applications ; Surgery, Plastic* ; Web Browser

OBJECTIVE: This study proposes a hospital information system through the design and actualization of the Health Level 7 Development Framework (HDF) as a medical standard data model to sharing medical records between different hospital systems. The Health Level 7 Development Framework is a technique designed to capture domain expertise in a manner that it to be structured to create and validate models, which are subsequently translated into messages. METHODS: The process used Health Level 7 Development Framework methodology with Health Level 7 tools. RESULTS: We drew diagrams for each steps of the Health Level 7 Development Framework and an Extensible Markup Language (XML) schema for chemotherapy order system. CONCLUSION: This study applied Health Level 7 Development Framework methodology to practice. It is a good reference for the hospital information system (HIS) and enables information sharing among healthcare institutions.
Delivery of Health Care ; Drug Therapy* ; Health Level Seven ; Hospital Information Systems ; Information Dissemination ; Medical Records

The development of hospital business demands the integration of information systems. After studying the relative technologies for system connection,system integration and different modes of connecting system, we put forward a protocol to integrate the existing laboratory information system( LIS) and hospital information system(HIS). It introduces the multi-tier distributed technical methods for improving the client/server applications; it ascertains the units and transactions participating in workflow integration by referencing the IHE( Integrating the Healthcare Enterprises) Laboratory Technology Framework; it implements information exchange by Health Level 7(HL7) standards; and it can conserve previous investment and avoid some problems of security, maintenance and realtime process without the risk of massively updating system.
Clinical Laboratory Information Systems ; Health Level Seven ; Hospital Information Systems ; Humans ; Systems Integration

The Arden Syntax is a language for expressing computable medical decisions. It was developed and published under the direction of Health Level Seven, Inc (HL7), and is a standard of the American National Standards Institute (ANSI). It is used to construct executable Medical Logic Modules (MLMs) that represent individual clinical decisions. The authors introduced brief explanation of the Arden Syntaxand gave an example to help readers understand it with easy. Although Arden Syntax is the HL7 standard, there are problems related to the adoption of Arden Syntax as the standard tool for describing medical logic: the curly-braces problem, and the compiler problem. GELLO as well as virtual Medical Record based on the HL7 Reference Information Model (RIM) may provide solutions to the former problem. The latter problem would be resolved by introducing XML based expression of Arden Syntax, the ArdenML: the next generation of Arden Syntax. Unfortunately, Korean hospital information systems are not yet ready to adopt clinical decision support system including Arden Syntax. However, when Arden Syntax version 3.0 (ArdenML) with Korean rule-base engines is introduced into the hospital information system, it would be easier to build up clinical decision support system in Korea.
Adoption ; Health Level Seven ; Hospital Information Systems ; Korea ; Logic ; Medical Records