[英]Is OBR segment required to view the OBX segment attachments in HL7 message?
I'm trying to parse an HL7 message file which is of version 2.3.1. 我正在尝试分析版本2.3.1的HL7消息文件。 OBX segment is coming as null when the message is parsed.
解析消息时,OBX段变为空。
If I don't have OBR segment in HL7 message, Terser is failing to fetch the OBX segment values (it's returning null values), so is OBR segment mandatory to view OBX attachments in an HL7 message? 如果HL7消息中没有OBR段,则Terser无法获取OBX段值(返回的是空值),那么OBR段是否必须查看HL7消息中的OBX附件?
The OBX
segment mainly carry clinical report data. OBX
段主要承载临床报告数据。 It is mainly used in ORU
message and rarely with ORM
, ADT
and other. 它主要用于
ORU
消息中,很少与ORM
, ADT
等一起使用。 This segment is optional and can be repeated in message. 此段是可选的,可以在消息中重复。
The OBR
segment mainly carry placer and filler order numbers (used as identifiers), exam information etc. This segment is mandatory. OBR
段主要包含放置和填充订单号(用作标识符),检查信息等。此段是必需的。
ORU (Observation Result) messages should contain the OBR segment followed by the OBX segment for each observation.
对于每个观察,ORU(观察结果)消息应包含OBR段,后跟OBX段 。
About its usage in ORM
message: 关于它在
ORM
消息中的用法:
Usage in the ORM Message
ORM消息中的用法
In an ORM message, the OBR segment is part of an optional group that provides details about the order.在ORM消息中,OBR段是提供有关订单详细信息的可选组的一部分。 When the order placer creates the ORM message, they will include the Placer Order Number in the OBR-2 and/or ORC-2 fields.
当订单放置者创建ORM消息时,它们将在OBR-2和/或ORC-2字段中包含放置者订单号。 These two fields should contain the same information, and at least one of the two must contain the placer order number.
这两个字段应该包含相同的信息,并且两个字段中的至少一个必须包含放置者订单号。 The message may contain multiple orders for which the rules still apply.
该消息可能包含规则仍适用的多个订单。
About its usage in ORU
message: 关于它在
ORU
消息中的用法:
Usage in the ORU Message
ORU消息中的用法
In an ORU message, the OBR segment is used as a report header and contains important information about the order being fulfilled (ie order number, request date/time, observation date/time, ordering provider, etc.).在ORU消息中,OBR段用作报告标头,并包含有关正在履行的订单的重要信息(即订单号,请求日期/时间,观察日期/时间,订购提供商等)。 It is part of a group that can be used more than once for each observation result that is reported in the message.
它是该组的一部分,可以为消息中报告的每个观察结果多次使用。
When the filler creates the ORU message, they will include the Filler Order Number (such as an accession number) in the OBR-3 and/or ORC-3 fields.
当填充者创建ORU消息时,它们将在OBR-3和/或ORC-3字段中包含填充者订单号(例如登录号)。 If the filler order number is not present in the ORC-3, it must be present in the OBR-3 because the ORC segment is optional in the ORU message.
如果ORC-3中不存在加油机订单号,则必须在OBR-3中存在,因为ORC段在ORU消息中是可选的。
Considering this, OBR
is mandatory segment in both the ORU
and ORM
(optional group) messages. 考虑到这一点,
OBR
是ORU
和ORM
(可选组)消息中的强制性段。 This is irrespective of dependency of OBX
segment on OBR
segment. 这与
OBX
段对OBR
段的依赖关系OBX
。
To answer your comment, I never used REF
message. 为了回答您的评论,我从未使用过
REF
消息。 But, first google search gave me this . 但是,首先谷歌搜索给了我这个 。 It look that
OBR
is mandatory in those messages. 看起来
OBR
在这些消息中是必需的。
While the OBR segment is stated as mandatory in the HL7 standards for most messages the parser software you are using may allow you to set it as optional. 虽然HL7标准将OBR段声明为大多数消息的必需项,但您使用的解析器软件可能会允许您将其设置为可选。
Deciding to do this though should be considered only if there is a good reason why the sending system cannot or will not include the OBR segment in the message. 但是,只有在有充分的理由说明发送系统不能或不将OBR段包含在消息中时,才应考虑决定这样做。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.