The 270/271, 278, and 276/277 guides all state that the real-time response should be delivered within 60 seconds. The 270/271 and 278 guides goes further, stating that either the response, a 997, or a TA1 must be delivered within the given time frame. It also limits the number of inquiries on a real-time 270/278 to one--there is no such limitation in the 276 guide, which I believe is an important oversight that should be considered for inclusion in trading partner agreements.
We are currently testing real-time 270 exchanges using a 'home-grown' tool which connects externally using TCP/IP. The port connection is maintained with poll messages, and the response is returned within one minute. If, due to some internal error, no response arrives from our backend system to the 'front door' for delivery by the end of a configurable time, a default response is sent to assure compliance with the 60 sec requirement. Monitoring and managing turn-around time is easy when the provider is connected directly, but difficult to impossible when the inquiry is from a clearinghouse, since there is no way to know or control the throughput of the entire system. -----Original Message----- From: Pulver, Scott [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 24, 2002 5:29 PM To: [EMAIL PROTECTED] 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. CONFIDENTIALITY NOTICE: This E-Mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you have received this communication in error, please do not distribute and delete the original message. Please notify the sender by E-Mail at the address shown. Thank you for your compliance. ********************************************************************** 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.
