11.07.2015 Views

acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...

acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...

acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - UPDATE 2013 DRAFT VERSIONthat combine tooth conditions into a single subfield at the tooth level, one subfieldis used per tooth. If in<strong>for</strong>mation separately <strong>for</strong> conditions on a particular tooth, eachcondition shall be a separate subfield with the same tooth number, designated inTID.This field shall only appear if Field 12.007: Original dental encoding systemin<strong>for</strong>mation / ODES is present in the record. If the transmittal system usesdifferent coding than that defined in ODES, then Field 12.008:Transmittal dentalencoding system in<strong>for</strong>mation / TDES shall be present in the record.All destination systems should be capable of receiving data relating to a singletooth in multiple subfields, even if tooth conditions in the destination system areexpressed jointly at the tooth level. If a destination system is capable of expressingtooth conditions separately does receive in<strong>for</strong>mation from a system that is notcapable of expressing tooth conditions separately, that destination system shouldtake care concerning the assignment of ANSI/ADA Standard No. 1058 codes toindividual conditions on the tooth.For cases when there is no in<strong>for</strong>mation about a tooth (e.g. even whether it wasmissing or present on the subject), there shall be no field entry. However, if it isknown that a tooth was missing, the appropriate ANSI/ADA Standard No. 1058 –Forensic Dental Codes should be represented, such as 9.3.2.2 – Missing notreplaced – used regardless of the etiology of the lost (extracted, congenital,unknown) with the exception of the case where the tooth lost was believed to be anavulsion, or 9.4.4.5.3 – Avulsion of Tooth – describing that a tooth has been<strong>for</strong>cefully exfoliated from its socket and the socket has exhibited virtually nohealing, used only if there is substantial evidence that the loss was traumatic andnot therapeutic or through natural causes.* The first in<strong>for</strong>mation item is the tooth capture date / TCD. Itcorresponds to Section 9.2 of ANSI/ADA Standard No. 3950. It ismandatory. See Section 7.7.2.3 <strong>for</strong> the <strong>for</strong>mat.* The second in<strong>for</strong>mation item is optional. It is tooth capture dateestimate range / TCDR. This is the amount of time (plus and minus) ofwhich TCD is the center point during which the tooth data could have beenoriginally collected. It is entered in the <strong>for</strong>mat as Y yyyy M mm D dd . It ispossible to enter only a year, month and/or day range, such D05, meaningthat the actual date of collection is estimated to be 5 days plus or minus fromthat specified in TCD.* The third in<strong>for</strong>mation item is the tooth ID / TID. It is mandatory.Teeth shall be numbered utilizing the permanent and deciduous teethcodes in ANSI/ADA Specification No. 3950. Note that if OTPCindicates that there is no distinction between deciduous teeth andpermanent teeth in the original coding, the tooth shall be listed aspermanent, even if the transmittal coding is capable of distinguishingbetween the two types of teeth. The analyst should be aware of thiswhen reviewing the data.286

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!