The latest grain of sand in the gearbox.
Since the Employer ID Final Rule published yesterday affects ALL uses of the
EIN in healthcare, you have to be careful in using the brand new HIPAA
Standard EIN, which is 10 positions long: two digits, one hyphen, seven
digits, as in 00-000. You MU
Peter,
Is this theend of ebXML? I hope they change their mind and start offering a
royalty free license. In the meantime... Viva EDI!
Kepa
On Wednesday 17 April 2002 01:55 pm, [EMAIL PROTECTED] wrote:
> Interesting article.
>
> http://techupdate.zdnet.com/techupdate/stories/main/0,14179,28
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 set
A sad note...
Back in 1994 I asked all my providers at Synaptek (a clearinghouse) to
give us power of attorney so we could enroll them with all the payers in
the country that required provider enrollment. Within three months of
Synaptek starting to use the power of attorney enrollments, HCFA
Chris,
For several years HCFA had been working on "payerID". Then HIPAA
specified Plan ID in the law. That is one of the reasons why the
regulations have not come out yet. It took a while to figure out how the
Plan ID, which is what the HIPAA law specifies, relates to the payerID,
which is w
William,
Some thoughts...
In your nslookup use -type=MX instead of "all". More concise response.
We could put several MX records for you, with different priorities.
You could use the TXT record instead of the MX record.
The TXT record does not have a "priority" associated with it, like the
M
Dave,
The dreamer in me was thinking that perhaps the industry would converge
on a simple solution without having to be compelled by the government.
Is that too idealistic?
Kepa
Dave Minch wrote:
> Kepa,
> In any proposal to create a domain name service, whether distributed or
> centralized
f the things that the DNS server's MX record points to?
>
> Thanks,
> Chris
>
> At 08:36 AM 2/13/02 -0700, Kepa Zubeldia wrote:
>
>> Chris,
>>
>> Nothing is "automatic", but a provider that designates a clearinghouse
>> as its delivery
Chris,
Nothing is "automatic", but a provider that designates a clearinghouse
as its delivery point would also designate the clearinghouse as its DNS
server. A provider that has its own "server" acting as its own delivery
point, would have to point its DNS server to the EDI server acting as a
William,
As it turns out, it is likely that my local BCBS will have a good number
of PlanIDs under HIPAA. Perhaps in the hundreds, as Regence BCBS has a
multitude of plans in several states.
A provider that sees a HIPAA PlanID and has a connection with a
clearinghouse as well as a connection
anyone creating a multi-payor 837 would already have to
> know which clearinghouse to send it to and would, therefore, not need
> this address discovery process (?).
> -Chris
>
> At 03:22 PM 2/9/02 -0700, Kepa Zubeldia wrote:
>
>> Ronald,
>>
>> Let me clari
Ronald,
Let me clarify something that may not have been properly expressed. One
of the problems we are facing today, and will face more acutely tomorrow
with the HIPAA PlanID, is how to identify the entry point for a plan ID.
The entry point may not be the payer, but a PPO instead. Or we ma
Ronald,
Here is what I have in mind...
Let's say that the ISA looks like:
ISA*00* *00* *30*731234567 *33*60054
*020207*1230*U*00401*1*0*T*>~
This represents a transmission from EIN:731234567 to NAIC:60054
The first step is to find who is the DNS server for the NA
or
repricing, or needs to reject them back to the provider as being sent to
the "wrong" address.
For the addresses to work, the trick is in a couple of areas:
completeness of the address for the intended routing mechanism, and
mapping between the identity and the address.
Complete add
William,
Could it be convened on Monday?
Kepa
William J. Kammerer wrote:
> Due to the amount of interest that the topic of EDI IDs and routing has
> generated, there is a possibility that more time for a Face-to-Face
> discussion at the Seattle X12 Trimester meeting will be needed.
>
> We ha
Let me add something here...
It would be trivial to create a database in which you could take the
NAIC or DUNS number from the ISA and look up the electronic route to
that entity, except... 1) who would create or maintain such a large
database? 2) a centralized database could pose a security
Here is a thought...
The joint effort of AFEHCT and WEDI on Internet interoperability could
be used as a test bed for the addressing and routing solution that is
being worked on by this WEDI SNIP group on routing. This new AFEHCT and
WEDI workgroup is just starting and I think the scope of bo
Bob,
Intentionally I did not put everything in one message, as I don't want
to make people choke, and I want to truly explore different
possibilities and different options.
As it has been pointed out, the DNS/MX problem does not solve the
selection of transport mechanism or security and authe
hope it ends up being useful in finding a solution to our problem.
Kepa
William J. Kammerer wrote:
> Thanks to Kepa Zubeldia and Dick Brooks for their enlightening
> historical perspectives on the evolution of DNS. I'm thankful the
> graybeards of our industry are around to share
ion comes into existence?
>
> Rachel
> Rachel Foerster
> Rachel Foerster & Associates, Ltd.
> Phone: 847-872-8070
>
>
> -Original Message-
> From: Kepa Zubeldia [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 30, 2002 3:18 PM
> To: WEDi/SNIP ID &
Before you read this, take a seat and get some popcorn...
Since history gives us a mechanism to not repeat the same mistakes all
over again, let me give a little history on Internet and pre-Internet
email addresses, in case we can learn something from it. There are some
known pioneers in this fi
Rachel,
Even though providers may participate in only as handful of health
networks, they routinely see patients that are covered by hundreds of
payers. THe exception could be some providers in very small rural
communities, where there is one prevailing employer. Other than those,
most provider
22 matches
Mail list logo
