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 ...
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
- Page 410 and 411: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 412 and 413: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 414 and 415: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 416 and 417: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 418 and 419: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 420 and 421: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 422 and 423: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 424 and 425: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 426 and 427: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 428 and 429: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 430 and 431: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 432 and 433: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 434 and 435: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 436 and 437: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 438 and 439: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 440 and 441: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 442 and 443: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 444 and 445: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 446 and 447: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 448 and 449: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 450 and 451: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 452 and 453: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 454 and 455: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 456 and 457: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 458 and 459: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 462 and 463: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 464 and 465: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 466 and 467: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 468 and 469: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 470 and 471: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 472 and 473: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 474 and 475: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 476 and 477: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 478 and 479: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 480 and 481: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 483 and 484: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 485 and 486: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 487 and 488: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 489 and 490: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 491 and 492: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 493 and 494: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 495 and 496: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 497 and 498: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 499 and 500: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 501 and 502: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 503 and 504: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 505 and 506: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 507 and 508: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 509 and 510: ANSI/NIST-ITL 1-2011 - UPDATE 2013
ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - 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 <strong>for</strong> details. See Section 7.1.8.22.2 Field 22.002: In<strong>for</strong>mation designation character / IDCThis mandatory field shall contain the IDC assigned to this Type-98 record as listed in thein<strong>for</strong>mation item IDC <strong>for</strong> this record in Field 1.003 Transaction content / CNT. SeeSection 7.3.1.8.22.3 Field 22.003: <strong>Image</strong>ry capture date / ICDThis is a mandatory field. See Section 7.7.2.2 <strong>for</strong> 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 <strong>for</strong> details. The source agency name may beentered in Field 22.993: Source agency name / SAN.8.22.5 Field 22.005: <strong>Image</strong>ry 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 <strong>for</strong>mat 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 in<strong>for</strong>mation 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 in<strong>for</strong>mation items:• The first in<strong>for</strong>mation 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 in<strong>for</strong>mation item shall be entered if SSC is 2. It is subject bodyMay, 2013 DRAFT VERSION UPDATE 2013 Page 419