When I explain Real Time to my clients(Request/Response pairs), I always equate it to a MAC machine. Once you insert your Credit/Debit Card, and enter your PIN, the transaction has started and you're connected to the system. The request is always followed by a response. If you want to check your balance, this would be a request transaction. Then the MAC machine responds with your current balance. Now this response might take 5-10 secs, but this is considered real time. In an other Insurance Field where we are using XML for such business, they are titled Request/Response pairs, and you must be able to receive the response. We had set time limits on how long a response should take. I believe it was 5 - 10 sec max (I may be a little off). The connection was maintained through the internet. Batch will always be batch. Sending numerous transactions that will be run later that day, or overnight. I will check my implementation guides for a more precise time limit set for real time, and a better example of how we are using it on one line of the insurance industry. I hope this helps. Thanks Anthony Mercaldi
----- Original Message ----- From: "Pulver, Scott" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, September 24, 2002 5:29 PM Subject: RE: Batch vs real time > As I read the HIPAA implementation guide ... the term "Real-time" doesn't > imply a set response time. Real-time means, a submitter makes a > "connection", submits the interchange and waits for a response without > breaking the connection. So far, I haven't heard of a specific > implementation for what "connection" means. > > If anyone has implemented any of the interchanges in "real-time", would you > forward to the ListServe what your implementation is please? I think as an > industry we should standardize what this means in order to facilitate the > communication between providers, payors and intermediaries, etc.. > > Scott Pulver > Per-Se Technologies > > > -----Original Message----- > From: Martin Scholl [mailto:[EMAIL PROTECTED]] > Sent: Saturday, September 21, 2002 8:39 AM > To: [EMAIL PROTECTED] > Subject: RE: Batch vs real time > > > I believe, if you have now a real-time interface, then you are reqired to > provide the same kind of service (real-time) through HIPAA TCS. > But, since there is no standard yet on routing EDI files, this might not be > possible. > What is real-time and EDI? I've heard 20 sec response time. > So, you are getting an EDI file, dumped into some kind of inbox, or pulled > from a VAN inbox. > To qualify for "real-time" you would have to poll the inbox every 10 > seconds, process the request and then what ???? Deposit the result file in > your outbox with the VAN, put it in your ftp server's outbox for pick-up or > push it into the receiver's inbox? > None of the traditional EDI routing mechanisms is designed for real-time. > Now there might be some solutions. Technically sophisticated, expensive and > proprietary that allow you "real-time" EDI transfer, but I think the > Legislator cannot force you to go that route. > I would say, try your best and let the dust settle. Maybe we will see in > the near future some nice, open interfaces that the industry can standardize > on. > Martin Scholl > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > www.HIPAASuite.com <http://www.HIPAASuite.com> > 301-924-5537 Voice > 301-570-0139 Fax > > > > > -----Original Message----- > From: Fleming, Cindy R [mailto:[EMAIL PROTECTED]] > Sent: Friday, September 20, 2002 4:08 PM > To: [EMAIL PROTECTED] > Subject: Batch vs real time > > > Could someone please assist me with the following question: > > For the 270/271 and the 276/277 transactions, are payers required to be able > to process these transactions in batch or is real time sufficient? > > Thank you, > Cindy Fleming > > > ********************************************************************** > 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. > > ====================================================== > > 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/. > Posting of advertisements or other commercial use of this listserv is > specifically prohibited. > > > > ********************************************************************** > 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. > > ====================================================== > > 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/. > Posting of advertisements or other commercial use of this listserv is > specifically prohibited. > > > ********************************************************************** > 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. > > ====================================================== > > 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/. > Posting of advertisements or other commercial use of this listserv is > specifically prohibited. > > ********************************************************************** 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. ====================================================== 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/. Posting of advertisements or other commercial use of this listserv is specifically prohibited.
