87-0320
- Original Message -----
From: "Ronald Bowron" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, 21 June, 2002 01:39 PM
Subject: Re: Route through email and attach EDI files
As a long time fan of efficient transfer of business data (i.e. EDI vs.
XML), I
As a long time fan of efficient transfer of business data
(i.e. EDI vs. XML), I've often wondered why the Open Source community has never
taken EDI under it's wing like they have other services (FTP, SMTP,
Telnet). I guess the market wasn't there.
Anyway, to keep in line with our efforts
lliam J. Kammerer
Novannet, LLC.
Columbus, US-OH 43221-3859
+1 (614) 487-0320
- Original Message -
From: "Martin Scholl" <[EMAIL PROTECTED]>
To: "William J. Kammerer" <[EMAIL PROTECTED]>; "WEDi/SNIP ID &
Routing" <[EMAIL PROTECTED]>
Sen
WEDi/SNIP.ID.&.Routing[routing]@wedi.org.comp
From: William.J.Kammerer[wkammerer]@novannet.com.comp
Sender: [EMAIL PROTECTED]
Subject: Re: Route through email and attach EDI files
Deepan:
Assuming your Practice Management System processes HIPAA standard
transactions, and you intend to transport
Kammerer"
<[EMAIL PROTECTED]>; "WEDi/SNIP ID & Routing" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Tuesday, 18 June, 2002 05:05 AM
Subject: Re: Route through email and attach EDI files
For payers it might be easy to decide on their Internet strategy. I
re
- Original Message -
From: "Martin Scholl" <[EMAIL PROTECTED]>
To: "William J. Kammerer" <[EMAIL PROTECTED]>; "WEDi/SNIP ID & Routing"
<[EMAIL PROTECTED]>
Sent: Tuesday, June 18, 2002 5:51 AM
Subject: Re: Route through email and attach EDI fi
Message-
From: Martin Scholl
To: David A. Feinberg, C.D.P.; WEDi/SNIP ID & Routing
Sent: 6/15/02 6:24 AM
Subject: Re: Route through email and attach EDI files
Well Dave,
Sure it is possible to use the body of the email for the transmission.
You can concoct a gruel email with multiple transac
- Original Message -
From:
David A.
Feinberg, C.D.P.
To: [EMAIL PROTECTED]
Sent: Saturday, June 15, 2002 1:49
AM
Subject: Re: Route through email and
attach EDI files
Paul, Martin, Cory, et.
al.,
Since it's been a verrry long day
this Friday,
ubject: Re: Route through email and
attach EDI files
I see Martin's 2 cents and raise a nickle. He makes a good point ---
especially for small volume batches. However where things get dicey is when
attachments start getting too large to get through firewalls and/or negatively
PROTECTED]
- Original Message -
From:
Dekker,
Cory
To: WEDi/SNIP ID & Routing
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
ar
I see Martin's 2 cents and raise a nickle. He makes a good point --- especially for small volume batches. However where things get dicey is when attachments start getting too large to get through firewalls and/or negatively impact network performance. For example, I worked for a large west coast HM
m: Deepan Vashi
[mailto:[EMAIL PROTECTED]] Sent: Friday, June 14, 2002 7:58
AMTo: Dekker, CorySubject: Re: Route through email and
attach EDI files
Dear Martin & Cory
From Provider's perspective are we looking at
multiple routing mechanism ?
1) Using modem and tel
Title: Message
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
paragrap
13 matches
Mail list logo
