HL7在HIS系统中的应用研究

医院信息系统(HIS)间的"异构"问题由来已久,而业务的发展要求实现医疗信息的交换和共享.本课题引入了HL7标准作为医院信息系统间共同遵循的数据交换协议,以实现异构系统间数据的交换.文章以HL7消息作为主要研究对象,设计一个HL7消息的构建、解析演示系统.中间件包括两个功能模块:HL7消息的构建/解析模块和消息传输模块.消息的格式基于XML技术.系统的演示表明,在对现有系统不作更改的前提之下,采用外挂中间件的模式,能在系统间正常地处理传输基于XML格式的HL7消息,很好地解决了异构系统间数据的交换,符合当前的需要.本课题所作的探讨也为将来深入的研究工作提供了帮助.     

基于HL7 V3模型建立应用系统自身数据模型的探讨

HL7 V3是采用模型驱动开发,RIM是HL7 V3模型的基础,DMIM和RMIM是建立在RIM基础上并用于直接生成接口消息定义的消息信息模型。由于HL7标准在医疗卫生信息领域的重要性,很多厂商试图基于HL7 V3的模型作为自身系统架构设计的基础,开发中间件平台产品或独立的应用系统。但RIM的模式完全是针对系统接口设计,并不适合应用系统设计。因此,基于HL7 V3的模型作为自身系统架构设计的基础。应抛开RIM和完全仿照RIM的DMIM、RMIM,而直接从更具体的HMD反推出未套用RIM之前的DIM,再按照适合自身系统的设计模式,建立系统自身的数据模型。     

基于MIF文件实现HL7 V3消息解析器

目的实现基于模型交换格式(MIF)文件的健康第7层标准第3版(HL7V3)消息解析器。方法通过MIF文件规定的约束,采用Java特殊兴趣小组(SIG)开发的工具包辅助开发,基于面向对象编程,对HL7V3消息进行解析,消息以RIM对象图在内存中表示,并重新构建后输出。结果选取大量不同域的HL7V3消息进行试验,均可很好地实现对HL7V3消息的解析。结论 HL7V3消息解析器完全达到了使用标准,为今后应用在支持HL7V3的医疗信息系统及相关产品中提供了底层技术支持,也为异构医疗系统间的信息共享提供解决方案。     

Mirth平台和HL7标准下的PACS/RIS与HIS接口设计及其应用

介绍HL7标准的消息格式,分析PACS/RIS与HIS之间的数据交换流程,设计HL7接口引擎,建立Mirth平台。通过Mirth平台和基于HL7标准的接口引擎实现PACS/RIS与HIS之间的数据交互和共享。     

HL7 V3在区域医疗交换平台中的应用研究

区域医疗交换平台是所有医疗信息系统中覆盖数据量最大、涉及信息系统种类最多的系统之一。HL7（HealthLevelSeven）标准的出现为异构医疗信息系统之间的信息数据交换与共享提供了基础条件和重要的应用价值。针对区域交换平台在国内外的研究现状以及HL7发展,概述了HL7 V2．x版本与HL7 V3版本,结合HL7 V2在区域交换平台的应用,借助HL7 V3的RIM模型及V3消息,设计了基于HL7 V3标准的区域医疗交换平台,实现了医院之间、医院与卫生机构之间的信息交换与共享。     

基于HL7标准与中间件技术集成方法的信息化平台

论述和总结了医院针对信息化建设中急待解决的医疗信息共享的问题,以中间件技术为解决方案,以XML和HL7为具体手段,加强信息平台建设,解决医院内部子系统之间,以及多家医院HIS与HIS的异构数据源环境下的数据集成与数据共享问题的思路与做法。     

HL7应用研究与数字医院建设

本文简述了目前我国医院信息系统之间数据交换与信息共享存在的问题,在研究和分析国际医疗卫生领域信息系统指标体系及交换协议(HL7)的组成与数据结构基础之上,提出了采用HL7消息构造器/解析器的方法,实现HL7本土化应用并保持与国际接轨,以解决我国医院信息系统之间数据交换与信息共享;建议以本土化HL7为基础,全面进行我国数字医院的建设.     

基于HL7标准的PACS/RIS与HIS集成设计与应用

目的：设计基于HL7标准PAcs／RIS与HIS之间的集成接口,解决两个系统之间数据共享的问题,优化业务流程。方法：介绍了HL7标准的消息格式,分析了PACS／RIS与HIS之间的数据交换流程,在此基础之上,设计了HL7接口引擎,实现了数据共享。结果：通过MIRTH平台,实现了PACS／RIS与HIS2之间基于HL7标准的集成。结论：基于HL7标准的PACS／RIS与HIS之间集成,符合国际标准,扩展性好,大大提高了医院的工作效率,避免了资源浪费。     

基于HL7的HIS与RIS/PACS集成设计

随着医院信息化的发展,医院信息系统间的集成已成为充分实现医院业务流程的重要环节。介绍了HL7的消息格式和数据交换方式,结合医院现有的HIS与RIS／PACS数据交换过程,提出了一种基于HL7的集成接口设计。     

灾难现场远程医疗数据交换标准构建探讨

从技术层面探讨了构建灾难现场远程医疗数据传输交换标准的原则、思路、方法以及具体应用,提出借鉴西方医学数据传输标准HL7的构建方法、维护机制以及具体应用。加入特定的应用场景、事件与相关的消息结构。完成远程医学数据传输标准的本地化应用与扩展。     

Implementation of HL7 to client-server Hospital Information System (HIS) in the University of Tokyo Hospital

In developing a large-scale Hospital Information System (HIS), a client-server architecture has been gaining in popularity. It is important to introduce a standard message protocol that is independent both on the database structure and on the vender's proprietary platform. We introduced Health Level Seven (HL7) to our hospital information system. From our experiences, although we had to modify the original HL7 specifications in order to introduce the protocol to a client-server HIS especially in the area of order entry and record-oriented query, it was found that HL7 can be adopted in a client-server HIS.     

基于HL7 V3的检验申请消息交互接口设计

以检验申请消息为例,介绍HL7 V3消息交互服务接口设计流程和方法,分为业务分析、业务域DMIM确定、业务模型RMIM确定、RMIM裁剪、生成HMD文件、生成消息定义文件6步.     

The Development of a Highly Constrained Health Level 7 Implementation Guide to Facilitate Electronic Laboratory Reporting to Ambulatory Electronic Health Record Systems

Electronic laboratory interfaces can significantly increase the value of ambulatory electronic health record (EHR) systems by providing laboratory result data automatically and in a computable form. However, many ambulatory EHRs cannot implement electronic laboratory interfaces despite the existence of messaging standards, such as Health Level 7, version 2 (HL7). Among several barriers to implementing laboratory interfaces is the extensive optionality within the HL7 message standard. This paper describes the rationale for and development of an HL7 implementation guide that seeks to eliminate most of the optionality inherent in HL7, but retain the information content required for reporting outpatient laboratory results. A work group of heterogeneous stakeholders developed the implementation guide based on a set of design principles that emphasized parsimony, practical requirements, and near-term adoption. The resulting implementation guide contains 93% fewer optional data elements than HL7. This guide was successfully implemented by 15 organizations during an initial testing phase and has been approved by the HL7 standards body as an implementation guide for outpatient laboratory reporting. Further testing is required to determine whether widespread adoption of the implementation guide by laboratories and EHR systems can facilitate the implementation of electronic laboratory interfaces.     

HL7 Clinical Document Architecture,Release 2

Clinical Document Architecture, Release One (CDA R1), became an American National Standards Institute (ANSI)–approved HL7 Standard in November 2000, representing the first specification derived from the Health Level 7 (HL7) Reference Information Model (RIM). CDA, Release Two (CDA R2), became an ANSI-approved HL7 Standard in May 2005 and is the subject of this article, where the focus is primarily on how the standard has evolved since CDA R1, particularly in the area of semantic representation of clinical events. CDA is a document markup standard that specifies the structure and semantics of a clinical document (such as a discharge summary or progress note) for the purpose of exchange. A CDA document is a defined and complete information object that can include text, images, sounds, and other multimedia content. It can be transferred within a message and can exist independently, outside the transferring message. CDA documents are encoded in Extensible Markup Language (XML), and they derive their machine processable meaning from the RIM, coupled with terminology. The CDA R2 model is richly expressive, enabling the formal representation of clinical statements (such as observations, medication administrations, and adverse events) such that they can be interpreted and acted upon by a computer. On the other hand, CDA R2 offers a low bar for adoption, providing a mechanism for simply wrapping a non-XML document with the CDA header or for creating a document with a structured header and sections containing only narrative content. The intent is to facilitate widespread adoption, while providing a mechanism for incremental semantic interoperability.