I doubt we have the time or wherewithal to develop a managed, virtual
private network (VPN) like the Automotive Network eXchange (ANX). ANX
is a TCP/IP-based private network for the auto industry, and sounds
something like what you're proposing. ANX has its advantages over the
hodgepodge of miscellaneous protocols, point-to-point T1s, and
proprietary networks now used between automakers and their suppliers.
But I wonder why they just didn't build it on top of the public
Internet. ANX would probably say all the standard stuff, like a private
network can guarantee service levels (you always have to add the "for
mission-critical apps") while the public internet is only "Best-effort."
Or ANX is reliable, while the Internet is unpredictable. And the list
can go on and on.
The ubiquitous internet already exists. There's no reason to build a
new infrastructure when the existing one works. Every provider and payer
is hooked up - otherwise how could they get their e-mail and sports
scores? There are workable security protocols already in place. There
are a number of transport and packaging protocols readily available:
EDIINT, e-mail with S/MIME, FTP, etc. Even ebXML Messaging services is
on the horizon.
Private network or public Internet, you still need a "directory." The
DNS "directory" Kepa is proposing, or an equivalent function for
"discovering" trading partners (such as Napster), is still necessary.
Unless I have a directory, how would I know to send claims for payer
so-and-so to this-or-that e-mail address or FTP directory?
William J. Kammerer
Novannet, LLC.
+1 (614) 487-0320
----- Original Message -----
From: "Ronald Bowron" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, 12 February, 2002 12:36 AM
Subject: Re: EDI Addresses and modem mumbo-jumbo
I also found the article interesting. They simply avoided the internet
issue altogether and used their existing private network. So, how do
the other 2 Million players in the Healthcare market take advantage of
this network?
Well, it might be easier to start our own America On-Line, but call it
HIPAA On-Line (HOL) and you don't get true Internet Access. Only
Healthcare Organizations responsible for HIPAA and other Healthcare EDI
transactions will be given access. I'm sure AT&T, WorldCom and Sprint
would be happy to layout the infrastructure for another HOL Internet.
While were at it, let's just make it only support the newest IPv6
technology with a Napster like application protocol. (Hey maybe UUNET
would support this too!) Instead of $21.95 per month, we'll charge
$34.95 per month (to cover IPv6 and additional security features) -
additional IPv4 Internet Access would be an additional $9.95 per month.
For those of you fortunate enough to make the Seattle meeting, be sure
to bring your napkins, I'm sure you'll be able draw this up over a few
drinks and if you can get it up and running in less than 60 days you'll
be one up on NEHEN. Just think, if you took all the current investment
in private network connections from VANS, CH's, Payers, Providers, I'd
bet you could easily justify the expense to create a HOL ("You've got
Interchanges") IPv6 network infrastructure. :)
Not to knock the NEHEN efforts(they solved an immediate business
problem quickly, easily and cost effectively), if they had built it on
IPv6 and established a routing standard that could support the entire
healthcare industry(including small players that cannot afford fiber
links), then they would be way ahead of this routing team. I am curious
to know what the "Gateway" is using to managing the "peer-to-peer"
routing over TCP/IP - I wonder if it's a simple DNS service or a truly a
Napster like service. If every Healthcare institution decided to build
this out - in the end we would have HIPAA On-Line and a Napster like
clients as the primary interface in every covered entity.
The biggest obstacle with the HOL Network is getting the Trading
Partner Agreements established to ensure we address each parties
fiduciary responsibility and that the Govt. doesn't shut us down for
improperly sharing PHI without paying copy right(or should I say
Informediary) fees.
All kidding aside, it is possible isn't it? Would a Napster like model
work better than a DNS model? (Are they one in the same? I'm not
familiar with Napster, never caught the music collection fever)
-RB
