The "use of process analysis resulting in business scenarios" may be "a critical and essential concept to Open-edi, ebXML and CPP/A," but I doubt we're going to be doing much of that stuff here in ID & Routing. All we have to work with are the existing HIPAA standard transactions - that much is not going to change. We are not redesigning healthcare e-commerce from the ground up, and I doubt many of us would have signed up for this project if that were required.
Dick Brooks, our liaison to the OASIS ebXML CPP/A Technical Committee, has already suggested we make do with the simple default 'file transfer' business process for exchanging HIPAA transactions. There is no need to scare folks into thinking we'll require elaborate business processes. See "RE: CPP Data elements draft for comment" (05-10) at http://www.mail-archive.com/routing%40wedi.org/msg00558.html. The deepest we'll have to get into "business analysis" is to analyze what the HIPAA IG business models already say - like what we'll have to do in order to design the CPP so COB support can be "announced," as I illustrated just a while ago. "Open-edi" is indeed the correct term for describing scenarios of trading that don't involve prior agreement and human intervention between parties; supposedly parties are to agree to conform to certain implementations of "FSV related standards." In effect, this has already been provided for by the HIPAA TCS Reg, which incidentally also supplies the "competent legal environment." I don't mean anything else by the term "Open-edi," and it seems to be consistent with what's said in the Open-Edi Reference Model. I can't imagine - for the purposes of our project - any need for us to get further into the mind-numbing details of FSVs and BOVs and stuff like that. William J. Kammerer Novannet, LLC. Columbus, US-OH 43221-3859 +1 (614) 487-0320 ----- Original Message ----- From: "Rachel Foerster" <[EMAIL PROTECTED]> To: "'WEDi/SNIP ID & Routing'" <[EMAIL PROTECTED]> Sent: Wednesday, 03 July, 2002 08:02 PM Subject: RE: Open-edi, Health Care, ebXML and CPP/A Since the term Open-edi has been used on numerous occasions I felt it important that it be put into the appropriate context of the ISO model and ebXML. Use of the term Open-edi when you actually mean something else can only serve to confuse rather than clarify. Whether one chooses to review the earlier version of the Open-edi Reference Model or the current one being ballotted is irrelevant to having a conceptual understanding of what Open-edi is and how it fits into an overall electronic business framework, including ebXML, from which the CPP/A is drawn. It's also important to know that the CPP/A as presently spec's expects that specific business process scenarios, etc. that each of the trading partner's support be identified. The use of process analysis resulting in business scenarios is a critical and essential concept to Open-edi, ebXML and CPP/A. 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 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.
