hl7api-devel — developer list

Re: [HAPI-devel] Basic question

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

No - HAPI is not built for HL7v3 - its for HL7v2

On 27 November 2016 at 19:24, Sterpu Victor <vi...@ca...> wrote:

> Hello
>
> Can I parse a HL7 v3 XML with Happy?
> I want to display as simple as possible the contents of such a XML.
> Does Happy support HL7 v3?
>
> Thank you.
>
> ------------------------------------------------------------
> ------------------
>
> _______________________________________________
> 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...

[HAPI-devel] Basic question

[Sterpu V. <vi...@ca...>]

Hello

Can I parse a HL7 v3 XML with Happy?
I want to display as simple as possible the contents of such a XML.
Does Happy support HL7 v3?

Thank you.

[HAPI-devel] Question on HAPI

[Shankar S <s_s...@ya...>]

Hi
I am new to this forum and I had a basic question: Does the HL7 parser parse all messages or does it parse only a subset of HL7 messages in the standard? If so which ones.

ThanksShankar

Re: [HAPI-devel] Distinguish segment as standard or non-standard

[Ankit S. <shr...@gm...>]

Is there any method available to get the no of segments present in a
message for a specified message ???
Eg: I would want to get a count of segment "GT1" in the message.

How to I get the count ?

On Thu, Sep 29, 2016 at 8:49 AM, James Agnew <jam...@gm...> wrote:

> I don't think there is a direct way but you could always create a new
> empty message instance and compare the results of the getNames() method.
>
> sent from my phone.
>
> On Sep 28, 2016 10:31 PM, "Ankit Shrestha" <shr...@gm...>
> wrote:
>
>> Hello,
>> Is it possible to distinguish a segment name as standard or non-standard
>> ? Adding a non-standard segment ( segment name already exists ), appends a
>> integer to segment name as it's parent identifies. But is it possible to
>> get values of all the possible segment ( regardless of standard or
>> non-standard) ) using only the segment name. Please answer with a code
>> example.
>>
>> ------------------------------------------------------------
>> ------------------
>>
>> _______________________________________________
>> Hl7api-devel mailing list
>> Hl7...@li...
>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>
>>

Re: [HAPI-devel] Distinguish segment as standard or non-standard

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

I don't think there is a direct way but you could always create a new empty
message instance and compare the results of the getNames() method.

sent from my phone.

On Sep 28, 2016 10:31 PM, "Ankit Shrestha" <shr...@gm...> wrote:

> Hello,
> Is it possible to distinguish a segment name as standard or non-standard ?
> Adding a non-standard segment ( segment name already exists ), appends a
> integer to segment name as it's parent identifies. But is it possible to
> get values of all the possible segment ( regardless of standard or
> non-standard) ) using only the segment name. Please answer with a code
> example.
>
> ------------------------------------------------------------
> ------------------
>
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>
>

[HAPI-devel] Distinguish segment as standard or non-standard

[Ankit S. <shr...@gm...>]

Hello,
Is it possible to distinguish a segment name as standard or non-standard ?
Adding a non-standard segment ( segment name already exists ), appends a
integer to segment name as it's parent identifies. But is it possible to
get values of all the possible segment ( regardless of standard or
non-standard) ) using only the segment name. Please answer with a code
example.

[HAPI-devel] StructureDefination initialization problem.

[Ankit S. <shr...@gm...>]

Hello,
 I am having problem to initialize StructureDefination of class
"ca.uhn.hl7v2.parser.StructureDefinition". There is a constructor to but
with empty parameters. Searching didn't gave me any results. It is possible
to initialize this class. Please demonstrate with a code example.
Thanks.

Re: [HAPI-devel] hl7api SegmentFinder.java performance fix

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

Submit your request here:

https://sourceforge.net/p/hl7api/feature-requests/

It will then be picked up by the development group

On 28 September 2016 at 13:20, Niels Ull Harremoës <
nie...@re...> wrote:

> Did anyone ever look at this? Does anyone care?
>
> I also sent it to the address on the website, jam...@so...,
> but it bounced.
>
> Regards, Niels Harremoës
>
>
>
> *Fra:* Niels Ull Harremoës [mailto:nie...@re...]
> *Sendt:* 7. juni 2016 12:10
> *Til:* HAPI Devel List
> *Emne:* [HAPI-devel] hl7api SegmentFinder.java performance fix
>
>
>
> I was profiling some of our code which uses HL7, and I noticed that we had
> a large number of calls to java.util.Pattern#compile.
>
>
>
> I tracked a number of them down to SegmentFinder#matches method. I would
> therefore suggest the patch below, which cuts down the number of
> Pattern#compile calls from 4 to 1.
>
>
>
> The unit tests passes. I have written the code myself and would like to
> submit it under the same GPL/MPL license as the rest of the code.
>
>
>
>
>
> Regards,
>
> Niels Harremoës
>
>
>
>
>
>
>
>
>
> Index: SegmentFinder.java
>
> ===================================================================
>
> --- SegmentFinder.java   (revision 983)
>
> +++ SegmentFinder.java (working copy)
>
> @@ -157,8 +157,13 @@
>
>          }
>
>          return matches;
>
>      }*/
>
> -
>
> +
>
>      /**
>
> +     * Patterns used for matching can only contain these characters
>
> +     */
>
> +    private static final Pattern VALID_PATTERN_PATTERN =
> Pattern.compile("[\\w\\*\\?]*");
>
> +
>
> +    /**
>
>       * Tests whether the given name matches the given pattern.
>
>       */
>
>      private boolean matches(String pattern, String candidate) {
>
> @@ -166,12 +171,12 @@
>
>          if (pattern.equals(candidate)) {
>
>              return true;
>
>          }
>
> -
>
> -        if (!Pattern.matches("[\\w\\*\\?]*", pattern))
>
> +
>
> +        if (!VALID_PATTERN_PATTERN.matcher(pattern).matches())
>
>              throw new IllegalArgumentException("The pattern " + pattern +
> " is not valid.  Only [\\w\\*\\?]* allowed.");
>
>
>
> -        pattern = Pattern.compile("\\*").matcher(pattern).replaceAll(".
> *");
>
> -        pattern = Pattern.compile("\\?").matcher(pattern).replaceAll(".
> ");
>
> +        pattern = pattern.replace("*",".*");
>
> +        pattern = pattern.replace('?','.');
>
>
>
>          return Pattern.matches(pattern, candidate);
>
>      }
>
>
>
>
>
>
>
> *Fra:* Ian Vowles [mailto:Ian...@he...
> <Ian...@he...>]
> *Sendt:* 6. juni 2016 23:43
> *Til:* HAPI Devel List
> *Emne:* [HAPI-devel] RDS and RDE O01 messages
>
>
>
> Is it possible to get a parser to recognise an implementation for RDS and
> RDE O01 messages?  My attempts so far have only returned a GenericMessage
> implementation. The HAPI structures have RDS_O13 and RDE_O11 but there
> doesn’t appear to be a mapping of RDE or RDS messages in model\v24\message
> 2.4.properties (or v25).
>
>
>
> Thanks
>
> Ian Vowles
>
> Systems Integration Team
>
> eHealth Queensland,
>
> Australia
>
> ************************************************************
> ********************
>
> 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.
>
> ************************************************************
> **********************
>
>
> ------------------------------
>
>
>
> Denne e-mail indeholder fortrolig information. Hvis du ikke er den rette
> modtager af denne e-mail eller hvis du modtager den ved en fejltagelse,
> beder vi dig venligst informere afsender om fejlen ved at bruge
> svarfunktionen. Samtidig bedes du slette e-mailen med det samme uden at
> videresende eller kopiere den.
>
> ------------------------------
>
>
> Denne e-mail indeholder fortrolig information. Hvis du ikke er den rette
> modtager af denne e-mail eller hvis du modtager den ved en fejltagelse,
> beder vi dig venligst informere afsender om fejlen ved at bruge
> svarfunktionen. Samtidig bedes du slette e-mailen med det samme uden at
> videresende eller kopiere den.
>
> ------------------------------------------------------------
> ------------------
>
> _______________________________________________
> 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...

Re: [HAPI-devel] hl7api SegmentFinder.java performance fix

[Niels U. H. <nie...@re...>]

Did anyone ever look at this? Does anyone care?
I also sent it to the address on the website, jam...@so...<mailto:jam...@so...>, but it bounced.
Regards, Niels Harremoës

Fra: Niels Ull Harremoës [mailto:nie...@re...]
Sendt: 7. juni 2016 12:10
Til: HAPI Devel List
Emne: [HAPI-devel] hl7api SegmentFinder.java performance fix

I was profiling some of our code which uses HL7, and I noticed that we had a large number of calls to java.util.Pattern#compile.

I tracked a number of them down to SegmentFinder#matches method. I would therefore suggest the patch below, which cuts down the number of Pattern#compile calls from 4 to 1.

The unit tests passes. I have written the code myself and would like to submit it under the same GPL/MPL license as the rest of the code.


Regards,
Niels Harremoës




Index: SegmentFinder.java
===================================================================
--- SegmentFinder.java   (revision 983)
+++ SegmentFinder.java (working copy)
@@ -157,8 +157,13 @@
         }
         return matches;
     }*/
-
+
     /**
+     * Patterns used for matching can only contain these characters
+     */
+    private static final Pattern VALID_PATTERN_PATTERN = Pattern.compile("[\\w\\*\\?]*");
+
+    /**
      * Tests whether the given name matches the given pattern.
      */
     private boolean matches(String pattern, String candidate) {
@@ -166,12 +171,12 @@
         if (pattern.equals(candidate)) {
             return true;
         }
-
-        if (!Pattern.matches("[\\w\\*\\?]*", pattern))
+
+        if (!VALID_PATTERN_PATTERN.matcher(pattern).matches())
             throw new IllegalArgumentException("The pattern " + pattern + " is not valid.  Only [\\w\\*\\?]* allowed.");

-        pattern = Pattern.compile("\\*").matcher(pattern).replaceAll(".*");
-        pattern = Pattern.compile("\\?").matcher(pattern).replaceAll(".");
+        pattern = pattern.replace("*",".*");
+        pattern = pattern.replace('?','.');

         return Pattern.matches(pattern, candidate);
     }



Fra: Ian Vowles [mailto:Ian...@he...]
Sendt: 6. juni 2016 23:43
Til: HAPI Devel List
Emne: [HAPI-devel] RDS and RDE O01 messages

Is it possible to get a parser to recognise an implementation for RDS and RDE O01 messages?  My attempts so far have only returned a GenericMessage implementation. The HAPI structures have RDS_O13 and RDE_O11 but there doesn’t appear to be a mapping of RDE or RDS messages in model\v24\message 2.4.properties (or v25).

Thanks
Ian Vowles
Systems Integration Team
eHealth Queensland,
Australia

********************************************************************************

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.

**********************************************************************************

________________________________


Denne e-mail indeholder fortrolig information. Hvis du ikke er den rette modtager af denne e-mail eller hvis du modtager den ved en fejltagelse, beder vi dig venligst informere afsender om fejlen ved at bruge svarfunktionen. Samtidig bedes du slette e-mailen med det samme uden at videresende eller kopiere den.

________________________________


Denne e-mail indeholder fortrolig information. Hvis du ikke er den rette modtager af denne e-mail eller hvis du modtager den ved en fejltagelse, beder vi dig venligst informere afsender om fejlen ved at bruge svarfunktionen. Samtidig bedes du slette e-mailen med det samme uden at videresende eller kopiere den.

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

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

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

[HAPI-devel] HAPI Test Panel source code?

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

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
Skype: cabolabs
<http://cabolabs.com/>
http://www.cabolabs.com
pab...@ca...

[HAPI-devel] running test panel on Mac OS

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

Hi, I downloaded the latest HAPI Test Panel from sourceforge and it is
asking for "legacy Java 6".

Is there any possibility of updating the Mac Os build to run with Java 7 or
8?

On windows I didn't have any problems running HAPI Test panel with Java 7.

Thanks.

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

[HAPI-devel] How to Deal with Numeric Result Values with Whitespace

[John G. <jdg...@gm...>]

Some clients of mine hand edited a HL7 result message to fix bad OBX-5
values. I'm not sure why but they padded the value with spaces.

OBX Line:
OBX|5|NM|2231^Sodium||140  |mEq/L|133-146||||F|||20160706073500|ML||||||||||

Because this was a NM type it threw a exception, but how can I attempt to
trim these values prior to parsing?

[HAPI-devel] hl7api SegmentFinder.java performance fix

[Niels U. H. <nie...@re...>]

I was profiling some of our code which uses HL7, and I noticed that we had a large number of calls to java.util.Pattern#compile.

I tracked a number of them down to SegmentFinder#matches method. I would therefore suggest the patch below, which cuts down the number of Pattern#compile calls from 4 to 1.

The unit tests passes. I have written the code myself and would like to submit it under the same GPL/MPL license as the rest of the code.


Regards,
Niels Harremoës




Index: SegmentFinder.java
===================================================================
--- SegmentFinder.java   (revision 983)
+++ SegmentFinder.java (working copy)
@@ -157,8 +157,13 @@
         }
         return matches;
     }*/
-
+
     /**
+     * Patterns used for matching can only contain these characters
+     */
+    private static final Pattern VALID_PATTERN_PATTERN = Pattern.compile("[\\w\\*\\?]*");
+
+    /**
      * Tests whether the given name matches the given pattern.
      */
     private boolean matches(String pattern, String candidate) {
@@ -166,12 +171,12 @@
         if (pattern.equals(candidate)) {
             return true;
         }
-
-        if (!Pattern.matches("[\\w\\*\\?]*", pattern))
+
+        if (!VALID_PATTERN_PATTERN.matcher(pattern).matches())
             throw new IllegalArgumentException("The pattern " + pattern + " is not valid.  Only [\\w\\*\\?]* allowed.");

-        pattern = Pattern.compile("\\*").matcher(pattern).replaceAll(".*");
-        pattern = Pattern.compile("\\?").matcher(pattern).replaceAll(".");
+        pattern = pattern.replace("*",".*");
+        pattern = pattern.replace('?','.');

         return Pattern.matches(pattern, candidate);
     }



Fra: Ian Vowles [mailto:Ian...@he...]
Sendt: 6. juni 2016 23:43
Til: HAPI Devel List
Emne: [HAPI-devel] RDS and RDE O01 messages

Is it possible to get a parser to recognise an implementation for RDS and RDE O01 messages?  My attempts so far have only returned a GenericMessage implementation. The HAPI structures have RDS_O13 and RDE_O11 but there doesn’t appear to be a mapping of RDE or RDS messages in model\v24\message 2.4.properties (or v25).

Thanks
Ian Vowles
Systems Integration Team
eHealth Queensland,
Australia

********************************************************************************

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.

**********************************************************************************

________________________________


Denne e-mail indeholder fortrolig information. Hvis du ikke er den rette modtager af denne e-mail eller hvis du modtager den ved en fejltagelse, beder vi dig venligst informere afsender om fejlen ved at bruge svarfunktionen. Samtidig bedes du slette e-mailen med det samme uden at videresende eller kopiere den.

Re: [HAPI-devel] RDS and RDE O01 messages

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

Found it!

Vendor told us it was v2.5, but they are using the v2.3 structure (plus Z segments), which is present in the 2.3 library.  Either way we will build a new message for this vendor, since they are problematic due to consistent issues like this.

Thanks
Ian Vowles
Systems Integration Team
eHealth Queensland,
Australia

From: Ian Vowles [mailto:Ian...@he...]
Sent: Tuesday, 7 June 2016 7:43 AM
To: HAPI Devel List
Subject: [HAPI-devel] RDS and RDE O01 messages

Is it possible to get a parser to recognise an implementation for RDS and RDE O01 messages?  My attempts so far have only returned a GenericMessage implementation. The HAPI structures have RDS_O13 and RDE_O11 but there doesn’t appear to be a mapping of RDE or RDS messages in model\v24\message 2.4.properties (or v25).

Thanks
Ian Vowles
Systems Integration Team
eHealth Queensland,
Australia

********************************************************************************

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] RDS and RDE O01 messages

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

Is it possible to get a parser to recognise an implementation for RDS and RDE O01 messages?  My attempts so far have only returned a GenericMessage implementation. The HAPI structures have RDS_O13 and RDE_O11 but there doesn’t appear to be a mapping of RDE or RDS messages in model\v24\message 2.4.properties (or v25).

Thanks
Ian Vowles
Systems Integration Team
eHealth Queensland,
Australia

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

Re: [HAPI-devel] How to parse NK1 segment in HL7 v2.1

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

Seeing the full format of the message or the printstructure might help with offering an explanation for the NK12 tag.  I seem to remember seeing this where a segment fell outside it’s expected group location, but that was a long time ago and I may be on the wrong track.

Mind you, the Structure array returned by the getAll isn’t that easy to deal with.  I added a second NK1 to my message, and was able to get a sensible output from this code IF I used a version higher than 2.1. The NK12 tag comes about because the standard did not allow multiple NK1 segments until version 2.2.  Your printstructure should have shown the second NK1 as a non-standard segment.

        Structure[] nk1Segments = hapiMessage.getAll("NK1");
        System.out.println("There are " + nk1Segments.length + " NK1 segments present.");
        Structure struct1 = nk1Segments[0];
        Structure struct2 = nk1Segments[1];
        System.out.println(((NK1) struct1).getNk12_NKName(0).getGivenName().getValue());
        System.out.println(((NK1) struct2).getNk12_NKName(0).getGivenName().getValue());

We have a tendency here to ensure that the structures we use in our code are from a higher version of the standard than the sender claims they are, because frequently senders will say they are 2.x but have added a field or segment that are from 2.x+y without realising.

Ian

From: Dayu Han [mailto:da...@st...]
Sent: Wednesday, 18 May 2016 2:28 AM
To: Ian Vowles
Cc: HAPI Devel List
Subject: Re: [HAPI-devel] How to parse NK1 segment in HL7 v2.1

Hi Ian

I solved the issue by using printStructure, content in segment NK1 is actually translated into segment NK12. No idea why, but it works now.

Thanks
Dayu

On May 17, 2016, at 8:06 AM, Dayu Han <da...@st...<mailto:da...@st...>> wrote:

Thanks for the reply Ian. This is what I have tried.

With NK1 segment as:
NK1||Test^Walls|SO|206-8404 Nowhere Rd^^Eastend^AA^H0H 0H0|123-488-1234|||

notice there is no set index, calling message.getAll("NK1”) returns no elements.

If NK1segment has set index:
NK1|1|Test^Walls|SO|206-8404 Nowhere Rd^^Eastend^AA^H0H 0H0|123-488-1234|||

calling message.getAll(“NK1”) returns 1 element. But if I cast the element to NK1, I couldn’t get any content out of it.

Any comments ?

Thanks
Dayu

On May 16, 2016, at 9:15 PM, Ian Vowles <Ian...@he...<mailto:Ian...@he...>> wrote:

I adjusted an earlier message example I had played with to try out the message.getall() that you are using. See below.  It looked to work ok, so I’m not able to offer much more. You may note that I went through a parse step on a message string first, before trying to use getAll.  I presume you had similar code. I am also a big supporter of using printstructure when I am trying things out.  It helps me avoid invalid assumptions about how HAPI has parsed the message.

Ian

Code example:

        String msg = "MSH|^~\\&|SCM|SCM|HL7ADT||20130114001147||ADT^A08|8456356603013|P|2.1\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());
        Structure[] nk1Segments = hapiMessage.getAll("NK1");
        System.out.println("There are " + nk1Segments.length + " NK1 segments present.");

From: Dayu Han [mailto:da...@st...]
Sent: Tuesday, 17 May 2016 7:56 AM
To: HAPI Devel List
Subject: Re: [HAPI-devel] How to parse NK1 segment in HL7 v2.1

Hello

In processing HL7 ADT message v2.1, I use the following code to parse NK1 segment:

Structure[] nk1Segments = message.getAll("NK1”);

However, this returns no element. My question is how to get ALL NK1 segments directly ?

Thanks
Dayu
--
Dayu Han
Software Developer
Strata Health Solutions
Office: +1.403.261.0855 x2102
Website<http://www.stratahealth.com/> | Overview Video<http://youtu.be/5wHGcurxMyY> | Resources<http://www.stratahealth.com/resources/>





********************************************************************************
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.
**********************************************************************************
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j_______________________________________________
Hl7api-devel mailing list
Hl7...@li...<mailto:Hl7...@li...>
https://lists.sourceforge.net/lists/listinfo/hl7api-devel












------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j_______________________________________________
Hl7api-devel mailing list
Hl7...@li...
https://lists.sourceforge.net/lists/listinfo/hl7api-devel

--
Dayu Han
Software Developer
Strata Health Solutions
Office: +1.403.261.0855 x2102
Website<http://www.stratahealth.com/> | Overview Video<http://youtu.be/5wHGcurxMyY> | Resources<http://www.stratahealth.com/resources/>

Re: [HAPI-devel] How to parse NK1 segment in HL7 v2.1

[Dayu H. <da...@st...>]

Hi Ian

I solved the issue by using printStructure, content in segment NK1 is actually translated into segment NK12. No idea why, but it works now.

Thanks
Dayu

> On May 17, 2016, at 8:06 AM, Dayu Han <da...@st...> wrote:
> 
> Thanks for the reply Ian. This is what I have tried.
> 
> With NK1 segment as:
> NK1||Test^Walls|SO|206-8404 Nowhere Rd^^Eastend^AA^H0H 0H0|123-488-1234|||
> 
> notice there is no set index, calling message.getAll("NK1”) returns no elements.
> 
> If NK1segment has set index:
> NK1|1|Test^Walls|SO|206-8404 Nowhere Rd^^Eastend^AA^H0H 0H0|123-488-1234|||
> 
> calling message.getAll(“NK1”) returns 1 element. But if I cast the element to NK1, I couldn’t get any content out of it.
> 
> Any comments ?
> 
> Thanks
> Dayu
> 
>> On May 16, 2016, at 9:15 PM, Ian Vowles <Ian...@he... <mailto:Ian...@he...>> wrote:
>> 
>> I adjusted an earlier message example I had played with to try out the message.getall() that you are using. See below.  It looked to work ok, so I’m not able to offer much more. You may note that I went through a parse step on a message string first, before trying to use getAll.  I presume you had similar code. I am also a big supporter of using printstructure when I am trying things out.  It helps me avoid invalid assumptions about how HAPI has parsed the message.
>>  
>> Ian
>>  
>> Code example: 
>>  
>>         String msg = "MSH|^~\\&|SCM|SCM|HL7ADT||20130114001147||ADT^A08|8456356603013|P|2.1\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());
>>         Structure[] nk1Segments = hapiMessage.getAll("NK1");
>>         System.out.println("There are " + nk1Segments.length + " NK1 segments present.");
>>  
>> From: Dayu Han [mailto:da...@st... <mailto:da...@st...>] 
>> Sent: Tuesday, 17 May 2016 7:56 AM
>> To: HAPI Devel List
>> Subject: Re: [HAPI-devel] How to parse NK1 segment in HL7 v2.1
>>  
>> Hello
>>  
>> In processing HL7 ADT message v2.1, I use the following code to parse NK1 segment:
>>  
>> Structure[] nk1Segments = message.getAll("NK1”);
>>  
>> However, this returns no element. My question is how to get ALL NK1 segments directly ?
>>  
>> Thanks
>> Dayu
>> --
>> Dayu Han
>> Software Developer
>> Strata Health Solutions 
>> Office: +1.403.261.0855 x2102
>> Website <http://www.stratahealth.com/> | Overview Video <http://youtu.be/5wHGcurxMyY> | Resources <http://www.stratahealth.com/resources/>
>> 
>> 
>>  
>>  
>> ********************************************************************************
>> 
>> 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.
>> 
>> **********************************************************************************
>> 
>> ------------------------------------------------------------------------------
>> Mobile security can be enabling, not merely restricting. Employees who
>> bring their own devices (BYOD) to work are irked by the imposition of MDM
>> restrictions. Mobile Device Manager Plus allows you to control only the
>> apps on BYO-devices by containerizing them, leaving personal data untouched!
>> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j_______________________________________________ <https://ad.doubleclick.net/ddm/clk/304595813;131938128;j_______________________________________________>
>> Hl7api-devel mailing list
>> Hl7...@li... <mailto:Hl7...@li...>
>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel <https://lists.sourceforge.net/lists/listinfo/hl7api-devel>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j_______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel

--
Dayu Han
Software Developer
Strata Health Solutions 
Office: +1.403.261.0855 x2102
Website <http://www.stratahealth.com/> | Overview Video <http://youtu.be/5wHGcurxMyY> | Resources <http://www.stratahealth.com/resources/>

Re: [HAPI-devel] How to parse NK1 segment in HL7 v2.1

[Dayu H. <da...@st...>]

Thanks for the reply Ian. This is what I have tried.

With NK1 segment as:
NK1||Test^Walls|SO|206-8404 Nowhere Rd^^Eastend^AA^H0H 0H0|123-488-1234|||

notice there is no set index, calling message.getAll("NK1”) returns no elements.

If NK1segment has set index:
NK1|1|Test^Walls|SO|206-8404 Nowhere Rd^^Eastend^AA^H0H 0H0|123-488-1234|||

calling message.getAll(“NK1”) returns 1 element. But if I cast the element to NK1, I couldn’t get any content out of it.

Any comments ?

Thanks
Dayu

> On May 16, 2016, at 9:15 PM, Ian Vowles <Ian...@he...> wrote:
> 
> I adjusted an earlier message example I had played with to try out the message.getall() that you are using. See below.  It looked to work ok, so I’m not able to offer much more. You may note that I went through a parse step on a message string first, before trying to use getAll.  I presume you had similar code. I am also a big supporter of using printstructure when I am trying things out.  It helps me avoid invalid assumptions about how HAPI has parsed the message.
>  
> Ian
>  
> Code example: 
>  
>         String msg = "MSH|^~\\&|SCM|SCM|HL7ADT||20130114001147||ADT^A08|8456356603013|P|2.1\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());
>         Structure[] nk1Segments = hapiMessage.getAll("NK1");
>         System.out.println("There are " + nk1Segments.length + " NK1 segments present.");
>  
> From: Dayu Han [mailto:da...@st... <mailto:da...@st...>] 
> Sent: Tuesday, 17 May 2016 7:56 AM
> To: HAPI Devel List
> Subject: Re: [HAPI-devel] How to parse NK1 segment in HL7 v2.1
>  
> Hello
>  
> In processing HL7 ADT message v2.1, I use the following code to parse NK1 segment:
>  
> Structure[] nk1Segments = message.getAll("NK1”);
>  
> However, this returns no element. My question is how to get ALL NK1 segments directly ?
>  
> Thanks
> Dayu
> --
> Dayu Han
> Software Developer
> Strata Health Solutions 
> Office: +1.403.261.0855 x2102
> Website <http://www.stratahealth.com/> | Overview Video <http://youtu.be/5wHGcurxMyY> | Resources <http://www.stratahealth.com/resources/>
> 
> 
>  
>  
> ********************************************************************************
> 
> 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.
> 
> **********************************************************************************
> 
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j_______________________________________________ <https://ad.doubleclick.net/ddm/clk/304595813;131938128;j_______________________________________________>
> Hl7api-devel mailing list
> Hl7...@li... <mailto:Hl7...@li...>
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel <https://lists.sourceforge.net/lists/listinfo/hl7api-devel>

Re: [HAPI-devel] How to parse NK1 segment in HL7 v2.1

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

I adjusted an earlier message example I had played with to try out the message.getall() that you are using. See below.  It looked to work ok, so I’m not able to offer much more. You may note that I went through a parse step on a message string first, before trying to use getAll.  I presume you had similar code. I am also a big supporter of using printstructure when I am trying things out.  It helps me avoid invalid assumptions about how HAPI has parsed the message.

Ian

Code example:

        String msg = "MSH|^~\\&|SCM|SCM|HL7ADT||20130114001147||ADT^A08|8456356603013|P|2.1\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());
        Structure[] nk1Segments = hapiMessage.getAll("NK1");
        System.out.println("There are " + nk1Segments.length + " NK1 segments present.");

From: Dayu Han [mailto:da...@st...]
Sent: Tuesday, 17 May 2016 7:56 AM
To: HAPI Devel List
Subject: Re: [HAPI-devel] How to parse NK1 segment in HL7 v2.1

Hello

In processing HL7 ADT message v2.1, I use the following code to parse NK1 segment:

Structure[] nk1Segments = message.getAll("NK1”);

However, this returns no element. My question is how to get ALL NK1 segments directly ?

Thanks
Dayu
--
Dayu Han
Software Developer
Strata Health Solutions
Office: +1.403.261.0855 x2102
Website<http://www.stratahealth.com/> | Overview Video<http://youtu.be/5wHGcurxMyY> | Resources<http://www.stratahealth.com/resources/>













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

Re: [HAPI-devel] How to parse NK1 segment in HL7 v2.1

[Dayu H. <da...@st...>]

Hello

In processing HL7 ADT message v2.1, I use the following code to parse NK1 segment:

Structure[] nk1Segments = message.getAll("NK1”);

However, this returns no element. My question is how to get ALL NK1 segments directly ?

Thanks
Dayu
--
Dayu Han
Software Developer
Strata Health Solutions 
Office: +1.403.261.0855 x2102
Website <http://www.stratahealth.com/> | Overview Video <http://youtu.be/5wHGcurxMyY> | Resources <http://www.stratahealth.com/resources/>

[HAPI-devel] Terminology Service HAPI FHIR

[<ISP...@li...>]

Hi, 
I should try to create a terminology service and I wonder if you can create it with HAPI FHIR. The features should be those offered by the terminology service of FHIR (lookup, validation, translation, etc.). Are there any examples or some documentation if you could send me this thing is achievable? In particular is it possible extract code and code system of a value set from a Bundles' entry?

Thanks,
Paul

Re: [HAPI-devel] CreateAMessage example incorrect?

[moparisthebest <ad...@mo...>]

Hello Christian and Jeremy,

Thanks very much, indeed in my IDE (IDEA) it was printing:

PID|||123456||Doe^John

But when ran from a standard shell it printed:

PID|||123456||Doe^Johnstem||||200701011539||ADT^A01^ADT A01||||123

And of course at the hint replacing \r in java or piping it to tr '\r'
'\n' in shell gave me the output I was expecting.

Thanks again, I'm sure I would have never realized that on my own!

Re: [HAPI-devel] CreateAMessage example incorrect?

[Jeremy H. <jer...@ka...>]

Depending on how your console functions, I'd have expected something more
like:

PID|||123456||Doe^Johnstem||||200701011539||ADT^A01^ADT A01||||123

But at any rate, try adding this before the println:

encodedMessage = encodedMessage.replaceAll("\r", "\n");


Jeremy Huiskamp | karoshealth
Software Engineer
7 Father David Bauer Drive, Suite 201
Waterloo, ON, N2L 0A2, Canada
www.karoshealth.com

On 12 April 2016 at 19:45, moparisthebest <ad...@mo...> wrote:

> Hello,
>
> I'm new to HAPI and HL7 in general, and I tried this example exactly:
>
>
> http://hl7api.sourceforge.net/xref/ca/uhn/hl7v2/examples/CreateAMessage.html
>
> With these maven dependencies:
>
>       <dependency>
>         <groupId>ca.uhn.hapi</groupId>
>         <artifactId>hapi-base</artifactId>
>         <version>2.2</version>
>       </dependency>
>       <dependency>
>         <groupId>ca.uhn.hapi</groupId>
>         <artifactId>hapi-structures-v24</artifactId>
>         <version>2.2</version>
>       </dependency>
>
> And though the example says it should print:
>
> MSH|^~\&|TestSendingSystem||||200701011539||ADT^A01^ADT A01||||123
> PID|||123456||Doe^John
>
> What it *actually* prints is only:
>
> PID|||123456||Doe^John
>
> What do I need to do to get it to print the entire message?
>
> I am using java version "1.8.0_74" amd64 on a Linux machine, if that
> matters.
>
> Thanks much!
>
>
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications
> Manager
> Applications Manager provides deep performance insights into multiple
> tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>

Re: [HAPI-devel] CreateAMessage example incorrect?

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

Be aware that in HL7 the segment separator is a "\r" (CR).
So if you print out the encoded message, only the last segment remains 
visible on Linux.
If you do something like 
System.out.println(encodedMessage.replace("\r","\n")) instead, you 
should see the complete message.

cheers
Christian

Am 12.04.2016 um 19:45 schrieb moparisthebest:
> Hello,
>
> I'm new to HAPI and HL7 in general, and I tried this example exactly:
>
> http://hl7api.sourceforge.net/xref/ca/uhn/hl7v2/examples/CreateAMessage.html
>
> With these maven dependencies:
>
>        <dependency>
>          <groupId>ca.uhn.hapi</groupId>
>          <artifactId>hapi-base</artifactId>
>          <version>2.2</version>
>        </dependency>
>        <dependency>
>          <groupId>ca.uhn.hapi</groupId>
>          <artifactId>hapi-structures-v24</artifactId>
>          <version>2.2</version>
>        </dependency>
>
> And though the example says it should print:
>
> MSH|^~\&|TestSendingSystem||||200701011539||ADT^A01^ADT A01||||123
> PID|||123456||Doe^John
>
> What it *actually* prints is only:
>
> PID|||123456||Doe^John
>
> What do I need to do to get it to print the entire message?
>
> I am using java version "1.8.0_74" amd64 on a Linux machine, if that
> matters.
>
> Thanks much!
>
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel