Hi Ismet,

just recently tested two variants wo. asking for implementing national specific 
definitions:

 *
Leave it as is - HAPI parses those messages kind without error but the 
following drawbacks:
    *
The parser returns a GenericMessage instead of an ADT-message. The terser, 
however, successfully finds e.g. your "/.ZBE-1-2" component or whatever.
    *
You cannot use the terser leave alone specific setter methods to deliberately 
set field contents and/or create a ZBE segment. You can add string content to 
the encoded part of the ADT-message and proceed to work with the generic 
message (see above)
 *
I created a custommodel ZDT message type where the classes derive from the ADT 
messages/groups/segments and implement the additional methods for handling ZBE.
    *
Drawback: I haven't tested them yet... (so I'm VERY eager to give them away in 
order to get some feedback)

Regards,

Stefan

T-Systems International GmbH
Klinische Systeme
Hausanschrift: Pascalstr. 11, 10587 Berlin
Telefon: +49-30-3997-2468
Mobiltelefon: +49-170-5 35 38 92
E-Mail: mailto:stefan.koeh...@t-systems.com
Internet: http://www.t-systems.com<http://www.t-systems.com/>

T-Systems International GmbH
Aufsichtsrat: René Obermann (Vorsitzender)
Geschäftsführung: Reinhard Clemens (Vorsitzender), Dr. Ferri Abolhassan, Olaf 
Heyden, Joachim Langmark, Dr. Matthias Schuster, Klaus Werner

Handelsregister: Amtsgericht Frankfurt am Main HRB 55933
Sitz der Gesellschaft: Frankfurt am Main WEEE-Reg-Nr. DE87523644

Notice: This transmittal and/or attachments may be privileged or confidential. 
If you are not the intended recipient, you are hereby notified that you have 
received this transmittal in error; any review, dissemination, or copying is 
strictly prohibited. If you received this transmittal in error, please notify 
us immediately by reply and immediately delete this message and all its 
attachments. Thank you.

________________________________
Von: Çelebi, Ismet [mailto:icel...@joho.de]
Gesendet: Dienstag, 22. März 2011 16:30
An: hl7api-devel@lists.sourceforge.net
Betreff: [HAPI-devel] ZBE-Segment

Hi Folks,

In our ADT-Messages there is a segment called ZBE. I can not use this segment 
via HAPI.
Is there a way to include this into HAPI or how am I going to implement this 
into HAPI?

ZBE|5007|20110316124300||UPDATE

Definition of this ZBE segment is:

Type    Length      Name
EI         250          TransferID
TS        250          Start of Transfer
TS        250          End of Transfer
ST        250          Action code ZBE


Cheers,
Ismet


St. Josefs-Hospital Wiesbaden GmbH, Beethovenstrasse 20, 65189 Wiesba den
Telefon 0611/177-0, Telefax 0611/177-1185, E-Mail: i...@joho.de 
Geschaeftsfuehrer: Karl-Josef Schmidt, stellv. Geschaeftsfuehrer: Pete r 
Pfaffenberger
Registergericht: AG Wiesbaden, HR B 21935

------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
Hl7api-devel mailing list
Hl7api-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hl7api-devel

Reply via email to