Kepa, I apologize, I miss-read Lisa's post. I was thinking of cr-lf as the segment separator itself.
I have seen many X12 documents sent "unwrapped" with the "~(cr-lf)", but generally smaller 'test' files, where they were intentionally unwrapped for readability. I never really thought too much of it with concentrating on data issues, that sort of thing seemed relatively minor. What happens often is they stream or block the data when they test the transmission and/or go into production. I do not know of many translators that can 'create' a two-character segment separator. That kind of "unwrapping" is often done outside of the translator - or perhaps with a home grown mapper. Question: Would the file then be considered "non HIPAA compliant" with a 2 character segment terminator? If it violates X12, should it in reality be rejected? Just curious. Thanks, Mary Burkinshaw Axiom Systems, Inc. The Managed Care Technical Experts Germantown, MD. www.axiom-systems.com -----Original Message----- From: Kepa Zubeldia [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2003 8:00 PM To: WEDI SNIP Transactions Workgroup List Subject: Re: Valid file formats Lisa, The X12 syntax specifies that the segment terminator is ONE single byte. In your case, it would be the tilde. To follow the segment terminator with a Carriage Return, New Line, or both (CR-LF) is not correct according to the X12 syntax. For chapter and verse, look at X12.6 or even the somewhat simplified description in the IGs at Appendix A, section A.1.2.7 where it says the delimiter is ONE byte. Or the note #1 for the ISA segment (Page B.3 of the IGs). The definitive document on X12 syntax issues is X12.6. Having said that... most translators will accept a Return or New Line or both after the segment terminator without complaining too much, even though it is technically in violation of the X12 syntax. The X12 syntax calls for a "byte stream" but the tradition has been to send a byte stream whenever possible and accept a line-oriented transaction set as an alternative mechanism when receiving files. I hope this helps. Kepa Zubeldia Claredi On Wednesday 12 March 2003 11:21 am, Eney, Lisa wrote: > Can an 837P (or any other transaction) file which is formatted so that > segment identifiers are aligned to the left (with tildes essentially > functioning as hard returns) be considered a HIPAA compliant format? > > For example: > > ST*837*0001~ > BHT*0019*00*0001*20020824*0000*CH~ > REF*87*004010X098D~ > > I do not think that it would be, but now that I find myself in a position to > defend that idea, I am unable to find the chapter and verse in the IG to > support it. Any help in this matter would be greatly appreciated. > > Thanks, > Lisa > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Lisa Eney > Project Manager > HIPAA Claims Transaction Code Sets > ADMS - Baltimore > 410.209.5216 > [EMAIL PROTECTED] --- The WEDI SNIP listserv to which you are subscribed is not moderated. The discussions on this listserv therefore represent the views of the individual participants, and do not necessarily represent the views of the WEDI Board of Directors nor WEDI SNIP. If you wish to receive an official opinion, post your question to the WEDI SNIP Issues Database at http://snip.wedi.org/tracking/. These listservs should not be used for commercial marketing purposes or discussion of specific vendor products and services. They also are not intended to be used as a forum for personal disagreements or unprofessional communication at any time. You are currently subscribed to wedi-transactions as: [EMAIL PROTECTED] To unsubscribe from this list, go to the Subscribe/Unsubscribe form at http://subscribe.wedi.org or send a blank email to [EMAIL PROTECTED] If you need to unsubscribe but your current email address is not the same as the address subscribed to the list, please use the Subscribe/Unsubscribe form at http://subscribe.wedi.org --- The WEDI SNIP listserv to which you are subscribed is not moderated. The discussions on this listserv therefore represent the views of the individual participants, and do not necessarily represent the views of the WEDI Board of Directors nor WEDI SNIP. If you wish to receive an official opinion, post your question to the WEDI SNIP Issues Database at http://snip.wedi.org/tracking/. These listservs should not be used for commercial marketing purposes or discussion of specific vendor products and services. They also are not intended to be used as a forum for personal disagreements or unprofessional communication at any time. You are currently subscribed to wedi-transactions as: [EMAIL PROTECTED] To unsubscribe from this list, go to the Subscribe/Unsubscribe form at http://subscribe.wedi.org or send a blank email to [EMAIL PROTECTED] If you need to unsubscribe but your current email address is not the same as the address subscribed to the list, please use the Subscribe/Unsubscribe form at http://subscribe.wedi.org
