Thread: [HAPI-devel] How to change default encoding characters (separators)?

Brought to you by: bryan_tripp, jamesagnew, ohr

hl7api-devel

[HAPI-devel] How to change default encoding characters (separators)?

From: Steve P. <st...@pr...> - 2006-01-05 19:47:02

I'm getting HL7 messages from a client that have non-default separators.
How can I set the parser to use the appropriate separators?
 
It looks like the EncodingCharacters class might be useful, but it's not
clear how to tie the EncodingCharacters object to a *Parser object, such as
PipeParser.
 
thanks,
Steve Pringle

Re: [HAPI-devel] How to change default encoding characters (separators)?

From: Bryan T. <bp...@gm...> - 2006-01-05 20:57:06

Hi Steve,

The parser should do this automatically, as long as they are declared
correctly in MSH-1 and MSH-2.

Bryan

On 1/5/06, Steve Pringle <st...@pr...> wrote:
> I'm getting HL7 messages from a client that have non-default separators.
> How can I set the parser to use the appropriate separators?
>
> It looks like the EncodingCharacters class might be useful, but it's not
> clear how to tie the EncodingCharacters object to a *Parser object, such =
as
> PipeParser.
>
> thanks,
> Steve Pringle

RE: [HAPI-devel] How to change default encoding characters (separators)?

From: Steve P. <st...@pr...> - 2006-01-05 22:17:48

Indeed it does!  Very exciting! =20

Next I'm going to try to register an application with a SimpleServer and
send messages to the SimpleServer via the TestPanel.

Thanks,
Steve

> -----Original Message-----
> From: hl7...@li...=20
> [mailto:hl7...@li...] On Behalf=20
> Of Bryan Tripp
> Sent: Thursday, January 05, 2006 12:57 PM
> To: spr...@po...
> Cc: hl7...@li...
> Subject: Re: [HAPI-devel] How to change default encoding=20
> characters (separators)?
>=20
>=20
> Hi Steve,
>=20
> The parser should do this automatically, as long as they are=20
> declared correctly in MSH-1 and MSH-2.
>=20
> Bryan
>=20
> On 1/5/06, Steve Pringle <st...@pr...> wrote:
> > I'm getting HL7 messages from a client that have non-default=20
> > separators. How can I set the parser to use the appropriate=20
> > separators?
> >
> > It looks like the EncodingCharacters class might be useful,=20
> but it's=20
> > not clear how to tie the EncodingCharacters object to a *Parser=20
> > object, such as PipeParser.
> >
> > thanks,
> > Steve Pringle
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep=20
> through log files for problems?  Stop!  Download the new AJAX=20
> search engine that makes searching your log files as easy as=20
> surfing the  web.  DOWNLOAD SPLUNK!=20
> http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=CCk
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>=20
>=20

[HAPI-devel] Detemining the Message type in Application.processMessage(...)

From: Steve P. <st...@pr...> - 2006-01-09 07:27:16

Could someone please tell me how one goes about determining what type of
message has been received in the Application.processMessage(Message in)
method?

Here's a code snippet, which is being sent an ADT_A01 msg, but I have no
idea how to determine that it is an ADT_A01.  All I want to do is determine
which message type was sent, get the data I need, then send an ACK.  

public class ABApplication implements Application
{
...
    public Message processMessage(Message in) throws ApplicationException
	{
        Message out = null;
		PipeParser parser =  new PipeParser();

        try
		{
			System.out.println("\nmsg Name: " + in.getName());
			System.out.println("\nmsg Name: " +
in.getClass().getName());
			System.out.println("\nmsg Version: " +
in.getVersion());
			System.out.println("\nmsg ?: " +
in.get("MSH").getName());

			String[] names = in.getNames();

			for (int i = 0; i < names.length; i++)
				System.out.println("** " + names[i]);
...

Here's the output:

msg Name: GenericMessage$V22

msg Name: ca.uhn.hl7v2.model.GenericMessage$V22

msg Version: 2.2

msg ?: MSH
** MSH
** EVN
** PID
** NK1
** PV1

Thanks,
Steve PRingle

Re: [HAPI-devel] Detemining the Message type in Application.processMessage(...)

From: Bryan T. <bp...@gm...> - 2006-01-10 21:26:46

Hi Steve,

The message type, event, and possibly structure should be in field
MSH-9. Actually if they are there, HAPI should not use the
GenericMessage class, and you should be able to tell what kind of
message it is from the class. Maybe these data are missing from the
message?

Bryan

On 1/9/06, Steve Pringle <st...@pr...> wrote:
> Could someone please tell me how one goes about determining what type of
> message has been received in the Application.processMessage(Message in)
> method?
>
> Here's a code snippet, which is being sent an ADT_A01 msg, but I have no
> idea how to determine that it is an ADT_A01.  All I want to do is determi=
ne
> which message type was sent, get the data I need, then send an ACK.
>
> public class ABApplication implements Application
> {
> ...
>    public Message processMessage(Message in) throws ApplicationException
>        {
>        Message out =3D null;
>                PipeParser parser =3D  new PipeParser();
>
>        try
>                {
>                        System.out.println("\nmsg Name: " + in.getName());
>                        System.out.println("\nmsg Name: " +
> in.getClass().getName());
>                        System.out.println("\nmsg Version: " +
> in.getVersion());
>                        System.out.println("\nmsg ?: " +
> in.get("MSH").getName());
>
>                        String[] names =3D in.getNames();
>
>                        for (int i =3D 0; i < names.length; i++)
>                                System.out.println("** " + names[i]);
> ...
>
> Here's the output:
>
> msg Name: GenericMessage$V22
>
> msg Name: ca.uhn.hl7v2.model.GenericMessage$V22
>
> msg Version: 2.2
>
> msg ?: MSH
> ** MSH
> ** EVN
> ** PID
> ** NK1
> ** PV1
>
> Thanks,
> Steve PRingle
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>