|
Cory,
So, out of curiosity on a Friday,
what methods and/or routings of communications do you think would
satisfy the real time requirements of the 270/271, 276/277, and 278
Implementation Guides?
Also, would you be measuring the complete end-to-end
[i.e., start-of-communications to payer processing through
end-of-communications] time, or just the turn-around time on the payer
processing system once a message is received?
Dave
Feinberg
Rensis
Corporation
206-617-1717
----- Original Message -----
Sent: Thursday, June 13, 2002 4:38
PM
Subject: RE: Route through email and
attach EDI files
I'd
think that e-mail is one viable mechanism for a small-volume batch
arrangement. We plan to use it as such with at least one
TP.
However, I suspect that e-mail falls well short of
the "2 to 30-seconds" definition for real-time [4010X092 270/271 IG; page 14,
4th paragraph, "Real Time Transactions ... should not exceed one minute"], and
it probably represents a dis-incentive if the payer also supports a real-time
Web or DDE interface.
I'd
say "close ... but no cigar" as a complete HIPAA routing
solution.
-Cory
Cory Dekker
GWL-EBIS HIPAA Project
Analyst
303/737-2022 or 303/522-8804 (Cell)
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.
- email is secure. Encrypting email with
PGP, Pretty Good Privacy is cheap, proven and common place
- Attachments can be relatively large, mega
bytes if need be and numerous too
- routing of email is long solved and works
great as we all know
- Identifiers are left between you and your
trading partner. We don't have to invent or find a unique ID as long
it is 15 digits long.
- virus filters and such are widely available
and HIPAA Security can be attained at low costs
- By having a robot check the inbox every minute
or so, "realtime" or something reasonably close to that can be
achieved.
- TA1, 997,271,277 ..... are send back as
an attachment
- You can also send back the detailed analysis
information. EDI compliance checker software produces verbose
output and when you send that back in the body of the email to the
message provider, you can give near instant feedback and go through the
training and testing phase faster.
- Off course, if you need to submit 10gig of EDI
to CMS, this does not work, but for the traffic between providers and
payers, email would solve the routing question
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
|
