Re: [HAPI-devel] HAPI 1.1 - No more hl7Exception for more than one OBR for one ORC in an ORM message

[Jens V. <jen...@gm...>]

Latest HAPI release is v2.2 and was back in 2014. v1.1 was released back in
2011. I would be surprised if anyone would be able to remember such a gap.

On 29 September 2015 at 11:05, Jasmine Piacenti <
jas...@sy...> wrote:

> Hi,
>
> I’m testing the follow message
>
>
> MSH|^~\&|VERBENA|PRAEZISION|RIS|SYNCROMED|20070828135556+0000||ORM^O01^ORM_O01|5366|P|2.5|
>
> PID|||19930013050^^^PK^PK^^^^^^~CODSTP^^^STP^STP~CODFISC^^^CF^CF~TEsSan^^^TS^TS||PROVACOGN^PROVANOME^^^^^L^^^^^^^||19361027|M|||VIA
> MASCAGNI 5^^URUGUAY^null^37014^^C^^999618^^^^^~VIA MASCAGNI
> 5^^URUGUAY^null^37014^^H^^999618^^^^^~^^URUGUAY^null^37014^^BR^^999618^^^^^|||||||GLLCLS36R24Z613E|611281734||||||||||||||||||||
>
> PD1|||ASL DELLA PROVINCIA DI BERGAMO^^^^^^H^^^301030~ASL
> ASS^^^^^^C^^^123456|
>
>
> PV1||E|||||133429^COGN^NOME|9PRZMARK^COGNOME^NOME^^^^^^^^^^9||114|||||||||589179|||||||||||||||||||||||A02|||||||||V|
>
> ORC|NW|67262|5189|2007100059|PR||1^^^20070828135500+0000||20070828135500+0000|||9PRZMARK^COGNOME^NOME|||||114^PRONTO
> SOCCORSO|
>
> OBR|1|67262|5189|1223^RX PELVI
> (bacino)||||||||3|RRR|||9PRZMARK^COGNOME||||||||1|||1^^^20070828135500+0000|
>
> OBR|2|67262|5189|1223^RX PELVI
> (bacino)||||||||3|RRR|||9PRZMARK^COGNOME||||||||1|||1^^^20070828135500+0000|
>
> OBX||FT|600936542||testo del referto |
>
> ORC|NW|67262|5190|2007100059|PR||1^^^20070828135500+0000||20070828135500+0000|||9PRZMARK^COGNOME^NOME|||||114^PRONTO
> SOCCORSO|
>
> OBR|1|67262|5190|8001^TAC
> CAPO||||||||3|RRR|||9PRZMARK^COGNOME||||||||7|||1^^^20070828135500+0000|
>
> OBR|2|67262|5190|8001^TAC
> CAPO||||||||3|RRR|||9PRZMARK^COGNOME||||||||7|||1^^^20070828135500+0000|
>
> OBX||FT|600936542||testo del referto |
>
> ZDS|1.2.300.4005|a^b^c|Application|DICOM|
>
>
>
> With HAPI 0.6 when I parsed an ORM message with more than one OBR for one
> ORC, I received an HL7Exception, like that:
>
> *HL7Exception arising from bad index: Error! Segment: OBR*
>
> *Either:*
>
> *a)The segment is in the wrong position  *
>
> *b)More than 1 instance exists and the Segment is non-repetitional.*
>
>
>
> With HAPI 1.1 any exception is caught.
>
> Could you explain me why?
>
> With the next versions (after 1.1) this behaviour remains the same or
> changes?
>
>
>
> Thank you
>
> Regards
>
>
>
> Jasmine Piacenti
>
>
>
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>
>


-- 

Med venlig hilsen / Kind regards

*Jens Kristian Villadsen*
cand.polyt

Stålhøjen 24
8240 Risskov
Denmark

Mobile +4523373806
jen...@gm...