[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: TP EDI Enabled ?
On 16 Jan 2001, at 20:49, William J. Kammerer wrote: > Dear David: > > ...snip.. Many insurers have claim acceptance done through clearinghouses, and therefore might not want (or perhaps even have) direct destination information to be published. Goverment agencies use a similar arangement (DOD comes to mind) and might have similar concerns. > > And when I say legitimate, I don't necessarily mean "known," either: > in Health Care, a provider (doctor or clinic, say) might not be known > to a particular payer (e.g., Insurance company). But they have a > legitimate need to submit a claim to that payer, without any > preexisting trading partner agreement in effect - though HIPAA '96 > provides the legal infrastructure. As long as the doctor is a > recognized submitter (because she's accredited, or affiliated with an > accredited hospital - all vouched for by some CA in the certificate > chain of trust), the insurance company has to take the claim. > Burdening the provider with manually tracking down somebody who can > set her up to submit electronic claims defeats the whole purpose of > open-EDI. > > William J. Kammerer > FORESIGHT Corp. > 4950 Blazer Memorial Pkwy. > Dublin, OH USA 43017-3305 > +1 614 791-1600 > > Visit FORESIGHT Corp. at http://www.foresightcorp.com/ > "Commerce for a New World" > > > ----- Original Message ----- > From: David RR Webber <Gnosis_@compuserve.com> > To: William J. Kammerer <wkammerer@foresightcorp.com> > Cc: ebXML Repository <ebxml-regrep@lists.ebxml.org>; EDI-L Mailing > List <EDI-L@LISTSERV.UCOP.EDU> Sent: Tuesday, January 16, 2001 6:04 PM > Subject: Fw: TP EDI Enabled ? > > > Message text written by "William J. Kammerer" > > > Surely, a powerful, omnipotent and all-encompassing registry > and repository ("Oz"), which can track down all the plumbers > in Cleveland, Ohio (to take one of the examples in a RegRep > e-mail) or tell me who will sell me car stereos and does > Rosetta Net PIP3A4 (a use case in ebXML Registry Services > Version 0.82), could do something as simple as giving me the > public key, the HTTP URL or SMTP e-mail address for the MSH, > and other miscellany of my partner - assuming I can give it > a list of IDs on which it can search. > > The "EDI Yellow Pages" Taylor refers to is touched upon in my original > diatribe "Registry/Repository questions and comments," at > http://lists.ebxml.org/archives/ebxml-regrep/200101/msg00048.html. > > <<<<<<<<<<<<<<<< > > William, > > I would humbly submit that it would only do some. However it would > give you a public email address to whom you could address the query. > > The information in this area seems to me to span business > confidential as well as business public. The registry can only > deal with business public. > > DW. > > > PDP
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC