.
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't
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
.
Dave Minch
TCS Project Manager
John Muir / Mt. Diablo Health System
Walnut Creek, CA
(925) 941-2240
-Original Message-
From: Ronald Bowron [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 09, 2002 1:39 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: Are only 15 characters
-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 the ISA receiver ID enough?
Dave,
Thanks for your detailed summary posts... very helpful! But I
...
Dave Minch
TCS 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
: 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 follow the workflow
below, starting with the responsible party's insurance
-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 Choice, and
besides my
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 I
04:26 PM
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 to
map the identifiers into an address?
It is still trivial and reliable and cheap to do this using the
currently existing DNS, using a small XML tag
Now, as Rachel would say, I think I'm getting wrapped around an axle
with this ISA and GS stuff. After thinking about it, the GS should only
be used for internal routing by the recipient - something we all learned
in EDI 101. No intermediary or communications package should ever have
to drill
well... the small size of the ISA08 field, combined with the variety of
application-specific addressing requirements, and the general reluctance to
require receivers to drill further in to ferret out more addressing
clues... would certainly seem to MANDATE the existence of one or more
Isn't the small size of these identifiers the main reason why we have to
map the identifiers into an address?
It is still trivial and reliable and cheap to do this using the currently
existing DNS, using a small XML tag in the TXT component of the DNS
directory, just like William has his
: 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 stuff. After thinking about
: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 to
map the identifiers into an address?
It is still trivial and reliable
14 matches
Mail list logo