From: Dekker, Cory [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 20, 2002 5:56 PM
To: '[EMAIL PROTECTED]'
Cc: '[EMAIL PROTECTED]'
Subject: Which REF are you!?
Hi all,
In the 837P (v4010X098), Loop ID 2010AA [BILLING PROVIDER NAME], there are 2 Situational REF Data Segments, with identical Data Elements; "BILLING PROVIDER SECONDARY IDENTIFICATION" and "CREDIT/DEBIT CARD BILLING INFORMATION".
Each REF segment can be repeated up to 8 times and both support the same REF Data Elements, including the REF01 ID codeset. Like most situational codesets, the Internal HIPAA codeset values are distinct by Data Segment, except for ONE code value: BOTH of them allow "LU" [Location Number]. Both are SITUATIONAL segments, such that it appears that it could be possible to encounter the latter, without the former, and by the data alone, not easily know which data segment you are looking at.
In reading and re-reading the IG, I have been unable to find a clue as to how to know in a grouping of 4 or 5 REF's in a row, where does SECONDARY INFO end, and BILLING INFO begin. I also found no mention of this problem in either the Errata or the Addenda drafts. Granted, as a Payer, we should never receive the second data segment. However, in theory, our HIPAA compliance validator should be recognizing when it might occur, and reject any transaction which contains it. [yes, I know, "he implied they might reject a claim!"... I'm still struggling with it myself...]
Am I missing something? Am I reading things correctly? Has anyone encountered this before?
Has anyone resolved this, and if so, how?
Thanks in
advance for all assistance...
-Cory
P.S. Sorry for the cross-post, but I see this as both a transactional recognition issue, as well as an internal situational codeset issue.
To be removed from this list, go to: http://snip.wedi.org/unsubscribe.cfm?list=codeset
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.
To be removed from this list, go to: http://snip.wedi.org/unsubscribe.cfm?list=codeset
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.