Damon It is my understanding that only option 1 (EDI Message sent as a continuous string of characters in a single record) is a valid X12 message format. If you look at the examples in the 837 professional (Section 4) you will see this presented as a string of text at the end of each example. We included this text string to put in an example of a correct X12 data string. Too many people were reading the segment-by-segment examples and thinking that this meant that each segment had to be followed by a carriage return. Not true!
Questions like this can usually be answered by reviewing Appendix A in the back of all the implementation guides. Everyone on this list serve should read Appendix A, front to back, at least once! Jan Root [EMAIL PROTECTED] wrote: > Are all of the following formats valid input formats for transmitting an > X12 transaction, for example an 835: > > EDI Message sent as a continuous string of characters in a single > record > EDI Message sent as a series of 80 byte records, every 80 characters > becomes a new record (80 byte wrapped) > EDI Message sent as each segment in a separate record of variable > length > > If valid, which of the above formats is the preferred format for receipt of > the EDI Message, or is it determined through a Trading Partner Agreement. > > Damon Tressler > AdvancePCS > > ********************************************************************** > 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.
