[HAPI-devel] Example for defining a custom Segment

2007-11-23 Thread Fabio Daprile
Hello all, i need to define a custom segment in HAPI. The segment : ZDS Somebody has an example which shows how to do this? It would be of great help. Greetz, Fabio - This SF.net email is sponsored by: Microsoft Defy all c

Re: [HAPI-devel] Posible BUG when messages or groups have duplicated elements

2007-11-23 Thread Leo
Hi Jan, I think it is not the problem because in the example i have write I put nk1 segment between ROL segments. I think the problem is how HAPI naming duplicates segments (using ROL, ROL2, ROL3, ROL4...) and parser dont consider it. On Nov 23, 2007 11:46 AM, Jan Klasser <[EMAIL PROTECTED]> wrote

Re: [HAPI-devel] Posible BUG when messages or groups have duplicated elements

2007-11-23 Thread Jan Klasser
Hi Leo, sometimes the message structure in HL7 is ambiguous if you omit required segments. In this case(QUERY_RESPONSE group) if you need the group you need to set the PID and PV1. Not sure if this solves the error, anyhow the message parsing without the required segments is error prone Leo-61

Re: [HAPI-devel] terser - syntax

2007-11-23 Thread Jan Klasser
Hi Epic, If you want the group to repeat, that's possible with the terser. Something like that terser.set("/FINANCIAL(0)/FT1-1", setId); terser.set("/FINANCIAL(1)/FT1-1", setId); Leo-61 wrote: > > Hello Epic! I think segment FT1 is not repeteable in FINANCIAL group, you > cant add second

Re: [HAPI-devel] Problem with message mapping

2007-11-23 Thread Torben Greiser
Hi Fabio, I'm quoting Bryan to answer you this: > There is one HAPI class for each message structure, but > multiple events can use the same structure (e.g. event A28 uses > structure ADT_A05). > > If you are creating a new message, use the structure that corresponds > to your event (this is give

[HAPI-devel] Problem with message mapping

2007-11-23 Thread Fabio Daprile
Hello all, i have a problem while transforming the following message: MSH|^~\\&|APA|ITACA_EXPORT|RIS|HL7_EXT|20071030200853.2890+0100||ADT^A28|HL7Gtw0115F250F6A900|P|2.5|||AL|AL|D|8859/1 When parsing this message with the PipeParser, the resulting message is an ADT_A05. I had a look in this fil