We currently have a process that checks each claim that comes in against our core 
system to see if it is a duplicate.  The current process will cut that claim from the 
file if it is.
We aren't so concerned about single claims being sent as dupes here and there, we're 
more concerned about duplicate files.  I know that our translator provides checking of 
the X12 interchange control number for duplicates.  But this will only be effective if 
the TP sends the SAME file multiple times, it won't prevent multiple files with 
different int. ctrl nos. from getting loaded. We certainly don't want to get into the 
business of cutting claims in X12.  What are other payers planning to do in the HIPAA 
world?

Thanks.


Jonathan Fox
eCommerce Analyst
Independent Health

CONFIDENTIALITY NOTICE. This e-mail and attachments, if any, may contain confidential 
information which is privileged and protected from disclosure by Federal and State 
confidentiality laws, rules or regulations.  This e-mail and attachments, if any, are 
intended for the designated addressee only .  If you are not the designated addressee, 
you are hereby notified that any disclosure, copying, or distribution of this e-mail 
and its attachments, if any, may be unlawful and may subject you to legal 
consequences.  If you have received this e-mail and attachments in error, please 
contact Independent Health immediately at (716) 631-3001 and delete the e-mail and its 
attachments from your computer.  Thank you for your attention.



To be removed from this list, go to: http://snip.wedi.org/unsubscribe.cfm?list=business
and enter your email address.

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.

Reply via email to