RE: Route through email and attach EDI files

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

Re: HIPAA Privacy, Security and the Intersection with EDI

Chris I disagree with you statement on small provider systems. I am a vendor on both the institutional and professional side and my clients are mostly the small providers and facilities and am able to generate compliant 837s with the current input except for taxonomy codes and Tax ID numbers of

Electronic Signatures

I don't understand why the comments from CMS re: electronic signatures (supposedly saying they will not be required under the final HIPAA security rule) are relevant here. Who's fooling whom? Are folks suddenly sighing with relief? Encryption is still certainly required, as Rachel said, when us

Route through email and attach EDI files

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

RE: An Overview or Primer Document

Bruce is on the mark when he says that many (I would even argue most) payers will not change their communication methods for HIPAA. There is no mandate to communicate the standard transactions in any particular manner, and mailboxes / secured bulletin boards are a perfectly acceptable manner in w

The payer centric model

Payers are required to use standard transactions if the provider requests that they do so. Somehow the messages have to be gotten to the provider. In the typical supply-chain scenario using VANs and interconnects, the sender merely "pushes" the interchange to his VAN. Then the sender's VAN itsel

RE: An Overview or Primer Document

Ahh, Paul.we used to call it a "technology in search of a market!" Good point. Rachel Foerster Rachel Foerster & Associates, Ltd. Phone: 847-872-8070 -Original Message- From: Paul Weber [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 13, 2002 11:55 AM To: [EMAIL PROTECTED] Subject:

Re: An Overview or Primer Document

Bruce, I believe the "payor mailbox drop" model will remain in existence for some time. As a provider, I will gladly check my "Big Blue" and "Medicare", and several other mailboxes every day if there might be money or claim rejection notices waiting for me. But that delivery model will become

RE: HIPAA Privacy, Security and the Intersection with EDI

Rachel, Regarding your question: "So, would someone please tell me how on earth a "discoverable" CPP and a registry is going to enable any covered entity, whether provider (small or large), payer, or clearinghouse to achieve compliance with the HIPAA EDI requirements by 10/16/03?" I agree in a

RE: HIPAA Privacy, Security and the Intersection with EDI

Chris, I agree that you've identified some issues here, but let's look at things rationally as far as getting "compliant" with the HIPAA EDI requirements is concerned by 10/16/03: 1. The vast majority of physicians and dare I say dentists and other small providers use a practice management syste

Re: HIPAA Privacy, Security and the Intersection with EDI

Hello Gale, Thanks for your encouraging comments. This and some feedback from the AFEHCT folks suggest that the small provider software situation may not be quite as dire as I described in my last post (i.e., 1% compliant claims on 10-16-03). But there is no way to really tell because neither

Re: An Overview or Primer Document

Putting on my provider hat for a moment: I've followed this thread trying to understand how this working paper project benefits my organization (large nationwide provider of ancillary services) as we deal with HIPAA compliance. Frankly, I'm not convinced that this effort helps me right now nor

Re: HIPAA Privacy, Security and the Intersection with EDI

Rachel, I agree with virtually all of your observations regarding our near-term business realities, but I must respectfully disagree with your [eminently rational] conclusions... because they amount to letting small providers "take the bullet" for HIPAA and I don't think HHS, the payor comm

Re: An Overview or Primer Document

There is a common thread that keeps showing up in this discussion that I just cannot get past my reality check mechanism. Payers are required to support the standard transactions. They are not required to transmit them. Rather, in the instances where I have knowledge, Medicaid, Medicare and some

Re: HIPAA Privacy, Security and the Intersection with EDI

So please, I'd appreciate some > succinct words of explanation that one could use when talking to industry > participants about how identifiers, addresses and delivery channels, > elements of the Healthcare Collaboration-Protocol Profile (CPP), discovery > of Healthcare CPPs via a Registry help a