Trading partners can rely only on having the interchange available - from the ISA to the IEA - as those have been the only parts standardized by HIPAA. So the information conveying real-time vs. batch must either appear somewhere in the interchange header (ISA) - which isn't possible as far as I can see, in the GS, or in the transaction itself.
Even if an inquiry could be enveloped by ebXML Messaging Services, and thus the syncReply attribute were available, we need to make recommendations based on what's known or seen by all parties implementing HIPAA standard transactions - and, unfortunately, that's just the stuff between the ISA and the IEA, inclusive. William J. Kammerer Novannet, LLC. +1 (614) 487-0320 ----- Original Message ----- From: "Dick Brooks" <[EMAIL PROTECTED]> To: "William J. Kammerer" <[EMAIL PROTECTED]>; "'WEDi/SNIP ID & Routing'" <[EMAIL PROTECTED]> Sent: Tuesday, 29 January, 2002 03:08 PM Subject: RE: Batch vs. Real Time transactions William, The facilities to identify Batch versus Real time processing may be provided by an underlying messaging service which would eliminate the need for "flags" within the transaction sets. For example, ebXML's Message Service contains a header attribute, called syncReply, to inform the receiver that a sender is expecting a "Real Time" (synchronous) response. Batch mode processing is indicated by absence of the syncReply attribute. Perhaps it would be worthwhile for the group to define some expectations/requirements with regard to the infrastructure needed to support transaction exchanges. One example requirement might be: - The Transport mechanism MUST support Batch and Real Time processing. - ... Dick Brooks Systrends, Inc 7855 South River Parkway, Suite 111 Tempe, Arizona 85284 Web: www.systrends.com <http://www.systrends.com> Phone:480.756.6777,Mobile:205-790-1542,eFax:240-352-0714
