发新话题
打印

HL7 传送报告 -- 有请 sfinder

HL7 传送报告 -- 有请 sfinder

[QUOTE]最初由 JB 发表
[B]讲起真的 HL7 的知识和应用怎么大家就没半点兴趣了? [/B][/QUOTE]

Perhaps guru JB should give chinese tagalongs a stump speech as October surprise to boost HL7 movement.
hello mi world

TOP

HL7 传送报告 -- 有请 sfinder

[QUOTE]最初由 dongxi 发表
[B]比如用SQL SERVER或ACCESS
用VB或DELPHI

您手把手,脚把脚,代码把代码,字节把字节地教我做一个例子,我就明白多了。
——这样才可能在实践层次,而不是“理论”层次理解HL7 [/B][/QUOTE]



chameleon有很多的例子。而且还配有java/c++/c#/delphi/vb的源代码,你可以先从研究这些例子开始。

TOP

HL7 传送报告 -- 有请 sfinder

我去年发了一个 Word 文件,是整合 HIS、RIS、PACS 的规范。TCP/IP 端口、HL7 消息与字段,用法等等都说明得很清楚。按那个文件,下载一些 Mesa 的开源码, HL7 可以很快上手。

这个帖子是去年 7 月份左右发的,如果这里找不到可以到中国 PACS 论坛 HL7 版去找。

TOP

HL7 传送报告 -- 有请 sfinder

看了一下,估计就是这篇了。

请注意,该文由JB撰写,来源是——中国PACS论坛。版权归他。

另外,由我翻出来的,“翻”权归我。哈哈
以复杂理论之牙,还复杂世界之牙

TOP

HL7 传送报告 -- 有请 sfinder

抱歉
以复杂理论之牙,还复杂世界之牙

TOP

HL7 传送报告 -- 有请 sfinder

看了jb的spec,觉得大部分hl7界面实际应用的要点都概括到了。补充一点在hl7 spec表中第3栏O/R的意思是
o--可选。R--必需。

JB提到的QUERY FOR RESULT 界面,在不同机构间的信息整合会用到(原因请大家思考一下)。还有就是ER部门(原因也请大家思考一下)。这种界面是近几年才开始使用,使用时一定要小心,检索条件一定要精确。(原因请大家思考一下)

TOP

HL7 传送报告 -- 有请 sfinder

sfinder 说得对,push 还是主要的作业方式,query 用得比较少,变数也可以比较多。

TOP

HL7 传送报告 -- 有请 sfinder

[QUOTE]最初由 uchinaboy 发表
[B]请楼主解释一下为什么“先不要用XML”的原因,谢谢!

顺便强烈赞同楼上 [/B][/QUOTE]

请sfinder解释一下哈

TOP

HL7 传送报告 -- 有请 sfinder

如果你的 HL7 只是接自己的东西,想怎么做都可以。如果考虑的是跟其他设备兼容,要照顾到多方面。XML 虽然 sexy 但是如果对方没有的话是没法用的。再说 XML 有什么 added value? 只有 added incompatibility 和 frustrations。


HL7 2.3、2.4 在北美非常普及,用得很多。

TOP

HL7 传送报告 -- 有请 sfinder

HL7 2.x 是目前在北美应用最广泛的标准,但正是通过大量实践的检验,发现它有着先天性的不足,才催发了Version 3 的制定. 它的局限性至少有以下(sorry, my skill of typing Chinese is very poor…):

Implicit information model, which cause ambiguity during communication between sites.
Need for controlled vocabulary.
Limited to single encoding syntax
No explicit support for object technologies
No explicit support for security functions
Optionality is ubiquitous and troublesome.

From my experience, even both site using HL7 2.3 or 2.4, there still are lots of re-mapping effort needed, just because of the above limitations. I think HL7 version 3 could finally effectively resolve above limitations without sacrificing the advantages that current V2.x have.

But, changing from V2.x to V3 is painful and I’m not sure how long it’ll take…
If You Can't Measure It, You Can't Improve It. Lord Calvin 1895

TOP

HL7 传送报告 -- 有请 sfinder

Hi, I totally agree with your options but who is using V3 in North America. Which big HIS player is supporting V3? By the way, has V3 been offically released?  5 years ago,  I thought we might need to wait 5 year to start to use it. Now , I guess we still need to wait another 5 years to see it happend.

TOP

HL7 传送报告 -- 有请 sfinder

Agree with you about the V3's future in North America. Even if V3 has been officialy released, I am not positive that all major HIS players will adopt it in several years.

What I try to say is in China, it worth a try by refering V3 XML idea. As I understand, it doesn't matter right now in China to use V2.x or V3 (draft), just because there are no dominated standard yet, and hospitals in China are not in the position of exchanging data among multiple institutions.

I also noticed that in this forum, people talks HL7 a lot, but without using controlled vocabulary/terminology(i.e LOINC, ICD, CPT,SNOMED...), I don't see there is much value of only focusing HL7.
If You Can't Measure It, You Can't Improve It. Lord Calvin 1895

TOP

HL7 传送报告 -- 有请 sfinder

wa sai,xian zai dou kai shi guo ji jiao liu la!gen bu shang xing shi le.
各位大哥,那个什么chameleon在哪里有下载的?谢谢了,再不学习就要落伍了 _:-(
本人热爱党,热爱祖国,工作认真,学习努力,争取作医院信息化的带头人。

TOP

HL7 传送报告 -- 有请 sfinder

哇噻,现在都开始国际交流啦!跟不上形势了。

TOP

HL7 传送报告 -- 有请 sfinder

现在都开始更加交流啦(xian zai dou kai shi guo ji jiao liu la!)
应为:
现在都开始“国际”交流啦

TOP

发新话题