In HIPAA loops have the exact same attributes but the attribute values are different from the pure X12N definitions. For example, the name of the loop may be different from the name of its first segment (In X12 a loop and its first segment usually use the same id). As such additional programming is done for these different naming values. And in OBOE the definitions are defined in its XML transaction set rules files; so the HIPAA package uses a different set of rules files for the different way HIPAA spells out the transaction.
The HIPAA specific design requires the OBOE package to recognize the segments that repeat but that are identified by different names. For instance, in X12 a segment may occur 7 times, but in HIPAA the same segment with the same ID will use a different name and occur multiple times at the same location. For example, in pure X12 the Segment DTP name repeats within its containers with the same name 'Date" but in HIPAA the same segment occurs multiple times using a unique name:
name="Date - Admission" id="DTP" name="Date - Discharge" id="DTP" name="Date - Referral" id="DTP"So the HIPAA package allows a program to search for a segment by its unique name, instead of searching by its non-unique name and its location within its container.
|3.0 Extended||Binary||$3250*||Purchase Binary|
|3.0 Extended||Source||$5250*||Purchase Source|