acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...
Share Embed Flag
Download ePaper

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 ...

biometrics.nist.gov
from biometrics.nist.gov More from this publisher
11.07.2015 Views

ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSION8.22.1 Field 22.001: Record headerThe content of this mandatory field is dependent upon the encoding used. See the relevantannex of this standard for details. See Section 7.1.8.22.2 Field 22.002: Information designation character / IDCThis mandatory field shall contain the IDC assigned to this Type-98 record as listed in theinformation item IDC for this record in Field 1.003 Transaction content / CNT. SeeSection 7.3.1.8.22.3 Field 22.003: Imagery capture date / ICDThis is a mandatory field. See Section 7.7.2.2 for details. It may not be possible to knowthe exact date of imagery capture. In such a case, specify the date to the level known andfill the rest of the date with zeros.8.22.4 Field 22.004: Source agency / SRCThis is a mandatory field. See Section 7.6 for details. The source agency name may beentered in Field 22.993: Source agency name / SAN.8.22.5 Field 22.005: Imagery capture date estimate range/ ICDRThis is the amount of time (plus and minus) of which ICDR is the center point duringwhich the image data could have been originally collected. It is entered in the format asY yyyy M mm D dd . It is possible to enter only a year, month and/or day range, such D05,meaning that the actual date of collection is estimated to be 5 days plus or minus from thatspecified in ICDR.8.22.6 Field 22.020: Comment / COMThis optional field may be used to insert comments or other text information with therepresentation data. See Section 7.4.4.8.22.7 Field 22.046: Subject / SUBThis field is optional. SUB is comprised of the following information items:• The first information item is mandatory if this field is present. It is subjectstatus code / SSC. Possible entries are:0 = Status of individual unknown1 = Data obtained from a living person – such as a victim orpersons unable to identify themselves2 = Data obtained from a decedent – such as an unknown deceased• The second information item shall be entered if SSC is 2. It is subject bodyMay, 2013 DRAFT VERSION UPDATE 2013 Page 419

ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSIONstatus code / SBSC. Its purpose is to indicate whether the information relates toan entire corpse or a separate body part. The numeric value is selected from thedescriptors below:1 = Whole2 = Fragment• The third information item shall be entered if SSC is 2. It is subject body classcode/ SBCC. The numeric value is selected from the descriptors below:1 = Natural Tissue2 = Decomposed3 = Skeletal8.22.8 Field 22.047: Capture organization name / CONThis field is optional. Note that this can be different from the agency entered in Field22.004: Source agency / SRC and Field 22.993: Source agency name / SAN. SRC andSAN describe the agency that created the record. Since the record may have beenforwarded by another agency to the final destination, Field 1.008 Originating agencyidentifier / ORI is used to indicate the transmitting organization. See Section 7.6 fordetails about SRC, SAN, and ORI. This field is not needed if the transmited information(for instance in DICOM) contains the capture organization information. For example,• The xray of the subject's spine was taken at a medical office two years ago – andnow could be used for possible identification of a body following a disaster.That office is entered as the CON.• The local police department that would create the actual ANSI/NIST-ITL 1-2011conformant record. Such an organization’s code would be entered in Field22.004: Source agency / SRC (for example NA54-X) and its name in Field22.993: Source agency name / SAN( for example New Artichoke Police )In many implementation domains, there are a limited number of transmission organizationsthat can send data. Therefore, the agency listed in SRC may send the transaction to anotherlocation that has access rights to the final destination. This intermediary may addinformation to the transaction, as well. The final transmitting organization code is listed inField 1.008 Originating agency identifier / ORI. Its name may be entered in Originatingagency name /OAN in Field 1.017 Agency names / ANM.8.22.9 Field 22.101: Image type / ITYPThis is a mandatory field. If the code for the particular image type is listed in the followingtable, enter that code. If it is not listed, enter a description of the image type.Table 104 Type-22 image typesDescriptionRadiographs (X-rays)CodeXRAY420

ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - UPDATE 2013 DRAFT VERSIONstatus code / SBSC. Its purpose is to indicate whether the in<strong>for</strong>mation relates toan entire corpse or a separate body part. The numeric value is selected from thedescriptors below:1 = Whole2 = Fragment• The third in<strong>for</strong>mation item shall be entered if SSC is 2. It is subject body classcode/ SBCC. The numeric value is selected from the descriptors below:1 = Natural Tissue2 = Decomposed3 = Skeletal8.22.8 Field 22.047: Capture organization name / CONThis field is optional. Note that this can be different from the agency entered in Field22.004: Source agency / SRC and Field 22.993: Source agency name / SAN. SRC andSAN describe the agency that created the record. Since the record may have been<strong>for</strong>warded by another agency to the final destination, Field 1.008 Originating agencyidentifier / ORI is used to indicate the transmitting organization. See Section 7.6 <strong>for</strong>details about SRC, SAN, and ORI. This field is not needed if the transmited in<strong>for</strong>mation(<strong>for</strong> instance in DICOM) contains the capture organization in<strong>for</strong>mation. For example,• The xray of the subject's spine was taken at a medical office two years ago – andnow could be used <strong>for</strong> possible identification of a body following a disaster.That office is entered as the CON.• The local police department that would create the actual ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong>con<strong>for</strong>mant record. Such an organization’s code would be entered in Field22.004: Source agency / SRC (<strong>for</strong> example NA54-X) and its name in Field22.993: Source agency name / SAN( <strong>for</strong> example New Artichoke Police )In many implementation domains, there are a limited number of transmission organizationsthat can send data. There<strong>for</strong>e, the agency listed in SRC may send the transaction to anotherlocation that has access rights to the final destination. This intermediary may addin<strong>for</strong>mation to the transaction, as well. The final transmitting organization code is listed inField 1.008 Originating agency identifier / ORI. Its name may be entered in Originatingagency name /OAN in Field 1.017 Agency names / ANM.8.22.9 Field 22.101: <strong>Image</strong> type / ITYPThis is a mandatory field. If the code <strong>for</strong> the particular image type is listed in the followingtable, enter that code. If it is not listed, enter a description of the image type.Table 104 Type-22 image typesDescriptionRadiographs (X-rays)CodeXRAY420

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

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

Saved successfully!

Ooh no, something went wrong!