I know people have asked for this in the past, but I have not paid
attention because I have not been using the Terser. Are there terser
methods you can use to determine how many reps of a group, segment or field
exist in a message? If not, what's the best current workaround?
Charles Fisher
Div
The United States is adopting specifications ("Implementation Guides") for
interoperable laboratory reporting based on the HL7 v2.5.1 ORU^R01 message.
Without going into too many details, for some of these documents the
authors are "pre-adopting" features from HL7 2.7.1 into the 2.5.1-based
guide
The new release is supposed to be backwards compatible. However, when I
swapped out 1.2 for 2.1, my PID.getName() started returning an XPN[]
instead of XPN for 2.3 messages. This turns out to be true as of release
2.0, which I never installed. So maybe this means "backwards compatible
with 2.0
I am running a junit test in Eclipse that uses HAPI and MyBatis. There is
a lot of logging output to the Eclipse console, and it seems to be from the
HAPI parser:
...
DEBUG [main] - Match exists after position ORCOBRNTEOBXNTECTI:OBXNTE(1) for
OBR? true
DEBUG [main] - Match exists after position
We tried using generic classes for our Z-segment (ZLR, "Z segment for Lab
Reporting") for version 2.3 ORU^R01, but ultimately found it simpler to
just build a new segment class out of the available field classes, using
other segment sources (it's open source!) as models.
Attached is the source fo
When you modify source, you don't necessarily have to recompile the whole
thing. You just have to recompile the ones you changed, and then contrive
to have them in the classpath ahead of the standard jar files, so your
modified ones get picked up first. This works for us.
Charles Fisher
Divisio
The dependency information on the "Developing Using HAPI" page
(http://hl7api.sourceforge.net/using_hapi.html) on the site is out of date.
The version should be "0.6-beta1" instead of "0.6". I spent some little
time figuring this out.
There is probably a way to use a maven property in the site d
Apparently no one has answered your question. I have similar concerns. I
have built a major system around HAPI. Within a year or less I will need
to parse 2.5.1 messages.
Your note was the first time I became aware that there was some progress
toward an 0.6. Seeing the "HAPI 0.6-SNAPSHOT API"
This is just a vote in support of producing the next HAPI release, with
version 2.5.1 included. Granted that version 2.5.1 is not very different
from version 2.5. However, if the messages say "2.5.1" in MSH-12 then the
messages won't parse. HL7 has finally approved an Implementation Guide for
r
Daniel,
The tree tells all: put your message into the TestPanel application that
comes with HAPI and parse it. You will see how HAPI is creating the
internal tree of the message based on the abstract syntax diagram.
Basically, the second OBR group is being interpreted as an "Order Prior"
group.
Jim,
You may want to just go with Bryan when he says that "you have to customize
the message class to put a Z-segment in the middle of a group." HAPI
obviously has some default behavior for deciding where an unknown Z-segment
belongs when it encounters it in a message in the middle of parsing.
11 matches
Mail list logo
