Menu
▾
▴
hl7api-devel — developer list
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(6) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
(4) |
May
(5) |
Jun
(6) |
Jul
(3) |
Aug
(13) |
Sep
(28) |
Oct
(33) |
Nov
(8) |
Dec
(1) |
| 2003 |
Jan
(6) |
Feb
(2) |
Mar
|
Apr
(25) |
May
(21) |
Jun
(13) |
Jul
(12) |
Aug
(14) |
Sep
(6) |
Oct
(6) |
Nov
(16) |
Dec
(6) |
| 2004 |
Jan
(5) |
Feb
(7) |
Mar
(13) |
Apr
(17) |
May
(24) |
Jun
(14) |
Jul
(14) |
Aug
(8) |
Sep
(3) |
Oct
(8) |
Nov
(14) |
Dec
(26) |
| 2005 |
Jan
(18) |
Feb
(12) |
Mar
(29) |
Apr
(9) |
May
(4) |
Jun
(12) |
Jul
(17) |
Aug
(9) |
Sep
(12) |
Oct
|
Nov
(12) |
Dec
|
| 2006 |
Jan
(46) |
Feb
(18) |
Mar
(11) |
Apr
(13) |
May
(12) |
Jun
(27) |
Jul
(34) |
Aug
(45) |
Sep
(27) |
Oct
(13) |
Nov
(26) |
Dec
(22) |
| 2007 |
Jan
(21) |
Feb
(29) |
Mar
(32) |
Apr
(6) |
May
(11) |
Jun
(13) |
Jul
(14) |
Aug
(11) |
Sep
(15) |
Oct
(7) |
Nov
(30) |
Dec
(16) |
| 2008 |
Jan
(11) |
Feb
(14) |
Mar
(5) |
Apr
(18) |
May
(12) |
Jun
(11) |
Jul
(5) |
Aug
(12) |
Sep
(3) |
Oct
(2) |
Nov
(15) |
Dec
(2) |
| 2009 |
Jan
(18) |
Feb
(6) |
Mar
(9) |
Apr
(10) |
May
(29) |
Jun
(16) |
Jul
(44) |
Aug
(49) |
Sep
(14) |
Oct
(21) |
Nov
(11) |
Dec
(22) |
| 2010 |
Jan
(12) |
Feb
(13) |
Mar
(5) |
Apr
(6) |
May
(15) |
Jun
(15) |
Jul
(14) |
Aug
(20) |
Sep
(17) |
Oct
(36) |
Nov
(19) |
Dec
(7) |
| 2011 |
Jan
(8) |
Feb
(14) |
Mar
(21) |
Apr
(12) |
May
(6) |
Jun
(12) |
Jul
(17) |
Aug
(6) |
Sep
(13) |
Oct
(15) |
Nov
(26) |
Dec
(9) |
| 2012 |
Jan
(25) |
Feb
(13) |
Mar
(31) |
Apr
(10) |
May
(16) |
Jun
(21) |
Jul
(61) |
Aug
(38) |
Sep
(16) |
Oct
(13) |
Nov
(37) |
Dec
(26) |
| 2013 |
Jan
(20) |
Feb
(26) |
Mar
(34) |
Apr
(32) |
May
(27) |
Jun
(56) |
Jul
(16) |
Aug
(38) |
Sep
(35) |
Oct
(17) |
Nov
(11) |
Dec
(7) |
| 2014 |
Jan
(36) |
Feb
(13) |
Mar
(25) |
Apr
|
May
(27) |
Jun
(33) |
Jul
(34) |
Aug
|
Sep
(4) |
Oct
(11) |
Nov
(42) |
Dec
(2) |
| 2015 |
Jan
(5) |
Feb
(6) |
Mar
(11) |
Apr
(3) |
May
|
Jun
(1) |
Jul
(2) |
Aug
(5) |
Sep
(5) |
Oct
(5) |
Nov
(8) |
Dec
(19) |
| 2016 |
Jan
(8) |
Feb
(12) |
Mar
(6) |
Apr
(5) |
May
(5) |
Jun
(3) |
Jul
(1) |
Aug
|
Sep
(9) |
Oct
(1) |
Nov
(2) |
Dec
(5) |
| 2017 |
Jan
(2) |
Feb
|
Mar
(3) |
Apr
(6) |
May
(8) |
Jun
(7) |
Jul
(14) |
Aug
(10) |
Sep
(6) |
Oct
(2) |
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
(9) |
Mar
(2) |
Apr
(3) |
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
(8) |
Sep
(4) |
Oct
(3) |
Nov
(1) |
Dec
(1) |
| 2019 |
Jan
(10) |
Feb
(2) |
Mar
(6) |
Apr
(1) |
May
(2) |
Jun
|
Jul
(5) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2020 |
Jan
(9) |
Feb
|
Mar
|
Apr
(6) |
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(9) |
Oct
(1) |
Nov
(11) |
Dec
|
| 2021 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(7) |
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2023 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
(2) |
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
(7) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
|
Dec
|
|
From: Shrock, C. <Sh...@in...> - 2004-10-28 19:48:59
|
Thank you, Nico.
I base64 encoded the actual message to avoid munching....the message didn't
have multiple segments when I sent the original email :)
copy-n-paste into TestPanel after decoding it to see what I mean.
TVNIfF5+XCZ8QURNfFNITXxBTEx8QUxMfDIwMDQxMDI3MTQ0Mnx8QURUXkE
xM3xBRE0tSFVCLjEuNDgwOTN8RHwyLjEKRVZOfEExM3x8fHxUV0IKUElEfD
F8WjQ5MzV8WjAwMDAwNDk4M3x8VEVTVFNITV5UV0JeXl5efE5JTkVUWU5JT
kUsQUdFTlR8MTk2MjEyMTJ8TXxEQU5HRVJeTklDS15eXl58MXw3ODU2IFcg
RUFTVF5eU1BPS0FORV5XQV45OTIwOHxTUE8tV0F8NTA5IDc4OS0wOTc4fDU
wOSA0NzQtMzEzMXx8RHxBR3xaMDAwMDYxNTF8ODkwLTIzLTQ1NjgKUFYxfD
F8RXxaLkJMVV5efEVNfHx8QkFCTEFeQmFiYl5MYXJyeV5eXl58RUFSQVJeR
WFybF5BcnRodXJeRF5eXnx8fHx8fEF8fHx8RVJ8fE1TQ1Z8fHx8fHx8fHx8
fHx8fHx8fHx8U0hNfHxSRUd8fHwyMDA0MTAyNzE0MjMKSU4xfDF8TVNDfHx
NU0MgUFJFTUVSQXxQTyBCT1ggMzA0OF5eU1BPS0FORV5XQV45OTIyMC0zMD
Q4fHw1MDkgNTM2LTQ1MDB8fHx8fDIwMDQxMjAxfDIwMDkxMjAzfHx8VEVTV
FNITV5UV0JeXl5efFNQfHx8fHx8fHx8fHx8fHx8fHx8MzIxNjU0OTg3fDEy
MzQ1Njc4OQpHVDF8MXx8VEVTVFNITV5UV0JeXl5efHw3ODU2IFcgRUFTVF5
eU1BPS0FORV5XQV45OTIwOHw1MDkgNzg5LTA5Nzh8fHx8fFNQfDg5MC0yMy
00NTY4fHx8fFNITUN8VyAxMDEgOFRILCBCT1ggVEFDIEYtOV5eU1BPS0FOR
V5XQV45OTIyMHw1MDkgNDc0LTMxMzF8fEZUCkRHMXwxfFRYfHxURVNURU1Q
QVRIIElOVEVSRkFDRQpaVjF8Xl5eXnxBQUxTVUVeQWFsZ2FyZF5TdWVeXl5
efERBQlJBXkRhYmFsb3NeUm9kb2xmb15BXl5efHx8fHxQVE5eREFEXl5eXn
xGQXw3NTMxIE4gU09VVEheXlNQT0tBTkVeV0FeOTkyMDN8NzU4IDYzMi00N
TEyfFRFU1RFUnxURVNURVJ8U0FDUkVEIEhFQVJUIE1FRElDQUwgQ0VOVEVS
fFcgMTAxIDhUSCwgQk9YIFRBQyBGLTleXlNQT0tBTkVeV0FeOTkyMjA=
-----Original Message-----
From: ni...@sk... [mailto:ni...@sk...]
Sent: Thursday, October 28, 2004 11:58 AM
To: hl7...@li...
Subject: RE: RE: [HAPI-devel] Peculiar parse of a valid HL7 message in
TestPan
Hi Court,
I don't have the documentation of HL7 v2.1 but I'm afraid that your message
is not correct.
Normally you can only have 1 PID segment and 1 PV1 segment in a A05 message
(at least in v2.5).
I think that's the cause of the strange behaviour of HAPI...
Best Regards
Nico
_____
I found that in this particular case, the order of the segments matters.
The DG1 segment was being recognized were is existed in the message, but a
placeholder was being put immediately following the PV1 segment where hl7api
thought it should be. My next question is where is this structure defined
and can it be relaxed as I am receiving messages from another interface and
can't control the order of the segments?
Thank you,
Court
-----Original Message-----
From: Shrock, Court [mailto:Sh...@in...]
Sent: Thursday, October 28, 2004 10:47 AM
To: 'hl7...@li...'
Subject: [HAPI-devel] Peculiar parse of a valid HL7 message in TestPanel
When using the HL7 message below, the TestPanel parses the message with 2
DG1 segments, the first being an empty node and the second containing the
actual data. This is curious because a call to terser.get("/DG1-2") and
terser.get("/DG1-4") return nothing wi! th this particular message. I have
noticed that is doesn't just happen with the DG1 segments either. I've seen
happen with the PV1 segments as well.
Any ideas/leads from an experienced hand?
Thanks,
Court
MSH|^~\\\\&|ADM|SHM|ALL|ALL|200410271610||ADT^A05|ADM-HUB.1.48134|D|2.1
EVN|A05||||TWB
PID|1|Z4935|Z000004983||TESTSHM^TWB^^^^|NINETYNINE,AGENT|19621212|M|DANG
PID|1|Z4935|Z000004983||ER^N
ICK^^^^|1|7856 W EAST^^SPOKANE^WA^99208|SPO-WA|509 789-0978|509
474-3131||D|AG|Z00006154|890-23-4568
NK1|1|NOK MOM |MO|4523 N SOUTH^^SPOKANE^WA^99205|890 123-4568
PV1|1|P|Z.7S^^|EL|||MABRO^Mabunga^Rogelio^^^^|NADDA^Nadig^Daniel^^^^||ME
PV1|1|P|DN||
||A|||LABSY^Labes^Sylvia^^^^|IN||MSCV|||||||||||||||||||SHM||PRE|||20041
||A|||0281
610
IN1|1|MSC||MSC PREMERA|PO BOX 3048^^SPOKANE^WA^99220-3048||509
536-4500|||||20041201|20091203|||TESTSHM^TWB^^^^|SP||||||||||||||||||321
536-4500|||||20041201|20091203|||6549
87|123456789
GT1|1||TESTSHM^TWB^^^^||7856 W EAST^^SPOKANE^WA^99208|509
789-0978|||||SP|890-23-4568||||SHMC|W 101 8TH, BOX TAC
F-9^^SPOKANE^WA^99220|509 474-3131||FT
DG1|1|TX||test a23
ZV1|^^^^|AALSUE^Aalgard^Sue^^^^|DABRA^Dabalos^Rodolfo^A^^^|||||PTN^DAD^^
ZV1|^^|F
A|7531 N SOUTH^^SPOKANE^WA^99203|758 632-4512|TESTER|TESTER|SACRED HEART
MEDICAL CENTER|W 101 8TH, BOX TAC F-9^^SPOKANE^WA^99220
-------------------------------------------------------
This Newsletter Sponsored by: Macrovision
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
_______________________________________________
Hl7api-devel mailing list
Hl7...@li...
https://lists.sourceforge.net/lists/listinfo/hl7api-devel
-------------------------------------------------------
This Newsletter Sponsored by: Macrovision
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
_______________________________________________
Hl7api-devel mailing list
Hl7...@li...
https://lists.sourceforge.net/lists/listinfo/hl7api-devel
|
|
From: <ni...@sk...> - 2004-10-28 18:58:26
|
Hi Court, I don't have the documentation of HL7 v2.1 but I'm afraid that your message is not correct. Normally you can only have 1 PID segment and 1 PV1 segment in a A05 message (at least in v2.5). I think that's the cause of the strange behaviour of HAPI... Best Regards Nico I found that in this particular case, the order of the segments matters. The DG1 segment was being recognized were is existed in the message, but a placeholder was being put immediately following the PV1 segment where hl7api thought it should be. My next question is where is this structure defined and can it be relaxed as I am receiving messages from another interface and can't control the order of the segments? Thank you, Court -----Original Message----- From: Shrock, Court [mailto:Sh...@in...] Sent: Thursday, October 28, 2004 10:47 AM To: 'hl7...@li...' Subject: [HAPI-devel] Peculiar parse of a valid HL7 message in TestPanel When using the HL7 message below, the TestPanel parses the message with 2 DG1 segments, the first being an empty node and the second containing the actual data. This is curious because a call to terser.get(\"/DG1-2\") and terser.get(\"/DG1-4\") return nothing with this particular message. I have noticed that is doesn't just happen with the DG1 segments either. I've seen happen with the PV1 segments as well. Any ideas/leads from an experienced hand? Thanks, Court MSH|^~\\\\&|ADM|SHM|ALL|ALL|200410271610||ADT^A05|ADM-HUB.1.48134|D|2.1 EVN|A05||||TWB PID|1|Z4935|Z000004983||TESTSHM^TWB^^^^|NINETYNINE,AGENT|19621212|M|DANG PID|1|Z4935|Z000004983||ER^N ICK^^^^|1|7856 W EAST^^SPOKANE^WA^99208|SPO-WA|509 789-0978|509 474-3131||D|AG|Z00006154|890-23-4568 NK1|1|NOK MOM |MO|4523 N SOUTH^^SPOKANE^WA^99205|890 123-4568 PV1|1|P|Z.7S^^|EL|||MABRO^Mabunga^Rogelio^^^^|NADDA^Nadig^Daniel^^^^||ME PV1|1|P|DN|| ||A|||LABSY^Labes^Sylvia^^^^|IN||MSCV|||||||||||||||||||SHM||PRE|||20041 ||A|||0281 610 IN1|1|MSC||MSC PREMERA|PO BOX 3048^^SPOKANE^WA^99220-3048||509 536-4500|||||20041201|20091203|||TESTSHM^TWB^^^^|SP||||||||||||||||||321 536-4500|||||20041201|20091203|||6549 87|123456789 GT1|1||TESTSHM^TWB^^^^||7856 W EAST^^SPOKANE^WA^99208|509 789-0978|||||SP|890-23-4568||||SHMC|W 101 8TH, BOX TAC F-9^^SPOKANE^WA^99220|509 474-3131||FT DG1|1|TX||test a23 ZV1|^^^^|AALSUE^Aalgard^Sue^^^^|DABRA^Dabalos^Rodolfo^A^^^|||||PTN^DAD^^ ZV1|^^|F A|7531 N SOUTH^^SPOKANE^WA^99203|758 632-4512|TESTER|TESTER|SACRED HEART MEDICAL CENTER|W 101 8TH, BOX TAC F-9^^SPOKANE^WA^99220 ------------------------------------------------------- This Newsletter Sponsored by: Macrovision For reliable Linux application installations, use the industry's leading setup authoring tool, InstallShield X. Learn more and evaluate today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/ _______________________________________________ Hl7api-devel mailing list Hl7...@li... https://lists.sourceforge.net/lists/listinfo/hl7api-devel ------------------------------------------------------- This Newsletter Sponsored by: Macrovision For reliable Linux application installations, use the industry's leading setup authoring tool, InstallShield X. Learn more and evaluate today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/ _______________________________________________ Hl7api-devel mailing list Hl7...@li... https://lists.sourceforge.net/lists/listinfo/hl7api-devel |
|
From: <ni...@sk...> - 2004-10-28 18:57:52
|
Hi Court, I don't have the documentation of HL7 v2.1 but I'm afraid that your message is not correct. Normally you can only have 1 PID segment and 1 PV1 segment in a A05 message (at least in v2.5). I think that's the cause of the strange behaviour of HAPI... Best Regards Nico I found that in this particular case, the order of the segments matters. The DG1 segment was being recognized were is existed in the message, but a placeholder was being put immediately following the PV1 segment where hl7api thought it should be. My next question is where is this structure defined and can it be relaxed as I am receiving messages from another interface and can't control the order of the segments? Thank you, Court -----Original Message----- From: Shrock, Court [mailto:Sh...@in...] Sent: Thursday, October 28, 2004 10:47 AM To: 'hl7...@li...' Subject: [HAPI-devel] Peculiar parse of a valid HL7 message in TestPanel When using the HL7 message below, the TestPanel parses the message with 2 DG1 segments, the first being an empty node and the second containing the actual data. This is curious because a call to terser.get(\"/DG1-2\") and terser.get(\"/DG1-4\") return nothing with this particular message. I have noticed that is doesn't just happen with the DG1 segments either. I've seen happen with the PV1 segments as well. Any ideas/leads from an experienced hand? Thanks, Court MSH|^~\\\\&|ADM|SHM|ALL|ALL|200410271610||ADT^A05|ADM-HUB.1.48134|D|2.1 EVN|A05||||TWB PID|1|Z4935|Z000004983||TESTSHM^TWB^^^^|NINETYNINE,AGENT|19621212|M|DANG PID|1|Z4935|Z000004983||ER^N ICK^^^^|1|7856 W EAST^^SPOKANE^WA^99208|SPO-WA|509 789-0978|509 474-3131||D|AG|Z00006154|890-23-4568 NK1|1|NOK MOM |MO|4523 N SOUTH^^SPOKANE^WA^99205|890 123-4568 PV1|1|P|Z.7S^^|EL|||MABRO^Mabunga^Rogelio^^^^|NADDA^Nadig^Daniel^^^^||ME PV1|1|P|DN|| ||A|||LABSY^Labes^Sylvia^^^^|IN||MSCV|||||||||||||||||||SHM||PRE|||20041 ||A|||0281 610 IN1|1|MSC||MSC PREMERA|PO BOX 3048^^SPOKANE^WA^99220-3048||509 536-4500|||||20041201|20091203|||TESTSHM^TWB^^^^|SP||||||||||||||||||321 536-4500|||||20041201|20091203|||6549 87|123456789 GT1|1||TESTSHM^TWB^^^^||7856 W EAST^^SPOKANE^WA^99208|509 789-0978|||||SP|890-23-4568||||SHMC|W 101 8TH, BOX TAC F-9^^SPOKANE^WA^99220|509 474-3131||FT DG1|1|TX||test a23 ZV1|^^^^|AALSUE^Aalgard^Sue^^^^|DABRA^Dabalos^Rodolfo^A^^^|||||PTN^DAD^^ ZV1|^^|F A|7531 N SOUTH^^SPOKANE^WA^99203|758 632-4512|TESTER|TESTER|SACRED HEART MEDICAL CENTER|W 101 8TH, BOX TAC F-9^^SPOKANE^WA^99220 ------------------------------------------------------- This Newsletter Sponsored by: Macrovision For reliable Linux application installations, use the industry's leading setup authoring tool, InstallShield X. Learn more and evaluate today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/ _______________________________________________ Hl7api-devel mailing list Hl7...@li... https://lists.sourceforge.net/lists/listinfo/hl7api-devel ------------------------------------------------------- This Newsletter Sponsored by: Macrovision For reliable Linux application installations, use the industry's leading setup authoring tool, InstallShield X. Learn more and evaluate today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/ _______________________________________________ Hl7api-devel mailing list Hl7...@li... https://lists.sourceforge.net/lists/listinfo/hl7api-devel |
|
From: Shrock, C. <Sh...@in...> - 2004-10-28 17:51:12
|
I found that in this particular case, the order of the segments matters.
The DG1 segment was being recognized were is existed in the message, but a
placeholder was being put immediately following the PV1 segment where hl7api
thought it should be. My next question is where is this structure defined
and can it be relaxed as I am receiving messages from another interface and
can't control the order of the segments?
Thank you,
Court
-----Original Message-----
From: Shrock, Court [mailto:Sh...@in...]
Sent: Thursday, October 28, 2004 10:47 AM
To: 'hl7...@li...'
Subject: [HAPI-devel] Peculiar parse of a valid HL7 message in TestPanel
When using the HL7 message below, the TestPanel parses the message with 2
DG1 segments, the first being an empty node and the second containing the
actual data. This is curious because a call to terser.get("/DG1-2") and
terser.get("/DG1-4") return nothing with this particular message. I have
noticed that is doesn't just happen with the DG1 segments either. I've seen
happen with the PV1 segments as well.
Any ideas/leads from an experienced hand?
Thanks,
Court
MSH|^~\&|ADM|SHM|ALL|ALL|200410271610||ADT^A05|ADM-HUB.1.48134|D|2.1
EVN|A05||||TWB
PID|1|Z4935|Z000004983||TESTSHM^TWB^^^^|NINETYNINE,AGENT|19621212|M|DANG
PID|1|Z4935|Z000004983||ER^N
ICK^^^^|1|7856 W EAST^^SPOKANE^WA^99208|SPO-WA|509 789-0978|509
474-3131||D|AG|Z00006154|890-23-4568
NK1|1|NOK MOM |MO|4523 N SOUTH^^SPOKANE^WA^99205|890 123-4568
PV1|1|P|Z.7S^^|EL|||MABRO^Mabunga^Rogelio^^^^|NADDA^Nadig^Daniel^^^^||ME
PV1|1|P|DN||
||A|||LABSY^Labes^Sylvia^^^^|IN||MSCV|||||||||||||||||||SHM||PRE|||20041
||A|||0281
610
IN1|1|MSC||MSC PREMERA|PO BOX 3048^^SPOKANE^WA^99220-3048||509
536-4500|||||20041201|20091203|||TESTSHM^TWB^^^^|SP||||||||||||||||||321
536-4500|||||20041201|20091203|||6549
87|123456789
GT1|1||TESTSHM^TWB^^^^||7856 W EAST^^SPOKANE^WA^99208|509
789-0978|||||SP|890-23-4568||||SHMC|W 101 8TH, BOX TAC
F-9^^SPOKANE^WA^99220|509 474-3131||FT
DG1|1|TX||test a23
ZV1|^^^^|AALSUE^Aalgard^Sue^^^^|DABRA^Dabalos^Rodolfo^A^^^|||||PTN^DAD^^
ZV1|^^|F
A|7531 N SOUTH^^SPOKANE^WA^99203|758 632-4512|TESTER|TESTER|SACRED HEART
MEDICAL CENTER|W 101 8TH, BOX TAC F-9^^SPOKANE^WA^99220
-------------------------------------------------------
This Newsletter Sponsored by: Macrovision
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
_______________________________________________
Hl7api-devel mailing list
Hl7...@li...
https://lists.sourceforge.net/lists/listinfo/hl7api-devel
|
|
From: Shrock, C. <Sh...@in...> - 2004-10-28 17:46:43
|
When using the HL7 message below, the TestPanel parses the message with 2
DG1 segments, the first being an empty node and the second containing the
actual data. This is curious because a call to terser.get("/DG1-2") and
terser.get("/DG1-4") return nothing with this particular message. I have
noticed that is doesn't just happen with the DG1 segments either. I've seen
happen with the PV1 segments as well.
Any ideas/leads from an experienced hand?
Thanks,
Court
MSH|^~\&|ADM|SHM|ALL|ALL|200410271610||ADT^A05|ADM-HUB.1.48134|D|2.1
EVN|A05||||TWB
PID|1|Z4935|Z000004983||TESTSHM^TWB^^^^|NINETYNINE,AGENT|19621212|M|DANGER^N
ICK^^^^|1|7856 W EAST^^SPOKANE^WA^99208|SPO-WA|509 789-0978|509
474-3131||D|AG|Z00006154|890-23-4568
NK1|1|NOK MOM |MO|4523 N SOUTH^^SPOKANE^WA^99205|890 123-4568
PV1|1|P|Z.7S^^|EL|||MABRO^Mabunga^Rogelio^^^^|NADDA^Nadig^Daniel^^^^||MEDN||
||A|||LABSY^Labes^Sylvia^^^^|IN||MSCV|||||||||||||||||||SHM||PRE|||200410281
610
IN1|1|MSC||MSC PREMERA|PO BOX 3048^^SPOKANE^WA^99220-3048||509
536-4500|||||20041201|20091203|||TESTSHM^TWB^^^^|SP||||||||||||||||||3216549
87|123456789
GT1|1||TESTSHM^TWB^^^^||7856 W EAST^^SPOKANE^WA^99208|509
789-0978|||||SP|890-23-4568||||SHMC|W 101 8TH, BOX TAC
F-9^^SPOKANE^WA^99220|509 474-3131||FT
DG1|1|TX||test a23
ZV1|^^^^|AALSUE^Aalgard^Sue^^^^|DABRA^Dabalos^Rodolfo^A^^^|||||PTN^DAD^^^^|F
A|7531 N SOUTH^^SPOKANE^WA^99203|758 632-4512|TESTER|TESTER|SACRED HEART
MEDICAL CENTER|W 101 8TH, BOX TAC F-9^^SPOKANE^WA^99220
|
|
From: Tripp, B. <Bry...@uh...> - 2004-10-06 14:16:18
|
Hi H=FCseyin,=20 I think the MsgStructID attribute of HL7v2xStaticDef has to be changed = to "ORU_R01". Could you try that and let me know if there are further probelems? =20 Thanks,=20 Bryan=20 > -----Original Message----- > From: H=FCseyin Kartal [mailto:h.k...@ya...] > Sent: October 6, 2004 8:40 AM > To: hl7...@li... > Subject: [HAPI-devel] Support for ConfGen Parser >=20 >=20 > hello dear hapi team, >=20 > we want to use in our company your hl7api. >=20 > My current system: > Eclipse IDE > Hapi 0.5beta form cvs HEAD Branch > Messaging Workbench 1.6.2 >=20 >=20 > i used the mwb to edit the hl7 conformace and generate hl7 registry > profiles. >=20 > at the moment i only have one hl7 message defined which=20 > registry profile is > in the attachment of this mail. >=20 > i want to use the profile compiler to generate the h7 code=20 > and i followed > the steps described in the tutorial. > http://hl7api.sourceforge.net/conf/compiler_manual/index.htm >=20 > i done the procedure 1 of the tutorial, but i can=B4t solve procedure = 2 >=20 > in the tutorial the start process is decribed like > java -classpath conf.jar ConfGen [flags] {source} {dest} > {package-name} >=20 > i start the project direct form the ide like > ca.uhn.hl7v2.conf.classes.generator.builders.ConfGen -v > "D:\eclipse\workspace\hapi\MEDOS\Medos-ORU_R01_ORD CNTRL.xml" = ./MEDOS/ > ./MEDOS >=20 > The output looks like >=20 > ./MEDOS/ > ConfGen: verbose display enabled > Generating Source... > ConformanceError: > ca.uhn.hl7v2.conf.classes.exceptions.ConformanceError:=20 > Underlying > class/method ca.uhn.hl7v2.model.v23.message.ORU.getMSH() can=20 > not be found. > The complete HAPI API must be installed prior to using this system. >=20 > Done. >=20 > If i start the confgen with test options like > ca.uhn.hl7v2.conf.classes.generator.builders.ConfGen -t >=20 > The output looks like > ./MEDOS/ > ConfGen: system test enabled > Checking for XML Parser: PASS > Checking for Xerces: PASS > Checking for Conformance Classes: PASS > Checking for Apache Ant: PASS >=20 >=20 > I don=B4t know what to do. >=20 > Please help... >=20 This e-mail may contain confidential and/or privileged information for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this e-mail in error, please contact = the sender and delete all copies. Opinions, conclusions or other information contained = in this e-mail may not be that of the organization. |
|
From: <h.k...@ya...> - 2004-10-06 12:39:51
|
hello dear hapi team, we want to use in our company your hl7api. My current system: Eclipse IDE Hapi 0.5beta form cvs HEAD Branch Messaging Workbench 1.6.2 i used the mwb to edit the hl7 conformace and generate hl7 registry profiles. at the moment i only have one hl7 message defined which registry profile = is in the attachment of this mail. i want to use the profile compiler to generate the h7 code and i = followed the steps described in the tutorial. http://hl7api.sourceforge.net/conf/compiler_manual/index.htm i done the procedure 1 of the tutorial, but i can=B4t solve procedure 2 in the tutorial the start process is decribed like java =96classpath conf.jar ConfGen [flags] {source} {dest} {package-name} i start the project direct form the ide like ca.uhn.hl7v2.conf.classes.generator.builders.ConfGen -v "D:\eclipse\workspace\hapi\MEDOS\Medos-ORU_R01_ORD CNTRL.xml" ./MEDOS/ ./MEDOS The output looks like ./MEDOS/ ConfGen: verbose display enabled Generating Source... ConformanceError: ca.uhn.hl7v2.conf.classes.exceptions.ConformanceError: Underlying class/method ca.uhn.hl7v2.model.v23.message.ORU.getMSH() can not be = found. The complete HAPI API must be installed prior to using this system. Done. If i start the confgen with test options like ca.uhn.hl7v2.conf.classes.generator.builders.ConfGen -t The output looks like ./MEDOS/ ConfGen: system test enabled Checking for XML Parser: PASS Checking for Xerces: PASS Checking for Conformance Classes: PASS Checking for Apache Ant: PASS I don=B4t know what to do. Please help... |
|
From: Tripp, B. <Bry...@uh...> - 2004-09-20 17:07:26
|
Yes, no problem. ASCII was used because that's what the standard = specifies, but I agree it should be flexible. =20 =20 Bryan=20 -----Original Message----- From: ni...@sk... [mailto:ni...@sk...] Sent: September 18, 2004 9:05 AM To: hl7...@li... Subject: [HAPI-devel] MinLLPReader/MinLLPWriter - ASCII/ISO-8859-1 Hi Bryan, =20 Please correct me if I'm wrong, but I think that in the current version = when a message is sent over a socket it's always encoded as ASCII. =20 Due to this ascii encoding the binary distribution of HAPI (without modifications) can't be used in parts of Europe (France, Belgium, = Germany, ...) since the characters =E9=E0=E7=EB are sent as ?=20 =20 Could you forsee a parameter/property or - even better - a kind of = default map that looks at the regional settings of your pc and chooses = ISO-8859-1 instead of ASCII for these countries ? =20 Thanks a lot! =20 Best Regards =20 Nico This e-mail may contain confidential and/or privileged information for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this e-mail in error, please contact = the sender and delete all copies. Opinions, conclusions or other information contained = in this e-mail may not be that of the organization. |
|
From: <ni...@sk...> - 2004-09-18 13:05:36
|
Hi Bryan, Please correct me if I'm wrong, but I think that in the current version w= hen a message is sent over a socket it's always encoded as ASCII. Due to this ascii encoding the binary distribution of HAPI (without modif= ications) can't be used in parts of Europe (France, Belgium, Germany, ...= ) since the characters =E9=E0=E7=EB are sent as ?=20 Could you forsee a parameter/property or - even better - a kind of defaul= t map that looks at the regional settings of your pc and chooses ISO-8859= -1 instead of ASCII for these countries ? Thanks a lot! Best Regards Nico |
|
From: Aaron B. <ab...@au...> - 2004-09-13 23:44:08
|
I'm developing an application for a diagnostic imaging office to receive an HL7 message containing patient data and then insert that data into an MS SQL Server database. I was wondering if anyone has seen an app using HAPI that already does this. It seems like such a generic feature I might be able to use the source of another application as a starting point. =20 Any suggestions would be appreciated. =20 =20 Aaron Bronow AutoScan, Inc. |
|
From: Tripp, B. <Bry...@uh...> - 2004-08-24 22:40:52
|
Hi Archie, Sorry about the bugs, and thanks for letting us know. I'll look into the looping problem further. Unfortunately I'll be unavailable for the next two weeks. If any one else wants to look at it, it sounds like MessageIterator is creating a spot for the unexpected segment but then not recognizing that spot as being suitable. Regarding the other problem, it doesn't make sense to try to XML encode messages of unknown structure (with HAPI or otherwise), so you're right that HAPI should just quit. I'll change this for the next release. GenericMessage is used when MSH-9 is not valued, or is valued with something for which there is no corresponding message class on the classpath. Regards, Bryan -----Original Message----- From: Archie Cobbs To: hl7...@li... Sent: 24/08/2004 5:54 PM Subject: Re: [HAPI-devel] Bugs encountered in 0.4.2 Archie Cobbs wrote: > > I've just upgraded to 0.4.2 and am encountering some problems. > > I've also just switched to a new HL7 feed so some of these problems > > may be related to that switch as well. > > > > #1: Infinite loops > > > > I'm receiving some ADT^A24 messages that seem to contain > > no PID segments (which is wrong I think). In any case, they > > send the HL7 server into an infinite loop when it tries to > > parse them! See log trace below. Oddly, when I cut & paste > > the same message into the Message Tester Swing app, it seems > > to parse it fine. > > Oops, correction: the ADT^A24 is properly formatted and does > contain the required PID segments. I was missing the latter half > of the message with cut&paste because of the carriage returns > without linefeeds. > > Also, the Message Tester Swing app goes into an infinite loop > (ie., hangs) also when trying to parse this message. > > I've attached a sanitized version below of a message that causes > this loop. FYI, ..continuing my conversation with myself... :-) This bug seems to be triggered by the fact that this message specifies that it is version "2.2" but actually contains a 2.3 segment, PD1. In any case, as a stopgap I've added the patch below to work around the problem. -Archie ________________________________________________________________________ __ Archie Cobbs * CTO, Awarix * http://www.awarix.com diff -ur /home/archie/hapi/hapi-0.4.2/src/ca/uhn/hl7v2/model/AbstractGroup.java ./ca/uhn/hl7v2/model/AbstractGroup.java --- /home/archie/hapi/hapi-0.4.2/src/ca/uhn/hl7v2/model/AbstractGroup.java 2004-08-24 12:25:07.000000000 -0500 +++ ./ca/uhn/hl7v2/model/AbstractGroup.java 2004-08-24 16:48:12.000000000 -0500 @@ -140,6 +140,17 @@ if (version == null) throw new HL7Exception("Need message version to add segment by name; message.getVersion() returns null"); Class c = ca.uhn.hl7v2.parser.Parser.findSegmentClass(name, version); + + // Hack to try the next version if segment not found in this version + if (c == null) { + String[] vlist = new String[] { "2.1", "2.2", "2.3", "2.3.1", "2.4", "2.5" }; + for (int i = 0; i < vlist.length - 1; i++) { + if (version.equals(vlist[i])) { + c = ca.uhn.hl7v2.parser.Parser.findSegmentClass(name, vlist[i + 1]); + break; + } + } + } if (c == null) c = GenericSegment.class; ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Hl7api-devel mailing list Hl7...@li... https://lists.sourceforge.net/lists/listinfo/hl7api-devel This e-mail may contain confidential and/or privileged information for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this e-mail in error, please contact the sender and delete all copies. Opinions, conclusions or other information contained in this e-mail may not be that of the organization. |
|
From: Archie C. <ar...@de...> - 2004-08-24 22:00:16
|
Archie Cobbs wrote: > > I've just upgraded to 0.4.2 and am encountering some problems. > > I've also just switched to a new HL7 feed so some of these problems > > may be related to that switch as well. > > > > #1: Infinite loops > > > > I'm receiving some ADT^A24 messages that seem to contain > > no PID segments (which is wrong I think). In any case, they > > send the HL7 server into an infinite loop when it tries to > > parse them! See log trace below. Oddly, when I cut & paste > > the same message into the Message Tester Swing app, it seems > > to parse it fine. > > Oops, correction: the ADT^A24 is properly formatted and does > contain the required PID segments. I was missing the latter half > of the message with cut&paste because of the carriage returns > without linefeeds. > > Also, the Message Tester Swing app goes into an infinite loop > (ie., hangs) also when trying to parse this message. > > I've attached a sanitized version below of a message that causes > this loop. FYI, ..continuing my conversation with myself... :-) This bug seems to be triggered by the fact that this message specifies that it is version "2.2" but actually contains a 2.3 segment, PD1. In any case, as a stopgap I've added the patch below to work around the problem. -Archie __________________________________________________________________________ Archie Cobbs * CTO, Awarix * http://www.awarix.com diff -ur /home/archie/hapi/hapi-0.4.2/src/ca/uhn/hl7v2/model/AbstractGroup.java ./ca/uhn/hl7v2/model/AbstractGroup.java --- /home/archie/hapi/hapi-0.4.2/src/ca/uhn/hl7v2/model/AbstractGroup.java 2004-08-24 12:25:07.000000000 -0500 +++ ./ca/uhn/hl7v2/model/AbstractGroup.java 2004-08-24 16:48:12.000000000 -0500 @@ -140,6 +140,17 @@ if (version == null) throw new HL7Exception("Need message version to add segment by name; message.getVersion() returns null"); Class c = ca.uhn.hl7v2.parser.Parser.findSegmentClass(name, version); + + // Hack to try the next version if segment not found in this version + if (c == null) { + String[] vlist = new String[] { "2.1", "2.2", "2.3", "2.3.1", "2.4", "2.5" }; + for (int i = 0; i < vlist.length - 1; i++) { + if (version.equals(vlist[i])) { + c = ca.uhn.hl7v2.parser.Parser.findSegmentClass(name, vlist[i + 1]); + break; + } + } + } if (c == null) c = GenericSegment.class; |
|
From: Archie C. <ar...@de...> - 2004-08-24 17:55:26
|
Archie Cobbs wrote: > I've just upgraded to 0.4.2 and am encountering some problems. > I've also just switched to a new HL7 feed so some of these problems > may be related to that switch as well. > > #1: Infinite loops > > I'm receiving some ADT^A24 messages that seem to contain > no PID segments (which is wrong I think). In any case, they > send the HL7 server into an infinite loop when it tries to > parse them! See log trace below. Oddly, when I cut & paste > the same message into the Message Tester Swing app, it seems > to parse it fine. Oops, correction: the ADT^A24 is properly formatted and does contain the required PID segments. I was missing the latter half of the message with cut&paste because of the carriage returns without linefeeds. Also, the Message Tester Swing app goes into an infinite loop (ie., hangs) also when trying to parse this message. I've attached a sanitized version below of a message that causes this loop. -Archie __________________________________________________________________________ Archie Cobbs * CTO, Awarix * http://www.awarix.com MSH|^~\&|ST01|S|IM|S|20040824090059||ADT^A24|177588|P|2.2|177588||AL|||||||2.2b EVN|A24|20040824090059|||ADS PID|1|HNE1111111111^^^NE^PE|~11111111^^^ST01^PI||XXXXXXX^XXXXX^""^""||11111111|M||1|11 MAIN STREET #11^^SOMECITYX^AL^12345^USA^P^AL111||(111)111-1111|(111)111-1111|E^ENGLISH^HL11111^E^ENGLISH^111111|M|CHR||111-11-1111|||||N|||N|||N|N|||||||||||||||||||N PD1||||||||||||||514^CHR NO CHURCH SPECIFIED^99CHR PV1|1|P|""|3|||111111^XXXXXX^XXXXXXX^""^^^MD^HL11111||""|PAI||||1|||111111^XXXXXX^XXXXXXX^""^^^MD^HL11111|OSS||L|||||||||||||||||||S||0|||123123123123||||||1231231231^^^ST01S^TN PID|2||123123123123^^^ST01S^MR||XXXXXXX^XXXXX^""^""||11111111|M||1|11 MAIN STREED #11^^SOMECITYX^AL^12345^USA^P^AL115||(111)111-1111|(111)111-1111|E^ENGLISH^HL11111^E^ENGLISH^99CLAN|M|CHR||111-11-1111|||||N|||N|||N|N|||||||||||||||||||N PD1||||||||||||||514^CHR NO CHURCH SPECIFIED^99CHR PV1|2|P|""|3|||111111^XXXXXX^XXXXXXX^""^^^MD^HL11111||""|PAI||||1|||111111^XXXXXX^XXXXXXX^""^^^MD^HL11111|OSS||L|||||||||||||||||||S||0|||111111111111||||||1111111111^^^ST01S^TN |
|
From: Archie C. <ar...@de...> - 2004-08-24 17:30:27
|
Hi,
I've just upgraded to 0.4.2 and am encountering some problems.
I've also just switched to a new HL7 feed so some of these problems
may be related to that switch as well.
#1: Infinite loops
I'm receiving some ADT^A24 messages that seem to contain
no PID segments (which is wrong I think). In any case, they
send the HL7 server into an infinite loop when it tries to
parse them! See log trace below. Oddly, when I cut & paste
the same message into the Message Tester Swing app, it seems
to parse it fine.
#2: GenericMessage -> XML?
Some HL7 messages that aren't fully recognized (?) by HAPI will
parse into "ca.uhn.hl7v2.model.GenericMessage$V22" objects.
When converting to XML, I get this:
org.w3c.dom.DOMException: INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified
...
ca.uhn.hl7v2.parser.DefaultXMLParser.encodeDocument(DefaultXMLParser.java:61)
...
because it's trying to create an XML tag with the name "GenericMessage$V22"
which is illegal because of the "$" character.
So is the bug that we just need to use a different name, or is it
wrong for me to be trying to XML encode a "GenericMessage$V22"
in the first place?
In the latter case, should HAPI not even bother trying, and instead
preemtively throw some other more informative exception when
DefaultXMLParser.encodeDocument() is called with such a message?
Any insights greatly appreciated.
-Archie
__________________________________________________________________________
Archie Cobbs * CTO, Awarix * http://www.awarix.com
...
[java] [Thread-6] DEBUG - Parsing segment PID
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PV13(0) for
PID? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PID
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PID
[java] [Thread-6] DEBUG - Loaded: ca.uhn.hl7v2.model.v22.segment.PID class: class ca.uhn.hl7v2.model.v22.segment.PID
[java] [Thread-6] DEBUG - 1reps delimited by: ~
[java] [Thread-6] DEBUG - Parsing field 1 repetition 0
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 1reps delimited by: ~
[java] [Thread-6] DEBUG - Parsing field 3 repetition 0
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 1reps delimited by: ~
[java] [Thread-6] DEBUG - Parsing field 5 repetition 0
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 1reps delimited by: ~
[java] [Thread-6] DEBUG - Parsing field 7 repetition 0
[java] [Thread-6] DEBUG - 1reps delimited by: ~
[java] [Thread-6] DEBUG - Parsing field 8 repetition 0
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 1reps delimited by: ~
[java] [Thread-6] DEBUG - Parsing field 10 repetition 0
[java] [Thread-6] DEBUG - 1reps delimited by: ~
[java] [Thread-6] DEBUG - Parsing field 11 repetition 0
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 1reps delimited by: ~
[java] [Thread-6] DEBUG - Parsing field 13 repetition 0
[java] [Thread-6] DEBUG - 1reps delimited by: ~
[java] [Thread-6] DEBUG - Parsing field 14 repetition 0
[java] [Thread-6] DEBUG - 1reps delimited by: ~
[java] [Thread-6] DEBUG - Parsing field 15 repetition 0
[java] [Thread-6] DEBUG - 1reps delimited by: ~
[java] [Thread-6] DEBUG - Parsing field 16 repetition 0
[java] [Thread-6] DEBUG - 1reps delimited by: ~
[java] [Thread-6] DEBUG - Parsing field 17 repetition 0
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 1reps delimited by: ~
[java] [Thread-6] DEBUG - Parsing field 19 repetition 0
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 1reps delimited by: ~
[java] [Thread-6] DEBUG - Parsing field 24 repetition 0
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 1reps delimited by: ~
[java] [Thread-6] DEBUG - Parsing field 27 repetition 0
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 1reps delimited by: ~
[java] [Thread-6] DEBUG - Parsing field 30 repetition 0
[java] [Thread-6] DEBUG - 1reps delimited by: ~
[java] [Thread-6] DEBUG - Parsing field 31 repetition 0
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 0reps delimited by: ~
[java] [Thread-6] DEBUG - 1reps delimited by: ~
[java] [Thread-6] DEBUG - Parsing field 50 repetition 0
[java] [Thread-6] DEBUG - Parsing segment PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PID3(0) for
PD1? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PD1
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PD12(0) for
PD1? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PD1
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PD13(0) for
PD1? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PD1
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PD14(0) for
PD1? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PD1
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PD15(0) for
PD1? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PD1
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PD16(0) for
PD1? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PD1
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PD17(0) for
PD1? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PD1
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PD18(0) for
PD1? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PD1
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PD19(0) for
PD1? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PD1
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PD110(0) for PD1? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PD1
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PD111(0) for PD1? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PD1
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PD112(0) for PD1? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PD1
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PD113(0) for PD1? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PD1
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PD114(0) for PD1? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PD1
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PD115(0) for PD1? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PD1
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PD116(0) for PD1? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PD1
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PD117(0) for PD1? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PD1
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PD118(0) for PD1? false
[java] [Thread-6] INFO - MessageIterator creating new segment: PD1
[java] [Thread-6] DEBUG - Trying to load: ca.uhn.hl7v2.model.v22.segment.PD1
[java] [Thread-6] DEBUG - Match exists after position ADT_A24:PD119(0) for PD1? false
... ad infinitum ...
|
|
From: Kelley, P. (HEALTH) <pet...@he...> - 2004-08-18 23:15:45
|
I don't know about a prepackaged solution but it wouldn't be too hard to put something together using the classes from the demonstration application in HAPI. Have a look at the following code to see what I mean: The processMessage() method in TestApplication and DefaultApplication to see how ACK messages are constructed and sent The run() method on Receiver to see how to obtain the text of the message. These are the examples I have been able to find quickly, others may want to comment on better places to look. In the code we have written we are actually using some of the example classes to provide the functionality we need. -----Original Message----- From: Lothar Frank [mailto:l....@ze...] Sent: Wednesday, 18 August 2004 19:05 To: hl7...@li... Subject: [HAPI-devel] newbi Hello List, i am total newbi concerning java and applications in java. According to that I need only a very small solution maybe anybody knows were I can find it: I need a HL7 intranet connection which enables that every hl7 message is simply archived in a file in that moment when the message comes in. and after saving this message to file it should send a ACK to the remote server. Is there already a solution programmed what I could use for that?? THX for a reply Lothar |
|
From: Lothar F. <l....@ze...> - 2004-08-18 09:35:07
|
Hello List, i am total newbi concerning java and applications in java. According to that I need only a very small solution maybe anybody knows were I can find it: I need a HL7 intranet connection which enables that every hl7 message is simply archived in a file in that moment when the message comes in. and after saving this message to file it should send a ACK to the remote server. Is there already a solution programmed what I could use for that?? THX for a reply Lothar |
|
From: <elm...@t-...> - 2004-08-12 10:34:08
|
Hello, my question probably sounds stupid. As I took up the duty to lead one of the NGOs in Berlin I lost the focus on HAPI and Java for a while. Somebody who is interested in using HAPI asked my about support of unicode. I guess it is fully supported? A Search with google (unicode site:hl7api.sourceforge.net) only finds one hit on this topic on whole hl7api.sourceforge.net. Regards Elmar |
|
From: Tripp, B. <Bry...@uh...> - 2004-08-03 19:51:33
|
Hi,=20
Very good questions. Regarding the first, HAPI takes this redundant =
mapping
from the HL7 database. My interpretation is that the trigger may use
different structures in different situations. Messy, but I think =
that's how
it has been modelled. The solution should be to specify the desired
structure explicitly in MSH-9-3. However, there was a bug in HAPI =
(fixed
now) that prevented that from working. I can send you the fix if you =
like,
otherwise it will be in the next release.=20
About the second question ... HAPI 0.4.x is a little more picky and =
won't
create another rep of the group unless is finds the (required) ORC =
segment.
If you change the last part of the message to this:=20
ORC|NW|6^^20040305^0005^6200403050005||0500051086|||||20040305110325|mit=
||TI
ZIANA^TIZIANA^Dr^494143^U212^MC-UNITE DE MEDECINE
COMMUNAUTAIRE^857818|||||||
OBR|1|6^^20040305^0005^6200403050005||EXAM^52^K^Potassium|||200403051105=
00||
||||857818^26^3~Etude du Dr No^16^3~TEST commentaire^5^3~Fi=E8vre =
d'origine
ind=E9termin=E9e^0^3||35^sg.v^Sang
veineux|||N|N^-1008933||||||||1^R||||||||||||||||
ORC
OBR|2|6^^20040305^0005^6200403050005||EXAM^42^bilanlipid^Bilan =
lipidique
(Chol+Trig+HDL)|||20040305110500||||||857818^26^3~Etude du Dr =
No^16^3~TEST
commentaire^5^3~Fi=E8vre d'origine ind=E9termin=E9e^0^3||35^sg.v^Sang
veineux|||N|N^-1008933||||||||1^R||||||||||||||||
ORC
OBR|3|6^^20040305^0005^6200403050005||EXAM^21^creatinine^Cr=E9atinine|||=
200403
05110500||||||857818^26^3~Etude du Dr No^16^3~TEST =
commentaire^5^3~Fi=E8vre
d'origine ind=E9termin=E9e^0^3||35^sg.v^Sang
veineux|||N|N^-1008933||||||||1^R||||||||||||||||
... it will parse as expected. Without the change, HAPI thinks the =
OBRs are
locally defined segments that go at the end of the first rep of the =
group.
This is actually the only way the message could be valid (otherwise =
it's
missing required ORCs). =20
Bryan=20
> -----Original Message-----
> From: Aris JAVIER RAMOS [mailto:Ari...@hc...]
> Sent: July 30, 2004 12:02 PM
> To: hl7...@li...
> Subject: [HAPI-devel] ORM 001 parsing problems
>=20
>=20
> Bonjour,
>=20
> 1st PROBLEM :
>=20
> parsing with hapi 0.4.2 in the 2.3 version of the norm HL7.
>=20
> When parsing ORM O01 messages the parser give me back an=20
> RDO-O01 message...
>=20
> I looked at the file=20
> ca\uhn\hl7v2\parser\eventmap\2.3.properties in the hapi-0.4.2.jar
> and saw a kind of mapping like this :
> [...]
> ORM_O01 ORM_O01
> ORM_O01 OMD_O01
> ORM_O01 OMN_O01
> ORM_O01 OMS_O01
> ORM_O01 RDO_O01 <--- may be problematic ??=20
> [...]
>=20
> After a debug session I saw that the file=20
> ca\uhn\hl7v2\parser\eventmap\2.3.properties is used as a set=20
> of properties when the hapi parser determines what structure=20
> to load when a message is parsed and his structure constructed.
>=20
> The problem is that in the file=20
> ca\uhn\hl7v2\parser\eventmap\2.3.properties there are=20
> several entries for ORM_O01 messages and the one who is taken=20
> is the last one :
> [...]
> ORM_O01 ORM_O01
> ORM_O01 OMD_O01 <--- may be problematic ??
> ORM_O01 OMN_O01 <--- may be problematic ??
> ORM_O01 OMS_O01 <--- may be problematic ??
> ORM_O01 RDO_O01 <--- may be problematic ??
> [...]
> The 2.4.properties seems to be OK as I saw only one mapping=20
> for ORM_O01:
> [...]
> ORM_O01 ORM_O01
> [...]
>=20
> Is this, what we are specting from the parser ??
> if yes how can I do to obtain an ORM_O01 message ??
>=20
> 2nd PROBLEM :
>=20
> I tryed to change the 2.3.properties to have one mapping=20
> ORM_O01 ORM_O01 and it worked well.
> But I obtained a different data organization that I obtained=20
> parsing with 0.3 hapi parser.
>=20
> data :=20
>=20
> MSH|^~\&|REQUETE|6^CL|UNILAB||20040305110331||ORM^O01|REQUETE-
> 6-1078481010|T|2.3|||||||
> PID|1||2004817||DERONT^Lisette||19400101|F|||^3 rue=20
> dancet^Geneve^1205^^CH|||||||||||||||||||N
> PV1|1|H|NEUROL.^^2-FL^2-FL^H.C.U. - G E N E V E^H.U.G. -=20
> HOPITAL=20
> CANTONAL^53401^^6421||||TIZIANA^TIZIANA^Dr^494143^U212^MC-UNIT
> E DE MEDECINE=20
> COMMUNAUTAIRE^857818||||||||||||01.1008933|3||||||||||||||||||
> ||||||20040115|20040212|||||||
> ORC|NW|6^^20040305^0005^6200403050005||0500051086|||||20040305
> 110325|mit||TIZIANA^TIZIANA^Dr^494143^U212^MC-UNITE DE=20
> MEDECINE COMMUNAUTAIRE^857818||2-FL^53401^^6421|||||
> OBR|1|6^^20040305^0005^6200403050005||EXAM^52^K^Potassium|||20
> 040305110500||||||857818^26^3~Etude du Dr No^16^3~TEST=20
> commentaire^5^3~Fi=E8vre d'origine=20
> ind=E9termin=E9e^0^3||35^sg.v^Sang=20
> veineux|||N|N^-1008933||||||||1^R||||||||||||||||
> OBR|2|6^^20040305^0005^6200403050005||EXAM^42^bilanlipid^Bilan
> lipidique=20
> (Chol+Trig+HDL)|||20040305110500||||||857818^26^3~Etude du Dr=20
> No^16^3~TEST commentaire^5^3~Fi=E8vre d'origine=20
> ind=E9termin=E9e^0^3||35^sg.v^Sang=20
> veineux|||N|N^-1008933||||||||1^R||||||||||||||||
> OBR|3|6^^20040305^0005^6200403050005||EXAM^21^creatinine^Cr=E9at
> inine|||20040305110500||||||857818^26^3~Etude du Dr=20
> No^16^3~TEST commentaire^5^3~Fi=E8vre d'origine=20
> ind=E9termin=E9e^0^3||35^sg.v^Sang=20
> veineux|||N|N^-1008933||||||||1^R||||||||||||||||
>=20
> with 0.3 parser :
>=20
> Structure _struct =3D=20
> ORM_O01.getAll("ORM_O01_ORCOBRRQDRQ1RXOODSODTNTEDG1OBXNTECTIBLG")=20
> normally _struct.lenght =3D=3D 3
>=20
> Structure with 0.4.1 and 0.4.2 parser
>=20
> Structure _struct =3D=20
> ORM_O01.getAll("ORM_O01_ORCOBRRQDRQ1RXOODSODTNTEDG1OBXNTECTIBLG")=20
> problem _struct.lenght =3D=3D 1 !!!!!=20
>=20
> If you wanna test this data you should disable telephone=20
> number validation.
>=20
> thanks for your help...
>=20
> Regards
>=20
> Aris Javier Ramos
> Analyst Developper
> Direction Informatique de Gestion
> H=F4pital Cantonal Universitaire de Gen=E8ve
> Switzerland
>=20
>=20
>=20
> =
**********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
>=20
> =
**********************************************************************
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the=20
> changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? =
Now,
> one more big change to announce. We are now OSTG- Open Source=20
> Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>=20
This e-mail may contain confidential and/or privileged information
for the sole use of the intended recipient. Any review or distribution
by anyone other than the person for whom it was originally intended is
strictly
prohibited. If you have received this e-mail in error, please contact =
the
sender and
delete all copies. Opinions, conclusions or other information contained =
in
this e-mail may not be that of the organization.
|
|
From: Aris J. R. <Ari...@hc...> - 2004-07-30 16:20:21
|
Bonjour,
1st PROBLEM :
parsing with hapi 0.4.2 in the 2.3 version of the norm HL7.
When parsing ORM O01 messages the parser give me back an RDO-O01 message...
I looked at the file ca\uhn\hl7v2\parser\eventmap\2.3.properties in the hap=
i-0.4.2.jar
and saw a kind of mapping like this :
[...]
ORM_O01 ORM_O01
ORM_O01 OMD_O01
ORM_O01 OMN_O01
ORM_O01 OMS_O01
ORM_O01 RDO_O01 <--- may be problematic ??=20
[...]
After a debug session I saw that the file ca\uhn\hl7v2\parser\eventmap\2.3=
.properties is used as a set of properties when the hapi parser determines =
what structure to load when a message is parsed and his structure construc=
ted.
The problem is that in the file ca\uhn\hl7v2\parser\eventmap\2.3.properties=
there are several entries for ORM_O01 messages and the one who is taken i=
s the last one :
[...]
ORM_O01 ORM_O01
ORM_O01 OMD_O01 <--- may be problematic ??
ORM_O01 OMN_O01 <--- may be problematic ??
ORM_O01 OMS_O01 <--- may be problematic ??
ORM_O01 RDO_O01 <--- may be problematic ??
[...]
The 2.4.properties seems to be OK as I saw only one mapping for ORM_O01:
[...]
ORM_O01 ORM_O01
[...]
Is this, what we are specting from the parser ??
if yes how can I do to obtain an ORM_O01 message ??
2nd PROBLEM :
I tryed to change the 2.3.properties to have one mapping ORM_O01 ORM_O01 an=
d it worked well.
But I obtained a different data organization that I obtained parsing with 0=
.3 hapi parser.
data :=20
MSH|^~\&|REQUETE|6^CL|UNILAB||20040305110331||ORM^O01|REQUETE-6-1078481010|=
T|2.3|||||||
PID|1||2004817||DERONT^Lisette||19400101|F|||^3 rue dancet^Geneve^1205^^CH|=
||||||||||||||||||N
PV1|1|H|NEUROL.^^2-FL^2-FL^H.C.U. - G E N E V E^H.U.G. - HOPITAL CANTONAL^5=
3401^^6421||||TIZIANA^TIZIANA^Dr^494143^U212^MC-UNITE DE MEDECINE COMMUNAUT=
AIRE^857818||||||||||||01.1008933|3||||||||||||||||||||||||20040115|2004021=
2|||||||
ORC|NW|6^^20040305^0005^6200403050005||0500051086|||||20040305110325|mit||T=
IZIANA^TIZIANA^Dr^494143^U212^MC-UNITE DE MEDECINE COMMUNAUTAIRE^857818||2-=
FL^53401^^6421|||||
OBR|1|6^^20040305^0005^6200403050005||EXAM^52^K^Potassium|||20040305110500|=
|||||857818^26^3~Etude du Dr No^16^3~TEST commentaire^5^3~Fi=E8vre d'origin=
e ind=E9termin=E9e^0^3||35^sg.v^Sang veineux|||N|N^-1008933||||||||1^R|||||=
|||||||||||
OBR|2|6^^20040305^0005^6200403050005||EXAM^42^bilanlipid^Bilan lipidique (C=
hol+Trig+HDL)|||20040305110500||||||857818^26^3~Etude du Dr No^16^3~TEST co=
mmentaire^5^3~Fi=E8vre d'origine ind=E9termin=E9e^0^3||35^sg.v^Sang veineux=
|||N|N^-1008933||||||||1^R||||||||||||||||
OBR|3|6^^20040305^0005^6200403050005||EXAM^21^creatinine^Cr=E9atinine|||200=
40305110500||||||857818^26^3~Etude du Dr No^16^3~TEST commentaire^5^3~Fi=E8=
vre d'origine ind=E9termin=E9e^0^3||35^sg.v^Sang veineux|||N|N^-1008933||||=
||||1^R||||||||||||||||
with 0.3 parser :
Structure _struct =3D ORM_O01.getAll("ORM_O01_ORCOBRRQDRQ1RXOODSODTNTEDG=
1OBXNTECTIBLG")=20
normally _struct.lenght =3D=3D 3
Structure with 0.4.1 and 0.4.2 parser
Structure _struct =3D ORM_O01.getAll("ORM_O01_ORCOBRRQDRQ1RXOODSODTNTEDG1=
OBXNTECTIBLG")=20
problem _struct.lenght =3D=3D 1 !!!!!=20
If you wanna test this data you should disable telephone number validation.
thanks for your help...
Regards
Aris Javier Ramos
Analyst Developper
Direction Informatique de Gestion
H=F4pital Cantonal Universitaire de Gen=E8ve
Switzerland
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
**********************************************************************
|
|
From: Tripp, B. <Bry...@uh...> - 2004-07-28 03:19:40
|
Hi Alan,
That sounds like the thing to do. I can't think of a reason against, so if
nobody else speaks up I'll make this change in HEAD as well.
Bryan
> -----Original Message-----
> From: Alan Shields [mailto:ala...@bt...]
> Sent: July 27, 2004 7:14 AM
> To: hl7...@li...
> Subject: [HAPI-devel] linefeeds and \.br\
>
>
> Hi all,
> After years of splitting my report text over several OBX messages
> somebody just asked me to send a single obx with \.br\ to signify
> linefeeds.
>
> At first I thought of replacing the linefeeds with \.br\ in my code,
> unfortunately HAPI escapes the \ to give me, \E\.br\E\.
>
> In the end I added the following line to
> ca/uhn/hl7v2/parser/Escape.java
> seqs.put("\\.br\\", String.valueOf('\n'));
>
> which works a treat for my outgoing messages, though I
> haven't tried it
> to see what happens if somebody sends me a \.br\
>
> Is this a reasonable approach?
> Is it possible for me to indicate to HAPI that I want to insert an
> escape sequence?
> Is there any reason anybody would NOT want HAPI to simply replace
> linefeeds with \.br\ ?
>
> Cheers
> Alan Shields
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>
This e-mail may contain confidential and/or privileged information
for the sole use of the intended recipient. Any review or distribution
by anyone other than the person for whom it was originally intended is
strictly
prohibited. If you have received this e-mail in error, please contact the
sender and
delete all copies. Opinions, conclusions or other information contained in
this e-mail may not be that of the organization.
|
|
From: Alan S. <ala...@bt...> - 2004-07-27 11:13:56
|
Hi all,
After years of splitting my report text over several OBX messages
somebody just asked me to send a single obx with \.br\ to signify
linefeeds.
At first I thought of replacing the linefeeds with \.br\ in my code,
unfortunately HAPI escapes the \ to give me, \E\.br\E\.
In the end I added the following line to ca/uhn/hl7v2/parser/Escape.java
seqs.put("\\.br\\", String.valueOf('\n'));
which works a treat for my outgoing messages, though I haven't tried it
to see what happens if somebody sends me a \.br\
Is this a reasonable approach?
Is it possible for me to indicate to HAPI that I want to insert an
escape sequence?
Is there any reason anybody would NOT want HAPI to simply replace
linefeeds with \.br\ ?
Cheers
Alan Shields
|
|
From: Alan S. <ala...@bt...> - 2004-07-27 09:41:00
|
I would guess the problem is the extra trailing ^ in MSH:9 as HL7 =20 defines this as a two component field. Alan Shields On 26 Jul 2004, at 22:52, stevmon wrote: > I am not certain of the contact for my question.=A0 If this is not = the =20 > correct place, please refer me to whomever - and TIA. > > I am having a problem with some messages that I don't think it is =20 > correct behavior of the HAPI engine and the testpanel application.=A0 = We =20 > are trying to interface with a MedStar system to receive Orders =20 > message and populate the patient and exam exam tables used by another =20= > application.=A0 You should be able to duplicate the problem by pasting = =20 > the following message into the testpanel application and parsing it.=A0 = =20 > Here is an excerpt from the raw_messages.log file: > > =20 > = MSH|^~\&|MedStar||||200407261635||ORM^O01^|1833|P^|2.3.1|||||||English| > =20 > = PID|001||0000004164||Patient5^Pending||20040404|F||Black|2342^23423^MIa=20= > mi^FL^44444^|||||S|||000000000||||||||||| > =20 > = PV1|001||^^^50||||^^^^|^^||||||||||||||||||||||||||||||||||||2004051715=20= > 00|||||||| > ORC|NW||1770||||||||||||||50|||||||^^^^^ > OBR|001||1770|Default =20 > reason||||||||||||^^^|||||||||||^^^200405171500|||||||||||||||||| > > > MSH|^~\&|||||20040726153600.968-0600||ACK|233|P|2.3.1 > MSA|AE|1833|Couldn't Read PID Message Header: PID does not exist in =20= > the group ca.uhn.hl7v2.m > ERR|^^^207&Application Internal Error&HL70357 > > If I copy and past the raw message into the testpanel application, it = =20 > fails to parse the segments correctly.=A0 HOWEVER if I change the =20 > message type to ADT^O01 it will parse correctly - and if I change the =20= > message type to ORM^001 it will still parse the message correctly so =20= > the the PID, PV1, ORC and OBR segments can be retrieved correctly.=A0 =20= > Another excerpt from the logging file after I do this: > > MSH|^~\&|MedStar||||200407261635||ORM^001|1833|P|2.3.1|||||||English > =20 > = PID|001||0000004164||Patient5^Pending||20040404|F||Black|2342^23423^MIa=20= > mi^FL^44444|||||S|||000000000 > PV1|001||^^^50|||||||||||||||||||||||||||||||||||||||||200405171500 > ORC|NW||1770||||||||||||||50 > OBR|001||1770|Default reason|||||||||||||||||||||||^^^200405171500 > > > MSH|^~\&|||||20040726154142.218-0600||ACK|234|P|2.3.1 > MSA|AA|1833 > > Note that the message that is logged has been slightly altered during = =20 > the process of changing the message type back and forth.=A0 I have = added =20 > my own message handler based on the simple_server and that seems to =20= > work very well once the message is interpreted and parsed into =20 > components correctly. > > I am trying to get some other examples from elsewhere and have tried =20= > some messages found on the internet including so,e from linkmed.com.=A0 = =20 > The ORM tag seems to cause some confusion but a simple edit to ADT and = =20 > everything seems fine (in some cases, it does appear that I cannot =20 > toggle back to ORM or the message will fail to parse again.) > > As usuall this project needs to get done very soon and I would =20 > appreciate a rapid response very much! > > Thanks > Stev=20= |
|
From: stevmon <ste...@si...> - 2004-07-26 21:52:55
|
I am not certain of the contact for my question. If this is not the correct place, please refer me to whomever - and TIA. I am having a problem with some messages that I don't think it is correct behavior of the HAPI engine and the testpanel application. We are trying to interface with a MedStar system to receive Orders message and populate the patient and exam exam tables used by another application. You should be able to duplicate the problem by pasting the following message into the testpanel application and parsing it. Here is an excerpt from the raw_messages.log file: MSH|^~\&|MedStar||||200407261635||ORM^O01^|1833|P^|2.3.1|||||||English| PID|001||0000004164||Patient5^Pending||20040404|F||Black|2342^23423^MIami^FL^44444^|||||S|||000000000||||||||||| PV1|001||^^^50||||^^^^|^^||||||||||||||||||||||||||||||||||||200405171500|||||||| ORC|NW||1770||||||||||||||50|||||||^^^^^ OBR|001||1770|Default reason||||||||||||^^^|||||||||||^^^200405171500|||||||||||||||||| MSH|^~\&|||||20040726153600.968-0600||ACK|233|P|2.3.1 MSA|AE|1833|Couldn't Read PID Message Header: PID does not exist in the group ca.uhn.hl7v2.m ERR|^^^207&Application Internal Error&HL70357 If I copy and past the raw message into the testpanel application, it fails to parse the segments correctly. HOWEVER if I change the message type to ADT^O01 it will parse correctly - and if I change the message type to ORM^001 it will still parse the message correctly so the the PID, PV1, ORC and OBR segments can be retrieved correctly. Another excerpt from the logging file after I do this: MSH|^~\&|MedStar||||200407261635||ORM^001|1833|P|2.3.1|||||||English PID|001||0000004164||Patient5^Pending||20040404|F||Black|2342^23423^MIami^FL^44444|||||S|||000000000 PV1|001||^^^50|||||||||||||||||||||||||||||||||||||||||200405171500 ORC|NW||1770||||||||||||||50 OBR|001||1770|Default reason|||||||||||||||||||||||^^^200405171500 MSH|^~\&|||||20040726154142.218-0600||ACK|234|P|2.3.1 MSA|AA|1833 Note that the message that is logged has been slightly altered during the process of changing the message type back and forth. I have added my own message handler based on the simple_server and that seems to work very well once the message is interpreted and parsed into components correctly. I am trying to get some other examples from elsewhere and have tried some messages found on the internet including so,e from linkmed.com. The ORM tag seems to cause some confusion but a simple edit to ADT and everything seems fine (in some cases, it does appear that I cannot toggle back to ORM or the message will fail to parse again.) As usuall this project needs to get done very soon and I would appreciate a rapid response very much! Thanks Stev |
|
From: Tripp, B. <Bry...@uh...> - 2004-07-14 16:17:43
|
Hi Iouri, Oops, sorry about that. It looks like we have to fix something. Let me take a look at it tonight and get back to you. Bryan -----Original Message----- From: Iouri Leonov To: Tripp, Bryan Cc: hl7...@li... Sent: 14/07/2004 12:00 PM Subject: RE: [HAPI-devel] How to use XML-binding to generate library class es for hapi parser? Hi Bryan, I am trying your idea of making hapi-compliant classes from an xml version of a conformance profile made by a Messaging Workbench. So I created IVLTest.mwb with standard A01 message with a twist - a custom ZVL segment. Then I created IVLTest.xml which among other things has a tag describing that ZVL custom segment. Next step - create classes using CongGen classes generator bundled in hapi-0.4.2.jar. Classes generator runs fine till it hits reference in A01 to my custom ZVL segment. This is what I am getting in the output: Generating Primitive: com.iouri.parser.generated.DG1children.DiagnosingClinician children.CompDegreeEgMD Generating Primitive: com.iouri.parser.generated.DG1children.DiagnosingClinician children.CompSourceTableId Generating Segment: com.iouri.parser.generated.SegDG1 ConformanceError: ca.uhn.hl7v2.conf.classes.exceptions.ConformanceError: Underlying HAPI class "ca .uhn.hl7v2.model.v22.message.ADT_A01" does not have accessor "getZVL()". This is probably a bug. Done. Hm!? I am wondering why it's happening. Are my settings are somehow wrong or classes generator has its own mind towards custom segments (he doesn't like the name of the segment I came up with ;)? Should you have five minutes to spare, may I ask you to have a look inside testPackage.zip where I put files mentioned in this message. Cheers, Iouri --- "Tripp, Bryan" <Bry...@uh...> wrote: > Hi Iouri, > > The instructions for making conformance classes are > here: > http://hl7api.sourceforge.net/conf/compiler.html > Conformance profiles are > normally written with the Messaging Workbench. Once > you have one, you can > use the HAPI tool to make corresponding classes. > > Alexei's suggestion is good though. If you go ahead > with that, conformance > profiles would also be a good source for these > transforms. > > HAPI uses the HL7 database to generate the code that > you download in the > source_vXX.zip files, i.e. most of what is under > ca.uhn.hl7v2.model.vXX. If > you have this database it's very easy to make the > classes (run the generate > and compile-gen Ant tasks). It's an access DB, and > it comes with forms for > adding segments, etc. The problem is that it is > expensive, so not many > people have it. It's for sale at > https://www.hl7.org/library/bookstore/ > > If there is interest, I'll ask the database creator > (Frank Oemig) whether we > could distribute an empty DB with the same structure > for free. I don't know > if the structure is considered intellectual property > or just the contents. > > Bryan > > > -----Original Message----- > > From: Iouri Leonov [mailto:iou...@ya...] > > Sent: July 13, 2004 1:23 AM > > To: hl7...@li... > > Subject: RE: [HAPI-devel] How to use XML-binding > to generate library > > class es for hapi parser? > > > > > > Hi Bryan, > > > > Thank you for your prompt and informative reply. > > > > Regarding the tool for generating Java classes > from > > HL7 conformance profiles. I am wondering what > tool is > > that? Is it available? Where could I see some docs > to > > figure out how to handle the tool? Is that tool > > somehow related to WHA Office of Information > Messaging > > Workbench? > > > > The same 'how-to' song with HL7 database. You > said > > that 'the message classes are normally generated > from > > the HL7 database'. Do those classes relate somehow > to > > classes in ca.uhn.hl7v2.model.vxx.message package? > > Well, I am very green both with hapi framework and > > with HL7 in general. Hence I do not have much of > an > > idea about that database schema nor about > > tools/techniques for generating from HL7 database > > records hapi-compliant Java classes (messages, > > segments, datatypes). Is there a way to provide > me > > with a link to info about this 'database HL7 > record - > > Java class' technique. > > > > Thanks again Bryan, > > > > Cheers, > > > > Iouri > > > > > > --- "Tripp, Bryan" <Bry...@uh...> wrote: > > > Hi Iouri, > > > > > > No, we don't have that. We do have a tool that > > > generates Java classes from > > > HL7 conformance profiles. These aren't message > > > classes, but wrappers that > > > further constrain underlying message classes to > > > agree with the profile. But > > > depending on how you want to use it this might > work > > > just as well for you. > > > > > > I should also point out that HAPI handles > unexpected > > > segments and fields > > > automatically, so normally you don't need to > make > > > corresponding custom > > > classes (although it does make some things more > > > convenient). > > > > > > Also, the message classes are normally generated > > > from the HL7 database, so > > > if you have access to that, it's just a matter > of > > > adding some entries to it. > > > I guess you could also make your own database > with > > > the same structure, if > > > you didn't have the standard one and wanted to > make > > > a lot of custom message > > > classes. > > > > > > Are any of the above satisfactory? > > > > > > Bryan > > > > > > -----Original Message----- > > > From: Iouri Leonov > > > To: hl7...@li... > > > Sent: 12/07/2004 2:17 PM > > > Subject: [HAPI-devel] How to use XML-binding to > > > generate library classes for > > > hapi parser? > > > > > > Good day developers. > > > > > > Recently I've started playing with hapi > framework. I > > > have a question > > > relating to configuration of messages. > > > > > > Let' say we have a very common scenario - a user > > > wants his custom > > > segment > > > ZUSER with some custom datatype MY_DT. I see the > > > only way to do it - > > > make > > > new Java files. I have to create a new > ZUSER.java in > > > segment package > > > and a > > > new MY_DT.java in datatype package. Then I have > to > > > go to message package > > > and > > > change message ADT_x.java file in order to make > it > > > work with these new > > > segment and datatype. Job that definitely > requires > > > skills of a Java > > > programmer. > > > > > > My question relates to ways of descriptive > > > programming. Is there a way > > > in > > > the current hapi implementations to describe the > > > content of my new > > > segment > > > and datatype not in .java file but rather in > some > > > XML file or in w3 XML > > > Schema file then run that xml instance through a > > > binding parser which > > > will > > > generate classes ZUSER.class and MY_DT.class > which > > > can be used directly > > > by > > > Pipe parser? Something in line with JAXB - XML > > > binding. If there is a > > > way, > > > then how to do it, if there's none - any idea > how to > > > make it happen? > > > > > > Cheers, > > > > > > Iouri Leonov > > > XML Developer > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email sponsored by Black Hat > Briefings & > > > Training. > > > Attend Black Hat Briefings & Training, Las Vegas > > > July 24-29 - > === message truncated === __________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail <<testPackage.zip>> This e-mail may contain confidential and/or privileged information for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this e-mail in error, please contact the sender and delete all copies. Opinions, conclusions or other information contained in this e-mail may not be that of the organization. |
|
From: Kelley, P. (HEALTH) <pet...@he...> - 2004-07-14 01:42:42
|
I'm parsing an HL7 message that is of type ORM-O01 but the parser is giving me type RDO-O01. As far as I can see the structures are similar but I was wondering if this is the expected behaviour? The HL7 message is as follows: MSH|^~\&|RAD|RAH|OACIS|DHS|20020327160528.0000+1030||ORM^O01|536702032716052 845|P|2.3.1|||AL|NE|AUS| PID|||10000008^^^RAH^MR~12345678^^^RAH^MC|46761|SUBARU^STIWRX^^^CMRS||198009 16110000.0000+1030|F||U|99 DOCKLAND^DOCKLAND 2^GREENPEACE^SA^5136||999-9999||U|U| ORC|NW||12345678|||||||Beanl^Bean^Les^^^Dr^^7776666B||Tooj^Toouli^J^^^Prof^^ 0241833J|||20020327160800.0000+1030| OBR|0||12345678|GENREP^General Radiology||20020327000000.0000+1030|20020327160800.0000+1030|||||||||Tooj^To ouli^J^^^Prof^^0241833J||RAH|WARD7|CIV|56507*|20020327160800.0000+1030|0.00| General Ra|I||^^^20020327160800.0000+1030^^R||||CXR^Chest~LE^Left Elbow~KNEEL^Knee Left| Note: This is a test message, no real data was used Regards, Peter Kelley Support Analyst Projects Branch - ICT Services Department of Health South Australia |
106 messages has been excluded from this view by a project administrator.
