hl7api-devel — developer list

[HAPI-devel] HAPI object-oriented HL7 2.x parser for Java able to parse embedded data?

[Andrew W. <aw...@tr...>]

Is the HAPI object-oriented HL7 2.x parser for Java, able to parse embedded data, of any size in HL7 ORU messages?


Respectfully,
Andrew West, PMP®
Healthcare Business Analyst
[cid:6B45E559-8C21-4724-9028-F769E55EF049]
The Platform for Population Wellness


The information transmitted is intended only for the person or entity to which it is addressed
and may contain CONFIDENTIAL material.  If you receive this material/information in error,
please contact the sender and delete or destroy the material/information.

[HAPI-devel] Allow binding to a specific local address

[Mrugank S. <mr...@gm...>]

Hi,

I am using SimpleServer and I need it to bind to a specific IP address on
the system and not on the wildcard address (as it does now). I tried to see
if this was easily achievable by extending some classes from the library.
But looks like it is not really easy to do this because a lot of
classes/methods are private/package-private and extending them is not
possible. Any suggestions on how to achieve this ?

Thanks,
Mrugank

Re: [HAPI-devel] MessageVisitor & Location - a bug?

[Christian O. <chr...@gm...>]

MessageVisitor wasn't used a lot, so it might be you found a bug.
Feel free to open an issue. If possible please add a unit test that 
demonstrates the problem.

Thank you
Christian

Am 23.05.2017 um 00:31 schrieb Conway Thomas:
> Hi Hapi Devels,
>
> I’m loving your stack – it’s beautifully done.
>
> I’m using HL7 v 2.5.1, and using MessageVisitor to build a different representation of the message to use in another system, and it seems that the field repeat of the Location object is not correctly set. In particular, when traversing PID-3, the patient identifier list, which is a repeating field, the result returned by Location.getFieldRepetition() is always –1, indicating that it is not repeated. However, the traversal does correctly visit multiple CXs, it’s just the location information that is incorrect.
>
> I couldn’t see anything indicating that this is a known problem. Anyone?
>
> Tom.
>
>
> Dr Thomas Conway
>
> Senior Research Scientist
>
> Peter MacCallum Cancer Centre
>
> http://www.petermac.org<http://www.petermac.org/>
>
>
> Phone: +61 3 9656 1575
>
> Mobile: +61 416 611 073
>
> Email: tho...@pe...
>
>
> [unknown.png]
>
> [unknown_1.png]
>
>
> This email (including any attachments or links) may contain
> confidential and/or legally privileged information and is
> intended only to be read or used by the addressee.  If you
> are not the intended addressee, any use, distribution,
> disclosure or copying of this email is strictly
> prohibited.
> Confidentiality and legal privilege attached to this email
> (including any attachments) are not waived or lost by
> reason of its mistaken delivery to you.
> If you have received this email in error, please delete it
> and notify us immediately by telephone or email.  Peter
> MacCallum Cancer Centre provides no guarantee that this
> transmission is free of virus or that it has not been
> intercepted or altered and will not be liable for any delay
> in its receipt.
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel

Re: [HAPI-devel] Lead spacing trimming

[James A. <jam...@gm...>]

Well.... These should be functionally equivalent, so it sounds like you've
found a bug. Please feel free to add a ticket for this.

Cheers,
James

On Fri, May 26, 2017 at 12:02 AM, Mike Mills <mi...@th...> wrote:

> James,
>
> I work with David and have been working with him to get to the bottom of
> the issue so that we can choose a suitable solution for us.
>
> We noticed that some validation is turned on when you use the pipeParser
> but not when you use the parse() on a Message. eg:
>
>         String msh_string = "MSH|^~\\&|MSH3|MSH4|MSH5|MSH6|20161221133021||ADT^A01|
>   MSH10|P|2.5";
>         final ADT_A01 adt_a01 = new ADT_A01();
>         adt_a01.parse(msh_string);
>         String objectParseMSH10 = adt_a01.getMSH().getMessageControlID().
> getValue();
>         System.out.println(objectParseMSH10.length());  // length is 8,
> spaces preserved
>
>         ADT_A01 parsedA01 = (ADT_A01) new DefaultHapiContext().
> getPipeParser().parse(msh_string);
>         String pipeParsedMSH10 = parsedA01.getMSH().getMessageControlID().
> getValue();
>         System.out.println(pipeParsedMSH10.length());  // length is 5, ie
> spaces stripped
>
>
> In this example the MSH10 has leading spaces and the parse() on a message
> method does not strip the spaces.
>
> With the pipeParser method it parses and strips the spaces.
>
> We have always assumed that they were functionally equivalent ways of
> parsing a string into a Hapi Message.
>
> As they are not which is the recommended way to parse a HL7 string into a
> Hapi Message object?
>
> Regards,
>
> -Mike
>
>
>
>
> On 25 May 2017 at 21:03, James Agnew <jam...@gm...> wrote:
>
>> Hi David,
>>
>> I'm not sure I could provide an answer as to why, given that this
>> behaviour has existed in the library for roughly 15 years now.
>>
>> I would be nervous about changing it given how longstanding it has
>> existed, but I can tell you that you can disable it by setting validation
>> to NoValidation (it's the validation engine that causes this trimming).
>>
>> Cheers,
>> James
>>
>> On Wed, May 24, 2017 at 11:37 PM, David Bunzli <
>> Dav...@he...> wrote:
>>
>>> Hi,
>>>
>>>
>>>
>>> I’m experiencing a situation where an NTE-3 field handled by HAPI is
>>> trimming leading spaces, eg ‘  an FT string’ -> ‘an FT string’. My
>>> investigation lead me to the HAPI FAQ link
>>> http://hl7api.sourceforge.net/hapi-faq.html#leading_space which
>>> describes this behaviour for FT, ST and TX fields.
>>>
>>>
>>>
>>> My questions are:
>>>
>>> ·         why does HAPI trim leading spaces given that the HL7 v2.4
>>> spec ‘Chapter 2.9.48 TX – text data’ says ‘Leading spaces should be
>>> included’?
>>>
>>> ·         I can’t find any reference in the rest of the HL7 v2.4 spec
>>> which mentions the trimming of leading spaces. Have I missed this, or why
>>> has HAPI chosen to trim?
>>>
>>>
>>>
>>> Regards,
>>>
>>> David Bunzli
>>>
>>> ************************************************************
>>> ********************
>>>
>>> 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 <+61%201800%20198%20175> 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.
>>>
>>> ************************************************************
>>> **********************
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Hl7api-devel mailing list
>>> Hl7...@li...
>>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>>
>>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Hl7api-devel mailing list
>> Hl7...@li...
>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>
>>
>

Re: [HAPI-devel] Lead spacing trimming

[Mike M. <mi...@th...>]

James,

I work with David and have been working with him to get to the bottom of
the issue so that we can choose a suitable solution for us.

We noticed that some validation is turned on when you use the pipeParser
but not when you use the parse() on a Message. eg:

        String msh_string =
"MSH|^~\\&|MSH3|MSH4|MSH5|MSH6|20161221133021||ADT^A01|   MSH10|P|2.5";
        final ADT_A01 adt_a01 = new ADT_A01();
        adt_a01.parse(msh_string);
        String objectParseMSH10 =
adt_a01.getMSH().getMessageControlID().getValue();
        System.out.println(objectParseMSH10.length());  // length is 8,
spaces preserved

        ADT_A01 parsedA01 = (ADT_A01) new
DefaultHapiContext().getPipeParser().parse(msh_string);
        String pipeParsedMSH10 =
parsedA01.getMSH().getMessageControlID().getValue();
        System.out.println(pipeParsedMSH10.length());  // length is 5, ie
spaces stripped


In this example the MSH10 has leading spaces and the parse() on a message
method does not strip the spaces.

With the pipeParser method it parses and strips the spaces.

We have always assumed that they were functionally equivalent ways of
parsing a string into a Hapi Message.

As they are not which is the recommended way to parse a HL7 string into a
Hapi Message object?

Regards,

-Mike




On 25 May 2017 at 21:03, James Agnew <jam...@gm...> wrote:

> Hi David,
>
> I'm not sure I could provide an answer as to why, given that this
> behaviour has existed in the library for roughly 15 years now.
>
> I would be nervous about changing it given how longstanding it has
> existed, but I can tell you that you can disable it by setting validation
> to NoValidation (it's the validation engine that causes this trimming).
>
> Cheers,
> James
>
> On Wed, May 24, 2017 at 11:37 PM, David Bunzli <
> Dav...@he...> wrote:
>
>> Hi,
>>
>>
>>
>> I’m experiencing a situation where an NTE-3 field handled by HAPI is
>> trimming leading spaces, eg ‘  an FT string’ -> ‘an FT string’. My
>> investigation lead me to the HAPI FAQ link http://hl7api.sourceforge.net/
>> hapi-faq.html#leading_space which describes this behaviour for FT, ST
>> and TX fields.
>>
>>
>>
>> My questions are:
>>
>> ·         why does HAPI trim leading spaces given that the HL7 v2.4 spec
>> ‘Chapter 2.9.48 TX – text data’ says ‘Leading spaces should be included’?
>>
>> ·         I can’t find any reference in the rest of the HL7 v2.4 spec
>> which mentions the trimming of leading spaces. Have I missed this, or why
>> has HAPI chosen to trim?
>>
>>
>>
>> Regards,
>>
>> David Bunzli
>>
>> ************************************************************
>> ********************
>>
>> 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 <+61%201800%20198%20175> 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.
>>
>> ************************************************************
>> **********************
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Hl7api-devel mailing list
>> Hl7...@li...
>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>
>>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>
>

Re: [HAPI-devel] Lead spacing trimming

[James A. <jam...@gm...>]

Hi David,

I'm not sure I could provide an answer as to why, given that this behaviour
has existed in the library for roughly 15 years now.

I would be nervous about changing it given how longstanding it has existed,
but I can tell you that you can disable it by setting validation to
NoValidation (it's the validation engine that causes this trimming).

Cheers,
James

On Wed, May 24, 2017 at 11:37 PM, David Bunzli <
Dav...@he...> wrote:

> Hi,
>
>
>
> I’m experiencing a situation where an NTE-3 field handled by HAPI is
> trimming leading spaces, eg ‘  an FT string’ -> ‘an FT string’. My
> investigation lead me to the HAPI FAQ link http://hl7api.sourceforge.net/
> hapi-faq.html#leading_space which describes this behaviour for FT, ST and
> TX fields.
>
>
>
> My questions are:
>
> ·         why does HAPI trim leading spaces given that the HL7 v2.4 spec
> ‘Chapter 2.9.48 TX – text data’ says ‘Leading spaces should be included’?
>
> ·         I can’t find any reference in the rest of the HL7 v2.4 spec
> which mentions the trimming of leading spaces. Have I missed this, or why
> has HAPI chosen to trim?
>
>
>
> Regards,
>
> David Bunzli
>
> ************************************************************
> ********************
>
> 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 <+61%201800%20198%20175> 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.
>
> ************************************************************
> **********************
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>
>

[HAPI-devel] Lead spacing trimming

[David B. <Dav...@he...>]

Hi,

I'm experiencing a situation where an NTE-3 field handled by HAPI is trimming leading spaces, eg '  an FT string' -> 'an FT string'. My investigation lead me to the HAPI FAQ link http://hl7api.sourceforge.net/hapi-faq.html#leading_space which describes this behaviour for FT, ST and TX fields.

My questions are:

*         why does HAPI trim leading spaces given that the HL7 v2.4 spec 'Chapter 2.9.48 TX - text data' says 'Leading spaces should be included'?

*         I can't find any reference in the rest of the HL7 v2.4 spec which mentions the trimming of leading spaces. Have I missed this, or why has HAPI chosen to trim?

Regards,
David Bunzli

********************************************************************************
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.
**********************************************************************************

[HAPI-devel] MessageVisitor & Location - a bug?

[Conway T. <Tho...@pe...>]

Hi Hapi Devels,

I’m loving your stack – it’s beautifully done.

I’m using HL7 v 2.5.1, and using MessageVisitor to build a different representation of the message to use in another system, and it seems that the field repeat of the Location object is not correctly set. In particular, when traversing PID-3, the patient identifier list, which is a repeating field, the result returned by Location.getFieldRepetition() is always –1, indicating that it is not repeated. However, the traversal does correctly visit multiple CXs, it’s just the location information that is incorrect.

I couldn’t see anything indicating that this is a known problem. Anyone?

Tom.


Dr Thomas Conway

Senior Research Scientist

Peter MacCallum Cancer Centre

http://www.petermac.org<http://www.petermac.org/>


Phone: +61 3 9656 1575

Mobile: +61 416 611 073

Email: tho...@pe...


[unknown.png]

[unknown_1.png]


This email (including any attachments or links) may contain 
confidential and/or legally privileged information and is 
intended only to be read or used by the addressee.  If you 
are not the intended addressee, any use, distribution, 
disclosure or copying of this email is strictly 
prohibited.  
Confidentiality and legal privilege attached to this email 
(including any attachments) are not waived or lost by 
reason of its mistaken delivery to you.
If you have received this email in error, please delete it 
and notify us immediately by telephone or email.  Peter 
MacCallum Cancer Centre provides no guarantee that this 
transmission is free of virus or that it has not been 
intercepted or altered and will not be liable for any delay 
in its receipt.

[HAPI-devel] HL7 over HTTP

[Ian J. <ipj...@ya...>]

Hi All,
I'm curious where the specification stands for pushing HL7 over HTTP. I'm interested in implementing it for ASP.Net Core as MLLP has so many draw backs.
Thanks-Ian

Re: [HAPI-devel] HAPI Test Panel source code?

[Pablo P. <pab...@ca...>]

Hi James,

I downloaded the code and tried to build with mvn, some of the projects are
built OK, but most fail to build during dependency problems.

Is there any guide to build the test panel? I want to debug it and find
what is causing issues on Mac and Linux.

BTW, I cloned it to github https://github.com/ppazos/hapi-testpanel
(includes all the hapi rpojects really).

Thanks.



On Mon, Apr 24, 2017 at 10:23 PM, Pablo Pazos <pab...@ca...>
wrote:

> Hi James,
>
> I recently tested HAPI Test Panel on linux and I'm seeing the same
> behavior I had on MacOS for the webstart version. One issue is when I try
> to create a sample message selecting the version and message type, shows an
> empty alert box and the message is not created.
>
> Not sure what is the issue here.
>
> BTW, is there any plan to move the code to github?
>
> On Tue, Sep 27, 2016 at 3:56 PM, James Agnew <jam...@gm...> wrote:
>
>> Hi Pablo,
>>
>> The source for the test panel can be found here: https://sourceforge.net/
>> p/hl7api/code/HEAD/tree/trunk/hapi-mvn/hapi-testpanel/
>>
>> For what it's worth, I recently got it working on OSX by using the Linux
>> build. It seems like recent versions of OSX don't like the binary format
>> produced by the Maven plugin we used to bundle the testpanel, but the Linux
>> build just uses a shell script and that works fine.
>>
>> Cheers,
>> James
>>
>> On Tue, Sep 20, 2016 at 11:22 AM, Pablo Pazos <pab...@ca...>
>> wrote:
>>
>>> Hi,
>>>
>>> I'm trying to use the HAPI Test Panel on a Mac and the downloaded
>>> binaries don't work. The Java web start version has some issues, give empty
>>> alerts when creating a sample message, etc.
>>>
>>> I want to build the test panel on my mac to see if I can avoid or fix
>>> these errors, but it seems the source code is not available.
>>>
>>> Can anyone point me out where the source code is and how can I
>>> contribute to the project? It seems the project stuck 4 years ago and is
>>> starting to not work on modern environments.
>>>
>>>
>>> Thanks.
>>>
>>> --
>>> Ing. Pablo Pazos Gutiérrez
>>> Cel:(00598) 99 043 145 <099%20043%20145>
>>> Skype: cabolabs
>>> <http://cabolabs.com/>
>>> http://www.cabolabs.com
>>> pab...@ca...
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>>
>>> _______________________________________________
>>> Hl7api-devel mailing list
>>> Hl7...@li...
>>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>>
>>>
>>
>
>
> --
> Ing. Pablo Pazos Gutiérrez
> Cel:(00598) 99 043 145 <099%20043%20145>
> Skype: cabolabs
> <http://cabolabs.com/>
> http://www.cabolabs.com
> pab...@ca...
> Subscribe to our newsletter <http://eepurl.com/b_w_tj>
>



-- 
Ing. Pablo Pazos Gutiérrez
Cel:(00598) 99 043 145
Skype: cabolabs
<http://cabolabs.com/>
http://www.cabolabs.com
pab...@ca...
Subscribe to our newsletter <http://eepurl.com/b_w_tj>

Re: [HAPI-devel] HAPI Test Panel source code?

[Pablo P. <pab...@ca...>]

Hi James,

I recently tested HAPI Test Panel on linux and I'm seeing the same behavior
I had on MacOS for the webstart version. One issue is when I try to create
a sample message selecting the version and message type, shows an empty
alert box and the message is not created.

Not sure what is the issue here.

BTW, is there any plan to move the code to github?

On Tue, Sep 27, 2016 at 3:56 PM, James Agnew <jam...@gm...> wrote:

> Hi Pablo,
>
> The source for the test panel can be found here: https://sourceforge.net/
> p/hl7api/code/HEAD/tree/trunk/hapi-mvn/hapi-testpanel/
>
> For what it's worth, I recently got it working on OSX by using the Linux
> build. It seems like recent versions of OSX don't like the binary format
> produced by the Maven plugin we used to bundle the testpanel, but the Linux
> build just uses a shell script and that works fine.
>
> Cheers,
> James
>
> On Tue, Sep 20, 2016 at 11:22 AM, Pablo Pazos <pab...@ca...>
> wrote:
>
>> Hi,
>>
>> I'm trying to use the HAPI Test Panel on a Mac and the downloaded
>> binaries don't work. The Java web start version has some issues, give empty
>> alerts when creating a sample message, etc.
>>
>> I want to build the test panel on my mac to see if I can avoid or fix
>> these errors, but it seems the source code is not available.
>>
>> Can anyone point me out where the source code is and how can I contribute
>> to the project? It seems the project stuck 4 years ago and is starting to
>> not work on modern environments.
>>
>>
>> Thanks.
>>
>> --
>> Ing. Pablo Pazos Gutiérrez
>> Cel:(00598) 99 043 145 <099%20043%20145>
>> Skype: cabolabs
>> <http://cabolabs.com/>
>> http://www.cabolabs.com
>> pab...@ca...
>>
>> ------------------------------------------------------------
>> ------------------
>>
>> _______________________________________________
>> Hl7api-devel mailing list
>> Hl7...@li...
>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>
>>
>


-- 
Ing. Pablo Pazos Gutiérrez
Cel:(00598) 99 043 145
Skype: cabolabs
<http://cabolabs.com/>
http://www.cabolabs.com
pab...@ca...
Subscribe to our newsletter <http://eepurl.com/b_w_tj>

Re: [HAPI-devel] how to TCP Client that doesn't send messages

[Pablo P. <pab...@ca...>]

You can create a broker that does what you need. In hl7 who sends is the
client.

On Apr 20, 2017 8:39 PM, "Lucila Armentano" <arm...@gm...>
wrote:

Thanks but I need to connect to an analyzer that only accepts TCP Client
connections. I tested it with Hercules app, and when I connected Hercules
as a TCP client I started to receive ORU messages.

I was reading the HAPI doc and I believe that I could create a Receiver
over the client connection obtained with ctx.newClient()... , but I'm not
sure if I'm misunderstanding the Receiver class concept.

any suggestion?

Thanks,



-- 
*Lucila*

------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Hl7api-devel mailing list
Hl7...@li...
https://lists.sourceforge.net/lists/listinfo/hl7api-devel

Re: [HAPI-devel] how to TCP Client that doesn't send messages

[Lucila A. <arm...@gm...>]

Thanks but I need to connect to an analyzer that only accepts TCP Client
connections. I tested it with Hercules app, and when I connected Hercules
as a TCP client I started to receive ORU messages.

I was reading the HAPI doc and I believe that I could create a Receiver
over the client connection obtained with ctx.newClient()... , but I'm not
sure if I'm misunderstanding the Receiver class concept.

any suggestion?

Thanks,



-- 
*Lucila*

Re: [HAPI-devel] how to TCP Client that doesn't send messages

[Christopher S. <cs...@mi...>]

What you're describing is a Server not a Client. What you probably want is HL7Service, by using HapiContext.newServer()

For example usage see
http://hl7api.sourceforge.net/xref/ca/uhn/hl7v2/examples/SendAndReceiveAMessage.html

--
Christopher Speck



> On Apr 20, 2017, at 3:56 PM, Lucila Armentano <arm...@gm...> wrote:
> 
> Hello,
> I need to create a TCP Client for connecting to a server that automatically sends Messages (ORU).
> I couldn't do this by using de newClient() method of HapiContext, because it only receives messages after sending one.
> 
> Is it possibly to create a client with a "Receiver" or some object that stablish a client connection and waits a message from the server?
> 
> Thanks a lot
> 
> 
> Lucila
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel

[HAPI-devel] how to TCP Client that doesn't send messages

[Lucila A. <arm...@gm...>]

Hello,
I need to create a TCP Client for connecting to a server that automatically
sends Messages (ORU).
I couldn't do this by using de newClient() method of HapiContext, because
it only receives messages after sending one.

Is it possibly to create a client with a "Receiver" or some object that
stablish a client connection and waits a message from the server?

Thanks a lot


Lucila

Re: [HAPI-devel] Empty Message field reps change after encode

[Christian O. <chr...@gm...>]

Thank you, I will have a look at this - probably takes a few more days 
until I find some time...

cheers
Christian

Am 20.03.2017 um 17:12 schrieb Christopher Speck:
> I have tested this and it does seem to be a bug. Comparing the original parsed string with the encoded result shows that the encoded result contains an extra carriage return, but otherwise equal.
>
> The first calls to rde_o11.getORDER(0).getRXCReps() and rde_o11.getPATIENT().getAL1Reps() will create new empty reps because that group is marked as "repeating" (see AbstractGroup.get(String name, int rep) where rep == list.size() which is empty). I am not familiar enough to understand whether this is a bug but it seems like one - you should maybe post this into the issue tracker?
>
> Christopher
>
>
>
>> Hi,
>>
>> I have found a wierd case where calling .encode() on a Hapi message can end
>> up changing the number of reps returned by the Message object
>>
>> This code shoudl print out the same console output before and after the
>> .encode call.
>>
>> Unfortunately calling .encode() causes some of the reps to indicate that
>> they have values when in fact they are empty.....
>>
>> I suspect this is not limited to RDE_O11 either......
>>
>> final RDE_O11 rde_o11 = new RDE_O11();
>> rde_o11.parse("MSH|^~\\&|MSH3|MSH4|MSH5|MSH6|20161221133021||RDE^O11|MSH10|P|2.5");
>> System.out.println(rde_o11.getORDER(0).getRXCReps());
>> System.out.println(rde_o11.getORDERReps());
>> System.out.println(rde_o11.getPATIENT().getAL1Reps());
>>   rde_o11.encode();
>> System.out.println(rde_o11.getORDER(0).getRXCReps());
>> System.out.println(rde_o11.getORDERReps());
>> System.out.println(rde_o11.getPATIENT().getAL1Reps());
>>
>> This prints out 0, 1, 0 before the encode.
>>
>> But prints out 1, 1,1 after the encode.
>>
>> This definitely seems like a bug.
>>
>> -Mike
>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel

Re: [HAPI-devel] Empty Message field reps change after encode

[Christopher S. <cs...@mi...>]

I have tested this and it does seem to be a bug. Comparing the original parsed string with the encoded result shows that the encoded result contains an extra carriage return, but otherwise equal.

The first calls to rde_o11.getORDER(0).getRXCReps() and rde_o11.getPATIENT().getAL1Reps() will create new empty reps because that group is marked as "repeating" (see AbstractGroup.get(String name, int rep) where rep == list.size() which is empty). I am not familiar enough to understand whether this is a bug but it seems like one - you should maybe post this into the issue tracker?

Christopher



> Hi,
> 
> I have found a wierd case where calling .encode() on a Hapi message can end
> up changing the number of reps returned by the Message object
> 
> This code shoudl print out the same console output before and after the
> .encode call.
> 
> Unfortunately calling .encode() causes some of the reps to indicate that
> they have values when in fact they are empty.....
> 
> I suspect this is not limited to RDE_O11 either......
> 
> final RDE_O11 rde_o11 = new RDE_O11();
> rde_o11.parse("MSH|^~\\&|MSH3|MSH4|MSH5|MSH6|20161221133021||RDE^O11|MSH10|P|2.5");
> System.out.println(rde_o11.getORDER(0).getRXCReps());
> System.out.println(rde_o11.getORDERReps());
> System.out.println(rde_o11.getPATIENT().getAL1Reps());
>  rde_o11.encode();
> System.out.println(rde_o11.getORDER(0).getRXCReps());
> System.out.println(rde_o11.getORDERReps());
> System.out.println(rde_o11.getPATIENT().getAL1Reps());
> 
> This prints out 0, 1, 0 before the encode.
> 
> But prints out 1, 1,1 after the encode.
> 
> This definitely seems like a bug.
> 
> -Mike

[HAPI-devel] Empty Message field reps change after encode

[Mike M. <mi...@th...>]

Hi,

I have found a wierd case where calling .encode() on a Hapi message can end
up changing the number of reps returned by the Message object

This code shoudl print out the same console output before and after the
.encode call.

Unfortunately calling .encode() causes some of the reps to indicate that
they have values when in fact they are empty.....

I suspect this is not limited to RDE_O11 either......

final RDE_O11 rde_o11 = new RDE_O11();
rde_o11.parse("MSH|^~\\&|MSH3|MSH4|MSH5|MSH6|20161221133021||RDE^O11|MSH10|P|2.5");
System.out.println(rde_o11.getORDER(0).getRXCReps());
System.out.println(rde_o11.getORDERReps());
System.out.println(rde_o11.getPATIENT().getAL1Reps());
 rde_o11.encode();
System.out.println(rde_o11.getORDER(0).getRXCReps());
System.out.println(rde_o11.getORDERReps());
System.out.println(rde_o11.getPATIENT().getAL1Reps());

This prints out 0, 1, 0 before the encode.

But prints out 1, 1,1 after the encode.

This definitely seems like a bug.

-Mike

Re: [HAPI-devel] Configure message validation

[Ian V. <Ian...@he...>]

We have a plethora of systems that don’t strictly adhere to the standard, and have taken to turning off validation as our default position.

On your context use:

setValidationRuleBuilder(new NoValidationBuilder())

Validation will not be performed.

Ian Vowles
Queensland Health
Australia

From: Jonny Rylands [mailto:jon...@vi...]
Sent: Friday, 27 January 2017 1:31 AM
To: hl7...@li...
Subject: [HAPI-devel] Configure message validation

Hi

Is it possible to disable or configure message content validation so that messages which fail validation continue to be sent to the receiving application?

Here’s a bit of background:

I have an HL7 service which receives messages over MLLP, does some processing, and forwards them to another destination.  The HL7Service class code I’m using is below.

I am receiving messages that are invalid against the specification from an endpoint over which I cannot change.

These are currently being sent straight to the ExceptionHandler.  I’m like these to continue to be sent to the receiving application so I can transform them to become valid messages.

HapiContext context = new DefaultHapiContext();
HL7Service service = context.newServer(channel.getPortNumber(), channel.isUseTls());
service.registerApplication("*", "*", new Hl7ReceivingApplication());
service.registerConnectionListener(new Hl7ConnectionListener());
service.setExceptionHandler(new Hl7ExceptionHandler());
service.startAndWait();

Many thanks
Jonny



********************************************************************************
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.
**********************************************************************************

[HAPI-devel] Configure message validation

[Jonny R. <jon...@vi...>]

Hi

Is it possible to disable or configure message content validation so that messages which fail validation continue to be sent to the receiving application?

Here’s a bit of background:

I have an HL7 service which receives messages over MLLP, does some processing, and forwards them to another destination.  The HL7Service class code I’m using is below.

I am receiving messages that are invalid against the specification from an endpoint over which I cannot change.

These are currently being sent straight to the ExceptionHandler.  I’m like these to continue to be sent to the receiving application so I can transform them to become valid messages.

HapiContext context = new DefaultHapiContext();
HL7Service service = context.newServer(channel.getPortNumber(), channel.isUseTls());
service.registerApplication("*", "*", new Hl7ReceivingApplication());
service.registerConnectionListener(new Hl7ConnectionListener());
service.setExceptionHandler(new Hl7ExceptionHandler());
service.startAndWait();

Many thanks
Jonny

Re: [HAPI-devel] Upcoming Release and migration to GitHub

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

Great news! Keep up the good work

Den 19. dec. 2016 8.55 PM skrev "James Agnew" <jam...@gm...>:

> Hello All,
>
> Two quick notes:
>
> 1. HAPI's HL7v2 codebase has been migrated to GitHub, and can now be found
> here: https://github.com/hapifhir/hapi-hl7v2/
>
> This should allow us to more easily accept patches, and should make the
> project more manageable generally as time goes on. I'm also planning on
> changing the model a bit so that the generated structures get checked into
> the repo, so that anyone can build the complete library whether they have
> the HL7 Database or not.
>
> 2. We're weeks away from our next release (HAPI Hl7v2 2.3) which will
> bring support for versions of HL7v2 up to v2.8.1.
>
> Cheers,
> James
>
> ------------------------------------------------------------
> ------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today.http://sdm.link/intel
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>
>

[HAPI-devel] Upcoming Release and migration to GitHub

[James A. <jam...@gm...>]

Hello All,

Two quick notes:

1. HAPI's HL7v2 codebase has been migrated to GitHub, and can now be found
here: https://github.com/hapifhir/hapi-hl7v2/

This should allow us to more easily accept patches, and should make the
project more manageable generally as time goes on. I'm also planning on
changing the model a bit so that the generated structures get checked into
the repo, so that anyone can build the complete library whether they have
the HL7 Database or not.

2. We're weeks away from our next release (HAPI Hl7v2 2.3) which will bring
support for versions of HL7v2 up to v2.8.1.

Cheers,
James

Re: [HAPI-devel] Tying a received message to a connection

[Jonny R. <jon...@vi...>]

James – many thanks for your help.

Regards
Jonny

From: James Agnew <jam...@gm...>
Date: Tuesday, 6 December 2016 at 16:00
To: Jonny Rylands <jon...@vi...>
Cc: "hl7...@li..." <hl7...@li...>
Subject: Re: [HAPI-devel] Tying a received message to a connection

Hi Jonny,

Have a look at MetadataKeys.java. These can be used as keys in the ReceivingApplication (assuming you're using ApplicationRouter) to get the originating IP and port. It's not a reference to the connection exactly but it could be used to figure it out.

Cheers,
James

On Tue, Dec 6, 2016 at 5:27 AM, Jonny Rylands <jon...@vi...<mailto:jon...@vi...>> wrote:
Hi folks

I have a small HAPI based server application to receive messages and forward them to another destination.

I was wondering, is there a way to tie together Connections that are notified to the ConnectionListener with Messages that are notified to the ReceivingApplication?

I’d like to be able to record a set of messages that were received against a particular connection.

I’m configuring the receiving service in a standard way:

HapiContext context = new DefaultHapiContext();
HL7Service service = context.newServer(channel.getPortNumber(), channel.isUseTls());
service.registerApplication("*", "*", new Hl7ReceivingApplication());
service.registerConnectionListener(new Hl7ConnectionListener());
service.setExceptionHandler(new Hl7ExceptionHandler());
service.startAndWait();

Many thanks
Jonny

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
_______________________________________________
Hl7api-devel mailing list
Hl7...@li...<mailto:Hl7...@li...>
https://lists.sourceforge.net/lists/listinfo/hl7api-devel

Re: [HAPI-devel] Tying a received message to a connection

[James A. <jam...@gm...>]

Hi Jonny,

Have a look at MetadataKeys.java. These can be used as keys in the
ReceivingApplication (assuming you're using ApplicationRouter) to get the
originating IP and port. It's not a reference to the connection exactly but
it could be used to figure it out.

Cheers,
James

On Tue, Dec 6, 2016 at 5:27 AM, Jonny Rylands <
jon...@vi...> wrote:

> Hi folks
>
>
>
> I have a small HAPI based server application to receive messages and
> forward them to another destination.
>
>
>
> I was wondering, is there a way to tie together Connections that are
> notified to the ConnectionListener with Messages that are notified to the
> ReceivingApplication?
>
>
>
> I’d like to be able to record a set of messages that were received against
> a particular connection.
>
>
>
> I’m configuring the receiving service in a standard way:
>
>
>
> HapiContext context = new DefaultHapiContext();
>
> HL7Service service = context.newServer(channel.getPortNumber(),
> channel.isUseTls());
>
> service.registerApplication("*", "*", new Hl7ReceivingApplication());
> service.registerConnectionListener(new Hl7ConnectionListener());
> service.setExceptionHandler(new Hl7ExceptionHandler());
> service.startAndWait();
>
>
>
> Many thanks
>
> Jonny
>
> ------------------------------------------------------------
> ------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today.http://sdm.link/xeonphi
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>
>

[HAPI-devel] Tying a received message to a connection

[Jonny R. <jon...@vi...>]

Hi folks

I have a small HAPI based server application to receive messages and forward them to another destination.

I was wondering, is there a way to tie together Connections that are notified to the ConnectionListener with Messages that are notified to the ReceivingApplication?

I’d like to be able to record a set of messages that were received against a particular connection.

I’m configuring the receiving service in a standard way:

HapiContext context = new DefaultHapiContext();
HL7Service service = context.newServer(channel.getPortNumber(), channel.isUseTls());
service.registerApplication("*", "*", new Hl7ReceivingApplication());
service.registerConnectionListener(new Hl7ConnectionListener());
service.setExceptionHandler(new Hl7ExceptionHandler());
service.startAndWait();

Many thanks
Jonny