Perhaps instead of rejecting it, you could return a 271 signifying that you
need more information, such as the member id.



                                                                                       
                        
                      Nick Van Kleeck                                                  
                        
                      <nick.vankleeck@heal         To:      "'[EMAIL PROTECTED]'" 
<[EMAIL PROTECTED]>  
                      thtrio.com>                  cc:                                 
                        
                                                   Subject: rejecting 270 transactions 
with dependent loops    
                      09/23/02 05:27 PM                                                
                        
                      Please respond to                                                
                        
                      transactions                                                     
                        
                                                                                       
                        
                                                                                       
                        
                                                                                       
                        




The 270-271 IG is clear that if a patient can be uniquely identified to an
information source, that patient's information should be passed at the
subscriber hierarchical level, "whether he or she is a child, spouse, or
the
actual subscriber to the plan" .  (pg 13).  Since this is the case for all
of our trading partners,  we are considering rejecting any transactions
that
pass a dependent loop as being incorrect.  Can anyone forsee any problems
with this?

We clearly won't be able to handle any transactions that use the "second
approach" outlined by the IG, where dependents cannot be uniquely
identified, but since we don't trade with any such systems, I can't see a
down side.



**********************************************************************
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.

Reply via email to