Hi Nicolas,
Thanks very much for offering the patch. I see you have contacted
James as well. He is in charge of the project and is the right person
to follow up with.
I should probably take my ID off the administrators' list, as I
haven't been involved in the project for several years.
All the b
Raphaëlle,
If you just have a few specific tests you want to perform, you could
write a custom ca.uhn.hl7v2.validation.MessageRule and add it to your
ValidationContext (maybe subclass DefaultValidation).
If you want to test against detailed specs, consider conformance
profiles. See the ca.uhn.hl7
Hi Frédéric,
> Note : just a stupid question, the HAPI project also exposes HL7
> specifications through its code, does it mean that it also conflicts with the
> IHE terms of use ?
The HAPI project has special permission from HL7 to release
specification-related code.
Regards,
Bryan
-
It's because in contrast to most fields, which have a pre-specified
data type, the data type for OBX-5 is defined at message time (in
OBX-2).
Bryan
On Wed, Feb 25, 2009 at 1:58 PM, Dayu Han wrote:
> Thanks for the code and it worked just fine. However, I wonder if anyone
> knows WHY for OBX-5, w
nada, where it was written. More specifically, it is totally
> under the control of Bryan Tripp, who seems to have created a lot of it
> originally, and James Agnew, to whom Bryan has largely passed the torch.
> Bryan wrote an excellent piece of software, and James seems to have kept
> the
HAPI doesn't test for valid structure by default. The thorough way to
do it is to use conformance profiles (see
http://www.hl7.org/Special/committees/ictc/index.cfm), and a
ca.uhn.hl7v2.validation.impl.ConformanceProfileRule. If that's too
much trouble, you can write a simpler
ca.uhn.hl7v2.validati
Hi,
If you're using the ca.uhn.hl7v2.protocol package, you can control
this by passing a NullSafeStorage to the HL7Server's constructor. This
is actually the default in HL7Server's main().
Bryan
On 4/17/08, Clarkson, Peter J <[EMAIL PROTECTED]> wrote:
>
>
>
> Is it possible to use the HL7Server
Hi Ryan,
You can write multi-version code with ca.uhn.hl7v2.util.Terser.
The message classes are in the jar. They aren't in CVS or the source
zip because they're automatically generated. (And they aren't in the
JavaDocs because there are thousands of them, and the docs aren't that
informative.)
ce the narrow
interpretation in this case.
James, do you have any comments?
Bryan
On 9/19/07, Life is hard, and then you die <[EMAIL PROTECTED]> wrote:
>
> [sorry for the slow reply - was offline for bit]
>
> On Thu, Sep 13, 2007 at 11:29:09AM -0400, Bryan Tripp wrote:
> >
Hi Ronald,
> I think there's a slight confusion regarding HL7 Null's: only a field
> as a whole may be Null, not individual components. So, |""| says the
Yes, I might be confused about that. Can you give me a section reference?
Thanks,
Bryan
-
Hi Ronald,
Thanks for the explanations. I think I understand where you're coming
from but I have a few more questions ...
> 1. Checking for Null currently is hard, because you actually have
>to check all parts in a composite type. E.g. for a field of type
>XPN you have to check that XPN.
Hi Fabio,
The RIM deals with v3. Version 2.3.1 and other 2.x versions don't use it.
Bryan
On 9/4/07, Fabio Daprile <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> i would like to know which version of HL7 RIM has been used for HAPI 2.3.1
> Numbering od RIM db's on HL/ site is not aligned with versio
Hi Ronald,
I'm not sure I understand the motivation for handling them specially.
Nulls (as opposed to empty fields) are to indicate that corresponding
data should be deleted from the receiving application. This is
supported -- if a field contains "\"\"" then the application should
delete data -- b
Hi Burke,
I'm not sure if you got Torben's answer before your last message, but
it was right. There is one HAPI class for each message structure, but
multiple events can use the same structure (e.g. event A28 uses
structure ADT_A05).
If you are creating a new message, use the structure that corre
Hi,
Have you tried ca.uhn.hl7v2.util.Terser? The set() and get() methods
access fields in a version-independent way (as much as possible) and
there is also getSegment() if you want a whole segment.
Bryan
On 6/19/07, granger44 <[EMAIL PROTECTED]> wrote:
>
>
> fer wrote:
> >
> > Hello, I newbie in
Hi Dan,
One simple way to do it would be to override Parser.parse(String) to
change "2.3.0" to "2.3". Another option would be to get Parser to
treat 2.3.0 as a valid version that is equivalent to 2.3, but this
would really amount to doing the same thing as above, but in multiple
places.
Bryan
On
16 matches
Mail list logo
