William, Sorry for the long delay, I've been traveling (again).
>In the matrix Chris developed for the Elements of the >Healthcare Collaboration-Protocol Profile, please distinguish between >stuff which is native to ebXML (I suspect this includes certificate >handling) and that stuff which is completely new and not thought of by >the ebXML people. We'll have to have some organized manner, perhaps in >the form of a "subsidiary" schema, to give the OASIS ebXML Technical >Committee to show our new elements which pertain to Healthcare EDI. I'll coordinate with Dale Moberg to accomplish this. >Actually, is there any possibility that our "kind" of stuff (e.g., which >transactions are supported, with their start dates) is more properly >part of a Business Process rather than an ebXML CPP? If so, then we >might also have to "liase" with the UN/CEFACT ebTWG eBusiness Transition >Working Group, at http://www.ebtwg.org/ - providing yet another >opportunity for "volunteers" who are looking for work to do. Given that HIPAA transactions are X12 only I would suggest that this group elect to use a "file transfer" business process for exchanging HIPAA transactions and avoid the complexities of the "deeper" business processes (Claim/enrollment business processes within the CPP). (Whew, now I only have 173 more messages to process.) Regards, Dick Brooks Systrends, Inc 7855 South River Parkway, Suite 111 Tempe, Arizona 85284 Web: www.systrends.com <http://www.systrends.com> Phone:480.756.6777,Mobile:205-790-1542,eFax:240-352-0714 -----Original Message----- From: William J. Kammerer [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 09, 2002 10:53 AM To: WEDi/SNIP ID & Routing Subject: Re: CPP Data elements draft for comment Dick: A lot of this security and certificate stuff is already in the ebXML CPP, though I don't know how inextricably it's tied into the business process or transport mechanisms - neither of which we'll probably be using in our recommendations, unless we come up with a default "legacy" EDI business process. In the matrix Chris developed for the Elements of the Healthcare Collaboration-Protocol Profile, please distinguish between stuff which is native to ebXML (I suspect this includes certificate handling) and that stuff which is completely new and not thought of by the ebXML people. We'll have to have some organized manner, perhaps in the form of a "subsidiary" schema, to give the OASIS ebXML Technical Committee to show our new elements which pertain to Healthcare EDI. Actually, is there any possibility that our "kind" of stuff (e.g., which transactions are supported, with their start dates) is more properly part of a Business Process rather than an ebXML CPP? If so, then we might also have to "liase" with the UN/CEFACT ebTWG eBusiness Transition Working Group, at http://www.ebtwg.org/ - providing yet another opportunity for "volunteers" who are looking for work to do. William J. Kammerer Novannet, LLC. Columbus, US-OH 43221-3859 +1 (614) 487-0320 ----- Original Message ----- From: "Dick Brooks" <[EMAIL PROTECTED]> To: "joe mcverry" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, 05 May, 2002 07:05 PM Subject: RE: CPP Data elements draft for comment Joe McVerry wrote: >Should public encryption keys be available in this template? IMO, yes. Along with other items needed to enable E-Commerce (e.g. self signed certificates for SSL, public keys for encryption, public keys for digital signature verification, Certificate Revocation List information). Dick Brooks Systrends, Inc 7855 South River Parkway, Suite 111 Tempe, Arizona 85284 Web: www.systrends.com <http://www.systrends.com> Phone:480.756.6777,Mobile:205-790-1542,eFax:240-352-0714
