I believe "enrollment" goes far beyond just access control. Rather, enrollment is what a payer does for a provider who wishes to submit claims to that payer for payment. The heart of the matter here is the financial aspect of obtaining payment from a payer....as Bruce LeGrand would say.....it's whether someone makes the payroll at the end of the week or not.
A CPP is only one aspect of establishing an electronic messaging interface. Agreeing to it is the other, and the CPA specification from ebXML is what addresses this aspect. Rachel Foerster Principal Rachel Foerster & Associates, Ltd. Professionals in EDI & Electronic Commerce 39432 North Avenue Beach Park, IL 60099 Phone: 847-872-8070 Fax: 847-872-6860 http://www.rfa-edi.com -----Original Message----- From: William J. Kammerer [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 17, 2002 10:46 AM To: WEDi/SNIP ID & Routing Subject: Authentication and Access to the Healthcare CPP Registry Some discussion is going on in the background among the Overview authors about Authentication and access to the Healthcare CPP Registry. The term "enroll" was being bandied about - this time in the context of "enrolling" for access to the Registry. I would use the term "enroll" in a more restricted sense: only when talking about bi-lateral (actually, usually one-sided) negotiation between two parties before actual trading commences. Just because someone is entered in the Healthcare CPP registry, it doesn't necessarily mean payers want to take EDI interchanges from him: payers will probably demand that the provider be "enrolled" (i.e., fill out a bunch of forms). Keep in mind that a vocal minority really wants Open-EDI (i.e., they interpret the TCS rule to say payers have to take in anyone's standard transactions, "enrolled" or not). Pretty much, I'd let anyone register their CPP and search others' CPPs in the CPP Registry as long as they had a certificate that said they had something to do with Healthcare. That "something to do with Healthcare" is hard to define - and even harder to express in X.509 certificates! Is it based on who signs (e.g., in effect the AMA, NCPDP or NAIC) the certificate, or which extensions are added, etc.? This has to be figured out; and since the problem is kind of unique to Healthcare, it will probably have to be done in the ID & Routing group - or even some AFEHCT group. Any ideas? Do we have any PKI or X.509 experts out there? William J. Kammerer Novannet, LLC. Columbus, US-OH 43221-3859 +1 (614) 487-0320 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. 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.
