Much food for thought on this thread, for certain. Re: Privacy, doen't that dialogue belong on the SNIP Privacy listserver, or on hipaalive? This testing subworkgroup is within the SNIP Transactions workgroup, and doesn't necessarily have hipaa privacy expertise...and there will continue to be plenty of e-mail related to the Transactions testing issues, we may not want to distract folks with privacy issues, which are aplenty! But, while we're on this, and fyi: I think JCAHO is integrating HIPAA Privacy standards into their accreditation process...
A concern that I have re: developing comprehensive and industry-wide transaction certification standards is timing - JCAHO, (which, by the way, I think uses the word "accredited" and not "certified"), is 50 years old, and their standards have been evolving for that long. New standards are published in draft, commented on, revised, tested, and then (a subset) rolled out. For some of their standards, I've seen the process take years - and I don't believe new accreditation criteria have ever been implemented in anything less than a year. HIPAA won't wait that long - and imho it shouldn't, There is plenty of precedence for entrepreneurially-defined certification standards - Microsoft-certified system engineers, for example. It's not unreasonable for a private entity to clearly define certification criteria and then give a stamp of approval to entities that meet that criteria. It's a quicker process - whether or not it is the best process is determined by the market - it IS a quicker process. In implementing transactions and code sets standardization, trading communities will continually identify new ambiguities and bugs in their internal and external tools - it's the nature of the HIPAA beast. (All the beast needs is love in order to become a prince! Think Beauty and the Beast, for those w/o kids I'd suggest renting a kid and the movie, it's good!). Sorry for the digression - In implementing transactions and code sets standardization, trading communities will continually identify new ambiguities and bugs in their internal and external tools. And as particular standards are stablized, attention will turn to less mature standards, so the issue resolution process needs to be continuous. If trading communities cluster together to accept issue resolutions, create infrastructure to distribute information about the resolutions, and implement those resolutions, well, that's implementation! Third party certification - whatever certification tool or vendor the trading community selects - should be the hub at the center of the process if the process is to be efficiently executed. My thoughts, thanks for your consideration! - Cy Cynthia Korman ----- Original Message ----- From: "Chris Brancato" <[EMAIL PROTECTED]> To: "WEDI SNIP Testing Subworkgroup List" <[EMAIL PROTECTED]> Sent: Thursday, December 19, 2002 9:51 AM Subject: RE: RE: NCQA Certifies Compliance SNIP Comes Up Short > Rama, Maracallee and John, I am enjoying the discourse on TNC. I'm very > interested in what you think specifically to NCQA's new Privacy > "certification"?. > > -----Original Message----- > > > > --- > 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/. These listservs should not be used for commercial marketing purposes or discussion of specific vendor products and services. They also are not intended to be used as a forum for personal disagreements or unprofessional communication at any time. > > You are currently subscribed to wedi-testing as: [EMAIL PROTECTED] > To unsubscribe from this list, go to the Subscribe/Unsubscribe form at http://subscribe.wedi.org or send a blank email to [EMAIL PROTECTED] > If you need to unsubscribe but your current email address is not the same as the address subscribed to the list, please use the Subscribe/Unsubscribe form at http://subscribe.wedi.org --- 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/. These listservs should not be used for commercial marketing purposes or discussion of specific vendor products and services. They also are not intended to be used as a forum for personal disagreements or unprofessional communication at any time. You are currently subscribed to wedi-testing as: [email protected] To unsubscribe from this list, go to the Subscribe/Unsubscribe form at http://subscribe.wedi.org or send a blank email to [EMAIL PROTECTED] If you need to unsubscribe but your current email address is not the same as the address subscribed to the list, please use the Subscribe/Unsubscribe form at http://subscribe.wedi.org
