Ah, your 'most obvious' method should have been obvious to me, too. I'll give
it a go. But yes, I think having access to the raw original text of the
message would be a useful convenience.
--
View this message in context:
http://www.nabble.com/Problem-with-misplaced-NTE-segment-tp24808667p248765
Yes, makes good sense, thanks. What would be handiest, though, is if the raw
message text could be passed to the registered handling application. How
could that happen?
--
View this message in context:
http://www.nabble.com/Problem-with-misplaced-NTE-segment-tp24808667p24865727.html
Sent from th
James,
Thanks for that, it's really useful to know how it works. I established in
the end that the segment was in fact in the right place, I had just been
misinformed about it in the spec (it was part of the patient group, not an
order level NTE), so it's probably just as well I didn't find a way
Sorry, you're right, I was assuming an ORM O01 message (which I've been
burying my head in recently). The same principle applies with an ORU_R01
message, though. Try:
int obxCount =
msg.getPATIENT_RESULT().getORDER_OBSERVATION().getOBSERVATIONReps();
for (int i = 0; i < obxCount; i++) {
I've run into a strange problem with an NTE segment in an HL7 message which I
think is malformed (but which I still have to be able to deal with). The
messages I'm receiving have an NTE segment after the PD1 segment, whereas I
think it should be after the MSH segment. HAPI chokes on it somewhat, i
Something like this should work:
int obxCount = msg.getORDER().getORDER_DETAIL().getOBSERVATIONReps();
for (int i = 0; i < obxCount; i++) {
OBX obx =
msg.getORDER().getORDER_DETAIL().getOBSERVATION(i).getOBX();
//use your terser here
String id = terser.get(obx, 1, 0, 1, 1);
nksharma0624 wrote:
>
> How do you mean..I thought your syntax for Terser was correct?
>
The syntax would have been correct if they really had been subcomponents
(and had ~, the tilde, been the subcomponent separator). But I was
completely misreading the field, which is really just a repeating
Sorry, not a terser problem, an idiocy problem on my part. I was mistaking
the repetition separator for a subcomponent separator...
--
View this message in context:
http://www.nabble.com/Terser-problem-with-subcomponents-tp24795762p24796097.html
Sent from the hl7api-devel mailing list archive a
I'm having problems getting a value I need using a Terser. Here's the PID
segment of a test message:
PID|1||0123456^^^H^HOSP~4567891252^^^NH^NHS||TEST SYSTEMS^TEST
PATIENT^^^||19400101|F|||Hinde House^Bethel Street^Norwich^Great Yarmouth
and Gorleston, Norfolk^NR2 1NR||01603 016030|||2|||
I'm working on an HL7 application taking ideas from Roger Searjeant's helpful
example
(http://sites.google.com/site/rogersearjeant/healthcare-and-hl7/hapi-ack-nak-message-helper).
That uses HAPI 0.5.1. I've been trying to get my stuff working with version
0.6, but I'm having a problem with one lin
10 matches
Mail list logo
