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.