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 VERSION• The seventh optional information item is the sample collection locationdescription / LLC. It is an optional string of up to 4000 Unicode characters. Anexample is “2 centimeter x 2 centimeter x 3 centimeter deep sample cut fromtissue of leg of the unidentified body”. Another example is “Grid 3 Sector 2Disaster site 32”.• The eighth optional information item is the sample donor status / SDS. Thisinformation item will include whether or not the sample donor is deceased,missing or unknown. Allowed numeric values are:0 = Deceased1 = Missing Person2 = UnknownNormally, this item would only be used for the sample associated with the subjectof the transaction (SDI = 0), but it could be possible to use it in other cases, suchas a hair sample from a deceased relative. It could also be 'unknown' for thepurported relative’s status, but DNA samples were available for that individual(such as blood sample previously collected).8.18.7 Field 18.007: Claimed or purported relationship / COPRThis field is mandatory if the value for DSD is equal to 1. It is selected from Table 94. Itis a numeric value selected from the “Relationship code” column.Table 94 Relationship tableRelationshipcodeRelationshipDescription1 Biological child2 Biological father3 Biological mother4 Biological sibling5 Maternal relative6 Paternal relative7 Other / unknown8.18.8 Field 18.008: Validated relationship / VRSThis field is optional and is a numeric value selected from the “Relationship Code”May, 2013 DRAFT VERSION UPDATE 2013 Page 373
ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSIONcolumn of Table 94. This information item is completed based upon a comparison of thesubject’s DNA with the DNA of the person with whom the relationship is claimed orpurported. It is only filled in if DSD = 1.8.18.9 Field 18.009: Pedigree information / PEDThis optional field contains information and structure associated with the pedigree.• The first information item is the pedigree ID / PID. It is a character string of upto 24 Unicode characters. It is mandatory if this field is used and it indicates theidentity of the pedigree determined and held at the laboratory that originates thepedigree.• The second information item is the pedigree member ID / PMI. It is a uniquereference within the pedigree. It is mandatory if this field is used. Thisinformation item refers to the subject of the transaction. It is a character string ofup to 6 Unicode characters. This information item shall also provide the ability tolink pedigree information.• The third information item is the pedigree member status / PMS. It is mandatoryif this field is used. It is a single-character containing one of the following values:[This information item refers to DNA associated with this record] :K = KnownU = Unknown• The fourth information item is the DNA sample identifier / SID for thetransaction. It is not an identifier within the pedigree chain, unlike the followingtwo identifiers or the PID. It is a character string of 24 Unicode characters or less.This information item relates the sample in this record to the pedigree.• The fifth information item is the father identifier / FID. It is optional and is anumeric value of 3 digits or less that is unique within the pedigree. Thisinformation item is the father identified as related to the sample indicated in thePMI item.• The sixth information item is the mother identifier / MID. It is optional and is anumeric value of 3 digits or less that is unique within the pedigree. Thisinformation item is the mother identified as related to the sample indicated in thePMI item.• The seventh optional information item is the pedigree comment / PCM. It is upto 2000 Unicode characters.8.18.10 Field 18.010: Sample type / STYThis mandatory field contains two information items. The first represents the origination374
- Page 364 and 365: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 366 and 367: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 368 and 369: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 370 and 371: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 372 and 373: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 374 and 375: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 376 and 377: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 378 and 379: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 380 and 381: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 382 and 383: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 384 and 385: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 386 and 387: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 388 and 389: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 390 and 391: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 392 and 393: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 394 and 395: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 396 and 397: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 398 and 399: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 400 and 401: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 402 and 403: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 404 and 405: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 406 and 407: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 408 and 409: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 410 and 411: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 412 and 413: 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 460 and 461: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 462 and 463: ANSI/NIST-ITL 1-2011 - UPDATE 2013
ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - UPDATE 2013 DRAFT VERSION• The seventh optional in<strong>for</strong>mation item is the sample collection locationdescription / LLC. It is an optional string of up to 4000 Unicode characters. Anexample is “2 centimeter x 2 centimeter x 3 centimeter deep sample cut fromtissue of leg of the unidentified body”. Another example is “Grid 3 Sector 2Disaster site 32”.• The eighth optional in<strong>for</strong>mation item is the sample donor status / SDS. Thisin<strong>for</strong>mation item will include whether or not the sample donor is deceased,missing or unknown. Allowed numeric values are:0 = Deceased1 = Missing Person2 = UnknownNormally, this item would only be used <strong>for</strong> the sample associated with the subjectof the transaction (SDI = 0), but it could be possible to use it in other cases, suchas a hair sample from a deceased relative. It could also be 'unknown' <strong>for</strong> thepurported relative’s status, but DNA samples were available <strong>for</strong> that individual(such as blood sample previously collected).8.18.7 Field 18.007: Claimed or purported relationship / COPRThis field is mandatory if the value <strong>for</strong> DSD is equal to 1. It is selected from Table 94. Itis a numeric value selected from the “Relationship code” column.Table 94 Relationship tableRelationshipcodeRelationshipDescription1 Biological child2 Biological father3 Biological mother4 Biological sibling5 Maternal relative6 Paternal relative7 Other / unknown8.18.8 Field 18.008: Validated relationship / VRSThis field is optional and is a numeric value selected from the “Relationship Code”May, 2013 DRAFT VERSION UPDATE 2013 Page 373