I sent it to the listserv as others might find benefit. If I'm not suppose to, I'm sure someone will yell at me. It's missing the IEA because it is a subset of a real 1+ megabyte file, I wasn't going to hand 'sanitize' an entire file by hand; thus, I sent you the first GS/GE segment combination.
Though it is an old file, the only difference between it and a later 4010 version is centuries in the dates and a possibility of a minor few other variations. I'll respond to the rest of your message a little later (I have a meeting to attend). ----- Original Message ----- From: "William J. Kammerer" <[EMAIL PROTECTED]> > John: > > Sure, I would like to discuss it! It's a handsome, if really old, 835, > indeed... except for the missing IEA. But did you mean to send this > privately? - it ended up going to the listserve. But in any case, it's > a good example to prompt questions which aid in our analysis. It's your > choice whether you want to answer the questions on the list, or to me > privately. > > It looks like both the sender and receiver are mutually defined (the > dreaded ZZ qualifiers). What are they supposed to be? - what is the > 9000000380, and who is DD0064? Were these sanitized, too, or are they > what was actually used? Actually it would help if only PHI (the > subscriber, patient and claim detail) was "sanitized" or deidentified - > the payee, payer and bank are the parties we want to want to know > everything about, and need the real detail. There's nothing secret > about these parties - and these are the very parties for whom we're > trying to figure out things like how they address each other. > > Other questions: Did this remittance go through a Clearinghouse? Or > point to point? Did it go straight to the provider, or to an > intermediary like a billing service? Who chose the sender and receiver > IDs to use? The payment was sent separately by ACH, but the ABA routing > code of the bank - and the account number - were "sanitized" away; at > least the ABA routing code would have been relevant if we were looking > at a payment order to a bank (how does a bank require the ISA to be > addressed?). Some providers might be queasy about having their account > number shared (though it's certainly not PHI) on a listserve, so it's > reasonable to switch a few digits around; but think about it: every > grocery and dry cleaners that I have ever written a check to now has my > bank's ABA routing code and my account number....so what?? > > Anyway, thanks for starting the ball rolling! We need detail, detail, > detail! > > William J. Kammerer > Novannet, LLC. > +1 (614) 487-0320 > > ----- Original Message ----- > From: "John Bristor" <[EMAIL PROTECTED]> > To: "WEDi/SNIP ID & Routing" <[EMAIL PROTECTED]> > Cc: "John Bristor" <[EMAIL PROTECTED]> > Sent: Friday, 15 March, 2002 01:43 PM > Subject: Re: Identifiers > > > Here's an example of an old 835 (sanitized).. would you like to discuss > it? > ------------------------------------------------------------------------ > -- > > ISA*00* *00* *ZZ*9000000380 *ZZ*DD0064 > *950510*0320*U*00303*951300304*0*P*>~ > GS*HP*9000000380*42T091*950510*0066*209225*X*003030M~ > ST*835*1076~ > BPR*I*18788.66*C*ACH************950511~ > TRN*1*000000000000000000000000000000*9000000380*000209225~ > REF*F5*ACPS99~ > N1*1P*Hospital Name~ > N3*Hospital Address Line~ > N4*ANYWHERE*SC*999999999~ > LX*950911~ > TS3*42T091*11*950930*2*21328.04*20901.64*426.40**18788.66**2112.98****** > ***4 > 26.40~ > TS2***********2*22*22~ > CLP*H031025061*01*6779.09*6832.24***0195117435150*11*1*01*462~ > CAS*CO*89*172.70**A2*-225.85**96*172.70~ > CAS*OA*B3*6606.39~ > NM1*QC*1*LASTNAME*FIRSTNAME***HN*248599999A~ > MIA*8**************8~ > REF*EA*H018999~ > DTM*232*950320~ > DTM*233*950328~ > CLP*H030578999*01*14548.95*11956.42***0195117447999*11*1*01*462~ > CAS*CO*89*253.70**A2*2338.83**96*253.70~ > CAS*OA*B3*14295.25~ > NM1*QC*1*LASTNAME*FIRSTNAME****HN*326096999A~ > MIA*14**************14~ > REF*EA*H206999~ > DTM*232*950303~ > DTM*233*950317~ > SE*27*1076~ > GE*1*209225~ > > > > >
