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: Chandan D. <cha...@au...> - 2014-11-26 12:13:50
|
Hi James, Is there a link to the war file that I can download now? On Fri, Nov 21, 2014 at 4:15 AM, James Agnew <jam...@gm...> wrote: > Hi Chandan, > > (FYI, this is actually the mailing list for HAPI's HL7 v2 library. It's > probably better to post to the HAPI FHIR list/group, which can be found > over here: https://groups.google.com/d/forum/hapi-fhir ) > > The easiest way to get started is probably with the "Vagrant" development > environment what was contributed last month. This starts up a virtual > machine on your workstation that has a fully functional version of the test > server running on it. Instructions can be found here: > http://jamesagnew.github.io/hapi-fhir/doc_vagrant.html > > Beyond that, you could then look at simply running the same server in a > local container (e.g. Tomcat). We haven't published instructions on how to > do that yet, but I'm sure we could talk you through it on the user group. > > Cheers, > James > > On Wed, Nov 19, 2014 at 6:16 AM, Chandan Datta < > cha...@au...> wrote: > >> Hi >> >> I am looking for a EMR data container that I can use to query patient >> data. Is there a data container that I might be able to download and >> install locally? >> >> I can see http://fhirtest.uhn.ca/about , but can I install it locally. >> If so, what are the steps? >> >> -- >> Regards, >> Chandan >> Doctoral student,Robotics Research Group >> University of Auckland, New Zealand >> >> >> ------------------------------------------------------------------------------ >> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server >> from Actuate! Instantly Supercharge Your Business Reports and Dashboards >> with Interactivity, Sharing, Native Excel Exports, App Integration & more >> Get technology previously reserved for billion-dollar corporations, FREE >> >> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk >> _______________________________________________ >> Hl7api-devel mailing list >> Hl7...@li... >> https://lists.sourceforge.net/lists/listinfo/hl7api-devel >> >> > -- Regards, Chandan Doctoral student,Robotics Research Group University of Auckland, New Zealand http://realworldrobotics.com |
|
From: Chandan D. <cha...@au...> - 2014-11-26 06:09:43
|
I am trying to use the conformance profile for HAPI: http://hl7api.sourceforge.net/conformance.html When I save the mvn config and compile it; it says these errors. Can i still use the generated classes and what is the resolution for the errors? http://pastebin.com/qZfX8CJ7 -- Regards, Chandan Doctoral student,Robotics Research Group University of Auckland, New Zealand http://realworldrobotics.com |
|
From: Pablo L. <pab...@ho...> - 2014-11-25 09:44:51
|
MSH|^~\&|EXTERNALAPL||MILENIO||20140813140855||ORU^R01^ORU_R01|368f14b8-b629-4f09-91f8-9b0067d8e517|P|2.5.1 PID|||12345^^^^NHC-DEMO1~DFK897812345^^^^CIP||PRIMER APELLIDO^NOMBRE^SEGUNDO APELLIDO||19691022|M||2106-3^BLANCA|CALLE BERNA 4^^LAS ROZAS^MADRID^28232^ESP||917103256^^^ho...@do...d|917103694^^^ho...@do...d PV1||HOSP|UE4I^^402-1^HS|IMEDICA||||fer...@do...d^APELLIDO 1^NOMBRE^APELLIDO 2||CAR1||||||||99220|12345678^^^^NHC-DEMO1||||||||||||||||||||HM|||||20141012092042 ORC|NW|667788|87111||A||||20141023092205|||fer...@do...d^APELLIDO 1^NOMBRE^APELLIDO 2 OBR|1|||24358-4^Hemograma^LN~2345-7^Glucosa^LN~3091-6^Urea^LN~13955-0^Anticuerpos Hepatitis C^LN~630-4^Urocultivo^LN~541-3^Cultivo de micobacterias en orina^LN~600-7^Hemocultivo^LN|||20141023094742|||||||||||||26436-6 OBX|1|NM|26464-8^Leucocitos^LN||6.79|mil/mm3|4.5 - 11.5|N|||F|||20141023113011||pab...@do...d^APELLIDO 1^NOMBRE^APELLIDO 2 OBX|2|NM|26453-1^Hematies^LN||5.08|mill/mm3|4.5 - 6.3|N|||F|||20141023113011||pab...@do...d^APELLIDO 1^NOMBRE^APELLIDO 2 OBX|3|NM|26515-7^Plaquetas^LN||222|mill/mm3|140 - 450|N|||F|||20141023113011||pab...@do...d^APELLIDO 1^NOMBRE^APELLIDO 2 OBX|4|NM|2345-7^Glucosa^LN||120|mg/dl|70 - 110|H|||F|||20141023113011||pab...@do...d^APELLIDO 1^NOMBRE^APELLIDO 2 OBX|5|ST|3091-6^Urea^LN||||||||P OBX|6|NM|13955-0^Anticuerpos Hepatitis C^LN||0.8||<1|N|||F|||20141023113011||pab...@do...d^APELLIDO 1^NOMBRE^APELLIDO 2 OBX|7|ST|13955-0^Anticuerpos Hepatitis C^LN||Negativo|||N|||F|||20141023113011||pab...@do...d^APELLIDO 1^NOMBRE^APELLIDO 2 OBX|8|ST|630-4^Urocultivo^LN||Se aisla|||A|||F|||20141023113011||pab...@do...d^APELLIDO 1^NOMBRE^APELLIDO 2 OBX|9|ST|630-4^Urocultivo^LN|1|112283007^Escherichia coli^SNM|||A|||F|||20141023113011||pab...@do...d^APELLIDO 1^NOMBRE^APELLIDO 2 OBX|10|ST|541-3^Cultivo de micobacterias en orina^LN||Negativo|||N|||F|||20141023113011||pab...@do...d^APELLIDO 1^NOMBRE^APELLIDO 2 OBX|11|ST|600-7^Hemocultivo^LN||Positivo|||A|||F|||20141023113011||pab...@do...d^APELLIDO 1^NOMBRE^APELLIDO 2 OBX|12|ST|600-7^Hemocultivo^LN|2|112283007^Escherichia coli^SNM|||A|||F|||20141023113011||pab...@do...d^APELLIDO 1^NOMBRE^APELLIDO 2 OBX|13|ST|600-7^Hemocultivo^LN|3|44827007^Staphylococcus hominis^SNM|||A|||F|||20141023113011||pab...@do...d^APELLIDO 1^NOMBRE^APELLIDO 2 OBR|2|||48611-8^Antibiograma^LN|||20141023094742|||||||||||||26436-6||||||630-4&Urocultivo&LN^1 OBX|1|ST|18860-7^Amikacina^LN||<2|||S|||F|||20141023113011||pab...@do...d^APELLIDO 1^NOMBRE^APELLIDO 2 OBX|2|ST|18864-9^Ampicilina^LN||>2|||R|||F|||20141023113011||pab...@do...d^APELLIDO 1^NOMBRE^APELLIDO 2 OBR|3|||48611-8^Antibiograma^LN|||20141023094742|||||||||||||26436-6||||||600-7&Hemocultivo&LN^3 OBX|1|ST|18928-2^Gentamicina^LN||>2|||R|||F|||20141023113011||pab...@do...d^APELLIDO 1^NOMBRE^APELLIDO 2 OBX|2|ST|35783-0^Cefuroxima^LN||>2|||R|||F|||20141023113011||pab...@do...d^APELLIDO 1^NOMBRE^APELLIDO 2 |
|
From: Juan C. R. <j.r...@ne...> - 2014-11-24 18:42:44
|
I have found the problem. The problem was mine not the API. Sorry De: Juan Carlos Rodríguez [mailto:j.r...@ne...] Enviado el: lunes, 24 de noviembre de 2014 17:23 Para: hl7...@li... Asunto: [HAPI-devel] OBX data value problems Hi, I have a problem in Java with OBX data value. If I do this (obx.getObx5_ObservationValue(0).getData().toString()) I get 44. Debugging, I obtain the same value: But, the message that I receive has another value: 4.4!! What is the mistake? Is it correct? Thanks!! Juan Carlos Rodríguez <mailto:x....@ne...> j.rodriguez <mailto:x....@ne...> @necsia.es <http://www.necsia.es/> Almogàvers 119-123. 3ª planta 08018 Barcelona T +34 932 521 285 <http://www.necsia.es/> www.necsia.es <http://www.linkedin.com/company/2639154?goback=.fcs_GLHD_necsia_false_*2_*2 _*2_*2_*2_*2_*2_*2_*2_*2_*2_*2&trk=ncsrch_hits> <https://twitter.com/#!/necsia> <http://necsia.es/blog/> <https://plus.google.com/100703513558424933457/posts> <http://www.facebook.com/pages/Necsia/256984597735956> AVISO DE CONFIDENCIALIDAD: Tanto este mensaje como todos los posibles documentos adjuntos al mismo son confidenciales y están dirigidos exclusivamente a los destinatarios de los mismos. Por favor, si Ud. no es uno de dichos destinatarios, notifíquenos este hecho y elimine el mensaje de su sistema. Queda prohibida la copia, difusión o revelación de su contenido a terceros sin el previo consentimiento por escrito de Necsia. En caso contrario, vulnerará la legislación vigente. INFORMACIÓN RELATIVA A LA LOPD: En cumplimiento de la Ley Orgánica de Protección de Datos de Carácter Personal (LOPD), le informamos que sus datos de contacto han sido incorporados en ficheros titularidad de Necsia IT Consulting SL, que responden a la finalidad de servir de directorio o agenda de contactos así como para facilitar la gestión administrativa y comercial desarrollada por la empresa. Ud tiene la posibilidad de ejercer los derechos de acceso, rectificación, cancelación y oposición previstos en la ley mediante carta dirigida a Necsia IT Consulting, SL, Ref. Protección de datos, C/Almogàvers, nº 119-123. 3ª Planta, puerta 3, CP 08018, Barcelona. |
|
From: Juan C. R. <j.r...@ne...> - 2014-11-24 16:56:15
|
Hi, I have a problem in Java with OBX data value. If I do this (obx.getObx5_ObservationValue(0).getData().toString()) I get 44. Debugging, I obtain the same value: But, the message that I receive has another value: 4.4!! What is the mistake? Is it correct? Thanks!! Juan Carlos Rodríguez <mailto:x....@ne...> j.rodriguez <mailto:x....@ne...> @necsia.es <http://www.necsia.es/> Almogàvers 119-123. 3ª planta 08018 Barcelona T +34 932 521 285 <http://www.necsia.es/> www.necsia.es <http://www.linkedin.com/company/2639154?goback=.fcs_GLHD_necsia_false_*2_*2 _*2_*2_*2_*2_*2_*2_*2_*2_*2_*2&trk=ncsrch_hits> <https://twitter.com/#!/necsia> <http://necsia.es/blog/> <https://plus.google.com/100703513558424933457/posts> <http://www.facebook.com/pages/Necsia/256984597735956> AVISO DE CONFIDENCIALIDAD: Tanto este mensaje como todos los posibles documentos adjuntos al mismo son confidenciales y están dirigidos exclusivamente a los destinatarios de los mismos. Por favor, si Ud. no es uno de dichos destinatarios, notifíquenos este hecho y elimine el mensaje de su sistema. Queda prohibida la copia, difusión o revelación de su contenido a terceros sin el previo consentimiento por escrito de Necsia. En caso contrario, vulnerará la legislación vigente. INFORMACIÓN RELATIVA A LA LOPD: En cumplimiento de la Ley Orgánica de Protección de Datos de Carácter Personal (LOPD), le informamos que sus datos de contacto han sido incorporados en ficheros titularidad de Necsia IT Consulting SL, que responden a la finalidad de servir de directorio o agenda de contactos así como para facilitar la gestión administrativa y comercial desarrollada por la empresa. Ud tiene la posibilidad de ejercer los derechos de acceso, rectificación, cancelación y oposición previstos en la ley mediante carta dirigida a Necsia IT Consulting, SL, Ref. Protección de datos, C/Almogàvers, nº 119-123. 3ª Planta, puerta 3, CP 08018, Barcelona. |
|
From: James A. <jam...@gm...> - 2014-11-24 14:57:34
|
To be honest, this sounds like it might be a bug with the profile validator... Are you able to share a sample message and profile by any chance? Cheers, James On Mon, Nov 24, 2014 at 2:46 PM, Pablo León <pab...@ho...> wrote: > Hi, > > I'm using HAPI profile validator for ORU messages, but I'm getting the > following error: > > "HL7 datatype XX doesn't match profile datatype VARIES at OBX-5" > > where XX stands for the datatype specified in OBX-2. > > What am I missing? Wrong datatype in profile? Or is there some specific > treatment required for this case? > > Cheers, > > Pablo. > > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > > http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk > _______________________________________________ > Hl7api-devel mailing list > Hl7...@li... > https://lists.sourceforge.net/lists/listinfo/hl7api-devel > |
|
From: Pablo L. <pab...@ho...> - 2014-11-24 13:46:35
|
Hi,
I'm using HAPI profile validator for ORU messages, but I'm getting the
following error:
"HL7 datatype XX doesn't match profile datatype VARIES at OBX-5"
where XX stands for the datatype specified in OBX-2.
What am I missing? Wrong datatype in profile? Or is there some specific
treatment required for this case?
Cheers,
Pablo.
|
|
From: James A. <jam...@gm...> - 2014-11-20 15:15:55
|
Hi Chandan, (FYI, this is actually the mailing list for HAPI's HL7 v2 library. It's probably better to post to the HAPI FHIR list/group, which can be found over here: https://groups.google.com/d/forum/hapi-fhir ) The easiest way to get started is probably with the "Vagrant" development environment what was contributed last month. This starts up a virtual machine on your workstation that has a fully functional version of the test server running on it. Instructions can be found here: http://jamesagnew.github.io/hapi-fhir/doc_vagrant.html Beyond that, you could then look at simply running the same server in a local container (e.g. Tomcat). We haven't published instructions on how to do that yet, but I'm sure we could talk you through it on the user group. Cheers, James On Wed, Nov 19, 2014 at 6:16 AM, Chandan Datta <cha...@au... > wrote: > Hi > > I am looking for a EMR data container that I can use to query patient > data. Is there a data container that I might be able to download and > install locally? > > I can see http://fhirtest.uhn.ca/about , but can I install it locally. If > so, what are the steps? > > -- > Regards, > Chandan > Doctoral student,Robotics Research Group > University of Auckland, New Zealand > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > > http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk > _______________________________________________ > Hl7api-devel mailing list > Hl7...@li... > https://lists.sourceforge.net/lists/listinfo/hl7api-devel > > |
|
From: Chandan D. <cha...@au...> - 2014-11-19 11:16:28
|
Hi I am looking for a EMR data container that I can use to query patient data. Is there a data container that I might be able to download and install locally? I can see http://fhirtest.uhn.ca/about , but can I install it locally. If so, what are the steps? -- Regards, Chandan Doctoral student,Robotics Research Group University of Auckland, New Zealand |
|
From: Pablo L. <pab...@ho...> - 2014-11-13 18:47:32
|
Hi,
We're about to start a new project for Android devices, and I was
wondering what are your experiences with this environment, both
positives and negatives ...
Best,
Pablo León
|
|
From: <rsa...@fs...> - 2014-11-13 10:25:44
|
Thank you, James and Pablo, for your help. I'm going to compare the OBR-4 with the OBX-3. If the value is the same, OBX-4 is a battery, else OBx-4 is a test. Regards. Rafael. Rafael San Vidal Hidalgo - Dpto. Sistemas de Diagnóstico Tlf.: 914702104 (ext.158) - Fax: 915261867 rsa...@fs... - www.f-soria.es AVISO DE CONFIDENCIALIDAD La información contenida en este mensaje y archivos adjuntos es privada, confidencial y de uso exclusivo de la(s) persona(s) y entidad(es) a la(s) que va dirigido. Si Ud. no es el destinatario de esta información se le notifica que está expresamente prohibida la declaración, reproducción, distribución o la toma de cualquier acción basada en el contenido de esta comunicación. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente y proceda a eliminarlo de todos sus sistemas. Francisco Soria Melguizo, S.A. no asume responsabilidad legal por el contenido de esta comunicación, ni representa la opinión de la firma, salvo que expresamente se especifique lo contrario y que el remitente esté autorizado para hacerlo. Gracias. RE: [HAPI-devel] ORU^R01 Message: Battery and its testsdf pablo pazos para: James Agnew, rsa...@fs... Enviado: 11/11/2014 18:36 Recibido: 12/11/2014 09:31 cc: HAPI Devel List, "bom...@fs..." Hi Rafael, the messages seem correct. IMO your system and the sender system might need to agree on the codes and have some kind of table that tells you which codes are for batteries and which ones are for individual results, but that's outside the messages. So in OBR-4 you might use those codes and use the lookup table to know which are batteries and which not. If you need that inside the messages you might use a Z segment or a NTE associated with the OBR. Hope that helps! -- Kind regards, Eng. Pablo Pazos Gutiérrez http://cabolabs.com From: jam...@gm... Date: Tue, 11 Nov 2014 12:04:37 -0500 To: rsa...@fs... CC: hl7...@li...; bom...@fs... Subject: Re: [HAPI-devel] ORU^R01 Message: Battery and its testsdf Hi Rafael, (Other people please chime in too! I'm hardly a lab expert..) One of the joys of HL7 v2 is that a lot of the standard is loose and subject to interpretation, which means that often there isn't a right answer to how something works in the specification, you need to understand how the sender/receiver is using it. This is one of those cases. Based on the samples you have provided it seems like your interpretation is correct.. but really only the sender would know for sure. Cheers, James On Tue, Nov 11, 2014 at 10:33 AM, <rsa...@fs...> wrote: Hi, I have received the next ORU^R01 message: MSH|^~\&|MG|MG|LAB|LAB|20100127101236+0100||ORU^R01^ORU_R01|1234567890|P|2.5 PID|... PV1|... ORC|... OBR|1|OP2|10101010|HEM^Hemograma^SISTEMA1|... OBX|1|NM|HTIE^Hematíes^SISTEMA1||7.00|x10*6/uL|4.5 - 5.9|HH|||F|||20100127095652 OBX|2|NM|HGB^Hemoglobina^SISTEMA1||567567.0|g/dL|13.0 - 17.5|HH|||F|||20100127095652 OBX|3|NM|HTCO^Hematocrito^SISTEMA1||77.0|%|37.0 - 53.0|HH|||F|||20100127095728 OBX|4|NM|VCM^VCM^SISTEMA1||67.0|fl|80.0 - 100.0|LL|||F|||20100127095728 SPM|1|9018000088||^SANGRE PERIFERICA||||||||||||||20100127095625||Y||||||1 In this message, the OBR Segment contains a Battery (HEM) and the tests have been added in OBX Segments. In this case, the HEM Battery contains 4 tests (HTIE, HGB, HTCO and VCM). I would like to know if this message is a Standard HL7 Message. At the moment, I have only received tests in ORU^R01 messages. In the next ORU^R01 message, I have received a test (CLC00500) with two results (OBX.1 and OBX.2 segments): MSH|^~\&|MG|MG|FSM|FSM|20141105132023+0100||ORU^R01^ORU_R01|LAB31415190023385|P|2.5 PID|... PV1|... ORC|... OBR|1|PA5999171|20000002|CLC00500^Pla--Glucosa; c.sust.(proc.)^SISTEMA1||||||CE||||||00010258960^ape1 ape2, nombre||||5||||LAB|F|||||||admin^20141105132022+0100 OBX|1|NM|CLC00500^Pla--Glucosa; c.sust.(proc.)^SISTEMA1||65|mg/dL||HH|||F|||20141105132022||admin|||20141105132022 OBX|2|ST|CLC00500^Pla--Glucosa; c.sust.(proc.)^SISTEMA1|1|POSITIVO|||||||||20141105132022||admin SPM|1|0120000002||3^Suero||||||||||||||20141105132010||Y||||||1 How could I to know when the OBR Segment contains a Battery or a test? My first idea is the next: if OBR.4.1 = OBX.3.1, then the OBR Segment contains a Test, else OBR Segment contains a Battery. But this is a bad solution :( Help me! Best Regards. Rafael. Rafael San Vidal Hidalgo - Dpto. Sistemas de Diagnóstico Tlf.: 914702104 (ext.158) - Fax: 915261867 rsa...@fs... - www.f-soria.es AVISO DE CONFIDENCIALIDAD La información contenida en este mensaje y archivos adjuntos es privada, confidencial y de uso exclusivo de la(s) persona(s) y entidad(es) a la(s) que va dirigido. Si Ud. no es el destinatario de esta información se le notifica que está expresamente prohibida la declaración, reproducción, distribución o la toma de cualquier acción basada en el contenido de esta comunicación. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente y proceda a eliminarlo de todos sus sistemas. Francisco Soria Melguizo, S.A. no asume responsabilidad legal por el contenido de esta comunicación, ni representa la opinión de la firma, salvo que expresamente se especifique lo contrario y que el remitente esté autorizado para hacerlo. Gracias. De: Rafael San Vidal Hidalgo/GSORIA Para: Ian Vowles <Ian...@he...> cc: "hl7...@li..." <hl7...@li...> Fecha: 08/05/2014 09:36 Asunto: RE: [HAPI-devel] Parse only Segment MSH Thank you, Ian I will develope your two options. In the first option (using parser method with the first segment only), How do I get the first segment in XML Format? I would try to get the first segment looking for the </MSH> value. I will try the preparser option too, proposed by our partner James Agner. Best regards. Rafael San Vidal. Rafael San Vidal Hidalgo - Dpto. Sistemas de Diagnóstico Tlf.: 914702104 (ext.158) - Fax: 915261867 rsa...@fs... - www.f-soria.es AVISO DE CONFIDENCIALIDAD La información contenida en este mensaje y archivos adjuntos es privada, confidencial y de uso exclusivo de la(s) persona(s) y entidad(es) a la(s) que va dirigido. Si Ud. no es el destinatario de esta información se le notifica que está expresamente prohibida la declaración, reproducción, distribución o la toma de cualquier acción basada en el contenido de esta comunicación. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente y proceda a eliminarlo de todos sus sistemas. Francisco Soria Melguizo, S.A. no asume responsabilidad legal por el contenido de esta comunicación, ni representa la opinión de la firma, salvo que expresamente se especifique lo contrario y que el remitente esté autorizado para hacerlo. Gracias. RE: [HAPI-devel] Parse only Segment MSH Ian Vowles para: rsa...@fs..., hl7...@li... Enviado: 08/05/2014 00:11 Recibido: 08/05/2014 09:10 Our team often finds itself wanting to deal with individual segments. Segment constructors still require something to base themselves on, so you seem to be required to do something like this: private static ADT_A01 parent; . . . parent = new ADT_A01(); parent.initQuickstart("ADT", "A01", "P"); String message = "MSH|^~\\&|SENDING-APP|SENDING-FAC|RECEIVING-APP|RECEIVING-FAC|20140508111155|SECURITY|ADT^A08|MESSAGE-CONTROL-ID|P|2.4|||AL|AL|AUS|ASCII|ENG|\r" + "MORE SEGMENTS GO HERE IN A REAL MESSAGE\r"; System.out.println("Message Control Id = " + getUID(message)); . . . /** * Get MessageControlID * @param mensaje * @return MessageControlID */ public static String getUID(String mensaje) { try { MSH msh = new MSH(parent,parent.getModelClassFactory()); if (mensaje.indexOf("\r") > 0) { msh.parse(mensaje.substring(0, mensaje.indexOf("\r"))); } return msh.getMessageControlID().getValue(); } catch (HL7Exception e) {} return null; } If anyone can show a simpler way to create a segment from scratch, that would be most helpful. To just get amongst the MSH you could go for all string manipulation, but you have to worry about the standard. You could do something like this: /** * Get MessageControlID * @param mensaje * @return MessageControlID */ public static String getUIDNoHapi(String mensaje) { if (mensaje != null && mensaje.length() > 4 && mensaje.startsWith("MSH") && mensaje.indexOf("\r") > 0) { String msh = mensaje.substring(0, mensaje.indexOf("\r")); String fieldDel = mshsubstring(3, 4); if ("|".equals(fieldDel)) { fieldDel = "\\|"; } String[] mshFields = msh.split(fieldDel); return mshFields[9]; } return null; } There are traps in this code if people start using non standard delimiters or send you very bad content. The HAPI library is a much better to help you avoid such trouble. Thanks Ian From: rsa...@fs... [mailto:rsa...@fs...] Sent: Wednesday, 7 May 2014 6:22 PM To: Ian Vowles; hl7...@li... Subject: [HAPI-devel] Parse only Segment MSH Hi, In our source code, we parse the full message (from string data) to get the MessageControlID value. How can I get the MessageControlID value without parsing the full message (Example: parsing only the MSH Segment)? Note: I attach the "getUID" method to get this value. Best regards. Rafael. import ca.uhn.hl7v2.model.Message; import ca.uhn.hl7v2.model.v25.segment.MSH; /** * Get MessageControlID * @param mensaje * @return MessageControlID */ public static String getUID(String mensaje) { try { Parser parseador = new GenericParser(); parseador.setValidationContext(new NoValidation()); Message mensajeHAPI = parseador.parse(mensaje); MSH segmentoHAPI_MSH = (MSH) mensajeHAPI.get(Parametros.MSH); return segmentoHAPI_MSH.getMessageControlID().getValue(); } catch (Exception e) {} return null; } Rafael San Vidal Hidalgo - Dpto. Sistemas de Diagnóstico Tlf.: 914702104 (ext.158) - Fax: 915261867 rsa...@fs... - www.f-soria.es AVISO DE CONFIDENCIALIDAD La información contenida en este mensaje y archivos adjuntos es privada, confidencial y de uso exclusivo de la(s) persona(s) y entidad(es) a la(s) que va dirigido. Si Ud. no es el destinatario de esta información se le notifica que está expresamente prohibida la declaración, reproducción, distribución o la toma de cualquier acción basada en el contenido de esta comunicación. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente y proceda a eliminarlo de todos sus sistemas. Francisco Soria Melguizo, S.A. no asume responsabilidad legal por el contenido de esta comunicación, ni representa la opinión de la firma, salvo que expresamente se especifique lo contrario y que el remitente esté autorizado para hacerlo. Gracias. ******************************************************************************** This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is strictly prohibited. The information contained in this email, including any attachment sent with it, may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender by telephone collect on Australia +61 1800 198 175 or by return email. You should also delete this email, and any copies, from your computer system network and destroy any hard copies produced. If not an intended recipient of this email, you must not copy, distribute or take any action(s) that relies on it; any form of disclosure, modification, distribution and/or publication of this email is also prohibited. Although Queensland Health takes all reasonable steps to ensure this email does not contain malicious software, Queensland Health does not accept responsibility for the consequences if any person's computer inadvertently suffers any disruption to services, loss of information, harm or is infected with a virus, other malicious computer programme or code that may occur as a consequence of receiving this email. Unless stated otherwise, this email represents only the views of the sender and not the views of the Queensland Government. ********************************************************************************** ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ Hl7api-devel mailing list Hl7...@li... https://lists.sourceforge.net/lists/listinfo/hl7api-devel ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ Hl7api-devel mailing list Hl7...@li... https://lists.sourceforge.net/lists/listinfo/hl7api-devel |
|
From: Ian V. <Ian...@he...> - 2014-11-12 04:55:33
|
I thought I would give your example a try, because you had mentioned ‘phantom’ DG1s, something I hadn’t seen. Well, I hadn’t used getNames before, so I was curious.
So, yes, I did see getnames listing DG1 even when the example didn’t contain one.
I also noticed that your example message provided earlier with have zero entries in the List of DG1s because none of them have content in the identifier field.
My complete code is as follows, so you can check if I made an invalid assumption. Not I did change it somewhat.
Thanks for the opportunity to learn some more about getNames.
Printstructure is your friend. ☺
Ian
package hapiexamples;
import ca.uhn.hl7v2.DefaultHapiContext;
import ca.uhn.hl7v2.HL7Exception;
import ca.uhn.hl7v2.HapiContext;
import ca.uhn.hl7v2.model.Message;
import ca.uhn.hl7v2.model.v24.segment.DG1;
import ca.uhn.hl7v2.parser.CanonicalModelClassFactory;
import ca.uhn.hl7v2.parser.PipeParser;
import ca.uhn.hl7v2.validation.builder.support.NoValidationBuilder;
import java.util.List;
import java.util.ArrayList;
/**
*
* @author VowlesI
*/
public class Dg1ZdgExample {
/**
* @param args the command line arguments
*/
public static void main(String[] args) throws HL7Exception {
String msg = "MSH|^~\\&|SCM|SCM|HL7ADT||20130114001147||ADT^A08|8456356603013|P|2.3\r"
+ "PID||5012223067^^^Corporate Num|50730137^^^EAST MRN|300000003^^^EID|Moose^Bullwinkle^J||19091011|F||1|1 Roanoke St^^New York^NY^11111^USA^Home||(888)111-1111^^^^^888^111-1111^^Home|^^^^^^^^Cellular|ENG|W|CA|3000000039^^^EAST MRN|111165812|11119791||Hispanic Origin \r"
+ "NK1|1|Bugs^Bee|19||(888)111-1111^^^^^888^111-1111^^Home||Emergency \r"
+ "PV1||E|ERM^^^EAST MRN|Emergency|||N20714^Chris^Bob^Bruce~1907828742^^^^^^^^^^^^NPI|||REH||||Non-Health Care||0||Emergency|3000000039^^^EAST MRN|||||||||||||||||||||Clean||||20130115001000 \r"
+ "PV2||^N|ABDOMINAL PAIN NAUSEA COLD SYM OBX|1|ST|Intolerances||None Entered||||||X \r"
+ "DG1|1||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason\r"
+ "ZDG|1||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason\r"
+ "DG1|2||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason\r"
+ "ZDG|2||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason\r"
+ "DG1|3||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason\r"
+ "ZDG|3||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason\r"
+ "OBX|2|ST|Allergies||See Allergy Icon/Pt Info Tab||||||X \r"
+ "AL1|1|Drug|quinolone antibiotics^^^^23^Multum|Swelling|facial swelling ZAL||||AL|Swelling \r"
+ "AL1|2|Drug|quinolone topicals^^^^70^Multum|Swelling|facial swelling ZAL||||AL|Swelling \r"
+ "IN1|1||BLUE|BLUE CROSS^MEDICARE|PO BOX 880031^^Boston^MA^02201||(888)111-1111^^^^^888^111-1111||||||||Medicare|Bugs^Bunny^M|18|19000928|1 Roanoke St^^New York^NY^11111^USA||||||||||||||||||||||||Male||||||1112223067 \r"
+ "IN2||475846521|DISABLED||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||(888)111-1111^^Phone^^^888^111-1111|||||||DISABLED\r";
HapiContext hapiContext = new DefaultHapiContext();
hapiContext.setValidationRuleBuilder(new NoValidationBuilder());
final PipeParser pipeParser = hapiContext.getPipeParser();
final Message hapiMessage = pipeParser.parse(msg);
System.out.println("hapiMsg.printStructure() = " + hapiMessage.printStructure());
String names[] = hapiMessage.getNames();
List<DG1> dg1List = new ArrayList<DG1>();
for (String name : names) {
System.out.println("Segment Name = " + name);
if (name.startsWith("DG1")) {
DG1 dg = (DG1) hapiMessage.get(name);
if (dg != null && dg.getDg13_DiagnosisCodeDG1().getCe1_Identifier().getValue() != null) {
dg1List.add(dg);
}
}
}
System.out.println(dg1List.size());
}
}
From: Singh, Brijesh [mailto:Si...@ad...]
Sent: Wednesday, 12 November 2014 1:46 PM
To: James Agnew
Cc: hl7...@li...
Subject: Re: [HAPI-devel] DG1 segments repetition.
James – Thanks so much for a quick response. I followed your suggestion and added the code by calling getNames() as described below. I found that HAPI is creating a phantom DG1 segment even when the Hl7 message does not have any DG1, for that reason I’m doing an extra logic in the highlighted text below. Is it intended behavior? If yes, what is the best way of handling it?
String Names[] = Msg.getNames();
List<DG1> LDGs = new ArrayList<DG1>();
for(String Name: Names){
if(Name == null || Name.startsWith("DG1") == false)
continue;
DG1 DG = (DG1)Msg.get(Name);
if(DG !=null && dg.getDiagnosisCodeDG1().getIdentifier().getValue()) !=null )
LDGs.add(DG);
}
Regards,
Brijesh
From: James Agnew [mailto:jam...@gm...]
Sent: Tuesday, November 11, 2014 6:15 PM
To: Singh, Brijesh
Cc: hl7...@li...<mailto:hl7...@li...>
Subject: Re: [HAPI-devel] DG1 segments repetition.
Hi Brijesh,
You're right, the custom segments are causing an issue since the parser csn't see subsequent DG1 repetitions as actual repetitions.
The easiest way to do this would be to call
MessageInstance.getAll("DG1")
followed by
MessageInstance.getAll("DG12")
followed by
MessageInstance.getAll("DG13")
etc.. Basically HAPI creates nonstandard segments for each of the following DG1s by adding a sequential number to the end.
If you wanted to be more fancy, you could create a custom structure that has a group containing the custom segment as well, or you could override the parser and use string maniulation to remove the Z-segments before parsing.. But the method above is definitely the least work.
Incidentally MessageInstance.getNames() will give you the names of all the segments (including the "DG1[number]" ones) so you will know how many there are.
Cheers,
James
On Tue, Nov 11, 2014 at 2:06 PM, Singh, Brijesh <Si...@ad...<mailto:Si...@ad...>> wrote:
Hi – I’m using HAPI library(2.2) to parse the below message and calling the method getAll(“DG1”) ( Structure[] Structs = MessageInstance.getAll(“DG1”) ) to retrieve the DG1 segments. I’m having issues getting all DG1 segments. From the below message, able to retrieve only one DG1 segment. Looks like the custom segment (ZDG) is in the middle of repeating DG1 segments and breaking the repetition.
Can you please suggest if I can use other API methods to retrieve all DG1 ( 3 in the below case) ignoring ZDG segments?
Thanks for your help.
MSH|^~\&|SCM|SCM|HL7ADT||20130114001147||ADT^A08|8456356603013|P|2.3
PID||5012223067<tel:5012223067>^^^Corporate Num|50730137^^^EAST MRN|300000003^^^EID|Moose^Bullwinkle^J||19091011|F||1|1 Roanoke St^^New York^NY^11111^USA^Home||(888)111-1111^^^^^888^111-1111^^Home|^^^^^^^^Cellular|ENG|W|CA|3000000039^^^EAST MRN|111165812|11119791||Hispanic Origin
NK1|1|Bugs^Bee|19||(888)111-1111^^^^^888^111-1111^^Home||Emergency
PV1||E|ERM^^^EAST MRN|Emergency|||N20714^Chris^Bob^Bruce~1907828742^^^^^^^^^^^^NPI|||REH||||Non-Health Care||0||Emergency|3000000039^^^EAST MRN|||||||||||||||||||||Clean||||20130115001000
PV2||^N|ABDOMINAL PAIN NAUSEA COLD SYM OBX|1|ST|Intolerances||None Entered||||||X
DG1|1||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
ZDG|1||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
DG1|2||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
ZDG|2||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
DG1|3||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
ZDG|3||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
OBX|2|ST|Allergies||See Allergy Icon/Pt Info Tab||||||X
AL1|1|Drug|quinolone antibiotics^^^^23^Multum|Swelling|facial swelling ZAL||||AL|Swelling
AL1|2|Drug|quinolone topicals^^^^70^Multum|Swelling|facial swelling ZAL||||AL|Swelling
IN1|1||BLUE|BLUE CROSS^MEDICARE|PO BOX 880031^^Boston^MA^02201||(888)111-1111^^^^^888^111-1111||||||||Medicare|Bugs^Bunny^M|18|19000928|1 Roanoke St^^New York^NY^11111^USA||||||||||||||||||||||||Male||||||1112223067
IN2||475846521|DISABLED||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||(888)111-1111^^Phone^^^888^111-1111|||||||DISABLED
Regards,
Brijesh Singh
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Hl7api-devel mailing list
Hl7...@li...<mailto:Hl7...@li...>
https://lists.sourceforge.net/lists/listinfo/hl7api-devel
********************************************************************************
This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error.
Any unauthorised use, alteration, disclosure, distribution or review of this email is strictly prohibited. The information contained in this email, including any attachment sent with it, may be subject to a statutory duty of confidentiality if it relates to health service matters.
If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender by telephone collect on Australia +61 1800 198 175 or by return email. You should also delete this email, and any copies, from your computer system network and destroy any hard copies produced.
If not an intended recipient of this email, you must not copy, distribute or take any action(s) that relies on it; any form of disclosure, modification, distribution and/or publication of this email is also prohibited.
Although Queensland Health takes all reasonable steps to ensure this email does not contain malicious software, Queensland Health does not accept responsibility for the consequences if any person's computer inadvertently suffers any disruption to services, loss of information, harm or is infected with a virus, other malicious computer programme or code that may occur as a consequence of receiving this email.
Unless stated otherwise, this email represents only the views of the sender and not the views of the Queensland Government.
**********************************************************************************
|
|
From: Singh, B. <Si...@ad...> - 2014-11-12 03:45:39
|
James – Thanks so much for a quick response. I followed your suggestion and added the code by calling getNames() as described below. I found that HAPI is creating a phantom DG1 segment even when the Hl7 message does not have any DG1, for that reason I’m doing an extra logic in the highlighted text below. Is it intended behavior? If yes, what is the best way of handling it?
String Names[] = Msg.getNames();
List<DG1> LDGs = new ArrayList<DG1>();
for(String Name: Names){
if(Name == null || Name.startsWith("DG1") == false)
continue;
DG1 DG = (DG1)Msg.get(Name);
if(DG !=null && dg.getDiagnosisCodeDG1().getIdentifier().getValue()) !=null )
LDGs.add(DG);
}
Regards,
Brijesh
From: James Agnew [mailto:jam...@gm...]
Sent: Tuesday, November 11, 2014 6:15 PM
To: Singh, Brijesh
Cc: hl7...@li...
Subject: Re: [HAPI-devel] DG1 segments repetition.
Hi Brijesh,
You're right, the custom segments are causing an issue since the parser csn't see subsequent DG1 repetitions as actual repetitions.
The easiest way to do this would be to call
MessageInstance.getAll("DG1")
followed by
MessageInstance.getAll("DG12")
followed by
MessageInstance.getAll("DG13")
etc.. Basically HAPI creates nonstandard segments for each of the following DG1s by adding a sequential number to the end.
If you wanted to be more fancy, you could create a custom structure that has a group containing the custom segment as well, or you could override the parser and use string maniulation to remove the Z-segments before parsing.. But the method above is definitely the least work.
Incidentally MessageInstance.getNames() will give you the names of all the segments (including the "DG1[number]" ones) so you will know how many there are.
Cheers,
James
On Tue, Nov 11, 2014 at 2:06 PM, Singh, Brijesh <Si...@ad...<mailto:Si...@ad...>> wrote:
Hi – I’m using HAPI library(2.2) to parse the below message and calling the method getAll(“DG1”) ( Structure[] Structs = MessageInstance.getAll(“DG1”) ) to retrieve the DG1 segments. I’m having issues getting all DG1 segments. From the below message, able to retrieve only one DG1 segment. Looks like the custom segment (ZDG) is in the middle of repeating DG1 segments and breaking the repetition.
Can you please suggest if I can use other API methods to retrieve all DG1 ( 3 in the below case) ignoring ZDG segments?
Thanks for your help.
MSH|^~\&|SCM|SCM|HL7ADT||20130114001147||ADT^A08|8456356603013|P|2.3
PID||5012223067<tel:5012223067>^^^Corporate Num|50730137^^^EAST MRN|300000003^^^EID|Moose^Bullwinkle^J||19091011|F||1|1 Roanoke St^^New York^NY^11111^USA^Home||(888)111-1111^^^^^888^111-1111^^Home|^^^^^^^^Cellular|ENG|W|CA|3000000039^^^EAST MRN|111165812|11119791||Hispanic Origin
NK1|1|Bugs^Bee|19||(888)111-1111^^^^^888^111-1111^^Home||Emergency
PV1||E|ERM^^^EAST MRN|Emergency|||N20714^Chris^Bob^Bruce~1907828742^^^^^^^^^^^^NPI|||REH||||Non-Health Care||0||Emergency|3000000039^^^EAST MRN|||||||||||||||||||||Clean||||20130115001000
PV2||^N|ABDOMINAL PAIN NAUSEA COLD SYM OBX|1|ST|Intolerances||None Entered||||||X
DG1|1||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
ZDG|1||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
DG1|2||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
ZDG|2||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
DG1|3||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
ZDG|3||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
OBX|2|ST|Allergies||See Allergy Icon/Pt Info Tab||||||X
AL1|1|Drug|quinolone antibiotics^^^^23^Multum|Swelling|facial swelling ZAL||||AL|Swelling
AL1|2|Drug|quinolone topicals^^^^70^Multum|Swelling|facial swelling ZAL||||AL|Swelling
IN1|1||BLUE|BLUE CROSS^MEDICARE|PO BOX 880031^^Boston^MA^02201||(888)111-1111^^^^^888^111-1111||||||||Medicare|Bugs^Bunny^M|18|19000928|1 Roanoke St^^New York^NY^11111^USA||||||||||||||||||||||||Male||||||1112223067
IN2||475846521|DISABLED||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||(888)111-1111^^Phone^^^888^111-1111|||||||DISABLED
Regards,
Brijesh Singh
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Hl7api-devel mailing list
Hl7...@li...<mailto:Hl7...@li...>
https://lists.sourceforge.net/lists/listinfo/hl7api-devel
|
|
From: Ian V. <Ian...@he...> - 2014-11-12 00:57:32
|
In our team I often use the phrase “printStructure is your friend!”. If you think something like this might be happening, output a printStructure after parsing and you will see exactly where your segments are, and the DG1, DG12, DG13 James has referred to will be very apparent, as will anything considered to be ‘non-standard’. This has revealed vendors sending what look to be sensible messages with standard segments which are NOT following the standard. NTE segments being thrown into unexpected places in ORM/ORU messages have given us some trouble in the past. printStructure is your friend ☺ Ian From: James Agnew [mailto:jam...@gm...] Sent: Wednesday, 12 November 2014 10:21 AM To: Hasson, Laurent Cc: HAPI Devel List; Singh, Brijesh Subject: Re: [HAPI-devel] DG1 segments repetition. Correct. It's unintuitive for sure, but unfortunately because of the way ER7 encoding works, there is no way to tell that these pairs are a repeating group and not just two unrelated segments of the same name (like the two PID segments in an A17). James sent from my phone. On Nov 11, 2014 6:36 PM, "Hasson, Laurent" <Ha...@ad...<mailto:Ha...@ad...>> wrote: So, this is essentially expected behavior Vs. A bug? Laurent Hasson Managing Director, Realtime Clinical Systems, Strategy and Engineering The Advisory Board Company - www.advisory.com<http://www.advisory.com> Cell: 646-283-2186<tel:646-283-2186> Sent from my BlackBerry Passport. From: James Agnew Sent: Tuesday, November 11, 2014 17:16 To: Singh, Brijesh Cc: hl7...@li...<mailto:hl7...@li...> Subject: Re: [HAPI-devel] DG1 segments repetition. Hi Brijesh, You're right, the custom segments are causing an issue since the parser csn't see subsequent DG1 repetitions as actual repetitions. The easiest way to do this would be to call MessageInstance.getAll("DG1") followed by MessageInstance.getAll("DG12") followed by MessageInstance.getAll("DG13") etc.. Basically HAPI creates nonstandard segments for each of the following DG1s by adding a sequential number to the end. If you wanted to be more fancy, you could create a custom structure that has a group containing the custom segment as well, or you could override the parser and use string maniulation to remove the Z-segments before parsing.. But the method above is definitely the least work. Incidentally MessageInstance.getNames() will give you the names of all the segments (including the "DG1[number]" ones) so you will know how many there are. Cheers, James On Tue, Nov 11, 2014 at 2:06 PM, Singh, Brijesh <Si...@ad...<mailto:Si...@ad...>> wrote: Hi – I’m using HAPI library(2.2) to parse the below message and calling the method getAll(“DG1”) ( Structure[] Structs = MessageInstance.getAll(“DG1”) ) to retrieve the DG1 segments. I’m having issues getting all DG1 segments. From the below message, able to retrieve only one DG1 segment. Looks like the custom segment (ZDG) is in the middle of repeating DG1 segments and breaking the repetition. Can you please suggest if I can use other API methods to retrieve all DG1 ( 3 in the below case) ignoring ZDG segments? Thanks for your help. MSH|^~\&|SCM|SCM|HL7ADT||20130114001147||ADT^A08|8456356603013|P|2.3 PID||5012223067<tel:5012223067>^^^Corporate Num|50730137^^^EAST MRN|300000003^^^EID|Moose^Bullwinkle^J||19091011|F||1|1 Roanoke St^^New York^NY^11111^USA^Home||(888)111-1111^^^^^888^111-1111^^Home|^^^^^^^^Cellular|ENG|W|CA|3000000039^^^EAST MRN|111165812|11119791||Hispanic Origin NK1|1|Bugs^Bee|19||(888)111-1111^^^^^888^111-1111^^Home||Emergency PV1||E|ERM^^^EAST MRN|Emergency|||N20714^Chris^Bob^Bruce~1907828742^^^^^^^^^^^^NPI|||REH||||Non-Health Care||0||Emergency|3000000039^^^EAST MRN|||||||||||||||||||||Clean||||20130115001000 PV2||^N|ABDOMINAL PAIN NAUSEA COLD SYM OBX|1|ST|Intolerances||None Entered||||||X DG1|1||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason ZDG|1||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason DG1|2||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason ZDG|2||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason DG1|3||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason ZDG|3||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason OBX|2|ST|Allergies||See Allergy Icon/Pt Info Tab||||||X AL1|1|Drug|quinolone antibiotics^^^^23^Multum|Swelling|facial swelling ZAL||||AL|Swelling AL1|2|Drug|quinolone topicals^^^^70^Multum|Swelling|facial swelling ZAL||||AL|Swelling IN1|1||BLUE|BLUE CROSS^MEDICARE|PO BOX 880031^^Boston^MA^02201||(888)111-1111^^^^^888^111-1111||||||||Medicare|Bugs^Bunny^M|18|19000928|1 Roanoke St^^New York^NY^11111^USA||||||||||||||||||||||||Male||||||1112223067 IN2||475846521|DISABLED||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||(888)111-1111^^Phone^^^888^111-1111|||||||DISABLED Regards, Brijesh Singh ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ Hl7api-devel mailing list Hl7...@li...<mailto:Hl7...@li...> https://lists.sourceforge.net/lists/listinfo/hl7api-devel ******************************************************************************** This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is strictly prohibited. The information contained in this email, including any attachment sent with it, may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender by telephone collect on Australia +61 1800 198 175 or by return email. You should also delete this email, and any copies, from your computer system network and destroy any hard copies produced. If not an intended recipient of this email, you must not copy, distribute or take any action(s) that relies on it; any form of disclosure, modification, distribution and/or publication of this email is also prohibited. Although Queensland Health takes all reasonable steps to ensure this email does not contain malicious software, Queensland Health does not accept responsibility for the consequences if any person's computer inadvertently suffers any disruption to services, loss of information, harm or is infected with a virus, other malicious computer programme or code that may occur as a consequence of receiving this email. Unless stated otherwise, this email represents only the views of the sender and not the views of the Queensland Government. ********************************************************************************** |
|
From: James A. <jam...@gm...> - 2014-11-12 00:21:19
|
Correct. It's unintuitive for sure, but unfortunately because of the way ER7 encoding works, there is no way to tell that these pairs are a repeating group and not just two unrelated segments of the same name (like the two PID segments in an A17). James sent from my phone. On Nov 11, 2014 6:36 PM, "Hasson, Laurent" <Ha...@ad...> wrote: > So, this is essentially expected behavior Vs. A bug? > > > Laurent Hasson > Managing Director, Realtime Clinical Systems, Strategy and Engineering > The Advisory Board Company - www.advisory.com > Cell: 646-283-2186 > Sent from my BlackBerry Passport. > > *From: *James Agnew > *Sent: *Tuesday, November 11, 2014 17:16 > *To: *Singh, Brijesh > *Cc: *hl7...@li... > *Subject: *Re: [HAPI-devel] DG1 segments repetition. > > Hi Brijesh, > > You're right, the custom segments are causing an issue since the parser > csn't see subsequent DG1 repetitions as actual repetitions. > > The easiest way to do this would be to call > MessageInstance.getAll("DG1") > followed by > MessageInstance.getAll("DG12") > followed by > MessageInstance.getAll("DG13") > etc.. Basically HAPI creates nonstandard segments for each of the > following DG1s by adding a sequential number to the end. > > If you wanted to be more fancy, you could create a custom structure that > has a group containing the custom segment as well, or you could override > the parser and use string maniulation to remove the Z-segments before > parsing.. But the method above is definitely the least work. > > Incidentally MessageInstance.getNames() will give you the names of all > the segments (including the "DG1[number]" ones) so you will know how many > there are. > > Cheers, > James > > On Tue, Nov 11, 2014 at 2:06 PM, Singh, Brijesh <Si...@ad...> > wrote: > >> Hi – I’m using HAPI library(2.2) to parse the below message and calling >> the method getAll(“DG1”) ( *Structure[] Structs = >> MessageInstance.getAll(“DG1”)* ) to retrieve the DG1 segments. I’m >> having issues getting all DG1 segments. From the below message, able to >> retrieve only one DG1 segment. Looks like the custom segment (ZDG) is in >> the middle of repeating DG1 segments and breaking the repetition. >> >> >> >> Can you please suggest if I can use other API methods to retrieve all DG1 >> ( 3 in the below case) ignoring ZDG segments? >> >> >> >> Thanks for your help. >> >> >> >> >> >> MSH|^~\&|SCM|SCM|HL7ADT||20130114001147||ADT^A08|8456356603013|P|2.3 >> >> PID||5012223067^^^Corporate Num|50730137^^^EAST >> MRN|300000003^^^EID|Moose^Bullwinkle^J||19091011|F||1|1 Roanoke St^^New >> York^NY^11111^USA^Home||(888)111-1111^^^^^888^111-1111^^Home|^^^^^^^^Cellular|ENG|W|CA|3000000039^^^EAST >> MRN|111165812|11119791||Hispanic Origin >> >> NK1|1|Bugs^Bee|19||(888)111-1111^^^^^888^111-1111^^Home||Emergency >> >> PV1||E|ERM^^^EAST >> MRN|Emergency|||N20714^Chris^Bob^Bruce~1907828742^^^^^^^^^^^^NPI|||REH||||Non-Health >> Care||0||Emergency|3000000039^^^EAST >> MRN|||||||||||||||||||||Clean||||20130115001000 >> >> PV2||^N|ABDOMINAL PAIN NAUSEA COLD SYM OBX|1|ST|Intolerances||None >> Entered||||||X >> >> *DG1|1||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION >> NAUSE||Visit Reason* >> >> *ZDG|1||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION >> NAUSE||Visit Reason* >> >> *DG1|2||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION >> NAUSE||Visit Reason* >> >> *ZDG|2||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION >> NAUSE||Visit Reason* >> >> DG1|3||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION >> NAUSE||Visit Reason >> >> ZDG|3||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION >> NAUSE||Visit Reason >> >> OBX|2|ST|Allergies||See Allergy Icon/Pt Info Tab||||||X >> >> AL1|1|Drug|quinolone antibiotics^^^^23^Multum|Swelling|facial swelling >> ZAL||||AL|Swelling >> >> AL1|2|Drug|quinolone topicals^^^^70^Multum|Swelling|facial swelling >> ZAL||||AL|Swelling >> >> IN1|1||BLUE|BLUE CROSS^MEDICARE|PO BOX >> 880031^^Boston^MA^02201||(888)111-1111^^^^^888^111-1111||||||||Medicare|Bugs^Bunny^M|18|19000928|1 >> Roanoke St^^New >> York^NY^11111^USA||||||||||||||||||||||||Male||||||1112223067 >> >> >> IN2||475846521|DISABLED||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||(888)111-1111^^Phone^^^888^111-1111|||||||DISABLED >> >> >> >> Regards, >> >> Brijesh Singh >> >> >> >> ------------------------------------------------------------------------------ >> Comprehensive Server Monitoring with Site24x7. >> Monitor 10 servers for $9/Month. >> Get alerted through email, SMS, voice calls or mobile push notifications. >> Take corrective actions from your mobile device. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk >> _______________________________________________ >> Hl7api-devel mailing list >> Hl7...@li... >> https://lists.sourceforge.net/lists/listinfo/hl7api-devel >> >> > |
|
From: Ian V. <Ian...@he...> - 2014-11-12 00:10:58
|
I can second James’ additional alternatives, having successfully coded several custom structures, and also pulled out Z-segments via string manipulation before parsing into a standard HAPI structure.
Hope it goes well
Ian
From: James Agnew [mailto:jam...@gm...]
Sent: Wednesday, 12 November 2014 9:15 AM
To: Singh, Brijesh
Cc: hl7...@li...
Subject: Re: [HAPI-devel] DG1 segments repetition.
Hi Brijesh,
You're right, the custom segments are causing an issue since the parser csn't see subsequent DG1 repetitions as actual repetitions.
The easiest way to do this would be to call
MessageInstance.getAll("DG1")
followed by
MessageInstance.getAll("DG12")
followed by
MessageInstance.getAll("DG13")
etc.. Basically HAPI creates nonstandard segments for each of the following DG1s by adding a sequential number to the end.
If you wanted to be more fancy, you could create a custom structure that has a group containing the custom segment as well, or you could override the parser and use string maniulation to remove the Z-segments before parsing.. But the method above is definitely the least work.
Incidentally MessageInstance.getNames() will give you the names of all the segments (including the "DG1[number]" ones) so you will know how many there are.
Cheers,
James
On Tue, Nov 11, 2014 at 2:06 PM, Singh, Brijesh <Si...@ad...<mailto:Si...@ad...>> wrote:
Hi – I’m using HAPI library(2.2) to parse the below message and calling the method getAll(“DG1”) ( Structure[] Structs = MessageInstance.getAll(“DG1”) ) to retrieve the DG1 segments. I’m having issues getting all DG1 segments. From the below message, able to retrieve only one DG1 segment. Looks like the custom segment (ZDG) is in the middle of repeating DG1 segments and breaking the repetition.
Can you please suggest if I can use other API methods to retrieve all DG1 ( 3 in the below case) ignoring ZDG segments?
Thanks for your help.
MSH|^~\&|SCM|SCM|HL7ADT||20130114001147||ADT^A08|8456356603013|P|2.3
PID||5012223067<tel:5012223067>^^^Corporate Num|50730137^^^EAST MRN|300000003^^^EID|Moose^Bullwinkle^J||19091011|F||1|1 Roanoke St^^New York^NY^11111^USA^Home||(888)111-1111^^^^^888^111-1111^^Home|^^^^^^^^Cellular|ENG|W|CA|3000000039^^^EAST MRN|111165812|11119791||Hispanic Origin
NK1|1|Bugs^Bee|19||(888)111-1111^^^^^888^111-1111^^Home||Emergency
PV1||E|ERM^^^EAST MRN|Emergency|||N20714^Chris^Bob^Bruce~1907828742^^^^^^^^^^^^NPI|||REH||||Non-Health Care||0||Emergency|3000000039^^^EAST MRN|||||||||||||||||||||Clean||||20130115001000
PV2||^N|ABDOMINAL PAIN NAUSEA COLD SYM OBX|1|ST|Intolerances||None Entered||||||X
DG1|1||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
ZDG|1||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
DG1|2||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
ZDG|2||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
DG1|3||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
ZDG|3||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
OBX|2|ST|Allergies||See Allergy Icon/Pt Info Tab||||||X
AL1|1|Drug|quinolone antibiotics^^^^23^Multum|Swelling|facial swelling ZAL||||AL|Swelling
AL1|2|Drug|quinolone topicals^^^^70^Multum|Swelling|facial swelling ZAL||||AL|Swelling
IN1|1||BLUE|BLUE CROSS^MEDICARE|PO BOX 880031^^Boston^MA^02201||(888)111-1111^^^^^888^111-1111||||||||Medicare|Bugs^Bunny^M|18|19000928|1 Roanoke St^^New York^NY^11111^USA||||||||||||||||||||||||Male||||||1112223067
IN2||475846521|DISABLED||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||(888)111-1111^^Phone^^^888^111-1111|||||||DISABLED
Regards,
Brijesh Singh
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Hl7api-devel mailing list
Hl7...@li...<mailto:Hl7...@li...>
https://lists.sourceforge.net/lists/listinfo/hl7api-devel
********************************************************************************
This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error.
Any unauthorised use, alteration, disclosure, distribution or review of this email is strictly prohibited. The information contained in this email, including any attachment sent with it, may be subject to a statutory duty of confidentiality if it relates to health service matters.
If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender by telephone collect on Australia +61 1800 198 175 or by return email. You should also delete this email, and any copies, from your computer system network and destroy any hard copies produced.
If not an intended recipient of this email, you must not copy, distribute or take any action(s) that relies on it; any form of disclosure, modification, distribution and/or publication of this email is also prohibited.
Although Queensland Health takes all reasonable steps to ensure this email does not contain malicious software, Queensland Health does not accept responsibility for the consequences if any person's computer inadvertently suffers any disruption to services, loss of information, harm or is infected with a virus, other malicious computer programme or code that may occur as a consequence of receiving this email.
Unless stated otherwise, this email represents only the views of the sender and not the views of the Queensland Government.
**********************************************************************************
|
|
From: James A. <jam...@gm...> - 2014-11-11 23:15:54
|
Hi Brijesh,
You're right, the custom segments are causing an issue since the parser
csn't see subsequent DG1 repetitions as actual repetitions.
The easiest way to do this would be to call
MessageInstance.getAll("DG1")
followed by
MessageInstance.getAll("DG12")
followed by
MessageInstance.getAll("DG13")
etc.. Basically HAPI creates nonstandard segments for each of the following
DG1s by adding a sequential number to the end.
If you wanted to be more fancy, you could create a custom structure that
has a group containing the custom segment as well, or you could override
the parser and use string maniulation to remove the Z-segments before
parsing.. But the method above is definitely the least work.
Incidentally MessageInstance.getNames() will give you the names of all the
segments (including the "DG1[number]" ones) so you will know how many there
are.
Cheers,
James
On Tue, Nov 11, 2014 at 2:06 PM, Singh, Brijesh <Si...@ad...> wrote:
> Hi – I’m using HAPI library(2.2) to parse the below message and calling
> the method getAll(“DG1”) ( *Structure[] Structs =
> MessageInstance.getAll(“DG1”)* ) to retrieve the DG1 segments. I’m having
> issues getting all DG1 segments. From the below message, able to retrieve
> only one DG1 segment. Looks like the custom segment (ZDG) is in the middle
> of repeating DG1 segments and breaking the repetition.
>
>
>
> Can you please suggest if I can use other API methods to retrieve all DG1
> ( 3 in the below case) ignoring ZDG segments?
>
>
>
> Thanks for your help.
>
>
>
>
>
> MSH|^~\&|SCM|SCM|HL7ADT||20130114001147||ADT^A08|8456356603013|P|2.3
>
> PID||5012223067^^^Corporate Num|50730137^^^EAST
> MRN|300000003^^^EID|Moose^Bullwinkle^J||19091011|F||1|1 Roanoke St^^New
> York^NY^11111^USA^Home||(888)111-1111^^^^^888^111-1111^^Home|^^^^^^^^Cellular|ENG|W|CA|3000000039^^^EAST
> MRN|111165812|11119791||Hispanic Origin
>
> NK1|1|Bugs^Bee|19||(888)111-1111^^^^^888^111-1111^^Home||Emergency
>
> PV1||E|ERM^^^EAST
> MRN|Emergency|||N20714^Chris^Bob^Bruce~1907828742^^^^^^^^^^^^NPI|||REH||||Non-Health
> Care||0||Emergency|3000000039^^^EAST
> MRN|||||||||||||||||||||Clean||||20130115001000
>
> PV2||^N|ABDOMINAL PAIN NAUSEA COLD SYM OBX|1|ST|Intolerances||None
> Entered||||||X
>
> *DG1|1||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION
> NAUSE||Visit Reason*
>
> *ZDG|1||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION
> NAUSE||Visit Reason*
>
> *DG1|2||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION
> NAUSE||Visit Reason*
>
> *ZDG|2||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION
> NAUSE||Visit Reason*
>
> DG1|3||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION
> NAUSE||Visit Reason
>
> ZDG|3||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION
> NAUSE||Visit Reason
>
> OBX|2|ST|Allergies||See Allergy Icon/Pt Info Tab||||||X
>
> AL1|1|Drug|quinolone antibiotics^^^^23^Multum|Swelling|facial swelling
> ZAL||||AL|Swelling
>
> AL1|2|Drug|quinolone topicals^^^^70^Multum|Swelling|facial swelling
> ZAL||||AL|Swelling
>
> IN1|1||BLUE|BLUE CROSS^MEDICARE|PO BOX
> 880031^^Boston^MA^02201||(888)111-1111^^^^^888^111-1111||||||||Medicare|Bugs^Bunny^M|18|19000928|1
> Roanoke St^^New
> York^NY^11111^USA||||||||||||||||||||||||Male||||||1112223067
>
>
> IN2||475846521|DISABLED||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||(888)111-1111^^Phone^^^888^111-1111|||||||DISABLED
>
>
>
> Regards,
>
> Brijesh Singh
>
>
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>
>
|
|
From: Singh, B. <Si...@ad...> - 2014-11-11 19:29:20
|
Hi - I'm using HAPI library(2.2) to parse the below message and calling the method getAll("DG1") ( Structure[] Structs = MessageInstance.getAll("DG1") ) to retrieve the DG1 segments. I'm having issues getting all DG1 segments. From the below message, able to retrieve only one DG1 segment. Looks like the custom segment (ZDG) is in the middle of repeating DG1 segments and breaking the repetition.
Can you please suggest if I can use other API methods to retrieve all DG1 ( 3 in the below case) ignoring ZDG segments?
Thanks for your help.
MSH|^~\&|SCM|SCM|HL7ADT||20130114001147||ADT^A08|8456356603013|P|2.3
PID||5012223067^^^Corporate Num|50730137^^^EAST MRN|300000003^^^EID|Moose^Bullwinkle^J||19091011|F||1|1 Roanoke St^^New York^NY^11111^USA^Home||(888)111-1111^^^^^888^111-1111^^Home|^^^^^^^^Cellular|ENG|W|CA|3000000039^^^EAST MRN|111165812|11119791||Hispanic Origin
NK1|1|Bugs^Bee|19||(888)111-1111^^^^^888^111-1111^^Home||Emergency
PV1||E|ERM^^^EAST MRN|Emergency|||N20714^Chris^Bob^Bruce~1907828742^^^^^^^^^^^^NPI|||REH||||Non-Health Care||0||Emergency|3000000039^^^EAST MRN|||||||||||||||||||||Clean||||20130115001000
PV2||^N|ABDOMINAL PAIN NAUSEA COLD SYM OBX|1|ST|Intolerances||None Entered||||||X
DG1|1||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
ZDG|1||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
DG1|2||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
ZDG|2||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
DG1|3||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
ZDG|3||^CHEST PAIN DEHYDRATION NAUSE|CHEST PAIN DEHYDRATION NAUSE||Visit Reason
OBX|2|ST|Allergies||See Allergy Icon/Pt Info Tab||||||X
AL1|1|Drug|quinolone antibiotics^^^^23^Multum|Swelling|facial swelling ZAL||||AL|Swelling
AL1|2|Drug|quinolone topicals^^^^70^Multum|Swelling|facial swelling ZAL||||AL|Swelling
IN1|1||BLUE|BLUE CROSS^MEDICARE|PO BOX 880031^^Boston^MA^02201||(888)111-1111^^^^^888^111-1111||||||||Medicare|Bugs^Bunny^M|18|19000928|1 Roanoke St^^New York^NY^11111^USA||||||||||||||||||||||||Male||||||1112223067
IN2||475846521|DISABLED||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||(888)111-1111^^Phone^^^888^111-1111|||||||DISABLED
Regards,
Brijesh Singh
|
|
From: pablo p. <paz...@ho...> - 2014-11-11 17:36:55
|
Hi Rafael, the messages seem correct. IMO your system and the sender system might need to agree on the codes and have some kind of table that tells you which codes are for batteries and which ones are for individual results, but that's outside the messages. So in OBR-4 you might use those codes and use the lookup table to know which are batteries and which not. If you need that inside the messages you might use a Z segment or a NTE associated with the OBR. Hope that helps! -- Kind regards, Eng. Pablo Pazos Gutiérrez http://cabolabs.com From: jam...@gm... Date: Tue, 11 Nov 2014 12:04:37 -0500 To: rsa...@fs... CC: hl7...@li...; bom...@fs... Subject: Re: [HAPI-devel] ORU^R01 Message: Battery and its testsdf Hi Rafael, (Other people please chime in too! I'm hardly a lab expert..) One of the joys of HL7 v2 is that a lot of the standard is loose and subject to interpretation, which means that often there isn't a right answer to how something works in the specification, you need to understand how the sender/receiver is using it. This is one of those cases. Based on the samples you have provided it seems like your interpretation is correct.. but really only the sender would know for sure. Cheers, James On Tue, Nov 11, 2014 at 10:33 AM, <rsa...@fs...> wrote: Hi, I have received the next ORU^R01 message: MSH|^~\&|MG|MG|LAB|LAB|20100127101236+0100||ORU^R01^ORU_R01|1234567890|P|2.5 PID|... PV1|... ORC|... OBR|1|OP2|10101010|HEM^Hemograma^SISTEMA1|... OBX|1|NM|HTIE^Hematíes^SISTEMA1||7.00|x10*6/uL|4.5 - 5.9|HH|||F|||20100127095652 OBX|2|NM|HGB^Hemoglobina^SISTEMA1||567567.0|g/dL|13.0 - 17.5|HH|||F|||20100127095652 OBX|3|NM|HTCO^Hematocrito^SISTEMA1||77.0|%|37.0 - 53.0|HH|||F|||20100127095728 OBX|4|NM|VCM^VCM^SISTEMA1||67.0|fl|80.0 - 100.0|LL|||F|||20100127095728 SPM|1|9018000088||^SANGRE PERIFERICA||||||||||||||20100127095625||Y||||||1 In this message, the OBR Segment contains a Battery (HEM) and the tests have been added in OBX Segments. In this case, the HEM Battery contains 4 tests (HTIE, HGB, HTCO and VCM). I would like to know if this message is a Standard HL7 Message. At the moment, I have only received tests in ORU^R01 messages. In the next ORU^R01 message, I have received a test (CLC00500) with two results (OBX.1 and OBX.2 segments): MSH|^~\&|MG|MG|FSM|FSM|20141105132023+0100||ORU^R01^ORU_R01|LAB31415190023385|P|2.5 PID|... PV1|... ORC|... OBR|1|PA5999171|20000002|CLC00500^Pla--Glucosa; c.sust.(proc.)^SISTEMA1||||||CE||||||00010258960^ape1 ape2, nombre||||5||||LAB|F|||||||admin^20141105132022+0100 OBX|1|NM|CLC00500^Pla--Glucosa; c.sust.(proc.)^SISTEMA1||65|mg/dL||HH|||F|||20141105132022||admin|||20141105132022 OBX|2|ST|CLC00500^Pla--Glucosa; c.sust.(proc.)^SISTEMA1|1|POSITIVO|||||||||20141105132022||admin SPM|1|0120000002||3^Suero||||||||||||||20141105132010||Y||||||1 How could I to know when the OBR Segment contains a Battery or a test? My first idea is the next: if OBR.4.1 = OBX.3.1, then the OBR Segment contains a Test, else OBR Segment contains a Battery. But this is a bad solution :( Help me! Best Regards. Rafael. Rafael San Vidal Hidalgo - Dpto. Sistemas de Diagnóstico Tlf.: 914702104 (ext.158) - Fax: 915261867 rsa...@fs... - www.f-soria.es AVISO DE CONFIDENCIALIDAD La información contenida en este mensaje y archivos adjuntos es privada, confidencial y de uso exclusivo de la(s) persona(s) y entidad(es) a la(s) que va dirigido. Si Ud. no es el destinatario de esta información se le notifica que está expresamente prohibida la declaración, reproducción, distribución o la toma de cualquier acción basada en el contenido de esta comunicación. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente y proceda a eliminarlo de todos sus sistemas. Francisco Soria Melguizo, S.A. no asume responsabilidad legal por el contenido de esta comunicación, ni representa la opinión de la firma, salvo que expresamente se especifique lo contrario y que el remitente esté autorizado para hacerlo. Gracias. De: Rafael San Vidal Hidalgo/GSORIA Para: Ian Vowles <Ian...@he...> cc: "hl7...@li..." <hl7...@li...> Fecha: 08/05/2014 09:36 Asunto: RE: [HAPI-devel] Parse only Segment MSH Thank you, Ian I will develope your two options. In the first option (using parser method with the first segment only), How do I get the first segment in XML Format? I would try to get the first segment looking for the </MSH> value. I will try the preparser option too, proposed by our partner James Agner. Best regards. Rafael San Vidal. Rafael San Vidal Hidalgo - Dpto. Sistemas de Diagnóstico Tlf.: 914702104 (ext.158) - Fax: 915261867 rsa...@fs... - www.f-soria.es AVISO DE CONFIDENCIALIDAD La información contenida en este mensaje y archivos adjuntos es privada, confidencial y de uso exclusivo de la(s) persona(s) y entidad(es) a la(s) que va dirigido. Si Ud. no es el destinatario de esta información se le notifica que está expresamente prohibida la declaración, reproducción, distribución o la toma de cualquier acción basada en el contenido de esta comunicación. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente y proceda a eliminarlo de todos sus sistemas. Francisco Soria Melguizo, S.A. no asume responsabilidad legal por el contenido de esta comunicación, ni representa la opinión de la firma, salvo que expresamente se especifique lo contrario y que el remitente esté autorizado para hacerlo. Gracias. RE: [HAPI-devel] Parse only Segment MSH Ian Vowles para: rsa...@fs..., hl7...@li... Enviado: 08/05/2014 00:11 Recibido: 08/05/2014 09:10 Our team often finds itself wanting to deal with individual segments. Segment constructors still require something to base themselves on, so you seem to be required to do something like this: private static ADT_A01 parent; . . . parent = new ADT_A01(); parent.initQuickstart("ADT", "A01", "P"); String message = "MSH|^~\\&|SENDING-APP|SENDING-FAC|RECEIVING-APP|RECEIVING-FAC|20140508111155|SECURITY|ADT^A08|MESSAGE-CONTROL-ID|P|2.4|||AL|AL|AUS|ASCII|ENG|\r" + "MORE SEGMENTS GO HERE IN A REAL MESSAGE\r"; System.out.println("Message Control Id = " + getUID(message)); . . . /** * Get MessageControlID * @param mensaje * @return MessageControlID */ public static String getUID(String mensaje) { try { MSH msh = new MSH(parent,parent.getModelClassFactory()); if (mensaje.indexOf("\r") > 0) { msh.parse(mensaje.substring(0, mensaje.indexOf("\r"))); } return msh.getMessageControlID().getValue(); } catch (HL7Exception e) {} return null; } If anyone can show a simpler way to create a segment from scratch, that would be most helpful. To just get amongst the MSH you could go for all string manipulation, but you have to worry about the standard. You could do something like this: /** * Get MessageControlID * @param mensaje * @return MessageControlID */ public static String getUIDNoHapi(String mensaje) { if (mensaje != null && mensaje.length() > 4 && mensaje.startsWith("MSH") && mensaje.indexOf("\r") > 0) { String msh = mensaje.substring(0, mensaje.indexOf("\r")); String fieldDel = mshsubstring(3, 4); if ("|".equals(fieldDel)) { fieldDel = "\\|"; } String[] mshFields = msh.split(fieldDel); return mshFields[9]; } return null; } There are traps in this code if people start using non standard delimiters or send you very bad content. The HAPI library is a much better to help you avoid such trouble. Thanks Ian From: rsa...@fs... [mailto:rsa...@fs...] Sent: Wednesday, 7 May 2014 6:22 PM To: Ian Vowles; hl7...@li... Subject: [HAPI-devel] Parse only Segment MSH Hi, In our source code, we parse the full message (from string data) to get the MessageControlID value. How can I get the MessageControlID value without parsing the full message (Example: parsing only the MSH Segment)? Note: I attach the "getUID" method to get this value. Best regards. Rafael. import ca.uhn.hl7v2.model.Message; import ca.uhn.hl7v2.model.v25.segment.MSH; /** * Get MessageControlID * @param mensaje * @return MessageControlID */ public static String getUID(String mensaje) { try { Parser parseador = new GenericParser(); parseador.setValidationContext(new NoValidation()); Message mensajeHAPI = parseador.parse(mensaje); MSH segmentoHAPI_MSH = (MSH) mensajeHAPI.get(Parametros.MSH); return segmentoHAPI_MSH.getMessageControlID().getValue(); } catch (Exception e) {} return null; } Rafael San Vidal Hidalgo - Dpto. Sistemas de Diagnóstico Tlf.: 914702104 (ext.158) - Fax: 915261867 rsa...@fs... - www.f-soria.es AVISO DE CONFIDENCIALIDAD La información contenida en este mensaje y archivos adjuntos es privada, confidencial y de uso exclusivo de la(s) persona(s) y entidad(es) a la(s) que va dirigido. Si Ud. no es el destinatario de esta información se le notifica que está expresamente prohibida la declaración, reproducción, distribución o la toma de cualquier acción basada en el contenido de esta comunicación. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente y proceda a eliminarlo de todos sus sistemas. Francisco Soria Melguizo, S.A. no asume responsabilidad legal por el contenido de esta comunicación, ni representa la opinión de la firma, salvo que expresamente se especifique lo contrario y que el remitente esté autorizado para hacerlo. Gracias. ******************************************************************************** This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is strictly prohibited. The information contained in this email, including any attachment sent with it, may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender by telephone collect on Australia +61 1800 198 175 or by return email. You should also delete this email, and any copies, from your computer system network and destroy any hard copies produced. If not an intended recipient of this email, you must not copy, distribute or take any action(s) that relies on it; any form of disclosure, modification, distribution and/or publication of this email is also prohibited. Although Queensland Health takes all reasonable steps to ensure this email does not contain malicious software, Queensland Health does not accept responsibility for the consequences if any person's computer inadvertently suffers any disruption to services, loss of information, harm or is infected with a virus, other malicious computer programme or code that may occur as a consequence of receiving this email. Unless stated otherwise, this email represents only the views of the sender and not the views of the Queensland Government. ********************************************************************************** ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ Hl7api-devel mailing list Hl7...@li... https://lists.sourceforge.net/lists/listinfo/hl7api-devel ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ Hl7api-devel mailing list Hl7...@li... https://lists.sourceforge.net/lists/listinfo/hl7api-devel |
|
From: James A. <jam...@gm...> - 2014-11-11 17:05:09
|
Hi Rafael, (Other people please chime in too! I'm hardly a lab expert..) One of the joys of HL7 v2 is that a lot of the standard is loose and subject to interpretation, which means that often there isn't a right answer to how something works in the specification, you need to understand how the sender/receiver is using it. This is one of those cases. Based on the samples you have provided it seems like your interpretation is correct.. but really only the sender would know for sure. Cheers, James On Tue, Nov 11, 2014 at 10:33 AM, <rsa...@fs...> wrote: > > Hi, I have received the next ORU^R01 message: > > > MSH|^~\&|MG|MG|LAB|LAB|20100127101236+0100||ORU^R01^ORU_R01|1234567890|P|2.5 > PID|... > PV1|... > ORC|... > OBR|1|OP2|10101010|HEM^Hemograma^SISTEMA1|... > OBX|1|NM|HTIE^Hematíes^SISTEMA1||7.00|x10*6/uL|4.5 - > 5.9|HH|||F|||20100127095652 > OBX|2|NM|HGB^Hemoglobina^SISTEMA1||567567.0|g/dL|13.0 - > 17.5|HH|||F|||20100127095652 > OBX|3|NM|HTCO^Hematocrito^SISTEMA1||77.0|%|37.0 - > 53.0|HH|||F|||20100127095728 > OBX|4|NM|VCM^VCM^SISTEMA1||67.0|fl|80.0 - 100.0|LL|||F|||20100127095728 > SPM|1|9018000088||^SANGRE PERIFERICA||||||||||||||20100127095625||Y||||||1 > > In this message, the OBR Segment contains a Battery (HEM) and the tests > have been added in OBX Segments. > In this case, the HEM Battery contains 4 tests (HTIE, HGB, HTCO and VCM). > > *I would like to know if this message is a Standard HL7 Message.* > At the moment, I have only received tests in ORU^R01 messages. > > In the next ORU^R01 message, I have received a test (CLC00500) with two > results (OBX.1 and OBX.2 segments): > > > MSH|^~\&|MG|MG|FSM|FSM|20141105132023+0100||ORU^R01^ORU_R01|LAB31415190023385|P|2.5 > PID|... > PV1|... > ORC|... > OBR|1|PA5999171|20000002|CLC00500^Pla--Glucosa; > c.sust.(proc.)^SISTEMA1||||||CE||||||00010258960^ape1 ape2, > nombre||||5||||LAB|F|||||||admin^20141105132022+0100 > OBX|1|NM|CLC00500^Pla--Glucosa; > c.sust.(proc.)^SISTEMA1||65|mg/dL||HH|||F|||20141105132022||admin|||20141105132022 > OBX|2|ST|CLC00500^Pla--Glucosa; > c.sust.(proc.)^SISTEMA1|1|POSITIVO|||||||||20141105132022||admin > SPM|1|0120000002||3^Suero||||||||||||||20141105132010||Y||||||1 > > *How could I to know when the OBR Segment contains a Battery or a test?* > *My first idea is the next: if OBR.4.1 = OBX.3.1, then the OBR Segment > contains a Test, else OBR Segment contains a Battery. But this is a bad > solution :(* > > Help me! > Best Regards. > Rafael. > > > > > * Rafael San Vidal Hidalgo - Dpto. Sistemas de Diagnóstico * > * Tlf.: 914702104 (ext.158) - Fax: 915261867 * > *rsa...@fs... * <rsa...@fs...>*- **www.f-soria.es * > <http://www.f-soria.es/> > > *AVISO DE CONFIDENCIALIDAD * > > ------------------------------ > La información contenida en este mensaje y archivos adjuntos es privada, > confidencial y de uso exclusivo de la(s) persona(s) y entidad(es) a la(s) > que va dirigido. Si Ud. no es el destinatario de esta información se le > notifica que está expresamente prohibida la declaración, reproducción, > distribución o la toma de cualquier acción basada en el contenido de esta > comunicación. Si ha recibido este mensaje por error, le rogamos que nos lo > comunique inmediatamente y proceda a eliminarlo de todos sus sistemas. > Francisco Soria Melguizo, S.A. no asume responsabilidad legal por el > contenido de esta comunicación, ni representa la opinión de la firma, salvo > que expresamente se especifique lo contrario y que el remitente esté > autorizado para hacerlo. Gracias. > > > > De: Rafael San Vidal Hidalgo/GSORIA Para: Ian Vowles < > Ian...@he...> cc: "hl7...@li..." < > hl7...@li...> Fecha: 08/05/2014 09:36 Asunto: RE: > [HAPI-devel] Parse only Segment MSH > ------------------------------ > > > Thank you, Ian > I will develope your two options. > > In the first option (using parser method with the first segment only), How > do I get the first segment in XML Format? > I would try to get the first segment looking for the </MSH> value. > I will try the preparser option too, proposed by our partner James Agner. > > Best regards. > Rafael San Vidal. > > > * Rafael San Vidal Hidalgo - Dpto. Sistemas de Diagnóstico * > * Tlf.: 914702104 (ext.158) - Fax: 915261867 * > *rsa...@fs... * <rsa...@fs...>*- **www.f-soria.es * > <http://www.f-soria.es/> > > *AVISO DE CONFIDENCIALIDAD * > > ------------------------------ > La información contenida en este mensaje y archivos adjuntos es privada, > confidencial y de uso exclusivo de la(s) persona(s) y entidad(es) a la(s) > que va dirigido. Si Ud. no es el destinatario de esta información se le > notifica que está expresamente prohibida la declaración, reproducción, > distribución o la toma de cualquier acción basada en el contenido de esta > comunicación. Si ha recibido este mensaje por error, le rogamos que nos lo > comunique inmediatamente y proceda a eliminarlo de todos sus sistemas. > Francisco Soria Melguizo, S.A. no asume responsabilidad legal por el > contenido de esta comunicación, ni representa la opinión de la firma, salvo > que expresamente se especifique lo contrario y que el remitente esté > autorizado para hacerlo. Gracias. > > > > > *RE: [HAPI-devel] Parse only Segment MSH* > *Ian Vowles * para: rsa...@fs..., > hl7...@li... > Enviado: 08/05/2014 00:11 > Recibido: 08/05/2014 09:10 > > > > ------------------------------ > > > > Our team often finds itself wanting to deal with individual segments. > Segment constructors still require something to base themselves on, so you > seem to be required to do something like this: > > private static ADT_A01 parent; > . > . > . > parent = new ADT_A01(); > parent.initQuickstart("ADT", "A01", "P"); > String message = > "MSH|^~\\&|SENDING-APP|SENDING-FAC|RECEIVING-APP|RECEIVING-FAC|20140508111155|SECURITY|ADT^A08|MESSAGE-CONTROL-ID|P|2.4|||AL|AL|AUS|ASCII|ENG|\r" > + "MORE SEGMENTS GO HERE IN A REAL MESSAGE\r"; > System.out.println("Message Control Id = " + getUID(message)); > . > . > . > > /** > * Get MessageControlID > * @param mensaje > * @return MessageControlID > */ > public static String getUID(String mensaje) > { > try > { > MSH msh = new > MSH(parent,parent.getModelClassFactory()); > if (mensaje.indexOf("\r") > 0) { > msh.parse(mensaje.substring(0, > mensaje.indexOf("\r"))); > } > return msh.getMessageControlID().getValue(); > } > catch (HL7Exception e) {} > return null; > } > > If anyone can show a simpler way to create a segment from scratch, that > would be most helpful. > > To just get amongst the MSH you could go for all string manipulation, but > you have to worry about the standard. You could do something like this: > > /** > * Get MessageControlID > * @param mensaje > * @return MessageControlID > */ > public static String getUIDNoHapi(String mensaje) > { > if (mensaje != null && mensaje.length() > 4 && > mensaje.startsWith("MSH") && mensaje.indexOf("\r") > 0) { > String msh = mensaje.substring(0, mensaje.indexOf("\r")); > String fieldDel = mshsubstring(3, 4); > if ("|".equals(fieldDel)) { > fieldDel = "\\|"; > } > String[] mshFields = msh.split(fieldDel); > return mshFields[9]; > } > return null; > } > > > There are traps in this code if people start using non standard delimiters > or send you very bad content. The HAPI library is a much better to help you > avoid such trouble. > > Thanks > Ian > > *From:* rsa...@fs... [mailto:rsa...@fs... > <rsa...@fs...>] > * Sent:* Wednesday, 7 May 2014 6:22 PM > * To:* Ian Vowles; hl7...@li... > * Subject:* [HAPI-devel] Parse only Segment MSH > > > Hi, > In our source code, we parse the full message (from string data) to get > the MessageControlID value. > How can I get the MessageControlID value without parsing the full message > (Example: parsing only the MSH Segment)? > > Note: I attach the "getUID" method to get this value. > Best regards. > Rafael. > > > * import* ca.uhn.hl7v2.model.Message; > * import* ca.uhn.hl7v2.model.v25.segment.MSH; > > /** > * Get MessageControlID > * *@param* mensaje > * *@return* MessageControlID > */ > *public* *static* String getUID(String mensaje) > { > *try* > { > Parser parseador = *new* GenericParser(); > parseador.*setValidationContext(**new** > NoValidation())*; > > Message mensajeHAPI = parseador.parse(mensaje); > > MSH segmentoHAPI_MSH = (MSH) > mensajeHAPI.get(Parametros.*MSH*); > *return* > segmentoHAPI_MSH.getMessageControlID().getValue(); > } > *catch* (Exception e) {} > *return* *null*; > } > > > > * Rafael San Vidal Hidalgo - Dpto. Sistemas de Diagnóstico * > * Tlf.: 914702104 (ext.158) - Fax: 915261867 * > *rsa...@fs... * <rsa...@fs...>*- **www.f-soria.es * > <http://www.f-soria.es/> > > > * AVISO DE CONFIDENCIALIDAD * > > > > ------------------------------ > > La información contenida en este mensaje y archivos adjuntos es privada, > confidencial y de uso exclusivo de la(s) persona(s) y entidad(es) a la(s) > que va dirigido. Si Ud. no es el destinatario de esta información se le > notifica que está expresamente prohibida la declaración, reproducción, > distribución o la toma de cualquier acción basada en el contenido de esta > comunicación. Si ha recibido este mensaje por error, le rogamos que nos lo > comunique inmediatamente y proceda a eliminarlo de todos sus sistemas. > Francisco Soria Melguizo, S.A. no asume responsabilidad legal por el > contenido de esta comunicación, ni representa la opinión de la firma, salvo > que expresamente se especifique lo contrario y que el remitente esté > autorizado para hacerlo. Gracias. > > > ******************************************************************************** > > This email, including any attachments sent with it, is confidential and > for the sole use of the intended recipient(s). This confidentiality is not > waived or lost, if you receive it and you are not the intended > recipient(s), or if it is transmitted/received in error. > > Any unauthorised use, alteration, disclosure, distribution or review of > this email is strictly prohibited. The information contained in this email, > including any attachment sent with it, may be subject to a statutory duty > of confidentiality if it relates to health service matters. > > If you are not the intended recipient(s), or if you have received this > email in error, you are asked to immediately notify the sender by telephone > collect on Australia +61 1800 198 175 or by return email. You should also > delete this email, and any copies, from your computer system network and > destroy any hard copies produced. > > If not an intended recipient of this email, you must not copy, distribute > or take any action(s) that relies on it; any form of disclosure, > modification, distribution and/or publication of this email is also > prohibited. > > Although Queensland Health takes all reasonable steps to ensure this email > does not contain malicious software, Queensland Health does not accept > responsibility for the consequences if any person's computer inadvertently > suffers any disruption to services, loss of information, harm or is > infected with a virus, other malicious computer programme or code that may > occur as a consequence of receiving this email. > > Unless stated otherwise, this email represents only the views of the > sender and not the views of the Queensland Government. > > > ********************************************************************************** > > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > _______________________________________________ > Hl7api-devel mailing list > Hl7...@li... > https://lists.sourceforge.net/lists/listinfo/hl7api-devel > > |
|
From: <rsa...@fs...> - 2014-11-11 16:04:46
|
Hi, I have received the next ORU^R01 message: MSH|^~\&|MG|MG|LAB|LAB|20100127101236+0100||ORU^R01^ORU_R01|1234567890|P|2.5 PID|... PV1|... ORC|... OBR|1|OP2|10101010|HEM^Hemograma^SISTEMA1|... OBX|1|NM|HTIE^Hematíes^SISTEMA1||7.00|x10*6/uL|4.5 - 5.9|HH|||F|||20100127095652 OBX|2|NM|HGB^Hemoglobina^SISTEMA1||567567.0|g/dL|13.0 - 17.5|HH|||F|||20100127095652 OBX|3|NM|HTCO^Hematocrito^SISTEMA1||77.0|%|37.0 - 53.0|HH|||F|||20100127095728 OBX|4|NM|VCM^VCM^SISTEMA1||67.0|fl|80.0 - 100.0|LL|||F|||20100127095728 SPM|1|9018000088||^SANGRE PERIFERICA||||||||||||||20100127095625||Y||||||1 In this message, the OBR Segment contains a Battery (HEM) and the tests have been added in OBX Segments. In this case, the HEM Battery contains 4 tests (HTIE, HGB, HTCO and VCM). I would like to know if this message is a Standard HL7 Message. At the moment, I have only received tests in ORU^R01 messages. In the next ORU^R01 message, I have received a test (CLC00500) with two results (OBX.1 and OBX.2 segments): MSH|^~\&|MG|MG|FSM|FSM|20141105132023+0100||ORU^R01^ORU_R01|LAB31415190023385|P|2.5 PID|... PV1|... ORC|... OBR|1|PA5999171|20000002|CLC00500^Pla--Glucosa; c.sust.(proc.)^SISTEMA1||||||CE||||||00010258960^ape1 ape2, nombre||||5||||LAB|F|||||||admin^20141105132022+0100 OBX|1|NM|CLC00500^Pla--Glucosa; c.sust.(proc.)^SISTEMA1||65|mg/dL||HH|||F|||20141105132022||admin|||20141105132022 OBX|2|ST|CLC00500^Pla--Glucosa; c.sust.(proc.)^SISTEMA1|1|POSITIVO|||||||||20141105132022||admin SPM|1|0120000002||3^Suero||||||||||||||20141105132010||Y||||||1 How could I to know when the OBR Segment contains a Battery or a test? My first idea is the next: if OBR.4.1 = OBX.3.1, then the OBR Segment contains a Test, else OBR Segment contains a Battery. But this is a bad solution :( Help me! Best Regards. Rafael. Rafael San Vidal Hidalgo - Dpto. Sistemas de Diagnóstico Tlf.: 914702104 (ext.158) - Fax: 915261867 rsa...@fs... - www.f-soria.es AVISO DE CONFIDENCIALIDAD La información contenida en este mensaje y archivos adjuntos es privada, confidencial y de uso exclusivo de la(s) persona(s) y entidad(es) a la(s) que va dirigido. Si Ud. no es el destinatario de esta información se le notifica que está expresamente prohibida la declaración, reproducción, distribución o la toma de cualquier acción basada en el contenido de esta comunicación. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente y proceda a eliminarlo de todos sus sistemas. Francisco Soria Melguizo, S.A. no asume responsabilidad legal por el contenido de esta comunicación, ni representa la opinión de la firma, salvo que expresamente se especifique lo contrario y que el remitente esté autorizado para hacerlo. Gracias. De: Rafael San Vidal Hidalgo/GSORIA Para: Ian Vowles <Ian...@he...> cc: "hl7...@li..." <hl7...@li...> Fecha: 08/05/2014 09:36 Asunto: RE: [HAPI-devel] Parse only Segment MSH Thank you, Ian I will develope your two options. In the first option (using parser method with the first segment only), How do I get the first segment in XML Format? I would try to get the first segment looking for the </MSH> value. I will try the preparser option too, proposed by our partner James Agner. Best regards. Rafael San Vidal. Rafael San Vidal Hidalgo - Dpto. Sistemas de Diagnóstico Tlf.: 914702104 (ext.158) - Fax: 915261867 rsa...@fs... - www.f-soria.es AVISO DE CONFIDENCIALIDAD La información contenida en este mensaje y archivos adjuntos es privada, confidencial y de uso exclusivo de la(s) persona(s) y entidad(es) a la(s) que va dirigido. Si Ud. no es el destinatario de esta información se le notifica que está expresamente prohibida la declaración, reproducción, distribución o la toma de cualquier acción basada en el contenido de esta comunicación. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente y proceda a eliminarlo de todos sus sistemas. Francisco Soria Melguizo, S.A. no asume responsabilidad legal por el contenido de esta comunicación, ni representa la opinión de la firma, salvo que expresamente se especifique lo contrario y que el remitente esté autorizado para hacerlo. Gracias. RE: [HAPI-devel] Parse only Segment MSH Ian Vowles para: rsa...@fs..., hl7...@li... Enviado: 08/05/2014 00:11 Recibido: 08/05/2014 09:10 Our team often finds itself wanting to deal with individual segments. Segment constructors still require something to base themselves on, so you seem to be required to do something like this: private static ADT_A01 parent; . . . parent = new ADT_A01(); parent.initQuickstart("ADT", "A01", "P"); String message = "MSH|^~\\&|SENDING-APP|SENDING-FAC|RECEIVING-APP|RECEIVING-FAC|20140508111155|SECURITY|ADT^A08|MESSAGE-CONTROL-ID|P|2.4|||AL|AL|AUS|ASCII|ENG|\r" + "MORE SEGMENTS GO HERE IN A REAL MESSAGE\r"; System.out.println("Message Control Id = " + getUID(message)); . . . /** * Get MessageControlID * @param mensaje * @return MessageControlID */ public static String getUID(String mensaje) { try { MSH msh = new MSH(parent,parent.getModelClassFactory()); if (mensaje.indexOf("\r") > 0) { msh.parse(mensaje.substring(0, mensaje.indexOf("\r"))); } return msh.getMessageControlID().getValue(); } catch (HL7Exception e) {} return null; } If anyone can show a simpler way to create a segment from scratch, that would be most helpful. To just get amongst the MSH you could go for all string manipulation, but you have to worry about the standard. You could do something like this: /** * Get MessageControlID * @param mensaje * @return MessageControlID */ public static String getUIDNoHapi(String mensaje) { if (mensaje != null && mensaje.length() > 4 && mensaje.startsWith("MSH") && mensaje.indexOf("\r") > 0) { String msh = mensaje.substring(0, mensaje.indexOf("\r")); String fieldDel = mshsubstring(3, 4); if ("|".equals(fieldDel)) { fieldDel = "\\|"; } String[] mshFields = msh.split(fieldDel); return mshFields[9]; } return null; } There are traps in this code if people start using non standard delimiters or send you very bad content. The HAPI library is a much better to help you avoid such trouble. Thanks Ian From: rsa...@fs... [mailto:rsa...@fs...] Sent: Wednesday, 7 May 2014 6:22 PM To: Ian Vowles; hl7...@li... Subject: [HAPI-devel] Parse only Segment MSH Hi, In our source code, we parse the full message (from string data) to get the MessageControlID value. How can I get the MessageControlID value without parsing the full message (Example: parsing only the MSH Segment)? Note: I attach the "getUID" method to get this value. Best regards. Rafael. import ca.uhn.hl7v2.model.Message; import ca.uhn.hl7v2.model.v25.segment.MSH; /** * Get MessageControlID * @param mensaje * @return MessageControlID */ public static String getUID(String mensaje) { try { Parser parseador = new GenericParser(); parseador.setValidationContext(new NoValidation()) ; Message mensajeHAPI = parseador.parse(mensaje); MSH segmentoHAPI_MSH = (MSH) mensajeHAPI.get(Parametros.MSH); return segmentoHAPI_MSH.getMessageControlID().getValue(); } catch (Exception e) {} return null; } Rafael San Vidal Hidalgo - Dpto. Sistemas de Diagnóstico Tlf.: 914702104 (ext.158) - Fax: 915261867 rsa...@fs... - www.f-soria.es AVISO DE CONFIDENCIALIDAD La información contenida en este mensaje y archivos adjuntos es privada, confidencial y de uso exclusivo de la(s) persona(s) y entidad(es) a la(s) que va dirigido. Si Ud. no es el destinatario de esta información se le notifica que está expresamente prohibida la declaración, reproducción, distribución o la toma de cualquier acción basada en el contenido de esta comunicación. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente y proceda a eliminarlo de todos sus sistemas. Francisco Soria Melguizo, S.A. no asume responsabilidad legal por el contenido de esta comunicación, ni representa la opinión de la firma, salvo que expresamente se especifique lo contrario y que el remitente esté autorizado para hacerlo. Gracias. ******************************************************************************** This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is strictly prohibited. The information contained in this email, including any attachment sent with it, may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender by telephone collect on Australia +61 1800 198 175 or by return email. You should also delete this email, and any copies, from your computer system network and destroy any hard copies produced. If not an intended recipient of this email, you must not copy, distribute or take any action(s) that relies on it; any form of disclosure, modification, distribution and/or publication of this email is also prohibited. Although Queensland Health takes all reasonable steps to ensure this email does not contain malicious software, Queensland Health does not accept responsibility for the consequences if any person's computer inadvertently suffers any disruption to services, loss of information, harm or is infected with a virus, other malicious computer programme or code that may occur as a consequence of receiving this email. Unless stated otherwise, this email represents only the views of the sender and not the views of the Queensland Government. ********************************************************************************** |
|
From: Rajendram K. <kat...@gm...> - 2014-11-10 04:22:33
|
Hi James Thanks for your quick response and the explanation about HL7 and XML message format. Thanks, Kathees On 4 November 2014 20:43, James Agnew <jam...@gm...> wrote: > Hi Kathees, > > This is actually correct behaviour. It's a somewhat confusing aspect of > HL7 v2 at first, but HL7 reuses some message structures for multiple > message trigger events. For example, the ADT^A01 and ADT^A04 messages both > need all of the same data fields, so HL7 decided to reuse the ADT^A01 > structure for the ADT^A04 message. They call this structure ADT_A01 (note > the underscore). > > MDM^T02 and MDM^T10 similarly share messages. The thing to note is the > message type and structure in MSH-9: > > <MSH.9> > <MSG.1>MDM</MSG.1> > <MSG.2>T10</MSG.2> > <MSG.3>MDM_T02</MSG.3> > </MSH.9> > > Cheers, > James > > On Tue, Nov 4, 2014 at 4:39 AM, Rajendram Kathees <kat...@gm...> > wrote: > >> Hi, >> >> We used the Hapi library to convert the HL7 message [1] to XML format >> [2]. I notice MDM_T02 comes as a root element in the XML. Shouldn't this be >> MDM_T10 like in the other cases? Is this a bug? Can someone explain why >> this is the case? >> >> [1] ER7 Message >> MSH|^~\\&|||||20141104095415.605+0530||MDM^T10^MDM_T02|2101||2.6| >> >> [2] XML Message >> <?xml version="1.0"?> >> <MDM_T02 xmlns="urn:hl7-org:v2xml"> >> <MSH> >> <MSH.1>|</MSH.1> >> <MSH.2>^~\&</MSH.2> >> <MSH.7>20141104095415.605+0530</MSH.7> >> <MSH.9> >> <MSG.1>MDM</MSG.1> >> <MSG.2>T10</MSG.2> >> <MSG.3>MDM_T02</MSG.3> >> </MSH.9> >> <MSH.10>2101</MSH.10> >> <MSH.12> >> <VID.1>2.6</VID.1> >> </MSH.12> >> </MSH> >> </MDM_T02> >> >> >> >> Thanks, >> Kathees >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Hl7api-devel mailing list >> Hl7...@li... >> https://lists.sourceforge.net/lists/listinfo/hl7api-devel >> >> > |
|
From: Clayton D. <cl...@am...> - 2014-11-07 04:16:46
|
Thanks Ian. 2.7.1 included a bunch of datatype replacements... which affects the XML structure (but not the pipe structure) in non-backwards compatible ways. If I were so motivated, what changes are required to get HAPI processing a 2.7.1 schema? Note that, due to field withdrawals, this basically *must* be a custom schema? I was hoping the "build from source" process would be enlightening... but tests are failing because XSD files are missing. I have those files (both for stock versions and 2.7.1), but errors like "Schema file not found on disk: dgjkn(/º$&f09e/ACK.xsd" aren't exactly clearing up my confusion. Thanks, Clayton Daley Ambassador Software Works On Wed, Nov 5, 2014 at 11:40 PM, Ian Vowles <Ian...@he...> wrote: > In HAPI vs 2.2 the maximum HL7 version supported with complete structures > is 2.6. > > > > However, HAPI is quite able to deal with messages that don’t exactly match > against a versions structure, so you are likely to still be able to meet > your requirements. > > > > So, point one is certainly possible, given that 2.6 is the maximum fully > supported version of structures at the moment. We do something like this, > where all our vendors sned HL7 versions 2.3, 2.3.1 and a couple of 2.4. All > of them are ‘upshifted’ to 2.4 or 2.5, and handled as such from then on. > > > > Given that point one is covered, point two happens as a result, since all > the messages conform to the representation we ‘upshifted’ them to. Fields > that have changed from a string to a datatype still have the fields > accessable. > > > > Using HAPI you can access XML representation of the HL7 if it is sent to > you in the old bar delimited form. If you are already dealing with XML, > things should be good. > > > > Which leaves the third point as the ball that is in your court. If you > need to transform a message you have received into another form, or change > values based on some specification, that’s the work in front of you. > > > > Whilst I’m not using any XML, all bar delimited stuff here, I do what you > are asking about all day every day. HAPI is a very useful library. > > > > Hope this helps > > > > Ian > > Systems Integration Team > > Dept of Health > > Queensland > > Australia > > > > *From:* Clayton Daley [mailto:cl...@am...] > *Sent:* Thursday, 6 November 2014 10:22 AM > *To:* hl7api-devel > *Subject:* Re: [HAPI-devel] Customized (v2.7.1 based) Parsing Schema > > > > Good Afternoon, > > > > We're a Healthcare IT SaaS startup using HAPI indirectly through Mirth > Connect. > > > > As a service provider, we will need to process messages from many > different HL7 versions. In brief, our idea is to: > > · Feed messages of any version into a single parser (currently, based on > 2.7.1), > > · Get a message in a uniform structure (avoiding, for example, > differences arising from datatype replacements), and > > · Build one set of (internal) XML interpreters for that output. > > Can someone clarify details like: > > · How much of this can be achieved using HAPI "out of the box", > > · Is it enough that I can generate an XSD schema or is this the wrong > format, and > > · What changes would be required inside HAPI > > ... and I suppose "are there any other questions I should have asked"? > > > > Thanks, > > > > Clayton Daley > > Ambassador Software Works > > > ******************************************************************************** > > This email, including any attachments sent with it, is confidential and > for the sole use of the intended recipient(s). This confidentiality is not > waived or lost, if you receive it and you are not the intended > recipient(s), or if it is transmitted/received in error. > > Any unauthorised use, alteration, disclosure, distribution or review of > this email is strictly prohibited. The information contained in this email, > including any attachment sent with it, may be subject to a statutory duty > of confidentiality if it relates to health service matters. > > If you are not the intended recipient(s), or if you have received this > email in error, you are asked to immediately notify the sender by telephone > collect on Australia +61 1800 198 175 or by return email. You should also > delete this email, and any copies, from your computer system network and > destroy any hard copies produced. > > If not an intended recipient of this email, you must not copy, distribute > or take any action(s) that relies on it; any form of disclosure, > modification, distribution and/or publication of this email is also > prohibited. > > Although Queensland Health takes all reasonable steps to ensure this email > does not contain malicious software, Queensland Health does not accept > responsibility for the consequences if any person's computer inadvertently > suffers any disruption to services, loss of information, harm or is > infected with a virus, other malicious computer programme or code that may > occur as a consequence of receiving this email. > > Unless stated otherwise, this email represents only the views of the > sender and not the views of the Queensland Government. > > > ********************************************************************************** > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Hl7api-devel mailing list > Hl7...@li... > https://lists.sourceforge.net/lists/listinfo/hl7api-devel > > |
|
From: Chandan D. <cha...@au...> - 2014-11-07 03:48:06
|
I am trying to convert a message with the following header and get the error below. Is there a way to generate the XML? MSH|^~\&|AKL|pathlabs|BOPHL7|riversmc|201102111218|PKI|ORU|6030124414|P|2.1 ca.uhn.hl7v2.HL7Exception: Can't determine message structure from MSH-9: ORU HINT: there are only 1 of 3 components present -- Regards, Chandan Doctoral student,Robotics Research Group University of Auckland, New Zealand |
|
From: Ian V. <Ian...@he...> - 2014-11-06 04:41:46
|
In HAPI vs 2.2 the maximum HL7 version supported with complete structures is 2.6. However, HAPI is quite able to deal with messages that don’t exactly match against a versions structure, so you are likely to still be able to meet your requirements. So, point one is certainly possible, given that 2.6 is the maximum fully supported version of structures at the moment. We do something like this, where all our vendors sned HL7 versions 2.3, 2.3.1 and a couple of 2.4. All of them are ‘upshifted’ to 2.4 or 2.5, and handled as such from then on. Given that point one is covered, point two happens as a result, since all the messages conform to the representation we ‘upshifted’ them to. Fields that have changed from a string to a datatype still have the fields accessable. Using HAPI you can access XML representation of the HL7 if it is sent to you in the old bar delimited form. If you are already dealing with XML, things should be good. Which leaves the third point as the ball that is in your court. If you need to transform a message you have received into another form, or change values based on some specification, that’s the work in front of you. Whilst I’m not using any XML, all bar delimited stuff here, I do what you are asking about all day every day. HAPI is a very useful library. Hope this helps Ian Systems Integration Team Dept of Health Queensland Australia From: Clayton Daley [mailto:cl...@am...] Sent: Thursday, 6 November 2014 10:22 AM To: hl7api-devel Subject: Re: [HAPI-devel] Customized (v2.7.1 based) Parsing Schema Good Afternoon, We're a Healthcare IT SaaS startup using HAPI indirectly through Mirth Connect. As a service provider, we will need to process messages from many different HL7 versions. In brief, our idea is to: · Feed messages of any version into a single parser (currently, based on 2.7.1), · Get a message in a uniform structure (avoiding, for example, differences arising from datatype replacements), and · Build one set of (internal) XML interpreters for that output. Can someone clarify details like: · How much of this can be achieved using HAPI "out of the box", · Is it enough that I can generate an XSD schema or is this the wrong format, and · What changes would be required inside HAPI ... and I suppose "are there any other questions I should have asked"? Thanks, Clayton Daley Ambassador Software Works ******************************************************************************** This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is strictly prohibited. The information contained in this email, including any attachment sent with it, may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender by telephone collect on Australia +61 1800 198 175 or by return email. You should also delete this email, and any copies, from your computer system network and destroy any hard copies produced. If not an intended recipient of this email, you must not copy, distribute or take any action(s) that relies on it; any form of disclosure, modification, distribution and/or publication of this email is also prohibited. Although Queensland Health takes all reasonable steps to ensure this email does not contain malicious software, Queensland Health does not accept responsibility for the consequences if any person's computer inadvertently suffers any disruption to services, loss of information, harm or is infected with a virus, other malicious computer programme or code that may occur as a consequence of receiving this email. Unless stated otherwise, this email represents only the views of the sender and not the views of the Queensland Government. ********************************************************************************** |
106 messages has been excluded from this view by a project administrator.
