Menu
▾
▴
hl7api-devel
|
From: Shrock, C. <Sh...@in...> - 2005-02-23 22:05:23
|
I see v2.3--good, I was seeing messages that said they were v2.2 but had some v2.3 components. I ended up having to extend the v2.2 model to include this "new" functionality. Off the top of my head, I would start looking at model/v23/message/ORM_O01 and model/v23/message/RDO_O01 classes and verify that the segments/groups that those classes load can match the message structure that you are receiving. Have you verified that is not related to the XML encoding by testing the messages with the included app/TestPanel class (it is the default class when you execute the hapi jar file)? -----Original Message----- From: Eric Freed [mailto:ef...@ne...] Sent: Wednesday, February 23, 2005 12:28 PM To: hl7...@li... Subject: [HAPI-devel] ORM 001 and XML Hi, I am having a problem that I think is related to a problem that has been brought up here a few times, but I am not sure of the answer. In the course of testing I tried to have a message go from regular encoding, to XML and then back. However, the final message is not the same as the first one: First message: ---------------------------------------------------------- MSH|^~\&|ADS|LL|PSCRIBE||200209181134||ORM^O01|2|P|2.3 PID|||263334||SMITH^JOHN||19471112|M|||ADDRESS^^CITY^ST||(914)633-7700|| PID|||263334|||||263334|123-45-6789 ORC|NW|LL02-194182||||||||||455^JONES^JOHN OBR||LL02-194182|(963)232-25AF|71020^CHEST PA LAT||20020920||||||||||455^JONES^JOHN|(914)632-9422 ---------------------------------------------------------- returned message: ---------------------------------------------------------- MSH|^~\&|ADS|LL|PSCRIBE||200209181134||ORM^O01|2|P|2.3 PID|||263334||SMITH^JOHN||19471112|M|||ADDRESS^^CITY^ST||(914)633-7700|| PID|||263334|||||263334|123-45-6789 ORC|NW|LL02-194182||||||||||455^JONES^JOHN ------------------------------------------------------------ The OBR segment is missing. When I look at the XML, it starts with <RDO_O01> I know the RDO^O01 and ORM^O01 issue has been brought up here, but I didn't see a solution and don't know if it would cause the problem above. Any advice? Thanks, -- Eric Freed IT Manager New Rochelle Radiology 914-633-7700 x339 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Hl7api-devel mailing list Hl7...@li... https://lists.sourceforge.net/lists/listinfo/hl7api-devel |
|
From: Tripp, B. <Bry...@uh...> - 2005-02-23 22:23:52
|
Hi Eric,=20 =20 There are a few things here: 1) The O01 event has a number of = alternative structures associated with it, which makes it impossible to choose the "right" message structure based on the event alone (I'm not aware of any other events like this). HAPI defaults to RDO. There are two ways you = can deal with this. If possible, specify the message structure in MSH-9-3 as ORM_O01. The other way is to change the default mapping in = parser.event_map from the RDO to the ORM structure. =20 =20 2) HAPI's XML support doesn't handle unexpected segments. (This is on = the list of things to do but hasn't been a priority, because few people seem = to use XML.) If the RDO structure is used, your OBR segment looks like an unexpected one, and the XML parser ignores it. =20 =20 3) I don't have the specs with me (I'm not at work today), but is LAT = part of the ORM structure? If not it will be seen as unexpected in any case, = and will be ignored by the XML parser. To address this you would have to customize the ORM_O01 class (not difficult ... just one line of code = added to the constructor). =20 =20 Bryan=20 ________________________________ From: hl7...@li... on behalf of Eric Freed Sent: Wed 23/02/2005 3:28 PM To: hl7...@li... Subject: [HAPI-devel] ORM 001 and XML Hi, I am having a problem that I think is related to a problem that has been brought up here a few times, but I am not sure of the answer. In the course of testing I tried to have a message go from regular encoding, to XML and then back. However, the final message is not the same as the first one: First message: ---------------------------------------------------------- MSH|^~\&|ADS|LL|PSCRIBE||200209181134||ORM^O01|2|P|2.3 PID|||263334||SMITH^JOHN||19471112|M|||ADDRESS^^CITY^ST||(914)633-7700|||= ||2 63334|123-45-6789 ORC|NW|LL02-194182||||||||||455^JONES^JOHN OBR||LL02-194182|(963)232-25AF|71020^CHEST PA LAT||20020920||||||||||455^JONES^JOHN|(914)632-9422 ---------------------------------------------------------- returned message: ---------------------------------------------------------- MSH|^~\&|ADS|LL|PSCRIBE||200209181134||ORM^O01|2|P|2.3 PID|||263334||SMITH^JOHN||19471112|M|||ADDRESS^^CITY^ST||(914)633-7700|||= ||2 63334|123-45-6789 ORC|NW|LL02-194182||||||||||455^JONES^JOHN ------------------------------------------------------------ The OBR segment is missing. When I look at the XML, it starts with = <RDO_O01> I know the RDO^O01 and ORM^O01 issue has been brought up here, but I didn't see a solution and don't know if it would cause the problem = above. Any advice? Thanks, -- Eric Freed IT Manager New Rochelle Radiology 914-633-7700 x339 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick _______________________________________________ Hl7api-devel mailing list Hl7...@li... https://lists.sourceforge.net/lists/listinfo/hl7api-devel |
|
From: Eric F. <ef...@ne...> - 2005-02-24 14:14:09
|
In reverse order: 3) LAT is not part of the ORM structure, it is an artifact of the segment being wrapped by the email: OBR||LL02-194182|(963)232-25AF|71020^CHEST PA LAT||20020920||||||||||455^JONES^JOHN|(914)632-9422 is one line with "|71020^CHEST PA LAT|" being field 5 2) OK. I wanted to use XML to do various transformations with XSLT...but if people don't use the XML much perhaps there is a reason and I should consider do the transformation in pure Java. 1) Perhaps I don't know as much as I thought, but how can I specify the message structure more explicitly than have ORM^O01 as MSH-9? And what is MSH-9-3, I have only seen two subfields in MSH-9, not three. Perhaps I am misunderstanding. Many Thanks Tripp, Bryan wrote: > Hi Eric, > > There are a few things here: 1) The O01 event has a number of alternative > structures associated with it, which makes it impossible to choose the > "right" message structure based on the event alone (I'm not aware of any > other events like this). HAPI defaults to RDO. There are two ways you can > deal with this. If possible, specify the message structure in MSH-9-3 as > ORM_O01. The other way is to change the default mapping in parser.event_map > from the RDO to the ORM structure. > > 2) HAPI's XML support doesn't handle unexpected segments. (This is on the > list of things to do but hasn't been a priority, because few people seem to > use XML.) If the RDO structure is used, your OBR segment looks like an > unexpected one, and the XML parser ignores it. > > 3) I don't have the specs with me (I'm not at work today), but is LAT part > of the ORM structure? If not it will be seen as unexpected in any case, and > will be ignored by the XML parser. To address this you would have to > customize the ORM_O01 class (not difficult ... just one line of code added > to the constructor). > > Bryan > > ________________________________ > > From: hl7...@li... on behalf of Eric Freed > Sent: Wed 23/02/2005 3:28 PM > To: hl7...@li... > Subject: [HAPI-devel] ORM 001 and XML > > > > Hi, > > I am having a problem that I think is related to a problem that has been > brought up here a few times, but I am not sure of the answer. > > In the course of testing I tried to have a message go from regular > encoding, to XML and then back. However, the final message is not the > same as the first one: > > First message: > > ---------------------------------------------------------- > MSH|^~\&|ADS|LL|PSCRIBE||200209181134||ORM^O01|2|P|2.3 > PID|||263334||SMITH^JOHN||19471112|M|||ADDRESS^^CITY^ST||(914)633-7700|||||2 > 63334|123-45-6789 > ORC|NW|LL02-194182||||||||||455^JONES^JOHN > OBR||LL02-194182|(963)232-25AF|71020^CHEST PA > LAT||20020920||||||||||455^JONES^JOHN|(914)632-9422 > ---------------------------------------------------------- > > returned message: > > ---------------------------------------------------------- > MSH|^~\&|ADS|LL|PSCRIBE||200209181134||ORM^O01|2|P|2.3 > PID|||263334||SMITH^JOHN||19471112|M|||ADDRESS^^CITY^ST||(914)633-7700|||||2 > 63334|123-45-6789 > ORC|NW|LL02-194182||||||||||455^JONES^JOHN > ------------------------------------------------------------ > > > The OBR segment is missing. When I look at the XML, it starts with <RDO_O01> > > I know the RDO^O01 and ORM^O01 issue has been brought up here, but I > didn't see a solution and don't know if it would cause the problem above. > > Any advice? > > Thanks, > > > -- > Eric Freed > IT Manager > New Rochelle Radiology > 914-633-7700 x339 > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Hl7api-devel mailing list > Hl7...@li... > https://lists.sourceforge.net/lists/listinfo/hl7api-devel > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_ide95&alloc_id396&op=click > _______________________________________________ > Hl7api-devel mailing list > Hl7...@li... > https://lists.sourceforge.net/lists/listinfo/hl7api-devel -- Eric Freed IT Manager New Rochelle Radiology 914-633-7700 x339 |
|
From: Tripp, B. <Bry...@uh...> - 2005-02-24 14:49:57
|
Hi Eric,=20 > 3) LAT is not part of the ORM structure, it is an artifact of the segment being wrapped by the email: :)=20 =20 > 2) OK. I wanted to use XML to do various transformations with = XSLT...but if people don't use the XML much perhaps there is a reason and I should consider do the transformation in pure Java. I'm not sure if there is a reason other than tradition. Although if = you're receiving the messages in ER7 you might get better performance without = XML, just because you will parse and encode each message once instead of = twice. =20 > 1) Perhaps I don't know as much as I thought, but how can I specify = the message structure more explicitly than have ORM^O01 as MSH-9? And what is MSH-9-3, I have only seen two subfields in MSH-9, not three. Perhaps I am misunderstanding. Come to think of it, MSH-9-3 was introduced in 2.3.1, but you're using = 2.3. It's an explicit statement of the message structure, whereas MSH-9-1 and MSH-9-2 give the type and event from which the structure can normally be derived by lookup (e.g. ADT^A03 uses structure ADT_A01). It's such a = handy field that HAPI recognizes it even if it shows up illegally in earlier versions. But maybe changing the default mapping is a better approach = with version 2.3. =20 =20 Bryan=20 =20 |
|
From: Archie C. <ar...@de...> - 2005-02-24 15:15:17
|
Tripp, Bryan wrote: >>2) OK. I wanted to use XML to do various transformations with XSLT...but > > if people don't use the XML much perhaps there is a reason and I should > consider do the transformation in pure Java. By the way.. for what it's worth, we are using the XML form and it is integral to the way our product works. HAPI inputs HL7 which we convert to XML and then run XSLT to convert that "raw" input into a form our product understands. The whole process works very nicely... -Archie __________________________________________________________________________ Archie Cobbs * CTO, Awarix * http://www.awarix.com |
|
From: Eric F. <ef...@ne...> - 2005-02-24 19:39:54
|
Thanks, I changed the default mapping for version 2.3 and it worked, so that is good. But I also tried to add the MSH-9-3 field (illegally) to the v2.3 message but had no luck. Out of curiosity, what would MSH-9 look like if I waned to use the ORM_O01 structure? I tried: ORM^O01^ORM_O01 but it did not work. Tripp, Bryan wrote: > > Come to think of it, MSH-9-3 was introduced in 2.3.1, but you're using 2.3. > It's an explicit statement of the message structure, whereas MSH-9-1 and > MSH-9-2 give the type and event from which the structure can normally be > derived by lookup (e.g. ADT^A03 uses structure ADT_A01). It's such a handy > field that HAPI recognizes it even if it shows up illegally in earlier > versions. But maybe changing the default mapping is a better approach with > version 2.3. > > Bryan > -- Eric Freed IT Manager New Rochelle Radiology 914-633-7700 x339 |
|
From: Eric F. <ef...@ne...> - 2005-02-25 14:19:01
|
No error, just no change: it continued to use RDO. In fact, if I change the version number to 2.3.1, it still uses RDO (but perhaps there are other parts of the message that are not 2.3.1. kosher). That is the right form, no? ORM^O01^ORM_O01 Eric Tripp, Bryan wrote: > Strange, I tried it too, and it worked for me. Was there an error message > or did it just continue to use RDO? > > Bryan > > -----Original Message----- > From: Eric Freed [mailto:ef...@ne...] > Sent: Thu 2/24/2005 2:39 PM > To: Tripp, Bryan > Cc: hl7...@li... > Subject: Re: [HAPI-devel] ORM 001 and XML > > Thanks, > > I changed the default mapping for version 2.3 and it worked, so that is > good. > > But I also tried to add the MSH-9-3 field (illegally) to the v2.3 > message but had no luck. Out of curiosity, what would MSH-9 look like if > I waned to use the ORM_O01 structure? I tried: > > ORM^O01^ORM_O01 > > but it did not work. > > > > Tripp, Bryan wrote: > > >>Come to think of it, MSH-9-3 was introduced in 2.3.1, but you're using > > 2.3. > >>It's an explicit statement of the message structure, whereas MSH-9-1 and >>MSH-9-2 give the type and event from which the structure can normally be >>derived by lookup (e.g. ADT^A03 uses structure ADT_A01). It's such a > > handy > >>field that HAPI recognizes it even if it shows up illegally in earlier >>versions. But maybe changing the default mapping is a better approach > > with > >>version 2.3. >> >>Bryan >> > > -- Eric Freed IT Manager New Rochelle Radiology 914-633-7700 x339 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X