After following the discussion now for a few months
I begin to believe that we have not solved routing, one of the most basic
issues of EDI. All this talk about CPP and ebXML makes my head spin; and to be
honest, having my hands full with transaction sets, I don't see myself studying
now XML too.
Why don't we use email as the preferred mode of
routing?
This would solve most problems.
I just started to test my payer oriented software
with a provider software house in India. We tried ftp and were
frustrated. We were fighting firewall issues, I had power outages and
my server was down, my IP lease expired and India is about 12 hours ahead
of me so that we could never communicate in real time.
Moving the communications over to email solved all these problems
and now we can concentrate on transaction set issues.
My 2cents
Martin Scholl
Scholl Consulting Group, Inc. 301-924-5537 Tel 301-570-0139 Fax [EMAIL PROTECTED] www.SchollConsulting.com |
- RE: Route through email and attach EDI files Martin Scholl
- RE: Route through email and attach EDI file... Dekker, Cory
- Re: Route through email and attach EDI ... David A. Feinberg, C.D.P.
- RE: Route through email and attach EDI file... Dekker, Cory
- Re: Route through email and attach EDI file... Paul Weber
- Re: Route through email and attach EDI ... David A. Feinberg, C.D.P.
- Re: Route through email and attach ... Martin Scholl
- Re: Route through email and att... Deepan Vashi
- Need for payor and CH inpu... Christopher J. Feahr, OD
- Re: Need for payor and... Martin Scholl
- Re: Route through email an... William J. Kammerer