1.) The HIPAA/Base EDI adapter takes XML and creates EDI do***ents with its
corresponding Segment Terminators, Element Delmiters, SubElement
Delimiters
from XML. It also adds a couple of additional features, automatic creation
of 997s, and re****ts to help in troubleshooting erroroneous files.
2.) The Base EDI adapter does some of the standard EDI transactions, the
HIPAA Adapter deal with transactions convered under the HIPAA mandate,
namely 837P, 837I, 837D, 834, 835, 820, 270, 271, 276, 277, and 278 which
are included in the install of the HIPAA accelerator install.
If you are looking at doing healthcare transactions, you want to spend
your
time on the HIPAA Accelerator.
Eric
http://blog.biztalk-info.com
"Chris" <desany@[EMAIL PROTECTED]
> wrote in message
news:%23bV3iBXcHHA.3616@[EMAIL PROTECTED]
>I need to create 837P (claim-professional) messages. I noticed the
schemas
>in c:\program files\Microsoft Accelerator for HIPAA
>3.3\HIPAA_EDI\Adapter\EDI Schemas\004010A1\Claim-Professional (837P). I
can
>probably muddle through and create a map from my source file (coming from
>mainframe) and map to this schema (although I can't find do***entation on
>what the nodes in 837P actually mean). I have a few questions:
>
> 1.) Should I be looking at the "adapters" themselves, and if so, what
> does this get me beyond just creating 837P messages from the schema (if
> that's all I need to do)? What does the adapter in gerenal really do?
(I
> do know what the Oracle adapter does, though)
> 2.) If I need to look at the adapter, what's the difference between the
> base EDI adapter and the HIPAA_EDI adapter (which I do have), and whch
one
> should I focus on for my purposes?
>
> Any help would be greatly appreciated,
>
> Chris
>
>
|
