Here is some background on the medical attachment using HL7: http://www.wedi.org/cmsUploads/pdfUpload/Generic/Pub/ClaimsAttachSurveyFinalRpt.pdf
David Frenkel ----- Original Message ---- From: Mike Rawlins <[EMAIL PROTECTED]> To: [email protected] Sent: Thursday, November 8, 2007 1:08:36 PM Subject: Re: [EDI-L] XML embedded in EDIFACT Yes, similar things have been done. I think there is even a case where some companies are sending an HL7 XML message inside an X12 EDI transaction set as the contents of a binary data element. However, this case and those you all mention are entirely different from the corrupt CONTRL message Eileen posted. Mike ------------ --------- --------- --------- -- Michael C. Rawlins, Rawlins EC Consulting www.rawlinsecconsul ting.com Lowell Porter wrote: > We did something similar with a TP once. They had been sending us a flat > file on a CD and wanted to do something more efficient than CD. They ended > up sending the data in an 864 "text message". The format of the flat file > did not change. They just sent every line of the flat file in on a MSG > segment. This allowed me to automate the entire process. > > > > Lowell > > _____ > > From: [EMAIL PROTECTED] com [mailto:[EMAIL PROTECTED] com] On Behalf Of > Rudolph, Mike > Sent: Thursday, November 08, 2007 11:11 AM > To: jkcedi > Cc: [EMAIL PROTECTED] com > Subject: RE: [EDI-L] XML embedded in EDIFACT > > > > > jkcedi, > > True. Years ago we used the GEIS 'pass through envelope' to receive > proprietary data from a specific TP. The payload was simply non-EDI > formatted file (probably 80 characters) wrapped with ISA/IEA, and both > parties knew about it. Don't know if GXS still offers it. > > Mike Rudolph > > -----Original Message----- > From: [EMAIL PROTECTED] <mailto:EDI- L%40yahoogroups. com> com > [mailto:EDI- [EMAIL PROTECTED] <mailto:EDI- L%40yahoogroups. com> com] On > Behalf > Of > jkcedi > Sent: Thursday, November 08, 2007 11:02 AM > To: edieileen; Mike Rawlins > Cc: [EMAIL PROTECTED] <mailto:EDI- L%40yahoogroups. com> com > Subject: Re: [EDI-L] XML embedded in EDIFACT > > Speaking generally, I have heard of putting enveloping around non-EDI > data for transmission/ routing purposes, to trick some systems into > allowing the data through. But this should be an exception, and should > never be done without the explicit agreement between partners. > > ----- Original Message ----- > From: Mike Rawlins > To: edieileen > Cc: [EMAIL PROTECTED] <mailto:EDI- L%40yahoogroups. com> com > Sent: Thursday, November 08, 2007 10:19 AM > Subject: Re: [EDI-L] XML embedded in EDIFACT > > Never seen anything like it for a CONTRL, 997, or 999. I suspect that > either something got messed up on the sender's end, or else they are > clueless. > > ------------ --------- --------- --------- -- > Michael C. Rawlins, Rawlins EC Consulting > www.rawlinsecconsul ting.com > > edieileen wrote: > >> One of our customers received and EDIFACT CONTRL transaction with >> XML embedded in it. Has anyone ever seen this before? >> >> Thanks, >> >> Eileen >> >> >> The transaction looks like this: >> >> >> > UNB+UNOA:2+XXX+ XXX:XX+071106: 1033+2000117' UNH+0001+ CONTRL:2: 2:UN'UCI+ > >> 000000005+XXX+ XXX+4'UCM+ Please look at the UCM Segments for your >> Error Details'UCM+ >> <HeaderInfo> >> <SenderInfo> >> <SenderId>MNP< /SenderId> >> <SenderControlNbr> 000000005< /SenderControlNb r> >> <SenderApplDocId> 62191</SenderApp lDocId> >> <ShipFromId> 88123</ShipFromI d> >> <ShipToId>72401< /ShipToId> >> </SenderInfo> >> <ReceiverInfo> >> <ReceiverId> 0935HRB2002201< /ReceiverId> >> </ReceiverInfo> >> <MsgInfo> >> <MsgType>DESADV< /MsgType> >> <DateTimeStamp> 11-06-2007T11: 34:22</DateTimeS tamp> >> </MsgInfo> >> </HeaderInfo> >> <ErrorDetails> >> <ErrorCode>7181< /ErrorCode> >> <TypeofError> MISSING ELEMENT</TypeofErro r> >> <LocationOfBadData> Segment: NAD; CdListRspAgencyCd >> Element</LocationOf BadData> >> <LineNumber> 12</LineNumber> >> <BadData>NAD< /BadData> >> </ErrorDetails> >> 'UNT+5+0001' UNZ+1+2000117' >> >> >> >> ... >> Please use the following Message Identifiers as your subject prefix: >> > <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> > >> Job postings are welcome, but for job postings or requests for work: >> > <JOBS> IS REQUIRED in the subject line as a prefix. > >> Yahoo! Groups Links >> >> >> >> >> >> > > [Non-text portions of this message have been removed] > > ... > Please use the following Message Identifiers as your subject prefix: > <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> > > Job postings are welcome, but for job postings or requests for work: > <JOBS> IS REQUIRED in the subject line as a prefix. > Yahoo! Groups Links > > > > > > [Non-text portions of this message have been removed] > > > > ... > Please use the following Message Identifiers as your subject prefix: <SALES>, > <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> > > Job postings are welcome, but for job postings or requests for work: <JOBS> > IS REQUIRED in the subject line as a prefix. > Yahoo! Groups Links > > > > > [Non-text portions of this message have been removed] ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
