William, I mean that the scope should not be limited to just the current suite of HIPAA-mandated transactions, since there are other transactions in use/to be used. I'm not at all suggesting that this group move into the supply chain sector of health care...that's neither the focus of WEDi (of which this group is a subgroup) nor are there participants here that can articulate the business requirements. And most certainly, stay out of the turf of HL7 and NCPDP.
Rachel -----Original Message----- From: William J. Kammerer [mailto:[EMAIL PROTECTED]] Sent: Friday, May 10, 2002 9:27 AM To: WEDi/SNIP ID & Routing Subject: Re: CPP Data elements draft for comment Rachel: When you say "the scope of this effort should not be limited to the HIPAA transactions, but serve all of health care," what do you mean? For example, even though the NCPDP retail pharmacy transaction is a HIPAA standard transaction, we haven't discussed it much. Can somebody enlighten us on how it is currently used? Are Clearinghouses involved? Can a pharmacy be treated like any other provider? How are NCPDP transactions packaged and identified? And there are certainly other X12 administrative and financial health care transactions that - while not HIPAA standard - will certainly be usable within our framework, e.g, the claims attachment. But were you thinking more broadly? Are you suggesting that we support HL7 clinical data, aside from the HIPAA claims attachment? Or Property and Casualty or Worker's compensation X12N transactions? Or were you thinking of the supply chain side of Health Care? William J. Kammerer Novannet, LLC. Columbus, US-OH 43221-3859 +1 (614) 487-0320 ----- Original Message ----- From: "Rachel Foerster" <[EMAIL PROTECTED]> To: "'WEDI/SNIP Listserve'" <[EMAIL PROTECTED]> Sent: Monday, 06 May, 2002 05:20 PM Subject: RE: CPP Data elements draft for comment If this group starts delving into the data of the various HIPAA transactions I fear it will most certainly veer off track big time. This effort is/should be substantially above the business data level and be dealing with message addressing and various transport methods that may be supported/required by a trading partner. Furthermore, the scope of this effort should not be limited to the HIPAA transactions, but serve all of health care. 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: Michael Mattias/Tal Systems [mailto:[EMAIL PROTECTED]] Sent: Monday, May 06, 2002 1:29 PM To: 'WEDI/SNIP Listserve' Subject: Re: CPP Data elements draft for comment > Developing a requirements document....how novel! Slightly off this topic..? Do we need to have separate work teams for "registry data elements by [business?] transaction?" If so, I can help with 270/271 Eligibility Request/Response pair. I know the '835 Health Care Remittance' pretty well: see http://www.providerpaymentpartner.com for a product to process the 835; but about the only thing Sally Provider would need to know about a payer's remittance capability is, "ANSI Remittance Available Yes or No?". (Unless, of course, Sally is going to set up Ole Doc Smith's office in the registry to help all those payers route 835s to her..) Michael Mattias Tal Systems, Inc. Racine WI [EMAIL PROTECTED]
