I agree - As far as I know the OMG^O19 did not change in 2.5. I just find
it troublesome that new 'global rules' such as the ones in section 2.5.2
does not apply for all messages, but only newly defined. I guess I'll just
have to live with that.
2012/11/20 christian ohr
>
> The definition for O
The definition for OMG^O19 did not change in 2.5 - the first segment in that
group is still optional. I don't think this statement in the spec does
anything about this - it's just that any new messages structures (introduced
in 2.5 and after) may not contain optional segments as first element in a
Okay, I get your point - the keywords in the note was "newly defined" ...
I'm just thinking that it's a weird way of maintaining backwards
compatibility - gotta blame that on the specification, this is of course
not HAPI's fault ;)
If, for instance the OMG^O19 was defined in, say the 2.4 spec (whi
OMG_O19 is one of the messages which may be hard to parse unambiguously. The
problem lies in the fact that the ORDER_PRIOR group begins with an
*optional* ORC segment. So, the sequence ORC TQ1 OBR can be parsed in both
ways Søren described it, and there is virtually no means for HAPI to pick
the "
Well, according to the standard - section 4.4.4, it is stated that the BLG
segment is optional. I think there might be a bug, in that it seems that
the parser does not respect the rule stated at Page 2-7, section 2.5.2:
"... *As of v 2.5, the first segment in a newly defined segment group will
be
I am using 2.0.1
Jens Kristian Villadsen writes:
>
>
> What version of HAPI are you using?
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free tod
What version of HAPI are you using?
2012/10/25 Søren Heintzelmann Therkildsen <
soren.heintzelmann.therkild...@systematic.com>
> Hi,
>
> ** **
>
> I am trying to parse an OMG message containing several orders for image
> diagnostics.
>
> ** **
>
> Unfortunately it seems that there is amb
Hi,
I am trying to parse an OMG message containing several orders for image
diagnostics.
Unfortunately it seems that there is ambiguity in the OMG structure.
My message looks like this:
MSH|^~\&|MYAPP|MY_FACILITY|RADIOLOGY_APP|RADIOLOGY_DEPARTMENT|20091027143626||OMG^O19|1235|P|2.5.1|||AL|AL
P
8 matches
Mail list logo
