hl7api-devel — developer list

RE: [HAPI-devel] International Phone Numbers

[Kenneth B. <Ken...@ka...>]

Peter,

I plan to avoid this problem by using the fields at the end of the XTN data
type.

eg
PID|||MR1^^^XYZ||BEATON^KENNETH||19661121|M|||||^WPN^PH^^61^02^62016842|||S|
|ACCT1

This is the recommended usage for version 2.3 onwards.

Kenneth Beaton

-----Original Message-----
From: Kelley, Peter (DHS)
To: 'hl7...@li...'
Sent: 23/02/04 14:04
Subject: [HAPI-devel] International Phone Numbers

Hi,
 
I was wondering if there was a possibility of making the exception
messages that get thrown when parsing a phone number in CommonTN.java
warning level ? Australian phone numbers don't conform to the format
specified as it is US centric. It would have been better if the
standards committee specified the international format
(+countrycode-areacode-number) but unfortunately that won't change for
HL7 2.3.1 which is what we use.
 
Peter Kelley 


************************************************************************
MIMEsweeper has been used to check this email for security
************************************************************************

[HAPI-devel] International Phone Numbers

[Kelley, P. (DHS) <pet...@dh...>]

Hi,
 
I was wondering if there was a possibility of making the exception messages
that get thrown when parsing a phone number in CommonTN.java warning level ?
Australian phone numbers don't conform to the format specified as it is US
centric. It would have been better if the standards committee specified the
international format (+countrycode-areacode-number) but unfortunately that
won't change for HL7 2.3.1 which is what we use.
 
Peter Kelley 

[HAPI-devel] HAPI 0.4.1

[Tripp, B. <Bry...@uh...>]

HAPI 0.4.1 is ready for download here:=20

http://sourceforge.net/project/showfiles.php?group_id=3D38899&package_id=
=3D31129
&release_id=3D217763

This is purely a maintenance release.  As you may be aware, there was =
one
substantial bug in version 0.4, in that ER7 message values were not =
being
unescaped when the messages were parsed.  Thanks to Fr=E9d=E9ric Dubru =
for being
the first to point this out.  0.4.1 fixes this and several less serious
bugs.  Please let me know as soon as possible if you find any problems =
with
this release. =20

I will send another mail in a week or two regarding plans for 0.4.2. =20

Regards,=20
Bryan=20


This e-mail may contain confidential and/or privileged information
for the sole use of the intended recipient. Any review or distribution
by anyone other than the person for whom it was originally intended is
strictly
prohibited. If you have received this e-mail in error, please contact =
the
sender and
delete all copies. Opinions, conclusions or other information contained =
in
this e-mail may not be that of the organization.

RE: [HAPI-devel] Question

[Tripp, B. <Bry...@uh...>]

Hi Gautam, 

You have to run it under Java 1.4 or higher.  If there is some reason you
can't do that please let me know.  

Bryan 

> -----Original Message-----
> From: Dev, Gautam (EDS) [mailto:Gau...@me...]
> Sent: February 4, 2004 6:05 PM
> To: 'hl7...@li...'
> Subject: [HAPI-devel] Question
> 
> 
> Hi,
> 
> Is the documentation available for the HAPI 4.0? I tried to run the
> testpanel.bat, but I got the following 
> error:
> 
> Exception in thread "main" java.lang.UnsupportedClassVersionError:
> ca/uhn/hl7v2/
> app/TestPanel (Unsupported major.minor version 48.0)
>         at java.lang.ClassLoader.defineClass0(Native Method)
>         at java.lang.ClassLoader.defineClass(Unknown Source)
>         at java.security.SecureClassLoader.defineClass(Unknown Source)
>         at java.net.URLClassLoader.defineClass(Unknown Source)
>         at java.net.URLClassLoader.access$100(Unknown Source)
>         at java.net.URLClassLoader$1.run(Unknown Source)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at java.net.URLClassLoader.findClass(Unknown Source)
>         at java.lang.ClassLoader.loadClass(Unknown Source)
>         at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
>         at java.lang.ClassLoader.loadClass(Unknown Source)
>         at java.lang.ClassLoader.loadClassInternal(Unknown Source)
> 
> Please help.
> 
> Gautam Dev
> Health SD&D Representative
> Largo, FL 33771
> 
> * phone: +01-727-399-3383 (8-xxx)
> * mailto:Gau...@me...
> pager: None
> pager mail: None
> 
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> 


This e-mail may contain confidential and/or privileged information
for the sole use of the intended recipient. Any review or distribution
by anyone other than the person for whom it was originally intended is
strictly
prohibited. If you have received this e-mail in error, please contact the
sender and
delete all copies. Opinions, conclusions or other information contained in
this e-mail may not be that of the organization.

[HAPI-devel] Question

[Dev, G. (EDS) <Gau...@me...>]

Hi,

Is the documentation available for the HAPI 4.0? I tried to run the
testpanel.bat, but I got the following 
error:

Exception in thread "main" java.lang.UnsupportedClassVersionError:
ca/uhn/hl7v2/
app/TestPanel (Unsupported major.minor version 48.0)
        at java.lang.ClassLoader.defineClass0(Native Method)
        at java.lang.ClassLoader.defineClass(Unknown Source)
        at java.security.SecureClassLoader.defineClass(Unknown Source)
        at java.net.URLClassLoader.defineClass(Unknown Source)
        at java.net.URLClassLoader.access$100(Unknown Source)
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at java.lang.ClassLoader.loadClassInternal(Unknown Source)

Please help.

Gautam Dev
Health SD&D Representative
Largo, FL 33771

* phone: +01-727-399-3383 (8-xxx)
* mailto:Gau...@me...
pager: None
pager mail: None

[HAPI-devel] (no subject)

[Aaron W. <aa...@ws...>]

On Jan 26, 2004 at 6:23, Bryan Tripp wrote:

 > I'm sorry, there may be a bug fix release within that time frame but 
it
 > won't include 2.5 support.

I am working on a decent project now that will be using HL7 2.5, moving 
to 3.0 in the future.

Any idea as to when 2.5 support will be integrated into HAPI, I'm quite 
happy with what I've gotten out of 2.4 thus far, but will have to look 
for another product if HAPI doesn't support HL7 2.5 when we get to the 
point where we are generating messages for more than just testing to 
make sure I understand the frameworks.

We are supposed to have a pilot in place by 1 March, though we are not 
sure if the consultants doing the development work will be able to keep 
to schedule.

-- 
Aaron Whiteman

Any sufficiently advanced technology is indistinguishable from
magic.  -- Arthur C. Clarke

[HAPI-devel] Small information

[raghavendra s. n. <rag...@re...>]

Hello,=0A  I just needed one small information. Will I be able to generate =
the HL7 messages using the API. I wanted to give as input some values like =
patient first name, last name , middle name and age and then generate a HL7=
 text ADT_A01 message. If possible can you please help me.=0A=0ARegards=0AR=
aghavendra.

RE: [HAPI-devel] about log4j

[Tripp, B. <Bry...@uh...>]

Hi Anibal, 

You also need commons-logging.jar in your classpath.  Actually, in general
it's best to put all the jars in HAPI_HOME/lib in your classpath.  

Bryan  

-----Original Message-----
From: Anibal Constante Brito
To: hl7...@li...
Sent: 27/01/2004 5:59 PM
Subject: [HAPI-devel] about log4j

Hello:
 
I tried to run the example that appear in HAPI Technical Documentation
in Message Parsing Tutoral. The exmple compile and build, but when I run
it this happen:
 
java.lang.NoClassDefFoundError: org/apache/commons/logging/Log
        at java.lang.ClassLoader.defineClass0(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:537)
        at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
        at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
        at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
        at ca.uhn.hl7v2.parser.Parser.<clinit>(Parser.java:52)
        at HAPI.main(HAPI.java:13)
Exception in thread "main" 

I think that the problem was the log4j and trying to copy the
log4j-1.2.8.jar to /ext folder, and /lib folder of jre. Beside copy to
/bin folder of jsdk. But not tired I copy the example in the same folder
at testpanel without any result.
 
Please if any body can help a pleasure very much.
Anibal.


This e-mail may contain confidential and/or privileged information
for the sole use of the intended recipient. Any review or distribution
by anyone other than the person for whom it was originally intended is
strictly
prohibited. If you have received this e-mail in error, please contact the
sender and
delete all copies. Opinions, conclusions or other information contained in
this e-mail may not be that of the organization.

[HAPI-devel] about log4j

[Anibal C. B. <an...@kr...>]

Hello:

I tried to run the example that appear in HAPI Technical Documentation =
in Message Parsing Tutoral. The exmple compile and build, but when I run =
it this happen:

java.lang.NoClassDefFoundError: org/apache/commons/logging/Log
        at java.lang.ClassLoader.defineClass0(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:537)
        at =
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
        at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
        at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
        at ca.uhn.hl7v2.parser.Parser.<clinit>(Parser.java:52)
        at HAPI.main(HAPI.java:13)
Exception in thread "main" =03

I think that the problem was the log4j and trying to copy the =
log4j-1.2.8.jar to /ext folder, and /lib folder of jre. Beside copy to =
/bin folder of jsdk. But not tired I copy the example in the same folder =
at testpanel without any result.

Please if any body can help a pleasure very much.
Anibal.

RE: [HAPI-devel] HL7 2.5

[Tripp, B. <Bry...@uh...>]

Hi Giovanni, 

I'm sorry, there may be a bug fix release within that time frame but it
won't include 2.5 support.  

Bryan  

> -----Original Message-----
> From: Giovanni Grimoldi [mailto:g.g...@me...]
> Sent: January 26, 2004 7:59 AM
> To: hl7...@li...
> Subject: [HAPI-devel] HL7 2.5
> 
> 
> 
> Hallo.
> 
> I used HAPI last year for a project which involved HL7 2.3.1 
> version messages.
> Now I have to upgrade it to HL7 2.5 compliance level.
> 
> I saw that HAPI last version supports HL7 2.4 specification.
> 
> I need to know (asap) if you are planning soon (next 15 days) such a 
> release or if it isn't in your to do list,yet.
> If not, is there anyone which have already implemented HL7 
> 2.5 and could 
> send me any hint?
> 
> Thanks
> 
> Giovanni Grimoldi
> g.g...@me...
> 
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> 


This e-mail may contain confidential and/or privileged information
for the sole use of the intended recipient. Any review or distribution
by anyone other than the person for whom it was originally intended is
strictly
prohibited. If you have received this e-mail in error, please contact the
sender and
delete all copies. Opinions, conclusions or other information contained in
this e-mail may not be that of the organization.

[HAPI-devel] HL7 2.5

[Giovanni G. <g.g...@me...>]

Hallo.

I used HAPI last year for a project which involved HL7 2.3.1 version messages.
Now I have to upgrade it to HL7 2.5 compliance level.

I saw that HAPI last version supports HL7 2.4 specification.

I need to know (asap) if you are planning soon (next 15 days) such a 
release or if it isn't in your to do list,yet.
If not, is there anyone which have already implemented HL7 2.5 and could 
send me any hint?

Thanks

Giovanni Grimoldi
g.g...@me...

RE: [HAPI-devel] Unescaping messages

[Tripp, B. <Bry...@uh...>]

Hi Fr=E9d=E9ric,=20
=20
Thank you!  Yes, this is definitely a bug, and that looks like the =
right
fix. =20
=20
Bryan=20

-----Original Message-----
From: Fr=E9d=E9ric Dubru [mailto:fre...@sk...]
Sent: December 6, 2003 3:52 PM
To: hl7...@li...
Subject: [HAPI-devel] Unescaping messages


Hi,

When the PipeParser class encodes a message, it escapes its content =
(for
instance, escape characters (\) are changed into "\E\" codes). But, =
when it
parses a message, it does'nt similarly unescape it. Is it normal ? or =
should
the code be corrected like this (line 340) :

private static void parse(Type destinationField, String data,
EncodingCharacters encodingCharacters) throws HL7Exception {
    ...
            // Terser.getPrimitive(destinationField, i+1,
j+1).setValue(subcomponents[j]);
            String val =3D subcomponents[j];
            if (val !=3D null) {
                val =3D Escape.unescape(val, encodingCharacters);
            }
            Terser.getPrimitive(destinationField, i+1, =
j+1).setValue(val);
    ...
}

(Using HAPI 0.4.)

Yours,


--=20

Fr=E9d=E9ric Dubru

Cliniques universitaires Saint-Luc

10, avenue Hippocrate

B-1200 Bruxelles

+32 2 764 36 43

http://www.saintluc.be <http://www.saintluc.be>=20




This e-mail may contain confidential and/or privileged information
for the sole use of the intended recipient. Any review or distribution
by anyone other than the person for whom it was originally intended is
strictly
prohibited. If you have received this e-mail in error, please contact =
the
sender and
delete all copies. Opinions, conclusions or other information contained =
in
this e-mail may not be that of the organization.

[HAPI-devel] Unescaping messages

[<fre...@sk...>]

Hi,

When the PipeParser class encodes a message, it *escapes* its content=20
(for instance, escape characters (\) are changed into "\E\" codes). But,=20
when it parses a message, it does'nt similarly *unescape* it. Is it=20
normal ? or should the code be corrected like this (line 340) :

private static void parse(Type destinationField, String data,=20
EncodingCharacters encodingCharacters) throws HL7Exception {
    ...
            // Terser.getPrimitive(destinationField, i+1,=20
j+1).setValue(subcomponents[j]);
            String val =3D subcomponents[j];
            if (val !=3D null) {
                val =3D Escape.unescape(val, encodingCharacters);
            }
            Terser.getPrimitive(destinationField, i+1, j+1).setValue(val)=
;
    ...
}

(Using HAPI 0.4.)

Yours,

--=20
Fr=E9d=E9ric Dubru
Cliniques universitaires Saint-Luc
10, avenue Hippocrate
B-1200 Bruxelles
+32 2 764 36 43
http://www.saintluc.be

RE: [HAPI-devel] IndexOufOfBoundsException

[Tripp, B. <Bry...@uh...>]

Hi William, 

Thanks, someone else pointed out the same bug a few days ago.  It's fixed in
HEAD, so let me know if you would like an interim build without this
problem.  

HL7 defines only 2 components for UB2-6, so when you have content (e.g. two
spaces) in component 6, HAPI's handler for "extra components" kicks in, and
the bug was in this code, for the case when a populated extra component
follows an empty extra component.  Messages that adhere strictly to the HL7
spec should work fine, as should most messages that don't.  At UHN we
haven't yet used HAPI 0.4 in a high-volume scenario, but we have parsed
perhaps 2000 test messages without any trouble.  

Bryan 

> -----Original Message-----
> From: William Butler [mailto:wb...@pa...]
> Sent: December 2, 2003 10:07 PM
> To: hl7...@li...
> Subject: [HAPI-devel] IndexOufOfBoundsException
> 
> 
> Some feedback here: I tried running TestPanel with some HL7 data from 
> my institution but I didn't get far. I get the message 
> "IndexOutOfBoundsException index 3 size 0". By deleting lines 
> one at at 
> time from the HL7 message I isolated the line
> 
> UB2|||~~~~~~|||^^^^^  ^^^^^^^^^^^^^^|^^^^^^^^^^^^^^^|^^^^^^^^
> 
> as the cause. In particular, deleting the two whitespaces  
> between the 
> ^ characters before feeding the message causes TestPanel to function 
> fine.
> 
> Thanks,
> 
> Bill Butler
> 
> Mass General Hospital
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by OSDN's Audience Survey.
> Help shape OSDN's sites and tell us what you think. Take this
> five minute survey and you could win a $250 Gift Certificate.
> http://www.wrgsurveys.com/2003/osdntech03.php?site=8
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> 


This e-mail may contain confidential and/or privileged information
for the sole use of the intended recipient. Any review or distribution
by anyone other than the person for whom it was originally intended is
strictly
prohibited. If you have received this e-mail in error, please contact the
sender and
delete all copies. Opinions, conclusions or other information contained in
this e-mail may not be that of the organization.

[HAPI-devel] IndexOufOfBoundsException

[William B. <wb...@pa...>]

Some feedback here: I tried running TestPanel with some HL7 data from 
my institution but I didn't get far. I get the message 
"IndexOutOfBoundsException index 3 size 0". By deleting lines one at at 
time from the HL7 message I isolated the line

UB2|||~~~~~~|||^^^^^  ^^^^^^^^^^^^^^|^^^^^^^^^^^^^^^|^^^^^^^^

as the cause. In particular, deleting the two whitespaces  between the 
^ characters before feeding the message causes TestPanel to function 
fine.

Thanks,

Bill Butler

Mass General Hospital

RE: [HAPI-devel] HL7 version-depended exception

[Tripp, B. <Bry...@uh...>]

Hi, 

When the message is parsed with HAPI 0.4, an HL7Exception is thrown because
MSH-9 (message type) is not present.  MSH-12 (version ID) isn't there
either.  Both these fields are needed to parse the message.  What are you
calling that throws an IndexOutOfBoundsException?    

Bryan 

> -----Original Message-----
> From: pv...@qu... [mailto:pv...@qu...]
> Sent: December 1, 2003 5:55 AM
> To: hl7...@li...
> Subject: [HAPI-devel] HL7 version-depended exception
> 
> 
> On next HL7 wich received from device Clinitec 50 (connected 
> by JavaLin)
> HAPI throw IndexOfBoundsException (11) because MSH don't 
> contains field #12
> :
> 
> 
> MSH|^~\&||002|||19990729000025|||1
> PID|1
> OBR|1||005|||||||||||||||Device002^002
> OBX|1||Color||LT.  YELLOW
> OBX|2||GLU||NEGATIVE
> OBX|3||BIL||NEGATIVE
> OBX|4||KET||NEGATIVE
> OBX|5||SG||>=1.030
> OBX|6||BLO||NEGATIVE
> OBX|7||pH||6.0
> OBX|8||PRO||NEGATIVE
> OBX|9||URO||0.2 E.U./dL
> OBX|10||NIT||NEGATIVE
> OBX|11||LEU||NEGATIVE
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> 


This e-mail may contain confidential and/or privileged information
for the sole use of the intended recipient. Any review or distribution
by anyone other than the person for whom it was originally intended is
strictly
prohibited. If you have received this e-mail in error, please contact the
sender and
delete all copies. Opinions, conclusions or other information contained in
this e-mail may not be that of the organization.

[HAPI-devel] HL7 version-depended exception

[<pv...@qu...>]

On next HL7 wich received from device Clinitec 50 (connected by JavaLin)
HAPI throw IndexOfBoundsException (11) because MSH don't contains field #12
:

MSH|^~\&||002|||19990729000025|||1
PID|1
OBR|1||005|||||||||||||||Device002^002
OBX|1||Color||LT.  YELLOW
OBX|2||GLU||NEGATIVE
OBX|3||BIL||NEGATIVE
OBX|4||KET||NEGATIVE
OBX|5||SG||>=1.030
OBX|6||BLO||NEGATIVE
OBX|7||pH||6.0
OBX|8||PRO||NEGATIVE
OBX|9||URO||0.2 E.U./dL
OBX|10||NIT||NEGATIVE
OBX|11||LEU||NEGATIVE


[HAPI-devel] Healthcare OS Survey

[Robin S C. <car...@cs...>]

Hi,

First off - great work - nice to see an open source project from one of 
the university ave. gang. (I used to be at Sinai).   The folks at Cihi 
were also singing your praises at a recent HL7 tutorial they held here. 

Anyways, I'm conducting a survey (for both personal interest and as a 
requirement for a course) of basic statistics of those interested and 
involved in open source software use in direct patient care.  All the 
information is available here:  http://www.cs.dal.ca/~carriere/hhs

I was just wondering if:you could;
a) complete the survey.
b) you could pass this onto any colleagues that share similar interests 
in open source use in healthcare


Thanks,  Robin

FW: [HAPI-devel] RDT Question

[Tripp, B. <Bry...@uh...>]

-----Original Message-----
From: Tripp, Bryan 
Sent: November 10, 2003 7:08 PM
To: 'Ackley, Keith A'
Subject: RE: [HAPI-devel] RDT Question


Hi Keith, 

My understanding is that RDT-1 doesn't repeat, but that there are an
undefined number of fields in RDT (in the standard, the table says 1-n in
the SEQ column).  When parsing an incoming message with an RDT, HAPI should
add whatever fields are present to the segment, all as Varies types.  

If you are building the message, use Segment.getField(i, 0) (1 < i <= number
of fields) to create each field on the fly (again, this will return a
Varies).  

Bryan 

> -----Original Message-----
> From: Ackley, Keith A [mailto:kei...@ed...]
> Sent: November 10, 2003 5:45 PM
> To: 'hl7...@li...'
> Subject: [HAPI-devel] RDT Question
> 
> 
> The max reps is 1 for the Varies in the constructor for RDT. 
> Here is the
> constructor:
> 
>   public RDT(Group parent) {
>     super(parent);
>     try {
>        this.add(Varies.class, true, 1, 0, null);
>     } catch (HL7Exception he) {
>         
> HapiLogFactory.getHapiLog(this.getClass()).error("Can't instantiate
> " + this.getClass().getName(), he);
>     }
>   }
> 
> From the HL7 2.4 specification, I would think that it should 
> be 0 for no
> limit. Am I misreading the specification or is the code wrong?
> 
> Thanks,
> Keith
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL,
> WebDAV, and more! http://www.apachecon.com/
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> 


This e-mail may contain confidential and/or privileged information
for the sole use of the intended recipient. Any review or distribution
by anyone other than the person for whom it was originally intended is
strictly
prohibited. If you have received this e-mail in error, please contact the
sender and
delete all copies. Opinions, conclusions or other information contained in
this e-mail may not be that of the organization.

[HAPI-devel] RDT Question

[Ackley, K. A <kei...@ed...>]

The max reps is 1 for the Varies in the constructor for RDT. Here is the
constructor:

  public RDT(Group parent) {
    super(parent);
    try {
       this.add(Varies.class, true, 1, 0, null);
    } catch (HL7Exception he) {
        HapiLogFactory.getHapiLog(this.getClass()).error("Can't instantiate
" + this.getClass().getName(), he);
    }
  }

From the HL7 2.4 specification, I would think that it should be 0 for no
limit. Am I misreading the specification or is the code wrong?

Thanks,
Keith

RE: [HAPI-devel] Varies handling.

[Tripp, B. <Bry...@uh...>]

Hi Keith, 

Thanks for pointing out these problems.  They are easy to fix for future
versions of HAPI -- there is actually a hook that deals with OBX-5 in the
same manner, so it can just be expanded to handle MFE and RDT.  I've put it
on the to-do list for version 0.5. 

In the mean time, your decorator approach sounds perfectly reasonable to me.


Another option is to set the datatype of each Varies object manually, using
setData().  You would parse the message, and then whatever code was using it
would check (for example) MFE-4, call setData() with the appropriate
datatype, and then getData() would return that type.  Doing this in a
decorator sounds better though.  

Bryan 

> How should I work around the problem? I could wrap your 
> parser and post
> process the message to "fix-up" the datatypes, but I was 
> hoping for a better
> solution. Any suggestions would be appreciated.



This e-mail may contain confidential and/or privileged information
for the sole use of the intended recipient. Any review or distribution
by anyone other than the person for whom it was originally intended is
strictly
prohibited. If you have received this e-mail in error, please contact the
sender and
delete all copies. Opinions, conclusions or other information contained in
this e-mail may not be that of the organization.

[HAPI-devel] Varies handling.

[Ackley, K. A <kei...@ed...>]

Hi,

I'm having problems parsing MFE. The parsing is using the incorrect type for
the primary key value. It should be a CE instead of a generic composite. It
should know this be examining MFE-5 which specifies the type used for the
primary key value contained in MFE-4.

I'm guessing this is a know problem with handling varies that you have not
had time to address? Is this correct?

How should I work around the problem? I could wrap your parser and post
process the message to "fix-up" the datatypes, but I was hoping for a better
solution. Any suggestions would be appreciated.

Another place the problem arises is with RDFs specifying the datatypes used
in the RDTs.

Thanks,
Keith

[HAPI-devel] Anyone familiar with Mailman? Also, one more try ... Stock Marke t

[Tripp, B. <Bry...@uh...>]

If anyone on the list is familiar with GNU Mailman, what am I doing wrong
here?  There is a field in the Web UI called "Hold posts with header value
matching a specified regexp", and I've added the following line: 

subject: .*Stock\sMarket.*

What should it be?  

Thanks, 
Bryan 


This e-mail may contain confidential and/or privileged information
for the sole use of the intended recipient. Any review or distribution
by anyone other than the person for whom it was originally intended is
strictly
prohibited. If you have received this e-mail in error, please contact the
sender and
delete all copies. Opinions, conclusions or other information contained in
this e-mail may not be that of the organization.

[HAPI-devel] please disregard, I'm just testing a new spam filter on ... Stock Market

[Tripp, B. <Bry...@uh...>]

This e-mail may contain confidential and/or privileged information
for the sole use of the intended recipient. Any review or distribution
by anyone other than the person for whom it was originally intended is
strictly
prohibited. If you have received this e-mail in error, please contact the
sender and
delete all copies. Opinions, conclusions or other information contained in
this e-mail may not be that of the organization.

[HAPI-devel] HAPI 0.4

[Tripp, B. <Bry...@uh...>]

HAPI 0.4 is now available for download ... 

https://sourceforge.net/project/showfiles.php?group_id=38899

Thanks for your patience.  Please let me know if you encounter any problems.

Bryan 


Changes since 0.4 beta: 

change build to compile core with debug line numbers 
add wildcards for MessageTypeRouter 
fix missing segment location on HL7Exception during parse 
handle Varies in Terser setter (check type and switch to GenericComposite if
comp > 1) 
allow unexpected components on composites 
update PipeParser to allow unexpected components 
allow unexpected field repetitions 
add hook for testing table values in profiles (profile, table / codeSystem)
per Lloyd's suggestion 
handle nnnn as wildcards in codes 
lookup table for events that don't map directly to message structures 
fix new DB errors noted on Frank Oemig's web page 
v2.2 PN: getFamiliyName should be getFamilyName 
add getXReps to generated code for repeating structures 
add HapiLog to docs and core source 
log4j config in release 
incorporate Alexei's GenericHL7Message fix
update DeepCopy to allow extra components 
update TreePanel to show extra components 
fix wildcard handling in AbstractCodeStore to treat wildcard-containing
codes as special cases, handle comma delimiter 
fix docs in HL7Service re registration 
use HAPI_HOME property for custom_packages, configuration, id_file, etc. 
add libs to distribution with Class-Path entry in manifest (use like
-classpath %HAPI_HOME%\hapi.jar) 
add copyright & license with libs 
remove commented code from PipeParser 
change MSH-9 to CM_MSG in v2.1 
change message in DefaultValidator: Value 'x' doesnt' equal constant value
of 'y' 
remove Status references and deprecate 
in DefaultValidator, skip validation of X (not used) elements 



This e-mail may contain confidential and/or privileged information
for the sole use of the intended recipient. Any review or distribution
by anyone other than the person for whom it was originally intended is
strictly
prohibited. If you have received this e-mail in error, please contact the
sender and
delete all copies. Opinions, conclusions or other information contained in
this e-mail may not be that of the organization.