1.理解HL7(HL7中的基本概念）(conceptual approach)

HL7在第二章（控制中）定义了一些基本概念如下

   1.trigger events

       The Standard is written from the assumption that an event in the real world of healthcare
creates the need for data to flow among systems. The real-world event is called the
trigger event. For example, the trigger event a patient is admitted may cause the need for
data about that patient to be sent to a number of other systems. The trigger event, an
observation (e.g., a CBC result) for a patient is available, may cause the need for that
observation to be sent to a number of other systems. When the transfer of information is
initiated by the application system that deals with the triggering event, the transaction
is termed an unsolicited update

  翻译：这标准中定义的，假如在真实的医疗保健世界中创建的需要将其数据在多个系统之间进行流动。真实世界的事件被叫做触发世界，例如，病人住院触发事件可能导致该住院数据在多个其他系统之间流动，这个触发事件，通过观察一个病人是可用的，可能导致需要将其观察的发送至其他的系统，当这个传输信息通过应用系统发动之后，需要处理这个触发事件，这个事物被定义为一个主动更新；

 理解：在嵌入式开发中，我们总是会遇到中断事件，当中断事件产生之后，我们就会做一些其他的操作，而这个中断事件就是一个触发事件，只是触发这个中断事件的，可能是定时器到期，有可能是外部中断，而在HL7中，触发事件的产生是由于在医疗系统中创建了新的数据。

acknowledgments: original mod

确认：原始模式

when the unsolicited update is sent from one system to another, this acknowledgment mode
specifies that it be acknowledged at the application level. The reasoning is that it is
not sufficient to know that the underlying communications system guaranteed delivery of the
message. It is also necessary to know that the receiving application processed the data
successfully at a logical application level;

但主动更新从一个系统发送到另外一个系统，确认模式指定了主动更新消息在应用层被确认了，样设
置的原因是，不仅在基本的通信系统确保信息的传递，而且还需要知道接收端程序在逻辑应用层上成功
地对数据进行了处理
 理解：意思就是当接收到触发世界发送的数据之后，我在应用层需要进行回复确认，以此来保证数据传递成功

The acknowledgment may contain data of interest to the system that initiated the exchange.
For example, if a patient care system has processed the trigger event a lab test is ordered
for a patient, it may send an unsolicited update to a lab application identifying the
patient, the test ordered, and various other information about the order. The ancillary
system will acknowledge the order when it has processed it successfully. For some pairings
of patient care and ancillary department systems the acknowledgment may also include the
ancillary identification number that was assigned. (HL7 does not require Order Entry and
Results Reporting applications to interface in this manner, but it supports those that do.

认模式用系统所感兴趣的数据来开始信息交流。例如，一个病人服务系统处理触发事件——病人预定
一化验检查，系统将发送一个主动更新（请求）到化验室应用程序来确认病人，以及其他的预定信息。
辅助系统将成功的处理有关检查预定信息。在一些病人服务及其辅助系统中，确认模式也包括系统分配
的确认号。（ HL7并不要求预定登录和结果报告程序一定使用这一方式进行工作，但它支持这一方

The HL7 Standard makes no assumptions about the ownership of data. It also makes no
requirements of its own on the subsequent action of the recipient of data, nor does it make
any assumption about the design or architecture of the receiving application system. The
scope of HL7 is restricted to the specification of messages between application systems,
and the events triggering them. HL7 does not explicitly support, but can be used with,
systems that support store and forward and data broadcast facilities (see the HL7
Implementation Support Guide
L7标准对数据的所有权不做任何假定。它不但自己对接受数据的一系列行为没有要求，而且也对数据
接收应用系统的设计或建构不作任何规定。 HL7的规定范围仅局限于应用系统之间交流的特定信息，和
相应的触发事件。 HL7没有明确的支持系统，但能应用于支持存储、转发、以及数据公布的系统。（ 见
HL7应用支持指
the HL7 Standard makes no functional interpretation of the requirement that a system commit
the data in a message to its database before acknowledging it. All that is required is
that the receiving system accept responsibility for the data, providing the same integrity
test that it would apply to data from any source. To continue the prior example, the
ancillary system may acknowledge the order after placing it in an input queue, expecting to
fully process the order into its database at a future time. The only assumption is that
the input queue is maintained at the same level of integrity as the database
HL7要求一个系统在对信息确认之前把信息中的数据提交到它的数据库中，但对这一要求没有功能上的
解释。所要求的是：接收系统对数据负责，并提供整体化测试以适用于任何来源的数据。我们继续以前
述例子为例：辅助系统可以将预定请求放入一个输入排队序列中，以后再进行确认，并在将来全面处理
数据库中预定信息。其仅有假定是：输入队列以如同数据库形式的保留，即保留在整体化的相同层中

Acknowledgments: enhanced mode
确认：增强模式
he HL7 acknowledgment paradigm has been extended to distinguish both accept and
application acknowledgments, as well the conditions under which each is required. With a
positive accept acknowledgment, the receiving system commits the message to safe storage in
a manner that releases the sending system from the need to resend the message. After the
message has been processed by the receiving system, an application acknowledgment may be
used to return the resultant status to the sending system
7确认范例已经扩展到要区别接受确认和应用程序水平确认，以及各自所要求的条件。对于一正确的
接受（信息）确认，接收系统会把信息提交给安全存储库，该方式能使发送系统免于重新发送信息。当
信息已经被接受系统处理之后，应用程序水平确认将给（信息）发送系统返回处理结果状态

Querie
query documentation including messages, segments, special protocols, implementation
considerations and examples have been moved to chapter 5. The unsolicited display messages
were also moved because their message syntax is query-like in nature

查询文档包括信息，信息段，特定协议，执行注意事项和例子（见第 5 章）。主动提供的显示信息也被
转移，因为这些信息的语法本质上是与查询一致的