RE: Are only 15 characters in the ISA receiver ID enough?

2002-04-11 Thread Robert Huffman
. Thanks, Bob Huffman RealMed Corporation Indianapolis, Indiana -Original Message- From: Rachel Foerster [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 11, 2002 11:23 AM To: [EMAIL PROTECTED] Subject: RE: Are only 15 characters in the ISA receiver ID enough? Ron, while I don&#

RE: Are only 15 characters in the ISA receiver ID enough?

2002-04-11 Thread Rachel Foerster
ubject: RE: Are only 15 characters in the ISA receiver ID enough? Rachel, You may recall that we had submitted definitions for ISA sender and ISA receiver that I thought were considered acceptable. The basic concept is that the sender is the entity responsible for creating the exchange and it'

RE: Are only 15 characters in the ISA receiver ID enough?

2002-04-09 Thread Dave Minch
: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: Are only 15 characters in the ISA receiver ID enough? Rachel, You may recall that we had submitted definitions for ISA sender and ISA receiver that I thought were considered acceptable. The basic concept is that the sender is the entity responsib

RE: Are only 15 characters in the ISA receiver ID enough?

2002-04-09 Thread Ronald Bowron
Rachel, You may recall that we had submitted definitions for ISA sender and ISA receiver that I thought were considered acceptable. The basic concept is that the sender is the entity responsible for creating the exchange and it's contents and the receiver is responsible to processing the content

RE: Are only 15 characters in the ISA receiver ID enough?

2002-04-05 Thread Rachel Foerster
stopher J. Feahr, OD [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 04, 2002 8:48 PM To: Dave Minch; '[EMAIL PROTECTED]' Subject: RE: Are only 15 characters in the ISA receiver ID enough? Dave, Thanks for your detailed summary posts... very helpful! But I was under the impression that the

RE: Are only 15 characters in the ISA receiver ID enough?

2002-04-05 Thread Dave Minch
b and host the database myself... Dave Minch T&CS Project Manager John Muir / Mt. Diablo Health System Walnut Creek, CA (925) 941-2240 -Original Message- From: William J. Kammerer [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 04, 2002 9:32 AM To: WEDi/SNIP ID & Routing Subject:

RE: Are only 15 characters in the ISA receiver ID enough?

2002-04-05 Thread Dave Minch
S Project Manager John Muir / Mt. Diablo Health System Walnut Creek, CA (925) 941-2240 -Original Message- From: Christopher J. Feahr, OD [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 04, 2002 6:48 PM To: Dave Minch; '[EMAIL PROTECTED]' Subject: RE: Are only 15 characters in t

RE: Are only 15 characters in the ISA receiver ID enough?

2002-04-04 Thread Christopher J. Feahr, OD
Dave, Thanks for your detailed summary posts... very helpful! But I was under the impression that the ISA08 is always intended to be the ID of the "next destination" for the interchange, rather than the ID of the payor or "plan" (in the case of a claim), as you seem to be suggesting here. Am

RE: Are only 15 characters in the ISA receiver ID enough?

2002-04-04 Thread Rachel Foerster
w.rfa-edi.com -Original Message- From: William J. Kammerer [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 04, 2002 11:32 AM To: WEDi/SNIP ID & Routing Subject: Re: Are only 15 characters in the ISA receiver ID enough? Dave: I took a look at my insurance card for Anthem Community Ch

Re: Are only 15 characters in the ISA receiver ID enough?

2002-04-04 Thread William J. Kammerer
ch" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, 02 April, 2002 09:36 PM Subject: RE: Are only 15 characters in the ISA receiver ID enough? If I can sum up the last few days of discussion that I have just waded through: as a transaction sender I should be able to fo

Re: Are only 15 characters in the ISA receiver ID enough?

2002-04-03 Thread William J. Kammerer
eahr, OD" <[EMAIL PROTECTED]>; "William J. Kammerer" <[EMAIL PROTECTED]>; "WEDi/SNIP ID & Routing" <[EMAIL PROTECTED]> Sent: Tuesday, 02 April, 2002 04:26 PM Subject: Re: Are only 15 characters in the ISA receiver ID enough? Isn't the small size of thes

RE: Are only 15 characters in the ISA receiver ID enough?

2002-04-02 Thread Dave Minch
: Kepa Zubeldia [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 02, 2002 1:27 PM To: Christopher J. Feahr, OD; William J. Kammerer; WEDi/SNIP ID & Routing Subject: Re: Are only 15 characters in the ISA receiver ID enough? Isn't the small size of these identifiers the main reason why we have

RE: Are only 15 characters in the ISA receiver ID enough?

2002-04-02 Thread David Frenkel
- From: William J. Kammerer [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 02, 2002 11:24 AM To: WEDi/SNIP ID & Routing Subject: Re: Are only 15 characters in the ISA receiver ID enough? Now, as Rachel would say, I think I'm getting "wrapped around an axle" with this ISA and GS st

Re: Are only 15 characters in the ISA receiver ID enough?

2002-04-02 Thread Kepa Zubeldia
r's NAIC company code in the ISA08 receiver field to distinguish > >between batch and real-time? > > > >William J. Kammerer > >Novannet, LLC. > >+1 (614) 487-0320 > > > >- Original Message - > > From: "William J. Kammerer" <[EMAI

Re: Are only 15 characters in the ISA receiver ID enough?

2002-04-02 Thread Christopher J. Feahr, OD
stinguish >between batch and real-time? > >William J. Kammerer >Novannet, LLC. >+1 (614) 487-0320 > >- Original Message ----- >From: "William J. Kammerer" <[EMAIL PROTECTED]> >To: "WEDi/SNIP ID & Routing" <[EMAIL PROTECTED]>

Re: Are only 15 characters in the ISA receiver ID enough?

2002-04-02 Thread William J. Kammerer
istinguish between batch and real-time? William J. Kammerer Novannet, LLC. +1 (614) 487-0320 - Original Message - From: "William J. Kammerer" <[EMAIL PROTECTED]> To: "WEDi/SNIP ID & Routing" <[EMAIL PROTECTED]> Sent: Tuesday, 02 April, 2002 11:51 AM Subject:

Are only 15 characters in the ISA receiver ID enough?

2002-04-02 Thread William J. Kammerer
Chris: We probably shouldn't call ISA08 an "EDI Address." It's the recipient's EDI Identifier. An "EDI Address," as Peter Barry would remind us, is all the technical mumbo-jumbo that defines the protocols, port addresses and other desiderata for moving EDI data to a particular point (e.g., FTP