I am creating a map to transform a flatfile to the HIPAA X12 835 transaction
.  I am getting the following error: Output Validation Warning(s):In record 
" TS835W1_1000B_REF_PayeeAdditionalIdentif
ication", one or more of the follow
ing fields must exist:
 @TS835W1_1000B_REF02__AdditionalPayeeIde
ntifier
@NU_TS835W1_1000B_REF03

This is also happening on three other REF segments.  These REF segments are 
options therefore it should not require data to be mapped.  Also the REF03 e
lement is not used in the HIPAA transactions, so why I am getting this error
.  The message should list
REF01 and REF02 elements.

How do I avoid this error.  I tired mapping the data to the trim functiod an
d then to a strength length functiod.  If the string length return is greate
r than 0, I perform the mapping.  However, this does not eliminate the error
.

Any Help?

[ Post a follow-up to this message ]

While each one may exist, it sounds like you might have a choice element as
the parent for these, and one of them is required.  is this the case?  If
so, then you'll have to have at least one of these elements.

Matt


"Curtis Vasbinder" <CurtisVasbinder@discussions.microsoft.com> wrote in
message news:EB96A25E-9510-448C-946E-C5B7BC275FF6@microsoft.com...
> I am creating a map to transform a flatfile to the HIPAA X12 835
transaction.  I am getting the following error: Output Validation
Warning(s):In record " TS835W1_1000B_REF_PayeeAdditionalIdentif
ication", one
or more of the following fields must exist:
>  @TS835W1_1000B_REF02__AdditionalPayeeIde
ntifier
> @NU_TS835W1_1000B_REF03
>
> This is also happening on three other REF segments.  These REF segments
are options therefore it should not require data to be mapped.  Also the
REF03 element is not used in the HIPAA transactions, so why I am getting
this error.  The message should list REF01 and REF02 elements.
>
> How do I avoid this error.  I tired mapping the data to the trim functiod
and then to a strength length functiod.  If the string length return is
greater than 0, I perform the mapping.  However, this does not eliminate the
error.
>
> Any Help?

[ Post a follow-up to this message ]

Similar instances where discovered on inbound 837
documents, where the guide said it was optional, but the
HIPAA accelerator document specs for 837 said it was
mandatory. My recommendation, against what microsoft
frowns on, is to modify the skema of the document spec to
make it optional. I would then take an 835 generated from
it and testit through EDIFECS free online testing for any
compliance issues. The link is http://www.edifecs.com

>-----Original Message-----
>While each one may exist, it sounds like you might have a
choice element as
>the parent for these, and one of them is required.  is
this the case?  If
>so, then you'll have to have at least one of these
elements.
>
>Matt
>
>
>"Curtis Vasbinder"
<CurtisVasbinder@discussions.microsoft.com> wrote in
>message news:EB96A25E-9510-448C-946E-
C5B7BC275FF6@microsoft.com... 
HIPAA X12 835[vbcol=seagreen]
>transaction.  I am getting the following error: Output
Validation
>Warning(s):In
record " TS835W1_1000B_REF_PayeeAdditionalIdentif
ication",
one
>or more of the following fields must exist: 
These REF segments[vbcol=seagreen]
>are options therefore it should not require data to be
mapped.  Also the
>REF03 element is not used in the HIPAA transactions, so
why I am getting
>this error.  The message should list REF01 and REF02
elements. 
the trim functiod[vbcol=seagreen]
>and then to a strength length functiod.  If the string
length return is
>greater than 0, I perform the mapping.  However, this
does not eliminate the
>error. 
>
>
>.
>

[ Post a follow-up to this message ]

I verified each of these elements are marked required=no and still get the e
rror messages.

"Joe Barton" wrote:

> Similar instances where discovered on inbound 837
> documents, where the guide said it was optional, but the
> HIPAA accelerator document specs for 837 said it was
> mandatory. My recommendation, against what microsoft
> frowns on, is to modify the skema of the document spec to
> make it optional. I would then take an 835 generated from
> it and testit through EDIFECS free online testing for any
> compliance issues. The link is http://www.edifecs.com
> 
> choice element as 
> this the case?  If 
> elements. 
> <CurtisVasbinder@discussions.microsoft.com> wrote in 
> C5B7BC275FF6@microsoft.com... 
> HIPAA X12 835 
> Validation 
> record " TS835W1_1000B_REF_PayeeAdditionalIdentif
ication",
> one 
> These REF segments 
> mapped.  Also the 
> why I am getting 
> elements. 
> the trim functiod 
> length return is 
> does not eliminate the 
>

[ Post a follow-up to this message ]

Might want to try the 'exists' functiod. That is a
logical '?'. Go from you input field to that, then output
to an advanced functoid 'plain arrow'. then run a
connector from the input field to this advanced arrow
functiod and the code within should look like this...
XSLT Script:
<xsl:if test='First Input="true"'>
Output = 'Second Input'
</xsl:if>

Hope this helps.
check with you documentation on the usage of these. I
believe it explains it.
Joe
State of Washington




>-----Original Message-----
>I verified each of these elements are marked required=no
and still get the error messages.
>
>"Joe Barton" wrote:
> 
the[vbcol=seagreen] 
to[vbcol=seagreen] 
from[vbcol=seagreen] 
any[vbcol=seagreen] 
have a[vbcol=seagreen] 
record " TS835W1_1000B_REF_PayeeAdditionalIdentif
ication",[vbcol=seagreen] 
so[vbcol=seagreen] 
to[vbcol=seagreen] 
>.
>

[ Post a follow-up to this message ]