Re: [HAPI-devel] WG: Problem with ORM O01, Terser, ORDER

[Thea S. <the...@ho...>]

Hi Martin!

Thanks a lot! This was the crucial note:

(note: <version> is the hapi version, not the message version. so for e.g. 2.5 messages, you need:

Now is works!

wbr

Thea
________________________________
Von: Martin Fleurke <mar...@po...>
Gesendet: Freitag, 11. September 2020 12:08
An: hl7...@li... <hl7...@li...>
Betreff: Re: [HAPI-devel] WG: Problem with ORM O01, Terser, ORDER

Hi Thea,

I can reproduce the problem for v2.3 messages :) But I found out why: I don't have the v2.3 code!

HAPI has a base jar, and for each message version an additional jar file. You need to include them in your project.
For maven, e.g.:


<dependency>
    <groupId>ca.uhn.hapi</groupId>
    <artifactId>hapi-structures-v23</artifactId>
    <version>2.3</version>
</dependency>

(note: <version> is the hapi version, not the message version. so for e.g. 2.5 messages, you need:

<dependency>
    <groupId>ca.uhn.hapi</groupId>
    <artifactId>hapi-structures-v25</artifactId>
    <version>2.3</version>
</dependency>

)



On 10/09/2020 12:28, Thea Schmidt wrote:
Hi Martin,

thanks for your response. It is definitly no problem with the endings, charset etc. I can read the message, parse it and access other fields via terser.

Tests like the following work:

assertEquals("3247", terser.get("PID-3-1-1"));
assertEquals("jmWo4", terser.get("ORC3-2-1-1"));
assertEquals("jmWo2", terser.get("ORC-2-1-1"));
assertEquals("jmWo4", terser.get("OBR3-2-1-1"));
assertEquals("jmWo2", terser.get("OBR-2-1-1"));

I can show you a snapshot from Eclipse. You can see there how the terser (or the finder) handels the segments.

[cid:par...@po...]
Its not a problem of the V2 Version. With 2.5 oder 2.7 it is the same.

Wbr

Thea

________________________________


Wbr
Martin Fleurke