The bottom line on the interpretation was that the relationship between
DTP01 and DTP02 (similar to the DMG case cited) was specified in a semantic
note and not a syntax note. The 997 only reports on syntax errors, so it
should only report if DTP02 failed the AN 1-35 criteria.
Additional background that did not get included in the official response
had to do with the lack of sufficient specificity in the
standard to do the
type of validation you suggest. For example, to validate the several date
format specifications from a syntax perspective, the grammar and allowable
patterns for the dates would have to be rigorously specified (probably in
BNF or a
regular expression). That type of specificity is not present in
the standard.
The response to the request for interpretation stated
X12's
position. However, there's nothing to prevent the WEDI SNIP
White Paper
(or those maintaining the HIPAA guidelines) from saying that the
circumstance cited should force a "Type 1" error. However, if they do, I
suggest they might want to supply the pieces I that I noted are missing
from the X12 standard.
Regards,
Mike
At 04:54 PM 12/5/2003 -0600, Rachel Foerster wrote:
>Mike, I'm assuming that by now you've read my response on this topic. While
>I agree that there is a semantic note providing a specific business meaning
>to DMG02, I believe there is sufficient specifity with the X12 standard such
>that an syntax analzyer can apply reasonableness edits at a minute. So, even
>though I'm no longer an official member of X12C, I respectfully disagree
>with C's interpretation on this query.
>
>The WEDI SNIP White Paper on Testing defines a Type 1 test as follows:
>
>Type 1: EDI syntax integrity testing - Testing of the EDI file for valid
>
segments, segment order, element attributes, testing for numeric values in
>numeric data elements, validation of X12 or NCPDP syntax, and compliance
>with X12 and NCPDP rules. This will validate the basic syntactical integrity
>of the EDI submission.
>
>I would suggest that a reasonableness check for the range of valid values
>for at a minimum the month and day components of the full 8-digit date is
>well within the scope of this type of testing. Since the field is
>semantically defined as birth date, a resonableness check may become a bit
>problematic unless one's system would impose a limit of no birth year ealier
>than some reasonable year designation.
>
>Rachel
>
>Rachel Foerster
>Rachel Foerster & Associates, Ltd.
>Voice: 847-872-8070
>email: <mailto:
>
>
>-----Original Message-----
>From: Mike Rawlins [mailto:
>Sent: Thursday, December 04, 2003 3:41 PM
>To:
>Subject: Re: [
EDI-L] HIPAA: Does use of a qualifier mean validation should
>be done?
>
>
>X12C received a formal request for interpretation on exactly this point
>sometime in the past year or two. Our official response was that this is
>not a syntax error. The relationship between DMG01 and DMG02 is specified
>in a *semantic* note, and there is no provision for generating syntax
>errors (reportable in a 997) from a semantic note.
>
>I can't speak to how Claredi works, but if they classify a "Level 1 Error -
>against X12 Standard Requirements" as applying to non-compliance with
>semantic notes, then I suppose it is correct. In addition, an
>implementation guide could certainly call something like this
>non-compliance. However, there's nothing in X12.6, the segment dictionary,
>or data element dictionary to formally call your example an "error".
>
>Contact me off-line if you need more info or a copy of the response.
>
>Mike
>
>At 09:17 PM 12/4/2003 +0000, anthonybeecher wrote:
> >I am trying to classify an error level for a rejected data element,
> >DMG02, where DMG01 is "D8" and the data value in DMG02 is "19999999";
> >obviously there is no month 99 and no day 99.
> >
> >Claredi calls it a Level 1 error - against X12 Standard Requirements.
> >I disagree with this assessment.
> >
> >In my mind, the only validation that is required relative to X12
> >Syntax Requirements is that the field is type AN and sized from 1 to
> >35 bytes.
> >
> > >From a pure X12 standpoint, does the use of a qualifier imply a
> >forced validation of the format of the data element that it
> >qualifies?
> >
> >I guess the possible answers would be:
> >1. no validation is required; only X12 AN and 1-35 applies
> >2. validation is required that 8 numeric values exist
> >3. validation is required that 8 numeric values exist and the
> >subportions are expressing proper ranges 1-12 for MM and 1-31 for DD
> >4. If 3 - then leap year rules also apply?
> >
> >Thanks
> >Anthony Beecher
> >
> >
> >
> >
> >To unsubscribe from this group, send an email to:
> >
> >Please use the following Message Identifiers as your subject prefix:
> ><SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
> >Access the list online at: http://groups.yahoo.com/group/EDI-L
> >
> >
> >Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>---------------------------------------------------------------
>Michael C. Rawlins, Rawlins EC Consulting
>www.rawlinsecconsulting.com
>Using XML with Legacy Business Applications (Addison-Wesley, 2003)
>www.awprofessional.com/titles/0321154940
>
>
>
>Yahoo! Groups Sponsor
>
>ADVERTISEMENT
>
><http://rd.yahoo.com/SIG=12c82qf92/M=267637.4116732.5333197.1261774/D=egroup
>web/S=1705005582:HM/EXP=1070660480/A=1853619/R=0/*http://www.netflix.com/Def
>ault?mqso=60178356&partid=4116732> click here
>
><http://us.adserver.yahoo.com/l?M=267637.4116732.5333197.1261774/D=egroupmai
>l/S=:HM/A=1853619/rand=549790734>
>
>To unsubscribe from this group, send an email to:
>
>Please use the following Message Identifiers as your subject prefix:
><SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
>Access the list online at: http://groups.yahoo.com/group/EDI-L
>
>
>Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
><http://docs.yahoo.com/info/terms/> .
>
>
>
>
>[Non-text portions of this message have been removed]
>
>
>
>To unsubscribe from this group, send an email to:
>
>Please use the following Message Identifiers as your subject prefix:
><SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
>Access the list online at: http://groups.yahoo.com/group/EDI-L
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
---------------------------------------------------------------
Michael C. Rawlins, Rawlins EC Consulting
www.rawlinsecconsulting.com
Using XML with Legacy Business Applications (Addison-Wesley, 2003)
www.awprofessional.com/titles/0321154940
Cart
