hl7api-devel — developer list

Re: [HAPI-devel] TestPanel on mac won't open after last update of Java

[Jure G. <jur...@gm...>]

In latest java update (http://www.oracle.com/technetwork/java/javase/7u25-relnotes-1955741.html) are added new JAR Manifest attributes, i.e. permissions and some changes+recommendations regarding web start deployment. App that I'm working on stopped working with update 7_25, but works fine with previous versions. Adding entries into Manifest fixed problems. Maybe is this same case with TestPanel.

Regards,
Jure

On Jun 20, 2013, at 6:07 PM, Paolo Galizzi <pa...@me...> wrote:

> 
> Hi James,
> thanks for response. 
> I downloaded the dmg bundle of TestPanel, the 2.0.1 version.
> After some java updating (actually 1.7 from Oracle) i'll reach a state 
> in which the TP start but when i click on message/server options nothing 
> change until i resize the window drugging the bottom-right corner of the panel.
> So changes appear only after window refresh. I hope this could help you.
> 
> I also find a partial solution to keep working..i downloaded the linux version
> and run it from terminal using the classic "java -jar" and it works.
> 
> PS : hapi and TP save me and my time...so thanks a lot!
> 
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel

Re: [HAPI-devel] TestPanel on mac won't open after last update of Java

[Paolo G. <pa...@me...>]

Hi James,
thanks for response. 
I downloaded the dmg bundle of TestPanel, the 2.0.1 version.
After some java updating (actually 1.7 from Oracle) i'll reach a state 
in which the TP start but when i click on message/server options nothing 
change until i resize the window drugging the bottom-right corner of the panel.
So changes appear only after window refresh. I hope this could help you.

I also find a partial solution to keep working..i downloaded the linux version
and run it from terminal using the classic "java -jar" and it works.

PS : hapi and TP save me and my time...so thanks a lot!

Re: [HAPI-devel] TestPanel on mac won't open after last update of Java

[James A. <ja...@ja...>]

Hi Paolo,

Mac/OSX has been such a painful moving target for the TestPanel! I'm a Mac
user myself and I have to say until we released TP I had no idea how much
more pain Mac app developers went through compared to their Linux/Windows
counterparts. :)

Are you using the WebStart/JNLP version or the downloadable DMG/app bundle?
I just did the same Java update on my machine, so I'll try and reproduce
this later today.

Cheers,
James


On Thu, Jun 20, 2013 at 6:59 AM, Paolo Galizzi <pa...@me...> wrote:

> I use a mac with 10.8.4 and i have done the last update of Java (Java for
> OS X 2013-002), and now i not able to open the Hapi TestPanel. I have read
> that  "This update uninstalls the Apple-provided Java applet plug-in from
> all web browsers" and probably this is the problem, but i do some try
> (re-install, change preferences, re-enable old java version) but i can't
> resolve. Any suggestion? Thanks.
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>
>

[HAPI-devel] TestPanel on mac won't open after last update of Java

[Paolo G. <pa...@me...>]

I use a mac with 10.8.4 and i have done the last update of Java (Java for OS X 2013-002), and now i not able to open the Hapi TestPanel. I have read that  "This update uninstalls the Apple-provided Java applet plug-in from all web browsers" and probably this is the problem, but i do some try (re-install, change preferences, re-enable old java version) but i can't resolve. Any suggestion? Thanks.

Re: [HAPI-devel] Generic class for ADT message

[sagarshah1983 <sag...@ci...>]

Ok. In that case, I think it makes more sense to replicate the code of
ADT_AXX and add support for additional event triggers (as suggested by you
in previous message).
Appreciate your direction.

Regards,
Sagar Shah


James Agnew wrote:
> 
> Hi Sagar,
> 
> Yes, there is definitely nothing wrong with using ADT_A01 to generate
> other
> types of messages.
> 
> The only challenge you may run into is that some ADT message types will
> have structures that ADT_A01 doesn't have. For example, an ADT_A17 has a
> second set of PID and PV1 segments, and these segments (which HAPI refers
> to as PID2 and PV12) don't exist in the ADT_A01 structure. The workaround
> there is to use the addNonStandardSegment method to add them as needed.
> This is definitely fine, and is fairly common.
> 
> Cheers,
> James
> 
> 
> On Wed, Jun 19, 2013 at 9:59 AM, sagarshah1983
> <sag...@ci...>wrote:
> 
>>
>> Hi James,
>> I also had one more question to understand difference between ADT_AXX and
>> ADT_A01.
>>
>> The issues that I am getting is with ADT_AXX. So what if I have to
>> replace
>> this with ADT_A01.
>> Can I used ADT_A01 class to generate ADT A04, A05, A08 and A28 messages
>> as
>> well?
>> I tried generating just MSH and PID segment using ADT_A01 for above
>> listed
>> different triggers and that atleast worked well.
>>
>>
>> Regards,
>> Sagar Shah
>>
>> James Agnew wrote:
>> >
>> > Hi All,
>> >
>> > This does indeed appear to be a bug in the generator for the
>> > superstructures unfortunately. Sagar, the good news is that your code
>> > *should* work, you're doing the right thing. But the bad news is that
>> it
>> > isn't working obviously. :)
>> >
>> > Superstructures are a brand new feature, and they haven't yet been
>> heavily
>> > used. I've got a fix for this issue locally, but it isn't yet released.
>> >
>> > One workaround you could easily implement would be to create your own
>> > local
>> > replacement class for ADT_AXX by copying the source to that class
>> > somewhere
>> > else and fixing the issue. The source for this class is here (NB this
>> is
>> > the HL7 v2.4 version):
>> >
>> http://grepcode.com/file_/repo1.maven.org/maven2/ca.uhn.hapi/hapi-structures-v24/2.1-beta1/ca/uhn/hl7v2/model/v24/message/ADT_AXX.java/?v=source
>> >
>> > If you look at the "init" method, you see a long string of method calls
>> > like this:
>> >
>> >     this.addSuperstructureApplication("MSH", "ADT_A04");
>> >
>> > These are the calls which advise HAPI that MSH may be used for an
>> ADT_A04
>> > message, but the bug is that there isn't a corresponding line for
>> ADT_A01.
>> > If you add that, you'll be allowed to add an MSH segment to an A01
>> > message.
>> > You'll need to do this for every segment and message type combination
>> > though, which I realise will be annoying.
>> >
>> > I'm going to try and get a fix at least checked in within the next week
>> or
>> > two...
>> >
>> > Cheers,
>> > James
>> >
>> >
>> > On Wed, Jun 19, 2013 at 5:35 AM, sagarshah1983
>> > <sag...@ci...>wrote:
>> >
>> >>
>> >> Thanks a ton Christian for this.
>> >> I think I can make use of Terser to make it generic and use ADT_A01 as
>> >> base
>> >> message, as there are some issues with ADT_AXX as reported in previous
>> >> message.
>> >>
>> >>
>> >>
>> >> Christian Ohr-2 wrote:
>> >> >
>> >> > Yes, I can reproduce this problem. It seems that the MSH segment is
>> not
>> >> > allowed e.g. for A01 message by the validator, which is obviously
>> >> > nonsense.
>> >> > Maybe James can enlighten this a bit.... potentially there's a bug
>> in
>> >> the
>> >> > generator.
>> >> >
>> >> > After all, when creating messages I don't see a need to create
>> >> > superstructure messages, as you know which message you create. You
>> >> still
>> >> > have the problem that there is no common super-class or interface to
>> >> ADT
>> >> > messages, but their are ways to circumvent this, e.g. using the
>> Terser
>> >> > class:
>> >> >
>> >> > Message m = new ADT_A01();
>> >> > m.initQuickstart("ADT", "A01", "P");
>> >> > // everything below works on a generic level
>> >> > Terser t = new Terser(m);
>> >> > t.set("/MSH-9-2", "A04");
>> >> > t.set("/PID-3-1", "myIdentifier");
>> >> > ...
>> >> >
>> >> > hope this helps
>> >> > Christian
>> >> >
>> >> >
>> >> > 2013/6/19 sagarshah1983 <sag...@ci...>
>> >> >
>> >> >>
>> >> >> Thanks Christian for sharing this link.
>> >> >> I was trying to use ADT_AXX structure only, but found few issues
>> with
>> >> >> generating HL7 message with ADT_AXX and did not find a way to solve
>> >> that
>> >> >> out. So thought of checking for any other generic structure for ADT
>> >> >> messages.
>> >> >> Anyways, here's the issue I am facing.
>> >> >> Code Snippet.
>> >> >>
>> >> >> ADT_AXX adt = new ADT_AXX();
>> >> >> MSH msh = adt.getMSH();
>> >> >> ....
>> >> >> msh.getMsh9_MessageType().getMsg1_MessageCode().setValue("ADT");
>> >> >> msh.getMsh9_MessageType().getMsg2_TriggerEvent().setValue("A28");
>> >> >>
>> >>
>> msh.getMsh9_MessageType().getMsg3_MessageStructure().setValue("ADT_A28");
>> >> >>
>> >> >> Above works perfectly fine, but the moment I change last two lines
>> to
>> >> >> reflect A01, it fails.
>> >> >>
>> >> >> msh.getMsh9_MessageType().getMsg2_TriggerEvent().setValue("A01");
>> >> >>
>> >>
>> msh.getMsh9_MessageType().getMsg3_MessageStructure().setValue("ADT_A01");
>> >> >>
>> >> >> Error details:
>> >> >> Caused by: ca.uhn.hl7v2.validation.ValidationException: Message
>> >> >> (superstructure ADT_AXX) of type ADT_A01 must not have content in
>> MSH
>> >> >>
>> >> >> Any advice is appreciated.
>> >> >>
>> >> >> Regards,
>> >> >> Sagar Shah
>> >> >>
>> >> >>
>> >> >>
>> >> >> Christian Ohr-2 wrote:
>> >> >> >
>> >> >> > If you are using HAPI 2.1, you should have a look at this:
>> >> >> >
>> >> >>
>> >>
>> http://hl7api.sourceforge.net/xref/ca/uhn/hl7v2/examples/ExampleSuperStructures.html
>> >> >> > .
>> >> >> >
>> >> >> > cheers
>> >> >> > Christian
>> >> >> >
>> >> >> >
>> >> >> > 2013/6/18 sagarshah1983 <sag...@ci...>
>> >> >> >
>> >> >> >>
>> >> >> >> That would be really great for me.
>> >> >> >> Appreciate your reply and time for the same.
>> >> >> >>
>> >> >> >> Regards,
>> >> >> >> Sagar Shah
>> >> >> >>
>> >> >> >> LDH-2 wrote:
>> >> >> >> >
>> >> >> >> > I am not aware of one in 1.x... I don't know 2.x well enough
>> yet.
>> >> I
>> >> >> am
>> >> >> >> on
>> >> >> >> > the road, but I can send out later the type of code I have
>> used
>> >> to
>> >> >> be
>> >> >> >> adt
>> >> >> >> > generic.
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > ___________________________________________
>> >> >> >> > Laurent Hasson (via my BlackBerry)
>> >> >> >> > email: ld...@36...
>> >> >> >> > cell: 646-283-2186
>> >> >> >> > twitter: @ldhasson
>> >> >> >> >
>> >> >> >> > -----Original Message-----
>> >> >> >> > From: sagarshah1983 <sag...@ci...>
>> >> >> >> > Date: Tue, 18 Jun 2013 08:53:15
>> >> >> >> > To: <hl7...@li...>
>> >> >> >> > Subject: [HAPI-devel]  Generic class for ADT message
>> >> >> >> >
>> >> >> >> >
>> >> >> >>
>> >> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> >> >> > This SF.net email is sponsored by Windows:
>> >> >> >> >
>> >> >> >> > Build for Windows Store.
>> >> >> >> >
>> >> >> >> > http://p.sf.net/sfu/windows-dev2dev
>> >> >> >> >
>> >> >> >> >
>> >> >> >>
>> >> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> >> >> > This SF.net email is sponsored by Windows:
>> >> >> >> >
>> >> >> >> > Build for Windows Store.
>> >> >> >> >
>> >> >> >> > http://p.sf.net/sfu/windows-dev2dev
>> >> >> >> > _______________________________________________
>> >> >> >> > Hl7api-devel mailing list
>> >> >> >> > Hl7...@li...
>> >> >> >> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >> >> >> >
>> >> >> >> >
>> >> >> >>
>> >> >> >> --
>> >> >> >> View this message in context:
>> >> >> >>
>> >> >>
>> >>
>> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35639472.html
>> >> >> >> Sent from the hl7api-devel mailing list archive at Nabble.com.
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> >> >> This SF.net email is sponsored by Windows:
>> >> >> >>
>> >> >> >> Build for Windows Store.
>> >> >> >>
>> >> >> >> http://p.sf.net/sfu/windows-dev2dev
>> >> >> >> _______________________________________________
>> >> >> >> Hl7api-devel mailing list
>> >> >> >> Hl7...@li...
>> >> >> >> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> >> > This SF.net email is sponsored by Windows:
>> >> >> >
>> >> >> > Build for Windows Store.
>> >> >> >
>> >> >> > http://p.sf.net/sfu/windows-dev2dev
>> >> >> > _______________________________________________
>> >> >> > Hl7api-devel mailing list
>> >> >> > Hl7...@li...
>> >> >> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >> >> >
>> >> >> >
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35642054.html
>> >> >> Sent from the hl7api-devel mailing list archive at Nabble.com.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> >> This SF.net email is sponsored by Windows:
>> >> >>
>> >> >> Build for Windows Store.
>> >> >>
>> >> >> http://p.sf.net/sfu/windows-dev2dev
>> >> >> _______________________________________________
>> >> >> Hl7api-devel mailing list
>> >> >> Hl7...@li...
>> >> >> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >> >>
>> >> >
>> >> >
>> >>
>> ------------------------------------------------------------------------------
>> >> > This SF.net email is sponsored by Windows:
>> >> >
>> >> > Build for Windows Store.
>> >> >
>> >> > http://p.sf.net/sfu/windows-dev2dev
>> >> > _______________________________________________
>> >> > Hl7api-devel mailing list
>> >> > Hl7...@li...
>> >> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35642561.html
>> >> Sent from the hl7api-devel mailing list archive at Nabble.com.
>> >>
>> >>
>> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> This SF.net email is sponsored by Windows:
>> >>
>> >> Build for Windows Store.
>> >>
>> >> http://p.sf.net/sfu/windows-dev2dev
>> >> _______________________________________________
>> >> Hl7api-devel mailing list
>> >> Hl7...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >>
>> >
>> >
>> ------------------------------------------------------------------------------
>> > This SF.net email is sponsored by Windows:
>> >
>> > Build for Windows Store.
>> >
>> > http://p.sf.net/sfu/windows-dev2dev
>> > _______________________________________________
>> > Hl7api-devel mailing list
>> > Hl7...@li...
>> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >
>> >
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35643630.html
>> Sent from the hl7api-devel mailing list archive at Nabble.com.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> Hl7api-devel mailing list
>> Hl7...@li...
>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> 
> 

-- 
View this message in context: http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35644330.html
Sent from the hl7api-devel mailing list archive at Nabble.com.

Re: [HAPI-devel] Generic class for ADT message

[James A. <ja...@ja...>]

Hi Sagar,

Yes, there is definitely nothing wrong with using ADT_A01 to generate other
types of messages.

The only challenge you may run into is that some ADT message types will
have structures that ADT_A01 doesn't have. For example, an ADT_A17 has a
second set of PID and PV1 segments, and these segments (which HAPI refers
to as PID2 and PV12) don't exist in the ADT_A01 structure. The workaround
there is to use the addNonStandardSegment method to add them as needed.
This is definitely fine, and is fairly common.

Cheers,
James


On Wed, Jun 19, 2013 at 9:59 AM, sagarshah1983 <sag...@ci...>wrote:

>
> Hi James,
> I also had one more question to understand difference between ADT_AXX and
> ADT_A01.
>
> The issues that I am getting is with ADT_AXX. So what if I have to replace
> this with ADT_A01.
> Can I used ADT_A01 class to generate ADT A04, A05, A08 and A28 messages as
> well?
> I tried generating just MSH and PID segment using ADT_A01 for above listed
> different triggers and that atleast worked well.
>
>
> Regards,
> Sagar Shah
>
> James Agnew wrote:
> >
> > Hi All,
> >
> > This does indeed appear to be a bug in the generator for the
> > superstructures unfortunately. Sagar, the good news is that your code
> > *should* work, you're doing the right thing. But the bad news is that it
> > isn't working obviously. :)
> >
> > Superstructures are a brand new feature, and they haven't yet been
> heavily
> > used. I've got a fix for this issue locally, but it isn't yet released.
> >
> > One workaround you could easily implement would be to create your own
> > local
> > replacement class for ADT_AXX by copying the source to that class
> > somewhere
> > else and fixing the issue. The source for this class is here (NB this is
> > the HL7 v2.4 version):
> >
> http://grepcode.com/file_/repo1.maven.org/maven2/ca.uhn.hapi/hapi-structures-v24/2.1-beta1/ca/uhn/hl7v2/model/v24/message/ADT_AXX.java/?v=source
> >
> > If you look at the "init" method, you see a long string of method calls
> > like this:
> >
> >     this.addSuperstructureApplication("MSH", "ADT_A04");
> >
> > These are the calls which advise HAPI that MSH may be used for an ADT_A04
> > message, but the bug is that there isn't a corresponding line for
> ADT_A01.
> > If you add that, you'll be allowed to add an MSH segment to an A01
> > message.
> > You'll need to do this for every segment and message type combination
> > though, which I realise will be annoying.
> >
> > I'm going to try and get a fix at least checked in within the next week
> or
> > two...
> >
> > Cheers,
> > James
> >
> >
> > On Wed, Jun 19, 2013 at 5:35 AM, sagarshah1983
> > <sag...@ci...>wrote:
> >
> >>
> >> Thanks a ton Christian for this.
> >> I think I can make use of Terser to make it generic and use ADT_A01 as
> >> base
> >> message, as there are some issues with ADT_AXX as reported in previous
> >> message.
> >>
> >>
> >>
> >> Christian Ohr-2 wrote:
> >> >
> >> > Yes, I can reproduce this problem. It seems that the MSH segment is
> not
> >> > allowed e.g. for A01 message by the validator, which is obviously
> >> > nonsense.
> >> > Maybe James can enlighten this a bit.... potentially there's a bug in
> >> the
> >> > generator.
> >> >
> >> > After all, when creating messages I don't see a need to create
> >> > superstructure messages, as you know which message you create. You
> >> still
> >> > have the problem that there is no common super-class or interface to
> >> ADT
> >> > messages, but their are ways to circumvent this, e.g. using the Terser
> >> > class:
> >> >
> >> > Message m = new ADT_A01();
> >> > m.initQuickstart("ADT", "A01", "P");
> >> > // everything below works on a generic level
> >> > Terser t = new Terser(m);
> >> > t.set("/MSH-9-2", "A04");
> >> > t.set("/PID-3-1", "myIdentifier");
> >> > ...
> >> >
> >> > hope this helps
> >> > Christian
> >> >
> >> >
> >> > 2013/6/19 sagarshah1983 <sag...@ci...>
> >> >
> >> >>
> >> >> Thanks Christian for sharing this link.
> >> >> I was trying to use ADT_AXX structure only, but found few issues with
> >> >> generating HL7 message with ADT_AXX and did not find a way to solve
> >> that
> >> >> out. So thought of checking for any other generic structure for ADT
> >> >> messages.
> >> >> Anyways, here's the issue I am facing.
> >> >> Code Snippet.
> >> >>
> >> >> ADT_AXX adt = new ADT_AXX();
> >> >> MSH msh = adt.getMSH();
> >> >> ....
> >> >> msh.getMsh9_MessageType().getMsg1_MessageCode().setValue("ADT");
> >> >> msh.getMsh9_MessageType().getMsg2_TriggerEvent().setValue("A28");
> >> >>
> >>
> msh.getMsh9_MessageType().getMsg3_MessageStructure().setValue("ADT_A28");
> >> >>
> >> >> Above works perfectly fine, but the moment I change last two lines to
> >> >> reflect A01, it fails.
> >> >>
> >> >> msh.getMsh9_MessageType().getMsg2_TriggerEvent().setValue("A01");
> >> >>
> >>
> msh.getMsh9_MessageType().getMsg3_MessageStructure().setValue("ADT_A01");
> >> >>
> >> >> Error details:
> >> >> Caused by: ca.uhn.hl7v2.validation.ValidationException: Message
> >> >> (superstructure ADT_AXX) of type ADT_A01 must not have content in MSH
> >> >>
> >> >> Any advice is appreciated.
> >> >>
> >> >> Regards,
> >> >> Sagar Shah
> >> >>
> >> >>
> >> >>
> >> >> Christian Ohr-2 wrote:
> >> >> >
> >> >> > If you are using HAPI 2.1, you should have a look at this:
> >> >> >
> >> >>
> >>
> http://hl7api.sourceforge.net/xref/ca/uhn/hl7v2/examples/ExampleSuperStructures.html
> >> >> > .
> >> >> >
> >> >> > cheers
> >> >> > Christian
> >> >> >
> >> >> >
> >> >> > 2013/6/18 sagarshah1983 <sag...@ci...>
> >> >> >
> >> >> >>
> >> >> >> That would be really great for me.
> >> >> >> Appreciate your reply and time for the same.
> >> >> >>
> >> >> >> Regards,
> >> >> >> Sagar Shah
> >> >> >>
> >> >> >> LDH-2 wrote:
> >> >> >> >
> >> >> >> > I am not aware of one in 1.x... I don't know 2.x well enough
> yet.
> >> I
> >> >> am
> >> >> >> on
> >> >> >> > the road, but I can send out later the type of code I have used
> >> to
> >> >> be
> >> >> >> adt
> >> >> >> > generic.
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > ___________________________________________
> >> >> >> > Laurent Hasson (via my BlackBerry)
> >> >> >> > email: ld...@36...
> >> >> >> > cell: 646-283-2186
> >> >> >> > twitter: @ldhasson
> >> >> >> >
> >> >> >> > -----Original Message-----
> >> >> >> > From: sagarshah1983 <sag...@ci...>
> >> >> >> > Date: Tue, 18 Jun 2013 08:53:15
> >> >> >> > To: <hl7...@li...>
> >> >> >> > Subject: [HAPI-devel]  Generic class for ADT message
> >> >> >> >
> >> >> >> >
> >> >> >>
> >> >>
> >>
> ------------------------------------------------------------------------------
> >> >> >> > This SF.net email is sponsored by Windows:
> >> >> >> >
> >> >> >> > Build for Windows Store.
> >> >> >> >
> >> >> >> > http://p.sf.net/sfu/windows-dev2dev
> >> >> >> >
> >> >> >> >
> >> >> >>
> >> >>
> >>
> ------------------------------------------------------------------------------
> >> >> >> > This SF.net email is sponsored by Windows:
> >> >> >> >
> >> >> >> > Build for Windows Store.
> >> >> >> >
> >> >> >> > http://p.sf.net/sfu/windows-dev2dev
> >> >> >> > _______________________________________________
> >> >> >> > Hl7api-devel mailing list
> >> >> >> > Hl7...@li...
> >> >> >> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >> >> >> >
> >> >> >> >
> >> >> >>
> >> >> >> --
> >> >> >> View this message in context:
> >> >> >>
> >> >>
> >>
> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35639472.html
> >> >> >> Sent from the hl7api-devel mailing list archive at Nabble.com.
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >>
> ------------------------------------------------------------------------------
> >> >> >> This SF.net email is sponsored by Windows:
> >> >> >>
> >> >> >> Build for Windows Store.
> >> >> >>
> >> >> >> http://p.sf.net/sfu/windows-dev2dev
> >> >> >> _______________________________________________
> >> >> >> Hl7api-devel mailing list
> >> >> >> Hl7...@li...
> >> >> >> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >> >> >>
> >> >> >
> >> >> >
> >> >>
> >>
> ------------------------------------------------------------------------------
> >> >> > This SF.net email is sponsored by Windows:
> >> >> >
> >> >> > Build for Windows Store.
> >> >> >
> >> >> > http://p.sf.net/sfu/windows-dev2dev
> >> >> > _______________________________________________
> >> >> > Hl7api-devel mailing list
> >> >> > Hl7...@li...
> >> >> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >> >> >
> >> >> >
> >> >> --
> >> >> View this message in context:
> >> >>
> >>
> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35642054.html
> >> >> Sent from the hl7api-devel mailing list archive at Nabble.com.
> >> >>
> >> >>
> >> >>
> >> >>
> >>
> ------------------------------------------------------------------------------
> >> >> This SF.net email is sponsored by Windows:
> >> >>
> >> >> Build for Windows Store.
> >> >>
> >> >> http://p.sf.net/sfu/windows-dev2dev
> >> >> _______________________________________________
> >> >> Hl7api-devel mailing list
> >> >> Hl7...@li...
> >> >> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >> >>
> >> >
> >> >
> >>
> ------------------------------------------------------------------------------
> >> > This SF.net email is sponsored by Windows:
> >> >
> >> > Build for Windows Store.
> >> >
> >> > http://p.sf.net/sfu/windows-dev2dev
> >> > _______________________________________________
> >> > Hl7api-devel mailing list
> >> > Hl7...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >>
> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35642561.html
> >> Sent from the hl7api-devel mailing list archive at Nabble.com.
> >>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> This SF.net email is sponsored by Windows:
> >>
> >> Build for Windows Store.
> >>
> >> http://p.sf.net/sfu/windows-dev2dev
> >> _______________________________________________
> >> Hl7api-devel mailing list
> >> Hl7...@li...
> >> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >>
> >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Windows:
> >
> > Build for Windows Store.
> >
> > http://p.sf.net/sfu/windows-dev2dev
> > _______________________________________________
> > Hl7api-devel mailing list
> > Hl7...@li...
> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35643630.html
> Sent from the hl7api-devel mailing list archive at Nabble.com.
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>

Re: [HAPI-devel] Generic class for ADT message

[sagarshah1983 <sag...@ci...>]

Hi James, 
I also had one more question to understand difference between ADT_AXX and
ADT_A01.

The issues that I am getting is with ADT_AXX. So what if I have to replace
this with ADT_A01.
Can I used ADT_A01 class to generate ADT A04, A05, A08 and A28 messages as
well?
I tried generating just MSH and PID segment using ADT_A01 for above listed
different triggers and that atleast worked well.


Regards,
Sagar Shah

James Agnew wrote:
> 
> Hi All,
> 
> This does indeed appear to be a bug in the generator for the
> superstructures unfortunately. Sagar, the good news is that your code
> *should* work, you're doing the right thing. But the bad news is that it
> isn't working obviously. :)
> 
> Superstructures are a brand new feature, and they haven't yet been heavily
> used. I've got a fix for this issue locally, but it isn't yet released.
> 
> One workaround you could easily implement would be to create your own
> local
> replacement class for ADT_AXX by copying the source to that class
> somewhere
> else and fixing the issue. The source for this class is here (NB this is
> the HL7 v2.4 version):
> http://grepcode.com/file_/repo1.maven.org/maven2/ca.uhn.hapi/hapi-structures-v24/2.1-beta1/ca/uhn/hl7v2/model/v24/message/ADT_AXX.java/?v=source
> 
> If you look at the "init" method, you see a long string of method calls
> like this:
> 
>     this.addSuperstructureApplication("MSH", "ADT_A04");
> 
> These are the calls which advise HAPI that MSH may be used for an ADT_A04
> message, but the bug is that there isn't a corresponding line for ADT_A01.
> If you add that, you'll be allowed to add an MSH segment to an A01
> message.
> You'll need to do this for every segment and message type combination
> though, which I realise will be annoying.
> 
> I'm going to try and get a fix at least checked in within the next week or
> two...
> 
> Cheers,
> James
> 
> 
> On Wed, Jun 19, 2013 at 5:35 AM, sagarshah1983
> <sag...@ci...>wrote:
> 
>>
>> Thanks a ton Christian for this.
>> I think I can make use of Terser to make it generic and use ADT_A01 as
>> base
>> message, as there are some issues with ADT_AXX as reported in previous
>> message.
>>
>>
>>
>> Christian Ohr-2 wrote:
>> >
>> > Yes, I can reproduce this problem. It seems that the MSH segment is not
>> > allowed e.g. for A01 message by the validator, which is obviously
>> > nonsense.
>> > Maybe James can enlighten this a bit.... potentially there's a bug in
>> the
>> > generator.
>> >
>> > After all, when creating messages I don't see a need to create
>> > superstructure messages, as you know which message you create. You
>> still
>> > have the problem that there is no common super-class or interface to
>> ADT
>> > messages, but their are ways to circumvent this, e.g. using the Terser
>> > class:
>> >
>> > Message m = new ADT_A01();
>> > m.initQuickstart("ADT", "A01", "P");
>> > // everything below works on a generic level
>> > Terser t = new Terser(m);
>> > t.set("/MSH-9-2", "A04");
>> > t.set("/PID-3-1", "myIdentifier");
>> > ...
>> >
>> > hope this helps
>> > Christian
>> >
>> >
>> > 2013/6/19 sagarshah1983 <sag...@ci...>
>> >
>> >>
>> >> Thanks Christian for sharing this link.
>> >> I was trying to use ADT_AXX structure only, but found few issues with
>> >> generating HL7 message with ADT_AXX and did not find a way to solve
>> that
>> >> out. So thought of checking for any other generic structure for ADT
>> >> messages.
>> >> Anyways, here's the issue I am facing.
>> >> Code Snippet.
>> >>
>> >> ADT_AXX adt = new ADT_AXX();
>> >> MSH msh = adt.getMSH();
>> >> ....
>> >> msh.getMsh9_MessageType().getMsg1_MessageCode().setValue("ADT");
>> >> msh.getMsh9_MessageType().getMsg2_TriggerEvent().setValue("A28");
>> >>
>> msh.getMsh9_MessageType().getMsg3_MessageStructure().setValue("ADT_A28");
>> >>
>> >> Above works perfectly fine, but the moment I change last two lines to
>> >> reflect A01, it fails.
>> >>
>> >> msh.getMsh9_MessageType().getMsg2_TriggerEvent().setValue("A01");
>> >>
>> msh.getMsh9_MessageType().getMsg3_MessageStructure().setValue("ADT_A01");
>> >>
>> >> Error details:
>> >> Caused by: ca.uhn.hl7v2.validation.ValidationException: Message
>> >> (superstructure ADT_AXX) of type ADT_A01 must not have content in MSH
>> >>
>> >> Any advice is appreciated.
>> >>
>> >> Regards,
>> >> Sagar Shah
>> >>
>> >>
>> >>
>> >> Christian Ohr-2 wrote:
>> >> >
>> >> > If you are using HAPI 2.1, you should have a look at this:
>> >> >
>> >>
>> http://hl7api.sourceforge.net/xref/ca/uhn/hl7v2/examples/ExampleSuperStructures.html
>> >> > .
>> >> >
>> >> > cheers
>> >> > Christian
>> >> >
>> >> >
>> >> > 2013/6/18 sagarshah1983 <sag...@ci...>
>> >> >
>> >> >>
>> >> >> That would be really great for me.
>> >> >> Appreciate your reply and time for the same.
>> >> >>
>> >> >> Regards,
>> >> >> Sagar Shah
>> >> >>
>> >> >> LDH-2 wrote:
>> >> >> >
>> >> >> > I am not aware of one in 1.x... I don't know 2.x well enough yet.
>> I
>> >> am
>> >> >> on
>> >> >> > the road, but I can send out later the type of code I have used
>> to
>> >> be
>> >> >> adt
>> >> >> > generic.
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > ___________________________________________
>> >> >> > Laurent Hasson (via my BlackBerry)
>> >> >> > email: ld...@36...
>> >> >> > cell: 646-283-2186
>> >> >> > twitter: @ldhasson
>> >> >> >
>> >> >> > -----Original Message-----
>> >> >> > From: sagarshah1983 <sag...@ci...>
>> >> >> > Date: Tue, 18 Jun 2013 08:53:15
>> >> >> > To: <hl7...@li...>
>> >> >> > Subject: [HAPI-devel]  Generic class for ADT message
>> >> >> >
>> >> >> >
>> >> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> >> > This SF.net email is sponsored by Windows:
>> >> >> >
>> >> >> > Build for Windows Store.
>> >> >> >
>> >> >> > http://p.sf.net/sfu/windows-dev2dev
>> >> >> >
>> >> >> >
>> >> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> >> > This SF.net email is sponsored by Windows:
>> >> >> >
>> >> >> > Build for Windows Store.
>> >> >> >
>> >> >> > http://p.sf.net/sfu/windows-dev2dev
>> >> >> > _______________________________________________
>> >> >> > Hl7api-devel mailing list
>> >> >> > Hl7...@li...
>> >> >> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >> >> >
>> >> >> >
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35639472.html
>> >> >> Sent from the hl7api-devel mailing list archive at Nabble.com.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> >> This SF.net email is sponsored by Windows:
>> >> >>
>> >> >> Build for Windows Store.
>> >> >>
>> >> >> http://p.sf.net/sfu/windows-dev2dev
>> >> >> _______________________________________________
>> >> >> Hl7api-devel mailing list
>> >> >> Hl7...@li...
>> >> >> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >> >>
>> >> >
>> >> >
>> >>
>> ------------------------------------------------------------------------------
>> >> > This SF.net email is sponsored by Windows:
>> >> >
>> >> > Build for Windows Store.
>> >> >
>> >> > http://p.sf.net/sfu/windows-dev2dev
>> >> > _______________________________________________
>> >> > Hl7api-devel mailing list
>> >> > Hl7...@li...
>> >> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >> >
>> >> >
>> >> --
>> >> View this message in context:
>> >>
>> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35642054.html
>> >> Sent from the hl7api-devel mailing list archive at Nabble.com.
>> >>
>> >>
>> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> This SF.net email is sponsored by Windows:
>> >>
>> >> Build for Windows Store.
>> >>
>> >> http://p.sf.net/sfu/windows-dev2dev
>> >> _______________________________________________
>> >> Hl7api-devel mailing list
>> >> Hl7...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >>
>> >
>> >
>> ------------------------------------------------------------------------------
>> > This SF.net email is sponsored by Windows:
>> >
>> > Build for Windows Store.
>> >
>> > http://p.sf.net/sfu/windows-dev2dev
>> > _______________________________________________
>> > Hl7api-devel mailing list
>> > Hl7...@li...
>> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >
>> >
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35642561.html
>> Sent from the hl7api-devel mailing list archive at Nabble.com.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> Hl7api-devel mailing list
>> Hl7...@li...
>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> 
> 

-- 
View this message in context: http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35643630.html
Sent from the hl7api-devel mailing list archive at Nabble.com.

Re: [HAPI-devel] Generic class for ADT message

[sagarshah1983 <sag...@ci...>]

Thanks a ton James for clarifications. I will look at ADT_AXX and create
another structure out of the same at my end and follow your instructions as
a work around.
Appreciate your suggestions.

Regards,
Sagar Shah

James Agnew wrote:
> 
> Hi All,
> 
> This does indeed appear to be a bug in the generator for the
> superstructures unfortunately. Sagar, the good news is that your code
> *should* work, you're doing the right thing. But the bad news is that it
> isn't working obviously. :)
> 
> Superstructures are a brand new feature, and they haven't yet been heavily
> used. I've got a fix for this issue locally, but it isn't yet released.
> 
> One workaround you could easily implement would be to create your own
> local
> replacement class for ADT_AXX by copying the source to that class
> somewhere
> else and fixing the issue. The source for this class is here (NB this is
> the HL7 v2.4 version):
> http://grepcode.com/file_/repo1.maven.org/maven2/ca.uhn.hapi/hapi-structures-v24/2.1-beta1/ca/uhn/hl7v2/model/v24/message/ADT_AXX.java/?v=source
> 
> If you look at the "init" method, you see a long string of method calls
> like this:
> 
>     this.addSuperstructureApplication("MSH", "ADT_A04");
> 
> These are the calls which advise HAPI that MSH may be used for an ADT_A04
> message, but the bug is that there isn't a corresponding line for ADT_A01.
> If you add that, you'll be allowed to add an MSH segment to an A01
> message.
> You'll need to do this for every segment and message type combination
> though, which I realise will be annoying.
> 
> I'm going to try and get a fix at least checked in within the next week or
> two...
> 
> Cheers,
> James
> 
> 
> On Wed, Jun 19, 2013 at 5:35 AM, sagarshah1983
> <sag...@ci...>wrote:
> 
>>
>> Thanks a ton Christian for this.
>> I think I can make use of Terser to make it generic and use ADT_A01 as
>> base
>> message, as there are some issues with ADT_AXX as reported in previous
>> message.
>>
>>
>>
>> Christian Ohr-2 wrote:
>> >
>> > Yes, I can reproduce this problem. It seems that the MSH segment is not
>> > allowed e.g. for A01 message by the validator, which is obviously
>> > nonsense.
>> > Maybe James can enlighten this a bit.... potentially there's a bug in
>> the
>> > generator.
>> >
>> > After all, when creating messages I don't see a need to create
>> > superstructure messages, as you know which message you create. You
>> still
>> > have the problem that there is no common super-class or interface to
>> ADT
>> > messages, but their are ways to circumvent this, e.g. using the Terser
>> > class:
>> >
>> > Message m = new ADT_A01();
>> > m.initQuickstart("ADT", "A01", "P");
>> > // everything below works on a generic level
>> > Terser t = new Terser(m);
>> > t.set("/MSH-9-2", "A04");
>> > t.set("/PID-3-1", "myIdentifier");
>> > ...
>> >
>> > hope this helps
>> > Christian
>> >
>> >
>> > 2013/6/19 sagarshah1983 <sag...@ci...>
>> >
>> >>
>> >> Thanks Christian for sharing this link.
>> >> I was trying to use ADT_AXX structure only, but found few issues with
>> >> generating HL7 message with ADT_AXX and did not find a way to solve
>> that
>> >> out. So thought of checking for any other generic structure for ADT
>> >> messages.
>> >> Anyways, here's the issue I am facing.
>> >> Code Snippet.
>> >>
>> >> ADT_AXX adt = new ADT_AXX();
>> >> MSH msh = adt.getMSH();
>> >> ....
>> >> msh.getMsh9_MessageType().getMsg1_MessageCode().setValue("ADT");
>> >> msh.getMsh9_MessageType().getMsg2_TriggerEvent().setValue("A28");
>> >>
>> msh.getMsh9_MessageType().getMsg3_MessageStructure().setValue("ADT_A28");
>> >>
>> >> Above works perfectly fine, but the moment I change last two lines to
>> >> reflect A01, it fails.
>> >>
>> >> msh.getMsh9_MessageType().getMsg2_TriggerEvent().setValue("A01");
>> >>
>> msh.getMsh9_MessageType().getMsg3_MessageStructure().setValue("ADT_A01");
>> >>
>> >> Error details:
>> >> Caused by: ca.uhn.hl7v2.validation.ValidationException: Message
>> >> (superstructure ADT_AXX) of type ADT_A01 must not have content in MSH
>> >>
>> >> Any advice is appreciated.
>> >>
>> >> Regards,
>> >> Sagar Shah
>> >>
>> >>
>> >>
>> >> Christian Ohr-2 wrote:
>> >> >
>> >> > If you are using HAPI 2.1, you should have a look at this:
>> >> >
>> >>
>> http://hl7api.sourceforge.net/xref/ca/uhn/hl7v2/examples/ExampleSuperStructures.html
>> >> > .
>> >> >
>> >> > cheers
>> >> > Christian
>> >> >
>> >> >
>> >> > 2013/6/18 sagarshah1983 <sag...@ci...>
>> >> >
>> >> >>
>> >> >> That would be really great for me.
>> >> >> Appreciate your reply and time for the same.
>> >> >>
>> >> >> Regards,
>> >> >> Sagar Shah
>> >> >>
>> >> >> LDH-2 wrote:
>> >> >> >
>> >> >> > I am not aware of one in 1.x... I don't know 2.x well enough yet.
>> I
>> >> am
>> >> >> on
>> >> >> > the road, but I can send out later the type of code I have used
>> to
>> >> be
>> >> >> adt
>> >> >> > generic.
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > ___________________________________________
>> >> >> > Laurent Hasson (via my BlackBerry)
>> >> >> > email: ld...@36...
>> >> >> > cell: 646-283-2186
>> >> >> > twitter: @ldhasson
>> >> >> >
>> >> >> > -----Original Message-----
>> >> >> > From: sagarshah1983 <sag...@ci...>
>> >> >> > Date: Tue, 18 Jun 2013 08:53:15
>> >> >> > To: <hl7...@li...>
>> >> >> > Subject: [HAPI-devel]  Generic class for ADT message
>> >> >> >
>> >> >> >
>> >> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> >> > This SF.net email is sponsored by Windows:
>> >> >> >
>> >> >> > Build for Windows Store.
>> >> >> >
>> >> >> > http://p.sf.net/sfu/windows-dev2dev
>> >> >> >
>> >> >> >
>> >> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> >> > This SF.net email is sponsored by Windows:
>> >> >> >
>> >> >> > Build for Windows Store.
>> >> >> >
>> >> >> > http://p.sf.net/sfu/windows-dev2dev
>> >> >> > _______________________________________________
>> >> >> > Hl7api-devel mailing list
>> >> >> > Hl7...@li...
>> >> >> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >> >> >
>> >> >> >
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35639472.html
>> >> >> Sent from the hl7api-devel mailing list archive at Nabble.com.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> >> This SF.net email is sponsored by Windows:
>> >> >>
>> >> >> Build for Windows Store.
>> >> >>
>> >> >> http://p.sf.net/sfu/windows-dev2dev
>> >> >> _______________________________________________
>> >> >> Hl7api-devel mailing list
>> >> >> Hl7...@li...
>> >> >> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >> >>
>> >> >
>> >> >
>> >>
>> ------------------------------------------------------------------------------
>> >> > This SF.net email is sponsored by Windows:
>> >> >
>> >> > Build for Windows Store.
>> >> >
>> >> > http://p.sf.net/sfu/windows-dev2dev
>> >> > _______________________________________________
>> >> > Hl7api-devel mailing list
>> >> > Hl7...@li...
>> >> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >> >
>> >> >
>> >> --
>> >> View this message in context:
>> >>
>> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35642054.html
>> >> Sent from the hl7api-devel mailing list archive at Nabble.com.
>> >>
>> >>
>> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> This SF.net email is sponsored by Windows:
>> >>
>> >> Build for Windows Store.
>> >>
>> >> http://p.sf.net/sfu/windows-dev2dev
>> >> _______________________________________________
>> >> Hl7api-devel mailing list
>> >> Hl7...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >>
>> >
>> >
>> ------------------------------------------------------------------------------
>> > This SF.net email is sponsored by Windows:
>> >
>> > Build for Windows Store.
>> >
>> > http://p.sf.net/sfu/windows-dev2dev
>> > _______________________________________________
>> > Hl7api-devel mailing list
>> > Hl7...@li...
>> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >
>> >
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35642561.html
>> Sent from the hl7api-devel mailing list archive at Nabble.com.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> Hl7api-devel mailing list
>> Hl7...@li...
>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> 
> 

-- 
View this message in context: http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35643545.html
Sent from the hl7api-devel mailing list archive at Nabble.com.

Re: [HAPI-devel] Generic class for ADT message

[James A. <ja...@ja...>]

Hi All,

This does indeed appear to be a bug in the generator for the
superstructures unfortunately. Sagar, the good news is that your code
*should* work, you're doing the right thing. But the bad news is that it
isn't working obviously. :)

Superstructures are a brand new feature, and they haven't yet been heavily
used. I've got a fix for this issue locally, but it isn't yet released.

One workaround you could easily implement would be to create your own local
replacement class for ADT_AXX by copying the source to that class somewhere
else and fixing the issue. The source for this class is here (NB this is
the HL7 v2.4 version):
http://grepcode.com/file_/repo1.maven.org/maven2/ca.uhn.hapi/hapi-structures-v24/2.1-beta1/ca/uhn/hl7v2/model/v24/message/ADT_AXX.java/?v=source

If you look at the "init" method, you see a long string of method calls
like this:

    this.addSuperstructureApplication("MSH", "ADT_A04");

These are the calls which advise HAPI that MSH may be used for an ADT_A04
message, but the bug is that there isn't a corresponding line for ADT_A01.
If you add that, you'll be allowed to add an MSH segment to an A01 message.
You'll need to do this for every segment and message type combination
though, which I realise will be annoying.

I'm going to try and get a fix at least checked in within the next week or
two...

Cheers,
James


On Wed, Jun 19, 2013 at 5:35 AM, sagarshah1983 <sag...@ci...>wrote:

>
> Thanks a ton Christian for this.
> I think I can make use of Terser to make it generic and use ADT_A01 as base
> message, as there are some issues with ADT_AXX as reported in previous
> message.
>
>
>
> Christian Ohr-2 wrote:
> >
> > Yes, I can reproduce this problem. It seems that the MSH segment is not
> > allowed e.g. for A01 message by the validator, which is obviously
> > nonsense.
> > Maybe James can enlighten this a bit.... potentially there's a bug in the
> > generator.
> >
> > After all, when creating messages I don't see a need to create
> > superstructure messages, as you know which message you create. You still
> > have the problem that there is no common super-class or interface to ADT
> > messages, but their are ways to circumvent this, e.g. using the Terser
> > class:
> >
> > Message m = new ADT_A01();
> > m.initQuickstart("ADT", "A01", "P");
> > // everything below works on a generic level
> > Terser t = new Terser(m);
> > t.set("/MSH-9-2", "A04");
> > t.set("/PID-3-1", "myIdentifier");
> > ...
> >
> > hope this helps
> > Christian
> >
> >
> > 2013/6/19 sagarshah1983 <sag...@ci...>
> >
> >>
> >> Thanks Christian for sharing this link.
> >> I was trying to use ADT_AXX structure only, but found few issues with
> >> generating HL7 message with ADT_AXX and did not find a way to solve that
> >> out. So thought of checking for any other generic structure for ADT
> >> messages.
> >> Anyways, here's the issue I am facing.
> >> Code Snippet.
> >>
> >> ADT_AXX adt = new ADT_AXX();
> >> MSH msh = adt.getMSH();
> >> ....
> >> msh.getMsh9_MessageType().getMsg1_MessageCode().setValue("ADT");
> >> msh.getMsh9_MessageType().getMsg2_TriggerEvent().setValue("A28");
> >>
> msh.getMsh9_MessageType().getMsg3_MessageStructure().setValue("ADT_A28");
> >>
> >> Above works perfectly fine, but the moment I change last two lines to
> >> reflect A01, it fails.
> >>
> >> msh.getMsh9_MessageType().getMsg2_TriggerEvent().setValue("A01");
> >>
> msh.getMsh9_MessageType().getMsg3_MessageStructure().setValue("ADT_A01");
> >>
> >> Error details:
> >> Caused by: ca.uhn.hl7v2.validation.ValidationException: Message
> >> (superstructure ADT_AXX) of type ADT_A01 must not have content in MSH
> >>
> >> Any advice is appreciated.
> >>
> >> Regards,
> >> Sagar Shah
> >>
> >>
> >>
> >> Christian Ohr-2 wrote:
> >> >
> >> > If you are using HAPI 2.1, you should have a look at this:
> >> >
> >>
> http://hl7api.sourceforge.net/xref/ca/uhn/hl7v2/examples/ExampleSuperStructures.html
> >> > .
> >> >
> >> > cheers
> >> > Christian
> >> >
> >> >
> >> > 2013/6/18 sagarshah1983 <sag...@ci...>
> >> >
> >> >>
> >> >> That would be really great for me.
> >> >> Appreciate your reply and time for the same.
> >> >>
> >> >> Regards,
> >> >> Sagar Shah
> >> >>
> >> >> LDH-2 wrote:
> >> >> >
> >> >> > I am not aware of one in 1.x... I don't know 2.x well enough yet. I
> >> am
> >> >> on
> >> >> > the road, but I can send out later the type of code I have used to
> >> be
> >> >> adt
> >> >> > generic.
> >> >> >
> >> >> >
> >> >> >
> >> >> > ___________________________________________
> >> >> > Laurent Hasson (via my BlackBerry)
> >> >> > email: ld...@36...
> >> >> > cell: 646-283-2186
> >> >> > twitter: @ldhasson
> >> >> >
> >> >> > -----Original Message-----
> >> >> > From: sagarshah1983 <sag...@ci...>
> >> >> > Date: Tue, 18 Jun 2013 08:53:15
> >> >> > To: <hl7...@li...>
> >> >> > Subject: [HAPI-devel]  Generic class for ADT message
> >> >> >
> >> >> >
> >> >>
> >>
> ------------------------------------------------------------------------------
> >> >> > This SF.net email is sponsored by Windows:
> >> >> >
> >> >> > Build for Windows Store.
> >> >> >
> >> >> > http://p.sf.net/sfu/windows-dev2dev
> >> >> >
> >> >> >
> >> >>
> >>
> ------------------------------------------------------------------------------
> >> >> > This SF.net email is sponsored by Windows:
> >> >> >
> >> >> > Build for Windows Store.
> >> >> >
> >> >> > http://p.sf.net/sfu/windows-dev2dev
> >> >> > _______________________________________________
> >> >> > Hl7api-devel mailing list
> >> >> > Hl7...@li...
> >> >> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >> >> >
> >> >> >
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >>
> >>
> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35639472.html
> >> >> Sent from the hl7api-devel mailing list archive at Nabble.com.
> >> >>
> >> >>
> >> >>
> >> >>
> >>
> ------------------------------------------------------------------------------
> >> >> This SF.net email is sponsored by Windows:
> >> >>
> >> >> Build for Windows Store.
> >> >>
> >> >> http://p.sf.net/sfu/windows-dev2dev
> >> >> _______________________________________________
> >> >> Hl7api-devel mailing list
> >> >> Hl7...@li...
> >> >> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >> >>
> >> >
> >> >
> >>
> ------------------------------------------------------------------------------
> >> > This SF.net email is sponsored by Windows:
> >> >
> >> > Build for Windows Store.
> >> >
> >> > http://p.sf.net/sfu/windows-dev2dev
> >> > _______________________________________________
> >> > Hl7api-devel mailing list
> >> > Hl7...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >> >
> >> >
> >> --
> >> View this message in context:
> >>
> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35642054.html
> >> Sent from the hl7api-devel mailing list archive at Nabble.com.
> >>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> This SF.net email is sponsored by Windows:
> >>
> >> Build for Windows Store.
> >>
> >> http://p.sf.net/sfu/windows-dev2dev
> >> _______________________________________________
> >> Hl7api-devel mailing list
> >> Hl7...@li...
> >> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >>
> >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Windows:
> >
> > Build for Windows Store.
> >
> > http://p.sf.net/sfu/windows-dev2dev
> > _______________________________________________
> > Hl7api-devel mailing list
> > Hl7...@li...
> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35642561.html
> Sent from the hl7api-devel mailing list archive at Nabble.com.
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>

Re: [HAPI-devel] Generic class for ADT message

[sagarshah1983 <sag...@ci...>]

Thanks a ton Christian for this.
I think I can make use of Terser to make it generic and use ADT_A01 as base
message, as there are some issues with ADT_AXX as reported in previous
message.



Christian Ohr-2 wrote:
> 
> Yes, I can reproduce this problem. It seems that the MSH segment is not
> allowed e.g. for A01 message by the validator, which is obviously
> nonsense.
> Maybe James can enlighten this a bit.... potentially there's a bug in the
> generator.
> 
> After all, when creating messages I don't see a need to create
> superstructure messages, as you know which message you create. You still
> have the problem that there is no common super-class or interface to ADT
> messages, but their are ways to circumvent this, e.g. using the Terser
> class:
> 
> Message m = new ADT_A01();
> m.initQuickstart("ADT", "A01", "P");
> // everything below works on a generic level
> Terser t = new Terser(m);
> t.set("/MSH-9-2", "A04");
> t.set("/PID-3-1", "myIdentifier");
> ...
> 
> hope this helps
> Christian
> 
> 
> 2013/6/19 sagarshah1983 <sag...@ci...>
> 
>>
>> Thanks Christian for sharing this link.
>> I was trying to use ADT_AXX structure only, but found few issues with
>> generating HL7 message with ADT_AXX and did not find a way to solve that
>> out. So thought of checking for any other generic structure for ADT
>> messages.
>> Anyways, here's the issue I am facing.
>> Code Snippet.
>>
>> ADT_AXX adt = new ADT_AXX();
>> MSH msh = adt.getMSH();
>> ....
>> msh.getMsh9_MessageType().getMsg1_MessageCode().setValue("ADT");
>> msh.getMsh9_MessageType().getMsg2_TriggerEvent().setValue("A28");
>> msh.getMsh9_MessageType().getMsg3_MessageStructure().setValue("ADT_A28");
>>
>> Above works perfectly fine, but the moment I change last two lines to
>> reflect A01, it fails.
>>
>> msh.getMsh9_MessageType().getMsg2_TriggerEvent().setValue("A01");
>> msh.getMsh9_MessageType().getMsg3_MessageStructure().setValue("ADT_A01");
>>
>> Error details:
>> Caused by: ca.uhn.hl7v2.validation.ValidationException: Message
>> (superstructure ADT_AXX) of type ADT_A01 must not have content in MSH
>>
>> Any advice is appreciated.
>>
>> Regards,
>> Sagar Shah
>>
>>
>>
>> Christian Ohr-2 wrote:
>> >
>> > If you are using HAPI 2.1, you should have a look at this:
>> >
>> http://hl7api.sourceforge.net/xref/ca/uhn/hl7v2/examples/ExampleSuperStructures.html
>> > .
>> >
>> > cheers
>> > Christian
>> >
>> >
>> > 2013/6/18 sagarshah1983 <sag...@ci...>
>> >
>> >>
>> >> That would be really great for me.
>> >> Appreciate your reply and time for the same.
>> >>
>> >> Regards,
>> >> Sagar Shah
>> >>
>> >> LDH-2 wrote:
>> >> >
>> >> > I am not aware of one in 1.x... I don't know 2.x well enough yet. I
>> am
>> >> on
>> >> > the road, but I can send out later the type of code I have used to
>> be
>> >> adt
>> >> > generic.
>> >> >
>> >> >
>> >> >
>> >> > ___________________________________________
>> >> > Laurent Hasson (via my BlackBerry)
>> >> > email: ld...@36...
>> >> > cell: 646-283-2186
>> >> > twitter: @ldhasson
>> >> >
>> >> > -----Original Message-----
>> >> > From: sagarshah1983 <sag...@ci...>
>> >> > Date: Tue, 18 Jun 2013 08:53:15
>> >> > To: <hl7...@li...>
>> >> > Subject: [HAPI-devel]  Generic class for ADT message
>> >> >
>> >> >
>> >>
>> ------------------------------------------------------------------------------
>> >> > This SF.net email is sponsored by Windows:
>> >> >
>> >> > Build for Windows Store.
>> >> >
>> >> > http://p.sf.net/sfu/windows-dev2dev
>> >> >
>> >> >
>> >>
>> ------------------------------------------------------------------------------
>> >> > This SF.net email is sponsored by Windows:
>> >> >
>> >> > Build for Windows Store.
>> >> >
>> >> > http://p.sf.net/sfu/windows-dev2dev
>> >> > _______________________________________________
>> >> > Hl7api-devel mailing list
>> >> > Hl7...@li...
>> >> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35639472.html
>> >> Sent from the hl7api-devel mailing list archive at Nabble.com.
>> >>
>> >>
>> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> This SF.net email is sponsored by Windows:
>> >>
>> >> Build for Windows Store.
>> >>
>> >> http://p.sf.net/sfu/windows-dev2dev
>> >> _______________________________________________
>> >> Hl7api-devel mailing list
>> >> Hl7...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >>
>> >
>> >
>> ------------------------------------------------------------------------------
>> > This SF.net email is sponsored by Windows:
>> >
>> > Build for Windows Store.
>> >
>> > http://p.sf.net/sfu/windows-dev2dev
>> > _______________________________________________
>> > Hl7api-devel mailing list
>> > Hl7...@li...
>> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >
>> >
>> --
>> View this message in context:
>> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35642054.html
>> Sent from the hl7api-devel mailing list archive at Nabble.com.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> Hl7api-devel mailing list
>> Hl7...@li...
>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> 
> 

-- 
View this message in context: http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35642561.html
Sent from the hl7api-devel mailing list archive at Nabble.com.

Re: [HAPI-devel] Generic class for ADT message

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

Yes, I can reproduce this problem. It seems that the MSH segment is not
allowed e.g. for A01 message by the validator, which is obviously nonsense.
Maybe James can enlighten this a bit.... potentially there's a bug in the
generator.

After all, when creating messages I don't see a need to create
superstructure messages, as you know which message you create. You still
have the problem that there is no common super-class or interface to ADT
messages, but their are ways to circumvent this, e.g. using the Terser
class:

Message m = new ADT_A01();
m.initQuickstart("ADT", "A01", "P");
// everything below works on a generic level
Terser t = new Terser(m);
t.set("/MSH-9-2", "A04");
t.set("/PID-3-1", "myIdentifier");
...

hope this helps
Christian


2013/6/19 sagarshah1983 <sag...@ci...>

>
> Thanks Christian for sharing this link.
> I was trying to use ADT_AXX structure only, but found few issues with
> generating HL7 message with ADT_AXX and did not find a way to solve that
> out. So thought of checking for any other generic structure for ADT
> messages.
> Anyways, here's the issue I am facing.
> Code Snippet.
>
> ADT_AXX adt = new ADT_AXX();
> MSH msh = adt.getMSH();
> ....
> msh.getMsh9_MessageType().getMsg1_MessageCode().setValue("ADT");
> msh.getMsh9_MessageType().getMsg2_TriggerEvent().setValue("A28");
> msh.getMsh9_MessageType().getMsg3_MessageStructure().setValue("ADT_A28");
>
> Above works perfectly fine, but the moment I change last two lines to
> reflect A01, it fails.
>
> msh.getMsh9_MessageType().getMsg2_TriggerEvent().setValue("A01");
> msh.getMsh9_MessageType().getMsg3_MessageStructure().setValue("ADT_A01");
>
> Error details:
> Caused by: ca.uhn.hl7v2.validation.ValidationException: Message
> (superstructure ADT_AXX) of type ADT_A01 must not have content in MSH
>
> Any advice is appreciated.
>
> Regards,
> Sagar Shah
>
>
>
> Christian Ohr-2 wrote:
> >
> > If you are using HAPI 2.1, you should have a look at this:
> >
> http://hl7api.sourceforge.net/xref/ca/uhn/hl7v2/examples/ExampleSuperStructures.html
> > .
> >
> > cheers
> > Christian
> >
> >
> > 2013/6/18 sagarshah1983 <sag...@ci...>
> >
> >>
> >> That would be really great for me.
> >> Appreciate your reply and time for the same.
> >>
> >> Regards,
> >> Sagar Shah
> >>
> >> LDH-2 wrote:
> >> >
> >> > I am not aware of one in 1.x... I don't know 2.x well enough yet. I am
> >> on
> >> > the road, but I can send out later the type of code I have used to be
> >> adt
> >> > generic.
> >> >
> >> >
> >> >
> >> > ___________________________________________
> >> > Laurent Hasson (via my BlackBerry)
> >> > email: ld...@36...
> >> > cell: 646-283-2186
> >> > twitter: @ldhasson
> >> >
> >> > -----Original Message-----
> >> > From: sagarshah1983 <sag...@ci...>
> >> > Date: Tue, 18 Jun 2013 08:53:15
> >> > To: <hl7...@li...>
> >> > Subject: [HAPI-devel]  Generic class for ADT message
> >> >
> >> >
> >>
> ------------------------------------------------------------------------------
> >> > This SF.net email is sponsored by Windows:
> >> >
> >> > Build for Windows Store.
> >> >
> >> > http://p.sf.net/sfu/windows-dev2dev
> >> >
> >> >
> >>
> ------------------------------------------------------------------------------
> >> > This SF.net email is sponsored by Windows:
> >> >
> >> > Build for Windows Store.
> >> >
> >> > http://p.sf.net/sfu/windows-dev2dev
> >> > _______________________________________________
> >> > Hl7api-devel mailing list
> >> > Hl7...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >>
> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35639472.html
> >> Sent from the hl7api-devel mailing list archive at Nabble.com.
> >>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> This SF.net email is sponsored by Windows:
> >>
> >> Build for Windows Store.
> >>
> >> http://p.sf.net/sfu/windows-dev2dev
> >> _______________________________________________
> >> Hl7api-devel mailing list
> >> Hl7...@li...
> >> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >>
> >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Windows:
> >
> > Build for Windows Store.
> >
> > http://p.sf.net/sfu/windows-dev2dev
> > _______________________________________________
> > Hl7api-devel mailing list
> > Hl7...@li...
> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >
> >
> --
> View this message in context:
> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35642054.html
> Sent from the hl7api-devel mailing list archive at Nabble.com.
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>

Re: [HAPI-devel] Generic class for ADT message

[sagarshah1983 <sag...@ci...>]

Thanks Christian for sharing this link.
I was trying to use ADT_AXX structure only, but found few issues with
generating HL7 message with ADT_AXX and did not find a way to solve that
out. So thought of checking for any other generic structure for ADT
messages.
Anyways, here's the issue I am facing.
Code Snippet.

ADT_AXX adt = new ADT_AXX();
MSH msh = adt.getMSH();
....
msh.getMsh9_MessageType().getMsg1_MessageCode().setValue("ADT");
msh.getMsh9_MessageType().getMsg2_TriggerEvent().setValue("A28");
msh.getMsh9_MessageType().getMsg3_MessageStructure().setValue("ADT_A28");

Above works perfectly fine, but the moment I change last two lines to
reflect A01, it fails.

msh.getMsh9_MessageType().getMsg2_TriggerEvent().setValue("A01");
msh.getMsh9_MessageType().getMsg3_MessageStructure().setValue("ADT_A01");

Error details:
Caused by: ca.uhn.hl7v2.validation.ValidationException: Message
(superstructure ADT_AXX) of type ADT_A01 must not have content in MSH

Any advice is appreciated.

Regards,
Sagar Shah



Christian Ohr-2 wrote:
> 
> If you are using HAPI 2.1, you should have a look at this:
> http://hl7api.sourceforge.net/xref/ca/uhn/hl7v2/examples/ExampleSuperStructures.html
> .
> 
> cheers
> Christian
> 
> 
> 2013/6/18 sagarshah1983 <sag...@ci...>
> 
>>
>> That would be really great for me.
>> Appreciate your reply and time for the same.
>>
>> Regards,
>> Sagar Shah
>>
>> LDH-2 wrote:
>> >
>> > I am not aware of one in 1.x... I don't know 2.x well enough yet. I am
>> on
>> > the road, but I can send out later the type of code I have used to be
>> adt
>> > generic.
>> >
>> >
>> >
>> > ___________________________________________
>> > Laurent Hasson (via my BlackBerry)
>> > email: ld...@36...
>> > cell: 646-283-2186
>> > twitter: @ldhasson
>> >
>> > -----Original Message-----
>> > From: sagarshah1983 <sag...@ci...>
>> > Date: Tue, 18 Jun 2013 08:53:15
>> > To: <hl7...@li...>
>> > Subject: [HAPI-devel]  Generic class for ADT message
>> >
>> >
>> ------------------------------------------------------------------------------
>> > This SF.net email is sponsored by Windows:
>> >
>> > Build for Windows Store.
>> >
>> > http://p.sf.net/sfu/windows-dev2dev
>> >
>> >
>> ------------------------------------------------------------------------------
>> > This SF.net email is sponsored by Windows:
>> >
>> > Build for Windows Store.
>> >
>> > http://p.sf.net/sfu/windows-dev2dev
>> > _______________________________________________
>> > Hl7api-devel mailing list
>> > Hl7...@li...
>> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> >
>> >
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35639472.html
>> Sent from the hl7api-devel mailing list archive at Nabble.com.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> Hl7api-devel mailing list
>> Hl7...@li...
>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> 
> 
-- 
View this message in context: http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35642054.html
Sent from the hl7api-devel mailing list archive at Nabble.com.

Re: [HAPI-devel] Generic class for ADT message

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

If you are using HAPI 2.1, you should have a look at this:
http://hl7api.sourceforge.net/xref/ca/uhn/hl7v2/examples/ExampleSuperStructures.html
.

cheers
Christian


2013/6/18 sagarshah1983 <sag...@ci...>

>
> That would be really great for me.
> Appreciate your reply and time for the same.
>
> Regards,
> Sagar Shah
>
> LDH-2 wrote:
> >
> > I am not aware of one in 1.x... I don't know 2.x well enough yet. I am on
> > the road, but I can send out later the type of code I have used to be adt
> > generic.
> >
> >
> >
> > ___________________________________________
> > Laurent Hasson (via my BlackBerry)
> > email: ld...@36...
> > cell: 646-283-2186
> > twitter: @ldhasson
> >
> > -----Original Message-----
> > From: sagarshah1983 <sag...@ci...>
> > Date: Tue, 18 Jun 2013 08:53:15
> > To: <hl7...@li...>
> > Subject: [HAPI-devel]  Generic class for ADT message
> >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Windows:
> >
> > Build for Windows Store.
> >
> > http://p.sf.net/sfu/windows-dev2dev
> >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Windows:
> >
> > Build for Windows Store.
> >
> > http://p.sf.net/sfu/windows-dev2dev
> > _______________________________________________
> > Hl7api-devel mailing list
> > Hl7...@li...
> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35639472.html
> Sent from the hl7api-devel mailing list archive at Nabble.com.
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>

Re: [HAPI-devel] Generic class for ADT message

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

I posted this response a couple of weeks back to a similar question about ADT generic.
 
Ian
---
I overcame this issue by creating a GENERIC_ADT message using techniques shown on the Hapi site. Our establishment has many Z-segments, so I had to do all those, and group them accordingly. A basic example is available on the Hapi site at http://hl7api.sourceforge.net/xref/ca/uhn/hl7v2/examples/CustomModelClasses.html
Snippets from the objects are shown below. It was quite a long repetitive process, and I even wrote a module that created java code from a text file for the Z segments. However, now it's done all that is required is to create a GENERIC_ADT with it's constructor, and parse the message text with it's parse method.
The groups shown in this snippet were defined in similar manner as additional classes in the java project.
Hope this helps
Ian
--- code snippets ---
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/
package au.gov.qld.health.sit.hl7;
import ca.uhn.hl7v2.HL7Exception;
import ca.uhn.hl7v2.model.AbstractMessage;
import ca.uhn.hl7v2.model.v24.segment.*;
import ca.uhn.hl7v2.parser.ModelClassFactory;
/**
*
* @author VowlesI
*/
public class GENERIC_ADT extends AbstractMessage {
public GENERIC_ADT(ModelClassFactory factory) throws HL7Exception {
super(factory);
Class<MSH> addMsh = MSH.class;
this.add(addMsh,true,false);
Class<EVN> addEvn = EVN.class;
this.add(addEvn, false, false);
Class<SCH> addSch = SCH.class;
this.add(addSch, false, false);
Class<PID> addPid = PID.class;
this.add(addPid, true, false);
Class<PD1> addPd1 = PD1.class;
this.add(addPd1, false, false);
.
. snip .
.
.
Class<MASTERFILE> addMasterFile = MASTERFILE.class;
this.add(addMasterFile,false,false);
Class<ZHBCIS> addZhbcis = ZHBCIS.class;
this.add(addZhbcis, false, false);
Class<ZNORM> addZnorm = ZNORM.class;
this.add(addZnorm, false, false);
}

public MSH getMSH() throws HL7Exception {
return (MSH) get("MSH");
}

public EVN getEVN() throws HL7Exception {
return (EVN) get ("EVN");
}

public SCH getSCH() throws HL7Exception {
return (SCH) get ("SCH");
}

public PID getPID() throws HL7Exception {
return (PID) get ("PID");
}

public PD1 getPD1() throws HL7Exception {
return (PD1) get ("PD1");
}
.
. snip
.
.

public MASTERFILE getMASTERFILE() throws HL7Exception {
return (MASTERFILE) get ("MASTERFILE");
}

public ZHBCIS getZHBCIS() throws HL7Exception {
return (ZHBCIS) get ("ZHBCIS");
}
public ZNORM getZNORM() throws HL7Exception {
return (ZNORM) get ("ZNORM");
}
}


>>> sagarshah1983 <sag...@ci...> 19/06/13 1:53 >>>

What is the generic class that can be used for any kind of ADT message covering all the possible segments?
I want to handle A01, A04, A05, A08 and A28 messages for now, but might want to extend the same design for any ADT trigger events. Which class from HAPI library is the best fit for the same?
I am relatively new to HAPI and hence need a help to get started.
I looked at ADT_AXX and ADT_A01 classes, but not sure, if these cover all the required segments as per specific trigger events.
<br><hr align="left" width="300">
View this message in context: <a href="http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35639316.html">Generic class for ADT message</a><br>
Sent from the <a href="http://old.nabble.com/hl7api-devel-f3468.html">hl7api-devel mailing list archive</a> at Nabble.com.<br>

********************************************************************************
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] Generic class for ADT message

[Laurent H. <ld...@36...>]

This is how we do it. I would do it more cleanly if I were to write this
again now, but this should point you in the right direction:

-          We have individual classes to store the data we care about from
each segment (see later)

-          We try to get a segment from the message

-          If the message is not there, we just throw an exception, ignore
and continue

 

          protected HL7Record(Message Msg)

          throws DataTypeException, HL7Exception

           {

                try

                 {

                   _PID = new HL7PID((PID)Msg.get("PID"));

                 }

                catch (HL7Exception E) { }

 

                try

                 {

                   Segment segment = (Segment)Msg.get("PV1");

                   if (segment != null)

                    _PV = new HL7PV((PV1)segment, (PV2)Msg.get("PV2"));

                 }

                catch (HL7Exception E) {  }

 

                try

                 {

                   Structure[] Structs = Msg.getAll("DG1");

                   if (Structs != null && Structs.length > 0)

                    {

                      _DG1 = new HL7DG1[Structs.length];

                      for (int i = 0; i < Structs.length; ++i)

                       _DG1[i] = new HL7DG1((DG1)Structs[i]);

                    }

                 }

                catch (HL7Exception E)  {  }

 

                try

                 {

                   Structure[] Structs = Msg.getAll("INSURANCE");

                   if (Structs != null && Structs.length > 0)

                    _IN1 = new HL7IN1(Structs);

                 }

                catch (HL7Exception E) {  }

 

                try

                 {

                   Structure[] Structs = Msg.getAll("AL1");

                   if (Structs != null && Structs.length > 0)

                     _AL1 = new HL7AL1(Structs);

                 }

                catch (HL7Exception E) {  }

 

                try

                 {

                   Segment s = (Segment) Msg.get("MRG");

                   if (s != null)

                    _MRG = new HL7MRG((MRG)s);

                 }

                catch (Exception E) { }

           }

 

And then, for an individual class, for example DG1, we do simple mappings:

 

public class HL7DG1

  {

    public final String  _SetId         ;

    public final String  _CodingMethod  ;

    public final String  _Code          ;

    public final String  _Description   ;

    public final HL7DTM  _DateTime      ;

    public final String  _Type          ;

    public final String  _MajorCategory ;

    public final String  _RelatedGroup  ;

    public final HL7XCN  _Clinician     ;

    public final String  _Classification;

    public final String  _Confidential  ;

    public final String  _Identifier    ;

 

    public HL7DG1(DG1 Diagnosis)

    throws DataTypeException, HL7Exception

      {

/*DG1-1: Set ID - DG1 (SI)                                   */ _SetId
= Diagnosis.getSetIDDG1().getValue();

/*DG1-2: Diagnosis Coding Method (NULLDT) optional           */
_CodingMethod   = Diagnosis.getDiagnosisCodingMethod().getValue();

/*DG1-3: Diagnosis Code - DG1 (CWE)                          */ _Code
=
MakeSureItsAlright(Diagnosis.getDiagnosisCodeDG1().getIdentifier().getValue(
), _CodingMethod);

/*DG1-4: Diagnosis Description (NULLDT) optional             */ _Description
= Diagnosis.getDiagnosisDescription().getValue();

/*DG1-5: Diagnosis Date/Time (DTM) optional                  */ _DateTime
= new HL7DTM(Diagnosis.getDiagnosisDateTime());

/*DG1-6: Diagnosis Type (IS)                                 */ _Type
= Diagnosis.getDiagnosisType().getValue();

/*DG1-7: Major Diagnostic Category (CNE) optional            */
_MajorCategory  =
Diagnosis.getMajorDiagnosticCategory().getIdentifier().getValue();

/*DG1-8: Diagnostic Related Group (CNE) optional             */
_RelatedGroup   =
Diagnosis.getDiagnosticRelatedGroup().getIdentifier().getValue();

/*DG1-9: DRG Approval Indicator (ID) optional                */

/*DG1-10: DRG Grouper Review Code (IS) optional              */

/*DG1-11: Outlier Type (CWE) optional                        */

/*DG1-12: Outlier Days (NM) optional                         */

/*DG1-13: Outlier Cost (CP) optional                         */

/*DG1-14: Grouper Version And Type (NULLDT) optional         */

/*DG1-15: Diagnosis Priority (ID) optional                   */

/*DG1-16: Diagnosing Clinician (XCN) optional repeating      */ _Clinician
= new HL7XCN(Diagnosis.getDiagnosingClinician(0));

/*DG1-17: Diagnosis Classification (IS) optional             */
_Classification = Diagnosis.getDiagnosisClassification().getValue();

/*DG1-18: Confidential Indicator (ID) optional               */
_Confidential   = Diagnosis.getConfidentialIndicator().getValue();

/*DG1-19: Attestation Date/Time (DTM) optional               */

/*DG1-20: Diagnosis Identifier (EI) optional                 */ _Identifier
= Diagnosis.getDiagnosisIdentifier().getEntityIdentifier().getValue();

/*DG1-21: Diagnosis Action Code (ID) optional                */

/*DG1-22: Parent Diagnosis (EI) optional                     */

/*DG1-23: DRG CCL Value Code (CWE) optional                  */

/*DG1-24: DRG Grouping Usage (ID) optional                   */

/*DG1-25: DRG Diagnosis Determination Status (IS) optional   */

/*DG1-26: Present On Admission (POA) Indicator (IS) optional */

      }    

  }

 

What I have found to be the biggest pain is to figure out if the data is in
x.getValue(), or x. getIdentifier().getValue() etc. Additionally, again, I
would do it a bit differently today and make this a lot more flexible by
using the basic parser and access fields with HL7 "paths" J 

 

 

 

 

___________________________________________________________

Laurent Hasson

Co-Founder and CTO

360Fresh Inc.

Cell: 646.283.2186

Office: 5 Penn Plaza, Suite 1986, NY NY 10001

 

This e-mail may contain confidential and/or privileged information. This
information is intended only for the use of the individual(s) and
entity(ies) to whom it is addressed. If you are the intended recipient,
further disclosures are prohibited without proper authorization. If you are
not the intended recipient (or have received this e-mail in error) please
notify the sender immediately and destroy this e-mail. Any unauthorized
copying, disclosure or distribution of the material in this e-mail is
strictly forbidden and possibly a violation of federal or state law and
regulations.

 

 

-----Original Message-----
From: sagarshah1983 [mailto:sag...@ci...] 
Sent: Tuesday, June 18, 2013 11:32
To: hl7...@li...
Subject: Re: [HAPI-devel] Generic class for ADT message

 

 

That would be really great for me.

Appreciate your reply and time for the same.

 

Regards,

Sagar Shah

 

LDH-2 wrote:

> 

> I am not aware of one in 1.x... I don't know 2.x well enough yet. I am 

> on the road, but I can send out later the type of code I have used to 

> be adt generic.

> 

> 

> 

> ___________________________________________

> Laurent Hasson (via my BlackBerry)

> email:  <mailto:ld...@36...> ld...@36...

> cell: 646-283-2186

> twitter: @ldhasson

> 

> -----Original Message-----

> From: sagarshah1983 < <mailto:sag...@ci...>
sag...@ci...>

> Date: Tue, 18 Jun 2013 08:53:15

> To: < <mailto:hl7...@li...>
hl7...@li...>

> Subject: [HAPI-devel]  Generic class for ADT message

> 

> ----------------------------------------------------------------------

> -------- This SF.net email is sponsored by Windows:

> 

> Build for Windows Store.

> 

>  <http://p.sf.net/sfu/windows-dev2dev> http://p.sf.net/sfu/windows-dev2dev

> 

> ----------------------------------------------------------------------

> -------- This SF.net email is sponsored by Windows:

> 

> Build for Windows Store.

> 

>  <http://p.sf.net/sfu/windows-dev2dev> http://p.sf.net/sfu/windows-dev2dev

> _______________________________________________

> Hl7api-devel mailing list

>  <mailto:Hl7...@li...>
Hl7...@li...

>  <https://lists.sourceforge.net/lists/listinfo/hl7api-devel>
https://lists.sourceforge.net/lists/listinfo/hl7api-devel

> 

> 

 

--

View this message in context:
<http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35639472.htm
l>
http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35639472.html

Sent from the hl7api-devel mailing list archive at Nabble.com.

 

 

----------------------------------------------------------------------------
--

This SF.net email is sponsored by Windows:

 

Build for Windows Store.

 

 <http://p.sf.net/sfu/windows-dev2dev> http://p.sf.net/sfu/windows-dev2dev

_______________________________________________

Hl7api-devel mailing list

 <mailto:Hl7...@li...>
Hl7...@li...

 <https://lists.sourceforge.net/lists/listinfo/hl7api-devel>
https://lists.sourceforge.net/lists/listinfo/hl7api-devel

Re: [HAPI-devel] Generic class for ADT message

[sagarshah1983 <sag...@ci...>]

That would be really great for me.
Appreciate your reply and time for the same.

Regards,
Sagar Shah

LDH-2 wrote:
> 
> I am not aware of one in 1.x... I don't know 2.x well enough yet. I am on
> the road, but I can send out later the type of code I have used to be adt
> generic.
> 
> 
> 
> ___________________________________________
> Laurent Hasson (via my BlackBerry)
> email: ld...@36...
> cell: 646-283-2186
> twitter: @ldhasson
> 
> -----Original Message-----
> From: sagarshah1983 <sag...@ci...>
> Date: Tue, 18 Jun 2013 08:53:15 
> To: <hl7...@li...>
> Subject: [HAPI-devel]  Generic class for ADT message
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> 
> 

-- 
View this message in context: http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35639472.html
Sent from the hl7api-devel mailing list archive at Nabble.com.

Re: [HAPI-devel] Generic class for ADT message

[LDH <ld...@36...>]

I am not aware of one in 1.x... I don't know 2.x well enough yet. I am on the road, but I can send out later the type of code I have used to be adt generic.



___________________________________________
Laurent Hasson (via my BlackBerry)
email: ld...@36...
cell: 646-283-2186
twitter: @ldhasson

-----Original Message-----
From: sagarshah1983 <sag...@ci...>
Date: Tue, 18 Jun 2013 08:53:15 
To: <hl7...@li...>
Subject: [HAPI-devel]  Generic class for ADT message

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev

[HAPI-devel] Generic class for ADT message

[sagarshah1983 <sag...@ci...>]

What is the generic class that can be used for any kind of ADT message
covering all the possible segments?
I want to handle A01, A04, A05, A08 and A28 messages for now, but might want
to extend the same design for any ADT trigger events. Which class from HAPI
library is the best fit for the same?
I am relatively new to HAPI and hence need a help to get started.
I looked at ADT_AXX and ADT_A01 classes, but not sure, if these cover all
the required segments as per specific trigger events.
-- 
View this message in context: http://old.nabble.com/Generic-class-for-ADT-message-tp35639316p35639316.html
Sent from the hl7api-devel mailing list archive at Nabble.com.

Re: [HAPI-devel] Hapi 2.1 version's MSH-9 filed concerns

[vijayaratha v. <vij...@gm...>]

Thanks Eugene, same solution also provided by James..
Would like to know about the decision for the first point of James's, That
is , it is a bug or not, in that case, what would be the trigger event for
this type of messages..

Regards;
-Ratha

On 14 June 2013 18:31, Eugene Berman <eug...@mu...> wrote:

> Folks, just FYI, I had a similar issue while working on some projects;
> however, Mule ESB provides a simple solution for this; you can intercept
> the ACK message before it is returned to the caller, and replace the MSH-9
> with any value that client would expect, by using one of several available
> transformers that accept HL7 messages. Ratha, perhaps you can do the same
> thing in your solution, e.g. you could use HAPI Terser, e.g.
> terser.set("/MSH-9", "ACK"); etc.
>
> Regards,
>
> Eugene
>
> --
> Eugene Berman
> Sr. Enterprise Solutions Architect
> ----
> MuleSoft Inc.
> 77 Geary Street, Ste. 400
> San Francisco, CA 94108
> Office: 415 229 2063
> Website: http://www.mulesoft.com <http://www.mulesoft.com/>
> ---
> Entia non sunt multiplicanda praeter necessitatem!
>
>
>
> On Jun 14, 2013, at 4:45 AM, James Agnew <ja...@ja...> wrote:
>
> > Hi Ratha,
> >
> > To be completely honest, I have no idea what the right answer is to
> this. Certainly you are right, the standard seems to indicate that the R22
> trigger is not allowable in an ACK message, but the standard also doesn't
> seem to provide any indication on what would be an appropriate trigger for
> an ACK to an OUL^R22 message.
> >
> > I think there are a few courses of action here:
> >
> > 1. It might make sense to take the question of "what belongs as a
> trigger event on an ACK to an OUL^R22 message" over to the HL7
> Infrastructure and Messaging (InM) mailing list for broader consideration.
> I'm curious now too, so if you didn't want to handle this I would be
> willing to do so.
> >
> > 2. If you wanted to file a bug report for HAPI, we could probably code
> in the ability for HAPI to not use a trigger event for ACKs to messages
> that shouldn't get one according to Table 0003. I'll be honest though, this
> will be somewhat painful to implement so it probably won't happen overnight
> (unless you or someone else wanted to give it a shot?)
> >
> > 3. As a fairly simple workaround, you could add custom logic to your
> application to clear MSH-9-2 as needed after you generate your ACK message.
> >
> > Cheers,
> > James
> >
> >
> >
> >
> > On Fri, Jun 14, 2013 at 3:18 AM, vijayaratha vijayasingam <
> vij...@gm...> wrote:
> > Hi James/all;
> >
> > Do you believe this as a BUG in Hapi or acceptable behavior?
> >
> > Thanks
> >
> >
> >
> > On 13 June 2013 14:45, vijayaratha vijayasingam <vij...@gm...>
> wrote:
> > Hi James;
> > Thanks for considering this.
> > Please find the following HL7 Data definition tables [1] .In   table
> 0003 (page A-25) . The trigger event R22 can be associated only with the
> OUL event type (but NOT with an ACK event type) whereas the trigger event
> A01 can be associated with both ADT and ACK event type.[2,3]
> >
> > [1]http://www.hl7.org/special/committees/vocab/v26_appendix_a.pdf
> >
> > [1]0003 A01 ADT/ACK - Admit/visit notification
> > [2]0003 R22 OUL - Unsolicited Specimen Oriented Observation Message
> >
> > Does this help you?
> >
> > Thanks
> > -Ratha
> >
> >
> > On 13 June 2013 01:40, James Agnew <ja...@ja...> wrote:
> > Hi Ratha,
> >
> > While the HL7 standard doesn't seem to specifically mention whether or
> not the response for an OUL^R22 should have the R22 trigger event in it's
> ACK, the general pattern in processing HL7 v2 is that the trigger event
> will always be the same as the message being acknowledged. A quick scan of
> the standard for words to that effect has come up blank (but maybe I'm not
> looking in the right place- I checked Chapter 2 of the 2.6 standard at
> least) but this is definitely how basically every system I work with
> regularly behaves.
> >
> > What leads you to believe this is not desirable behaviour? Are you
> interfacing with a system that specifically rejects ACK messages with the
> R22 trigger?
> >
> > Cheers,
> > James
> >
> >
> > On Wed, Jun 12, 2013 at 11:34 AM, vijayaratha vijayasingam <
> vij...@gm...> wrote:
> > Oh..hapi generates this ack message, when i send OUL^R22 message..
> > Others any clue?..
> > Is this valid or bug?
> >
> >
> > On 12 June 2013 20:22, VIOT Yves <yve...@cs...> wrote:
> > Sorry, i never had to handle such triggers, but if i had to, i will
> produce an ACK - unless the sender doesn't need them.
> > In specs, there is no ACK^R22 following de OUL^R22 definition but i
> can't say it's a mistake or not.
> >
> > Le 12/06/2013 16:46, vijayaratha vijayasingam a écrit :
> >> Hi Viot;
> >> Sorry i sent different initial sample message ;Please check my later
> replies;
> >> Im getting following[1] ACK in  MSH-9 filde fro my OUL^R22 message. Is
> that valid?
> >> ACK^R22^ACK|
> >>
> >> Thanks
> >>
> >>
> >> On 12 June 2013 17:11, VIOT Yves <yve...@cs...> wrote:
> >> Hi,
> >> This is valid
> >> Here is what you can find in the HL7 2.5 documentation, following the
> ADT^A01^ADT_A01 messages structure definition.
> >> ACK^A01^ACK
> >> To get rid of it just get the MSH-9-1 with the terser.
> >>
> >> Yves
> >>
> >> Le 12/06/2013 13:25, vijayaratha vijayasingam a écrit :
> >>> Hi all;
> >>> Anyone have clue..?:(
> >>> I badly need this to sort out..
> >>> thanks
> >>>
> >>>
> >>> On 12 June 2013 15:31, vijayaratha vijayasingam <vij...@gm...>
> wrote:
> >>> Hi all;
> >>> Im using Hapi 2.1 version release an dit works perfect. But i have an
> issue with an error response which i get from Hapi.
> >>> My request is;
> >>> MSH|^~\&|||||20130612143324.392+0530||ADT^A01^ADT_A01|2601|T|2.5
> >>>
> >>> And My response is;
> >>> MSH|^~\&|||||20130612152510.448+0530||ACK^A01^ACK|1623|T|2.5
> >>> MSA|AE|2601
> >>> ERR|||207^Application internal error^HL70357^^^^^^OOPS|E
> >>>
> >>>
> >>> In the above response , if you check the MSH-9 filed , it is;
> >>>
> >>> ACK^A01^ACK
> >>>
> >>> Shouldn't that be "|ACK". because it is additionaly adding "AO1"
> message to that filed, which is not valid. And i suspect that , it picks
> from that from original request.
> >>>
> >>> Can anybody help me on this? Ho w can i avoid that invalid segment?
> >>> Why Hapi additionally adds that filed in the MSH-9 filed?
> >>>
> >>> Thanks
> >>> -ratha
> >>>
> >>>
> >>>
> >>>
> >>>
> ------------------------------------------------------------------------------
> >>> This SF.net email is sponsored by Windows:
> >>>
> >>> Build for Windows Store.
> >>>
> >>>
> >>> http://p.sf.net/sfu/windows-dev2dev
> >>>
> >>>
> >>> _______________________________________________
> >>> Hl7api-devel mailing list
> >>>
> >>> Hl7...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> This SF.net email is sponsored by Windows:
> >>
> >> Build for Windows Store.
> >>
> >> http://p.sf.net/sfu/windows-dev2dev
> >> _______________________________________________
> >> Hl7api-devel mailing list
> >> Hl7...@li...
> >> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >>
> >>
> >
> >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Windows:
> >
> > Build for Windows Store.
> >
> > http://p.sf.net/sfu/windows-dev2dev
> > _______________________________________________
> > Hl7api-devel mailing list
> > Hl7...@li...
> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Windows:
> >
> > Build for Windows Store.
> >
> > http://p.sf.net/sfu/windows-dev2dev
> > _______________________________________________
> > Hl7api-devel mailing list
> > Hl7...@li...
> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> >
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Windows:
> >
> > Build for Windows Store.
> >
> >
> http://p.sf.net/sfu/windows-dev2dev_______________________________________________
> > Hl7api-devel mailing list
> > Hl7...@li...
> > https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>
>


-- 
-Ratha
http://vvratha.blogspot.com/

[HAPI-devel] Question on HL7 ADT message generation

[Sagar S. <sag...@ci...>]

Hello James,

My question is fairly simple, but since I am pretty new to HL7 and HAPI. I
think it would be good to get started with clearing my basics.

My job is to generate a HL7 message of type ADT (could be few events like
A01, A04, A05, A8, and A28).

Input that I have with me is a POJO java class with the attributes required
for generating HL7 message.

 

What I want to know is,

-          Is there any utility class in HAPI that helps me to generate HL7
message using path like notations (the way terser works for parsing).

-          Secondly, can I create specific segments (like MSH or PID)
individually without creating group first like ADT_A01? If so, how? I wish
to create PID independently and then add the same to any group. So I am
looking for option other than ADT_A01.getPID(). I noticed that, if I create
PID as PID pid = new PID(adt_a01_object, factory), then still PID is not
added to adt_a01_object, when I print adt_a01_object.encode().

 

Appreciate your inputs.

Thanks.

 

Regards,

Sagar Shah




===========================================================================================================================================================================================
DISCLAIMER:
The information contained in this message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and permanently delete this message and any attachments from your system. Any dissemination, use, review, distribution, printing or copying of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. CitiusTech shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. CitiusTech does not guarantee that the integrity of this communication has been maintained or that this communication is free of viruses, interceptions or interferences. 
====================================================================================================================================================================



===========================================================================================================================================================================================
DISCLAIMER:
The information contained in this message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and permanently delete this message and any attachments from your system. Any dissemination, use, review, distribution, printing or copying of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. CitiusTech shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. CitiusTech does not guarantee that the integrity of this communication has been maintained or that this communication is free of viruses, interceptions or interferences. 
====================================================================================================================================================================

Re: [HAPI-devel] Hapi 2.1 version's MSH-9 filed concerns

[Eugene B. <eug...@mu...>]

Folks, just FYI, I had a similar issue while working on some projects; however, Mule ESB provides a simple solution for this; you can intercept the ACK message before it is returned to the caller, and replace the MSH-9 with any value that client would expect, by using one of several available transformers that accept HL7 messages. Ratha, perhaps you can do the same thing in your solution, e.g. you could use HAPI Terser, e.g. terser.set("/MSH-9", "ACK"); etc.

Regards,

Eugene

-- 
Eugene Berman
Sr. Enterprise Solutions Architect
----
MuleSoft Inc.
77 Geary Street, Ste. 400
San Francisco, CA 94108
Office: 415 229 2063
Website: http://www.mulesoft.com <http://www.mulesoft.com/> 
---
Entia non sunt multiplicanda praeter necessitatem!



On Jun 14, 2013, at 4:45 AM, James Agnew <ja...@ja...> wrote:

> Hi Ratha,
> 
> To be completely honest, I have no idea what the right answer is to this. Certainly you are right, the standard seems to indicate that the R22 trigger is not allowable in an ACK message, but the standard also doesn't seem to provide any indication on what would be an appropriate trigger for an ACK to an OUL^R22 message.
> 
> I think there are a few courses of action here:
> 
> 1. It might make sense to take the question of "what belongs as a trigger event on an ACK to an OUL^R22 message" over to the HL7 Infrastructure and Messaging (InM) mailing list for broader consideration. I'm curious now too, so if you didn't want to handle this I would be willing to do so.
> 
> 2. If you wanted to file a bug report for HAPI, we could probably code in the ability for HAPI to not use a trigger event for ACKs to messages that shouldn't get one according to Table 0003. I'll be honest though, this will be somewhat painful to implement so it probably won't happen overnight (unless you or someone else wanted to give it a shot?)
> 
> 3. As a fairly simple workaround, you could add custom logic to your application to clear MSH-9-2 as needed after you generate your ACK message.
> 
> Cheers,
> James
> 
> 
> 
> 
> On Fri, Jun 14, 2013 at 3:18 AM, vijayaratha vijayasingam <vij...@gm...> wrote:
> Hi James/all;
> 
> Do you believe this as a BUG in Hapi or acceptable behavior?
> 
> Thanks
> 
> 
> 
> On 13 June 2013 14:45, vijayaratha vijayasingam <vij...@gm...> wrote:
> Hi James;
> Thanks for considering this.
> Please find the following HL7 Data definition tables [1] .In   table 0003 (page A-25) . The trigger event R22 can be associated only with the OUL event type (but NOT with an ACK event type) whereas the trigger event A01 can be associated with both ADT and ACK event type.[2,3]
> 
> [1]http://www.hl7.org/special/committees/vocab/v26_appendix_a.pdf
> 
> [1]0003 A01 ADT/ACK - Admit/visit notification 
> [2]0003 R22 OUL - Unsolicited Specimen Oriented Observation Message
> 
> Does this help you?
> 
> Thanks
> -Ratha
> 
> 
> On 13 June 2013 01:40, James Agnew <ja...@ja...> wrote:
> Hi Ratha,
> 
> While the HL7 standard doesn't seem to specifically mention whether or not the response for an OUL^R22 should have the R22 trigger event in it's ACK, the general pattern in processing HL7 v2 is that the trigger event will always be the same as the message being acknowledged. A quick scan of the standard for words to that effect has come up blank (but maybe I'm not looking in the right place- I checked Chapter 2 of the 2.6 standard at least) but this is definitely how basically every system I work with regularly behaves.
> 
> What leads you to believe this is not desirable behaviour? Are you interfacing with a system that specifically rejects ACK messages with the R22 trigger?
> 
> Cheers,
> James
> 
> 
> On Wed, Jun 12, 2013 at 11:34 AM, vijayaratha vijayasingam <vij...@gm...> wrote:
> Oh..hapi generates this ack message, when i send OUL^R22 message..
> Others any clue?..
> Is this valid or bug?
> 
> 
> On 12 June 2013 20:22, VIOT Yves <yve...@cs...> wrote:
> Sorry, i never had to handle such triggers, but if i had to, i will produce an ACK - unless the sender doesn't need them. 
> In specs, there is no ACK^R22 following de OUL^R22 definition but i can't say it's a mistake or not.
> 
> Le 12/06/2013 16:46, vijayaratha vijayasingam a écrit :
>> Hi Viot;
>> Sorry i sent different initial sample message ;Please check my later replies;
>> Im getting following[1] ACK in  MSH-9 filde fro my OUL^R22 message. Is that valid?
>> ACK^R22^ACK|
>> 
>> Thanks
>> 
>> 
>> On 12 June 2013 17:11, VIOT Yves <yve...@cs...> wrote:
>> Hi,
>> This is valid
>> Here is what you can find in the HL7 2.5 documentation, following the ADT^A01^ADT_A01 messages structure definition.
>> ACK^A01^ACK
>> To get rid of it just get the MSH-9-1 with the terser.
>> 
>> Yves
>> 
>> Le 12/06/2013 13:25, vijayaratha vijayasingam a écrit :
>>> Hi all;
>>> Anyone have clue..?:( 
>>> I badly need this to sort out..
>>> thanks
>>> 
>>> 
>>> On 12 June 2013 15:31, vijayaratha vijayasingam <vij...@gm...> wrote:
>>> Hi all;
>>> Im using Hapi 2.1 version release an dit works perfect. But i have an issue with an error response which i get from Hapi.
>>> My request is;
>>> MSH|^~\&|||||20130612143324.392+0530||ADT^A01^ADT_A01|2601|T|2.5
>>> 
>>> And My response is;
>>> MSH|^~\&|||||20130612152510.448+0530||ACK^A01^ACK|1623|T|2.5
>>> MSA|AE|2601
>>> ERR|||207^Application internal error^HL70357^^^^^^OOPS|E
>>> 
>>> 
>>> In the above response , if you check the MSH-9 filed , it is;
>>> 
>>> ACK^A01^ACK
>>> 
>>> Shouldn't that be "|ACK". because it is additionaly adding "AO1" message to that filed, which is not valid. And i suspect that , it picks from that from original request.
>>> 
>>> Can anybody help me on this? Ho w can i avoid that invalid segment?
>>> Why Hapi additionally adds that filed in the MSH-9 filed?
>>> 
>>> Thanks
>>> -ratha
>>> 
>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by Windows:
>>> 
>>> Build for Windows Store.
>>> 
>>> 
>>> http://p.sf.net/sfu/windows-dev2dev
>>> 
>>> 
>>> _______________________________________________
>>> Hl7api-devel mailing list
>>> 
>>> Hl7...@li...
>>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> 
>> 
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>> 
>> Build for Windows Store.
>> 
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> Hl7api-devel mailing list
>> Hl7...@li...
>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>> 
>> 
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> 
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev_______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel

Re: [HAPI-devel] Hapi 2.1 version's MSH-9 filed concerns

[vijayaratha v. <vij...@gm...>]

Thanks a lot James..Please find my comments inline..



On 14 June 2013 17:15, James Agnew <ja...@ja...> wrote:

> Hi Ratha,
>
> To be completely honest, I have no idea what the right answer is to this.
> Certainly you are right, the standard seems to indicate that the R22
> trigger is not allowable in an ACK message, but the standard also doesn't
> seem to provide any indication on what would be an appropriate trigger for
> an ACK to an OUL^R22 message.
>
> I think there are a few courses of action here:
>
> 1. It might make sense to take the question of "what belongs as a trigger
> event on an ACK to an OUL^R22 message" over to the HL7 Infrastructure and
> Messaging (InM) mailing list for broader consideration. I'm curious now
> too, so if you didn't want to handle this I would be willing to do so.
>
> I would like you to discuss this in that mailing list, since i'm a newbie
to this area and if they ask more, i'll be in trouble:(


> 2. If you wanted to file a bug report for HAPI, we could probably code in
> the ability for HAPI to not use a trigger event for ACKs to messages that
> shouldn't get one according to Table 0003. I'll be honest though, this will
> be somewhat painful to implement so it probably won't happen overnight
> (unless you or someone else wanted to give it a shot?)
>

I'll keep holding this, once i got to know clearly whether it is a bug in
Hapi or not, after your discussion at H L7 Infrastructure and Messaging
(InM) mailing list. I believe that you will reply about your decision in
this mailing list.

"unless you or someone else wanted to give it a shot?"
I never went through the Hapi code.We here(in WSO2ESB) use Hapi library to
provide our HL7 adapter feature. So, i'm learning from you all.
Thanks all for helping me..


> 3. As a fairly simple workaround, you could add custom logic to your
> application to clear MSH-9-2 as needed after you generate your ACK message.
>

In a worst case, i'll try to add this from our end ..

>
> Cheers,
> James
>
>
>
>
> On Fri, Jun 14, 2013 at 3:18 AM, vijayaratha vijayasingam <
> vij...@gm...> wrote:
>
>> Hi James/all;
>>
>> Do you believe this as a BUG in Hapi or acceptable behavior?
>>
>> Thanks
>>
>>
>>
>> On 13 June 2013 14:45, vijayaratha vijayasingam <vij...@gm...>wrote:
>>
>>> Hi James;
>>> Thanks for considering this.
>>> Please find the following HL7 Data definition tables [1] .In   table
>>> 0003 (page A-25) . The trigger event R22 can be associated only with the
>>> OUL event type (but NOT with an ACK event type) whereas the trigger event
>>> A01 can be associated with both ADT and ACK event type.[2,3]
>>>
>>> [1]http://www.hl7.org/special/committees/vocab/v26_appendix_a.pdf
>>>
>>> [1]0003 A01 ADT/ACK - Admit/visit notification
>>> [2]0003 R22 OUL - Unsolicited Specimen Oriented Observation Message
>>>
>>> Does this help you?
>>>
>>> Thanks
>>> -Ratha
>>>
>>>
>>> On 13 June 2013 01:40, James Agnew <ja...@ja...> wrote:
>>>
>>>> Hi Ratha,
>>>>
>>>> While the HL7 standard doesn't seem to specifically mention whether or
>>>> not the response for an OUL^R22 should have the R22 trigger event in it's
>>>> ACK, the general pattern in processing HL7 v2 is that the trigger event
>>>> will always be the same as the message being acknowledged. A quick scan of
>>>> the standard for words to that effect has come up blank (but maybe I'm not
>>>> looking in the right place- I checked Chapter 2 of the 2.6 standard at
>>>> least) but this is definitely how basically every system I work with
>>>> regularly behaves.
>>>>
>>>> What leads you to believe this is not desirable behaviour? Are you
>>>> interfacing with a system that specifically rejects ACK messages with the
>>>> R22 trigger?
>>>>
>>>> Cheers,
>>>> James
>>>>
>>>>
>>>> On Wed, Jun 12, 2013 at 11:34 AM, vijayaratha vijayasingam <
>>>> vij...@gm...> wrote:
>>>>
>>>>> Oh..hapi generates this ack message, when i send OUL^R22 message..
>>>>> Others any clue?..
>>>>> Is this valid or bug?
>>>>>
>>>>>
>>>>> On 12 June 2013 20:22, VIOT Yves <yve...@cs...> wrote:
>>>>>
>>>>>>  Sorry, i never had to handle such triggers, but if i had to, i will
>>>>>> produce an ACK - unless the sender doesn't need them.
>>>>>> In specs, there is no ACK^R22 following de OUL^R22 definition but i
>>>>>> can't say it's a mistake or not.
>>>>>>
>>>>>> Le 12/06/2013 16:46, vijayaratha vijayasingam a écrit :
>>>>>>
>>>>>> Hi Viot;
>>>>>> Sorry i sent different initial sample message ;Please check my later
>>>>>> replies;
>>>>>> Im getting following[1] ACK in  MSH-9 filde fro my OUL^R22 message.
>>>>>> Is that valid?
>>>>>>  *ACK^R22^ACK|*
>>>>>>  *
>>>>>> *
>>>>>> Thanks
>>>>>>
>>>>>>
>>>>>> On 12 June 2013 17:11, VIOT Yves <yve...@cs...> wrote:
>>>>>>
>>>>>>>  Hi,
>>>>>>> This is valid
>>>>>>> Here is what you can find in the HL7 2.5 documentation, following
>>>>>>> the ADT^A01^ADT_A01 messages structure definition.
>>>>>>> ACK^A01^ACK
>>>>>>> To get rid of it just get the MSH-9-1 with the terser.
>>>>>>>
>>>>>>> Yves
>>>>>>>
>>>>>>>  Le 12/06/2013 13:25, vijayaratha vijayasingam a écrit :
>>>>>>>
>>>>>>>  Hi all;
>>>>>>> Anyone have clue..?:(
>>>>>>> I badly need this to sort out..
>>>>>>> thanks
>>>>>>>
>>>>>>>
>>>>>>> On 12 June 2013 15:31, vijayaratha vijayasingam <
>>>>>>> vij...@gm...> wrote:
>>>>>>>
>>>>>>>> Hi all;
>>>>>>>> Im using Hapi 2.1 version release an dit works perfect. But i have
>>>>>>>> an issue with an error response which i get from Hapi.
>>>>>>>> My request is;
>>>>>>>> MSH|^~\&|||||20130612143324.392+0530||ADT^A01^ADT_A01|2601|T|2.5
>>>>>>>>
>>>>>>>>  And My response is;
>>>>>>>>  MSH|^~\&|||||20130612152510.448+0530||ACK^A01^ACK|1623|T|2.5
>>>>>>>> MSA|AE|2601
>>>>>>>> ERR|||207^Application internal error^HL70357^^^^^^OOPS|E
>>>>>>>>
>>>>>>>>
>>>>>>>>  In the above response , if you check the MSH-9 filed , it is;
>>>>>>>>
>>>>>>>>  *ACK^A01^ACK
>>>>>>>> *
>>>>>>>>
>>>>>>>>  Shouldn't that be "|ACK". because it is additionaly adding "*AO1*" message to
>>>>>>>> that filed, which is not valid. And i suspect that , it picks from that
>>>>>>>> from original request.
>>>>>>>>
>>>>>>>>  Can anybody help me on this? Ho w can i avoid that invalid
>>>>>>>> segment?
>>>>>>>> Why Hapi additionally adds that filed in the MSH-9 filed?
>>>>>>>>
>>>>>>>>  Thanks
>>>>>>>> -ratha
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>   ------------------------------------------------------------------------------
>>>>>>> This SF.net email is sponsored by Windows:
>>>>>>>
>>>>>>> Build for Windows Store.
>>>>>>> http://p.sf.net/sfu/windows-dev2dev
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Hl7api-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> This SF.net email is sponsored by Windows:
>>>>>>>
>>>>>>> Build for Windows Store.
>>>>>>>
>>>>>>> http://p.sf.net/sfu/windows-dev2dev
>>>>>>> _______________________________________________
>>>>>>> Hl7api-devel mailing list
>>>>>>> Hl7...@li...
>>>>>>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> This SF.net email is sponsored by Windows:
>>>>>>
>>>>>> Build for Windows Store.
>>>>>>
>>>>>> http://p.sf.net/sfu/windows-dev2dev
>>>>>> _______________________________________________
>>>>>> Hl7api-devel mailing list
>>>>>> Hl7...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> This SF.net email is sponsored by Windows:
>>>>>
>>>>> Build for Windows Store.
>>>>>
>>>>> http://p.sf.net/sfu/windows-dev2dev
>>>>> _______________________________________________
>>>>> Hl7api-devel mailing list
>>>>> Hl7...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>>>>
>>>>>
>>>>
>>>
>>
>

Re: [HAPI-devel] Message profile, DefaultRuleBuilder and ValidationExceptions by field repeation

[James A. <ja...@ja...>]

Hi Brennan,

Any chance you could extract the issue into a code snippet and/or simple
demo project that shows the issue?

Cheers,
James


On Thu, Jun 13, 2013 at 10:42 AM, Brennan O'Banion <
bre...@gm...> wrote:

> I'm attempting to validate an HL7 message against a message profile.
> The profile was created using MWB, used to configure an instance of
> DefaultValidationWithoutTNBuilder and it works as expected.  The issue
> i'm encountering is that when implementations exclude the first
> occurrence of PID-5 in lieu of a second instance (~^^^^^^NameTypeCode)
> I get a validation exception.  It appears there is a way around this
> issue, since I validated the same message against the same profile
> using TestPanel and did not get the validation error.  How should I
> proceed to permit the absence of the first instance of patient name?
>
> Thanks,
> Brennan
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>

Re: [HAPI-devel] Hapi 2.1 version's MSH-9 filed concerns

[James A. <ja...@ja...>]

Hi Ratha,

To be completely honest, I have no idea what the right answer is to this.
Certainly you are right, the standard seems to indicate that the R22
trigger is not allowable in an ACK message, but the standard also doesn't
seem to provide any indication on what would be an appropriate trigger for
an ACK to an OUL^R22 message.

I think there are a few courses of action here:

1. It might make sense to take the question of "what belongs as a trigger
event on an ACK to an OUL^R22 message" over to the HL7 Infrastructure and
Messaging (InM) mailing list for broader consideration. I'm curious now
too, so if you didn't want to handle this I would be willing to do so.

2. If you wanted to file a bug report for HAPI, we could probably code in
the ability for HAPI to not use a trigger event for ACKs to messages that
shouldn't get one according to Table 0003. I'll be honest though, this will
be somewhat painful to implement so it probably won't happen overnight
(unless you or someone else wanted to give it a shot?)

3. As a fairly simple workaround, you could add custom logic to your
application to clear MSH-9-2 as needed after you generate your ACK message.

Cheers,
James




On Fri, Jun 14, 2013 at 3:18 AM, vijayaratha vijayasingam <
vij...@gm...> wrote:

> Hi James/all;
>
> Do you believe this as a BUG in Hapi or acceptable behavior?
>
> Thanks
>
>
>
> On 13 June 2013 14:45, vijayaratha vijayasingam <vij...@gm...>wrote:
>
>> Hi James;
>> Thanks for considering this.
>> Please find the following HL7 Data definition tables [1] .In   table 0003
>> (page A-25) . The trigger event R22 can be associated only with the OUL
>> event type (but NOT with an ACK event type) whereas the trigger event A01
>> can be associated with both ADT and ACK event type.[2,3]
>>
>> [1]http://www.hl7.org/special/committees/vocab/v26_appendix_a.pdf
>>
>> [1]0003 A01 ADT/ACK - Admit/visit notification
>> [2]0003 R22 OUL - Unsolicited Specimen Oriented Observation Message
>>
>> Does this help you?
>>
>> Thanks
>> -Ratha
>>
>>
>> On 13 June 2013 01:40, James Agnew <ja...@ja...> wrote:
>>
>>> Hi Ratha,
>>>
>>> While the HL7 standard doesn't seem to specifically mention whether or
>>> not the response for an OUL^R22 should have the R22 trigger event in it's
>>> ACK, the general pattern in processing HL7 v2 is that the trigger event
>>> will always be the same as the message being acknowledged. A quick scan of
>>> the standard for words to that effect has come up blank (but maybe I'm not
>>> looking in the right place- I checked Chapter 2 of the 2.6 standard at
>>> least) but this is definitely how basically every system I work with
>>> regularly behaves.
>>>
>>> What leads you to believe this is not desirable behaviour? Are you
>>> interfacing with a system that specifically rejects ACK messages with the
>>> R22 trigger?
>>>
>>> Cheers,
>>> James
>>>
>>>
>>> On Wed, Jun 12, 2013 at 11:34 AM, vijayaratha vijayasingam <
>>> vij...@gm...> wrote:
>>>
>>>> Oh..hapi generates this ack message, when i send OUL^R22 message..
>>>> Others any clue?..
>>>> Is this valid or bug?
>>>>
>>>>
>>>> On 12 June 2013 20:22, VIOT Yves <yve...@cs...> wrote:
>>>>
>>>>>  Sorry, i never had to handle such triggers, but if i had to, i will
>>>>> produce an ACK - unless the sender doesn't need them.
>>>>> In specs, there is no ACK^R22 following de OUL^R22 definition but i
>>>>> can't say it's a mistake or not.
>>>>>
>>>>> Le 12/06/2013 16:46, vijayaratha vijayasingam a écrit :
>>>>>
>>>>> Hi Viot;
>>>>> Sorry i sent different initial sample message ;Please check my later
>>>>> replies;
>>>>> Im getting following[1] ACK in  MSH-9 filde fro my OUL^R22 message. Is
>>>>> that valid?
>>>>>  *ACK^R22^ACK|*
>>>>>  *
>>>>> *
>>>>> Thanks
>>>>>
>>>>>
>>>>> On 12 June 2013 17:11, VIOT Yves <yve...@cs...> wrote:
>>>>>
>>>>>>  Hi,
>>>>>> This is valid
>>>>>> Here is what you can find in the HL7 2.5 documentation, following the
>>>>>> ADT^A01^ADT_A01 messages structure definition.
>>>>>> ACK^A01^ACK
>>>>>> To get rid of it just get the MSH-9-1 with the terser.
>>>>>>
>>>>>> Yves
>>>>>>
>>>>>>  Le 12/06/2013 13:25, vijayaratha vijayasingam a écrit :
>>>>>>
>>>>>>  Hi all;
>>>>>> Anyone have clue..?:(
>>>>>> I badly need this to sort out..
>>>>>> thanks
>>>>>>
>>>>>>
>>>>>> On 12 June 2013 15:31, vijayaratha vijayasingam <
>>>>>> vij...@gm...> wrote:
>>>>>>
>>>>>>> Hi all;
>>>>>>> Im using Hapi 2.1 version release an dit works perfect. But i have
>>>>>>> an issue with an error response which i get from Hapi.
>>>>>>> My request is;
>>>>>>> MSH|^~\&|||||20130612143324.392+0530||ADT^A01^ADT_A01|2601|T|2.5
>>>>>>>
>>>>>>>  And My response is;
>>>>>>>  MSH|^~\&|||||20130612152510.448+0530||ACK^A01^ACK|1623|T|2.5
>>>>>>> MSA|AE|2601
>>>>>>> ERR|||207^Application internal error^HL70357^^^^^^OOPS|E
>>>>>>>
>>>>>>>
>>>>>>>  In the above response , if you check the MSH-9 filed , it is;
>>>>>>>
>>>>>>>  *ACK^A01^ACK
>>>>>>> *
>>>>>>>
>>>>>>>  Shouldn't that be "|ACK". because it is additionaly adding "*AO1*" message to
>>>>>>> that filed, which is not valid. And i suspect that , it picks from that
>>>>>>> from original request.
>>>>>>>
>>>>>>>  Can anybody help me on this? Ho w can i avoid that invalid segment?
>>>>>>> Why Hapi additionally adds that filed in the MSH-9 filed?
>>>>>>>
>>>>>>>  Thanks
>>>>>>> -ratha
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>   ------------------------------------------------------------------------------
>>>>>> This SF.net email is sponsored by Windows:
>>>>>>
>>>>>> Build for Windows Store.
>>>>>> http://p.sf.net/sfu/windows-dev2dev
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Hl7api-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> This SF.net email is sponsored by Windows:
>>>>>>
>>>>>> Build for Windows Store.
>>>>>>
>>>>>> http://p.sf.net/sfu/windows-dev2dev
>>>>>> _______________________________________________
>>>>>> Hl7api-devel mailing list
>>>>>> Hl7...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> This SF.net email is sponsored by Windows:
>>>>>
>>>>> Build for Windows Store.
>>>>>
>>>>> http://p.sf.net/sfu/windows-dev2dev
>>>>> _______________________________________________
>>>>> Hl7api-devel mailing list
>>>>> Hl7...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>>>>
>>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> This SF.net email is sponsored by Windows:
>>>>
>>>> Build for Windows Store.
>>>>
>>>> http://p.sf.net/sfu/windows-dev2dev
>>>> _______________________________________________
>>>> Hl7api-devel mailing list
>>>> Hl7...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>>>
>>>>
>>>
>>
>

Re: [HAPI-devel] Hapi 2.1 version's MSH-9 filed concerns

[vijayaratha v. <vij...@gm...>]

Hi james;
The tool complains about the above invalid ACK message is, "*7edit *"[1]

[1]http://www.7edit.com/home/index.php

Thanks& regards
-Ratha


On 14 June 2013 12:48, vijayaratha vijayasingam <vij...@gm...>wrote:

> Hi James/all;
>
> Do you believe this as a BUG in Hapi or acceptable behavior?
>
> Thanks
>
>
>
> On 13 June 2013 14:45, vijayaratha vijayasingam <vij...@gm...>wrote:
>
>> Hi James;
>> Thanks for considering this.
>> Please find the following HL7 Data definition tables [1] .In   table 0003
>> (page A-25) . The trigger event R22 can be associated only with the OUL
>> event type (but NOT with an ACK event type) whereas the trigger event A01
>> can be associated with both ADT and ACK event type.[2,3]
>>
>> [1]http://www.hl7.org/special/committees/vocab/v26_appendix_a.pdf
>>
>> [1]0003 A01 ADT/ACK - Admit/visit notification
>> [2]0003 R22 OUL - Unsolicited Specimen Oriented Observation Message
>>
>> Does this help you?
>>
>> Thanks
>> -Ratha
>>
>>
>> On 13 June 2013 01:40, James Agnew <ja...@ja...> wrote:
>>
>>> Hi Ratha,
>>>
>>> While the HL7 standard doesn't seem to specifically mention whether or
>>> not the response for an OUL^R22 should have the R22 trigger event in it's
>>> ACK, the general pattern in processing HL7 v2 is that the trigger event
>>> will always be the same as the message being acknowledged. A quick scan of
>>> the standard for words to that effect has come up blank (but maybe I'm not
>>> looking in the right place- I checked Chapter 2 of the 2.6 standard at
>>> least) but this is definitely how basically every system I work with
>>> regularly behaves.
>>>
>>> What leads you to believe this is not desirable behaviour? Are you
>>> interfacing with a system that specifically rejects ACK messages with the
>>> R22 trigger?
>>>
>>> Cheers,
>>> James
>>>
>>>
>>> On Wed, Jun 12, 2013 at 11:34 AM, vijayaratha vijayasingam <
>>> vij...@gm...> wrote:
>>>
>>>> Oh..hapi generates this ack message, when i send OUL^R22 message..
>>>> Others any clue?..
>>>> Is this valid or bug?
>>>>
>>>>
>>>> On 12 June 2013 20:22, VIOT Yves <yve...@cs...> wrote:
>>>>
>>>>>  Sorry, i never had to handle such triggers, but if i had to, i will
>>>>> produce an ACK - unless the sender doesn't need them.
>>>>> In specs, there is no ACK^R22 following de OUL^R22 definition but i
>>>>> can't say it's a mistake or not.
>>>>>
>>>>> Le 12/06/2013 16:46, vijayaratha vijayasingam a écrit :
>>>>>
>>>>> Hi Viot;
>>>>> Sorry i sent different initial sample message ;Please check my later
>>>>> replies;
>>>>> Im getting following[1] ACK in  MSH-9 filde fro my OUL^R22 message. Is
>>>>> that valid?
>>>>>  *ACK^R22^ACK|*
>>>>>  *
>>>>> *
>>>>> Thanks
>>>>>
>>>>>
>>>>> On 12 June 2013 17:11, VIOT Yves <yve...@cs...> wrote:
>>>>>
>>>>>>  Hi,
>>>>>> This is valid
>>>>>> Here is what you can find in the HL7 2.5 documentation, following the
>>>>>> ADT^A01^ADT_A01 messages structure definition.
>>>>>> ACK^A01^ACK
>>>>>> To get rid of it just get the MSH-9-1 with the terser.
>>>>>>
>>>>>> Yves
>>>>>>
>>>>>>  Le 12/06/2013 13:25, vijayaratha vijayasingam a écrit :
>>>>>>
>>>>>>  Hi all;
>>>>>> Anyone have clue..?:(
>>>>>> I badly need this to sort out..
>>>>>> thanks
>>>>>>
>>>>>>
>>>>>> On 12 June 2013 15:31, vijayaratha vijayasingam <
>>>>>> vij...@gm...> wrote:
>>>>>>
>>>>>>> Hi all;
>>>>>>> Im using Hapi 2.1 version release an dit works perfect. But i have
>>>>>>> an issue with an error response which i get from Hapi.
>>>>>>> My request is;
>>>>>>> MSH|^~\&|||||20130612143324.392+0530||ADT^A01^ADT_A01|2601|T|2.5
>>>>>>>
>>>>>>>  And My response is;
>>>>>>>  MSH|^~\&|||||20130612152510.448+0530||ACK^A01^ACK|1623|T|2.5
>>>>>>> MSA|AE|2601
>>>>>>> ERR|||207^Application internal error^HL70357^^^^^^OOPS|E
>>>>>>>
>>>>>>>
>>>>>>>  In the above response , if you check the MSH-9 filed , it is;
>>>>>>>
>>>>>>>  *ACK^A01^ACK
>>>>>>> *
>>>>>>>
>>>>>>>  Shouldn't that be "|ACK". because it is additionaly adding "*AO1*" message to
>>>>>>> that filed, which is not valid. And i suspect that , it picks from that
>>>>>>> from original request.
>>>>>>>
>>>>>>>  Can anybody help me on this? Ho w can i avoid that invalid segment?
>>>>>>> Why Hapi additionally adds that filed in the MSH-9 filed?
>>>>>>>
>>>>>>>  Thanks
>>>>>>> -ratha
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>   ------------------------------------------------------------------------------
>>>>>> This SF.net email is sponsored by Windows:
>>>>>>
>>>>>> Build for Windows Store.
>>>>>> http://p.sf.net/sfu/windows-dev2dev
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Hl7api-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> This SF.net email is sponsored by Windows:
>>>>>>
>>>>>> Build for Windows Store.
>>>>>>
>>>>>> http://p.sf.net/sfu/windows-dev2dev
>>>>>> _______________________________________________
>>>>>> Hl7api-devel mailing list
>>>>>> Hl7...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> This SF.net email is sponsored by Windows:
>>>>>
>>>>> Build for Windows Store.
>>>>>
>>>>> http://p.sf.net/sfu/windows-dev2dev
>>>>> _______________________________________________
>>>>> Hl7api-devel mailing list
>>>>> Hl7...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>>>>
>>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> This SF.net email is sponsored by Windows:
>>>>
>>>> Build for Windows Store.
>>>>
>>>> http://p.sf.net/sfu/windows-dev2dev
>>>> _______________________________________________
>>>> Hl7api-devel mailing list
>>>> Hl7...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>>>>
>>>>
>>>
>>
>