Re: [HAPI-devel] message segment counts

[Phillip T. <pto...@co...>]

I like the idea of a getter that returns an array of multiple type-safe 
values, or a count. Either would work for me.. One question though.. I 
can't think of an example.. but how would it work if there were RXC 
segments in multiple places in the message?

I technically don't want to get allRXC() in the entire RDE, I want all 
the RXC segments within the RXE. Make sense?

I'm very new to hapi, so maybe this is an issue that's covered some 
other way.

-Phill


On Tuesday, August 12, 2003, at 06:46  AM, Tripp, Bryan wrote:

> Hi Phill,
>
>> construct.. I have an object of type
>> RDE_O11_ORCRXONTERXRRXCNTERXERXRRXCOBXNTECTI... crazy.
>
> Yes, the brute-force method of avoiding name collisions.  This is how 
> group
> names were originally defined in the XML encoding.  For example the
> corresponding DTD element for this group was:
>
> <!ENTITY % RDE_O01.ORCRXONTERXRRXCNTERXERXRRXCOBXNTECTI.CONTENT
> (ORC,RDE_O01.RXONTERXRRXCNTE?,RXE,RXR+,RXC*,RDE_O01.OBXNTE+,CTI*)">
>
> More recently HL7 has been coming up with nice, short group names, so 
> this
> won't last forever.
>
>> what's my mechanism for iterating them?
>
> I would do this:
>
> (RXC[]) group.getAll("RXC");
>
> ... but come to think of it this doesn't test your assumptions about 
> message
> structure at compile time.  Maybe there should also be:
>
> RXC[] getAllRXC();
>
> ... or:
>
> int getNumRXC();
>
> What does everyone think?
>
> 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.
>