Hi,
I'm trying to convert a flat file to an 834 message using
Biztalk 2002 and the HIPAA Accelerator.  I've set up the
source document spec and the mapping to the 834 template
provided with the HIPAA Accelerator but when I test it the
output 834 has non standard prefixes for the message
segments. Eg. ISA_InterchangeControlHeader instead of ISA

Do I need to create a destination document spec or can the
HIPAA Accelerator documents be used directly to produce
valid X12?

Thanks

mary

[ Post a follow-up to this message ]

Not sure what's happening, but I know that the HIPAA Accelerator can produce
valid XML.

Did you use the Trading Partner Manager to set up your channel?

--- Nick
<anonymous@discussions.microsoft.com> wrote in message
news:074a01c3de9d$fa342920$a301280a@phx.gbl...
> Hi,
> I'm trying to convert a flat file to an 834 message using
> Biztalk 2002 and the HIPAA Accelerator.  I've set up the
> source document spec and the mapping to the 834 template
> provided with the HIPAA Accelerator but when I test it the
> output 834 has non standard prefixes for the message
> segments. Eg. ISA_InterchangeControlHeader instead of ISA
>
> Do I need to create a destination document spec or can the
> HIPAA Accelerator documents be used directly to produce
> valid X12?
>
> Thanks
>
> mary

[ Post a follow-up to this message ]

No.  I was testing the map via the Mapper tool only.  I'll
set up a channel and see if the weird prefixes disappear

I couldn't find any documenation on generating X12 using
the HIPAA Accelerator - do you any good resources that
cover this?

>-----Original Message-----
>Not sure what's happening, but I know that the HIPAA
Accelerator can produce
>valid XML.
>
>Did you use the Trading Partner Manager to set up your
channel?
>
>--- Nick
><anonymous@discussions.microsoft.com> wrote in message
>news:074a01c3de9d$fa342920$a301280a@phx.gbl... 
using 
the 
ISA 
the 
>
>
>.
>

[ Post a follow-up to this message ]

If you can get the HIPAA Accelerator to generate XML, then getting it to
generate EDI is simply a matter of setting the Envelope to the HIPAA EDI
envelope type.  That's one reason I suggest using the Trading Partner
Manager... it sets up the envelopes and doc definitions for you.

--- Nick

<anonymous@discussions.microsoft.com> wrote in message
news:096501c3deb7$2134b670$a401280a@phx.gbl...
> No.  I was testing the map via the Mapper tool only.  I'll
> set up a channel and see if the weird prefixes disappear
>
> I couldn't find any documenation on generating X12 using
> the HIPAA Accelerator - do you any good resources that
> cover this?
> 
> Accelerator can produce 
> channel? 
> using 
> the 
> ISA 
> the 

[ Post a follow-up to this message ]