Kepa, Your advice is good.
Re your observation that some systems generate a CRLF as a segment terminator....this is often done by PC-based low-end systems. Most of the major commercial EDI management systems have evolved over the years to be able to handle this circumstance, even though we know that the X12 standards specify that the terminator character is a single character. As is usually the case, it's the receiver of something not quite standard that must find a way to handle it, especially since in many cases the originator actually has little if any control over what is being generated. This does bring up an interesting point, however, in that the use of CRLF as a segment terminator clearly is not compliant with the X12 standard, but common non-health care EDI community practice over the years has evolved to accommodating this variant. What do you think this might mean for any strict compliance validation with the X12 standards? Rachel Foerster Principal Rachel Foerster & Associates, Ltd. Professionals in EDI & Electronic Commerce 39432 North Avenue Beach Park, IL 60099 Phone: 847-872-8070 Fax: 847-872-6860 http://www.rfa-edi.com <http://www.rfa-edi.com> -----Original Message----- From: Kepa Zubeldia [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 18, 2001 12:49 PM To: [EMAIL PROTECTED] Subject: Re: Segment separators - Translators Joe, I think you have two choices: 1) fix the program in the mainframe to handle these very long files without carriage returns in them. 2) pre-process the files to change the segment terminator into something more palatable to your mainframe. However, be careful with option #2, because when you get a 275 transaction (future claims attachment HIPAA transaction, in the works) that contains an embedded HL7 transaction for which the delimiter will also be the CR-LF, your translator could get pretty confused. And, for some people the new line is CR (e.g. macIntosh), for other people it is LF (e.g. UNIX) and for other people it is CR-LF (e.g. MS-DOS) and that is actually two bytes. X12 syntax say that the delimiter is only one byte. Good luck. Kepa "BARTON, Joe" wrote: > > All the HIPAA transaction examples I have seen, and IG's use a tilde for a > segment separator. This segment separator is defined in the ISA segment at > the top of the transaction set. I have referenced in BizTalk server 2000 > documentation where a carriage return is the most common choice as defined > in X12 standards dictionary X12.22 Our Unisys mainframe can handle a > segment as a record containing a carriage return very well, but not several > thousand segments as one record if the tilde is the separator. Your comments > on this matter are appreciated. > > Joseph "JP" Barton > Information Technology Applications Specialist > State of Washington DSHS/ASD/OIS > (360) 664-6147 {mailto:[EMAIL PROTECTED]] > > CONFIDENTIALITY NOTICE: This email message is for the sole use of the > intended recipient(s) and may contain confidential and privileged > information. Any unauthorized review, use, disclosure or distribution is > prohibited. If you are not the intended recipient, please promptly delete > this message and its attachments from your computer system, and notify the > sender. All messages to and from the Department of Social and Health > Services may be disclosed to the public. > > . > > <<BARTON, Joe.vcf>> > > ********************************************************************** > 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. ********************************************************************** 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.
