The way I interpret HL "top-down, left-right, ordered structure" is that it follows the database-table record/structure integrity. By this I mean:
1. The master records (Parent level HL loops) must occur before corresponding child HL loops (key point). 2. It is okay to have all master records (Parent level HL loops) occur one after another before their respective children records. 3. There is enough information in HL segment to associate an occurring child HL loop with correct HL parent hierarchy even if the child HL loop does not occur immediately after it's immediate parent. Thanks and regards, Ajay Ajay K Sanghi Managing Director ABO Software Private Limited B102 Gulmohar Park, New Delhi 110049 Tel: +91 11 6968976, 6512822 Fax: 6518873 Website: http://www.abosoftware.com email: [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Kepa Zubeldia Sent: Sunday, October 28, 2001 7:50 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; HIPAAlive; X12N Subject: TCS: HL structure clarification There has been some debate on the proper structuring of HL loops for the HIPAA transactions. This is very important, as it could make the HIPAA transactions totally unprocessable by the receiver. The X12 standard is somewhat subject to interpretation as to what is a "top-down/left-right" ordered structure. So I asked William Kammerer, past X12C chair. His response is below. I think that X12N, SNIP, or DHHS ought to submit a "Request for interpretation" to X12C as soon as possible on this topic. In the meantime, maybe X12N, SNIP, or DHHS can address this topic. Comments? Kepa Zubeldia Claredi "William J. Kammerer" wrote: I looked at both X12.6 Application Control Structure and 12.59 Implementation of EDI Structures - Semantic Impact, and though the latter mentions the HL, there is no mention that subordinate HL loops must be contiguous to their parent in a top-down left-to-right manner. But there is a segment comment associated with the HL that says "The HL segment defines a top-down/left-right ordered structure," for whatever that's worth. I realize that doesn't definitively mean the HLs have to be physically in that order in the data. "Does in order mean that all the children HL must immediately follow their parent HL before there is another parent HL?" I would maintain that, yes, in-order means top-down, left to right ordering. "Is that stated somewhere in X12?" Not explicitly in X12.6, X12.59 nor in the HL dictionary itself, as I indicated above. I think this calls for a Request for Interpretation. If I had still been "chair" of X12C TG2, I would have been the one to write the response. Actually, even if X12 doesn't address the issue, shouldn't the HIPAA IGs explicitly lay down this rule once and for all? William J. Kammerer Novannet, LLC. +1 (614) 487-9286 +1 (614) 638-4384 (c) +1 (520) 396-6310 (FAX) ----- Original Message ----- From: "Kepa Zubeldia" <[EMAIL PROTECTED]> To: "William J. Kammerer" <[EMAIL PROTECTED]> Subject: Re: TCS: Hierarchical Level Structure William, What does "in order" mean? If someone sends all the "insured HL" in order first and then all the "patient HL" in order also, but from a patient HL is pointing to an insured HL that is many levels above as being the parent, is that out of order? Does in order mean that all the children HL must immediately follow their parent HL before there is another parent HL? Is that stated somewhere in X12? ********************************************************************** To be removed from this list, send a message to: [EMAIL PROTECTED] Please note that it may take up to 72 hours to process your request. ********************************************************************** To be removed from this list, send a message to: [EMAIL PROTECTED] Please note that it may take up to 72 hours to process your request.
