Download:
pdf |
pdfDENY THE ENEMY ANONYMITY
Department of Defense
Electronic Biometric
Transmission Specification
(DoD EBTS) v4.1
Integrated Data Dictionary (IDD)
April 2019
ii
Table of Contents
1.0
Overview ................................................................................................................................................. iii
2.0
Intended Audience .................................................................................................................................... iii
3.0
IDD Organization and Structure .................................................................................................................. iii
3. 1 Field Status States ................................................................................................................................... iii
3.2 IDD Subject Areas ...................................................................................................................................... v
3.3 IDD Data Element Characteristics ................................................................................................................ vii
4.0
Date and Time Fields .............................................................................................................................. ix
7.0 IDD Element Definitions by Type ................................................................................................................... xi
Type‐1: Transaction Information Record………………………………………………………………………………………………….……….001
Type‐2: User‐Defined Descriptive Text Record………………………………………………………………………………………………..020
Type‐9: Minutiae Data Record…………………………………………………………………………………………………………………............326
Type‐10: Facial, Other Body Part and SMT Image Record………………………………………………………………………………..479
Type‐11: Forensic and Investigatory Voice Record……………………………………………………………………………………………570
Type-13: Variable- Resolution Latent Image Record…………………………………………………………………………………………670
Type‐14: Variable‐Resolution Fingerprint Image Record………………………………………………………………………………….717
Type‐15: Variable‐Resolution Palmprint Image Record…………………………………………………………………………………….773
Type‐17: Iris Image Record………………………………………………………………………………………………………………………………...815
Type‐18: DNA Record…………………………………………………………………………………………………………………………………………..868
Type‐20: Source Representation Record………………………………………………………………………………………………………….930
Type-21: Associated Context Record………………………………………………………………………………………………………………….970
Type-98: Information Assurance Record………………………………………………………………………………………………………….1001
Type-99: CBEFF Biometric Data Record…………………………………………………………………………………………………………….1010
Table of Figures
Figure 1: Data Element Statuses ........................................................................................................................... iv
Figure 2: IDD Data Element Transition Path ............................................................................................................. v
Figure 3: ANSI/NIST-ITL Record Types ................................................................................................................... v
Figure 4: IDD Data Element Characteristics .......................................................................................................... vii
April 2019
UNCLASSIFIED - DISTRIBUTION UNLIMITED
iii
1.0
Overview
The Department of Defense Integrated Data Dictionary (IDD) is one of the products published
by the Defense Forensics and Biometrics Agency (DFBA) to facilitate interoperability between
biometric systems. The IDD is the authoritative source for DoD biometrics data elements.
The IDD is one of the key components of the DoD Electronic Biometrics Transmission
Specification (DoD EBTS) Information Exchange Package (IEP), and serves the following
functions: identifies the high-value data exchanged across DoD biometric systems (both
current and future), establishes authoritative definitions for that data, and documents
standards for data in order to ensure accurate and efficient data flow.
2.0
Intended Audience
The intended audience for this Integrated Data Dictionary spans across the DoD Biometrics
Community, other United States Government (USG) agencies, and Foreign Partners with a
need to understand DoD EBTS transactions. This includes, but is not limited to, those
responsible for biometric system design and development.
3.0
IDD Organization and Structure
3. 1 Field Status States
As Standards and data usages evolve over time, the IDD must reflect the transition and
retirement of certain data elements. The IDD does this by tracking the lifecycle of the data
elements through the states as shown in Figure 1 below. The “NEW” prefix will be added to
April 2019
UNCLASSIFIED - DISTRIBUTION UNLIMITED
iv
the Status to indicate that it is an element that was added as a result of the EBTS v4.1 release
(i.e. “NEW – Active”).
State
Active
Description
Currently viable and fully usable data element.
Deprecated
Element is still usable in current implementations, but it should not be
used going forward. It will gradually be phased out with a new element(s)
that incorporates the functionality of the deprecated element. The IDD
will clearly mark if an element is deprecated. The IDD will also provide the
superseding element(s) and any qualifying condition.
Sunset
Used for alerting the user community that an element may be retired in
the future. IDD will provide indicator to clearly mark if an element is in the
sunset state and the reason why.
Retired
Used to alert the user community that the data element shall not be used
for current and future applications. The IDD will clearly mark if an element
is retired.
Emerging
An element that can be considered for future capability. It has not yet
been approved by FBSWG for use and can be subject to change.
Figure 1: Data Element Statuses
Figure 2 illustrates how an IDD data element transitions from one state to another.
For
example, a DoD data element which is Emerging may become Active after approval of the
Forensics and Biometrics Standards Working Group and adoption by the biometric systems
in use.
April 2019
UNCLASSIFIED - DISTRIBUTION UNLIMITED
v
Emerging
Active
Sunset
Deprecated
Retired
Figure 2: IDD Data Element Transition Path
3.2 IDD Subject Areas
The IDD is divided into sections based on the subject area in order to provide the context in
which the data elements are used. The IDD contains data elements categorized within the
subject areas that are listed in the table below.
Record
Subject Area
Description
Type-1
Transaction Information Record
Type-2
User-Defined Descriptive Text
Record
Contains
contextual/situational/processing
information
(i.e.
identification, biographic, and descriptive, information) regarding the
subject, the encounter, response, sample and the transaction itself.
Type-4
High-Resolution Grayscale
Fingerprint Image (Deprecated)
The use of this logical record for the binary Fingerprint image has been
deprecated by Type-14 Variable-Resolution Fingerprint Image Record.
Contains useful/required information items regarding the use or
purpose of the transaction.
Figure 3: ANSI/NIST-ITL Record Types
April 2019
UNCLASSIFIED - DISTRIBUTION UNLIMITED
vi
Subject Area
Record
Description
Type-7
The use of this logical record for the binary Latent Fingerprint image
Latent Image Binary Latent Image
has been deprecated by Type-13 Variable-Resolution Latent Image
(Deprecated)
Record.
Type-9
Includes fields 9.001 – 9.004. These common data elements shall be
included for any minutiae features within a Type-9 record. Also
Minutiae Data Record (Common)
includes fields 9.901- 9.904 for the universal latent workstation
annotations and workstation identifiers.
Type-9
Minutiae Data Record (Standard Includes fields 9.005 through 9.012.
Features – Legacy)
legacy in ANSI/NIST ITL 1-2011.
Minutiae Data Record (IAFIS
Features)
Type-9
These fields are marked as
Includes fields 9.013 – 9.030. Used for exchanging geometric and
topological minutiae templates and information encoded from a finger
or palm based on the FBI IAFIS standard.
Type-9
Includes fields 9.126 – 9.150. Used for exchanging geometric and
Minutiae Data Record (INCITS M1topological minutiae templates and information encoded from a finger
378 Features)
or palm based on the ANSI/INCITS standard.
Type-9
Extended Feature Set (EFS)
Includes fields 9.300 – 9.399. The EFS defines additional types of
fingerprint features, which allows Latent Print Examiners to document
latent prints in much greater detail. These features are standardized
to enhance interoperability between the various federal, state, and
local agencies.
Type-10
Facial, Other Body
Part and SMT Image Record
Used for exchanging facial, other body parts and image data from
scars, marks, and tattoos (SMT) with textual information.
Type-11
Forensic and Investigatory Voice
Focused upon the analysis of voice signals for forensic and
investigatory purposes.
Type-13
Variable Resolution Latent Image Used for exchanging latent fingerprint or palmprint image data with
Record
textual information.
Variable Resolution Fingerprint
Image
Used for exchanging variable-resolution fingerprint image data,
segmented flat fingerprint data, or major case print data with textual
information.
Type-15
VariableResolution Palm Print Image
Used for exchanging variable-resolution palm print image data with
textual information.
Type-17
Iris Image
Type-18
DNA Record
Type-14
Used for exchanging iris image data.
Used for exchange of DNA data.
Figure 3: ANSI/NIST-ITL Record Types (Cont.)
April 2019
UNCLASSIFIED - DISTRIBUTION UNLIMITED
vii
Subject Area
Description
Source Representation Record
The source representation(s) from which other Record
Types were derived. Examples are an image of multiple latent prints,
of which one or more is of interest. Those would be segmented and
prepared for sending in a Type-13 record.
Associated Context Record
Contains an associated context record. This information does NOT
contain information used to derive biometric information contained in
other records. Record Type-20 serves that function. Record Type-21
may be used to convey contextual information, such as an image of
the area where latent fingerprints were captured.
Information Assurance Record
Contain security information that assures the authenticity and/or
integrity of the transaction.
CBEFF Biometric Data Record
Common Biometric Exchange Formats Framework (CBEFF). Used for
exchanging biometric data not supported by other ANSI/NIST ITL
logical record types.
Record
Type-20
Type-21
Type-98
Type-99
Figure 3: ANSI/NIST-ITL Record Types (Cont.)
3.3 IDD Data Element Characteristics
The following figure lists the data element characteristics and describes the types of
information represented by those characteristics.
Name
Description
Field ID
The Field ID number assigned by the transmission specifications (DoD EBTS or FBI EBTS) or
ANSI/NIST ITL standard.
Element Name
Name of the data element containing the Category and Subcategory names. The element name
is intended to be human readable.
Mnemonic
The Mnemonic is an abbreviated Element name assigned by the transmission specifications
(DoD EBTS or FBI EBTS) or ANSI/NIST ITL standard.
Conditionality
Consists of Mandatory (M), Optional (O), and Dependent (D) codes which indicate the normal
state of the field or component. An arrow indicator may be present to indicate hierarchical
dependency.
Status
Indicates the current lifecycle status of the field (i.e. emerging, retired, active, etc.)
Figure 4: IDD Data Element Characteristics
April 2019
UNCLASSIFIED - DISTRIBUTION UNLIMITED
viii
Name
Description
Description
Description or definition for the data element.
Field Min/Max
Defines the number of characters allowed in the data element. For example, for some date
fields the format will be YYYYMMDD, so therefore both the Field Min and Field Max will be equal
to 8.
Occur Min/Max
The occurrence minimum and maximum indicate the number of times a data element is allowed
to occur within the transaction.
A
Alphabetic
26 English letters (both upper and lower case) within the 7bit ASCII character set.
AN
Alphanumeric
Alphabetic and numeric 1 2 3 4 5 6 7 8 9 0 within the 7- bit
ASCII character set.
ANS
Alphanumeric character set plus those special characters
Alphanumeric and
which are specifically stated in the description of the data,
special characters
within the 7-bit ASCII character set.
AS
Alphabetic character set plus those special characters which
Alphanumeric and
are specifically stated in the description of the data, within the
special characters
7-bit ASCII character set.
B
Binary
See the ANSI/NIST-ITL for rules regarding binary encoding
for traditional encoding (See Annex B: Traditional encoding)
or Base64 for XML (See Annex C: NIEM- conformant
encoding rules).
Base64
Base-64
Encoded (exclusively)
H
Hexadecimal
Representation: 0 1 2 3 4 5 6 7 8 9 A B C D E F
N
Numeric
1234567890
NS
Numeric
Numeric character set plus those special characters which
are specifically stated in the description of the data, within the
7-bit ASCII character set.
Char Types
U
Unicode
Characters available in UTF-8: Latin and extended Latin
characters like ü, Ñ, ç, Þ, ß, ł, ặ, and/or special characters
like ₤, €, ™, +, * and ‡, and/or non-Latin characters like ㆇ,
๐, , ᐂ, � ,ж , ཏ , 句 , ت, ע, and の.
Special
Chars
Allowable characters that are neither alphanumeric nor binary, such as punctuation characters.
For example: Period, Comma, Minus, Plus, Hyphen. 7-bit ASCII characters shall be used for
special characters when Character Type is either AS, ANS or NS. UTF-8 character encoding
shall be used for special characters when Character type is U.
Figure 4: IDD Data Element Characteristics (Cont.)
April 2019
UNCLASSIFIED - DISTRIBUTION UNLIMITED
ix
Name
Description
Format
The Format field defines the data format for the element (e.g. YYYYMMDD for date).
Value Constraints
Identifies the value constraints that shall be applied to the content within the element (e.g. specific
codes from the look up codes list, integer value of certain range, etc.).
Code List
Name of the code list located in Appendix A of this document containing the allowable codes for
the data element.
Source
The authoritative source where the data element is completely or partially derived from.
XML Levels
Contains the default namespace prefix and XML field name. The level indicates the elements
hierarchical appearance in the XML document.
Cardinality
Indicates the Minimum and maximum numbers of allowed occurrences for the referenced XML
element. (1…1)
DoD EBTS vX
Indicator that the dictionary element was referenced by the DoD EBTS in v1.2, 3.0, 4.0, or 4.1.
Figure 4: IDD Data Element Characteristics (Cont.)
4.0 Date and Time Fields
Date fields must be valid dates and in accordance with the requirements stated below.
In general, the format for date fields are follows:
• A date is shown as an 8-digit numeric field of the format YYYYMMDD (YYYY- MM-DD
for XML encoding), where:
•
YYYY (Year) must be 0000 to 9999
•
MM (Month) must be 01 to 12
•
DD (Day) must be 01 to the limit defined by the month and year (e.g., DD
may be 29 for MM = 02 in leap years).
April 2019
UNCLASSIFIED - DISTRIBUTION UNLIMITED
x
Gregorian calendar is default if not specified. For example 19921201 represents December 1,
1992.
Date-Time fields must be valid dates and time fields in coordinated universal time format
(UTC), also known as “Zulu Time.” UTC is reflected as YYYYMMDDHHMMSSZ in Traditional
Encoding and YYYY-MM-DDTHH:MM:SSZ in XML Encoding. The “Z” at the end of the datetime string indicates the time zone, which is always set to UTC time. The format for the date
is the same as above. The format for time is as follows:
•
HH (Hour) must be 00 to 23
•
MM (Minute) must be 00 to 59
•
SS (Second) must be 00 to 59
For example 19921201103015Z represents December 1, 1992 at 10:30:15AM.
Since dates and time find a variety of uses in EBTS transactions, each use may have
specific format restrictions or special edits. For specific format restrictions or special edits,
see the individual date field entries for detail.
April 2019
UNCLASSIFIED - DISTRIBUTION UNLIMITED
xi
7.0 IDD Element Definitions by Type
April 2019
UNCLASSIFIED - DISTRIBUTION UNLIMITED
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1
Type-1: Transaction Information
1.001: Record Header (LEN)
Description:
The record header appears as the first field in each Record Type. It contains information particular to the encoding format
chosen, in order to enable proper reading of the record. In Traditional encoding, this field (xx.001) contains the record length in
bytes (including all information separators) and has a mnemonic of LEN. Table 5 of the ANSI/NIST-ITL Update: 2015 lists the
minimum and maximum permitted lengths of the field in Traditional encoding. In NIEM-conformant XML encoding, this field
contains the RecordCategoryCode, which is the numeric representation of the Record Type.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
Depending Upon Encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord
NIEM Element: itl:Transaction
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
1.002: Version Number (VER)
Description:
This mandatory four-character ASCII value shall be used to specify the current version number of the standard implemented by
the software or system creating the transaction. The format of this field shall consist of four numeric characters. The first two
characters shall specify the major version number. The last two characters shall be used to specify the minor revision number.
The 2011 version of the standard without any of the record types or fields introduced for the 2013 Update has the entry “0500”.
The 2013 Update uses “0501”. The 2015 Update uses "0502". In XML, nist-itl:TransactionMajorVersionValue is 5, and nistitl:TransactionMinorVersionValue is 1.
Field Minimum
T=4;X=1
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
T = #### ; X = #
Constraints
T = 0500, 0501 or 0502 ; X
=
biom:TransactionMajorVersi
onValue = 5,
biom:TransactionMinorVersi
onValue = 2
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction
NIEM Element: itl:TransactionMajorVersionValue/tl:TransactionMinorVersionValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
2
Type-1: Transaction Information
1.003: Transaction Content (CNT)
Description:
This mandatory field shall list and identify each of the records in the transaction by record type and its IDC value. It also
specifies the order in which the remaining records shall appear in the file. It shall consist of two or more subfields. The first
subfield shall relate to this Type-1 record.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction
NIEM Element: itl:TransactionContentSummary
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
1.003_0: Transaction Content - Subfield: Single set of information items (CNT_0)
Description:
This field indicates repeating subsets of the Transaction Content field.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
3
Type-1: Transaction Information
1.003_1a: Transaction Content - First Record Category Code (FRC)
Description:
The first information item (first record category code / FRC) within this subfield shall be “1”. This indicates that the first record in
the transaction is a Type-1 record consisting of header information.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
FRC = 1 integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: dod-ebts:TransactionContentSummary
NIEM Element: dod-ebts:ContentFirstRecordCategoryCode
XML Min/Max: 1 / *
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
1.003_1b: Transaction Content - Content Record Count (CRC)
Description:
The second information item of the first subfield (content record count / CRC) shall be the sum of the Type-2 through Type-99
records contained in this transaction. This number is also equal to the count of the remaining subfields of Field 1.003:
Transaction content / CNT. The maximum for CRC is 999.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
CRC = count of record
types 2 through 99; min = 1;
max = 999; positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction/itl:TransactionContentSummary
NIEM Element: itl:ContentRecordQuantity
XML Min/Max: 1 / *
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
4
Type-1: Transaction Information
1.003_2: Transaction Content - Content Record Summary (REC)
Description:
This information item represents repeating subsets of the Content Record Summary.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
*
Character Types
n/a
Special Characters
n/a
Format
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction/itl:TransactionContentSummary/itl:ContentRecordSummary
NIEM Element: itl:RecordCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
1.003_2a: Transaction Content - Subfield: Repeating pairs of information items (REC_0)
Description:
This field indicates repeating subsets of the Transaction Content field.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
CRC value
Occurrence Maximum
CRC value
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: dod-ebts:TransactionContentSummary
NIEM Element: dod-ebts:ContentRecordSummary
XML Min/Max: 1 / *
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
5
Type-1: Transaction Information
1.003_2a: Transaction Content - Record Category Code (REC)
Description:
The first information item (record category code / REC), shall contain a number chosen from the "record identifier" column of
Table 3 in the ANSI/NIST-ITL Update: 2015.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
REC = 2 or 4; or 7 ≤ REC ≤
22; or REC = 98 or 99;
integer
Code List: DOD EBTS APPROVED LOGICAL RECORD NUMBER CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015, DFBA
Status: Active
XML Parent: dod-ebts:TransactionContentSummary
NIEM Element: dod-ebts:ContentRecordSummary
XML Min/Max: 1 / *
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
1.003_2b: Transaction Content - Information Designation Character (IDC)
Description:
The second information item (information designation character / IDC) shall be an integer equal to or greater than zero and
less than or equal to 99. See Section 7.3.1 of the ANSI/NIST-ITL Update: 2015.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ IDC ≤ 99 non-negative
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction/itl:TransactionContentSummary/itl:ContentRecordSummary
NIEM Element: biom:ImageReferenceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
6
Type-1: Transaction Information
1.004: Type of Transaction (TOT)
Description:
This mandatory field shall contain an identifier, which designates the type of transaction and subsequent processing that this
transaction should be given. This shall be a maximum of 16 alphabetic characters. The TOT shall be in accordance with
definitions provided by the domain or application profile. Versions of this standard prior to 2011 specifically restricted the
character length of TOT to 4 characters. See DoD EBTS v4.1 ToT Matrix for allowed Types of Transactions.
Field Minimum
1
Field Maximum
16
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
DoD EBTS v4.1 ToT Matrix
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction
NIEM Element: itl:TransactionCategoryAbstract
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
1.005: Date (DAT)
Description:
This mandatory field shall contain the local date when the transaction was submitted. See Section 7.7.2.3 of the ANSI/NISTITL Update: 2015.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Character Types
N
Special Characters
None
Occurrence Minimum
1
Occurrence Maximum
1
Format
Constraints
YYYYMMDD - for
Dependent upon encoding.
Traditional Encoding or
Default is YYYYMMDD.
NEIM Conformant Encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction
NIEM Element: itl:TransactionDat
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
7
Type-1: Transaction Information
1.006: Priority (PRY)
Description:
This optional field shall contain a single information character to designate the urgency with which a response is desired. The
values shall range from 1 to 9, with 1 denoting the highest priority. The default value shall be defined by the agency receiving
the transaction.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
Default: 1 ≤ PRY ≤ 9
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015, DFBA
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction
NIEM Element: itl:TransactionPriorityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
1.007: Destination Agency Identifier (DAI)
Description:
This mandatory field shall contain the identifier of the administration or organization designated to receive the transmission.
The size and data content of this field shall be userdefined and in accordance with the application profile. The name of the
destination agency may be entered in Field 1.017: Agency names / ANM. A valid value for this field is “Not Specified.”
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction/itl:TransactionDestinationAgency
NIEM Element: itl:PackageInformationRecord/itl:Transaction/itl:TransactionDestinationAgency
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
8
Type-1: Transaction Information
1.008: Originating Agency Identifier (ORI)
Description:
This mandatory field shall contain the identifier of the administration or organization originating the transaction. The size and
data content of this field shall be user-defined and in accordance with the application profile. See Section 7.6. The name of the
originating agency may be entered in Field 1.017: Agency names / ANM. A valid value for this field is “Not Specified.”
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015, DFBA
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction/itl:TransactionOriginatingAgency
NIEM Element: nc:IdentificationID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
1.009: Transaction Control Number (TCN)
Description:
This mandatory field shall contain the transaction control number as assigned by the originating agency. A unique (for the
originating agency) control number shall be assigned to each transaction. For any transaction that requires a response, the
respondent shall refer to this number in communicating with the originating agency.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
None
Format
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015, DFBA
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction
NIEM Element: itl:TransactionControlNumberID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
9
Type-1: Transaction Information
1.010: Transaction Control Reference (TCR)
Description:
This optional field shall be used for responses that refer to the TCN of a previous transaction involving an inquiry or other
action that required a response.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
None
Format
See 1.009 TCN
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction
NIEM Element: itl:TransactionControlReferenceNumberID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
DoD EBTS 4.1:
Yes
Yes
1.011: Native Scanning Resolution (NSR)
Description:
This mandatory field shall be set to “00.00” if there are no Type-4 records in the transaction. See Section 8 for information
concerning leading zeros. This field may be used to apply to Type-7 records if specified by the domain or application profile.
The special character that is allowed is “.” (the period). When there are Type-4 records present, this field is used to specify the
native scanning resolution of the friction ridge image capture device. This field shall specify the resolution in pixels per
millimeter. The resolution shall be expressed as two numeric characters followed by a decimal point and two more numeric
characters. If Record Type-4 is used and images are scanned at greater than the class of 500 ppi, they shall be subsampled,
scaled down, or interpolated down to produce a class resolution of 500 ppi for transmission. Users shall utilize Record Type-14
if transmitting a fingerprint image at greater than the limits of the 500 ppi class. Images with scanning resolution greater than or
equal to the 1000 ppi class should not be transmitted using Record Type-4 unless being transmitted at 500 ppi class to a
system incapable of receiving Type-14 records at 1000 ppi class or greater.
Field Minimum
T = 5; X = 4
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
NS
Special Characters
Period
Format
##.##
Constraints
NSR = 00.00 if no Type-4
records in transaction;
otherwise xx.xx
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction/itl:TransactionImageResolutionDetails
NIEM Element: biom:NativeScanningResolutionValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
10
Type-1: Transaction Information
1.012: Nominal Resolution (NTR)
Description:
This mandatory field shall be set to “00.00” if there are no Type-4 records in the transaction. This field may be used to apply to
Type-7 records if specified by Type of Transaction. The special character that is allowed is “.” (the period).
W hen there are
Type-4 records present, this field specifies the nominal resolution for the image(s) being exchanged. This field shall specify the
resolution in pixels per millimeter (ppmm). The resolution shall be within the range 19.30 ppmm (490 ppi) to 20.08 ppmm (510
ppi). For example, a sensor that scans natively at 508 ppi would show both NSR and NTR as 20 ppmm (508 ppi). These
images should not be sampled down to exactly 500 ppi. This field was called “Nominal transmitting resolution” in earlier
versions of the standard. The mnemonic is still retained as NTR in this version.The 2007 version of the standard stated:
“Any transmitting resolution within the range of the minimum scanning resolution to a value of 20.47 ppmm plus or minus 0.20
ppmm (520 ppi plus or minus 5 ppi) is permitted for the processing of high resolution records.” This version of the standard
specifically prohibits transmission resolution above 510 ppi (the upper limit of the 500 ppi class) for Type-4 records; a higher
transmission resolution for Type-7 records may be specified by the application profile. (See Table 18 Class resolution with
defined tolerance of the ANSI/NIST-ITL Update: 2015).
Field Minimum
T = 5; X = 4
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
NS
Special Characters
Period
Format
##.##
Constraints
NTR = 00.00 if no Type-4
records in transaction;
otherwise xx.xx
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction/itl:TransactionImageResolutionDetails
NIEM Element: biom:NominalTransmittingResolutionValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
11
Type-1: Transaction Information
1.013: Domain Name (DOM)
Description:
This optional field identifies the domain name for the user-defined Type-2 record implementation. The domain name may only
appear once within a transaction. It shall consist of one or two information items. See Section 6 for more information and the
relationship to Field 1.016: Application profile specifications / APS. All characters marked “A” ,“N” or “S” in the 'Type' column of
Table 128 Character encoding set values of the ANSI/NIST-ITL Update: 2015 may be used.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015, DFBA
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction
NIEM Element: itl:TransactionDomain
XML Min/Max: 0 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
1.013_1: Domain Name - Domain Name Implementation (DNM)
Description:
The mandatory first information item (domain name / DNM) will uniquely identify the agency, entity, or implementation used for
formatting the fields in the Type-2 record.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
None
Format
n/a
Constraints
For DoD EBTS, DNM =
DoD EBTS
Source: ANSI/NIST ITL 1-2011 Update: 2015, DFBA
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction/itl:TransactionDomain
NIEM Element: itl:TransactionDomainName
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
12
Type-1: Transaction Information
1.013_2: Domain Name - Domain Version Number (DVN)
Description:
An optional second information item (domain version number / DVN) shall contain the unique version of the particular
implementation, such as 4.1.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
None
Format
n/a
Constraints
For DoD EBTS 4.1, DVN =
4.1
Source: ANSI/NIST ITL 1-2011 Update: 2015, DFBA
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction/itl:TransactionDomain
NIEM Element: itl:DomainVersionNumberID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
1.014: Greenwich Mean Time (GMT)
Description:
This optional field provides a mechanism for expressing the date and time of the transaction in terms of universal Greenwich
Mean Time (GMT) units. See Section 7.7.2.2 of the ANSI/NIST-ITL Update: 2015.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
YYYYMMDDhhmmssZ for Traditional Encoding
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction
NIEM Element: dod-ebts:TransactionUTCDate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
13
Type-1: Transaction Information
1.015: Character Encoding (DCS)
Description:
This optional field specifies the character encoding that may appear within this transaction for data with the character type
listed as "U" or 'user-defined' in the record format tables. This field shall contain one set of information items (coded as a
subfield). For a description of the use of alternate character encoding see Section 5.6 of the ANSI/NIST-ITL Update: 2015.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a,
TransactionCharacterSetTy
pe
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction
NIEM Element: itl:TransactionCharacterSetDirectory
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
1.015_0: Character Encoding - Subfield: A single set of information items (DCS_0)
Description:
This field indicates repeating subsets of the Character Encoding imformation items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction
NIEM Element: itl:TransactionCharacterSetDirectory
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
14
Type-1: Transaction Information
1.015_1: Character Encoding - Character Encoding Set Index (CSI)
Description:
This first information item (character encoding index / CSI) is the index number that references an associated character
encoding. See the "Character encoding index" column of Table 4 of the ANSI/NIST-ITL Update: 2015 for the valid values for
this information item.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ CSI ≤ 4 or 128 ≤ CSI ≤
999 non-negative integer
Code List: TRANSACTION CHARACTER SET INDEX CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015, DFBA
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction/itl:TransactionCharacterSetDirectory
NIEM Element: itl:CharacterSetIndexCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
1.015_2: Character Encoding - Character Encoding Set Name (CSN)
Description:
The second information item (character encoding name / CSN) shall be the "Character encoding name" associated with that
index number, taken from Table 4 of ANSI/NIST-ITL Update: 2015. All characters marked "A", "N" or "S" in the 'Type' column of
Table 128 Character encoding set values of ANSI/NIST-ITL Update: 2015 may be used. Character Set Name '8-bit Latin' has
been deprecated and should not be used. DoD EBTS v4.1 default character encoding is 7-bit ASCII; UTF-8 is also allowed.
Field Minimum
1
Field Maximum
16
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
Any
Format
n/a
Constraints
CSN = ASCII, UTF-8, UTF16 or UTF-32
Code List: TRANSACTION CHARACTER SET INDEX CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015, DFBA
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction/itl:TransactionCharacterSetDirectory
NIEM Element: itl:CharacterSetCommonNameCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
15
Type-1: Transaction Information
1.015_3: Character Encoding - Character Encoding Set Version (CSV)
Description:
The optional third information item (character encoding version / CSV) is the specific version of the character set used. In the
case of the use of UTF-8, the third optional information item may be used to hold the specific version used, so that the display
terminal can be switched to the correct font family.
Field Minimum
1
Field Maximum
16
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction/itl:TransactionCharacterSetDirectory
NIEM Element: itl:CharacterSetVersionID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
1.016: Application Profile Specifications (APS)
Description:
Use of this optional field indicates the transaction's conformance with one or more Application Profile Specifications that are
derived from ANSI/NIST-ITL 1-2011, such as EBTS or INT-I. There may be multiple subfields, each designating an application
profile to which this transaction conforms. If multiple Application Profile Specifications are included in this field, the
specifications must be compatible with each other. This transaction must be in conformance with all of the cited specifications.
See Section 6 of the ANSI/NIST-ITL Update: 2015. Each subfield shall consist of three mandatory information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction
NIEM Element: itl:TransactionApplicationProfile
XML Min/Max: 0 / 99
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
16
Type-1: Transaction Information
1.016_0: Application Profile Specifications - Subfields: Repeating sets of information items (APS_0)
Description:
Mandatory Subfields of Application Profile Specifications: Repeating sets of information items 1 to 100
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
99
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction
NIEM Element: itl:TransactionApplicationProfile
XML Min/Max: 0 / 99
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
1.016_1: Application Profile Specifications - Application Profile Organization (APO)
Description:
The first information item (application profile organization / APO) will uniquely identify the agency or entity responsible for the
specification.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
None
Format
n/a
Constraints
For DoD EBTS, APO =
DFBA
Source: ANSI/NIST ITL 1-2011 Update: 2015, DFBA
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction/itl:TransactionApplicationProfile
NIEM Element: biom:ApplicationProfileOrganizationName
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
17
Type-1: Transaction Information
1.016_2: Application Profile Specifications - Application Profile Name (APN)
Description:
The second information item (application profile name / APN) shall contain the name of the specification.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
None
Format
n/a
Constraints
For Baseline Application
Profile, APN = ToT
Source: ANSI/NIST ITL 1-2011 Update: 2015, DFBA
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction/itl:TransactionApplicationProfile
NIEM Element: biom:ApplicationProfileName
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
1.016_3: Application Profile Specifications - Application Profile Version Number (APV)
Description:
The third information item (application profile version number / APV) shall contain the specific version of the specification.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
None
Format
n/a
Constraints
For Baseline Application
Profile, APV = 4.1
Source: ANSI/NIST ITL 1-2011 Update: 2015, DFBA
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction/itl:TransactionApplicationProfile
NIEM Element: itl:ApplicationProfileVersionNumberID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
18
Type-1: Transaction Information
1.017: Agency Names (ANM)
Description:
This optional field is comprised of two optional information items. Both information items are alphanumeric and can have any
special characters in the names.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction
NIEM Element: itl:TransactionDestinationAgency
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
1.017_1: Agency Names - Destination Agency Name (DAN)
Description:
The first is the destination agency name / DAN. This corresponds to the agency listed in Field 1.007: Destination agency
identifier / DAI.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction/itl:TransactionDestinationAgency
NIEM Element: itl:AgencyName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
19
Type-1: Transaction Information
1.017_2: Agency Names - Originating Agency Name (OAN)
Description:
The second optional information item is the originating agency name / OAN. This corresponds to the agency listed in Field
1.008: Originating agency identifier / ORI.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction/itl:TransactionOriginatingAgency
NIEM Element: itl:AgencyName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
1.018: Geographic Name Set (GNS)
Description:
This optional field is used if the transaction uses GENC in lieu of ISO 3166-1 as a code set for country code specifications. ISO
3166-1 is the default country code set used for the transaction when this field is not contained in Record Type-1. GENC is
available at https://nsgreg.nga.mil/genc/registers.jsp . The values for this field are: ISO = ISO 3166-1 (default) GENC =
GENC. I
nformation items affected by this choice have “Values from ISO 3166-1 or GENC” specified in the value constraints.
Field Minimum
3
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
GNS = ISO, GENC
Code List: GEOGRAPHIC NAME SET CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord/itl:Transaction
NIEM Element: itl:TransactionGeographicNameSetCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
20
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.001: Record Header
Description:
The record header appears as the first field (xx.001) in each Record Type. It contains information particular to the encoding
format chosen, in order to enable proper reading of the record. In Traditional encoding, this field contains the record length in
bytes (including all information separators). In NIEM-conformant XML encoding, this field contains the RecordCategoryCode,
which is the numeric representation of the Record Type.
Field Minimum
T = 2; X = 1
Field Maximum
T = 8; X = 2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
positive integer; X =
Source: ANSI/NIST ITL 1-2011 (Update 2015) Type-2
Status: Active
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.002: Information Designation Character (IDC)
Description:
Each of the records present in a transaction, with the exception of the Type-1 record, shall include a field (xx.002) containing
the information designation character / IDC. The value of the IDC shall be a sequentially assigned positive integer starting
from zero and incremented by one up to a maximum of 99. IDC references are stated in Type-1 Field 1.003 Transaction
content (CNT) and shall be used to relate information items in the CNT field of the Type-1 record to the other records in the
transaction. Two or more records may share a single IDC solely to identify and link together records that pertain to different
representations of the same biometric trait.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
0 <= IDC <= 99; integer
Source: ANSI/NIST ITL 1-2011 (Update 2015) Type-3
Status: Active
XML Level 1: itl:PackageDescriptiveTextRecord
Cardinality: 1…1
XML Level 2: biom:ImageReferenceID
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
21
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.003: FBI File Number (FFN)
Description:
This is a 10-byte numeric representing the FBI Investigative File Number. This is not the FBI Number specified by the
mnemonic “FBI.” Since it is used for FBI LFPS record keeping purposes, it is imperative that the user transmit this number if
known.
Field Minimum
10
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Sunset
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:FBIFileNumber/nc:IdentificationID
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
No
2.005: Retention Code (RET)
Description:
This field indicates whether the information submitted as a part of a transaction is to be retained as a permanent part of the
Master File. Submit a ‘Y’ for yes or an ‘N’ for no.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: YES NO CODE
Source: NGI-DOC-01078-10.1
Status: Active
XML Level 1: dod-ebts:RecordRetentionIndicator
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
22
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.006: Attention Indicator (ATN)
Description:
This alphanumeric-special field shall contain a designation of the individual to whose attention a response is to be directed.
Periods shall not be used e.g., Det. J. Q. Public shall be entered as DET J Q PUBLIC. The value of ATN returned to the
submitter is the value submitted.
Field Minimum
3
Field Maximum
30
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: dod-ebts:AttentionIndicator
Cardinality: 0…1
XML Level 2: nc:TextType
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.007: Send Copy to (SCO)
Description:
The purpose of this 9-to-19-character alphanumeric-special ANS field is to indicate that additional electronic responses need to
be forwarded to agencies other than the contributor by the State Identification Bureau. The first nine characters shall be
alphanumeric and shall contain the NCIC-assigned Originating Agency Identifier ORI for an agency who is to receive a copy of
the response. At the option of the transmitting agency, the ORI may be expanded to a size of 19 characters, with 10
characters of alphanumeric-special (ANS) data appended to the end to assist in proper routing of the responses. listed in the
"SEND COPY TO" block
Field Minimum
9
Field Maximum
19
Occurrence Minimum
0
Occurrence Maximum
9
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: dod-ebts:RecordForwardOrganizations
Cardinality: 0…1
XML Level 2: nc:OrganizationIdentification
Cardinality: 0…9
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
23
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.009: Originating Agency Case Number (OCA)
Description:
This field contains the one-to-twenty character Originating Agency Case Identifier OCA assigned by the originating agency.
This alphanumeric-special ANS field may contain any printable 7-bit ASCII character with the exception of the period. The OCA
must not begin with a blank.
Field Minimum
1
Field Maximum
20
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 3: nc:CaseTrackingID
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.010: Contributor Case Identifier Number (CIN)
Description:
This grouped free-text field is a 48-byte maximum alphanumeric-special assigned by the contributor to uniquely identify a latent
case. It consists of: a literal subfield Contributor Case Prefix CIN_PRE of up to 24 characters e.g., "Incident #, "Laboratory
Number," "Investigation No."
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
5
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:ContributorCaseIdentificationNumber
Cardinality: 0..5
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
24
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.010_0: Contributor Case Identifier Number - Subfields: Repeating sets of information items (CIN_0)
Description:
Repeating subfield for Contributor Case Identifier Number
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
1
Occurrence Maximum
5
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: New-Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:ContributorCaseIdentificationNumber
Cardinality: 1..5
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.010_1: Contributor Case Identifier Number - Contributor Case Identifier Prefix (CIN_PRE)
Description:
Literal subfield Contributor Case Prefix (CIN_PRE) of up to 24 characters (e.g., “Incident #,” “Laboratory Number,”
“Investigation No.”)
Field Minimum
1
Field Maximum
24
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:ContributorCaseIdentificationNumber
Cardinality: 1…5
XML Level 3: ebts:ContributorCasePrefixIdentification/nc:IdentificationID
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
25
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.010_2: Contributor Case Identifier Number - Contributor Case Identifier (CIN_ID)
Description:
The Contributor Case Identifier subfield (CIN_ID) of up to 24 characters.
Field Minimum
1
Field Maximum
24
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:ContributorCaseIdentificationNumber
Cardinality: 1…1
XML Level 3: ebts:ContributorCaseIdentification/nc:IdentificationID
Cardinality: 1…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.011: Contributor Case Identifier Extension (CIX)
Description:
An element that supplements the Case Identifier Number, allowing multiple searches to be associated with the same case.
This field is a two-byte to four-byte numeric supplement to the Case Identifier Number that allowsmultiple searches to be
associated with the same case. The CIX shall be used only in conjunction with the CIN.
Field Minimum
2
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.1
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:ContributorCaseIdentificationNumber
Cardinality: 0…1
XML Level 3: ebts:ContributorCaseExtensionIdentification/nc:IdentificationID
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
26
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.013: Latent Case Number Extension (LCX)
Description:
Defines extensions assigned by the FBI for each submission related to a Latent Case Number. The LCX shall be a five-digit
extension starting with “00000” for the first submission and incrementing by one for each subsequent submission. The LCX
shall be used only in conjunction with LCN. As this field is for FBI LPS internal use only, this response field will be used for
record-keeping purposes only.
Field Minimum
5
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Sunset
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…11
XML Level 2: ebts:FBILatentCaseIdentification
Cardinality: 0…1
XML Level 3: ebts:FBILatentCaseNumberExtension/nc:IdentificationID
Cardinality: 0..1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
No
2.014: FBI Number UCN (FBI)
Description:
This field is used to uniquely specify Identities contained in the NGI database, and shall be no more than nine alphanumeric
characters. This Universal Control Number (UCN) is used to identify records in the criminal, civil, ULF and other repositories.
The UCN number returned in a response is dependent upon the search results. The Legacy Subject Control Number (SCNA)
used for ULF records may be provided in this field where designated in the message definition.
Field Minimum
1
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
1000
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: j:PersonFBIIdentification/nc:IdentificationID
Cardinality: 0…1000
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
27
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.015: State Identification Number (SID)
Description:
This field contains any known state identification number. The native encoding format is the standard two-character
abbreviation of the state name followed by the number. Embedded blanks are not permitted. SIDs from New York, Oregon, or
Pennsylvania may contain a hyphen in the last position. The SID returned in a response is dependent upon the search
results.
FBI IAFIS expects the format to be the standard two-character abbreviation of the state name followed by the
number.
Field Minimum
3
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1000
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: nc:PersonStateIdentification/nc:IdentificationID
Cardinality: 0…1000
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.016: Social Security Account Number (SOC)
Description:
This field contains the subject’s social security number, if known. This number shall be entered as nine consecutive digits with
no embedded punctuation characters. No foreign social security numbers shall be used.
Field Minimum
9
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
4
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: nc:PersonSSNIdentification/nc:IdentificationID
Cardinality: 0…4
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
28
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.017: Miscellaneous Identification Number (MNU)
Description:
If there are any miscellaneous identification numbers, they shall be entered in this field. The format of the data shall be a twoletter identifying code, followed by a hyphen -, followed by the number itself. The size of the MNU is limited to 15 characters
and as many as four miscellaneous numbers may be included in this field. Each MNU shall be separated from the next by the
{RS} separator character. See look up type and associated codes for th list of acceptable two-letter identifying codes. If “AF” or
“AS” is entered, all characters following the hyphen must be numeric. Interspersed blanks are invalid. Types of numbers not
listed in the MISCELLANEOUS IDENTIFICATION NUMBER CODE table shall not be entered. Only U.S. passport numbers
shall be entered; foreign numbers shall be ignored. For the list of 2 letter identifying code, see look up codes below.
Field Minimum
4
Field Maximum
15
Occurrence Minimum
0
Occurrence Maximum
4
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: MISCELLANEOUS IDENTIFICATION NUMBER CODE
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: nc:PersonOtherIdentification
Cardinality: 0…4
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
29
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.018: Name Legacy (NAM)
Description:
This alpha-special field contains the names of the subject. The format shall be the surname followed by a comma, followed by
the given names, which are separated by a space. Part IV of the NCIC Code Manual describes in greater detail the manner in
which each name is to be entered. Hyphens, commas, and blanks are all allowed as special characters. Numerics are not
allowed. Special values of NAM to be entered in cases where the subject's name is not known are listed in the NAME look up
code table.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AS
Special Characters
N/A
Format
NCIC Name Format:
,, …
Constraints
N/A
Code List: NAME
Source: NGI-DOC-01078-10.0
Status: Deprecated
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonName
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
No
2.018_1: Name Legacy - Surname (NAM1)
Description:
A last name or family name of a person.
Field Minimum
3
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Deprecated
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonName
Cardinality: 0…1
XML Level 3: nc:PersonSurName
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
No
30
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.018_2: Name Legacy - Given Name (NAM2)
Description:
A first name of a person.
Field Minimum
3
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Deprecated
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonName
Cardinality: 0…1
XML Level 3: nc:PersonGivenName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
No
2.018_3: Name Legacy - Middle Name (NAM3)
Description:
A middle name of a person.
Field Minimum
3
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Deprecated
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonName
Cardinality: 0…1
XML Level 3: nc:PersonMiddleName
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
No
31
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.019: Aliases Legacy (AKA)
Description:
This 3-to-30 alpha-special AS field contains alias names of the subject. Up to ten aliases may be provided, separated from one
another by the {RS} character. AKA may contain a comma, hyphen, or blank as special characters. The format shall be the
surname followed by a comma, followed by the given names separated by a space. The following restrictions and exceptions
to the general format apply (the first three apply only to the traditional encoding): 1. Minimum length is three bytes in the
following sequence: alpha or ampersand, comma, or alphabetic. 2. A comma must be followed by a minimum of one
alphabetic character. 3. A blank before or after comma is invalid. 4. A hyphen in first and last position of any name segment is
invalid. 5. Two consecutive blanks or hyphens between characters are invalid.
Field Minimum
3
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Deprecated
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonAlternateName
Cardinality: 0…10
XML Level 3: nc:PersonGivenName, nc:PersonMiddleName, nc:PersonSurName, ebts:PersonFourthImportanceName
,ebts:PersonFifthImportanceName
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
No
2.020: Place of Birth (POB)
Description:
The subject’s place of birth shall be entered in this field. Indicate in this POB field the state Mexican, United States, territorial
possession, province Canadian, or country of birth. The appropriate two-letter abbreviation shall be used as listed in Part IV of
the NCIC State and Country Data Code Table (Appendix O NGI-DOC-01078-10.0).
Field Minimum
2
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: PLACE OF BIRTH CONDITIONS and Appendix O NGI-DOC-01078-10.0
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonBirthPlaceCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
32
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.021: Country of Citizenship (CTZ)
Description:
This field contains two-letter abbreviation for the name of the country of which the subject is a citizen. Entry must be a valid
country code from the NCIC State and Country Data Code Table found in Appendix O [of FBI EBTS10.0].
Field Minimum
2
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
10
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: Appendix O NGI-DOC-01078-10.0
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonCitizenshipCode
Cardinality: 0…10
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.022: Date of Birth (DOB)
Description:
This field contains the date of birth. It is entered as an eight-digit number in the same format as specified in Section 1.1 of this
appendix [in FBI EBTS 9.1]. If DOB is completely unknown, enter as 00000000. Partial DOBs are not allowed. DOB shall not
exceed date of submission after time zone adjustment. When a submission contains an unknown DOB and is a non-ident
retained, that submission will be rejected, as IAFIS will not allow a master record to be created with an unknown DOB.
Field Minimum
8
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
5
Character Types
N
Special Characters
N/A
Format
YYYYMMDD
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Deprecated
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: nc:PersonBirthDate/nc:Date
Cardinality: 0…5
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
No
33
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.023: Age Range (AGR)
Description:
An estimated age range may be entered using a pair of two-digit numbers. The first two digits shall represent the minimum
age, and the second two the maximum. There shall be no separator character used between the ages.
Field Minimum
4
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: nc:PersonAgeMeasure
Cardinality: 0…1
XML Level 3: nc:MeasureIntegerRange/nc:RangeMinimumValue/nc:RangeMaximumValue
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.024: Sex (SEX)
Description:
This field is used to report the gender of the subject. The entry is a single character selected from the GENDER CODES table
in Appendix A of the EBTS IDD v6.0.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: GENDER CODES
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonSexCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
34
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.025: Race Legacy (RAC)
Description:
This field is used to indicate the race of the subject. Use the predominant race code from the [look up codes].
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: RACE
Source: NGI-DOC-01078-10.0
Status: Deprecated
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: nc:PersonRace
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
No
2.026: Scars, Marks and Tattoos (SMT)
Description:
For each scar, mark, or tattoo present on the subject, the appropriate NCIC code shall be used in this information item. Blanks
are allowed as special characters.
Field Minimum
3
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
10
Character Types
AS
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: NCIC DESTINATION
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: biom:PhysicalFeatureCategoryCode
Cardinality: 0…10
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
35
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.027: Height Legacy (HGT)
Description:
This field contains the subject’s height as a three-character value. If reported in feet and inches, the first leftmost digit is used
to show feet while the two rightmost digits are used to show the inches between 00 and 11. If reported in inches then the left
most character is “N” followed by two digits. If height is unknown, 000 is entered. The allowable range is 400 to 711. Heights
outside this range will be clamped at these limits.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Deprecated
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: nc:PersonHeightMeasure
Cardinality: 0…1
XML Level 3: nc:MeasureValue/nc:MeasureUnitText
Cardinality: 1…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
No
2.028: Height Range (HTR)
Description:
This field will be used to give an estimated height range to be expressed as two three-character values formatted as described
for mnemonic HGT, indicating the shortest and tallest heights of the subject. For the native encoding of this field, the first three
characters shall represent the minimum height and the second three the maximum height. There shall be no separator
character used between the heights. The allowable range is 400 to 711 or N48 to N95
Field Minimum
6
Field Maximum
6
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Deprecated
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: nc:PersonHeightMeasure
Cardinality: 0…1
XML Level 3: nc:MeasureRangeValue/nc:RangeMinimumValue/nc:RangeMinimumValue/
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
No
36
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.029: Weight Legacy (WGT)
Description:
In this field, the subject‘s weight in pounds is entered. If weight is unknown, 000 is entered. All weights in excess of 499
pounds will be set to 499 lbs. WGT must be in the range 050 to 499 lbs. however, there is no minimum range limit for missing
persons or unknown persons.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Deprecated
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: nc:PersonWeightMeasure
Cardinality: 0…1
XML Level 3: nc:MeasureValue
Cardinality: 1…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
No
2.030: Weight Range (WTR)
Description:
If a range of weight is given, it shall be expressed as two 3-digit numbers indicating the minimum and maximum weights in
pounds of the subject. There shall be no separator character used between the weights. WTR must be in the range 050 to 499
lbs however, there is no minimum range limit for missing persons or unknown persons.
Field Minimum
6
Field Maximum
6
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Deprecated
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: nc:PersonWeightMeasure
Cardinality: 0…1
XML Level 3: nc:PersonWeightMeasure/ nc:MeasureRangeValue or nc:RangeMaximumValue
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
No
37
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.031: Color Eyes (EYE)
Description:
For this field, the three-letter code from the following table is used to indicate the subject's color of eyes.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: ALPHA EYE COLOR CODES
Source: NGI-DOC-01078-10.0
Status: Deprecated
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: nc:PersonEyeColorCode
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
No
2.032: Hair Color (HAI)
Description:
In this field, the three-letter code is used to indicate the subject‘s color of hair.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: HAIR COLOR
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: j:PersonHairColorCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
38
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.034: Pattern Level Classifications (PAT)
Description:
This grouped field contains pattern classification information about the latent finger(s) image. As such, this field shall only be
included when one or more of finger positions 0-10 are being searched. PAT shall consist of two-character finger position
code followed by the primary pattern type code as chosen from the following table. Up to two reference pattern classifications
per finger are also allowed, thereby making the total number of pattern classes allowable per finger equal to three. For
traditional encoding, if multiple pattern types are used for reference for the same finger, they shall be separated from each
other by the {US} separator. Multiple fingers shall be separated by the {RS} separator. If submitting a Latent Fingerprint whose
actual finger position is unknown, the PAT and FGP (2.074) fields are used in conjunction as follows to supply guesses for
which finger position the latent print might be: place a “00” in the FGP subfield of PAT to indicate the actual position is
unknown; place the actual pattern in the PATCL subfield; place one or more finger number guesses in the FGP field (2.074).
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonFingerprintSet
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.034_0: Pattern Level Classifications - Subfields: Repeating sets of information items (PAT_0)
Description:
Repeating subfield for Pattern Level Classifications
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
1
Occurrence Maximum
10
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: New-Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonFingerprintSet
Cardinality: 1…10
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
39
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.034_1: Pattern Level Classifications - Finger Number (FGP)
Description:
This two-byte field shall contain a character designating the finger position.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: FINGERPRINT TEN FINGER NUMBER PLUS UNKNOWN
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonFingerprintSet
Cardinality: 1…10
XML Level 3: ebts:FingerprintImageFinger
Cardinality: 1…10
XML Level 4: ansi-nist:FingerPositionCode
Cardinality: 1…10
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.034_2: Pattern Level Classifications - Pattern Classification Code (PATCL)
Description:
The list of acceptable CJIS pattern level fingerprint classifications.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
3
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: FINGERPRINT CJIS PATTERN CLASSIFICATION
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonFingerprintSet
Cardinality: 1…10
XML Level 3: ebts:PersonFingerprintSet/ ebts:FingerprintImageFinger/
ebts:RidgeCoreDelta/ebts:FingerprintPatternClassificationCode
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
40
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.035: Palmprints Available Indicator (PPA)
Description:
If palm prints are available, this field shall contain a "Y"; otherwise, the field shall be omitted.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: PALM PRINT AVAILABLE INDICATOR
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonPalmPrintAvailableIndicator
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.038: Date Printed (DPR)
Description:
This field contains the date that the subject was printed. This date field shall contain the local date for the region submitting
the request. DPR shall not exceed the date of submission.
Field Minimum
8
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonGeneralizedFrictionRidgePositions
Cardinality: 0…1
XML Level 3: nc:BiometricCaptureDate/nc:Date
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
41
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.039: Employer and Address (EAD)
Description:
The name and address of the subject’s primary employer may be entered into this free-text field. The EAD returned in a
response is the same as the one submitted. For the native encoding, this field is a free form text field.
Field Minimum
1
Field Maximum
120
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: nc:Employer
Cardinality: 0…1
XML Level 3: nc:EntityOrganization/nc:OrganizationName
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.040: Occupation (OCP)
Description:
This free-text field contains the person‘s occupation. The OCP returned in a response is the same as the one submitted.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: nc:EmployeeOccupationText
Cardinality: 0…1
XML Level 3: nc:EmploymentLocation/ nc:LocationAddress/nc:StructuredAddress/nc:LocationStreet/ nc:StreetNumberText or
nc:StreetName, nc:EmploymentLocation/ nc:LocationAddress/ nc:StructuredAddress/ nc:LocationStreet/nc:StreetName,
nc:EmploymentLocation/ nc:LocationAdd
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
42
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.041: Residence of Person Fingerprinted (RES)
Description:
This is a free-text field, including printable special characters and formatting characters (CR, LF, TAB) that is used for the
residential address of the person fingerprinted. The RES returned in a response is the same as the one submitted.
Field Minimum
1
Field Maximum
120
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonResidenceLocation
Cardinality: 0…1
XML Level 3: ebts:PersonResidenceLocation/ nc:LocationAddress/ nc:StructuredAddress/
nc:LocationStreet/nc:StreetNumberText or nc:StreetName, ebts:PersonResidenceLocation/ nc:LocationAddress/
nc:StructuredAddress/nc:LocationCityName or nc:LocationStateNCICLSTAC
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.042: Military Code (MIL)
Description:
A one-letter code from the following table shall be entered in this field to indicate which branch of the United States Military
submitted the enlistment transaction.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: MILITARY
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: dod-ebts:TransactionSubmissionMilitaryCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
43
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.043: Type of Search Requested (TSR)
Description:
A one-byte code shall be entered in this field from the Type of Search Codelist to indicate the type of record being submitted.
The field is applicable to the NFUF, CPDR, FNDR, NNDR, CPNU, DOCE, EMUF, NFAP, and NFUE transactions.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: TYPE OF SEARCH
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:TransactionSearchRequestCategoryCode
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.045: Date of Arrest (DOA)
Description:
This field contains the date of arrest. The date shall appear as an eight-digit number. DOA shall not exceed date of submission
except when the submission originates from an international contributor located in a time zone earlier than the Eastern Time
Zone.This date field shall contain the local date for the region submitting the request.
Field Minimum
8
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
YYYYMMDD
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:ArrestDate/nc:Date
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
44
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.046: Date of Arrest - Suffix (DOS)
Description:
This field contains a code representing the sequence of the subject's arrests within a given date. The code also indicates the
type of fingerprint card on which the Date of Arrest was contained. This field is for internal use within the FBI only.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:ArrestDateSuffixCode
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.047: Arrest Segment Literal (ASL)
Description:
This field is made up of the following subfields: Date of Offense DOO Arrest Offense Literal AOL.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:CriminalCycle
Cardinality: 0…1
XML Level 3: ebts:ArrestOffenseData
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
45
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.047_0: Arrest Segment Literal - Subfields: Repeating sets of information items (ASL_0)
Description:
Repeating subfield for Arrest Segment Literal
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
40
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: New-Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:CriminalCycle
Cardinality: 0…40
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.047_1: Arrest Segment Literal - Date of Offense (DOO)
Description:
The DOO shall appear as an eight-digit number. The DOO shall not exceed the current date except when the submission
originates from an international contributor located in a time zone earlier than the Eastern Time Zone. This date field shall
contain the local date for the region submitting the request. CJIS has edit checks in place to allow for the acceptance of the
local date as valid up to 24 hours in advance to accommodate the variance between international time zones. The DOO shall
be separated from the AOL by the {US} separator character. A DOO is prohibited without a corresponding AOL offense. If a
DOO is not present, a {US} character separator shall still be used.
Field Minimum
8
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
YYYYMMDD
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:CriminalCycle
Cardinality: 0…40
XML Level 3: ebts:OffenseDate/nc:Date
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
46
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.047_2: Arrest Segment Literal - Arrest Offense Literal (AOL)
Description:
A free text description of an offense charged on an arrest. The first character of the AOL text must not be blank. Each AOL
should have a corresponding DOO.
Field Minimum
1
Field Maximum
300
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:CriminalCycle
Cardinality: 0…40
XML Level 3: j:ChargeText
Cardinality: 1…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.051: Court Segment Literal (CSL)
Description:
The CSL field is made up of the Court Disposition Date CDD, the Court Offense Literal COL, Other CourtSentence Provision
Literal CPL, Court Disposition (CDN) and Court Count Number (CCT). A CDD (if available), followed by a COL, followed by a
CPL, followed by a CDN, followed by CCT (if available), each separated by a {US} separator character must be present for
each occurrence of the CSL field.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:CriminalCycle
Cardinality: 0…40
XML Level 3: ebts:CourtDispositionData
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
47
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.051_0: Court Segment Literal- Subfields: Repeating sets of information items (CSL_0)
Description:
Repeating subfield for Court Segment Literal
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
40
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: New-Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:CriminalCycle
Cardinality: 0…40
XML Level 3: ebts:CourtDispositionData
Cardinality: 0…40
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.051_1: Court Segment Literal - Court Disposition Date (CDD)
Description:
The date a court count was disposed of by the court. The CDD shall appear as an eight-digit number. The CDD shall not
exceed the current date except when the submission originates from an international contributor located in a time zone earlier
than the Eastern Time Zone. This date field shall contain the local date for the region submitting the request.
Field Minimum
8
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
YYYYMMDD
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:CriminalCycle
Cardinality: 0…40
XML Level 3: ebts:CourtDispositionData
Cardinality: 0…40
XML Level 4: nc:DispositionDate/nc:Date
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
48
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.051_2: Court Segment Literal - Court Offense Literal (COL)
Description:
A freeform text description of an offense charged in a court count. The first character of the COL must not be a blank.
Field Minimum
1
Field Maximum
300
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:CriminalCycle
Cardinality: 0…40
XML Level 3: ebts:CourtDispositionData
Cardinality: 0…40
XML Level 4: j:ChargeText
Cardinality: 1…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.051_3: Court Segment Literal - Other Court Sentence Provision Literal (CPL)
Description:
The freeform text containing information on sentence provisions.
Field Minimum
1
Field Maximum
300
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:CriminalCycle
Cardinality: 0…40
XML Level 3: ebts:CourtDispositionData
Cardinality: 0…40
XML Level 4: nc:DispositionText
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
49
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.051_4: Court Segment Literal - Court Disposition (CDN)
Description:
A code from Table 12 of NGI-DOC-01078-10.0 representing the definitive disposition information about a Subject for a
particular charge. This element must contain a value most closely associated with the disposition type.
Field Minimum
1
Field Maximum
32
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AS
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: CDN VALUES CODES
Source: NGI-DOC-01078-10.0
Status: New-Emerging
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:CriminalCycle
Cardinality: 0…40
XML Level 3: ebts:CourtDispositionData
Cardinality: 0…40
XML Level 4: ebts:DispositionCategoryCodeText
Cardinality: 1…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.051_5: Court Segment Literal - Court Count Number (CCT)
Description:
A two-byte sequential number assigned to each court count, with the valid value range from 01 to 40.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
>1 and <= 40
Source: NGI-DOC-01078-10.0
Status: New-Emerging
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:CriminalCycle
Cardinality: 0…40
XML Level 3: ebts:CourtDispositionData
Cardinality: 0…40
XML Level 4: ebts:CourtCountNumber
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
50
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.053: Offense Category (OFC)
Description:
The category for a crime committed by the biometric subject.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: OFFENSE CATEGORY
Source: NGI-DOC-01078-10.0
Status: Sunset
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:OffenseCategoryCode
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
No
2.054: Custody or Supervisory Status Start Date (SSD)
Description:
This field contains the start date for the subject’s indicated custody or supervisory status. The date shall appear as an eightdigit number. The SSD may not be less than Date Of Arrest. The SSD shall not exceed the current date except when the
submission originates from an international contributor located in a time zone earlier than the Eastern Time Zone. This date
field shall contain the local date for the region submitting the request. The SSD may not be less than DOA. The SSD shall not
exceed the current date.
Field Minimum
8
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
YYYYMMDD
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:CriminalCycle
Cardinality: 0…40
XML Level 3: ebts:CustodySupervisoryData
Cardinality: 0…1
XML Level 4: nc:StartDate/nc:Date
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
51
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.055: Custody or Supervisory Literal (SLE)
Description:
This field contains the free-text description of the subject‘s custody or supervision status. The first character must not be blank.
Entry of SLE requires that SSD also be entered.
Field Minimum
1
Field Maximum
300
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:CriminalCycle
Cardinality: 0…40
XML Level 3: ebts:CustodySupervisoryData
Cardinality: 0…1
XML Level 4: ebts:SupervisionStatus(0…1)/nc:StatusText(0…1)
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.056: Identification Comments (ICO)
Description:
Additional miscellaneous identification remarks. The reason for caution may be entered in this free-text field. The first character
may not be a blank.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: j:SubjectOffenderNoticeText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
52
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.057: Finger Numbers Requested (FNR)
Description:
This numeric field is used in transactions involving a request for fingerprint image information. The finger numbers for which
image information is requested are selected from Table, “Finger Position Code,” in the ANSI/NIST-ITL. Up to 13 individual
finger image numbers may be listed, separated from one another by the separator. For traditional encoding, the finger
codes being requested shall appear as 01{RS}02{RS} ... {RS}10{GS}. This field may also include the supplemental position
code of 19 and/or the palm position codes outlined in the associated codelist.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
13
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: PALM POSITION and FINGER POSITION CODE
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:TransactionFingerprintImagesRequested/ansi-nist:FingerPositionCode
Cardinality: 0…13
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.059: Search Results Findings (SRF)
Description:
This field is used in responses to submissions and contains a single character indicating the results of a comparison. See Look
Up Codes, which outlines the valid values, their meanings, and transactions which may contain those values. SRF values that
are specific to a single request TOT reflect the request and response TOTs with a dash between them (e.g., FDSP-SRE),
where only the response TOT contains the SRF field.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: SEARCH RESULT FINDING
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:TransactionResponseData
Cardinality: 0…1
XML Level 3: ebts:TransactionSearchResultsCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
53
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.060: Status/Error Message (MSG)
Description:
This free-text field will contain reason, status, or error messages that are generated as a result of the processing of a
transaction and will be sent back to the submitter. For example, an Unsolicited Unsolved Latent Delete transaction will contain
the reason for the deletion of a record. For native encoding, each message will be separated by the RS separator character.
Field Minimum
1
Field Maximum
300
Occurrence Minimum
0
Occurrence Maximum
1000
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:TransactionResponseData
Cardinality: 0…1
XML Level 3: ebts:TransactionStatusText
Cardinality: 0…1000
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.061: Case Title (CST)
Description:
This field identifies the Latent Case. It will include information concerning the case, and it must include the offense type.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: nc:CaseTitleText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
54
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.062: Image Type (IMT)
Description:
This field identifies the type of image e.g., palmprints, toe prints included in an electronic submittal. The list of IMT values to be
used in an electronic latent submittal to identify the Type-7 or Type-13 records present. The field definition has been modified
to allow multiple occurrences in one transaction. The following table is a list of IMT values to be used to identify the records
present or biometric sets being referenced in the submission or response.
Note that the value of 2 is deprecated in favor of
the new value of 6, and the values 4 and 5 are deprecated in favor of the new value of 7.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1000
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: BIOMETRIC IMAGE
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordBiometricImageCategoryCode
Cardinality: 0…1000
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.064: Candidate List (CAN)
Description:
This grouped field shall contain a candidate list. It is composed of two subfields: Universal Control Number / UCN and Name /
NAM. For traditional encoding, each field will be separated by a {US} separator and will be provided for each candidate in the
list. Commas, hyphens, and blanks are allowed in the NAM subfield as specified in the NCIC Message Book, Part 1. Each
UCN and NAM set shall be separated from the next by the {RS} separator character. Note: The UCN can contain an FBI
number if appropriate for that record.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionData (0…1)/ ebts:TransactionResponseData (0…1)
Cardinality: 0…1
XML Level 2: ebts:TransactionCandidateList
Cardinality: 0…3
XML Level 3: ebts:Candidate
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
55
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.064_0: Candidate List - Subfields: Repeating sets of information items (CAN_0)
Description:
Repeating subfield for Candidate List.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
1
Occurrence Maximum
99
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: Active
XML Level 1: ebts:RecordTransactionData (0…1)/ebts:TransactionResponseData (0…1)
Cardinality: 0…1
XML Level 2: ebts:TransactionCandidateList (0…3)/ebts:Candidate (1…99)
Cardinality: 1…99
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.064_1: Candidate List - Universal Control Number (SI)
Description:
This conditional alphanumeric text field is used to identify the record with which the photos or images being requested are
associated, to identify candidates in a candidate list, or otherwise identify individual subject records.
The UCN can contain
an FBI number FNU if appropriate for that record.
Field Minimum
1
Field Maximum
40
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionData (0…1)/ebts:TransactionResponseData (0…1)
Cardinality: 0…1
XML Level 2: ebts:TransactionCandidateList (0…3)/ebts:Candidate (1…99)
Cardinality: 1…99
XML Level 3: j:PersonFBIIdentification/nc:IdentificationID
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
56
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.064_2: Candidate List - Name (NAM)
Description:
This alpha-special field contains the names of the subject. The format shall be the surname followed by a comma , followed by
the given names, which are separated by a space. Part IV of the NCIC Code Manual describes in greater detail the manner in
which each name is to be entered. Numerics are not allowed.
Field Minimum
3
Field Maximum
30
Character Types
AS
Special Characters
N/A
Occurrence Minimum
1
Occurrence Maximum
1
Format
NCIC Name Format:
,
…
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionData (0…1)/ebts:TransactionResponseData (0…1)
Cardinality: 0…1
XML Level 2: ebts:TransactionCandidateList (0…3)/ebts:Candidate (1…99)
Cardinality: 1…99
XML Level 3: ebts:PersonName
Cardinality: 0…1
XML Level 4: nc:PersonGivenName (0…1), nc:PersonMiddleName (0…1), nc:PersonSurName (1…1)
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
57
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.065: Repository Statistics Response (RSR)
Description:
This field contains a file generated by the NGI Latent Friction Ridge system that provides detailed statistics that can be used to
estimate the level of penetration of the repository given a set of search parameters defined in the search request. This field is
in the form of a large ASCII file that can contain up to 96,000 bytes of alphanumeric-special (ANS) data. This field contains five
items separated by tab characters: 1. Parameter name 2. Parameter Value 3. The fraction of the Criminal file having that
value of the parameter 4. The fraction of the Civil file having that value of the parameter 5. The fraction of the combined
Criminal and Civil files having the value of the parameter. In the traditional encoding formatting, the fields are separated with
“whitespace” (spaces and/or tabs) with MS DOS end-of-line convention (CR/LR). A period character is used as a decimal point
in the fraction values. The value should be interpreted as the proportion of records matching that category and code. Data
rows containing all zeroes will not be returned.
Field Minimum
1
Field Maximum
96000
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: REPOSITORY STATISTICS RESPONSE
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionData (0…1)/ ebts:TransactionResponseData (0…1)
Cardinality: 0…1
XML Level 2: ebts:TransactionRepositoryResponse
Cardinality: 0…1
XML Level 3: ebts:TransactionRepositoryResponseRecord
Cardinality: 1…*
XML Level 4: ebts:RepositoryParameterText (1…1), ebts:RepositoryParameterValueText (1…1),
ebts:RepositoryCriminalParameterPercent (1…1), ebts:RepositoryCivilParameterPercent (1…1),
ebts:RepositoryCombinedParameterPercent1 (1…1)
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
58
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.067: Image Capture Equipment (IMA)
Description:
This free text field is used to log the make, model, and serial number of the equipment used to acquire images. It is a grouped
field, comprised of three subfields: the Make MAK, Model MODL, and Serial Number SERNO of the acquisition device,
separated by the {US} separator character.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordImageCaptureDetail
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.067_1: Image Capture Equipment - Image Capture Equipment Legacy Derivable (MAK)
Description:
The Make of the acquisition device.
Field Minimum
1
Field Maximum
25
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordImageCaptureDetail
Cardinality: 0…1
XML Level 2: ansi-nist:CaptureDeviceMakeText
Cardinality: 1..1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
59
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.067_2: Image Capture Equipment - Originating Fingerprint Reading System Model Legacy Derivable
(MODL)
Description:
The Model of the acquisition device.
Field Minimum
1
Field Maximum
25
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordImageCaptureDetail
Cardinality: 0…1
XML Level 2: ansi-nist:CaptureDeviceModelText
Cardinality: 0..1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.067_3: Image Capture Equipment - Originating Fingerprint Reading System Model Legacy Derivable
(SERNO)
Description:
The Serial Number of the acquisition device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordImageCaptureDetail
Cardinality: 0…1
XML Level 2: ansi-nist:CaptureDeviceSerialNumberText
Cardinality: 0..1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
60
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.070: Request for Electronic Rap Sheet (RAP)
Description:
The purpose of this field is to allow the contributor to optionally request an electronic identity history summary (IdHS) of the
identity. An NIDR is returned if the submission results in a nonidentification. A ‘Y’ in this field indicates that an IdHS is desired,
while an omitted field or an ‘N’ in this field indicates that no IdHS should be returned with the response.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: YES NO CODES
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: dod-ebts:RecordRapSheetRequestIndicator
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.071: Action to be Taken (CAN)
Description:
This field is used to include text answers to submission requests to indicate that a latent case will be established or to indicate
recommendations for further actions in either latent or tenprint responses. This field will also be used to indicate action taken
by the FBI in response to electronic document e.g., disposition submissions. For the native encoding of this field, commas,
hyphens, ampersands, slashes, number signs, and blanks are all allowed as special characters.
Field Minimum
0
Field Maximum
300
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
T = Comma, Hyphen,
Ampersand, Slash,
Number Sign, Blanks
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:TransactionResponseData
Cardinality: 0..1
XML Level 3: ebts:TransactionActionText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
61
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.072: Fingerprint Images Updated (FIU)
Description:
This field contains the finger positions that were updated in the FBI’s Fingerprint Image Master File as a result of an electronic
request to update fingerprint images. The finger numbers for which image information is requested are selected from Table,
“Finger Position Code,” in the ANSI/NISTITL. Up to 13 individual finger numbers may be listed. For encoding, each finger
number will be separated from one another by the {RS} separator. If images of all 14 fingers were updated, the single
character “A” is shown instead of individual finger numbers. If no images were updated, an ‘N’ will be returned.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
13
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: FINGERPRINT IMAGE UPDATED CODES
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionData/ebts:TransactionFingerprintImagesUpdated
Cardinality: 0…1
XML Level 2: ansi-nist:FingerPositionCode
Cardinality: 0…13
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.073: Controlling Agency Identifier (CRI)
Description:
In Criminal and Civil transactions, the first instance of this field (CRI1) shall contain the Originating Agency Identifier (ORI) of
the organization controlling the transaction. The CRI may be different from the submitting agency’s ORI (e.g., the CSA), which
shall be placed in the ORI field. When the controlling agency is also the submitting agency, both the ORI and CRI fields shall
be submitted with the same identifier.
Field Minimum
9
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
3
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:RecordControllingAgency
Cardinality: 0…3
XML Level 3: nc:OrganizationIdentification/nc:IdentificationID
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
62
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.074: Finger Numbers Requested - Finger Position (FGP)
Description:
This field is used for latent submissions and searches and contains the fingerprint position code of the latent prints submitted.
If more than one finger is submitted with native encoding, then the codes will be separated by the {RS} character separator.
For latent searches, if multiple fingerprint images are included in one search, finger position is mandatory for all images. If
finger position is unknown, the search may contain only a single image, and the field FGP will be omitted or may contain
multiple guesses at the correct finger position in the FGP field. In this case, the PAT field must contain "00" in its Finger
Number subfield to indicate that the actual position is unknown (see also PAT entry). If the submitter cannot determine what
portion of the hand the latent image was derived from, then the position code should be omitted or “18” to spawn a search of
all friction ridge areas (fingerprints, palm prints, supplemental prints) within the FBI/CJIS repository If the submitter cannot
determine what portion of the hand the latent image was derived from, then the position code should be omitted or “18” to
spawn a search of all friction ridge areas (fingerprints, palm prints, supplemental prints) within the FBI/CJ
Field Minimum
2
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
10
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: FRICTION RIDGE GENERALIZED POSITION
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: biom-4.0.1:FingerPositionCode
Cardinality: 0…10
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
63
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.075: Electronic Rap Sheet (ERS)
Description:
This field shall contain the Electronic Identity History Summary (IdHS) of an identified subject. In the case of a nonidentification, the IdHS will consist of the Non-Identification Response (NIDR). For a TPRR transaction that contains multiple
candidates, the IdHS for each candidate will be concatenated into this field.
Field Minimum
4
Field Maximum
200000
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:TransactionResponseData
Cardinality: 0..1
XML Level 3: ebts:TransactionElectronicRapSheetText
Cardinality: 0…1
XML Level 4: ebts:TransactionBiometricImageEnrollmentRecordList
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.078: Penetration Query Response (PEN)
Description:
This field provides a response to the penetration query that includes a set of search parameters for a new search. The
response will be an estimated size, in percentage, of the repository that will be searched given the input parameters.
Field Minimum
2
Field Maximum
0
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Sunset
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:TransactionResponseData
Cardinality: 0..1
XML Level 3: ebts:TransactionPenetrationQueryResponsePercent
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
No
DoD EBTS 4.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
No
64
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.079: Number of Candidates' Images Returned (NCR)
Description:
This field contains the number of candidates the submitter desires to receive in response to a biometric Investigative Search
request per ranked candidate list, with a maximum of 99. If multiple candidate lists are to be returned in a search request, the If
the NIR in the request is greater than NCR in the request, CJIS will set NIR to the NCR value. This field is also found in the
responses to a biometric Investigative Search where it reflects the actual total number of candidates returned in the CNL for
the entire concatenated list. For EQRR, this field identifies the number of Identity History Summary reports that are be returned
in response to an EQHR.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:TransactionImagesRequestedQuantity
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.080: Response Explanation (EXP)
Description:
This field is free-form text to elaborate on the Response Code field for the Type-10 Photo record requested.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:TransactionResponseData
Cardinality: 0..1
XML Level 3: dod-ebts:TransactionReasonText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
65
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.082: Response Code (REC)
Description:
Natively, this one-byte alpha field will contain allowable values of "Y" or "N." This field is used in the PDR and PRR
transactions to indicate the status of the corresponding request. If the request contains any errors, the response code REC will
be set to "N." Otherwise it will be set to "Y."
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: YES NO CODES
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:TransactionResponseData
Cardinality: 0…1
XML Level 3: ebts:TransactionResponseIndicator
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.083: Unsolved Latent File (ULF)
Description:
This one-character alpha field is used to designate whether a latent image or features record in a search should be added to
the Unsolved Latent File. Submit a "Y" for yes. If negative, submit "N". If the field is omitted, the default behavior will be ‘N’.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: YES NO CODES
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:TransactionUnsolvedLatentFileIndicator
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
66
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.084: Amputated or Bandaged (AMP)
Description:
This repeating field contains information about amputated or bandaged fingerprints in a submission. The field is composed of
repeating sets of two subfields: Finger Position / FGP and Amputated Or Bandaged Code / AMPCD. This field is to be used
any time there are fewer than ten printable fingers in a tenprint submission for finger positions 1 – 10 or positions 11–15 to
specify when no slap fingerprint images are provided in the finger positions. A partially amputated finger should be printed and
be marked amputated, XX. If the finger’s image is missing for any reason, the UP code should be used. This field is used to tell
the AFIS which finger positions need to characterized. The UP code should only be used when the entire image is not
provided for fingerprints in the submission. This code will indicate that the AFIS matcher should ignore this image and not
include the image in the matching process. For the traditional encoding, the two-character finger position code is followed by
the {US} separator and the amputated or bandaged code. Each set of fingers/amp codes shall be separated by the {RS}
separator.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonFingerprintSet
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.084_0: Amputated or Bandaged - Subfields: Repeating sets of information items (AMP_0)
Description:
Repeating sub field for Amputated or Bandaged.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
13
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonFingerprintSet
Cardinality: 0…13
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
67
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.084_1: Amputated or Bandaged - Finger Position Code (FGP)
Description:
The two-character finger position code.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
01 <= FGP <= 15
Code List: FINGER POSITION CODE
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonFingerprintSet
Cardinality: 0…13
XML Level 3: itl:FingerprintImageFingerMissing
Cardinality: 0…13
XML Level 4: ansi-nist:FingerPositionCode
Cardinality: 1…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.084_2: Amputated or Bandaged - Amputated or Bandaged Code (AMPCD)
Description:
This information item provides the code that describes the reason the finger's image is missing.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: AMPUTATED OR BANDAGED CODE
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonFingerprintSet
Cardinality: 0…13
XML Level 3: itl:FingerprintImageFingerMissing
Cardinality: 0…13
XML Level 4: ansi-nist:FingerMissingCode
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
68
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.086: AFIS Segment Control Number (SCNA)
Description:
This field contains an identifier used to track or reference unsolved records. Legacy records that were deposited in the ULF
prior to NGI Increment 3 will be referenced with their legacy SCNA. All other unsolved records will be referenced with a UCN in
this field. The SCNA field is used, for example, to reference records in the ULF or UPF in the response to a latent or facial
investigative search respectively.
Field Minimum
1
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:AFISSegmentControlID
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.087: Treat As Adult (TAA)
Description:
A one-byte optional field to indicate whether a juvenile is to be processed as an adult. A "Y" indicates yes; an omitted field
indicates no. The TAA returned in a response is the same as the one submitted.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
If Yes, this field shall
contain "Y," if No, the field is
omitted.
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonAdultTreatmentIndicator
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
69
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.088: Note Field (NOT)
Description:
This free-text field is used to provide additional information regarding electronic latent submissions. For latent search
identification results feedback, the NOT field will be used to indicate the candidate from the SRL that matched the search
image. For UHN transactions, the NOT field will contain case related information about the search transaction with the hit that
generated the unsolicited notification. For ULM transactions, the NOT field will provide information related to latent search
images that are candidates for comparison with the unsolved latent (e.g., case-related identifiers or point of contact
information).
Field Minimum
1
Field Maximum
1000
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:TransactionDescriptionText
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.089: Match Score (MSC)
Description:
This field contains the match score from NGI for each candidate listed in the 2.064 CAN field.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:TransactionResponseData (0…1)/ebts:TransactionCandidateList(0…3)
Cardinality: 0…1
XML Level 3: ebts:TransactionCandidateList
Cardinality: 0…1
XML Level 4: ebts:CandidateMatchScoreValue
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
70
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.091: Ridge Core Delta One for Subpattern Classification (RCD1)
Description:
This grouped field contains information about the finger(s) ridge counts and is used for Native Mode searches in conjunction
with the Pattern Level Classification (PAT 2.034).
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonFingerprintSet
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.091_0: Ridge Core Delta One for Subpattern Classification - Subfields: Repeating sets of information
items (RCD1_0)
Description:
Repeating subfield for Ridge Core Delta One for Subpattern Classification.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: New-Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonFingerprintSet
Cardinality: 0…1
XML Level 3: ebts:FingerprintImageFinger
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
71
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.091_1: Ridge Core Delta One for Subpattern Classification - Finger Position Code (FGP)
Description:
The two-character finger position code.
Classification PAT.
The two-character finger position code as specified for the related Pattern Level
Field Minimum
2
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
10
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: FINGER POSITION CODE
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonFingerprintSet
Cardinality: 0…1
XML Level 3: ebts:FingerprintImageFinger
Cardinality: 0…10
XML Level 4: ansi-nist:FingerPositionCode
Cardinality: 1…10
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
72
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.091_2: Ridge Core Delta One for Subpattern Classification - First Subpattern Ridge Count (RCN1)
Description:
The Ridge Count Number (RCN1 and RCN2) represents the number of ridges between the core and the delta. For right and
left slant loops, this count identifies the ridges crossed on a line between the core and the delta. For whorls, both the RCN1
and the RCN2 values have meaning. Permissible values are 1 to 30 for actual ridge counts and 30 if there are more than 30
ridges. The count of 31 indicates an unknown number of ridges, and 0 indicates that the ridge count is not applicable.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
2
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: RIDGE COUNT NUMBER
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonFingerprintSet
Cardinality: 0…1
XML Level 3: ebts:FingerprintImageFinger
Cardinality: 0…10
XML Level 4: ansi-nist:RidgeCountValue
Cardinality: 0…2
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.092: Ridge Core Delta Two for Subpattern Classification (RCD2)
Description:
This grouped field contains information about the finger(s) ridge counts and is used for Native Mode searches in conjunction
with the Pattern Level Classification (PAT 2.034).
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonFingerprintSet/ ebts:FingerprintImageFinger
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
73
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.092_0: Ridge Core Delta Two for Subpattern Classification - Subfields: Repeating sets of information
items (RCD2_0)
Description:
Repeating subfield for Ridge Core Delta Two for Subpattern Classification.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: New-Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonFingerprintSet/ ebts:FingerprintImageFinger
Cardinality: 0…1
XML Level 3: ebts:FingerprintImageFinger
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.092_1: Ridge Core Delta Two for Subpattern Classification - Finger Position Code (FGP)
Description:
The two-character finger position code.
Classification PAT.
The two-character finger position code as specified for the related Pattern Level
Field Minimum
2
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
10
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: FINGER POSITION CODE
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonFingerprintSet/ ebts:FingerprintImageFinger
Cardinality: 0…1
XML Level 3: ebts:FingerprintImageFinger
Cardinality: 0…10
XML Level 4: ansi-nist:FingerPositionCode
Cardinality: 1…10
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
74
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.092_2: Ridge Core Delta Two for Subpattern Classification - Second Subpattern Ridge Count (RCN2)
Description:
The Ridge Count Number (RCN1 and RCN2) represents the number of ridges between the core and the delta. For right and
left slant loops, this count identifies the ridges crossed on a line between the core and the delta. For whorls, both the RCN1
and the RCN2 values have meaning. Permissible values are 1 to 30 for actual ridge counts and 30 if there are more than 30
ridges. The count of 31 indicates an unknown number of ridges, and 0 indicates that the ridge count is not applicable.
Deprecated for this set only.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
2
Character Types
N
Special Characters
N/A
Format
Constraints
N/A
Code List: RIDGE COUNT NUMBER
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:PersonFingerprintSet/ ebts:FingerprintImageFinger
Cardinality: 0…1
XML Level 3: ebts:RidgeCoreDelta
Cardinality: 0…10
XML Level 4: ansi-nist:RidgeCountValue
Cardinality: 0…2
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.095: Repository Statistics Response (RFR)
Description:
This one-character alpha field is used to indicate a user’s desire to have CJIS return a Type-9 features record associated with
an image requested via IRQ, LFIS, and LFFS transactions. For the Latent Investigative Search, the features and matched
minutiae will be returned to allow for an overlay on the image for comparison purposes. A features record will be returned if the
RFR value equals “Y.” A features record will not be returned if the field is omitted, its use is optional or if the value of RFR
equals “N.”
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
RFR = 'Y' or 'N'
Code List: YES NO CODES
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordFeaturesRequestIndicator
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
75
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.096: Request Photo Record (RPR)
Description:
This one-character alpha field is used to indicate a user’s desire to have the repository return a Type-10 photo record if one is
on file and disseminable. This field is used in conjunction with a Rapid Fingerprint Identification Search transaction RPIS.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: FBI REQUEST PHOTO RECORD CODES
Source: NGI-DOC-01078-10.0
Status: Sunset
XML Level 1: ebts:RecordPhotoRequestIndicator
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
No
2.098: Name of Designated Repository (NDR)
Description:
This field contains the numerical designation of the repository to be searched. Repository numbers are assigned by the CJIS
Division. Multiple entries in this field will indicate a desire to search more than one repository.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
10
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: DESIGNATED REPOSITORY NAME
Source: NGI-DOC-01078-10.0
Status: Active
XML Level 1: ebts:RecordFBIRepositoryCode
Cardinality: 0…10
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
76
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.300: BAT Global Unique Identifier (GUID)
Description:
This optional field shall contain the Biometrics Automated Toolset BAT Global Unique Identifier GUID as assigned to the
subject by the BAT.
Field Minimum
36
Field Maximum
38
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: dod‐ebts:BATGlobalUniqueID/nc:IdentificationID
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.302: Internment Serial Number (ISN)
Description:
The internment serial number (ISN) is a unique identification number assigned to each EPW, RP and CI taken into the custody
of the U.S. Armed Forces. The ISN will consist of three components, with the first two separated by a dash as follows: A. First
Component. The first component will contain five characters. The first two will be the alpha-characters ’US’. The third character
will be either the alpha or numeric designation for the command/theater under which the EPW, RP and CI came into the
custody of the U.S. The fourth and fifth positions are alpha-characters designating the EPW, RP and CI serving power. B.
Second Component. The second component is a six character numeric identifier. These numbers will be assigned
consecutively to all EPW, RP and CI processed through ISN assigning organizations. The Branch PWIC will assign blocks of
numbers to ISN assigning organization/elements in the supported theater. c. Third Component. The third component will
consist of an acronym identifying the classification of the individual: either EPW, RP, or CI, to represent Enemy Prisoner of
War, Retained Person, or Civilian Internee, respectively. Should an individual that was initially classified as an EPW later
determined to be a medically or religiously qualified retained person, the classification may be changed to “RP”with the
approval of the EPW command/brigade.
Field Minimum
15
Field Maximum
16
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Army Regulation 190-8
Status: Active
XML Level 1: dod-ebts:InternmentSerialNumberID/nc:IdentificationID
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
77
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.303: DoD Number (DOD_NO)
Description:
Number assigned to the enrollment by a DoD repository.
Field Minimum
1
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
5
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: dod‐ebts:DoDNumber/nc:IdentificationID
Cardinality: 0…5
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.308: Electronic Data Interchange Personal Identifier (EDIPI)
Description:
The identifier for the dossier collection of documents about the subject.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: dod‐ebts:ElectronicDataInterchangePersonalID/nc:IdentificationID
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
78
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.309: Defense Biometric Identification System Identifier (DBIDS_ID)
Description:
This optional field shall contain the DBIDS ID unique identifier for a DBIDS user.
Field Minimum
10
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: dod‐ebts:DBIDSID/nc:IdentificationID
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.310: Biometric Subject Personnel Type (PER_TYPE)
Description:
Contains a code that describes a general category or classification of a biometric subject by the reason they are of interest
when encountered.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
47
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: dod‐ebts:PersonCategoryCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
79
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.310_1: Biometric Subject Personnel Type - Person Category Code (PER_CAT)
Description:
A data type for an enumeration of the type of person category codes.
Field Minimum
3
Field Maximum
30
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AS
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: PERSON CATEGORY CODES
Source: EBTS v4.1
Status: New-Active
XML Level 1: dod‐ebts:PersonCategoryCode
Cardinality: 0…1
XML Level 2: dod-ebts:PersonCategoryCodeList
Cardinality: 1…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
No
DoD EBTS 4.1:
Yes
2.310_2: Biometric Subject Personnel Type - Foreign National Citizenship (FN_GENC)
Description:
The GENC Country Code of the Foreign National Hire.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
N/A
Format
Constraints
N/A
Source: EBTS v4.1
Status: New-Active
XML Level 1: dod‐ebts:PersonCategoryCode
Cardinality: 0…1
XML Level 2: dod-ebts:ForeignNationalGENC
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
80
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.310_3: Biometric Subject Personnel Type - Agency of Employment (EMPLOY_BY)
Description:
The agency to which the individual works for.
Field Minimum
3
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
Constraints
N/A
Code List: EMPLOYED BY CODES
Source: EBTS v4.1
Status: New-Active
XML Level 1: dod‐ebts:PersonCategoryCode
Cardinality: 0…1
XML Level 2: dod-ebts:EmployedBy
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
No
DoD EBTS 4.1:
Yes
2.310_4: Biometric Subject Personnel Type - Country Employed In (WORK_IN)
Description:
The GENC Country Code to label the country of employment.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
N/A
Format
Constraints
N/A
Source: EBTS v4.1
Status: New-Active
XML Level 1: dod‐ebts:PersonCategoryCode
Cardinality: 0…1
XML Level 2: dod-ebts:WorkingIn
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
81
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.310_5: Biometric Subject Personnel Type - Comment (PER_TYP_COM)
Description:
Additional comments on the employee.
Field Minimum
1
Field Maximum
128
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
Constraints
N/A
Source: EBTS v4.1
Status: New-Active
XML Level 1: dod‐ebts:PersonCategoryCode
Cardinality: 0…1
XML Level 2: nc:CommentText
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
No
DoD EBTS 4.1:
Yes
2.316: Request Mug Shot (RMS)
Description:
An indicator that requests a return of the most recent mug shot frontal pose on file with DoD for the given biometric subject.
Otherwise, this field may be omitted.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: YES NO CODES
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: dod-ebts:MugShotRequestIndicator
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
82
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.317: Request IAFIS Search (RIS)
Description:
This optional field shall indicate a request to search IAFIS in addition to the DoD ABIS.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: YES NO CODES
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: dod-ebts:IAFISSearchRequestIndicator
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.318: XML-based Rap Sheet (XML)
Description:
An electronic rap sheet for the biometric subject in XML format. Notes: The electronic rap sheet shall consist of lines with a
maximum of 174 characters per line. The response formatting shall conform to a future DoD standard.
Field Minimum
4
Field Maximum
400000
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: dod‐ebts:TransactionXMLRapSheetText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
83
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.334: Submission Color Code (SCC)
Description:
The color classification of the biometric subject. Red Force includes persons that are Enemy Prisoners of War and Enemy
Combatants. Blue Force includes persons that are U.S. Military, DoD Contractors, or DoD civilians. Grey Force includes
person that are local nationals, Third Country Nationals or Contractors, or Coalition.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: COLOR CLASSIFICATION CODES
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: dod‐ebts:PersonSubmissionColorCode
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.335: Dossier Number (DOSSIER)
Description:
The identifier for the dossier collection of documents about the subject.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: dod‐ebts:DossierNumber/nc:IdentificationID
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
84
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.350: Alert (ALERT)
Description:
This field contains alert information that will be used in the case where a new submission into the system results in an
IDENTED response against the submission containing the alert data. This field should be used in response messages only,
and should not be used when submitting new biometric files to DoD ABIS. This field contains four information items and all
four must be completed if this field is used. It consists of: Alert Category, Alert Value, Alert Contact and Alert Detail.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: dod‐ebts:Alert
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.350_0: Alert - Subfields: Repeating sets of information items (ALERT_0)
Description:
Repeating subfield for Alert.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
1
Occurrence Maximum
52
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: New-Active
XML Level 1: dod‐ebts:Alert
Cardinality: 0…*
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
85
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.350_1: Alert - Alert Category (ALERT_CAT)
Description:
The alert category assigned to a biometric subject indicating what action, if any, should be taken regarding the biometric
subject if he/she is encountered. DoD ABIS and NGIC should have coordination on acceptable ALERT Categories.
Field Minimum
1
Field Maximum
100
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: dod‐ebts:Alert
Cardinality: 0…*
XML Level 2: dod‐ebts:AlertCategory
Cardinality: 1…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.350_2: Alert - Alert Identifier (ALERT_ID)
Description:
The unique identifier of the parallel relational database to DoD ABIS
Field Minimum
1
Field Maximum
12
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: dod‐ebts:Alert
Cardinality: 0…*
XML Level 2: dod‐ebts:DBIDSID
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
86
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.350_3: Alert - Alert Contact (ALERT_CONTACT)
Description:
The agency and individual contact reference responsible for establishing the alert.
Field Minimum
1
Field Maximum
255
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: dod‐ebts:Alert
Cardinality: 0…*
XML Level 2: dod‐ebts:AlertContactName
Cardinality: 1…1
XML Level 3: nc:PersonDescriptionText
Cardinality: 1..1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.350_4: Alert - Alert Detail (ALERT_DETAIL)
Description:
Special handling instructions or other information about the individual identified in an alert.
Field Minimum
1
Field Maximum
500
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: dod‐ebts:Alert
Cardinality: 0…*
XML Level 2: dod-ebts:AlertDetailDescriptionText
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
87
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.351: Encounter Protection (EP)
Description:
The encounter protection fields defined below allow for an incoming submission to identify and conceal associations made with
other previously submitted transactions. This set of fields can be used by an individual ORI to either protect or unprotect a
single associated match or all associated matches. This field contains information that will be used in the case where a new
submission wants the subject’s association(s) to be protected or unprotected. Protection of either an individual encounter or
multiple encounters will be decided based on the entries in this field. This field contains two subfields and both must be
completed if this field is used.
DoD EBTS v4.1 identifies Field 2.351 for Encounter Protection. However, Field 2.351
Encounter Protection shall not be configurable by the user or the biometric capturing device i.e., Encounter Protection is for
internal use only at this time. Submissions from organizations that must use Encounter Protection should contact BIMA
operations and coordinate the use of Encounter Protection with them. It is the responsibility of ABIS to follow the Encounter
Protection business rules based on the ORI
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: dod‐ebts:EncounterProtection
Cardinality: 0…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.351_1: Encounter Protection - Encounter Protection Function (EP_FUN)
Description:
This field contains information that will be used to determine the action to be taken. It will contain a single numeric value
0=Unprotect, 1=Protect.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: ENCOUNTER PROTECTION FUNCTION CODES
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: dod‐ebts:EncounterProtection
Cardinality: 0…1
XML Level 2: dod‐ebts:EncounterProtectionFunctionCode
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
88
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.351_2: Encounter Protection - Encounter Protection Level (EP_LEVEL)
Description:
This field contains information that will be used to determine the level of protection being assigned to the subject being
searched. This field will contain a single numeric value 0 = Single Encounter, 1 = All Encounter.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: ENCOUNTER PROTECTION LEVEL CODES
Source: DOD_BTF_TS_EBTS_Nov06_01.02.00
Status: Active
XML Level 1: dod‐ebts:EncounterProtection
Cardinality: 0…1
XML Level 2: dod‐ebts:EncounterProtectionLevelCode
Cardinality: 1…1
DoD EBTS 1.2:
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.850: Biometric Modality Available (BIO_MOD_0)
Description:
List the biometric modalities available within a specific designated repository and the identifier assigned to it by the repository if
applicable.
Part of a response from a submission or search.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for Blue Force capability. Pending approval
Status: Emerging
XML Level 1: dod‐ebts:BiometricModality
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
89
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.850_0: Biometric Modality Available - Subfields: Repeating sets of information items (BIO_MOD)
Description:
Repeating subfield for Biometric Modality Available.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
*
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: Emerging
XML Level 1: dod‐ebts:BiometricModality
Cardinality: 0…*
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.850_1: Biometric Modality Available - Modality Type (MOD_TYPE)
Description:
The type of biometric modality indicated.
Field Minimum
3
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: MODALITY TYPE CODES
Source: Developed for Blue Force capability. Pending approval
Status: Emerging
XML Level 1: dod‐ebts:BiometricModality
Cardinality: 0…*
XML Level 2: dod-ebts:ModalityTypeCode
Cardinality: 0..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
90
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.850_2: Biometric Modality Available - Modality Sub-Type (MOD_STYPE)
Description:
A more specific type of the particular biometric modality being referenced.
For example, finger position code is the
Modality Sub-Type of Fingerprint Image, the left or right position of the eye is the Biometric Sub-Type of Iris Image, and subject
pose code is the Biometric Sub-Type of a Facial Photo Image.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: MODALITY SUB-TYPE CODES
Source: Developed for Blue Force capability. Pending approval
Status: Emerging
XML Level 1: dod‐ebts:BiometricModality
Cardinality: 0…*
XML Level 2: dod-ebts:ModalitySubTypeCode
Cardinality: 0..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.850_3: Biometric Modality Available - Name of Designated Repository (MOD_REPO)
Description:
This field contains the numerical designation of the repositories to be searched. Repository numbers are assigned by the CJIS
Division. Multiple entries will be separated by the {RS} separator.
This information item indicates the repository where the
modality is located.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: DESIGNATED REPOSITORY NAME
Source: Developed for Blue Force capability. Pending approval
Status: Emerging
XML Level 1: dod‐ebts:BiometricModality
Cardinality: 0…*
XML Level 2: ebts:RecordFBIRepositoryCode" /nc:IdentificationID
Cardinality: 0..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
91
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.850_4: Biometric Modality Available - Modality Location Originating Agency Identifier (MOD_LOC)
Description:
The Originating Agency Identifier of the location which has the biometric modality available for the identified biometric subject.
Field Minimum
9
Field Maximum
9
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for Blue Force capability. Pending approval
Status: Emerging
XML Level 1: dod‐ebts:BiometricModality
Cardinality: 0…*
XML Level 2: nc:Agency
Cardinality: 0..1
XML Level 3: nc:OrganizationDescriptionText
Cardinality: 1.1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.850_5: Biometric Modality Available - Modality Retrieval Identifier Type (MOD_ID_TYPE)
Description:
The type of identifier used to retrieve the biometric modality e.g. TCN, FNU, DOD, SSN, ISN, GUID, etc. It is up to the
Application Profile to determine what the appropriate identifier types should be.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: IDENTIFIER TYPE CODES
Source: Developed for Blue Force capability. Pending approval
Status: Emerging
XML Level 1: dod‐ebts:BiometricModality
Cardinality: 0…*
XML Level 2: dod-ebts:ModalityIdentifierTypeCode
Cardinality: 0..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
92
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.850_6: Biometric Modality Available - Modality Retrieval Identifier (MOD_ID)
Description:
The identifier used to retrieve the biometric modality.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for Blue Force capability. Pending approval
Status: Emerging
XML Level 1: dod‐ebts:BiometricModality
Cardinality: 0…*
XML Level 2: dod-ebts:RetrievalID/nc:IdentificationID
Cardinality: 0..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.850_7: Biometric Modality Available - Comment (MOD_COM)
Description:
The optional Comment field appears in many record types and may be used to insert free text information. It is not reserved
exclusively for log-related information but has historically often been used for this purpose. It is limited to a maximum of 126
characters. This maximum size was established in order to maintain consistency across encodings. The maximum size differed
in the 2007 and 2008 versions of the standard.
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for Blue Force capability. Pending approval
Status: Emerging
XML Level 1: dod‐ebts:BiometricModality
Cardinality: 0…*
XML Level 2: nc:CommentText
Cardinality: 0..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
93
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.851: Biometric Modality Request (BIO_MODR)
Description:
Specify the biometric modality being requested.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for Blue Force capability. Pending approval
Status: Emerging
XML Level 1: dod‐ebts:BiometricModalityRequest
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.851_1: Biometric Modality Request - Modality Type (MODR_TYPE)
Description:
The type of biometric modality indicated.
Field Minimum
3
Field Maximum
6
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: MODALITY TYPE CODES
Source: Developed for Blue Force capability. Pending approval
Status: Emerging
XML Level 1: dod‐ebts:BiometricModalityRequest
Cardinality: 0…1
XML Level 2: dod-ebts:ModalityTypeCode
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
94
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.851_2: Biometric Modality Request - Modality Sub-Type (MODR_SUBTYPE)
Description:
A more specific type of the particular biometric modality being referenced.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: MODALITY SUB-TYPE CODES
Source: Developed for Blue Force capability. Pending approval
Status: Emerging
XML Level 1: dod‐ebts:BiometricModalityRequest
Cardinality: 0…1
XML Level 2: dod-ebts:SubTypeCode
Cardinality: 0..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.851_3: Biometric Modality Request - Name of Designated Repository (MODR_REPO)
Description:
This field contains the numerical designation of the repositories to be searched. Repository numbers are assigned by the CJIS
Division. Multiple entries will be separated by the {RS} separator.
This information item indicates the repository where the
modality is located.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: DESIGNATED REPOSITORY NAME
Source: Developed for Blue Force capability. Pending approval
Status: Emerging
XML Level 1: dod‐ebts:BiometricModalityRequest
Cardinality: 0…1
XML Level 2: dod-ebts:RespositoryCode
Cardinality: 0..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
95
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.851_4: Biometric Modality Request - Modality Location Originating Agency Identifier (MODR_AGENCY)
Description:
The Originating Agency Identifier of the location which has the biometric modality available for the identified biometric subject.
Field Minimum
9
Field Maximum
9
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for Blue Force capability. Pending approval
Status: Emerging
XML Level 1: dod‐ebts:BiometricModalityRequest
Cardinality: 0…1
XML Level 2: nc:Agency
Cardinality: 0..1
XML Level 3: nc:OrganizationDescriptionText
Cardinality: 1.1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.851_5: Biometric Modality Request - Modality Retrieval Identifier Type (MODR_ID_TYPE)
Description:
The type of identifier used to retrieve the biometric modality e.g. TCN, FNU, DOD, SSN, ISN, GUID, etc. It is up to the
Application Profile to determine what the appropriate identifier types should be.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: IDENTIFIER TYPE CODES
Source: Developed for Blue Force capability. Pending approval
Status: Emerging
XML Level 1: dod‐ebts:BiometricModalityRequest
Cardinality: 0…1
XML Level 2: dod-ebts:ModalityIdentifierCode
Cardinality: 0..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
96
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.851_6: Biometric Modality Request - Modality Retrieval Identifier (MODR_ID)
Description:
The identifier used to retrieve the biometric modality.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for Blue Force capability. Pending approval
Status: Emerging
XML Level 1: dod‐ebts:BiometricModalityRequest
Cardinality: 0…1
XML Level 2: dod-ebts:ModalityRetrievalID/nc:IdentificationID
Cardinality: 0..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.851_7: Biometric Modality Request - Requested Image Quantity (MODR_QUAL)
Description:
The maximum number of images the requester desires to receive.
Field Minimum
0
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for Blue Force capability. Pending approval
Status: Emerging
XML Level 1: dod‐ebts:BiometricModalityRequest
Cardinality: 0…1
XML Level 2: dod-ebts:ImageQuantity
Cardinality: 0..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
97
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.852: Biometric Subject Body Build (SUBJ_BUILD)
Description:
The physique of an individual.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: BODY BUILD CODES
Source: Developed for BAT V5 AP. Pending approval.
Status: Emerging
XML Level 1: nc:PersonBuildText
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.853: Biometric Subject Education (SUBJ_ED)
Description:
The highest level of education the biometric subject has obtained.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: EDUCATION CODES
Source: Developed for BAT V5 AP. Pending approval.
Status: Emerging
XML Level 1: nc:PersonEducationLevelText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
98
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.854: Collection Unit (SUBJ_SPEC)
Description:
Information regarding the unit that collected the biometric sample.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile. Pending approval.
Status: Emerging
XML Level 1: dod‐ebts:BiometricCollectionUnit
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.854_1: Collection Unit - Superior Unit (SUBJ_SPEC_VAL)
Description:
The name of the superior unit.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile. Pending approval.
Status: Emerging
XML Level 1: dod‐ebts:BiometricCollectionUnit
Cardinality: 0…1
XML Level 2: dod-ebts:SuperiorUnitDescriptor
Cardinality: 1..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
99
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.854_2: Collection Unit - SubSuperior Unit (SUBJ_SPEC_PRO)
Description:
The name of the sub superior unit.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile. Pending approval.
Status: Emerging
XML Level 1: dod‐ebts:BiometricCollectionUnit
Cardinality: 0…1
XML Level 2: dod-ebts:SubSuperiorUnitDescription
Cardinality: 0..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.855: Military Association (MIL_ASSOC)
Description:
The military branch that the subject is affiliated with. The set consists of the country that the military branch belongs in, the
name of the military branch, the subject's rank/grade, and an indicator regarding if the subject is active or inactive in the
military branch.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile. Pending approval.
Status: Emerging
XML Level 1: dod‐ebts:MilitaryAssoc
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
100
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.855_1: Military Association - Military Branch Country Code (MIL_CNTRY)
Description:
The country the military branch belongs in.
Field Minimum
2
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: GENC ALPHA3 CODES
Source: Developed for BAT V5 Application Profile. Pending approval.
Status: Emerging
XML Level 1: dod‐ebts:MilitaryAssoc
Cardinality: 0…1
XML Level 2: dod-ebts:MilitaryCountryGENCCode
Cardinality: 1..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.855_2: Military Association - Military Branch Name (MIL_BRNCH)
Description:
The name of the military branch that the subject belongs in.
apply, then enter "Unknown".
E.G. Army, Navy, Air Force, Marine Corps. If this does not
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile. Pending approval.
Status: Emerging
XML Level 1: dod‐ebts:MilitaryAssoc
Cardinality: 0…1
XML Level 2: nc:MilitaryBranchName
Cardinality: 1..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
101
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.855_3: Military Association - Rank Grade Code (MIL_RANK)
Description:
The military rank or civilian rank of the person.
Rank/Grade Codes of the Military Branch of the Country indicated.
Field Minimum
1
Field Maximum
20
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: MILITARY RANK GRADE CODES
Source: Developed for BAT V5 Application Profile. Pending approval.
Status: Emerging
XML Level 1: dod‐ebts:MilitaryAssoc
Cardinality: 0…1
XML Level 2: dod‐ebts:MilitaryRankCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.855_4: Military Association - Military Active Indicator (MIL_IND)
Description:
Indicator whether the subject is active or inactive in the associated military.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: MILITARY ACTIVE INDICATOR CODES
Source: Developed for BAT V5 Application Profile. Pending approval.
Status: Emerging
XML Level 1: dod‐ebts:MilitaryAssoc
Cardinality: 0…1
XML Level 2: dod‐ebts:MilitaryIndicator
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
102
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.856: Previous Transaction - Identification (PREV_TRAN)
Description:
The set shall contain a transaction identifier from an earlier submission. One usage might be to obtain the current transaction
status. Another usage might be to request cancellation of the transaction. Different types of identifiers might be used to
reference the transaction.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for Blue Force capability. Pending approval.
Status: Emerging
XML Level 1: dod-ebts:PreviousTransaction
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.856_1: Previous Transaction - Identifier Type (PREV_TRAN_1)
Description:
The category of the identifier such as TCN, EncounterID, etc. used to identify a previous transaction.
Field Minimum
1
Field Maximum
20
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for Blue Force capability. Pending approval.
Status: Emerging
XML Level 1: dod-ebts:PreviousTransaction
Cardinality: 0…1
XML Level 2: nc:ActivityCategoryText
Cardinality: 1..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
103
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.856_2: Previous Transaction - Previous Transaction Identifier (PREV_TRAN_2)
Description:
The value of the identifier used to identify a previous transaction.
Field Minimum
1
Field Maximum
100
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for Blue Force capability. Pending approval.
Status: Emerging
XML Level 1: dod-ebts:PreviousTransaction
Cardinality: 0…1
XML Level 2: dod-ebts:PreviousActivity/nc:IdentificationID
Cardinality: 1..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.856_3: Previous Transaction - Transaction Association (PREV_TRAN_3)
Description:
An augmentation point for the previous activity.
Field Minimum
1
Field Maximum
100
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Added in NEIM Core to nc:PreviousAcitivity
Status: Emerging
XML Level 1: dod-ebts:PreviousTransaction
Cardinality: 0…1
XML Level 2: nc:PreviousActivityAssociation
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
104
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.858: Vendor Software (SOFT_VEN)
Description:
Information regarding the software application provided by vendor. The set consists of Software Vendor Name, Software
Application Name and Software Application Version Number.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile.
Status: Emerging
XML Level 1: dod-ebts:VendorSoftware
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.858_0: Vendor Software - Subfields: Repeating sets of information items (SOFT_VEN_0)
Description:
Repeating subfield for Vendor Software.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
1
Occurrence Maximum
99
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile.
Status: Emerging
XML Level 1: dod-ebts:VendorSoftware
Cardinality: 1..99
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
105
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.858_1: Vendor Software - Software Vendor Name (SOFT_VEN_1)
Description:
The name of the software vendor e.g. Microsoft.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile.
Status: Emerging
XML Level 1: dod-ebts:VendorSoftware
Cardinality: 1..1
XML Level 2: dod-ebts:SoftwareVendorNameText
Cardinality: 1..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.858_2: Vendor Software - Software Application Name (SOFT_VEN_2)
Description:
The name of the software application e.g. Excel.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile.
Status: Emerging
XML Level 1: dod-ebts:VendorSoftware
Cardinality: 0..1
XML Level 2: dod-ebts:SoftwareName
Cardinality: 1..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
106
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.858_3: Vendor Software - Software Application Version Number (SOFT_VEN_3)
Description:
The number that specifies the software vendor application version number.
Build number the vendor assigned to the application.
May consist the Major, Minor, Revision and
Field Minimum
1
Field Maximum
255
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile.
Status: Emerging
XML Level 1: dod-ebts:VendorSoftware
Cardinality: 0..1
XML Level 2: dod-ebts:softwareVersionText
Cardinality: 1..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.859: Biometric Subject Previous Residence (SUBJ_PREV_RESIDE)
Description:
The addresses of the previous residence of the biometric subject.
Field Minimum
Field Maximum
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile.
Status: Emerging
XML Level 1: dod-ebts:BiometricSubjectPreviousResidence
Cardinality: PersonPreviousResidenceLocation
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
107
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.859_1: Biometric Subject Previous Residence - Address Line 1 (SUBJ_PREV_RESIDE_1)
Description:
The street, including both number and name.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile.
Status: Emerging
XML Level 1: dod-ebts:BiometricSubjectPreviousResidence
Cardinality: 0…1
XML Level 2: nc:StreetFullText
Cardinality: 0..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.859_2: Biometric Subject Previous Residence - Address Line 2 (SUBJ_PREV_RESIDE_2)
Description:
Additional information about the street e.g. apt #.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile.
Status: Emerging
XML Level 1: dod-ebts:BiometricSubjectPreviousResidence
Cardinality: 0…1
XML Level 2: nc:StreetFullText
Cardinality: 0..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
108
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.859_3: Biometric Subject Previous Residence - City (SUBJ_PREV_RESIDE_3)
Description:
Name of the city.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile.
Status: Emerging
XML Level 1: dod-ebts:BiometricSubjectPreviousResidence
Cardinality: 0…1
XML Level 2: nc:LocationCityName
Cardinality: 0..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.859_4: Biometric Subject Previous Residence - State / Province (SUBJ_PREV_RESIDE_4)
Description:
The state, province or subdivision of a location.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile.
Status: Emerging
XML Level 1: dod-ebts:BiometricSubjectPreviousResidence
Cardinality: 0…1
XML Level 2: nc:LocationStateName
Cardinality: 0..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
109
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.859_5: Biometric Subject Previous Residence - Country Code (SUBJ_PREV_RESIDE_5)
Description:
The GENC alpha3 country code.
(genc:CountryAlpha3CodeType).
The DoD EBTS v4.1 default for this field is the GENC three character alpha codelist
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile.
Status: Emerging
XML Level 1: dod-ebts:BiometricSubjectPreviousResidence
Cardinality: 0…1
XML Level 2: nc:LocationCountryGENCCode
Cardinality: 0..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.859_6: Biometric Subject Previous Residence - Postal Code (SUBJ_PREV_RESIDE_6)
Description:
Alphanumeric code assigned to groups of addresses by various national postal systems throughout the world.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile.
Status: Emerging
XML Level 1: dod-ebts:BiometricSubjectPreviousResidence
Cardinality: 0…1
XML Level 2: nc:LocationPostalCode
Cardinality: 0..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
110
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.859_7: Biometric Subject Previous Residence - Neighborhood / District (SUBJ_PREV_RESIDE_7)
Description:
A geographically localized community within a larger city, town or suburb.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile.
Status: Emerging
XML Level 1: dod-ebts:BiometricSubjectPreviousResidence
Cardinality: 0…1
XML Level 2: nc:LocaleNeighborhoodName
Cardinality: 0..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.859_8: Biometric Subject Previous Residence - Village (SUBJ_PREV_RESIDE_8)
Description:
Small population unit, typically rural, held together by common economic and political ties.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Developed for BAT V5 Application Profile.
Status: Emerging
XML Level 1: dod-ebts:BiometricSubjectPreviousResidence
Cardinality: 0…1
XML Level 2: dod‐ebts:LocationVillageName
Cardinality: 0..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
111
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.859_9: Biometric Subject Previous Residence - Address Validity (SUBJ_PREV_RESIDE_9)
Description:
This field defines the validity of the address information.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: VALIDITY CODES
Source: Developed for BAT V5 Application Profile.
Status: Emerging
XML Level 1: dod-ebts:BiometricSubjectPreviousResidence
Cardinality: 0…1
XML Level 2: dod‐ebts:LocationAddressValidityCode
Cardinality: 0..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.859_10: Biometric Subject Previous Residence - Start Date (SUBJ_PREV_RESIDE_10)
Description:
The date that the subject began residing at this address.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
YYYYMMDD
Constraints
N/A
Source: Developed for BAT V5 Application Profile.
Status: Emerging
XML Level 1: dod-ebts:BiometricSubjectPreviousResidence
Cardinality: 0…1
XML Level 2: nc:StartDate/nc:Date
Cardinality: 0..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
112
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.859_11: Biometric Subject Previous Residence - End Date (SUBJ_PREV_RESIDE_11)
Description:
The date that the subject ceased to reside at this address.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
YYYYMMDD
Constraints
N/A
Source: Developed for BAT V5 Application Profile.
Status: Emerging
XML Level 1: dod-ebts:BiometricSubjectPreviousResidence
Cardinality: 0…1
XML Level 2: nc:EndDate/nc:Date
Cardinality: 0..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2010: Number of Images Requested (NIR)
Description:
This optional field contains the number of maximum candidate images the submitter desires to receive in response to a
biometric Investigative search request for a given candidate list. If multiple candidate lists are to be returned the NIR value
applies to each. If NIR is omitted in a biometric investigative search request, it defaults to 20. This field is also found in the
responses to a biometric Investigative search where it reflects the actual number of candidates with image returned in the CNL
field for the entire concatenated list.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordImagesRequestedQuantity
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
113
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2022: Contributor Assigned Identification Number (CIDN)
Description:
This field is the unique number assigned to a single biographic search by the contributor. This field shall contain ten bytes of
alphanumeric data. This is a field in a Type-2 biographic search request EQHR.
Field Minimum
10
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionActivity
Cardinality: 0…1
XML Level 2: ebts:ContributorAssignedIdentificationNumber/nc:IdentificationID
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2023: Supplementary Identity Information (SII)
Description:
This field will contain identity information not within the scope of the standard NGI Identity History Summary. The format and
content of the information in this field may vary for different transactions.
Field Minimum
4
Field Maximum
10000
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:TransactionResponseData (0…1)/ebts:TransactionCandidateList(0…3)
Cardinality: 0…1
XML Level 3: ebts:TransactionSupplementaryIdentityInformationText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
114
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2024: Hit Type Indicator (HTI)
Description:
This field will contain a code for the type of hit that generated an unsolicited notification. In the future, a fixed list of values will
be created to populate this field. This field will initially be used for the UHN TOT for RISC Notifications. The value will be
"RISC" for this initial use.
Field Minimum
1
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AS
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: HIT TYPE
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:TransactionResponseData
Cardinality: 0…1
XML Level 3: ebts:TransactionHitCategoryCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2028: Biometric Image Description (BID)
Description:
This repeating set contains information about biometric images the user is requesting in the submission. Each repeating set
consists of the following subfields: 1. UCN of the identity or latent record, 2. IMT image type of the image to be retrieved, 3. BSI
of the biometric set to be retrieved, 4. FNR is the fingerprint or palmprint position code of the image to be retrieved, 5. PPD of
the supplemental image to be retrieved, E. PPD of the supplemental image to be retrieved when FNR equals supplemental. F.
POS of a face image, G. SMT code for a scar, mark, or tattoo image.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData (0…1)/ebts:TransactionBiometricImagesRequested (0…1)
Cardinality: 0…1
XML Level 2: ebts:BiometricImageDescription
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
115
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2028_0: Biometric Image Description - Subfields: Repeating sets of information items (BID_0)
Description:
Repeating subfield for Biometric Image Description.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
1
Occurrence Maximum
1000
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.1
Status: Emerging
XML Level 1: ebts:RecordTransactionData (0…1)/ebts:TransactionBiometricImagesRequested (0…1)
Cardinality: 0…1
XML Level 2: ebts:BiometricImageDescription
Cardinality: 0…1000
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2028_1: Biometric Image Description - FBI Number/UCN (SI)
Description:
SI (Subject Identifier) of the identity or latent record.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData (0…1)/ebts:TransactionBiometricImagesRequested (0…1)
Cardinality: 0…1
XML Level 2: ebts:BiometricImageDescription
Cardinality: 0…1000
XML Level 3: j:PersonFBIIdentification/nc:IdentificationID
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
116
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2028_2: Biometric Image Description - Image Type (IMT)
Description:
The Image Type information items can be used to specify which types of biometric sets are requested. The list of IMT values to
be used in an electronic latent submittal to identify the Type-7 or Type-13 records present in Biometric Image code.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
IMT = 1, 2, 3 or 4; integer
Code List: BIOMETRIC IMAGE
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData (0…1)/ebts:TransactionBiometricImagesRequested (0…1)
Cardinality: 0…1
XML Level 2: ebts:BiometricImageDescription
Cardinality: 0…1000
XML Level 3: ebts:BiometricImageCategoryCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2028_3: Biometric Image Description - Biometric Set Identifier (BSI)
Description:
Code used to identify the specific biometric set being requested. If the BSI (2.2028_3) information item is not present, the
representative biometric set(s) are retrieved for the identity specified in the Subject Identifier (SI) item. The representative set
for fingerprints will be a composite fingerprint set of images, while the representative set for palm prints or supplemental
fingerprint and palm print will be the latest set enrolled.
Field Minimum
4
Field Maximum
24
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
integer
Code List: BIOMETRIC SET IDENTIFIER CODES
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData (0…1)/ebts:TransactionBiometricImagesRequested (0…1)
Cardinality: 0…1
XML Level 2: ebts:BiometricImageDescription
Cardinality: 0…1000
XML Level 3: ebts:BiometricSetID
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
117
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2028_4: Biometric Image Description - Friction Ridge Position Requested (FNR)
Description:
The friction ridge number requested.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
fingerprint or palmprint
position code
Code List: FINGER POSITION CODES and PALM POSITION CODES
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData (0…1)/ebts:TransactionBiometricImagesRequested (0…1)
Cardinality: 0…1
XML Level 2: ebts:BiometricImageDescription
Cardinality: 0…1000
XML Level 3: ansi-nist:FrictionRidgePositionCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
118
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2028_5: Biometric Image Description - Print Position Descriptors (PPD)
Description:
This field is used to specify which Supplemental Fingerprint and Palm Print images are being requested. This PPD is a subfield
to fields of Type Set. This subfield will be present if and only if the subfield Friction ridge Generalized Position code FGP or the
Friction ridge Numbers Requested FNR code "19" appears in the Set field.These PPD subfields have no subfields unlike PPD
2.2030. This field shall consist of two mandatory information items. The first is the Probable Decimal finger Position code 0-10
taken from the ANSI/NIST-ITL specification. But for the finger position it must be a two character numeric; implying a leading
zero for positions 0 thru 9. The second code information item is the Finger Image Code; it also is taken from the ANSI/NIST-ITL
specification to indicate the portion of the EJI or tip image. There may be up to 8 such images for a single finger, but NGI only
expects the values of EJI. Both the probable decimal friction ridge code and the image code are concatenated into 1
information item without any separator.
Field Minimum
5
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: FINGER POSITION CODES and PALM POSITION CODES
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData (0…1)/ebts:TransactionBiometricImagesRequested (0…1)
Cardinality: 0…1
XML Level 2: ebts:BiometricImageDescription
Cardinality: 0…1000
XML Level 3: ansi-nist:FrictionRidgePositionCode
Cardinality: 0…1
XML Level 4: ebts:PrintPositionDescriptors (0…1)/ebts:FingerImageCodes (1…1)
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
119
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2028_6: Biometric Image Description - Pose Code (POS)
Description:
The POS (2.2028_6) information item specifies the subject pose code of the facial photo image to be retrieved.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: New-Emerging
XML Level 1: ebts:RecordTransactionData (0…1)/ebts:TransactionBiometricImagesRequested (0…1)
Cardinality: 0…1
XML Level 2: ebts:BiometricImageDescription
Cardinality: 0…1000
XML Level 3: ansi-nist:FaceImageSubjectPoseCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2028_7: Biometric Image Description - SMT Code (SMT)
Description:
SMT code for a scar, mark, or tattoo image. The SMT is required when an SMT image is to be retrieved.
Field Minimum
3
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: SMT DESCRIPTORS
Source: NGI-DOC-01078-10.0
Status: New-Emerging
XML Level 1: ebts:RecordTransactionData (0…1)/ebts:TransactionBiometricImagesRequested (0…1)
Cardinality: 0…1
XML Level 2: ebts:BiometricImageDescription
Cardinality: 0…1000
XML Level 3: nc:PhysicalFeatureCategoryCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
120
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2029: Biometric Set Identifier (BSI)
Description:
This numeric field will uniquely identify each biometric image set or photo, such as a facial photo, a fingerprint set, a palm print
set, or a supplemental print set.
Field Minimum
4
Field Maximum
24
Occurrence Minimum
0
Occurrence Maximum
1000
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: BIOMETRIC SET IDENTIFIER CODES
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:BiometricSetID
Cardinality: 0…1000
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2030: Print Position Descriptors (PPD)
Description:
This field will be present if and only if the finger position code "19" appears in Field 2.074. This field will consist of two
mandatory information items: The first is the probable integer finger position code 0-10 taken from finger position table. The
second information item is the code taken from Table P-1, found in Appendix P of NGI-DOC-01078-10.0, to indicate the portion
of the EJI or tip image that is a part of the transaction.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
10
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:TransactionPrintPositionDescriptors
Cardinality: 0…10
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
121
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2030_1: Print Position Descriptors - Friction Ridge Generalized Position (FGP)
Description:
This field is used in Record types dealing with friction ridges. It specifies which friction ridge biometric sample was
collected.
Use finger position code 0-10.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
0 <= FGP <= 10; integer
Code List: FRICTION RIDGE GENERALIZED POSITION
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:TransactionPrintPositionDescriptors
Cardinality: 0…10
XML Level 3: biom:FingerPositionCode
Cardinality: 1…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2030_2: Print Position Descriptors - Finger Image Code (FIC)
Description:
A code to indicate the portion of the EJI or tip image that is a part of the transaction. See Look Up Codes for valid entries.
Only EJI, TIP, FV1, FV2, FV3, FV4, PRX, DST, MED are allowed.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: PRINT POSITION DISCRIPTOR
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData
Cardinality: 0…1
XML Level 2: ebts:TransactionPrintPositionDescriptors
Cardinality: 0…10
XML Level 3: ebts:FingerImageCode
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
122
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2031: Biometric Image Available (BIA)
Description:
This field will indicate the existence of available biometric images (fingerprint, palmprint, supplemental print, facial photo, and
SMT photo) for an Identity in the NGI AFIS/FBI repository. Allowable BIA values are listed in the codelist table. The following
abbreviations are used in the table for each image type: FP – Fingerprint, PP – Palmprint, SP – Supplemental Print, PHF –
Photo Facial, and PSMT – Photo Scar, Mark, & Tattoo.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
6
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
0 <= BIA <= 31; integer
Code List: BIOMETRIC IMAGE AVAILABLE CODES
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordSubject
Cardinality: 0…1
XML Level 2: ebts:BiometricImageAvailableCode
Cardinality: 0…6
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2032: Audit Trail Record (ATR)
Description:
This repeating record contains the information associated with the dissemination of the owner’s images. The FNR and PPD
items are present in ATR to identify the image within the biometric set that was disseminated when the entire set was not
returned.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:TransactionAuditTrailRecordList
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
123
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2032_0: Audit Trail Record - Subfields: Repeating sets of information items (ATR_0)
Description:
Repeating subfield for Audit Trail Record.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
1
Occurrence Maximum
100
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.1
Status: Emerging
XML Level 1: ebts:TransactionAuditTrailRecordList
Cardinality: 0…1
XML Level 2: ebts:AuditTrailRecord
Cardinality: 1…100
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2032_1: Audit Trail Record - Originating Agency Identifier (ORI)
Description:
The origination field shall contain the ORI identifying the agency or organization submitting the transaction.
Field Minimum
9
Field Maximum
9
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:TransactionAuditTrailRecordList
Cardinality: 0…1
XML Level 2: ebts:AuditTrailRecord
Cardinality: 1…100
XML Level 3: ebts:RecordReceivingAgency/nc:IdentificationID
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
124
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2032_2: Audit Trail Record - Date of Dissemination (DAT)
Description:
Date the images were disseminated.
Field Minimum
8
Field Maximum
8
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
YYYYMMDD
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:TransactionAuditTrailRecordList
Cardinality: 0…1
XML Level 2: ebts:AuditTrailRecord
Cardinality: 1…100
XML Level 3: ebts:RecordDisseminationDate/nc:YearMonthDate
Cardinality: 1…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2032_3: Audit Trail Record - TOT of Dissemination (TOT)
Description:
TOT used to acquire the image set.
Field Minimum
3
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:TransactionAuditTrailRecordList
Cardinality: 0…1
XML Level 2: ebts:AuditTrailRecord
Cardinality: 1…100
XML Level 3: ebts:RecordTransactionCategoryCode
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
125
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2032_4: Audit Trail Record - Biometric Set Identifier Disseminated (BSI)
Description:
BSI of the image disseminated.
Field Minimum
4
Field Maximum
24
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:TransactionAuditTrailRecordList
Cardinality: 0…1
XML Level 2: ebts:AuditTrailRecord
Cardinality: 1…100
XML Level 3: ebts:BiometricSetID
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2032_5: Audit Trail Record - Image Type Disseminated (IMT)
Description:
Type of image disseminated.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: BIOMETRIC IMAGE
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:TransactionAuditTrailRecordList
Cardinality: 0…1
XML Level 2: ebts:AuditTrailRecord
Cardinality: 1…100
XML Level 3: ebts:BiometricImageCategoryCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
126
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2032_6: Audit Trail Record - Friction Ridge Position Requested (FNR)
Description:
The friction ridge number requested.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
Fingerprint and Palmprint
position codes
Code List: FINGER POSITION
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:TransactionAuditTrailRecordList
Cardinality: 0…1
XML Level 2: ebts:AuditTrailRecord
Cardinality: 1…100
XML Level 3: ansi-nist:FingerPositionCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2032_7: Audit Trail Record - Print Position Descriptors (PPD)
Description:
This PPD is an information item included within other fields. This item will be present if and only if the Friction ridge
Generalized Position code (FGP) or the Friction ridge Number(s) Requested (FNR) code (19) appears in the field. These
instances of PPD shall consist of a string containing two mandatory pieces of information. The first is the Probable Decimal
finger Position code (0-10) taken from the ANSI/NIST-ITL specification. The finger position must include a leading zero for
positions 0 through 9.
Both the probable decimal friction ridge code and the image code are concatenated into 1
information item without any separator.
Field Minimum
5
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:TransactionAuditTrailRecordList
Cardinality: 0…1
XML Level 2: ebts:AuditTrailRecord
Cardinality: 1…100
XML Level 3: ebts:PrintPositionDescriptors/ebts:FingerImageCode(1…1)
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
127
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2032_8: Audit Trail Record - Subject Pose (POS)
Description:
POS of facial image.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:TransactionAuditTrailRecordList
Cardinality: 0…1
XML Level 2: ebts:AuditTrailRecord
Cardinality: 1…100
XML Level 3: ansi-nist:FaceImageSubjectPoseCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2032_9: Audit Trail Record - NCIC SMT Code (SMT)
Description:
SMT code of SMT images.
Field Minimum
3
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: SMT DESCRIPTORS
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:TransactionAuditTrailRecordList
Cardinality: 0…1
XML Level 2: ebts:AuditTrailRecord
Cardinality: 1…100
XML Level 3: ansi-nist:PhysicalFeatureCategoryCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
128
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2033: Candidate Investigative List (CNL / CAN)
Description:
This field is added to the Investigative search response TOTs, providing a candidate list that supports a multi-biometric type
and multi-event repository. The legacy CAN field in the SRL is still supported as well for Fingerprint-only candidate lists. It is
possible for the CNL to contain multiple ranked lists concatenated together due to multiple biometric types being searched. For
friction ridge, NGI supports three biometric types for a latent investigative search: fingerprint, upper-palm, and lower-palm.
Therefore, an SRL can contain one, two, or three ranked lists where the number of candidates in each list is determined by the
NCR from the request. Therefore, the maximum number of candidates for an SRL is 3 x NCR. When multiple biometric types
are searched, a maximum of NIR images are returned for each type. Therefore, the maximum number of images for an SRL is
3 x NIR. Multiple candidates in traditional encoding will be separated by the {RS} separator.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData/ebts:TransactionResponseData
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2033_0: Candidate Investigative List - Subfields: Repeating sets of information items (CNL_0 / CAN_0)
Description:
Repeating subfield for Candidate Investigative List.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
3
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: Emerging
XML Level 1: ebts:RecordTransactionData/ebts:TransactionResponseData
Cardinality: 0…1
XML Level 2: ebts:TransactionCandidateList
Cardinality: 0…3
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
129
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2033_1: Candidate Investigative List - FBI Number/UCN (SI)
Description:
The FBI or UCN number assigned by FBI.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
integer
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData/ebts:TransactionResponseData
Cardinality: 0…1
XML Level 2: ebts:TransactionCandidateList
Cardinality: 0…3
XML Level 3: ebts:Candidate
Cardinality: 1…99
XML Level 4: j:PersonFBIIdentification/nc:IdentificationID
Cardinality: 1…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2033_2: Candidate Investigative List - Master Name (NAM)
Description:
Indicates the name of the subject.
Field Minimum
3
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData/ebts:TransactionResponseData
Cardinality: 0…1
XML Level 2: ebts:TransactionCandidateList
Cardinality: 0…3
XML Level 3: ebts:Candidate
Cardinality: 1…99
XML Level 4: ebts:PersonName (0…1), nc:PersonGivenName (0…1), nc:PersonMiddleName(0…1), nc:PersonSurName
(1…1)
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
130
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2033_3: Candidate Investigative List - Biometric Set Identifier (BSI)
Description:
This numeric field will uniquely identify a fingerprint set, palmprint set, or a supplemental print set.
Field Minimum
4
Field Maximum
24
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
integer
Code List: BIOMETRIC SET IDENTIFIER CODES
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData/ebts:TransactionResponseData
Cardinality: 0…1
XML Level 2: ebts:TransactionCandidateList
Cardinality: 0…3
XML Level 3: ebts:Candidate
Cardinality: 1…99
XML Level 4: ebts:BiometricSetID
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2033_4: Candidate Investigative List - Image Type (IMT)
Description:
This field identifies the type of image e.g., palmprints, toe prints included in an electronic submittal. The list of IMT values to be
used in an electronic latent submittal to identify the Type-7 or Type-13 records present [is listed in the look up codes below].
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: BIOMETRIC IMAGE
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData/ebts:TransactionResponseData
Cardinality: 0…1
XML Level 2: ebts:TransactionCandidateList
Cardinality: 0…3
XML Level 3: ebts:Candidate
Cardinality: 1…99
XML Level 4: ebts:RecordBiometricImageCategoryCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
131
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2033_5: Candidate Investigative List - Friction Ridge Generalized Position (FGP)
Description:
This field is used in Record types dealing with friction ridges. It specifies which friction ridge biometric sample was collected.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
1 <= FGP <= 19 or FGP =
33 or 36 or 40 <= FGP <=
50; integer
Code List: FRICTION RIDGE GENERALIZED POSITION
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData/ebts:TransactionResponseData
Cardinality: 0…1
XML Level 2: ebts:TransactionCandidateList
Cardinality: 0…3
XML Level 3: ebts:Candidate
Cardinality: 1…99
XML Level 4: ansi-nist:FrictionRidgePositionCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
132
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2033_6: Candidate Investigative List - Print Position Descriptors [Type-2, subfield to fields of Type Set]
(PPD)
Description:
This PPD is an information item included within other fields. This item will be present if and only if the Friction ridge
Generalized Position code (FGP) or the Friction ridge Number(s) Requested (FNR) code (19) appears in the field. These
instances of PPD shall consist of a string containing two mandatory pieces of information. The first is the Probable Decimal
finger Position code (0-10) taken from the ANSI/NIST-ITL specification. The finger position must include a leading zero for
positions 0 through 9.
Both the probable decimal friction ridge code and the image code are concatenated into 1
information item without any separator.
Field Minimum
5
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData/ebts:TransactionResponseData
Cardinality: 0…1
XML Level 2: ebts:TransactionCandidateList
Cardinality: 0…3
XML Level 3: ebts:Candidate
Cardinality: 1…99
XML Level 4: ebts:PrintPositionDescriptors(0…1)/ebts:FingerImageCode (1…1)
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
133
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2033_7: Candidate Investigative List - Match Score (MSC)
Description:
This field contains the match score from AFIS for each candidate listed in the 2.064 CAN field.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData/ebts:TransactionResponseData
Cardinality: 0…1
XML Level 2: ebts:TransactionCandidateList
Cardinality: 0…3
XML Level 3: ebts:Candidate
Cardinality: 1…99
XML Level 4: ebts:CandidateMatchScoreValue
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2033_8: Candidate Investigative List - Biometric Image Available (BIA)
Description:
This field will indicate the existence of available biometric images fingerprint, palmprint, supplemental print, facial photo, and
SMT photo for an Identity in the NGI AFIS/FBI repository. Allowable BIA values are shown in the table below. The following
abbreviations are used in the table for each image type: FP – Fingerprint, PP – Palmprint, SP – Supplemental Print, PHF –
Photo Facial, and PSMT – Photo Scar, Mark, & Tattoo.
integer
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
<= BIA <= 31
Code List: BIOMETRIC IMAGE AVAILABLE CODES
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData/ebts:TransactionResponseData
Cardinality: 0…1
XML Level 2: ebts:TransactionCandidateList
Cardinality: 0…3
XML Level 3: ebts:Candidate
Cardinality: 1…99
XML Level 4: ebts:BiometricImageAvailableCode
Cardinality: 0…6
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
134
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2033_9: Candidate Investigative List - Name of Designated Repository (NDR)
Description:
This field contains the numerical designation of the repository to be searched. Repository numbers are assigned by the CJIS
Division. Multiple entries in this field will indicate a desire to search more than one repository.
Field Minimum
1
Field Maximum
400
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: DESIGNATED REPOSITORY NAME
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData/ebts:TransactionResponseData
Cardinality: 0…1
XML Level 2: ebts:TransactionCandidateList
Cardinality: 0…3
XML Level 3: ebts:Candidate
Cardinality: 1…99
XML Level 4: ebts:RecordFBIRepositoryCodenc:IdentificationID
Cardinality: 0…100
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
135
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2033_10: Candidate Investigative List - Information Designation Character (IDC)
Description:
The value of the IDC shall be a sequentially assigned positive integer starting from zero and incremented by one up to a
maximum of 99. IDC references are stated in Type-1 Field 1.003 Transaction content (CNT) and shall be used to relate
information items in the CNT field of the Type-1 record to the other records in the transaction. Two or more records may share
a single IDC solely to identify and link together records that pertain to different representations of the same biometric trait.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
0 < IDC < 99; integer
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData/ebts:TransactionResponseData
Cardinality: 0…1
XML Level 2: ebts:TransactionCandidateList
Cardinality: 0…3
XML Level 3: ebts:Candidate
Cardinality: 1…99
XML Level 4: ansi-nist:ImageReferenceIdentification/nc:IdentificationID
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2033_11: Candidate Investigative List - Note Field (NOT)
Description:
NOT provides owning ORI information when no image is available for candidate
Field Minimum
1
Field Maximum
1000
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData/ebts:TransactionResponseData
Cardinality: 0…1
XML Level 2: ebts:TransactionCandidateList
Cardinality: 0…3
XML Level 3: ebts:Candidate
Cardinality: 1…99
XML Level 4: ebts:ORIPointOfContactText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
136
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2033_12: Candidate Investigative List - Subject Pose (POS)
Description:
A pose of a subject.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData/ebts:TransactionResponseData
Cardinality: 0…1
XML Level 2: ebts:TransactionCandidateList
Cardinality: 0…3
XML Level 3: ebts:Candidate
Cardinality: 1…99
XML Level 4: ansi-nist:FaceImageSubjectPoseCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.2033_13: Candidate Investigative List - SMT Code (SMT)
Description:
SMT provides SMT codes for SMT images.
Field Minimum
3
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: SMT DESCRIPTORS
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData/ebts:TransactionResponseData
Cardinality: 0…1
XML Level 2: ebts:TransactionCandidateList
Cardinality: 0…3
XML Level 3: ebts:Candidate
Cardinality: 1…99
XML Level 4: nc:PhysicalFeatureCategoryCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
137
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.2034: Unsolved Latent Retained (ULR)
Description:
This field is used in a Biometric Decision BDEC when the decision is a positive identification and the user requests that the
unsolved record is to be retained in the unsolved file. A value of “Y” indicates that the latent record should be retained in the
ULF. No value or a value of “N” indicates that the user does not want the unsolved record retained.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
ULR = Y or N
Code List: Y - Yes or N = No
Source: NGI-DOC-01078-10.0
Status: Emerging
XML Level 1: ebts:RecordTransactionData
Cardinality: 0..1
XML Level 2: ebts:TransactionUnsolvedLatentFileIndicator
Cardinality: 0..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8003: Biometric Subject Birth Date (SUBJ_BIRTHDATE)
Description:
The biometric subject's complete date of birth.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: Active
XML Level 1: dod-ebts:PersonBirthDate
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
138
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8003_0: Biometric Subject Birth Date - Subfields: Repeating sets of information items
(SUBJ_BIRTHDATE_0)
Description:
Repeating subfield for Biometric Subject Birth Date.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
5
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: Active
XML Level 1: dod-ebts:PersonBirthDate
Cardinality: 0…5
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8003_1: Biometric Subject Birth Date - Birth Date (DOB)
Description:
The 8 digit calendar date for the person's birth date.
Pad any portion of the date with zero's when unknown or not used.
For example, 00000000 when the field is mandatory, but the date is unknown. 20100000 when the year is known but month
and day are unknown or not used.
Field Minimum
Dependent on Encoding
Field Maximum
Dependent on Encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
YYYY-MM-DD
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod-ebts:PersonBirthDate
Cardinality: 0…5
XML Level 2: dod‐ebts:PersonBirthDate/nc:Date
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
139
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8003_2: Biometric Subject Birth Date - Date Validity (DATEVLD)
Description:
This field defines the validity of the date.
set to 'EST' for estimated.
When any part of the date value is padded with zero's, the date validity shall be
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
See Look Up Codes
Code List: VALIDITY CODES
Source: BSWG
Status: Active
XML Level 1: dod-ebts:PersonBirthDate
Cardinality: 0…5
XML Level 2: dod‐ebts:DateValidityCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8003_3: Biometric Subject Birth Date - Calendar Type (CALTYP)
Description:
The type of calendar the date is being specified in e.g. Gregorian and Islamic.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
See Look Up Codes
Code List: CALENDAR TYPE CODES
Source: BSWG
Status: Active
XML Level 1: dod-ebts:PersonBirthDate
Cardinality: 0…5
XML Level 2: dod‐ebts:CalendarCategoryCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
140
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8005: Biometric Subject Death Date (SUBJ_DEATHDATE)
Description:
The biometric subject's complete date of death.
Pad any portion of the date with zero's when unknown or not used. For
example, 00000000 when the field is mandatory, but the date is unknown. 20100000 when the year is known but month and
day are unknown or not used.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod-ebts:PersonDeathDate
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
DoD EBTS 4.0:
Yes
Yes
DoD EBTS 4.1:
Yes
2.8005_1: Biometric Subject Death Date - Death Date (DOD)
Description:
The 8 digit calendar date for the person's death date.
Dependent on Profile
Field Minimum
Dependent on Encoding
Field Maximum
Dependent on Encoding
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
YYYYMMDD
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod-ebts:PersonDeathDate
Cardinality: 0…1
XML Level 2: dod-ebts:PersonDeathDate/nc:date
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
141
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8005_2: Biometric Subject Death Date - Date Validity (DATEVLD)
Description:
This field defines the validity of the date.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
See Look Up Codes
Code List: VALIDITY CODES
Source: BSWG
Status: Active
XML Level 1: dod-ebts:PersonDeathDate
Cardinality: 0…1
XML Level 2: dod‐ebts:DateValidityCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8005_3: Biometric Subject Death Date - Calendar Type (CALTYP)
Description:
The type of calendar the date is being specified in e.g. Gregorian and Islamic.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
See Look Up Codes
Code List: CALENDAR TYPE CODES
Source: BSWG
Status: Active
XML Level 1: dod-ebts:PersonDeathDate
Cardinality: 0…1
XML Level 2: dod‐ebts:CalendarCategoryCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
142
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8007: Biometric Subject Citizenship (SUBJ_CTZ)
Description:
The country of which the biometric subject is a citizen. GENC alpha3 country codes are used.
for this field is the GENC three character alpha codelist (genc:CountryAlpha3CodeType).
The DoD EBTS v4.1 default
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
5
Character Types
A
Special Characters
N/A
Format
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod-ebts:PersonCitizenshipGENCText
Cardinality: 0…5
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8008: Biometric Subject Ethnic/Racial Characteristic (SUBJ_RAC)
Description:
The observed or reported ethnic/racial physical characteristic of the biometric subject.
Code Mappings from DoD EBTS 3.0
to/from FBI EBTS 9.3. DoD Field 2.8008 Biometric Subject Ethnic/Racial Characteristic map to FBI Field 2.025 Race: A <-> A
B <-> B I <-> I W <-> W U <-> U PI -> A HL -> W AR -> U AI -> A AS -> A NA -> I XX -> U
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
3
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: ETHNIC/RACIAL CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEthnicRacialCharacteristicCode
Cardinality: 0…3
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
143
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8013: Biometric Subject Blood Type (SUBJ_BLOOD)
Description:
The blood type of the biometric subject. It consists of Blood Type Value and Blood Type Validity.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonBloodGroup
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8013_0: Biometric Subject Blood Type - Subfields: Repeating sets of information items (SUBJ_BLOOD_0)
Description:
Repeating subfield for Biometric Subject Blood Type.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
3
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonBloodGroup
Cardinality: 0…3
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
144
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8013_1: Biometric Subject Blood Type - Blood Type Code (BLTCD)
Description:
The biometric subject's blood type/classification. Notes: Any of the four main types into which human blood is divided: A, B,
AB, and O. Blood types are based on the presence or absence of specific antigens on red blood cells. Also called blood group.
Field Minimum
4
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
See Look Up Codes
Code List: BLOOD TYPE CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonBloodGroup
Cardinality: 0…3
XML Level 2: j:PersonBloodTypeCode
Cardinality: 1…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8013_2: Biometric Subject Blood Type - Blood Type Validity (BLTVLD)
Description:
This field defines the validity of the biometric subject blood type.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
See Look Up Codes
Code List: VALIDITY CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonBloodGroup
Cardinality: 0…3
XML Level 2: dod‐ebts:PersonBloodTypeValidityCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
145
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8014: Biometric Subject Vital Status (SUBJ_VITAL_0)
Description:
The set of fields to indicate the condition of the biometric subject at the time of biometric sample collection.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonVitalStatus
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8014_0: Biometric Subject Vital Status - Subfields: Repeating sets of information items (SUBJ_VITAL)
Description:
Repeating subfield for Biometric Subject Vital Status.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
3
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonVitalStatus
Cardinality: 0…3
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
146
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8014_1: Biometric Subject Vital Status - Vital Status Validity (VSVLD)
Description:
This field defines the validity of the vital status of the biometric subject.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: VALIDITY CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonVitalStatus
Cardinality: 0…3
XML Level 2: dod‐ebts:PersonVitalStatusValidityCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8014_2: Biometric Subject Vital Status - Vital Status Code (VSCD)
Description:
The condition alive, dead of the biometric subject at the time of biometric sample collection. This field should be used only
when taking biometric sample of the subject and not for latent sample.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: SUBJECT STATUS CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonVitalStatus
Cardinality: 0…3
XML Level 2: dod‐ebts:PersonVitalStatusCode
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
147
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8016: Biometric Subject Marital Status (SUBJ_MARITAL)
Description:
Marital status of the biometric subject.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: MARITAL STATUS CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonMaritalStatusCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8019: Collected Identification (COL_IDENT)
Description:
Information about an identification issued by an agency. It is a set of fields that consists of Identification Type, Identification
Identifier, Issuance Organization, Issuance Office, Issuance Date, Expiration Date, and Comment.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:CollectedIdentification
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
148
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8019_0: Collected Identification - Subfields: Repeating sets of information items (COL_IDENT_0)
Description:
Repeating subfield for Collected Identification.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
100
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:CollectedIdentification
Cardinality: 0…100
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8019_1: Collected Identification - Collected Identification Identifier (CIID)
Description:
The identifying value for the issued identification. Examples include passport number, ssn, or drivers license number. This field
is free form text.
Field Minimum
1
Field Maximum
100
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:CollectedIdentification
Cardinality: 0…100
XML Level 2: nc:IdentificationCategoryDescriptionText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
149
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8019_2: Collected Identification - Collected Identification Type (CITYP)
Description:
The category of the collected identification, such as passport, employee id, and internment serial number.
Field Minimum
2
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
4
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: IDENTIFICATION CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:CollectedIdentification
Cardinality: 0…100
XML Level 2: dod-ebts:CollectedIdentificationCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8019_3: Collected Identification - Collected Identification Issuance Organization (CII)
Description:
The organization or system that issued the identification collected. This field is free form text and contains values such as “US
Government”, a country name, a state name, an agency name.
Field Minimum
1
Field Maximum
100
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:CollectedIdentification
Cardinality: 0…100
XML Level 2: dod-ebts:IdentificationIssuanceOrganizationText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
150
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8019_4: Collected Identification - Collected Identification Issuance Date (CIISSDT)
Description:
The date when the collected identification was issued effective.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
YYYYMMDD
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:CollectedIdentification
Cardinality: 0…100
XML Level 2: nc:IdentificationEffectiveDate/nc:Date
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8019_5: Collected Identification - Collected Identification Expiration Date (CIEXPDT)
Description:
The date the issued identification expires.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
YYYYMMDD
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:CollectedIdentification
Cardinality: 0…100
XML Level 2: nc:IdentificationExpirationDate/nc:Date
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
151
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8019_6: Collected Identification - Collected Identification Issuance Office (CIISSOFF)
Description:
A location or branch identifier for the office or system which issued the identification. This field is free form text. E.G. The
location where the biometric subject receives their card after verification.
Field Minimum
1
Field Maximum
100
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:CollectedIdentification
Cardinality: 0…100
XML Level 2: dod‐ebts:IdentificationIssuanceOfficeText
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8019_7: Collected Identification - Collected Identification Comment (CICOM)
Description:
The notes and comments concerning the issued identification collected.
Field Minimum
1
Field Maximum
250
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:CollectedIdentification
Cardinality: 0…100
XML Level 2: nc:CommentText
Cardinality: 0….1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
152
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8021: Biometric Subject Clearance (SUBJ_CLEAR)
Description:
The set of fields to indicate the biometric subject clearance level and validity.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonSecurityClearance
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8021_1: Biometric Subject Clearance - Clearance Code (CLRCD)
Description:
The clearance level that the biometric subject claims to have. This field is not authoritative.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: CLEARANCE CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonSecurityClearance
Cardinality: 0…1
XML Level 2: dod‐ebts:ClearanceCategoryCode
Cardinality: 1...1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
153
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8021_2: Biometric Subject Clearance - Clearance Validity (CLRVLD)
Description:
The state or quality of being valid of the clearance level that the biometric subject claims to hold.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: VALIDITY CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonSecurityClearance
Cardinality: 0…1
XML Level 2: dod‐ebts:ClearanceValidityCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8022: Biometric Subject Compartments (SUBJ_COMPART)
Description:
A freeform text to describe the compartments or section of information that might bear special community controls and might
require restricted handling that the biometric subject claims to be cleared for.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
50
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonCompartment
Cardinality: 0…50
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
154
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8022_1: Biometric Subject Compartments - Compartment Description (CMPDESC)
Description:
A freeform text to describe the compartments or section of information that might bear special community controls and might
require restricted handling that the biometric subject claims to be cleared for.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonCompartment
Cardinality: 0…50
XML Level 2: dod‐ebts:PersonCompartmentValueText
Cardinality: 1...1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8022_2: Biometric Subject Compartments - Compartments Validity (CMPVLD)
Description:
The state or quality of being valid for the compartments that the biometric subject claims to hold.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: VALIDITY CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonCompartment
Cardinality: 0…50
XML Level 2: dod‐ebts:PersonCompartmentValidityCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
155
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8023: Biometric Subject Comment (SUBJ_COM)
Description:
The comments or remarks on the biometric subject for which the biometric sample was collected.
Field Minimum
1
Field Maximum
120
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonCommentText
Cardinality: 0…1
XML Level 2: nc:TextType
Cardinality: 0..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8024: Biometric Subject Specialty - Biometric Subject US Person Indicator (US_IND)
Description:
The indicator of whether a biometric subject is a citizen of the United States, an alien lawfully admitted for permanent
residence in the United States, or a member of the U.S. Armed Forces.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: YES NO CODE
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:USPersonIndicator
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
156
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8025: Biometric Subject Derogatory Comment (DEROG_COM)
Description:
The derogatory notes and comments concerning a biometric subject.
Field Minimum
1
Field Maximum
120
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonDerogatoryCommentText
Cardinality: 0…1
XML Level 2: nc:TextType
Cardinality: 0..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8026: Biometric Subject Alternate Name (SUBJ_AKA)
Description:
An alternate name used by the biometric subject.
Can also be used to capture the subject's full maiden name.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonAlternateName
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
157
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8026_0: Biometric Subject Alternate Name - Subfields: Repeating sets of information items (SUBJ_AKA_0)
Description:
Repeating subfield for Biometric Subject Alternate Name.
Can also be used to capture the subject's full maiden name.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
10
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonAlternateName
Cardinality: 0…10
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8026_1: Biometric Subject Alternate Name - Name - One (NAM1)
Description:
The personal name of a person. It is typically the first name in western culture. Enter "UNKNOWN" if this information item is
required and not available at the time of collection.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonAlternateName
Cardinality: 0…10
XML Level 2: nc:PersonGivenName
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
158
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8026_2: Biometric Subject Alternate Name - Name - Two (NAM2)
Description:
The middle name of a person. It is placed between the first given name and the surname. Enter "UNKNOWN" if this
information item is required and not available at the time of collection.
Can be mapped to the Arabic Kunya name, the
person's first-born son is used as a substitute for the ism.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonAlternateName
Cardinality: 0…10
XML Level 2: nc:PersonMiddleName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8026_3: Biometric Subject Alternate Name - Name - Three (NAM3)
Description:
The last name, surname or the family name of the person. Enter "UNKNOWN" if this information item is required and not
available at the time of collection.
Can be mapped to the Arabic Nasab name, a patronymic or series of patronymics.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonAlternateName
Cardinality: 0…10
XML Level 2: nc:PersonSurName
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
159
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8026_4: Biometric Subject Alternate Name - Name - Four (NAM4)
Description:
A name of a person to represent the fourth name for a culture using four or five names e.g., a tribal or village name. It will be
given the ranking of fourth importance of naming in the culture from which the person is associated. Enter "UNKNOWN" if this
information item is required and not available at the time of collection.
Can be mapped to the Arabic Nisbah name,
describes a person's occupation, geographic home area, or descent tribe, family, etc..
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonAlternateName
Cardinality: 0…10
XML Level 2: ebts:PersonFourthImportanceName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8026_5: Biometric Subject Alternate Name - Name - Five (NAM5)
Description:
A name of a person to represent the fifth name for a culture using four or five names e.g., a tribal or village name. It will be
given the ranking of fifth importance of naming in the culture from which the person is associated. Enter "UNKNOWN" if this
information item is required and not available at the time of collection.
Can be mapped to the Arabic Laqab name, intended
as a description of the person. Also can be used for the honorific title.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonAlternateName
Cardinality: 0…10
XML Level 2: ebts:PersonFifthImportanceName
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
160
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8026_6: Biometric Subject Alternate Name - Name Validity (NAME_VLD)
Description:
This field defines the validity of the individual's name.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: VALIDITY CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonAlternateName
Cardinality: 0…10
XML Level 2: dod‐ebts:PersonNameValidityCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8026_7: Biometric Subject Alternate Name - Transliteration Code (TRANSLIT_CD)
Description:
An encoding to transcribe from one alphabet to another.
Field Minimum
4
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: TRANSLITERATION CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonAlternateName
Cardinality: 0…10
XML Level 2: dod‐ebts:TransliterationCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
161
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8026_8: Biometric Subject Alternate Name - Person Alternate Name Category Code (NAMCATCD)
Description:
Defines the type of name such as maiden name, nickname, alias.
Field Minimum
3
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: PERSON ALTERNATE NAME CATEGORY CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonAlternateName
Cardinality: 0…10
XML Level 2: dod‐ebts:PersonAlternateNameCategoryCode
Cardinality: 1…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8026_9: Biometric Subject Alternate Name - Comment (COM)
Description:
The optional Comment field appears in many record types and may be used to insert free text information. It is not reserved
exclusively for log-related information but has historically often been used for this purpose. It is limited to a maximum of 126
characters. This maximum size was established in order to maintain consistency across encodings. The maximum size differed
in the 2007 and 2008 versions of the standard.
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonAlternateName
Cardinality: 0…10
XML Level 2: nc:CommentText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
162
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8028: Employment (EMPLOY)
Description:
The information about the biometric subject's employment.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8028_0: Employment - Subfields: Repeating sets of information items (EMPLOY_0)
Description:
Repeating subfield for Employment.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
5
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: New-Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
163
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8028_1: Employment - Employer Name (EMPNAM)
Description:
The organization name of the employer, such as company name or corporate name.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
XML Level 2: nc:EntityName
Cardinality: 1…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8028_2: Employment - Employee Position Name (POSNAM)
Description:
A job title or position of an employee.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
XML Level 2: nc:EmployeePositionName
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
164
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8028_3: Employment - Address Line 1 (ADD1)
Description:
The street, including both number and name.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
XML Level 2: dod‐ebts:LocationAddress
Cardinality: 0…1
XML Level 3: nc:StreetFullText
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8028_4: Employment - Address Line 2 (ADD2)
Description:
Additional information about the street e.g. apt #.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
XML Level 2: dod‐ebts:LocationAddress
Cardinality: 0…1
XML Level 3: nc:StreetFullText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
165
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8028_5: Employment - City (CITY)
Description:
Name of the city.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
XML Level 2: dod‐ebts:LocationAddress
Cardinality: 0…1
XML Level 3: nc:LocationCityName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8028_6: Employment - State / Province (STATE)
Description:
The state, province or subdivision of a location.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
XML Level 2: dod‐ebts:LocationAddress
Cardinality: 0…1
XML Level 3: nc:LocationStateName
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
166
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8028_7: Employment - Country Code (CTRY)
Description:
The GENC alpha3 country code.
(genc:CountryAlpha3CodeType).
The DoD EBTS Default for this field is the GENC three character alpha codelist
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
XML Level 2: dod‐ebts:LocationAddress
Cardinality: 0…1
XML Level 3: nc:LocationCountryGENCCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8028_8: Employment - Postal Code (POSTAL)
Description:
Alphanumeric code assigned to groups of addresses by various national postal systems throughout the world.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
XML Level 2: dod‐ebts:LocationAddress
Cardinality: 0…1
XML Level 3: nc:LocationPostalCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
167
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8028_9: Employment - Village (VLG)
Description:
Small population unit, typically rural, held together by common economic and political ties.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
XML Level 2: dod‐ebts:LocationAddress
Cardinality: 0…1
XML Level 3: dod‐ebts:LocationVillageName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8028_10: Employment - Phone Number (PHNUM)
Description:
The full telephone number including international country code and area code. Space and hypen are allowed.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
XML Level 2: nc:TelephoneNumberFullID
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
168
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8028_11: Employment - Email Address (EMAIL)
Description:
Identifies an email box to which email messages are delivered. Application Profile might be more specific to what characters
are allowed to be entered for the email address.
Field Minimum
1
Field Maximum
254
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
XML Level 2: nc:ContactEmailID
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8028_12: Employment - Clearance Code (CLRCD)
Description:
The clearance level that the biometric subject claims to have. This field is not authoritative.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: CLEARANCE CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
XML Level 2: dod‐ebts:PersonSecurityClearance
Cardinality: 0…1
XML Level 3: dod‐ebts:PersonSecurityClearanceCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
169
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8028_13: Employment - Job Duties (DUTY)
Description:
A list of tasks performed at a job.
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
XML Level 2: dod‐ebts:EmployeeJobDutyText
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8028_14: Employment - Job Description (JOBDESC)
Description:
Freeform text to describe a job such as responsibilities, expected outcome, etc.
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
XML Level 2: nc:EmployeeOccupationText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
170
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8028_15: Employment - Supervisor Name (SUPV)
Description:
The name of the person who is in charge of a particular department or unit.
Field Minimum
1
Field Maximum
100
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
XML Level 2: nc:EmployeeSupervisor
Cardinality: 0…1
XML Level 3: nc:PersonName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8028_16: Employment - Start Date (STARTDATE)
Description:
The begin date.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
YYYYMMDD
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
XML Level 2: nc:StartDate/nc:Date
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
171
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8028_17: Employment - Start Date (ENDDATE)
Description:
The end date.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
YYYYMMDD
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
XML Level 2: nc:EndDate/nc:Date
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8028_18: Employment - Comment (COM)
Description:
The optional Comment field appears in many record types and may be used to insert free text information. It is not reserved
exclusively for log-related information but has historically often been used for this purpose. It is limited to a maximum of 126
characters. This maximum size was established in order to maintain consistency across encodings. The maximum size differed
in the 2007 and 2008 versions of the standard.
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEmploymentSummary
Cardinality: 0…5
XML Level 2: nc:CommentText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
172
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8029: Biometric Subject Contact Email (SUBJ_EMAIL)
Description:
The email address of the biometric subject.
This field was previously part of 2.8002 SUBJ_CNTCT in DoD EBTS 2.0.To
achieve better harmonization with other agencies as well to improve alignment to the NIEM XML, the subject's email address
has been split out into a new Field with ID 2.8029, as assigned in DoD EBTS 3.0.
Field Minimum
1
Field Maximum
254
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod-ebts:BiometricSubjectContactEmail
Cardinality: 0..10
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8031: Biometric Subject Current Residence (SUBJ_ADDR)
Description:
The address of the current residence of the biometric subject.
This field was previously 2.8001 SUBJ_ADDR in DoD EBTS
2.0. To achieve better harmonization with other agencies as well to improve alignment to the NIEM XML, the previous
normalized field has been restructured and a new Field ID 2.8031 was assigned in DoD EBTS 3.0. In addition, Village,
Neighborhood and Address Validity are also supported. This field has been updated the various parts of a street address with
GENC Alpha3 country codes.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonCurrentResidenceLocation
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
173
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8031_1: Biometric Subject Current Residence - Address Line 1 (ADD1)
Description:
The street, including both number and name.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonCurrentResidenceLocation
Cardinality: 0…1
XML Level 2: dod-ebts:AddressLine1
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8031_2: Biometric Subject Current Residence - Address Line 2 (ADD2)
Description:
Additional information about the street e.g. apt #.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonCurrentResidenceLocation
Cardinality: 0…1
XML Level 2: dod-ebts:AddressLine2
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
174
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8031_3: Biometric Subject Current Residence - City (CITY)
Description:
Name of the city.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonCurrentResidenceLocation
Cardinality: 0…1
XML Level 2: dod-ebts:LocationCityName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8031_4: Biometric Subject Current Residence - State / Province (STATE)
Description:
The state, province or subdivision of a location.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonCurrentResidenceLocation
Cardinality: 0…1
XML Level 2: dod-ebts:LocationStateName
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
175
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8031_5: Biometric Subject Current Residence - Country Code (CTRY)
Description:
The GENC alpha3 country code.
(genc:CountryAlpha3CodeType).
The DoD EBTS v4.1 Default for this field is the GENC three character alpha codelist
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonCurrentResidenceLocation
Cardinality: 0…1
XML Level 2: dod-ebts:LocationCountryGENCCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8031_6: Biometric Subject Current Residence - Postal Code (POSTAL)
Description:
Alphanumeric code assigned to groups of addresses by various national postal systems throughout the world.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonCurrentResidenceLocation
Cardinality: 0…1
XML Level 2: dod-ebts:LocationPostalCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
176
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8031_7: Biometric Subject Current Residence - Neighborhood / District (NEIG)
Description:
A geographically localized community within a larger city, town or suburb.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonCurrentResidenceLocation
Cardinality: 0…1
XML Level 2: dod-ebts:LocationNeighborhoodName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8031_8: Biometric Subject Current Residence - Village (VLG)
Description:
Small population unit, typically rural, held together by common economic and political ties.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonCurrentResidenceLocation
Cardinality: 0…1
XML Level 2: dod‐ebts:LocationVillageName
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
177
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8031_9: Biometric Subject Current Residence - Address Validity (ADDR_VLD)
Description:
This field defines the validity of the address information.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: VALIDITY CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonCurrentResidenceLocation
Cardinality: 0…1
XML Level 2: dod‐ebts:LocationAddressValidityCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8032: Biometric Subject Contact Telephone (SUBJ_PHONE)
Description:
The telephone number including extension (if available) that you might contact the biometric subject. Different categories of
telephone number (e.g. cell, home, work, etc.) are supported. This field was previously part of 2.8002 SUBJ_CNTCT in DoD
EBTS 2.0.To achieve better harmonization with other agencies as well to improve alignment to the NIEM XML, the subject's
telephone number(s) has been split out into a new Field with ID 2.8032 has been assigned in DoD EBTS 3.0. This field
continue to support the various categories of telephone that the subject can be contacted by. The telephone number and
extension are supported.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod-ebts:ContactTelephone
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
178
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8032_1: Biometric Subject Contact Telephone - Telephone Category Code (PH_TYP)
Description:
The method of contact for the individual e.g. phone, email.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: TELEPHONE CATEGORY CODES
Source: BSWG
Status: Active
XML Level 1: dod-ebts:ContactTelephone
Cardinality: 0…1
XML Level 2: dod-ebts:ContactTelephoneCategoryCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8032_2: Biometric Subject Contact Telephone - Phone Number (PHNUM)
Description:
The full telephone number including international country code and area code. Space and hypen are allowed.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod-ebts:ContactTelephone
Cardinality: 0…1
XML Level 2: nc:FullTelephoneNumberFulID/nc:TelephoneSuffixID
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
179
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8032_3: Biometric Subject Contact Telephone - Phone Extension (PHEXT)
Description:
The number for an additional telephone wired to the same telephone line as another.
Field Minimum
1
Field Maximum
20
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod-ebts:ContactTelephone
Cardinality: 0…1
XML Level 2: nc:FullTelephoneNumberFulID
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8032_4: Biometric Subject Contact Telephone - Telephone Number Description Text (TELDESC)
Description:
Description of the telephone number
Field Minimum
1
Field Maximum
20
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod-ebts:ContactTelephone
Cardinality: 0…1
XML Level 2: nc:TelephoneNumberDescriptionText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
180
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8033: Biometric Subject Birth Location (SUBJ_POB)
Description:
Information identifying where the biometric subject was born.
This field was previously 2.8004 POB in DoD EBTS 2.0.To
achieve better harmonization with other agencies as well to improve alignment to the NIEM XML, the previously normalized
field has been renamed and restructured. A new Field with ID 2.8033 has been assigned in DoD EBTS 3.0. For all location
type field, city, state/province, village and comment are supported. This field has been updated to contain the GENC 3166-1
Alpha3 country code.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod-ebts:PersonBirthLocation
Cardinality: 0…1
XML Level 2: nc:AddressFullText
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8033_1: Biometric Subject Birth Location - City (CITY)
Description:
Name of the city.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod-ebts:PersonBirthLocation
Cardinality: 0…1
XML Level 2: dod-ebts:LocationCityName
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
181
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8033_2: Biometric Subject Birth Location - State / Province (STATE)
Description:
The state, province or subdivision of a location.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod-ebts:PersonBirthLocation
Cardinality: 0…1
XML Level 2: dod-ebts:LocationStateName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8033_3: Biometric Subject Birth Location - Country Code (CTRY)
Description:
The GENC alpha3 country code.
(genc:CountryAlpha3CodeType).
The DoD EBTS v4.1 default for this field is the GENC three character alpha codelist
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod-ebts:PersonBirthLocation
Cardinality: 0…1
XML Level 2: dod-ebts:LocationCountryGENCCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
182
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8033_4: Biometric Subject Birth Location - Village (VLG)
Description:
Small population unit, typically rural, held together by common economic and political ties.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod-ebts:PersonBirthLocation
Cardinality: 0…1
XML Level 2: dod-ebts:LocationVillageName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8033_5: Biometric Subject Birth Location - Comment (COM)
Description:
The optional Comment field appears in many record types and may be used to insert free text information. It is not reserved
exclusively for log-related information but has historically often been used for this purpose. It is limited to a maximum of 126
characters. This maximum size was established in order to maintain consistency across encodings. The maximum size differed
in the 2007 and 2008 versions of the standard.
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod-ebts:PersonBirthLocation
Cardinality: 0…1
XML Level 2: nc:LocationDescriptionText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
183
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8034: Biometric Subject Death Location (SUBJ_POD)
Description:
Defines the biometric subject's place of death.
This field was previously 2.8006 POD in DoD EBTS 2.0.To achieve better
harmonization with other agencies as well to improve alignment to the NIEM XML, the previously normalized field has been
renamed and restructured. A new Field with ID 2.8034 has been assigned in DoD EBTS 3.0. For all location type field, city,
state/province, village and comment are supported. The GENC Alpha3 country code should now be used in place of the ISO
3166-1 Alpha3 country code.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonDeathLocation
Cardinality: 0…1
XML Level 2: nc:AddressFullText
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8034_1: Biometric Subject Death Location - City (CITY)
Description:
Name of the city.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonDeathLocation
Cardinality: 0…1
XML Level 2: dod-ebts:LocationCityName
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
184
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8034_2: Biometric Subject Death Location - State / Province (STATE)
Description:
The state, province or subdivision of a location.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonDeathLocation
Cardinality: 0…1
XML Level 2: dod-ebts:LocationStateName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8034_3: Biometric Subject Death Location - Country Code (CTRY)
Description:
The GENC alpha3 country code.
(genc:CountryAlpha3CodeType).
The DoD EBTS v4.1 default for this field is the GENC three character alpha codelist
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonDeathLocation
Cardinality: 0…1
XML Level 2: dod-ebts:LocationCountryGENCCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
185
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8034_4: Biometric Subject Death Location - Village (VLG)
Description:
Small population unit, typically rural, held together by common economic and political ties.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonDeathLocation
Cardinality: 0…1
XML Level 2: dod-ebts:LocationVillageName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8034_5: Biometric Subject Death Location - Biometric Subject Death Location (COM)
Description:
Comment
Field Minimum
0
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonDeathLocation
Cardinality: 0…1
XML Level 2: nc:LocationDescriptionText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
186
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8035: Biometric Subject Height Measurement (SUBJ_HEIGHT)
Description:
The set of data describing the height measurement including measurement range of a biometric subject.
This field was
previously 2.8009 HGT. Measurement Type has been removed from the set. A new field ID, 2.8035 SUBJ_HEIGHT has been
assigned by DoD EBTS 3.0. For measurement range, provide 2 subfields of the same measurement type where validity is set
to estimated.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonHeightMeasure
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8035_1: Biometric Subject Height Measurement - Height Value (HGT)
Description:
The value of the height measurement. Mininum height shall be 4'0" and maximum height shall be 7'11". The metric equivalent
is also allowed min = 1.22M, max = 2.41M. The following rules apply when measuring an individual's height: Height FTIN Three-character value, the first leftmost digit is used to show feet while the two rightmost digits are used to show inches
between 00 and 11. Height IN - Two-character value. Height M - Four-character value, the first leftmost digit is used.
Field Minimum
2
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonHeightMeasure
Cardinality: 0…1
XML Level 2: nc:MeasureIntegerValue
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
187
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8035_2: Biometric Subject Height Measurement - Length Unit (LENUNIT)
Description:
The units of measure associated with a given height measurement e.g., inches, centimeters, etc
Field Minimum
2
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: UNIT OF MEASURE CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonHeightMeasure
Cardinality: 0…1
XML Level 2: nc:MeasureUnitText
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8035_3: Biometric Subject Height Measurement - Measurement Validity (MEASVLD)
Description:
Captures the validity of the measurement.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: VALIDITY CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonHeightMeasure
Cardinality: 0…1
XML Level 2: dod‐ebts:PersonMeasureValidityCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
188
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8036: Biometric Subject Weight Measurement (SUBJ_WEIGHT)
Description:
The set of data describing the weight measurement including measurement range of a biometric subject.
This field was
previously 2.8010 WGT. Measurement Type has been removed from the set. A new field ID, 2.8036 SUBJ_WEIGHT has been
assigned by DoD EBTS 3.0. For measurement range, provide 2 subfields of the same measurement type where validity is set
to estimated.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod-ebts:PersonWeightMeasure
Cardinality: 0…1
Cardinality: 1…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8036_1: Biometric Subject Weight Measurement - Weight Value (WGT)
Description:
The value of the weight measurement. The minimum weight shall be 0 LB/KG. The maximum weight shall be 499 LB or 227
KG. Measurement shall be rounded up to the nearest pound or kilogram. Note: If the measurement is unknown but mandatory,
use "000" to represent unknown measurement.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod-ebts:PersonWeightMeasure
Cardinality: 0…1
XML Level 2: nc:MeasureIntegerValue
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
189
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8036_2: Biometric Subject Weight Measurement - Mass Unit (MASSUNIT)
Description:
The units of measure associated with a given weight measurement e.g., pounds.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: UNIT OF MEASURE CODES
Source: BSWG
Status: Active
XML Level 1: dod-ebts:PersonWeightMeasure
Cardinality: 0…1
XML Level 2: nc:measureunitText
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8036_3: Biometric Subject Weight Measurement - Measurement Validity (MEASVLD)
Description:
Captures the validity of the measurement.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: VALIDITY CODES
Source: BSWG
Status: Active
XML Level 1: dod-ebts:PersonWeightMeasure
Cardinality: 0…1
XML Level 2: od-ebts:PersonMeasureValidityCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
190
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8037: Biometric Subject Eye Color (SUBJ_EYE_0)
Description:
The color of the biometric subject's eyes.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEyeColor
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8037_0: Biometric Subject Eye Color - Subfields: Repeating sets of information items (SUBJ_EYE)
Description:
Repeating subfield for Biometric Subject Eye Color.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
2
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: New-Active
XML Level 1: dod‐ebts:PersonEyeColor
Cardinality: 0…2
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
191
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8037_1: Biometric Subject Eye Color - Eye Position (EPOS)
Description:
The position of the eye.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
EPOS = 0, 1, or 2,
Code List: EYE POSITION CODE
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEyeColor
Cardinality: 0…2
XML Level 2: biom:IrisEyePositionCode
Cardinality: 1…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8037_2: Biometric Subject Eye Color (ECOL)
Description:
This field shall specify the subject's eye color.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: ALPHA EYE COLOR CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonEyeColor
Cardinality: 0…2
XML Level 2: nc:PersonEyeColorText
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
192
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8038: Biometric Subject Group Membership (GRPMBR)
Description:
This set of fields identifies the names, gender, roles, address information and contact information of an individual who is
associated with the biometric subject.
This field was previously 2.8017 IASSOC in DoD EBTS 2.0.To achieve better
harmonization with other agencies as well to improve alignment to the NIEM XML, the previous normalized field has been
restructured and a new Field ID 2.8038 has been assigned in DoD EBTS 3.0. This field continues to support the associated
individual gender, role, name, address and contact phone. The associated individual birth date, occupation and comment have
been added to the set.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8038_0: Biometric Subject Group Membership - Subfields: Repeating sets of information items
(GRPMBR_0)
Description:
Repeating subfield for Biometric Subject Group Membership.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
100
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: New-Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
193
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8038_1: Biometric Subject Associated Individual - Associated Individual Gender (IASSOC_SEX)
Description:
This field is used to report the gender of the associated individual. The entry is a single character selected from the look-up
code list.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
see Look Up Codes
Code List: GENDER CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
XML Level 2: ebts:PersonSexCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8038_2: Biometric Subject Associated Individual - Associated Individual Role (IASSOC_ROLE)
Description:
The role of an individual who is affiliated with the biometric subject.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
see Look Up Codes
Code List: ASSOCIATED INDIVIDUAL ROLE CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
XML Level 2: dod-ebts:AssociatedIndividualRoleCode
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
194
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8038_3: Biometric Subject Associated Individual - Name - One (NAM1)
Description:
The personal name of a person. It is typically the first name in western culture. Enter "UNKNOWN" if this information item is
required and not available at the time of collection.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Emerging
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
XML Level 2: nc:PersonGivenName
Cardinality: 1…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8038_4: Biometric Subject Associated Individual - Name - Two (NAM2)
Description:
The middle name of a person. It is placed between the first given name and the surname. Enter "UNKNOWN" if this
information item is required and not available at the time of collection.
Can be mapped to the Arabic Kunya name, the
person's first-born son is used as a substitute for the ism.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
XML Level 2: nc:PersonMiddleName
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
195
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8038_5: Biometric Subject Associated Individual - Name - Three (NAM3)
Description:
The last name, surname or the family name of the person. Enter "UNKNOWN" if this information item is required and not
available at the time of collection.
Can be mapped to the Arabic Nasab name, a patronymic or series of patronymics.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
XML Level 2: nc:PersonSurName
Cardinality: 1…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8038_6: Biometric Subject Associated Individual - Name - Four (NAM4)
Description:
A name of a person to represent the fourth name for a culture using four or five names e.g., a tribal or village name. It will be
given the ranking of fourth importance of naming in the culture from which the person is associated. Enter "UNKNOWN" if this
information item is required and not available at the time of collection.
Can be mapped to the Arabic Nisbah name,
describes a person's occupation, geographic home area, or descent tribe, family, etc..
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
XML Level 2: ebts:PersonFourthImportanceName
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
196
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8038_7: Biometric Subject Associated Individual - Name - Five (NAM5)
Description:
A name of a person to represent the fifth name for a culture using four or five names e.g., a tribal or village name. It will be
given the ranking of fifth importance of naming in the culture from which the person is associated. Enter "UNKNOWN" if this
information item is required and not available at the time of collection.
Can be mapped to the Arabic Laqab name, intended
as a description of the person. Also can be used for the honorific title.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
XML Level 2: ebts:PersonFifthImportanceName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8038_8: Biometric Subject Associated Individual - Address Line 1 (ADD1)
Description:
The street, including both number and name.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
XML Level 2: nc:StreetFullText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
197
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8038_9: Biometric Subject Associated Individual - Address Line 2 (ADD2)
Description:
Additional information about the street e.g. apt #.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
XML Level 2: nc:StreetFullText
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8038_10: Biometric Subject Associated Individual - City (CITY)
Description:
Name of the city.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
XML Level 2: dod-ebts:LocationCityName
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
198
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8038_11: Biometric Subject Associated Individual - State / Province (STATE)
Description:
The state, province or subdivision of a location.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
XML Level 2: dod-ebts:LocationStateName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8038_12: Biometric Subject Associated Individual - Country Code (CTRY)
Description:
The GENC alpha3 country code.
(genc:CountryAlpha3CodeType).
The DoD EBTS v4.1 default for this field is the GENC three character alpha codelist
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
XML Level 2: dod-ebts:LocationCountryGENCCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
199
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8038_13: Biometric Subject Associated Individual - Postal Code (POSTAL)
Description:
Alphanumeric code assigned to groups of addresses by various national postal systems throughout the world.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
XML Level 2: dod-ebts:LocationPostalCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8038_14: Biometric Subject Associated Individual - Village (VLG)
Description:
Small population unit, typically rural, held together by common economic and political ties.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
XML Level 2: dod-ebts:LocationVillageName
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
200
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8038_15: Biometric Subject Associated Individual - Phone Number (PHNUM)
Description:
The full telephone number including international country code and area code. Space and hypen are allowed.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
XML Level 2: nc:TelephoneNumberFullID
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8038_16: Biometric Subject Associated Individual - Birth Date (DOB)
Description:
The 8 digit calendar date for the person's birth date.
Field Minimum
Dependent on Encoding
Field Maximum
Dependent on Encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
YYYYMMDD
Constraints
8 digit date
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
XML Level 2: dod‐ebts:PersonBirthDate/nc:Date
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
201
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8038_17: Biometric Subject Associated Individual - Occupation (OCP)
Description:
This free-text field contains the person‘s occupation. The OCP returned in a response is the same as the one submitted.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
XML Level 2: nc:EmployeeOccupationText
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8038_18: Biometric Subject Associated Individual - Comment (COM)
Description:
The optional Comment field appears in many record types and may be used to insert free text information. It is not reserved
exclusively for log-related information but has historically often been used for this purpose. It is limited to a maximum of 126
characters. This maximum size was established in order to maintain consistency across encodings. The maximum size differed
in the 2007 and 2008 versions of the standard.
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:AssociatedIndividual
Cardinality: 0…100
XML Level 2: nc:CommentText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
202
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8039: Biometric Subject Group Membership - Biometric Subject Group Membership Biometric Subject
Group Membership (GRPMBR)
Description:
Provide summary information on organizations the biometric subject is a member of.
This field was previously 2.8018
GRPMBR in DoD EBTS 2.0.To achieve better harmonization with other agencies as well to improve alignment to the NIEM
XML, the previous normalized field has been restructured and a new Field ID 2.8039 has been assigned in DoD EBTS 4.1.
This field continues to support the group name, type, member role, address, contact phone and comment.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:OrganizationMembership
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8039_0: Biometric Subject Group Membership - Subfields: Repeating sets of information items
(GRPMBR_0)
Description:
Repeating subfield for Biometric Subject Group Membership.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
100
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: New-Active
XML Level 1: dod‐ebts:OrganizationMembership
Cardinality: 0…100
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
203
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8039_1: Biometric Subject Group Membership - Group Name (GMNAM)
Description:
The name of the group that the biometric subject is associated with.
Field Minimum
1
Field Maximum
100
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:OrganizationMembership
Cardinality: 1…1
XML Level 2: nc:OrganizationName
Cardinality: 1…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8039_2: Biometric Subject Group Membership - Group Type (GMTYP)
Description:
The type of group that the biometric subject is associated with.
Field Minimum
3
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
see Look Up Codes
Code List: GROUP TYPE CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:OrganizationMembership
Cardinality: 1…1
XML Level 2: dod-ebts:OrganizationCategoryCode
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
204
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8039_3: Biometric Subject Group Membership - Group Member Role (GMRL)
Description:
The role within the associated group that the biometric subject is acting as.
Field Minimum
1
Field Maximum
100
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:OrganizationMembership
Cardinality: 0…1
XML Level 2: nc:OrganizationCategoryText
Cardinality: 0..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8039_4: Biometric Subject Group Membership - Address Line 1 (ADD1)
Description:
The street, including both number and name.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:OrganizationMembership
Cardinality: 0…1
XML Level 2: dod-ebts:AddressLine1
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
205
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8039_5: Biometric Subject Group Membership - Address Line 2 (ADD2)
Description:
Additional information about the street e.g. apt #.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:OrganizationMembership
Cardinality: 0…1
XML Level 2: dod-ebts:AddressLine2
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8039_6: Biometric Subject Group Membership - City (CITY)
Description:
Name of the city.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:OrganizationMembership
Cardinality: 0…1
XML Level 2: dod-ebts:LocationCityName
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
206
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8039_7: Biometric Subject Group Membership - State / Province (STATE)
Description:
The state, province or subdivision of a location.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:OrganizationMembership
Cardinality: 0…1
XML Level 2: dod-ebts:LocationStateName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8039_8: Biometric Subject Group Membership - Country Code (CTRY)
Description:
The GENC alpha3 country code.
(genc:CountryAlpha3CodeType).
The DoD EBTS v4.1 default for this field is the GENC three character alpha codelist
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:OrganizationMembership
Cardinality: 0…1
XML Level 2: dod-ebts:LocationCountryGENCCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
207
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8039_9: Biometric Subject Group Membership - Postal Code (POSTAL)
Description:
Alphanumeric code assigned to groups of addresses by various national postal systems throughout the world.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:OrganizationMembership
Cardinality: 0…1
XML Level 2: dod-ebts:LocationPostalCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8039_10: Biometric Subject Group Membership - Village (VLG)
Description:
Small population unit, typically rural, held together by common economic and political ties.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:OrganizationMembership
Cardinality: 0…1
XML Level 2: dod-ebts:LocationVillageName
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
208
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8039_11: Biometric Subject Group Membership - Phone Number (PHNUM)
Description:
The full telephone number including international country code and area code. Space and hypen are allowed.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:OrganizationMembership
Cardinality: 0…1
XML Level 2: nc:TelephoneNumberFullID
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8039_12: Biometric Subject Group Membership - Comment (COM)
Description:
The optional Comment field appears in many record types and may be used to insert free text information. It is not reserved
exclusively for log-related information but has historically often been used for this purpose. It is limited to a maximum of 126
characters. This maximum size was established in order to maintain consistency across encodings. The maximum size differed
in the 2007 and 2008 versions of the standard.
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:OrganizationMembership
Cardinality: 0…1
XML Level 2: nc:CommentText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
209
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8040: Biometric Subject Name (SUBJ_NAME)
Description:
The name of the biometric subject.
This field was previously 2.8000 SUBJ_NAM in DoD EBTS 2.0.To achieve better
harmonization with other agencies as well to improve alignment to the NIEM XML, the previous normalized field has been
restructured and a new Field ID 2.8030 has been assigned in DoD EBTS 3.0. This field continues to support Arabic names. For
aliases, see Field 2.8206 SUBJ_AKA for Biometric Subject Alternate Name.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8040_1: Biometric Subject Name - Name - One (NAM1)
Description:
The personal name of a person. It is typically the first name in western culture. Enter "UNKNOWN" if this information item is
required and not available at the time of collection.
Can be mapped to the Arabic Ism name, the main name of an Arab
person; his or her personal name e.g. "Kareem" or "Fatimah".
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonName
Cardinality: 0…1
XML Level 2: nc:PersonGivenName
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
210
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8040_2: Biometric Subject Name - Name - Two (NAM2)
Description:
The middle name of a person. It is placed between the first given name and the surname. Enter "UNKNOWN" if this
information item is required and not available at the time of collection.
Can be mapped to the Arabic Kunya name, the
person's first-born son is used as a substitute for the ism.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonName
Cardinality: 0…1
XML Level 2: nc:PersonMiddleName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8040_3: Biometric Subject Name - Name - Three (NAM3)
Description:
The last name, surname or the family name of the person. Enter "UNKNOWN" if this information item is required and not
available at the time of collection.
Can be mapped to the Arabic Nasab name, a patronymic or series of patronymics.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonName
Cardinality: 0…1
XML Level 2: nc:PersonSurName
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
211
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8040_4: Biometric Subject Name - Name - Four (NAM4)
Description:
A name of a person to represent the fourth name for a culture using four or five names e.g., a tribal or village name. It will be
given the ranking of fourth importance of naming in the culture from which the person is associated. Enter "UNKNOWN" if this
information item is required and not available at the time of collection.
Can be mapped to the Arabic Nisbah name,
describes a person's occupation, geographic home area, or descent tribe, family, etc..
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonName
Cardinality: 0…1
XML Level 2: ebts:PersonFouthImportanceName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8040_5: Biometric Subject Name - Name - Five (NAM5)
Description:
A name of a person to represent the fifth name for a culture using four or five names e.g., a tribal or village name. It will be
given the ranking of fifth importance of naming in the culture from which the person is associated. Enter "UNKNOWN" if this
information item is required and not available at the time of collection.
Can be mapped to the Arabic Laqab name, intended
as a description of the person. Also can be used for the honoric title.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonName
Cardinality: 0…1
XML Level 2: ebts:PersonFifthImportanceName
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
212
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8040_6: Biometric Subject Name - Name Validity (NAME_VLD)
Description:
This field defines the validity of the individual's name.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
see Look Up Codes
Code List: VALIDITY CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonName
Cardinality: 0…1
XML Level 2: dod‐ebts:PersonNameValidityCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8040_7: Biometric Subject Name - Transliteration Code (TRANSLIT_CD)
Description:
An encoding to transcribe from one alphabet to another.
Field Minimum
4
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
see Look Up Codes
Code List: TRANSLITERATION CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonName
Cardinality: 0…1
XML Level 2: dod‐ebts:TransliterationCode
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
213
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8102: Encounter Mission Type (ENCTR_MSN)
Description:
The kind of mission under which the biometric subject's data was collected.
Field Minimum
2
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
see Look Up Codes
Code List: MISSION CODES
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:EncounterMissionCategoryCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8103: Collection Reason (COL_RSN)
Description:
The purpose for which a biometric sample was obtained from the biometric subject.
Field Minimum
1
Field Maximum
300
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:CollectionReasonText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
214
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8106: Triggering Event (EVENT)
Description:
Something that happens at a given place and time that triggers subsequent collection encounter.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
Unlimited
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Referenced by DoD EBTS 2.0. Coordination with DoD ABIS required. Pending approval.
Status: Active
XML Level 1: dod-ebts:TriggeringEvent
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8106_0: Triggering Event - Subfields: Repeating sets of information items (EVENT_0)
Description:
Repeating subfield for Triggering Event.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
*
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: New-Active
XML Level 1: dod-ebts:TriggeringEvent
Cardinality: 0..*
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
215
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8106_1: Triggering Event - Triggering Event Identifier (EVENT_ID)
Description:
The unique identifier for the triggering event.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Referenced by DoD EBTS 2.0. Coordination with DoD ABIS required. Pending approval.
Status: Active
XML Level 1: dod-ebts:TriggeringEvent
Cardinality: 0..*
XML Level 2: nc:ActivityIdentification/nc:IdentificationID
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8106_2: Triggering Event - Address Line 1 (ADD1)
Description:
The street, including both number and name.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Referenced by DoD EBTS 2.0. Coordination with DoD ABIS required. Pending approval.
Status: Active
XML Level 1: dod-ebts:TriggeringEvent
Cardinality: 0..*
XML Level 2: dod-ebts:AddressLine1
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
216
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8106_3: Triggering Event - Address Line 2 (ADD2)
Description:
Additional information about the street e.g. apt #.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Referenced by DoD EBTS 2.0. Coordination with DoD ABIS required. Pending approval.
Status: Active
XML Level 1: dod-ebts:TriggeringEvent
Cardinality: 0..*
XML Level 2: dod-ebts:AddressLine2
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8106_4: Triggering Event - City (CITY)
Description:
Name of the city.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Referenced by DoD EBTS 2.0. Coordination with DoD ABIS required. Pending approval.
Status: Active
XML Level 1: dod-ebts:TriggeringEvent
Cardinality: 0..*
XML Level 2: dod-ebts:LocationCityName
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
217
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8106_5: Triggering Event - Country Code (CTRY)
Description:
The GENC alpha3 country code.
(genc:CountryAlpha3CodeType).
The DoD EBTS v4.1 default for this field is the GENC three character alpha codelist
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Referenced by DoD EBTS 2.0. Coordination with DoD ABIS required. Pending approval.
Status: Active
XML Level 1: dod-ebts:TriggeringEvent
Cardinality: 0..*
XML Level 2: dod-ebts:LocationCountryGENCCode
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8106_6: Triggering Event - Village (VLG)
Description:
Small population unit, typically rural, held together by common economic and political ties.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Referenced by DoD EBTS 2.0. Coordination with DoD ABIS required. Pending approval.
Status: Active
XML Level 1: dod-ebts:TriggeringEvent
Cardinality: 0..*
XML Level 2: dod-ebts:LocationVillageName
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
218
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8106_7: Triggering Event - Event Description (EVENT_DESC)
Description:
The textual description of an event that triggers subsequent collection encounter.
Field Minimum
1
Field Maximum
255
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Referenced by DoD EBTS 2.0. Coordination with DoD ABIS required. Pending approval.
Status: Active
XML Level 1: dod-ebts:TriggeringEvent
Cardinality: 0..*
XML Level 2: nc:ActivityName
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8106_8: Triggering Event - Comment (COM)
Description:
The optional Comment field appears in many record types and may be used to insert free text information. It is not reserved
exclusively for log-related information but has historically often been used for this purpose. It is limited to maximum of 126
characters. This maximum size was established in order to maintain consistency across encodings. The maximum size
differed in the 2007 and 2008 versions of the standard.
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Referenced by DoD EBTS 2.0. Coordination with DoD ABIS required. Pending approval.
Status: Active
XML Level 1: dod-ebts:TriggeringEvent
Cardinality: 0..*
XML Level 2: nc:ActivityDescriptionText
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
219
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8106_9: Triggering Event - Event Status (EVENT-STATUS)
Description:
The status of the related actions, events, or process steps.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: ANSI NIST ITL 2011: Update 13 Type 11 Field Addition and NIEM 3.0
Status: New-Emerging
XML Level 1: dod-ebts:TriggeringEvent
Cardinality: 0..*
XML Level 2: nc:StatusCommentText
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8106_10: Triggering Event - Event Date (EVENT_DATE)
Description:
The date for related actions, events, or process steps.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: ANSI NIST ITL 2011: Update 13 Type 11 Field Addition and NIEM 3.0
Status: New-Emerging
XML Level 1: dod-ebts:TriggeringEvent
Cardinality: 0..*
XML Level 2: nc:ActivityDate/nc:Date
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
220
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8107: Biometric Subject Privacy Act Indicator (PRI_ACT)
Description:
This field indicates whether U.S. citizens or U.S. persons who are being enrolled have signed a privacy act disclosure that
would allow their biometrics to be captured.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
See Look Up Codes
Code List: YES NO CODE
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:PersonPrivacyActIndicator
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8108: Employment - Encounter Comment (ENCTR_COM)
Description:
The comments or notes on the encounter mission in which the biometric sample was collected including any extenuating
circumstances of the encounter.
Field Minimum
1
Field Maximum
1000
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:EncounterCommentText
Cardinality: 0…1
XML Level 2: nc:CommentText
Cardinality: 0..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
221
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8109: Repository Candidate List (REPO_CAN)
Description:
This grouped field shall contain a candidate list. It is composed of four information items: Name of DesignatedRepository,
Candidate Identifier Type, Candidate Identifer and Candidate Name. These fields will be provided for each candidate in the list.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Referenced by DoD EBTS 2.0. Coordination with DoD ABIS required. Pending approval.
Status: Active
XML Level 1: dod-ebts:RepositoryCandidateList
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8109_0: Repository Candidate List - Subfields: Repeating sets of information items (REPO_CAN_0)
Description:
Repeating subfield for Repository Candidate List.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
*
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: Active
XML Level 1: dod-ebts:RepositoryCandidateList
Cardinality: 0…*
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
222
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8109_1: Repository Candidate List - Name of Designated Repository (NDR)
Description:
This field contains the numerical designation of the repository to be searched. Repository numbers are assigned by the CJIS
Division. Multiple entries in this field will indicate a desire to search more than one repository.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: DESIGNATED REPOSITORY NAME
Source: Referenced by DoD EBTS 2.0.
Status: Active
XML Level 1: dod-ebts:RepositoryCandidateList
Cardinality: 0…*
XML Level 2: nc:RepositoryID
Cardinality: 0..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8109_2: Repository Candidate List - Repository Candidate Identifier Category Code (CAN_ID_CAT_CD)
Description:
The category of the candidate identification such as DoD Number, FBI Number, etc.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: IDENTIFIER TYPE CODES
Source: Referenced by DoD EBTS 2.0.
Status: Active
XML Level 1: dod-ebts:RepositoryCandidateList
Cardinality: 0…*
XML Level 2: dod-ebts:RepositoryCandidateCode
Cardinality: 0..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
223
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8109_3: Repository Candidate List - Repository Candidate Identifier (CAN_ID)
Description:
The identifying value for the candidate's identification.
Field Minimum
1
Field Maximum
100
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Referenced by DoD EBTS 2.0.
Status: Active
XML Level 1: dod-ebts:RepositoryCandidateList
Cardinality: 0…*
XML Level 2: dod-ebts:CandidateID
Cardinality: 0..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8109_4: Repository Candidate List - Repository Candidate Name (CAN_NAM)
Description:
The name of a person included in a Repository Candidate List.
For DoD Candidate List/Candidate Name, use the
"UNKNOWN, XX" when the name of the subject is unknown and is mandatory.
Field Minimum
1
Field Maximum
100
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: Referenced by DoD EBTS 2.0.
Status: Active
XML Level 1: dod-ebts:RepositoryCandidateList
Cardinality: 0…*
XML Level 2: nc:PersonFullName
Cardinality: 0..1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
224
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8110: Iris Image Omitted Reason (IOMITTED)
Description:
Reason why the iris image aka Type-17 record is not present in the associated file.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
N/A
Format
N/A
Constraints
N/A
Code List: IRIS IMAGE OMITTED REASON CODES
Source: BSWG
Status: Active
XML Level 1: dod-ebts:IrisImageOmittedReasoncode
Cardinality: 0…1
XML Level 2: dod-ebts:IrisImageOmittedReason
Cardinality: 0..1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8114: Collection Location (COLL_BLO)
Description:
The field is used to capture the geographic location where the biometric sample was collected for the entire submission. This
field can also be used to capture the geographic location where the Type-2 data was collected if it is captured at a different
location.
This field was previously 2.301 BLO in DoD EBTS 1.2 and 2.8100 COLL_BLO with extended size in DoD EBTS
2.0. With ANSI/NIST ITL 1-2011, many logical records have included a field X.998 GEO that captures the geographic location
where the data was collected. A Type-2 field is still needed for response transactions.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:CollectionLocationDetail
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
225
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8114_0: Collection Location - Subfields: Repeating sets of information items (COLL_BLO_0)
Description:
Repeating subfield for Collection Location.
Field Minimum
N/A
Field Maximum
N/A
Occurrence Minimum
0
Occurrence Maximum
*
Character Types
N/A
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: EBTS v4.1
Status: Active
XML Level 1: dod‐ebts:CollectionLocationDetail
Cardinality: 0…*
DoD EBTS 1.2:
No
DoD EBTS 3.0:
No
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8114_1: Collection Location - Universal Time Entry (UTE)
Description:
The coordinated universal time (UTC) where the biometric sample was collected. This time is independent of the actual time
zone where the time and date is recorded. The date is YYYYMMDDhhmmssZ, where the Z is indicates the zone description of
0 hours.
If sample collection time is unknown, set it to "00000000000000Z."
Field Minimum
15
Field Maximum
15
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
N/A
Format
N/A
Constraints
N/A
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:CollectionLocationDetail
Cardinality: 0…*
XML Level 2: nc:CaptureUTCDateTime/nc:DateTime
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
226
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8114_2: Collection Location - Latitude Degree Value (LTD)
Description:
The second information item is latitude degree value (LTD). This is a value that specifies the degree of latitude. The value shall
be between -90 (inclusive) and +90 (inclusive). The degrees may be expressed as an integer (without a decimal) or a real
number including decimals. If decimals are present, then minutes and seconds shall be empty. Examples: Buenos Aires,
Argentina: -34 (with minutes LTM = 36) NIST, Gaithersburg, Maryland: 39.137627 (no LTM or LTS)
Field Minimum
1
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
N/A
Format
N/A
Constraints
=90 <= LTD <= 90
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:CollectionLocationDetail
Cardinality: 0…*
XML Level 2: nc:LatitudeDegreeValue
Cardinality: 1…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8114_3: Collection Location - Latitude Minute Value (LTM)
Description:
This information item is latitude minute value (LTM). This is a value that specifies a minute of a degree. The value shall be
between 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall be empty. Thus, the allowed special character is a
period. The minute value can be empty, even if the degree value is an integer. LTM and LGM are co-conditional, so they shall
both be present if either is present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
N/A
Format
N/A
Constraints
0 <= LTM < 60
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:CollectionLocationDetail
Cardinality: 0…*
XML Level 2: nc:LatitudeMinuteValue
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
227
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8114_4: Collection Location - Latitude Second Value (LTS)
Description:
The fourth information item is the latitude second value (LTS). This is a value that specifies a second of a minute. The integer
shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
0 <= LTS < 60
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:CollectionLocationDetail
Cardinality: 0…*
XML Level 2: nc:LatitudeSecondValue
Cardinality: 0…1
XML Level 3: nc:GeographicCoordinateLongitude
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8114_5: Collection Location - Longitude Degree Value (LGD)
Description:
The fifth information item is the longitude degree value (LGD). It is a value that specifies the degree of a longitude. The value
shall be between -180 (inclusive) and +180 (inclusive). If LTD is present, then LGD shall be present. The degrees may be
expressed as whole numbers (without a decimal) or real numbers including decimals. If decimals are present, then minutes
and seconds are empty. Examples: Buenos Aires, Argentina: -58 (with minutes LGM = 22), NIST, Gaithersburg, Maryland: 77.216032 (no LGM or LGS)
Field Minimum
1
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
N/A
Format
N/A
Constraints
=-80 <= LGD <= 180
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:CollectionLocationDetail
Cardinality: 0…*
XML Level 2: nc:LongitudeDegreeValue
Cardinality: 1…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
228
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8114_6: Collection Location - Longitude Minute Value (LGM)
Description:
The sixth information item is the longitude minute value (LGM). It is a value that specifies a minute of a degree. The value shall
be from 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall not appear. The minute value is empty, even if the
degree value is an integer. If LTM is present, then LGM shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
N/A
Format
N/A
Constraints
0 <=LGS<60
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:CollectionLocationDetail
Cardinality: 0…*
XML Level 2: nc:LongitudeMinuteValue
Cardinality: 0…1
DoD EBTS 1.2:
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
DoD EBTS 4.1:
Yes
2.8114_7: Collection Location - Longitude Second Value (LGS)
Description:
The seventh information item is the longitude second value (LGS). This is a value that specifies a second of a minute. The
integer shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer. If LTS is
present, then LGS shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
N/A
Format
N/A
Constraints
0 <=LGM<60
Source: BSWG
Status: Active
XML Level 1: dod‐ebts:CollectionLocationDetail
Cardinality: 0…*
XML Level 2: nc:LongitudeSecondValue
Cardinality: 0…1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
229
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
Type-2: User-Defined Descriptive Text
2.8114_8: Collection Location - Elevation (ELE)
Description:
The eighth information item is elevation (ELE). It is expressed in meters. It is a numeric value. It is between -422 meters (Dead
Sea) and 8848 meters (Mount Everest). Allowed special characters are the negative sign and the period.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
N/A
Format
N/A
Constraints
-422.000
Constraints
Date concatenated with text
Source: ANSI/NIST ITL 1-2011 Update: 2015 (Type-9)
Status: Active
XML Parent: itl:PackageMinutiaeRecord
NIEM Element: biom:MinutiaeUniversalLatentWorkstationAnnotationText
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
9.902: Annotated Information (ANN)
Description:
This optional field is used to store annotation, logging, or processing information associated with one or more processing
algorithms, processes, or latent workstations (other than the FBI-developed ULW). If present, this text shall consist of one or
more subfields comprised of a set of information items. Four mandatory items comprise a subfield.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015 (Type-9)
Status: Active
XML Parent: itl:PackageMinutiaeRecord
NIEM Element: biom:ProcessAnnotation
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
474
Type-9 Minutiae Data Record (Common)
9.902_0: Annotated Information - Subfields: Repeating sets of information items (ANN_0)
Description:
This optional field is used to store annotation, logging, or processing information associated with one or more processing
algorithms, processes, or latent workstations (other than the FBI-developed ULW). If present, this text shall consist of one or
more subfields comprised of a set of information items. Four mandatory items comprise a subfield.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
*
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015 (Type-9)
Status: Active
XML Parent: itl:PackageMinutiaeRecord
NIEM Element: biom:ProcessAnnotation
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
9.902_1: Annotated Information - Greenwich Mean Time (GMT)
Description:
This information item is the Greenwich Mean Time (GMT) when the processing occured. The data is formatted as
YYYYMMDDhhmmssZ, where the Z is indicates the zone description of 0 hours. Time (GMT) units. This time is independent of
the actual time zone where the time and date is recorded.
Field Minimum
15
Field Maximum
15
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
YYYYMMDDHHMMSSZ for Traditional Encoding
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015 (Type-9)
Status: Active
XML Parent: itl:PackageMinutiaeRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessUTCDate/nc:ZuluDateTime
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
475
Type-9 Minutiae Data Record (Common)
9.902_2: Annotated Information - Processing Algorithm Name / Version (NAV)
Description:
This information item shall contain text identifying the name and version of the processing algorithm, application, procedure, or
workstation.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015 (Type-9)
Status: Active
XML Parent: itl:PackageMinutiaeRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessName
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
9.902_3: Annotated Information - Algorithm Owner (OWN)
Description:
This information item shall contain an unformatted text string of up to 64 characters with the contact information for the
organization that owns the processing algorithm or latent workstation. Where there is no 'algorithm owner,' enter N/A.
Field Minimum
1
Field Maximum
64
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015 (Type-9)
Status: Active
XML Parent: itl:PackageMinutiaeRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessOwnerText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
476
Type-9 Minutiae Data Record (Common)
9.902_4: Annotated Information - Process Description (PRO)
Description:
This information item field shall contain text describing a process or procedure applied to the sample in this Type-9 record.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015 (Type-9)
Status: Active
XML Parent: itl:PackageMinutiaeRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessDescriptionText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
9.903: Device Unique Identifier (DUI)
Description:
The DUI shall contain a string uniquely identifying the device or source of the data. This field shall be one of the following: a
Host PC MAC address (identified by the first character “M”), a Host PC processor ID (identified by the first character “P”).
Field Minimum
13
Field Maximum
16
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
Any
Format
n/a
Constraints
First character = M or P
Source: ANSI/NIST ITL 1-2011 Update: 2015 (Type-9)
Status: Active
XML Parent: itl:PackageMinutiaeRecord/biom:CaptureDevice
NIEM Element: biom:DeviceID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
477
Type-9 Minutiae Data Record (Common)
9.904: Make/Model/Serial Number (MMS)
Description:
The MMS contains the make, model and serial number for the capture device. It shall consist of three information items. Each
information item shall be 1 to 50 characters. Unknown information may be indicated with the value "0." Any or all information
items may indicate that information is unknown with the value “0”.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015 (Type-9)
Status: Active
XML Parent: biom:BiometricCapture
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
9.904_1: Make/Model/Serial Number - Make (MAK)
Description:
The name of the manufacturer for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
"0" = Unknown
Source: ANSI/NIST ITL 1-2011 Update: 2015 (Type-9)
Status: Active
XML Parent: itl:PackageMinutiaeRecord/biom:CaptureDevice
NIEM Element: biom:DeviceMakeText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
478
Type-9 Minutiae Data Record (Common)
9.904_2: Make/Model/Serial Number - Model (MOD)
Description:
The model number for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
"0" = Unknown
Source: ANSI/NIST ITL 1-2011 Update: 2015 (Type-9)
Status: Active
XML Parent: itl:PackageMinutiaeRecord/biom:CaptureDevice
NIEM Element: biom:DeviceModelText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
9.904_3: Make/Model/Serial Number - Serial Number (SER)
Description:
The serial number for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
"0" = Unknown
Source: ANSI/NIST ITL 1-2011 Update: 2015 (Type-9)
Status: Active
XML Parent: itl:PackageMinutiaeRecord/biom:CaptureDevice
NIEM Element: biom:DeviceSerialNumberText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
479
Type-10: Photographic Body Part Imagery (including Face and
10.001: Record Header
Description:
The record header appears as the first field (xx.001) in each Record Type. It contains information particular to the encoding
format chosen, in order to enable proper reading of the record. In Traditional encoding, this field contains the record length in
bytes (including all information separators). In NIEM-conformant XML encoding, this field contains the RecordCategoryCode,
which is the numeric representation of the Record Type.
Field Minimum
T = 4; X = 1
Field Maximum
T = 8; X = 2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.002: Information Designation Character (IDC)
Description:
Each of the records present in a transaction, with the exception of the Type-1 record, shall include a field (xx.002) containing
the information designation character / IDC. The value of the IDC shall be a sequentially assigned positive integer starting from
zero and incremented by one up to a maximum of 99. IDC references are stated in Type-1 Field 1.003 Transaction content /
CNT and shall be used to relate information items. Two or more records may share a single IDC solely to identify and link
together records that pertain to different representations of the same biometric trait.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 <= IDC <= 99; integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
480
Type-10: Photographic Body Part Imagery (including Face and
10.003: Image Type (IMT)
Description:
Indicate the type of image contained in the Type-10 record.
Patterned injuries are not treated as a separate image type.
Note that patterned injuries may be on any part of the body.
Field Minimum
4
Field Maximum
11
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AS
Special Characters
Blank, Hyphen
Format
n/a
Constraints
see Look Up Codes
Code List: TYPE 10 IMAGE TYPES
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:ImageCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.004: Source Agency (SRC)
Description:
This is the identifier of the agency that actually created the record and supplied the information contained in it.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/
biom:ImageCaptureDetail/biom:CaptureOrganization
NIEM Element: nc:OrganizationIdentification/nc:IdentificationID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
481
Type-10: Photographic Body Part Imagery (including Face and
10.005: Photo Capture Date (PHD)
Description:
This mandatory field shall contain the date that the image contained in the record was captured.
Field Minimum
Dependent on encoding
Field Maximum
Dependent on encoding
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
YYYYMMDD
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/ biom:ImageCaptureDetail
NIEM Element: biom:CaptureDate/nc:Date
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.006: Horizontal Line Length (HLL)
Description:
HLL defines the number of pixels contained on a single horizontal line of the image. The maximum horizontal size is limited to
65,535 pixels in Record Types-4 and 8, and to 99,999 for other record types. The minimum value is 10 pixels. The total image
size (HLL times VLL) must be able to be accommodated in Field xx.001 for Traditional encoding.
Field Minimum
2
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
10 <= HLL <= 99999;
positive integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage
NIEM Element: biom:HorizontalLineLengthPixelQuantity
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
482
Type-10: Photographic Body Part Imagery (including Face and
10.007: Vertical Line Length (VLL)
Description:
VLL defines the number of horizontal lines contained in the image. The maximum vertical size is limited to 65,535 pixels in
Record Types-4 and 8, and to 99,999 for other record types. The minimum value is 10 pixels.
Field Minimum
2
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
10 <= HLL <= 99999;
positive integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage
NIEM Element: biom:ImageVerticalLineLengthPixelQuantity
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.008: Scale Units (SLC)
Description:
The image sampling frequency (pixel density). A value of “1” shall indicate pixels per inch. A value of “2” shall indicate pixels
per centimeter. A value of “0” in this field indicates that no scale is provided, and the quotient of THPS/TVPS shall provide the
pixel aspect ratio.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 <= SLC <= 2; integer
Code List: SCALE UNIT CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:ImageScaleUnitsCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
483
Type-10: Photographic Body Part Imagery (including Face and
10.009: Transmitted Horizontal Pixel Scale (THPS)
Description:
This is the integer pixel density used in the horizontal direction of the image if SLC has a value of “1” or “2”. If SLC has a value
of “0”, this information item shall contain the horizontal component of the pixel aspect ratio, up to 5 integer digits. For example,
if the SLC value = 1, then the value of THPS could be ‘1000’ for a 1000 ppi sensor.
When using certain formats, such as
PNG, conversion from ppm (or other scales) may result in a decimal value. Since these fields require integer values, rounding
should be used.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage
NIEM Element: biom:ImageHorizontalPixelDensityValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.010: Transmitted Vertical Pixel Scale (TVPS)
Description:
This is the integer pixel density used in the vertical direction of the image if SLC has a value of “1” or “2”. If SLC has a value of
“0”, this information item shall contain the vertical component of the pixel aspect ratio, up to 5 integer digits. If SLC is 1 or 2,
then TVPS shall equal THPS.
When using certain formats, such as PNG, conversion from ppm (or other scales) may result
in a decimal value. Since these fields require integer values, rounding up at .5 should be used.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage
NIEM Element: biom:ImageVerticalPixelDensityValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
484
Type-10: Photographic Body Part Imagery (including Face and
10.011: Compression Algorithm (CGA)
Description:
This is a mandatory field. It shall specify the algorithm used to compress the transmitted color or grayscale images. For those
images that are to be compressed, the method for the compression of facial and SMT images is specified by the baseline
mode of the JPEG, JPEG 2000, or PNG algorithms. When Record Type-10 contains a facial image, the conditions described in
ANSI NIST 2011: Update 2011 Annex E: E.6.1 Compression algorithm apply. For non-facial images contained in Record Type10, Field 10.011: Compression algorithm / CGA may be set to any value in the COMPRESSION Code List except WSQ20.
WSQ is not supported. The image shall be represented as an array of n rows by m columns by at least 8-bit pixels. Each pixel
in a monochrome image shall be represented by eight or more bits. Color images shall be represented as a series of
sequential samples of a red, green, and blue intensity for each pixel.The image shall be organized in row-major order, with the
lowest address corresponding to the upper left corner of the image.
Field Minimum
3
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
Code List: COMPRESSION CODES
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:ImageCompressionAlgorithmCodeType
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
485
Type-10: Photographic Body Part Imagery (including Face and
10.012: Color Space (CSP)
Description:
Scanned images shall consist of nominal 24 to 48-bit RGB pixels. Color image data may be transmitted in either compressed
or uncompressed form in certain record types. The transmission of uncompressed color images shall consist of RGB pixels,
each component of which shall be quantized to at least 256 levels (8 bits). Grayscale image data may be transmitted in either
compressed or uncompressed form. The transmission of uncompressed grayscale images shall consist of pixels, each of
which shall normally be quantized to eight bits (256 gray levels) and held in a single unsigned byte. Black and white (binary
representation) image data may be transmitted in either compressed or uncompressed form. The uncompressed binary
images shall consist of pixels, each of which shall be quantized to one of two levels (binary representation). A value of zero
shall be used to represent a white pixel and a value of one shall be used to represent a black pixel. See ANSI/NIST ITL 12011, section on Color, black-and-white, and grayscale image requirements for detail. To ensure that color images exchanged
between differing systems can be correctly displayed or printed, images should be converted to the device-independent color
space, sRGB, beforecompression or transmission to another system.
Field Minimum
3
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
see Look Up Codes
Code List: COLOR SPACE CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage
NIEM Element: biom:ImageColorSpaceCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.013: Subject Acquisition Profile (SAP)
Description:
To provide a general description of the criteria under which the facial image was captured. Typically, the higher the value, the
stronger the acquisition requirements become. Therefore, in the text below, the SAP value will also be denoted as a
“level”.
The Subject Acquisition Profile (SAP) is a mandatory ASCII text field when [Type-10 Image Type field 10.003]
contains "FACE”.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
see Look Up Codes
Code List: SUBJECT ACQUISITION PROFILES - FACE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImageAcquisitionProfileCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
486
Type-10: Photographic Body Part Imagery (including Face and
10.014: Face Image Bounding Box Coordinates in Full Image (FIP)
Description:
If the face image (IMT='FACE') contains more than one face, or is not cropped to a “head only” or “head and shoulders”
composition, this optional field contains offsets to the location of the bounding box of the face of the subject within a larger
image. This field is only appropriate for images that do not comply with SAP Levels 30, 32, 40, 42, 50, 51 or 52, because those
images shall be cropped to a “head only” or “head and shoulders” composition. If the image contains more than one face, the
bounding box indicates the face of interest; all associated Type-10 fields are limited to the face defined by the bounding box in
the larger image.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImageBoundingSquare
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.014_1: Face Image Bounding Box Coordinates in Full Image - Left Horizontal Coordinate Value (LHC)
Description:
It is the horizontal offset in pixels to the left edge of the bounding box relative to the origin positioned in the upper left corner of
the image.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
0 < LHC < HLL
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/ biom:FaceImageBoundingSquare
NIEM Element: biom:SegmentRightHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
487
Type-10: Photographic Body Part Imagery (including Face and
10.014_2: Face Image Bounding Box Coordinates in Full Image - Right Horizontal Coordinate Value (RHC)
Description:
It is the horizontal offset in pixels to the right edge of the bounding box relative to the origin positioned in the upper left corner
of the image.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
0 < RHC < HLL, RHC > LHC
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/ biom:FaceImageBoundingSquare
NIEM Element: biom:SegmentLeftHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.014_3: Face Image Bounding Box Coordinates in Full Image - Top Vertical Coordinate Value (TVC)
Description:
The vertical offset (pixel counts down) to the top of the bounding box.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
0 < BVC < VLL, BVC > TVC
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/ biom:FaceImageBoundingSquare
NIEM Element: biom:SegmentTopVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
488
Type-10: Photographic Body Part Imagery (including Face and
10.014_4: Face Image Bounding Box Coordinates in Full Image - Bottom Vertical Coordinate Value (BVC)
Description:
It is the vertical offset from the upper left corner of the image down to the bottom of the bounding box. It is counted in pixels.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 <= BVC <= VLL
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/ biom:FaceImageBoundingSquare
NIEM Element: biom:SegmentBottomVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.014_5: Face Image Bounding Box Coordinates in Full Image - Bounding Box Head Position Code (BBC)
Description:
The fifth information item of FIP is the bounding box type, indicating the contents of the bounding box. If this field is omitted,
the default value shall be H (Head only).
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
n/a
Format
n/a
Constraints
see Look Up Codes
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/ biom:FaceImageBoundingSquare
NIEM Element: biom:FaceImageBoundingCategoryCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
489
Type-10: Photographic Body Part Imagery (including Face and
10.015: Face Image Path Coordinates in Full Image (FPFI)
Description:
If the face image (IMT = 'FACE') contains more than one face, or is not cropped to a “head only” or “head and shoulders”
composition, this optional field contains offsets to the location of the path defining a region containing the face of the subject
within a larger image. This field is only appropriate for images that do not comply with SAP Levels Levels 30, 32, 40, 42, 50,
51, or 52, because those images shall be cropped to a “head only” or “head and shoulders” composition.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Code List: FACE BOUNDING CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImageBoundary
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.015_1: Face Image Path Coordinates in Full Image - Boundary Code (BYC)
Description:
Defines the shape of a boundary of a feature within an image.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
n/a
Format
n/a
Constraints
BYC = C, E or P
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/ biom:FaceImageBoundary
NIEM Element: biom:FaceImageBoundaryShapeCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
490
Type-10: Photographic Body Part Imagery (including Face and
10.015_2: Face Image Path Coordinates in Full Image - Number of Points (NOP)
Description:
Specifies the number of vertices.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
2 < NOP < 99, positive
integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImageBoundary
NIEM Element: biom:PositionPolygonVertexQuantity
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.015_3: Face Image Path Coordinates in Full Image - Horizontal Point Offset (HPO)
Description:
The pixel counts to the right.
path – for a total of NOP pairs
The HPO and NPO information items are repeated as pairs, in order by point following the
Field Minimum
1
Field Maximum
5
Occurrence Minimum
2
Occurrence Maximum
NOP
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
0 < HPO < HLL, integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImageBoundary/biom:PositionPolygonVertex
NIEM Element: biom:PositionHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
491
Type-10: Photographic Body Part Imagery (including Face and
10.015_4: Face Image Path Coordinates in Full Image - Vertical Point Offset (VPO)
Description:
The pixel counts down from the origin.
The HPO and NPO information items are repeated as pairs, in order by point
following the path – for a total of NOP pairs
Field Minimum
1
Field Maximum
5
Occurrence Minimum
2
Occurrence Maximum
NOP
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
0 < VPO < VLL, nonnegative
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImageBoundary/biom:PositionPolygonVertex
NIEM Element: biom:PositionVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.016: Scanned Horizontal Pixel Scale (SHPS)
Description:
The horizontal pixel density used for the scanning of the original image / impression providing that the SLC field contains a “1”
or “2”. Otherwise, this shall indicate the horizontal component of the pixel aspect ratio, up to 5 integer digits.
This field is
used if the transmission pixel scale differs from the original image scale, as listed in Transmitted horizontal pixel scale / THPS.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:ImageCaptureDetail
NIEM Element: biom:CaptureHorizontalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
492
Type-10: Photographic Body Part Imagery (including Face and
10.017: Scanned Vertical Pixel Scale (SVPS)
Description:
The vertical pixel density used for the scanning of the original image / impression providing that the SLC field contains a “1” or
“2”. Otherwise, this shall indicate the vertical component of the pixel aspect ratio, up to 5 integer digits.
Note that density is
directly related to resolution. If SLC is 1 or 2 and SHPS is entered, then SVPS shall equal SHPS.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: biom:FaceImage/biom:ImageCaptureDetail or biom:PhysicalFeatureImage/biom:ImageCaptureDetail
NIEM Element: biom:CaptureVerticalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.018: Distortion (DIST)
Description:
This field contains the type of distortion, whether it is estimated or calculated, and its relative severity. This field contains three
information items: Distortion Code (IDK), Distortion Field (IDK) and Distortion (DIS).
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:ImageDistortion
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
493
Type-10: Photographic Body Part Imagery (including Face and
10.018_1: Distortion - Distortion Code (IDK)
Description:
The first information item of the Distortion (DIST) field is the distortion code.
Field Minimum
6
Field Maximum
10
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
n/a
Format
n/a
Constraints
IDK = Barrel or Inflated or
Pincushion
Code List: DISTORTION CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:ImageDistortion
NIEM Element: biom:ImageDistortionCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.018_2: Distortion - Distortion Measurement Code (IDM)
Description:
The second information item of the Distortion field (DIST) is an alphabetic code, which is a distortion measurement code (IDM),
that indicates if the distortion is estimated “E” or calculated “C”.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
n/a
Format
n/a
Constraints
IDM = E or C
Code List: DISTORTION MEASUREMENT CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:ImageDistortion
NIEM Element: biom:ImageDistortionMeasurementCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
494
Type-10: Photographic Body Part Imagery (including Face and
10.018_3: Distortion - Distortion Severity Code (DSC)
Description:
The third information item of the Distortion field (DIS) is the distortion severity code (DSC).
Field Minimum
4
Field Maximum
8
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
n/a
Format
n/a
Constraints
DSC = Mild, Moderate or
Severe
Code List: DISTORTION SEVERITY CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:ImageDistortion
NIEM Element: biom:ImageDistortionSeverityCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.019: Lighting Artifacts (LAF)
Description:
This optional field (contains the type of lighting artifacts found in the Type-10 image record. It is only applicable to face images
(IMT = 'FACE'). Multiple lighting artifacts may be repeated as separate subfields.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
see Look Up Codes
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImageLightingArtifactsCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
495
Type-10: Photographic Body Part Imagery (including Face and
10.019_0: Lighting Artifacts - Subfields: Repeating values (LAF_0)
Description:
This optional field (contains the type of lighting artifacts found in the Type-10 image record. It is only applicable to face images
(IMT = 'FACE'). Multiple lighting artifacts may be repeated as separate subfields.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
3
Character Types
A
Special Characters
n/a
Format
n/a
Constraints
value = F, H or R
Code List: LIGHTING ARTIFACTS CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImageLightingArtifactsCode
XML Min/Max: 0 / 3
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.020: Subject Pose (POS)
Description:
This field is to be used for the exchange of facial image data. When included, this field shall contain one ASCII character code
selected from [possible codes below] to describe the pose of the subject. For the angled pose entry "A", [10.025 SPA Pose
Offset Angle field] shall contain the offset angle from the full face orientation. For the determined 3D pose entry "D", [Type-10
Subject Post Angles field] shall contain a set of determined 3D pose angles. Note that the offset angle in [Type-10 Pose
Offset Angle field] is opposite from the yaw angle in [Type-10 Subject Post Angles field] as indicated by a minus sign. A value
of POS = D does not imply that the image itself is a 3D image, such as a point cloud. 3D imagery shall be transmitted in a Type22 record.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
see Look Up Codes
Code List: SUBJECT POSE CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImageSubjectPoseCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
496
Type-10: Photographic Body Part Imagery (including Face and
10.021: Pose Offset Angle (POA)
Description:
This shall only be used for the exchange of facial image data (IMT = "FACE"). It may be used if Field 10.020: Subject pose /
POS contains an “A” to indicate an angled pose of the subject. The field shall not be used if the entry in POS is an “F”, “R”, “L”
or “D”. This field shall be omitted for a full face or a profile. This field specifies the pose direction of the subject at any possible
orientation within a circle. Its value shall be to the nearest degree. The offset angle shall be measured from the full-face pose
position and have a range of values from -180 degrees to +180 degrees. A positive angle is used to express the angular offset
as the subject rotates from a full-face pose to their left (approaching a right profile). The allowed special characters are the
plus sign and minus sign.
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Minus Sign, Plus Sign
Format
n/a
Constraints
-180 <= POA <= 180; integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImagePoseOffsetAngleMeasure
XML Min/Max: 0 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.023: Photo Acquisition Source (PAS)
Description:
This field shall specify the classification of the source of the image contained in this record.
This field is required if the SAP
entry [10.013 Subject Acquisition Profile field] is "40" or greater (IMT=FACE only). When included, this field shall contain an
ASCII character code selected to describe the source of captured image data.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImageAcquisitionSource
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
497
Type-10: Photographic Body Part Imagery (including Face and
10.023_1: Photo Acquisition Source - Photo Attribute Code (PAC)
Description:
The first information item in the Photo Acquisition Source (PAS) field shall contain an attribute code to describe the source of
captured image data.
Field Minimum
6
Field Maximum
14
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
n/a
Format
n/a
Constraints
see Look Up Codes
Code List: FACE IMAGE ACQUISITION CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImageAcquisitionSource
NIEM Element: biom:FaceImageAcquisitionSource
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.023_2: Photo Acquisition Source - Vendor-Specific Description (VSD)
Description:
When “VENDOR” is specified in photo attribute code / PAC, a second free-format information item (vendorspecific description /
VSD) may be entered with up to 64 characters to describe the vendor-specific source of the captured image or to enter
unlisted or miscellaneous source attributes for the facial image.
Field Minimum
1
Field Maximum
64
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImageAcquisitionSource
NIEM Element: biom:FaceImageAcquisitionCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
498
Type-10: Photographic Body Part Imagery (including Face and
10.024: Subject Quality Score (SQS)
Description:
This optional field shall specify quality score data for facial images (IMT = 'FACE') stored in this record. There may be subfields
for different quality scores and algorithms.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage
NIEM Element: biom:AcquisitionSourceDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.024_0: Subject Quality Score - Subfields: Repeating sets of information items (SQS_0)
Description:
This optional field shall specify quality score data for facial images (IMT = 'FACE') stored in this record. There may be subfields
for different quality scores and algorithms.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
9
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage
NIEM Element: biom:ImageQuality
XML Min/Max: 1 / 9
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
499
Type-10: Photographic Body Part Imagery (including Face and
10.024_1: Subject Quality Score - Quality Value (QVU)
Description:
This information item shall contain the integer image quality score between 0 and 100 (inclusive) assigned to the image data
by a quality algorithm. Higher values indicate better quality. An entry of “255” shall indicate a failed attempt to calculate a
quality score. An entry of “254” shall indicate that no attempt to calculate a quality score was made.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 < QVU < 100, nonnegative integer or QVU =
254 or 255
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage
NIEM Element: biom:QualityValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.024_2: Subject Quality Score - Algorithm Vendor Identification (QAV)
Description:
This information item shall specify the ID of the vendor of the quality algorithm used to calculate the quality score. This 4-digit
hex value is assigned by IBIA and expressed as four ASCII characters. The IBIA shall maintain the Vendor Registry of CBEFF
Biometric Organizations that will map the value in this field to a registered organization.
Field Minimum
4
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
0000 < QAV < FFFF
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:ImageQuality
NIEM Element: biom:QualityAlgorithmVendorID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
500
Type-10: Photographic Body Part Imagery (including Face and
10.024_3: Subject Quality Score - Algorithm Product Identification (QAP)
Description:
This information item shall specify a numeric product code assigned by the vendor of the quality algorithm, which may be
registered with the IBIA, but it is not required to be registered. It indicates which of the vendor’s algorithms was used in the
calculation of the quality score. This field contains the ASCII representation of the integer product code and should be within
the range 1 to 65535.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 < QAP < 65535, positive
integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:ImageQuality
NIEM Element: biom:QualityAlgorithmProductID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.025: Subject Pose Angles (SPA)
Description:
This ASCII set shall be present when [10.020 Subject Pose field] (POS) contains a "D" to indicate a set of determined 3D pose
angles of the same subject for a facial image (IMT = 'FACE'). When present, this information shall be entered as three or six
information items. The first three items specify the pose of the subject estimated or measured at constrained possible
orientations within a sphere. If this field is used, the first three are mandatory. Notes: ANSI/NIST ITL 1-2011: Update 2013
Subject Pose (POS) and subject pose angles (SPA) contains, additional information, details, and examples of the subject pose
angles.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImage3DPoseAngle
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
501
Type-10: Photographic Body Part Imagery (including Face and
10.025_1: Subject Pose Angles - Yaw Angle (YAW)
Description:
This information item is the Yaw angle (rotation about the vertical 'y' axis).
Field Minimum
1
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
NS
Special Characters
Minus Sign
Format
n/a
Constraints
-180 < YAW < 180, integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImage3DPoseAngle
NIEM Element: biom:PoseYawAngleMeasure
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.025_2: Subject Pose Angles - Pitch Angle (PIT)
Description:
This information item is the Pitch angle (rotation about 'x' horizontal axis).
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
NS
Special Characters
Minus Sign
Format
n/a
Constraints
-90 < PIT < 90, integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImage3DPoseAngle
NIEM Element: biom:PosePitchAngleMeasure
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
502
Type-10: Photographic Body Part Imagery (including Face and
10.025_3: Subject Pose Angles - Roll Angle (ROL)
Description:
This information Item is the Roll angle (rotation about the 'z' axis).
Field Minimum
1
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
NS
Special Characters
Minus Sign
Format
n/a
Constraints
180 < PIT < 180, integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImage3DPoseAngle
NIEM Element: biom:PoseRollAngleMeasure
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.025_4: Subject Pose Angles - Uncertainty in Degrees for Yaw (YAWU)
Description:
The measure of uncertainty concerning the rotation about the vertical or Y axis of the pose.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
0 < YAWU < 90, nonnegative, integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImage3DPoseAngle
NIEM Element: biom:PoseYawUncertaintyValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
503
Type-10: Photographic Body Part Imagery (including Face and
10.025_5: Subject Pose Angles - Uncertainty in Degrees for Pitch (PITU)
Description:
The fifth information item is the uncertainty in degrees for pitch / PITU.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
0 < PITU < 90, nonnegative, integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImage3DPoseAngle
NIEM Element: biom:PosePitchUncertaintyValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.025_6: Subject Pose Angles - Uncertainty in Degrees for Roll (ROLU)
Description:
The measure of uncertainty concerning the rotation about the Z axis of the pose.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
0 < ROLU < 90, nonnegative, integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImage3DPoseAngle
NIEM Element: biom:PoseRollUncertaintyValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
504
Type-10: Photographic Body Part Imagery (including Face and
10.026: Subject Facial Description (SXS)
Description:
This field is mandatory if the SAP entry for a facial image (Field 10.013: Subject acquisition profile / SAP) is “30” or greater.
(IMT = FACE only). In other cases, this field is optional for facial images. When present, it shall describe attributes associated
with the subject’s captured facial image. This version maintains the upper limit of 50 repeating subfields for all encodings from
the 2007 version. (The 2008 version was unrestricted). In the 2007 version, the minimum character count for this was listed as
5; however, there was an entry of “HAT” which has 3 characters. Thus, the minimum character count in this version is set at 3.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
D
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImageDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.026_0: Subject Facial Description - Subfields: repeating values (SXS_0)
Description:
This field is mandatory if the SAP entry for a facial image (Field 10.013: Subject acquisition profile / SAP) is “30” or greater.
(IMT = FACE only). In other cases, this field is optional for facial images. When present, it shall describe attributes associated
with the subject’s captured facial image. This version maintains the upper limit of 50 repeating subfields for all encodings from
the 2007 version. (The 2008 version was unrestricted). In the 2007 version, the minimum character count for this was listed as
5; however, there was an entry of “HAT” which has 3 characters. Thus, the minimum character count in this version is set at 3.
Field Minimum
3
Field Maximum
20
Occurrence Minimum
1
Occurrence Maximum
50
Character Types
AS
Special Characters
n/a
Format
n/a
Constraints
see Look Up Codes
Code List: SUBJECT FACIAL DESCRIPTION CODES
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImageDescriptionText
XML Min/Max: 1 / 50
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
505
Type-10: Photographic Body Part Imagery (including Face and
10.027: Subject Eye Color - Repeating values. (SEC)
Description:
Describe the eye color of the subject as seen in the photograph. If unusual or unnatural such as may be the case when colored
contact lenses are present and the “real” eye color cannot be ascertained, then the color should be labeled as “XXX”. Eye
color attributes and attribute codes are given by possible codes.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
see Look Up Codes
Code List: ALPHA EYE COLOR CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: j:PersonEyeColorCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.028: Subject Hair Color (SHC)
Description:
Describes the hair color of the subject as seen in the photograph.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:HairColorCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
506
Type-10: Photographic Body Part Imagery (including Face and
10.028_0: Subject Hair Color - Subfields: Repeating values (SHC_0)
Description:
Describes the hair color of the subject as seen in the photograph.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
2
Character Types
A
Special Characters
n/a
Format
n/a
Constraints
see Look Up Codes
Code List: HAIR COLOR
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:HairColorCode
XML Min/Max: 0 / 2
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.029: 2D Facial Feature Points (FFP)
Description:
The ASCII set shall be used for the exchange of facial image data. When present, it shall describe special attributes of
manually or automatically detected facial feature points of the captured facial image. The optional field shall be used for the
exchange of facial (IMT = 'FACE', 'HEAD', 'LIP', 'EXTRAORAL' and 'CONDITION') feature points or landmarks. This
information shall be entered as a four-information item feature point block in a repeating subfield.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImage2DFeaturePoint
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
507
Type-10: Photographic Body Part Imagery (including Face and
10.029_0: 2D Facial Feature Points - Subfields: Repeating sets of information items (FFP_0)
Description:
The ASCII set shall be used for the exchange of facial image data. When present, it shall describe special attributes of
manually or automatically detected facial feature points of the captured facial image. The optional field shall be used for the
exchange of facial (IMT = 'FACE', 'HEAD', 'LIP', 'EXTRAORAL' and 'CONDITION') feature points or landmarks. This
information shall be entered as a four-information item feature point block in a repeating subfield.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
88
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImage2DFeaturePoint
XML Min/Max: 1 / 88
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.029_1: 2D Facial Feature Points - Feature Point Type (FPT)
Description:
The first information item of 2D Facial Feature Points (FFP) or 3D Facial Feature Points (3DF) is a one character value. It is
mandatory. It shall be either: 1 = Denoting an MPEG4 Feature point, or 2 = Anthropometric landmark.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
FPT = 1 or 2
Code List: FEATURE POINT TYPE CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImage2DFeaturePoint
NIEM Element: biom:FeaturePointCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
508
Type-10: Photographic Body Part Imagery (including Face and
10.029_2: 2D Facial Feature Points - Feature Point Code (FPC)
Description:
If FPT is 1, this information item shall be “A.B” with A and B defined. If FPT is 2, the codes are entered as shown in the
Feature Point ID column of the Feature Point ID Code table.
Field Minimum
3
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
Period
Format
n/a
Constraints
Format: N.N, N.NN, NN.N,
NN.NN, a, aa, aaa or aaaa
Code List: FEATURE POINT ID CODE / EYE AND NOSTRIL CENTER FEATURE POINT CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImage3DFeaturePoint
NIEM Element: biom:FeaturePointID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.029_3: 2D Facial Feature Points - X Coordinate (HCX)
Description:
The third information item of the 2D Facial Feature Points (FFD) or 3D Facial Feature Points (3DF). It is 1 to 5 characters,
denoting the pixel count horizontally to the right from the upper left pixel, which is set to 0.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 < HCX< HLL, non-negative
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImage3DFeaturePoint
NIEM Element: biom:FeaturePointHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
509
Type-10: Photographic Body Part Imagery (including Face and
10.029_4: 2D Facial Feature Points - Y Coordinate (HCY)
Description:
The fourth information item of the 2D Facial Feature Points (FFD) or 3D Facial Feature Points (3DF). It is 1 to 5 characters,
denoting the pixel count vertically down from the upper left pixel, which is set to 0.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 < HCY < VLL, nonnegative
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImage3DFeaturePoint
NIEM Element: biom:FeaturePointVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.030: Device Monitoring Mode (DMM)
Description:
This field provides information describing the human monitoring operation of the image capture device, and will contain an
entry from the Device Monitoring Mode Code list to indicate the monitoring mode of the biometric sample capture device.
Field Minimum
7
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
see Look Up Codes
Code List: CAPTURE DEVICE MONITORING MODE CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:ImageCaptureDetail
NIEM Element: biom:CaptureDeviceMonitoringModeCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
510
Type-10: Photographic Body Part Imagery (including Face and
10.031: Tiered Markup Collection (TMC)
Description:
This optional field describes the specific facial (IMT = 'FACE') feature points contained in Field 10.029: 2D Facial feature points
/ FFP and if level 5, contours shall be contained in Field 10.033: Feature contours / FEC.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer; see Look Up Codes
Code List: TIERED MARKUP COLLECTION CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImageFeaturePointTierNumeric
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.032: 3D Facial Feature Points (3DF)
Description:
Each subfield refers to a specific contour on the image and contains a minimum of three points. This field shall appear if TMC
= 5, otherwise, it is optional.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImage3DFeaturePoint
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
511
Type-10: Photographic Body Part Imagery (including Face and
10.032_0: 3D Facial Feature Points - Subfields: Repeating sets of information items (3DF_0)
Description:
Each subfield refers to a specific contour on the image and contains a minimum of three points. This field shall appear if TMC
= 5, otherwise, it is optional.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
88
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImage3DFeaturePoint
XML Min/Max: 1 / 88
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.032_1: 3D Facial Feature Points - Feature Point Type (FPT)
Description:
The first information item of 2D Facial Feature Points (FFP) or 3D Facial Feature Points (3DF) is a one character value. It is
mandatory. It shall be either: 1 = Denoting an MPEG4 Feature point, or 2 = Anthropometric landmark. The allowed special
character is a period. If FPT is 2, the codes are entered as shown in the “Feature Point ID” column of Table 65. Note that this
entry is one to four alphabetic characters.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
FPT = 1 or 2
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImage3DFeaturePoint
NIEM Element: biom:FeaturePointCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
512
Type-10: Photographic Body Part Imagery (including Face and
10.032_2: 3D Facial Feature Points - Feature Point Code (FPC)
Description:
The second information item, feature point code / FPC is 3 to 5 characters. If FPT is 1, this information item shall be “A.B” with
A and B defined ANSI/NIST ITL 1-2011: Update 2013. If FPT is 2, the codes are entered as shown in the “Feature Point ID”
column Feature Point ID Code and Eye and Nostril Center Feature Point Code lists.
Field Minimum
3
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
Period
Format
N.N, N.NN, NN.N, NN.NN,
a, aa, aaa or aaaa
Constraints
Format: N.N, N.NN, NN.N,
NN.NN, a, aa, aaa or aaaa
Code List: FEATURE POINT ID CODE / EYE AND NOSTRIL CENTER FEATURE POINT CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImage3DFeaturePoint
NIEM Element: biom:FeaturePointID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.032_3: 3D Facial Feature Points - X Coordinate (HCX)
Description:
The third information item of the 2D Facial Feature Points (FFD) or 3D Facial Feature Points (3DF). It is 1 to 5 characters,
denoting the pixel count horizontally to the right from the upper left pixel, which is set to 0.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 < HCX< HLL, nonnegative, integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImage3DFeaturePoint
NIEM Element: biom:FeaturePointHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
513
Type-10: Photographic Body Part Imagery (including Face and
10.032_4: 3D Facial Feature Points - Y Coordinate (HCY)
Description:
The fourth information item of the 2D Facial Feature Points (FFD) or 3D Facial Feature Points (3DF). It is 1 to 5 characters,
denoting the pixel count vertically down from the upper left pixel, which is set to 0.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 < HCY < VLL, nonnegative, integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImage3DFeaturePoint
NIEM Element: biom:FeaturePointVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.032_5: 3D Facial Feature Points - Z Coordinate (HCZ)
Description:
The fifth information item of the 3D Facial Feature Points (3DF) field. It is 1 to 5 characters, denoting the pixel count from the XY plane, which is set to 0.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 < HCZ < 99999,
nonnegative, integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImage3DFeaturePoint
NIEM Element: biom:FeaturePointZCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
514
Type-10: Photographic Body Part Imagery (including Face and
10.033: Feature Contours (FEC)
Description:
Each subfield refers to a specific contour on the image and contains a minimum of three points. This field shall appear if TMC
= 5. It is optional otherwise.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImageContour
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.033_0: Feature Contours - Subfields: Repeating sets of information items (FEC_0)
Description:
Each subfield refers to a specific contour on the image and contains a minimum of three points. This field shall appear if TMC
= 5. It is optional otherwise.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
12
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImageContour
XML Min/Max: 1 / 12
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
515
Type-10: Photographic Body Part Imagery (including Face and
10.033_1: Feature Contours - Feature Contour Code (FCC)
Description:
The first information item of the Feature Contour (FEC).
Field Minimum
4
Field Maximum
14
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
n/a
Format
n/a
Constraints
see Look Up Codes
Code List: FEATURE CONTOUR CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImageContour
NIEM Element: biom:FaceImageContourCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.033_2: Feature Contours - Number of Points (NOP)
Description:
Specifies the number of vertices.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
3 < NOP < 99
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImageContour
NIEM Element: biom:PositionPolygonVertexQuantity
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
516
Type-10: Photographic Body Part Imagery (including Face and
10.033_3: Feature Contours - Horizontal Point Offset (HPO)
Description:
The pixel counts to the right.
The HPO and VPO information items are repeated as pairs, in order by point following the
path, up to the final point - for a total of NOP pairs.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
3
Occurrence Maximum
NOP
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
0 < HPO < HLL
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImageContour/biom:PositionPolygonVertex
NIEM Element: biom:PositionHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.033_4: Feature Contours - Vertical Point Offset (VPO)
Description:
The pixel counts down from the origin.
The HPO and VPO information items are repeated as pairs, in order by point
following the path, up to the final point - for a total of NOP pairs.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
3
Occurrence Maximum
NOP
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
0 < VPO < VLL
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImageContour/biom:PositionPolygonVertex
NIEM Element: biom:PositionVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
517
Type-10: Photographic Body Part Imagery (including Face and
10.034: IMAGE CAPTURE DATE RANGE ESTIMATE (ICDR)
Description:
It is possible to enter only a year, month and/or day range, such as D5, meaning that the actual date of collection is estimated
to be 5 days plus or minus from that specified in PHD.
Leading zeros need not be entered.
Field Minimum
3
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
n/a
Format
YYMMDD
Constraints
Time measure indicator
followed by 1 or 2 digits.
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:ImageCaptureDetail
NIEM Element: biom:CaptureDateEstimateRangeDuration
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.038: Comment (COM)
Description:
The optional Comment field appears in many record types and may be used to insert free text information. It is not reserved
exclusively for log-related information but has historically often been used for this purpose. It is limited to a maximum of 126
characters. This maximum size was established in order to maintain consistency across encodings. The maximum size differed
in the 2007 and 2008 versions of the standard.
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage
NIEM Element: biom:ImageCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
518
Type-10: Photographic Body Part Imagery (including Face and
10.039: Type-10 Reference Number (T10)
Description:
Cheiloscopic image data / CID or dental visual image comparison descriptive text / VICD is present in Field 10.050: Dental
visual image data information / VID. The same T10 is used when referring to a particular image. This field shall only be
present if multiple Type-10 records in the transaction contain the same SMT or body part. It can be used for any image type
specified in Field 10.003: Image type / IMT. T10 is a positive integer. The only requirement is that a value for T10 only links
related images. An example would be to assign a value of 1 to two different Type-10 records, the first of which has an image of
a tattoo over the entire chest of a male. A second image of a small portion of the tattoo on the chest showing a gang symbol is
contained in another Type-10 with the same value of 1 for T10. No other Type-10 records (in this example) would have a value
of 1 for T10. This is an optional field. It is used when several images cover either the entire scar, (needle) mark, tattoo (SMT)
or portions of it. This field shall be present if lip print comparison descriptive text / LPCT is present in Field 10.049: The same
T10 is used when referring to a particular image. This field shall only be present if multiple Type-10 records in the transaction
contain the same SMT or body part.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
1 <= T10 <= 255
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage
NIEM Element: biom:Type10CrossReferenceID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
519
Type-10: Photographic Body Part Imagery (including Face and
10.040: NCIC SMT Code (SMT)
Description:
This field shall be used only when Field 10.003: Image type / IMT = “SCAR”, “MARK”, or “TATTOO”. It is not used for other
images. It is used to identify a general location of the captured scar, mark, tattoo, or other characteristic (including piercings)
in an image. The contents of this field shall be from the NCIC code. The captured image may encompass an area larger than
that specified by a single NCIC body part code for the particular image type. This situation may be accommodated by listing
multiple NCIC codes, each in a separate subfield. In this case the primary code is listed first. There need not be more than one
subfield. For the “marks” category, the NCIC manual lists the common locations for needle track marks. For other body part
locations not listed under the “marks” category, use the body location codes listed for scars.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
None
Format
n/a
Constraints
Values from Annex D of
ANSI/NIST ITL 1-2011
(Update 2013)
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage
NIEM Element: biom:PhysicalFeatureNCICCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.040_0: NCIC SMT Code - Subfields: Repeating values (SMT_0)
Description:
This field shall be used only when Field 10.003: Image type / IMT = “SCAR”, “MARK”, or “TATTOO”. It is not used for other
images. It is used to identify a general location of the captured scar, mark, tattoo, or other characteristic (including piercings)
in an image. The contents of this field shall be from the NCIC code. The captured image may encompass an area larger than
that specified by a single NCIC body part code for the particular image type. This situation may be accommodated by listing
multiple NCIC codes, each in a separate subfield. In this case the primary code is listed first. There need not be more than one
subfield. For the “marks” category, the NCIC manual lists the common locations for needle track marks. For other body part
locations not listed under the “marks” category, use the body location codes listed for scars.
Field Minimum
3
Field Maximum
10
Occurrence Minimum
1
Occurrence Maximum
3
Character Types
AS
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage
NIEM Element: biom:PhysicalFeatureNCICCode
XML Min/Max: 1 / 3
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
520
Type-10: Photographic Body Part Imagery (including Face and
10.041: SMT SIZE OR SIZE OF INJURY OR IDENTIFYING CHARACTERISTIC (SMS)
Description:
This set shall contain the dimensions of the portion of image contained in this record (it may be the entire scar, mark, tattoo,
injury or identifying characteristic). Each dimension shall be entered to the nearest centimeter.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:PhysicalFeatureSize
XML Min/Max: 0 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.041_1: SMT SIZE OR SIZE OF INJURY OR IDENTIFYING CHARACTERISTIC - Height (HGT)
Description:
The height of the scar, mark or tattoo in nearest centimeter.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:PhysicalFeatureSize
NIEM Element: biom:PhysicalFeatureHeightMeasure
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
521
Type-10: Photographic Body Part Imagery (including Face and
10.041_2: SMT SIZE OR SIZE OF INJURY OR IDENTIFYING CHARACTERISTIC - Width (WID)
Description:
The width of the scar, mark or tattoo in the nearest centimeter.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:PhysicalFeatureSize
NIEM Element: biom:PhysicalFeatureWidthMeasure
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.042: SMT Descriptors (SMD)
Description:
This field is used to describe the content of the SMT image to an extent greater than documented in Field 10.040: NCIC SMT
code / SMT. It shall consist of one or more subfields. This version maintains the upper limit of 9 for all encodings. This field
shall be used only when Field 10.003: Image type / IMT= “SCAR”, “MARK”, or “TATTOO”. An SMT image consisting of several
parts or sub-images shall use subfields to fully describe the various parts or features found in the total image.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:PhysicalFeatureDescriptionDetail
NIEM Element: biom:PhysicalFeatureDescriptionDetail
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
522
Type-10: Photographic Body Part Imagery (including Face and
10.042_0: SMT Descriptors - Subfields: Repeating values (SMD_0)
Description:
This field is used to describe the content of the SMT image to an extent greater than documented in Field 10.040: NCIC SMT
code / SMT. It shall consist of one or more subfields. This version maintains the upper limit of 9 for all encodings. This field
shall be used only when Field 10.003: Image type / IMT= “SCAR”, “MARK”, or “TATTOO”. An SMT image consisting of several
parts or sub-images shall use subfields to fully describe the various parts or features found in the total image.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
9
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:PhysicalFeatureDescriptionDetail
NIEM Element: biom:PhysicalFeatureDescriptionDetail
XML Min/Max: 1 / 9
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.042_1: SMT Descriptors - SMT code indicator (SMI)
Description:
This information item shall identify the source of the image as being a scar, a mark or a tattoo.
Field Minimum
3
Field Maximum
8
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
Code List: SMT DESCRIPTORS
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:PhysicalFeatureDescriptionDetail
NIEM Element: biom:PhysicalFeatureCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
523
Type-10: Photographic Body Part Imagery (including Face and
10.042_2: SMT Descriptors - Tattoo Class (TAC)
Description:
This information item shall be the general class code of tattoo chosen. For each general class of tattoo, there are several
defined subclasses.
Field Minimum
4
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
Code List: TATTOO CLASSES CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:PhysicalFeatureDescriptionDetail
NIEM Element: biom:PhysicalFeatureClassCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.042_3: SMT Descriptors - Tattoo Subclass (TSC)
Description:
This information item of the subfield shall be the appropriate subclass code selected from the various subclasses of tattoos for
each of the general classes.
Field Minimum
3
Field Maximum
11
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
Code List: TATTOO CLASSES CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:PhysicalFeatureDescriptionDetail
NIEM Element: biom:PhysicalFeatureSubClassCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
524
Type-10: Photographic Body Part Imagery (including Face and
10.042_4: SMT Descriptors - Tattoo Description (TDS)
Description:
This information item in the subfield shall be an ASCII text string that provides additional qualifiers to describe the image or
portion of the image.
Field Minimum
1
Field Maximum
256
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:PhysicalFeatureDescriptionDetail
NIEM Element: biom:PhysicalFeatureDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.043: Tattoo Color (COL)
Description:
This field is optional, but it can only be used when Field 10.042: SMT descriptors / SMD is in the record. It shall contain one
subfield corresponding to each subfield contained in Field 10.042: SMT descriptors / SMD. Each subfield shall contain up to 6
information items that state the color(s) of the tattoo or part of the tattoo. For each subfield entry, the first one shall be the
predominant color. Additional colors may be entered as optional subsequent information items of the form tattoo color code 1
through tattoo code 6. There need not be more than one information item.
This field can only be used when Field 10.042:
SMT descriptors / SMD is in the record.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
D
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:PhysicalFeatureDescriptionDetail
NIEM Element: biom:PhysicalFeatureColorDetail
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
525
Type-10: Photographic Body Part Imagery (including Face and
10.043_0: Tattoo Color - Subfields: repeating values in the same order as those of SMD (COL_0)
Description:
This field is optional, but it can only be used when Field 10.042: SMT descriptors / SMD is in the record. It shall contain one
subfield corresponding to each subfield contained in Field 10.042: SMT descriptors / SMD. Each subfield shall contain up to 6
information items that state the color(s) of the tattoo or part of the tattoo. For each subfield entry, the first one shall be the
predominant color. Additional colors may be entered as optional subsequent information items of the form tattoo color code 1
through tattoo code 6. There need not be more than one information item.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
9
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:PhysicalFeatureDescriptionDetail
NIEM Element: biom:PhysicalFeatureColorDetail
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.043_1: Tattoo Color - Tattoo Color Code 1 (TC1)
Description:
This first information item is part of the Tattoo Color (COL) field. It lists the predominant color of the tattoo or part of the tattoo.
Field Minimum
3
Field Maximum
7
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:PhysicalFeatureDescriptionDetail/biom:Physi
calFeatureColorDetail
NIEM Element: biom:PhysicalFeaturePrimaryColorCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
526
Type-10: Photographic Body Part Imagery (including Face and
10.043_2: Tattoo Color - Tattoo Color Code 2 (TC2)
Description:
This second information item is part of the Tattoo Color (COL) field. It lists the additional color of the tattoo or part of the tattoo.
Field Minimum
3
Field Maximum
7
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:PhysicalFeatureDescriptionDetail/biom:Physi
calFeatureColorDetail
NIEM Element: biom:PhysicalFeatureSecondaryColorCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.043_3: Tattoo Color - Tattoo Color Code 3 (TC3)
Description:
This third information item is part of the Tattoo Color (COL) field. It lists the additional color of the tattoo or part of the tattoo.
Field Minimum
3
Field Maximum
7
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:PhysicalFeatureDescriptionDetail/biom:Physi
calFeatureColorDetail
NIEM Element: biom:PhysicalFeatureSecondaryColorCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
527
Type-10: Photographic Body Part Imagery (including Face and
10.043_4: Tattoo Color - Tattoo Color Code 4 (TC4)
Description:
This fourth information item is part of the Tattoo Color (COL) field. It lists the additional color of the tattoo or part of the tattoo.
Field Minimum
3
Field Maximum
7
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:PhysicalFeatureDescriptionDetail/biom:Physi
calFeatureColorDetail
NIEM Element: biom:PhysicalFeatureSecondaryColorCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.043_5: Tattoo Color - Tattoo Color Code 5 (TC5)
Description:
This fifth information item is part of the Tattoo Color (COL) field. It lists the additional color of the tattoo or part of the tattoo.
Field Minimum
3
Field Maximum
7
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:PhysicalFeatureDescriptionDetail/biom:Physi
calFeatureColorDetail
NIEM Element: biom:PhysicalFeatureSecondaryColorCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
528
Type-10: Photographic Body Part Imagery (including Face and
10.043_6: Tattoo Color - Tattoo Color Code 6 (TC6)
Description:
This sixth information item is part of the Tattoo Color (COL) field. It lists the additional color of the tattoo or part of the tattoo.
Field Minimum
3
Field Maximum
7
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:PhysicalFeatureDescriptionDetail/biom:Physi
calFeatureColorDetail
NIEM Element: biom:PhysicalFeatureSecondaryColorCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.044: Image Transform (ITX)
Description:
This optional field is used in the case when the image in this Type-10 record has been transformed from the original image.
The untransformed image(s) (optionally) may be included in a Type-20 record. The information item in this field may be
repeated if multiple transforms were performed. It can be used for any image type specified in Field 10.003: Image type / IMT .
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:ImageTransformationCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
529
Type-10: Photographic Body Part Imagery (including Face and
10.044_0: Image Transform - Subfields: Repeating values (ITX_0)
Description:
This optional field is used in the case when the image in this Type-10 record has been transformed from the original image.
The untransformed image(s) (optionally) may be included in a Type-20 record. The information item in this field may be
repeated if multiple transforms were performed. It can be used for any image type specified in Field 10.003: Image type / IMT .
Field Minimum
3
Field Maximum
11
Occurrence Minimum
1
Occurrence Maximum
18
Character Types
A
Special Characters
None
Format
n/a
Constraints
see Look Up Codes
Code List: IMAGE TRANSFORM VALUES CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:ImageTransformationCode
XML Min/Max: 1 / 18
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.045: Occlusions (OCC)
Description:
This optional field defines the outline and contents of any occlusions that partially or totally blocks the image of the face (IMT =
'FACE'). This is a contour or a polygon. Each point on the polygon is represented by a pair of information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImageOcclusion
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
530
Type-10: Photographic Body Part Imagery (including Face and
10.045_0: Occlusions - Subfields: Repeating values (OCC_0)
Description:
This optional field defines the outline and contents of any occlusions that partially or totally blocks the image of the face (IMT =
'FACE'). This is a contour or a polygon. Each point on the polygon is represented by a pair of information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
16
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:FaceImageOcclusion
XML Min/Max: 1 / 16
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.045_1: Occlusions - Occlusion Opacity (OCY)
Description:
This field contains a code from the Occlusion Opacity Code table.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
n/a
Format
n/a
Constraints
OCY = T, I, L or S
Code List: OCCLUSION OPACITY CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImageOcclusion
NIEM Element: biom:FaceImageOcclusionOpacityCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
531
Type-10: Photographic Body Part Imagery (including Face and
10.045_2: Occlusions - Occlusion Type (OCT)
Description:
This field contains a code from the Occlusion Type Code table.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
OCT = H, S, C, R, or O
Code List: OCCLUSION TYPE CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImageOcclusion
NIEM Element: biom:FaceImageOcclusionCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.045_3: Occlusions - Number of Points (NOP)
Description:
This field shall specify the number of vertices.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
3 <= NOP <=99
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImageOcclusion
NIEM Element: biom:PositionPolygonVertexQuantity
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
532
Type-10: Photographic Body Part Imagery (including Face and
10.045_4: Occlusions - Horizontal Point Offset (HPO)
Description:
This field contains information items are pairs of x and y coordinates of vertices. The horizontal offsets (X) are the pixel counts
to the right. Pairings are inserted for each vertex, up to the NOP.
The HPO and VPO two information items are repeated as
pairs, in order by point following the path, up to the final point - for a total of NOP pairs
Field Minimum
1
Field Maximum
5
Occurrence Minimum
3
Occurrence Maximum
NOP
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
0 <= HPO <= HLL
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImageContour/biom:PositionPolygonVertex
NIEM Element: biom:PositionHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.045_5: Occlusions - Vertical Point Offset (VPO)
Description:
This field contains information items are pairs of x and y coordinates of vertices. The vertical offsets (Y) are the pixel counts
down from the origin. Pairings are inserted for each vertex, up to the NOP.
The HPO and VPO two information items are
repeated as pairs, in order by point following the path, up to the final point - for a total of NOP pairs
Field Minimum
1
Field Maximum
5
Occurrence Minimum
3
Occurrence Maximum
NOP
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
0 <= VPO <= VLL
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:FaceImageContour/biom:PositionPolygonVertex
NIEM Element: biom:PositionVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
533
Type-10: Photographic Body Part Imagery (including Face and
10.046: Image Subject Condition (SUB)
Description:
This field is optional. This field is particularly useful if the image is obtained from a deceased person. However, its use is not
limited to such circumstances. Some implementation domains support the submission of fingerprints taken from deceased
individuals as latent prints, due to the quality of the friction ridges and the resulting images. In such cases, SSC is specified as
D. For latent images taken from a surface, the value is typically X.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:SubjectExistentialDetails
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.046_1: Image Subject Condition - Subject Status Code (SSC)
Description:
The first information item is mandatory if this field is present. It is subject status code (SSC).
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
n/a
Format
n/a
Constraints
SSC = X, A or D
Code List: SUBJECT STATUS CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:SubjectExistentialDetails
NIEM Element: biom:SubjectExistentialStatusCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
534
Type-10: Photographic Body Part Imagery (including Face and
10.046_2: Image Subject Condition - Subject Body Status Code (SBSC)
Description:
The second information item shall be entered if and only if SSC is D. It is subject body status code (SBSC). Its purpose is to
indicate whether the information relates to an entire corpse or a separate body part.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
SBSC = 1 or 2, positive
integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:SubjectExistentialDetails
NIEM Element: biom:SubjectBodyStatusCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.046_3: Image Subject Condition - Subject Body Class Code (SBCC)
Description:
The third information item shall be entered if and only if SSC is D. It is subject body class code (SBCC).
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
SBCC = 1, 2, or 3, positive
integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:SubjectExistentialDetails
NIEM Element: biom:SubjectBodyClassCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
535
Type-10: Photographic Body Part Imagery (including Face and
10.047: Capture Organization Name (CON)
Description:
Describes the agency that created the record. Since the record may have been forwarded by another agency to the final
destination, Field 1.008: Originating agency identifier / ORI is used to indicate the transmitting organization. In many
implementation domains, there are a limited number of transmission organizations that can send data. Therefore, the agency
listed in SRC may send the transaction to another location that has access rights to the final destination. This intermediary may
add information to the transaction, as well. The final transmitting organization code is listed in Field 1.008: Originating agency
identifier / ORI. Its name may be entered in Originating agency name /OAN in Field 1.017: Agency names
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:ImageCaptureDetail/biom:CaptureOrganization
NIEM Element: nc:OrganizationUnitName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.048: Suspected Patterned Injury Detail (PID)
Description:
This field contains information concerning suspected patterned injuries. This optional field defines the outline and contents of
any occlusions that partially or totally blocks the image of the face (IMT = 'FACE'). This is a contour or a polygon. Values for
Field 10.003: Image type / IMT of SCAR, MARK, TATTOO, MISSING, OTHER and CONDITION shall not be used for patterned
injuries, and thus this field shall not appear if IMT is set to any of those values. Field 10.041: SMT size or size of injury or
identifying characteristic / SMS should be included in the record if this field is present.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:PatternedInjuryDetail
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
536
Type-10: Photographic Body Part Imagery (including Face and
10.048_0: Suspected Patterned Injury Detail - Subfields: Repeating sets of information items (PID_0)
Description:
This field contains information concerning suspected patterned injuries. This optional field defines the outline and contents of
any occlusions that partially or totally blocks the image of the face (IMT = 'FACE'). This is a contour or a polygon. Values for
Field 10.003: Image type / IMT of SCAR, MARK, TATTOO, MISSING, OTHER and CONDITION shall not be used for patterned
injuries, and thus this field shall not appear if IMT is set to any of those values. Field 10.041: SMT size or size of injury or
identifying characteristic / SMS should be included in the record if this field is present.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
Unlimited
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage
NIEM Element: biom:PatternedInjuryDetail
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.048_1: Suspected Patterned Injury Detail - ADA Reference Code List (PARC)
Description:
This field ontains a code value characterizing a patterned injury in ANSI/ADA Standard No. 1077 – Dental Biometric
Descriptors.
Field Minimum
1
Field Maximum
30
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
n/a
Format
n/a
Constraints
Valid Code from ANSI/ADA
Standard No. 1077
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:PatternedInjuryDetail
NIEM Element: biom:PatternedInjuryReferenceCodeText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
537
Type-10: Photographic Body Part Imagery (including Face and
10.048_2: Suspected Patterned Injury Detail - Additional Descriptive Text (PADT)
Description:
This field contains a Unicode free text information item description of the patterned injury.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:PatternedInjuryDetail
NIEM Element: biom:PatternedInjuryDescriptiveText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.049: Cheilioscopic Image Description (CID)
Description:
This field contains a set of subfield relaying information about the Cheilioscopic Image. If this field is encoded in Traditional
format, each of the values in information items designated as a 'list' shall be separated by '|' (vertical bar). For XML each value
in a list should be entered as a separate element. This field may be used only if Field 10.003: Image type / IMT is LIP. The
vertical bar “|” is used in Traditional format in a list as a separating character. In XML encoding, each value (including <>) is a
separate element and the vertical bar does not appear.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage
NIEM Element: biom:CheiloscopicImageInformation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
538
Type-10: Photographic Body Part Imagery (including Face and
10.049_1: Cheilioscopic Image Description - Lip Print Width (LPW)
Description:
It corresponds to the distance from feature point code 8.4 to feature point code 8.3 on the MOUTH in Feature point codes
defined inISO/IEC 14496-2 FEATURE POINT CODES. It is measured in millimeters.
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
positive integer
Code List: ISO/IEC 14496-2 FEATURE POINT CODES
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:CheiloscopicImageInformation
NIEM Element: biom:LipPrintWidthValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.049_2: Cheilioscopic Image Description - Lip Print Height (LPH)
Description:
It contains the distance from feature points 8.2 to feature point 2.3 PLUS the distance from feature point 2.2 to feature 8.1 on
the MOUTH in Feature point codes defined ISO/IEC 14496-2 FEATURE POINT CODES. It is measured in millimeters.
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
positive integer
Code List: ISO/IEC 14496-2 FEATURE POINT CODES
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:CheiloscopicImageInformation
NIEM Element: biom:LipPrintHeightValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
539
Type-10: Photographic Body Part Imagery (including Face and
10.049_3: Cheilioscopic Image Description - Philtrum Width (PHW)
Description:
It is the distance from feature point 8.9 to 8.10 as shown in Feature point codes defined in ISO/IEC 14496-2 FEATURE POINT
CODES. It is measured in millimeters.
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
positive integer
Code List: ISO/IEC 14496-2 FEATURE POINT CODES
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:CheiloscopicImageInformation
NIEM Element: biom:PhiltrumWidthValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.049_4: Cheilioscopic Image Description - Philtrum Height (PHH)
Description:
PHH is the distance in millimeters from feature point 8.1 to 9.15 (on the nose).
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
positive integer
Code List: CHEILIOSCOPIC CHARACTERIZATION CODES
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:CheiloscopicImageInformation
NIEM Element: biom:PhiltrumHeightValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
540
Type-10: Photographic Body Part Imagery (including Face and
10.049_5: Cheilioscopic Image Description - Upper Lip Characterization List (ULCL)
Description:
The fifth information item, upper lip print characterization list/ ULCL, is optional. It is text that may be used to describe the print.
The characterizations are those developed by Suzuki and Tsuchihashi. It is highly recommended that any distinctive patterns
be outlined using Field 10.033: Feature contours / FEC.
This field's XML reference is not in the NIEM Biometrics domain
table. Coded as biom domain by NIST Appendix G.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AS
Special Characters
n/a
Format
n/a
Constraints
list may have up to 5 values
Code List: CHEILIOSCOPIC CHARACTERIZATION CODES
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:CheiloscopicImageInformation
NIEM Element: biom:UpperLipCharacterizationCodeList
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.049_6: Cheilioscopic Image Description - Lower Lip Characterization List (LLCL)
Description:
The fifth information item, lower lip print characterization list/ LLCL, is optional. It is text that may be used to describe the print.
The characterizations are those developed by Suzuki and Tsuchihashi. It is highly recommended that any distinctive patterns
be outlined using Field 10.033: Feature contours / FEC.
This field's XML reference is not in the NIEM Biometrics domain
table. Coded as biom domain by NIST Appendix G.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AS
Special Characters
For traditional encoding,
the special character “|” is
allowed as a separator
character
Format
n/a
Constraints
list may have up to 5 values
Code List: CHEILIOSCOPIC CHARACTERIZATION CODES
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:CheiloscopicImageInformation
NIEM Element: biom:LowerLipCharacterizationCodeList
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
541
Type-10: Photographic Body Part Imagery (including Face and
10.049_7: Cheilioscopic Image Description - Lip Contact Line Descriptor (LCLD)
Description:
Contains the LIP CONTACT LINE DESCRIPTOR CODES.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
n/a
Format
n/a
Constraints
LCLD = L, C or M
Code List: LIP CONTACT LINE DESCRIPTOR CODES
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:CheiloscopicImageInformation
NIEM Element: biom:LipContactLineDescriptorCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.049_8: Cheilioscopic Image Description - Lip Print Characterization Text (LPCT)
Description:
Description of the lip print characterization. This field is mandatory if LPCL contains the value O. It is UNICODE free text.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:CheiloscopicImageInformation
NIEM Element: biom:CheiloscopicImageInformation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
542
Type-10: Photographic Body Part Imagery (including Face and
10.049_9: Cheilioscopic Image Description - Lip Print Pathologies and Peculiarities List (LPPL)
Description:
If Type-code 99 is selected, then LPPT shall be used to describe the condition. Only one of the values 8, 9, 10, 11 or 12 may
appear in the list.
List may have up to 13 values. Only one of the values 8, 9, 10 11, or 12 may appear in the list. List may
have up to 13 values. This field's XML reference is not in the NIEM Biometrics domain table. Coded as biom domain by NIST
Appendix G.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
For traditional encoding,
the special character “|” is
allowed as a separator
character
Format
n/a
Constraints
8, 9, 10 11, or 12
Code List: LIP PATHOLOGIES AND PECULIARITIES CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:CheiloscopicImageInformation
NIEM Element: biom:LipPrintPathologiesPeculiaritiesCodeList
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.049_10: Cheilioscopic Image Description - Lip Print Pathologies and Peculiarities Descriptive Text (LPPT)
Description:
This field contains descriptive text regarding the lip print pathologies and peculiarities. This field shall appear if LPPL has a
value of 99.
This field's XML reference is not in the NIEM Biometrics domain table. Coded as biom domain by NIST
Appendix G.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:CheiloscopicImageInformation
NIEM Element: biom:LipPrintPathologiesPeculiaritiesText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
543
Type-10: Photographic Body Part Imagery (including Face and
10.049_11: Cheilioscopic Image Description - Lip Print Surface List (LPSL)
Description:
Multiple codes may be selected from Lip Print Surface codes, since a lip print may be on multiple surfaces. An exemplar of a
lip print may be made on a standard surface, such as a glass photographic slide mount. If a Type-code other than 1 is
selected, then lip print surface descriptive text / LPST shall be entered. If Type-code 1 is chosen, then no other values shall be
entered in the list.
List may have up to 3 values. If Typecode 1 is chosen, no other values are allowed. This field's XML
reference is not in the NIEM Biometrics domain table. Coded as biom domain by NIST Appendix G.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
For traditional encoding,
the special character “|” is
allowed as a separator
character
Format
n/a
Constraints
Code List: LIP PRINT SURFACE CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:CheiloscopicImageInformation
NIEM Element: biom:LipPrintSurfaceCodeList
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.049_12: Cheilioscopic Image Description - Lip Print Surface Descriptive Text (LPST)
Description:
This field describes the surface on which the lip print occurs. This field contains descriptive text for the lip print surface. It
should be entered if LPSL has a value other than 1.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:CheiloscopicImageInformation
NIEM Element: biom:LipPrintSurfaceText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
544
Type-10: Photographic Body Part Imagery (including Face and
10.049_13: Cheilioscopic Image Description - Lip Print Medium Code (LPMC)
Description:
This field shall be selected from Lip Print Medium Codes. If Type-code 9 is selected, then lip print medium descriptive text /
LPMT shall be entered.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
Code List: LIP PRINT MEDIUM CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:CheiloscopicImageInformation
NIEM Element: biom:LipPrintMediumCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.049_14: Cheilioscopic Image Description - Lip Print Medium Descriptive Text (LPMT)
Description:
This field describes the lip print medium. If LPMC has a value of 9, then it shall be entered.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:CheiloscopicImageInformation
NIEM Element: biom:LipPrintMediumText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
545
Type-10: Photographic Body Part Imagery (including Face and
10.049_15: Cheilioscopic Image Description - Facial Hair Descriptive Text (FHDT)
Description:
This field is used to describe the presence, pattern, distribution and density of the follicles if they are visible in the image.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:CheiloscopicImageInformation
NIEM Element: nc:PersonFacialHairText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.049_16: Cheilioscopic Image Description - Lip Print Position and Tension Text (LPDT)
Description:
This information item should describe in general terms the probable, possible or verified relative position of the lips to each
other and the muscle tension and shape of the lip print. There may be considerable variation in lip prints if the lips were pursed
or open or if a print is taken post-mortem.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:CheiloscopicImageInformation
NIEM Element: biom:LipPositionTensionDescriptiveText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
546
Type-10: Photographic Body Part Imagery (including Face and
10.049_17: Cheilioscopic Image Description - Lip Print Additional Descriptive Text (LPAT)
Description:
This field should be used to describe any relevant information that may assist in the analysis of the cheiloscopic image.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:CheiloscopicImageInformation
NIEM Element: biom:LipPrintDescriptiveText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.049_18: Cheilioscopic Image Description - Lip Print Comparison Descriptive Text (LPCT)
Description:
This field may be used by an analyst to note the results of a comparison against another image. If this information item is
present, then Field 10.039: Type-10 reference number / T10 shall be present in the record to indicate the image against which
the image in this instance of the Record Type-10 is compared.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:CheiloscopicImageInformation
NIEM Element: biom:LipPrintCharacterizationText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
547
Type-10: Photographic Body Part Imagery (including Face and
10.050: Dental Visual Image Data Information (VID)
Description:
This field is used to highlight distinctive features in an image. This field shall only be used if Field 10.003: Image type / IMT
has a value of EXTRAORAL or INTRAORAL. When distinct features are outlined for comparison on an exemplar and a latent
image, then Field 10.039: Type-10 reference number / T10 should be used to link the two Type-10 records.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage
NIEM Element: biom:DentalVisualImageDataInformation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.050_1: Dental Visual Image Data Information - Visual Image View Code (VIVC)
Description:
It is an entry selected from the “View Code” column of Dental Image codes.
Field Minimum
3
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
n/a
Format
n/a
Constraints
Code List: DENTAL IMAGE CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:DentalVisualImageDataInformation
NIEM Element: biom:DentalVisualImageCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
548
Type-10: Photographic Body Part Imagery (including Face and
10.050_2: Dental Visual Image Data Information - Visual Image Additional Descriptive Text (VIDT)
Description:
This field contains descriptive text on the Dental Visual Image.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:DentalVisualImageDataInformation
NIEM Element: biom:DentalVisualImageDescriptiveText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.050_3: Dental Visual Image Data Information - Visual Image Comparison Descriptive Text (VICD)
Description:
This field is normally used by an analyst to note the results of a comparison against another image. If this information item is
present, then Field 10.039: Type-10 reference number / T10 shall be present in the record to indicate the image against which
the image in this instance of the Record Type-10 is compared.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:DentalVisualImageDataInformation
NIEM Element: biom:DentalVisualImageComparisonDescriptiveText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
549
Type-10: Photographic Body Part Imagery (including Face and
10.051: Ruler or Scale Presence (RSP)
Description:
This set of fields allows the user to state whether a ruler or other known scale is present in the image.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage
NIEM Element: biom:RulerScalePresenceInformation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.051_1: Ruler or Scale Presence - Ruler or Scale Units (RSU)
Description:
This field indicates the units of measurement visible on the ruler or measurement scale. Valid entries are: IN = inches; MM =
millimeters; BOTH = both inches and millimeters
Field Minimum
2
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
n/a
Format
n/a
Constraints
RSU = IN, MM, or BOTH
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:RulerScalePresenceInformation
NIEM Element: biom:RulerScaleUnitCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
550
Type-10: Photographic Body Part Imagery (including Face and
10.051_2: Ruler or Scale Presence - Ruler or Scale Make (RSM)
Description:
This field lists the maker of the ruler or scale (if known).
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:RulerScalePresenceInformation
NIEM Element: biom:RulerScaleMakeText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
10.051_3: Ruler or Scale Presence - Ruler or Scale Model (RSO)
Description:
This field lists the model of the ruler or scale (if known). For patterned injuries, the ABFO # 2 Reference Scale (commonly
called the ABFO # 2 ruler) shall be used.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:RulerScalePresenceInformation
NIEM Element: biom:RulerScaleModelText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
551
Type-10: Photographic Body Part Imagery (including Face and
10.902: Annotated Information (ANN)
Description:
This is an optional field, listing the operations performed on the original source in order to prepare it for inclusion in a biometric
record type.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord
NIEM Element: itl:PackagePhotographicBodyPartImageRecord
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.902_0: Annotated Information - Subfields: Repeating sets of information items (ANN_0)
Description:
This is an optional field, listing the operations performed on the original source in order to prepare it for inclusion in a biometric
record type.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
Unlimited
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord
NIEM Element: itl:PackagePhotographicBodyPartImageRecord
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
552
Type-10: Photographic Body Part Imagery (including Face and
10.902_1: Annotated Information - Greenwich Mean Time (GMT)
Description:
This information item is the Greenwich Mean Time (GMT) when the processing occured. The data is formatted as
YYYYMMDDhhmmssZ, where the Z is indicates the zone description of 0 hours. This time is independent of the actual time
zone where the time and date is recorded.
Field Minimum
Dependent on encoding
Field Maximum
Dependent on encoding
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
YYYYMMDDHHMMSSZ for Traditional Encoding
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessUTCDate/nc:ZuluDateTime
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.902_2: Annotated Information - Processing Algorithm Name / Version (NAV)
Description:
This information item shall contain text identifying the name and version of the processing algorithm, application, procedure, or
workstation
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessName
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
553
Type-10: Photographic Body Part Imagery (including Face and
10.902_3: Annotated Information - Algorithm Owner (OWN)
Description:
This information item shall contain an unformatted text string of up to 64 characters with the contact information for the
organization that owns the processing algorithm or latent workstation. Where there is no 'algorithm owner,' enter N/A.
Field Minimum
1
Field Maximum
64
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessOwnerText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.902_4: Annotated Information - Process Description (PRO)
Description:
This information item field shall contain text describing a process or procedure applied to the sample in this Type-10 record.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessDescriptionText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
554
Type-10: Photographic Body Part Imagery (including Face and
10.903: Device Unique Identifier (DUI)
Description:
The DUI shall contain a string uniquely identifying the device or source of the data. This field shall be one of the following: a
Host PC MAC address (identified by the first character “M”), a Host PC processor ID (identified by the first character “P”).
since it is available in the Make / Model / Serial Number field.
Field Minimum
13
Field Maximum
16
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
Any
Format
n/a
Constraints
first character = M or P
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.904: Make/Model/Serial Number (MMS)
Description:
The MMS contains the make, model and serial number for the capture device. It shall consist of three information items. Each
information item shall be 1 to 50 characters. Unknown information may be indicated with the value "0." Any or all information
items may indicate that information is unknown with the value “0”.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:ImageCaptureDetail
NIEM Element: biom:CaptureDevice
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
555
Type-10: Photographic Body Part Imagery (including Face and
10.904_1: Make/Model/Serial Number - Make (MAK)
Description:
The name of the manufacturer for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceMakeText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.904_2: Make/Model/Serial Number - Model (MOD)
Description:
The model number for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceModelText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
556
Type-10: Photographic Body Part Imagery (including Face and
10.904_3: Make/Model/Serial Number - Serial Number (SER)
Description:
The serial number for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceSerialNumberText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.992: Biometric Cross Reference Identification (T2C)
Description:
When used, it contains the IDC value of the Type-2 record that contains relevant biographic information and other data
concerning the subject of this instance of the record, who may be different from the subject of the transaction.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
0 < T2C < 99, non-negative
integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord
NIEM Element: biom:Type2CrossReferenceID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
557
Type-10: Photographic Body Part Imagery (including Face and
10.993: Source Agency Name (SAN)
Description:
This is an optional field. It may contain up to 125 Unicode characters. It is the name of the agency referenced in Field xx.004:
Source agency / SRC for record types 9-99.
Field Minimum
1
Field Maximum
125
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:ImageCaptureDetail/biom:CaptureOrganizati
on
NIEM Element: nc:OrganizationName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.995: Associated Context (ASC)
Description:
This optional field refers to one or more Type 21 Records with the same ACN. Type 21 Records contain images that are NOT
used to derive the biometric data in Field 13.999: Latent friction ridge image (DATA) but that may be relevant to the collection
of that data, such as general scenes of the area where a latent print was found.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord
NIEM Element: biom:AssociatedContext
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
558
Type-10: Photographic Body Part Imagery (including Face and
10.995_0: Associated Context - Subfields: Repeating sets of information items (ASC_0)
Description:
This optional field refers to one or more Type 21 Records with the same ACN. Type 21 Records contain images that are NOT
used to derive the biometric data in Field 13.999: Latent friction ridge image (DATA) but that may be relevant to the collection
of that data, such as general scenes of the area where a latent print was found.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
255
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord
NIEM Element: biom:AssociatedContext
XML Min/Max: 1 / 255
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.995_1: Associated Context - Associated Context Number (ACN)
Description:
The first information item for the Associated Context field for a particular Record Type-21. This is mandatory for each Field
xx.995, when the field is used. It contains an index to a particular instance of a Type-21 record in the transaction. This same
index value appears in the appropriate instance of Record Type-21 as Field 21.021: Associated context number (CAN). The
value of the CAN shall be a sequentially assigned a positive integer starting from one and incremented by one, not to exceed
255.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
1 <= ACN <= 255; positive
integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:AssociatedContext
NIEM Element: biom:ContextID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
559
Type-10: Photographic Body Part Imagery (including Face and
10.995_2: Associated Context - Associated Segment Position (ASP)
Description:
The first information item is the associated segment position (ASP). This provides a unique index to a segmentation.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
1 <= ASP <= 99; positive
integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:AssociatedContext
NIEM Element: biom:ImageSegmentID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.996: Hash (HAS)
Description:
Optional field xx.996, is designed for use in Record types 10 and above with a Field xx.999 storing the biometric data. It is
comprised of 64 characters representing hexadecimal values. Thus, each character may be a digit from “0” to “9” or a letter “A”
through “F”. See the latest version of the Federal Information Processing Standard 180, Secure Hash Standard for information
on computing SHA-256 hashes. At the time of this standard’s publication, FIPS 180-37 had been published.
Field Minimum
64
Field Maximum
64
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord
NIEM Element: biom:ImageHashValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
560
Type-10: Photographic Body Part Imagery (including Face and
10.997: Source Representation (SOR)
Description:
This optional field refers to a representation in Record Type-20 with the same SRN from which the data in Field 13.999: Latent
friction ridge image (DATA) was derived.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord
NIEM Element: biom:SourceInformation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.997_0: Source Representation (SOR_0)
Description:
This optional field refers to a representation in Record Type-20 with the same SRN from which the data in Field 13.999: Latent
friction ridge image (DATA) was derived.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
255
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord
NIEM Element: biom:SourceInformation
XML Min/Max: 1 / 255
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
561
Type-10: Photographic Body Part Imagery (including Face and
10.997_1: Source Representation - Source Representation Number (SRN)
Description:
This is the first information item and is mandatory for each Field xx.997. It contains an index to a particular instance of a Type20 record in the transaction. This same index value appears in the appropriate instance of Record Type-20 as Field 20.021:
Source representation number (SRN). The value of the SRN shall be a sequentially assigned a positive integer starting from
one and incremented by one, not to exceed 255.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 <= SRN <= 255; positive
integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:SourceInformation
NIEM Element: biom:SourceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.997_2: Source Representation - Reference Segment Position (RSP)
Description:
The first information item is the reference segment position (RSP). This provides a unique index to a segmentation.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
n/a
Format
n/a
Constraints
1 <= RSP <= 99; positive
integer
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:SourceInformation
NIEM Element: biom:ImageSegmentID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
562
Type-10: Photographic Body Part Imagery (including Face and
10.998: Geographic Sample Acquisition Location (GEO)
Description:
This optional field contains the location where the iris sample/original source/context information was acquired – not where it is
stored.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:ImageCaptureDetail
NIEM Element: biom:GeographicSampleAcquisitionLocation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.998_01: Geographic Sample Acquisition Location - Universal Time Entry (UTE)
Description:
The coordinated universal time (UTC) where the biometric sample was collected. This time is independent of the actual time
zone where the time and date is recorded. The date is YYYYMMDDhhmmssZ, where the Z is indicates the zone description of
0 hours.
If sample collection time is unknown, set it to "00000000000000Z."
Field Minimum
Dependent on encoding
Field Maximum
Dependent on encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisition
Location
NIEM Element: biom:CaptureUTCDateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
563
Type-10: Photographic Body Part Imagery (including Face and
10.998_02: Geographic Sample Acquisition Location - Latitude Degree Value (LTD)
Description:
The second information item is latitude degree value (LTD). This is a value that specifies the degree of latitude. The value shall
be between -90 (inclusive) and +90 (inclusive). The degrees may be expressed as an integer (without a decimal) or a real
number including decimals. If decimals are present, then minutes and seconds shall be empty. Examples: Buenos Aires,
Argentina: -34 (with minutes LTM = 36) NIST, Gaithersburg, Maryland: 39.137627 (no LTM or LTS)
However, latitude
degree value / LTD and longitude degree value / LGD are co-conditional, so they shall both be present if either is present.
Field Minimum
1
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal,Minus Sign,Plus
Sign
Format
n/a
Constraints
-90 < LTD < 90
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisition
Location/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLatitude
NIEM Element: nc:LatitudeDegreeValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.998_03: Geographic Sample Acquisition Location - Latitude Minute Value (LTM)
Description:
This information item is latitude minute value (LTM). This is a value that specifies a minute of a degree. The value shall be
between 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall be empty. Thus, the allowed special character is a
period. The minute value can be empty, even if the degree value is an integer. LTM and LGM are co-conditional, so they shall
both be present if either is present.
Further, “minutes” values LTM and LGM can only be present if their corresponding
“degrees” values are present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal,Minus Sign,Plus
Sign
Format
n/a
Constraints
0 <= LTM < 60
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisition
Location/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLatitude
NIEM Element: nc:LatitudeMinuteValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
564
Type-10: Photographic Body Part Imagery (including Face and
10.998_04: Geographic Sample Acquisition Location - Latitude Second Value (LTS)
Description:
The fourth information item is the latitude second value (LTS). This is a value that specifies a second of a minute. The integer
shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer.
Also, “seconds”
values LTS and LGS can only be present if their corresponding “minutes” value is present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 <= LTS < 60
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisition
Location/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLatitude
NIEM Element: nc:LatitudeSecondValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.998_05: Geographic Sample Acquisition Location - Longitude Degree Value (LGD)
Description:
The fifth information item is the longitude degree value (LGD). It is a value that specifies the degree of a longitude. The value
shall be between -180 (inclusive) and +180 (inclusive). If LTD is present, then LGD shall be present. The degrees may be
expressed as whole numbers (without a decimal) or real numbers including decimals. If decimals are present, then minutes
and seconds are empty. Examples: Buenos Aires, Argentina: -58 (with minutes LGM = 22), NIST, Gaithersburg, Maryland: 77.216032 (no LGM or LGS)
However, latitude degree value / LTD and longitude degree value / LGD are co-conditional, so
they shall both be present if either is present.
Field Minimum
1
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal,Minus Sign,Plus
Sign
Format
n/a
Constraints
-180 =< LGD =< 180
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisition
Location/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLongitude
NIEM Element: nc:LongitudeDegreeValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
565
Type-10: Photographic Body Part Imagery (including Face and
10.998_06: Geographic Sample Acquisition Location - Longitude Minute Value (LGM)
Description:
The sixth information item is the longitude minute value (LGM). It is a value that specifies a minute of a degree. The value shall
be from 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall not appear. The minute value is empty, even if the
degree value is an integer. If LTM is present, then LGM shall be present.
Further, “minutes” values LTM and LGM can only
be present if their corresponding “degrees” values are present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
1 <= LGM < 60
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisition
Location/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLongitude
NIEM Element: nc:LongitudeMinuteValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.998_07: Geographic Sample Acquisition Location - Longitude Second Value (LGS)
Description:
The seventh information item is the longitude second value (LGS). This is a value that specifies a second of a minute. The
integer shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer. If LTS is
present, then LGS shall be present.
Also, “seconds” values LTS and LGS can only be present if their corresponding
“minutes” value is present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 <= LGS < 60
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisition
Location/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLongitude
NIEM Element: nc:LongitudeSecondValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
566
Type-10: Photographic Body Part Imagery (including Face and
10.998_08: Geographic Sample Acquisition Location - Elevation (ELE)
Description:
The eighth information item is elevation (ELE). It is expressed in meters. It is a numeric value. It is between -422 meters (Dead
Sea) and 8848 meters (Mount Everest). Allowed special characters are the negative sign and the period.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Minus Sign,Period
Format
n/a
Constraints
-422.000 < ELE < 8848.000;
real number
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisition
Location/nc:Location3DGeospatialCoordinate
NIEM Element: nc:LocationElevation/nc:MeasureDecimalValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.998_09: Geographic Sample Acquisition Location - Geodetic Datum Code (GDC)
Description:
The ninth information item is the geodetic datum code (GDC11). It is an alphanumeric value of 3 to 6 characters in length. This
information item is used to indicate which coordinate system was used to represent the values in information items 2 through
7. If no entry is made in this information item, then the basis for the values entered in the first eight information items shall be
WGS84, the code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values. If no entry is
made in this information item, then the basis for the values entered in the first eight information items shall be WGS84, the
code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values.
Field Minimum
3
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
see Look Up Codes
Code List: GEOGRAPHIC COORDINATE DATUM CODE
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:FaceImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisition
Location/nc:Location3DGeospatialCoordinate
NIEM Element: biom:GeodeticDatumCoordinateSystemCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
567
Type-10: Photographic Body Part Imagery (including Face and
10.998_10: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Zone (GCM)
Description:
It is an alphanumeric value of 2 to 3 characters. This is a one or two digit UTM zone number followed by the 8 degree
latitudinal band designator (which is a single letter).
Field Minimum
2
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
One or two integers
followed by a single letter
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:ImageCaptureDetail/biom:GeographicSampl
eAcquisitionLocation
NIEM Element: nc:LocationUTMCoordinateValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.998_11: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Easting (GCE)
Description:
The eleventh information item is the geographic coordinate universal transverse Mercator easting (GCE). It is an integer of 1 to
6 digits.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:ImageCaptureDetail/biom:GeographicSampl
eAcquisitionLocation
NIEM Element: biom:CaptureLocation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
568
Type-10: Photographic Body Part Imagery (including Face and
10.998_12: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Northing (GCN)
Description:
The twelfth information item is the geographic coordinate universal transverse Mercator northing (GCN). It is an integer of 1 to
8 digits.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:ImageCaptureDetail/biom:GeographicSampl
eAcquisitionLocation
NIEM Element: biom:CaptureLocation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.998_13: Geographic Sample Acquisition Location - Geographic Reference Text (GRT)
Description:
It is a free form text describing a street address or other physical location (such as ‘Corner of Washington and Madison,
Geneva, NY’).
Field Minimum
1
Field Maximum
150
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:ImageCaptureDetail/biom:GeographicSampl
eAcquisitionLocation
NIEM Element: nc:LocationDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
569
Type-10: Photographic Body Part Imagery (including Face and
10.998_14: Geographic Sample Acquisition Location - Geographic Coordinate Other System Identifier (OSI)
Description:
A fourteenth optional information item geographic coordinate other system identifier (OSI) allows for other coordinate systems.
This information items specifies the system identifier. It is up to 10 characters in length. Examples are: • MGRS (Militar Grid
Reference System), • USNG (United States National Grid), • GARS (Global Area Reference System), • GEOREF (World
Geographic Reference), • LANDMARK landmark (e.g. hydant) and position relative to the landmark.
Field Minimum
1
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:ImageCaptureDetail/biom:GeographicSampl
eAcquisitionLocation
NIEM Element: biom:GeographicLocationSystemName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
10.998_15: Geographic Sample Acquisition Location - Geographic Coordinate Other System Value (OCV)
Description:
A fifteenth optional information item, is the geographic coordinate other system value (OCV). It shall only be present if OSI is
present in the record. It can be up to 126 characters in length. If OSI is LANDMARK, OCV is free text and may be up to 126
characters. For details on the formatting of OCV for the other coordinate systems shown in OSI as examples, see http://earthinfo.nga.mil/GandG/coordsys/grids/referencesys.html .
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent:
itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage/biom:ImageCaptureDetail/biom:GeographicSampl
eAcquisitionLocation
NIEM Element: biom:GeographicLocationText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
570
Type-10: Photographic Body Part Imagery (including Face and
10.999: Body Part Image (DATA)
Description:
This mandatory field contains the image. See Section 7.2 of ANSI/NIST ITL 1-2011 for details.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
B
Special Characters
None, niemxs:base64Binary
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011: (Update 2015)
Status: Active
XML Parent: itl:PackagePhotographicBodyPartImageRecord/biom:PhysicalFeatureImage
NIEM Element: nc:Base64BinaryObject
XML Min/Max: 0 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
11.001: Record Header (LEN)
Description:
The record header appears as the first field (xx.001) in each Record Type. It contains information particular to the encoding
format chosen, in order to enable proper reading of the record. In Traditional encoding, this field contains the record length in
bytes (including all information separators). In NIEM-conformant XML encoding, this field contains the RecordCategoryCode,
which is the numeric representation of the Record Type.
Field Minimum
T = 4; X = 1
Field Maximum
T = 8; X = 2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
571
Type-11: Forensic and Investigatory Voice Data
11.002: Information Designation Character (IDC)
Description:
Contains the IDC assigned to this Type-11 record as listed in the information item IDC for this record.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ IDC ≤ 99
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord
NIEM Element: biom:ImageReferenceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.003: Audio Object Descriptor Code (AOD)
Description:
This mandatory field shall be a numeric entry selected from the attribute code column of Table 89 Audio Object Descriptor.
Only one value is allowed and indicates the type of audio object containing the voice recording which is the focus of this Type11 record. Attribute code 0 indicates that the audio object of this record is a digital voice data file in the Field 11.999: Voice
record data / DATA. Attribute code 1 indicates that the audio object is a digital voice data file at the location specified in Field
11.994: External file reference / EFR. Attribute codes 2-4 indicate that the audio object is a physical media object at a location
described in Field 11.994. If the Type-11 record contains only metadata (such as in a response to a voice recording
submission), attribute code 5 shall be selected. Note that the difference between Attribute code 1 and Attribute code 2 is that 1
indicates a file that is accessible without the physical media object itself – such as being stored at a URL. Code 2 indicates that
something that is a physical object like a digital telephone answering machine contains the digital file. Therefore, the physical
media object is required to retrieve and analyze the data.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
T = integer, X =
AudioObjectDescriptorCode
Type
Special Characters
None
Format
n/a
Constraints
0 ≤ AOD ≤ 5
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:AudioObjectDescriptorCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
572
Type-11: Forensic and Investigatory Voice Data
11.004: Source Agency (SRC)
Description:
The SRC is a code for a particular agency that is assigned by the implementation domain (such as NORAM, which is
maintained by the FBI). It is often not the common name of the organization. This mandatory field denotes the agency that
prepared this record. It is not necessarily the agency that is transmitting this transaction.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:BiometricCapture/biom:CaptureOrganization
NIEM Element: nc:OrganizationIdentification/nc:IdentificationID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.005: Voice Recording Source Organization (VRSO)
Description:
This is an optional field and shall contain information about the person, group, site or agency that created the voice recording
pointed to or included in this record. In the case of files created from previous recordings, this is not necessarily the source of
the original transduction of the acoustic vocalizations from the person to whom the Type- 11 record pertains.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:RecordingSettingDetail
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
573
Type-11: Forensic and Investigatory Voice Data
11.005_1: Voice Recording Source Organization - Source Organization Type Code (STC)
Description:
The first information item is the source organization type code / STC. It is mandatory if this field is used. There may be no more
than one occurrence of this item. A single character describing the site or agency that created the voice recording: U =
Unknown, P = Private individual, I = Industry/Commercial, G = Government or O = Other.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
U, P, I, G or O
Code List: SOURCE ORGANIZATION TYPE CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:RecordingSettingDetail
NIEM Element: biom:RecordingSourceCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.005_2: Voice Recording Source Organization - Source Organization Name (SON)
Description:
The second information item is the source organization name / SON. It is optional and shall be the name of the group,
organization or agency that created the voice recording.
Field Minimum
1
Field Maximum
400
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:RecordingSettingDetail
NIEM Element: biom:SourceOrganizationName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
574
Type-11: Forensic and Investigatory Voice Data
11.005_3: Voice Recording Source Organization - Point Of Contact (POC)
Description:
The third information item is the point of contact / POC. It states who composed the voice recording. This is an optional
information item that could include the name, telephone number and e-mail address of the person or persons responsible for
the creation of the voice recording.
Field Minimum
1
Field Maximum
200
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:RecordingSettingDetail
NIEM Element: nc:OrganizationPrimaryContactInformation/nc:ContactInformationDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.005_4: Voice Recording Source Organization - Source Organization Country Code (CSC)
Description:
The fourth information item the country code of the sending country / CSC. It is optional. This is the code of where the voice
recording was created – not necessarily the nation of the agency entered in Field 11.993: Source agency name / SAN. All
three formats specified in ISO-3166-1 are allowed (Alpha2, Alpha3 and Numeric). A country code is either 2 or 3 characters
long. Note that if Field 1.018: Geographic name set / GNS is set to GENC, the entry in this information item is from GENC.
Field Minimum
2
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
Values from ISO-3166-1 or
GENC.
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:RecordingSettingDetail
NIEM Element: biom:RecordingSourceCountry
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
575
Type-11: Forensic and Investigatory Voice Data
11.006: Voice Recording Content Descriptor (VRC)
Description:
This field is optional and shall describe the contents of the voice recording.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:RecordingContentDescriptor
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.006_1: Voice Recording Content Descriptor - Assigned Voice Indicator (AVI)
Description:
Assigned voice indicator / AVI - Indicates if the voice recording sample was obtained from a known subject. This is mandatory
field if this field is used. A = the subject of this record is 'assigned' an identity (whether or not there is biographical information
associated with the individual.) Q = this record contains a voice sample of a 'questioned' identity (such as a sample to be
compared against a database for identification)
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
AVI = A, N or Q
Code List: VOICE RECORDING CONTENT INDICATOR CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:RecordingContentDescriptor
NIEM Element: biom:RecordingAssignedVoiceCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
576
Type-11: Forensic and Investigatory Voice Data
11.006_2: Voice Recording Content Descriptor - Speaker Plurality Code (SPC)
Description:
Speaker plurality code / SPC is an optional field which indicates the plurality of speakers represented on voice recording. M =
multiple speakers; S = single speaker
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
SPC = M or S
Code List: SPEAKER PLURALITY CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:RecordingContentDescriptor
NIEM Element: biom:SpeakerPluralityCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.006_3: Voice Recording Content Descriptor - Comment (COM)
Description:
Describes methods by which the plurality and nationality of the speakers was determined, along with any supporting text. This
is an optional field.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:RecordingContentDescriptor
NIEM Element: biom:RecordingContentCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
577
Type-11: Forensic and Investigatory Voice Data
11.007: Audio Recording Device (AREC)
Description:
This field is optional and shall indicate information about the recording equipment that created the voice recording contained in
or pointed to by this record. As recordings or data files may be transcoded from previously recorded or broadcast content, this
equipment may or may not be the equipment used to record the original acoustic vocalization of the person to whom the Type11 record pertains.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:AudioSourceRecorder
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.007_1: Audio Recording Device - Recording Device Descriptive Text (RDD)
Description:
The first information item is the recording device descriptive text / RDD. It is an optional text field escribing the recording device
that created the voice recording.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:AudioSourceRecorder
NIEM Element: biom:DeviceDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
578
Type-11: Forensic and Investigatory Voice Data
11.007_2: Audio Recording Device - Recording Device Make (MAK)
Description:
Describes make of the recording device that created the voice recording.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:AudioSourceRecorder
NIEM Element: biom:DeviceMakeText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.007_3: Audio Recording Device - Recording Device Model (MOD)
Description:
Contains the make, model and serial number, respectively, for the recording device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:AudioSourceRecorder
NIEM Element: biom:DeviceModelText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
579
Type-11: Forensic and Investigatory Voice Data
11.007_4: Audio Recording Device - Recording Device Serial Number (SER)
Description:
Recording device serial number.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:AudioSourceRecorder
NIEM Element: biom:DeviceSerialNumberText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.008: Acquisition Source (AQS)
Description:
Specifies and describes the acquisition source. Mandatory field if AOD does not equal 5. It shall not appear if AOD = 5.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:SourceAcquisition
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
580
Type-11: Forensic and Investigatory Voice Data
11.008_1: Acquisition Source - Acquisition Source Code (AQC)
Description:
It is a mandatory integer that specifies the source from which the voice in the identified segments was received. It shall be a
numeric entry selected from the 'attribute code' from Table 121 Acquisition Source from ANSI/NIST-ITL update 2015.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
Value from Table 121
Acquisition Source from
ANSI/NIST-ITL update 2015.
Code List: ACQUISITION SOURCE CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SourceAcquisition
NIEM Element: biom:AcquisitionSourceCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.008_2: Acquisition Source - Analog To Digital Conversion Description (A2D)
Description:
This field is optional if an analog to digital conversion occurred. Used to enter the make, model and serial number of the analog
to digital conversion equipment used, if known. This field should also address parameters used, such as the sampling rate, if
known.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SourceAcquisition
NIEM Element: biom:AcquisitionDigitalConversionDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
581
Type-11: Forensic and Investigatory Voice Data
11.008_3: Acquisition Source - Radio Transmission Format Description (FDN)
Description:
Radio transmission format description / FDN - Mandatory if the AQT is 23 or 24 otherwise optional.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SourceAcquisition
NIEM Element: biom:AcquisitionRadioTransmissionFormatDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.008_4: Acquisition Source - Acquisition Special Characteristics (AQSC)
Description:
Describes any specific conditions not mentioned in the table.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SourceAcquisition
NIEM Element: biom:AcquisitionSpecialCharacteristicsText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
582
Type-11: Forensic and Investigatory Voice Data
11.009: Record Creation Date - Record Creation Date (RCD)
Description:
This mandatory field shall contain the date and time of creation of this Type-11 record. This date will generally be different from
the voice recording creation date and may be different from the date at which the acoustic vocalization originally occurred.
Field Minimum
Dependent on Encoding
Field Maximum
Dependent on Encoding
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
Dependent on Encoding
Constraints
YYYYMMDDhhmm
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:RecordCreationDate/nc:DateTime
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.010: Total Recording Duration - Voice Recording Creation Date (VRD)
Description:
This optional field shall contain the date and time of creation of the voice recording contained in this Type-11 record (not the
original source recording contained in Record Type-20, if it is different from that). If pre-recorded or transcoded materials were
used, this date may be different from the date at which the acoustic vocalization originally occurred.
Field Minimum
Dependent on Encoding
Field Maximum
Dependent on Encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
Dependent on Encoding
Constraints
YYYYMMDDhhmm
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:BiometricCapture
NIEM Element: biom:CaptureDate/nc:DateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
583
Type-11: Forensic and Investigatory Voice Data
11.011: Voice Recording Date - Total Recording Duration (TRD)
Description:
This field is optional and gives the total length of the voice recording time for this Type-11 record. The second and third items
of this field only apply to digital audio objects, as indicated by a value of 0, 1 or 2 in AOD. At least one of the three information
items must be entered if this field is used.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:RecordingDurationDetail
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.011_1: Voice Recording Date - Voice Recording Time (TIM)
Description:
This optional field gives the total time of the voice recording in microseconds. The size of this item is limited to 11 digits,
limiting the total time duration of the signal to 99,999 seconds, which is approximately 28 hours.
Field Minimum
1
Field Maximum
11
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
Contains integers with no
commas or periods
Format
n/a
Constraints
1 ≤ TIM ≤ 99999999999
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:RecordingDurationDetail
NIEM Element: biom:RecordingDuration
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
584
Type-11: Forensic and Investigatory Voice Data
11.011_2: Voice Recording Date - Compressed Bytes (CBY)
Description:
The total number of compressed bytes in the digital voice data file. This information item is optional and applies only to digital
voice recordings stored as voice data files. The size of this item is limited to 14 digits, limiting the total size of the voice data file
to 99 terabytes.
Field Minimum
1
Field Maximum
14
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
Contains integers with no
commas or periods
Format
n/a
Constraints
1 ≤ CBY ≤ 99999999999999
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:RecordingDurationDetail
NIEM Element: biom:RecordingCompressedBytesQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.011_3: Voice Recording Date - Total Digital Samples (TSM)
Description:
The number of digital samples in the voice data file after any decompression of the compressed signal. This optional
information item applies only to digital voice recordings stored as voice data files. The size of this item is limited to 14 digits.
Field Minimum
1
Field Maximum
14
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
Contains integers with no
commas or periods
Format
n/a
Constraints
1 ≤ TSM ≤ 99999999999999
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:RecordingDurationDetail
NIEM Element: biom:RecordingSampleQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
585
Type-11: Forensic and Investigatory Voice Data
11.012: Physical Media Object (PMO)
Description:
This field is optional and identifies the characteristics of the physical media containing the voice recording. There can be only
one physical media object per Type-11 record, but multiple Type-11 records can point to the same physical media object. This
field only applies if AOD has an attribute code of 2, 3 or 4. The location of the physical media object is given in EFR.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:PhysicalMediaObject
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.012_1: Physical Media Object - Media Type Description (MTD)
Description:
It is mandatory if this field is used and contains text describing the general type of media (e.g., analog cassette tape, reel-toreel tape, CD, DVD, phonograph record) upon which the voice recording is stored. If an analog media is used for storage, and
AQC of Field 11.008: Acquisition source / AQS is 14, then a description of the digital to analog procedure should be noted in
Field 11.902: Annotation information / ANN and the reasons for such a conversion noted in COM of this field.
Field Minimum
1
Field Maximum
300
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:PhysicalMediaObject
NIEM Element: biom:MediaCategoryText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
586
Type-11: Forensic and Investigatory Voice Data
11.012_2: Physical Media Object - Recording Speed (RSP)
Description:
This field is optional and gives a numerical value to the speed at which the physical media object must be played to reproduce
the voice signal content.
Field Minimum
1
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
numbers, with decimals
allowed
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:PhysicalMediaObject
NIEM Element: biom:RecordingSpeedRate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.012_3: Physical Media Object - Recording Speed Measurement Units Description Text (RSU)
Description:
The third information item is recording speed measurement units description text / RSU. Mandatory if the second information
item, RSP, is entered and contains text to indicate the units of measure to which RSP refers (such as Rotations per minute).
Otherwise, it is not entered.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:PhysicalMediaObject
NIEM Element: biom:RecordingSpeedUnitText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
587
Type-11: Forensic and Investigatory Voice Data
11.012_4: Physical Media Object - Equalization Description (EQD)
Description:
Optional text field that indicates the equalization that should be applied for faithful rendering of the voice recording on the
physical media object.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:PhysicalMediaObject
NIEM Element: biom:AudioEqualizationText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.012_5: Physical Media Object - Track Count (TRC)
Description:
Gives the number of tracks on the physical media object.
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ TRC ≤ 9999
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:PhysicalMediaObject
NIEM Element: biom:AudioTrackQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
588
Type-11: Forensic and Investigatory Voice Data
11.012_6: Physical Media Object - Speaker Track Number (STK)
Description:
Indicate which tracks carry the voices of the speaker(s). A value of 0 or no entry for this information item indicates that all
tracks contain voice data for the speaker(s). (list may have less than or equal to TRC elements)
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
9999
Character Types
NS
Special Characters
List of up to TRC elements.
For Traditional encoding,
the separator character “|”
is used between elements.
This is not applicable to
XML encoding.
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:PhysicalMediaObject
NIEM Element: biom:SpeakerTrackList
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.012_7: Physical Media Object - Comment (COM)
Description:
This optional field allows for additional comments describing the physical media object.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:PhysicalMediaObject
NIEM Element: biom:MediaCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
589
Type-11: Forensic and Investigatory Voice Data
11.013: Container (CONT)
Description:
This conditional field, which need not appear in the record, contains information about the container format that encapsulates
the audio data of the electronic file used to carry the voice data in the digital recording. This field is not used if the voice
recording is stored on a physical media object as an analog signal – so it should only appear if Audio object descriptor code
/AOD is set to 0, 1 or 2. If present, this field overrides Field 11.014: Codec / CDC. There cannot be multiple container formats
specified within a single Type-11 record. The container format shall be entered as the appropriate integer code from Table 90
Audio Visual Container Codes.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:DigitalMediaContainer
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.013_1: Container - Container Code (CONC)
Description:
The first information item, which is mandatory, is container code / CONC. Information about the container format that
encapsulates the audio data of the electronic file used to carry the voice data in the digital recording. A container code of Other
(CONC = 2) indicates that the container is given neither in Table 90 Audio Visual Container Codes in ANSI/NIST-ITL update
2015 nor in the external container table and must be specified. If CONC = 2, the Field 11.051: Comment / COM shall be used
to describe the container.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
Value from Table 90 Audio
Visual Container Codes in
ANSI/NIST-ITL update 2015.
Code List: CONTAINER CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:DigitalMediaContainer
NIEM Element: biom:DigitalMediaContainerFormatCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
590
Type-11: Forensic and Investigatory Voice Data
11.013_2: Container - External Container Reference Code (ECON)
Description:
Contains the external container reference code. Only appears if CONC = 1.
Field Minimum
1
Field Maximum
80
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Code List: Code List Here - http://biometrics.nist.gov/cs_links/standard/ansi_2012/Codec.xlsx - Includes the fields
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:DigitalMediaContainer
NIEM Element: biom:DigitalMediaContainerExternalReferenceCodeText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.013_3: Container - Comment (COM)
Description:
The third information item is comments / COM. It is an optional, unrestricted text string. However, it is required if CONC = 2. It
can contain additional information about the container or additional instructions for reconstruction of audio output from the
stored digital data. Container parameters shall be specified in this information item when required for unambiguous decoding.
This item should include a description of any noise reduction processing or equalization that must be applied to faithfully
render the voice recording.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:DigitalMediaContainer
NIEM Element: biom:AudioCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
591
Type-11: Forensic and Investigatory Voice Data
11.014: Codec (CDC)
Description:
Gives information about the codec used to encode the voice and audio data in the digital recording. This optional field appears
only when AOD is set to 0, 1 or 2. This field is not used if the voice recording is stored on a physical media object as an analog
signal.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:CodecDetails
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.014_1: Codec - Codec Code (CODC)
Description:
The first information item is the codec code / CODC. It is mandatory if this field is used and indicates the single codec type
used for all audio segments in the record. If the codec code is identified as Other (CODC = 2), the final information item
(comments / COM) shall be used to describe the codec. If other Codecs are used (reference here http://www.nist.gov/itl/iad/ig/ansi_standard.cfm) then use codec 1.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
Value from Table 91 Codec
Type Codes in ANSI/NISTITL update 2015.
Code List: CODEC TYPE CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:CodecDetails
NIEM Element: biom:CodecCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
592
Type-11: Forensic and Investigatory Voice Data
11.014_2: Codec - Sampling Rate Number (SRTN)
Description:
Indicates the number of digital samples per second that represent a second of analog voice data upon conversion to an
acoustic signal. The value of 0 shall only be used to indicate unknown or variable sampling rate. The sampling rate is
expressed in Hz and must be an integer value. Acceptable values are between 1 and 100,000,000 Hz, but unknown or variable
sampling rates shall be given the value of 0.
Field Minimum
1
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
positive integer, no commas
Format
n/a
Constraints
0 ≤ SRTN ≤ 100000000
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:CodecDetails
NIEM Element: biom:SamplingRate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.014_3: Codec - Bit Depth Count (BITD)
Description:
Indicates the number of bits that are used to represent a single digital sample of voice data. Encoders of unknown or variable
bit depth shall be given the value of 0. Changes to the bit depth should be logged in Field 98.900: Audit log / ALF or Field
11.902: Annotation information / ANN audit logs.
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ BITD ≤ 1024, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:CodecDetails
NIEM Element: biom:RecordingBitDepthValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
593
Type-11: Forensic and Investigatory Voice Data
11.014_4: Codec - Endian Code (ENDC)
Description:
Indicates which byte goes first for digital samples containing two or more bytes. The values for ENDC are 0 = big and 1 = little.
ENDC is optional and ignored for digital samples that do not contain two or more integer multiples of bytes.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
ENDC = 0 or 1
Code List: ENDIAN CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:CodecDetails
NIEM Element: biom:RecordingEndianCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.014_5: Codec - Numeric Format (NFMT)
Description:
Integer and floating point representations.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
Format
n/a
Constraints
NFMT = positive integer
with an optional letters s, b,
or d following it
Code List: NUMERIC FORMAT CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:CodecDetails
NIEM Element: biom:NumericFormatText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
594
Type-11: Forensic and Investigatory Voice Data
11.014_6: Codec - Channel Count (CHC)
Description:
Integer of number of channels of data represented in the digital voice data file. The number of channels must be between 1
and 9999, inclusive.
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ CHC ≤ 9999, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:CodecDetails
NIEM Element: biom:RecordingChannelsQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.014_7: Codec - External Codec Reference Code (ECOD)
Description:
It contains the 'reference code' from the table of codecs available at http://www.nist.gov/itl/iad/ig/ansi_standard.cfm. If the
codec is not listed in the external table, enter the name and description of the codec in COM. It can only appear if CODC = 1.
Field Minimum
1
Field Maximum
80
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Code List: Table of codecs available at http://www.nist.gov/itl/iad/ig/ansi_standard.cfm.
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:CodecDetails
NIEM Element: biom:CodecExternalReferenceCodeText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
595
Type-11: Forensic and Investigatory Voice Data
11.014_8: Codec - Comment (COM)
Description:
The eighth information item is comments / COM. It is an unrestricted textstring. It can contain additional information about the
codec or additionalinstructions for reconstruction of audio output from the stored digital data.Codec parameters shall be
specified in this information item when required for unambiguous decoding. This item should include a description of any noise
reduction processing or equalization that must be applied to faithfully render the voice recording.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:CodecDetails
NIEM Element: biom:CodecCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.021: Redaction (RED)
Description:
It indicates whether the voice recording contains overwritten or erased sections intended to remove, without altering the
relative timings within, or the length of, the segment, semantic content deemed not suitable for transmission or storage. This
field is not to be used to indicate that audio content has been snipped with the alteration of the relative timings in, or length of,
the recording. This field may be present to indicate that redaction has or has not occurred, even if Field 11.022: Redaction
diary / RDD is not present in the record to provide timings and tracks for the affected segments (if redaction did occur).
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:RedactionInformation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
596
Type-11: Forensic and Investigatory Voice Data
11.021_1: Redaction - Redaction Indicator (RDI)
Description:
The first information item is the redaction indicator / RDI. It is mandatory if this field is present in the record. Single character
redaction indicator code. A value of 0 indicates no redaction occurred and a value of 1 indicates that redaction has occurred. A
value of 2 indicates that the organization creating this record is not able to assert or does not assert that redaction has
occurred or not occurred.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
RDI = 0, 1 or 2
Code List: REDACTION INDICATOR CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:RedactionInformation
NIEM Element: biom:ProcessingIndicatorCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.021_2: Redaction - Redaction Authority Organization Name (RDA)
Description:
Contains information about the agency that directed, authorized or performed the redaction. It is an optional field, but can only
be present if RDI = 1.
Field Minimum
1
Field Maximum
300
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:RedactionInformation
NIEM Element: biom:ProcessingAuthorityText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
597
Type-11: Forensic and Investigatory Voice Data
11.021_3: Redaction - Comment (COM)
Description:
It is an optional unrestricted text string that may contain text information about the redactions affecting the stored voice
recording.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:RedactionInformation
NIEM Element: biom:ProcessingCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.022: Redaction Diary (RDD)
Description:
This optional field indicates that redaction has occurred and lists the timings within the voice recording of redacted (overwritten)
audio segments. This field accommodates up to 600,000 redactions. It may be present even if Field 11.021: Redaction / RED
is not in the record. If Field 11.021: Redaction / RED is present in this instance of the record, then this field shall only appear if
the redaction indicator / RDI is set to a value of 1. RDD isn't required to be present when RDI is set to 1 – although it is highly
recommended that it be present.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:RedactionDiaryInformation
XML Min/Max: 0 / 600000
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
598
Type-11: Forensic and Investigatory Voice Data
11.022_0: Redaction Diary - Subfields: Repeating Sets Of Information Items (RDD_0)
Description:
This field contains subfields that locate the segments within the recording of this Type- 11 record that may be of interest for
investigatory purposes but are not focused upon speech.
If Field 11.027 is included in the record, then this field shall be
present only if DII = 1.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
600000
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.022_1: Redaction Diary - Segment Identifier (SID)
Description:
Present in each subfield and uniquely numbers the segment to which the following items in the subfield apply. The number of
redactions is limited to 600,000.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
Contains positive integer,
no commas
Format
n/a
Constraints
1 ≤ SID ≤ 600000
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:RedactionDiaryInformation
NIEM Element: biom:SegmentID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
599
Type-11: Forensic and Investigatory Voice Data
11.022_2: Redaction Diary - Track And Channel Number List (TRK)
Description:
A track and channel number list. It is mandatory if TRC in Field 11.012: Physical media object / PMO or CHC of Field 11.014:
Codec / CDC is greater than one and lists all tracks or channels on the recording to which the segment identifier applies. This
information item may appear even if neither TRC nor CHC are present in the record. No value in this list should be greater than
the value of TRC or CHC, whichever applies.
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
9999
Character Types
NS
Special Characters
For Traditional encoding,
the separator character “|”
is used between elements.
This is not applicable to
XML encoding.
Format
n/a
Constraints
List of non-negative integers
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:RedactionDiaryInformation/biom:TrackChannelList
NIEM Element: biom:TrackID
XML Min/Max: 1 / 9999
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.022_3: Redaction Diary - Relative Start Time (RST)
Description:
It indicates in microseconds the time of the start of the redaction relative to the absolute beginning of the recording. Redactions
from the same track of the audio object identified in Field 11.003: Audio object descriptor code /AOD should not overlap. If the
Type-11 record refers to an analog recording, the method of determining the start time shall be given in the comment item of
this field.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
positive integer
Format
n/a
Constraints
1 ≤ RST
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:RedactionDiaryInformation
NIEM Element: biom:RelativeStartTimeInMSValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
600
Type-11: Forensic and Investigatory Voice Data
11.022_4: Redaction Diary - Relative End Time (RET)
Description:
It indicates in microseconds the time of the end of the redaction relative to the absolute beginning of the recording. It is a
mandatory integer for the redaction identified by SID within each subfield.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
positive integer
Format
n/a
Constraints
RET > RST
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:RedactionDiaryInformation
NIEM Element: biom:RelativeEndTimeInMSValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.022_5: Redaction Diary - Comment (COM)
Description:
Contains an unrestricted text string that allows for comments of any type to be made on a segment.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:RedactionDiaryInformation
NIEM Element: biom:DiaryCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
601
Type-11: Forensic and Investigatory Voice Data
11.023: Discontinuities (DIS)
Description:
This field is optional and indicates by its presence that the voice recording referenced in this Type-11 record has had segments
removed or that signals are not present for another reason. This field is used to indicate post-recording removal (cutting) of a
signal or non-presence of a useful signal, for any reason, from the original recording of the acoustic vocalizations in a way that
disrupts time references.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:DiscontinuityInformation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.023_1: Discontinuities - Discontinuity Indicator (DCI)
Description:
Code that indicates whether the voice recording contains temporal discontinuities. A value of 0 indicates that there are no
discontinuous signals on the recording and a value of 1 indicates that there are discontinuities. A value of 2 indicates that the
organization creating this record is not able to assert or does not assert that there are or are not discontinuities in the recording.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
non-negative integer
Format
n/a
Constraints
SGI = 0 , 1 or 2
Code List: DISCONTINUITY INDICATOR CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:DiscontinuityInformation
NIEM Element: biom:ProcessingIndicatorCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
602
Type-11: Forensic and Investigatory Voice Data
11.023_2: Discontinuities - Cutting Authority Organization Name (CTA)
Description:
Contains information about the agency that performed a post-processing cutting upon the original recording (removing signal
content). Agencies undertaking postprocessing cutting activities should log their actions in Field 98.900: Audit log / ALF and/or
Field 11.902: Annotation information / ANN of this record. Item shall only appear if DCI = 1.
Field Minimum
1
Field Maximum
300
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:DiscontinuityInformation
NIEM Element: biom:ProcessingAuthorityText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.023_3: Discontinuities - Comments (COM)
Description:
Optional unrestricted text string that may contain text information about the snip activities affecting the voice recording.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:DiscontinuityInformation
NIEM Element: biom:ProcessingCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
603
Type-11: Forensic and Investigatory Voice Data
11.024: Discontinuities Diary - Discontinuities Diary (DCD)
Description:
This optional field allows the documentation of discontinuities in the signal. There may be up to 600,000 segments, each
registered in an individual subfield. If there are no discontinuities (DCI = 0 in Field 11.023: Discontinuities / DIS), then all of the
data in the voice recording shall be considered as being in toto and this field shall not be present in this instance of the record.
This field may be present even if Field 11.023: Discontinuities / DIS is not present in the record. This field need not be present
if Field 11.023: Discontinuities / DIS is present in the record and DCI = 1, but it is highly recommended in such a case that this
field be present. A very practical use of DCD is when an original recording is stored in a Type-20 record and segments relating
to a single speaker are combined together and conveyed in a Type-11 record. DCD then indicates the locations of the temporal
discontinuities within the resulting Type-11 record.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:DiscontinuityDiaryInformation
XML Min/Max: 0 / 600000
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.024_0: Discontinuities Diary - Subfields: Repeating Sets Of Information Items (DCD_0)
Description:
This optional field allows the documentation of discontinuities in the signal.
This field need not be present if Field 11.023:
Discontinuities / DIS is present in the record and DCI = 1, but it is highly recommended in such a case that this field be present.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
600000
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
604
Type-11: Forensic and Investigatory Voice Data
11.024_1: Discontinuities Diary - Segment Identifier (SID)
Description:
Uniquely numbers the discontinuity to which the following items in the subfield apply. It is mandatory in each subfield.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
positive integer, no commas
Format
n/a
Constraints
1 ≤ SID ≤ 600000
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:DiscontinuityDiaryInformation
NIEM Element: biom:SegmentID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.024_2: Discontinuities Diary - Track And Channel Number List (TRK)
Description:
Contains the Track and Channel Number List. It is mandatory if TRC in Field 11.012: Physical media object / PMO or CHC of
Field 11.014: Codec / CDC is greater than one and lists all tracks or channels on the recording to which SID applies. No value
in this list should be greater than the value of TRC or CHC, whichever applies.
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
9999
Character Types
NS
Special Characters
For Traditional encoding,
the separator character “|”
is used between elements.
This is not applicable to
XML encoding.
Format
n/a
Constraints
List of non-negative integers
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:DiscontinuityDiaryInformation/biom:TrackChannelList
NIEM Element: biom:TrackID
XML Min/Max: 1 / 9999
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
605
Type-11: Forensic and Investigatory Voice Data
11.024_3: Discontinuities Diary - Relative Start Time (RST)
Description:
It indicates in microseconds the time of the start of the discontinuity relative to the beginning of the voice recording contained in
this Type-11 record. It is mandatory for every discontinuity identified by an SID.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ RST, integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:DiscontinuityDiaryInformation
NIEM Element: biom:RelativeStartTimeInMSValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.024_4: Discontinuities Diary - Relative End Time (RET)
Description:
It indicates in microseconds the time of the end of the discontinuity relative to the beginning of the voice recording contained in
this Type-11 record. It is mandatory for every discontinuity identified by an SID. If RET > RST, that indicates that the content
has been removed or is not present, but not redacted (masked).
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
RET ≥ RST, integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:DiscontinuityDiaryInformation
NIEM Element: biom:RelativeEndTimeInMSValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
606
Type-11: Forensic and Investigatory Voice Data
11.024_5: Discontinuities Diary - Comment (COM)
Description:
An unrestricted text string that allows for comments of any type to be made about a discontinuity.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:DiscontinuityDiaryInformation
NIEM Element: biom:DiaryCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.025: Vocal Content (VOC)
Description:
This optional field indicates whether the voice recording content has been diarized, meaning that time markings are included in
Field 11.026: Vocal content diary / VCD to indicate the speech segments of interest pertaining to the subject of this Type-11
record.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:VocalContentInformation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
607
Type-11: Forensic and Investigatory Voice Data
11.025_1: Vocal Content - Diarization Indicator (DII)
Description:
Code that indicates whether the voice recording is accompanied by a segment diary in Field 11.026 indicating speech
segments from the voice signal subject of the Type-11 record. It is mandatory if this field is used. A value of 0 indicates that
there is no accompanying diary and a value of 1 indicates the presence of Field 11.026: Vocal content diary / VCD.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
DII = 0 or 1
Code List: DISCONTINUITY INDICATOR CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalContentInformation
NIEM Element: biom:DiarizationIndicatorCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.025_2: Vocal Content - Diarization Authority Organization Name (DAU)
Description:
An optional text field of up to 300 characters containing information about the agency that performed the diarization. Agencies
undertaking diarization activities on the original speech should log their actions by appending to this item and noting the
change of field contents in the Type-98 record and/or Field 11.902: Annotation information / ANN of this record. This
information item shall only appear if DII = 1.
Field Minimum
1
Field Maximum
300
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalContentInformation
NIEM Element: biom:ProcessingAuthorityText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
608
Type-11: Forensic and Investigatory Voice Data
11.025_3: Vocal Content - Comments (COM)
Description:
This optional field contains text information about the diarization activities undertaken on the voice data.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalContentInformation
NIEM Element: biom:ProcessingCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.026: Vocal Content Diary (VCD)
Description:
This field contains subfields that locate the segments within the voice recording of this Type-11 record that are associated with
a single speaker – the subject of the record (not necessarily the subject of the transaction). Contains text information about the
diarization activities undertaken on the voice data. If Field 11.025 is included in the record, then this field shall be present only
if DII = 1. This field may be used for individual snips, as well as concatenated snips.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:VocalContentDiaryInformation
XML Min/Max: 0 / 600000
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
609
Type-11: Forensic and Investigatory Voice Data
11.026_0: Vocal Content Diary - Subfields: Repeating Sets Of Information Items (VCD_0)
Description:
This field contains subfields that locate the segments within the voice recording of this Type-11 record that are associated with
a single speaker – the subject of the record (not necessarily the subject of the transaction). Contains text information about the
diarization activities undertaken on the voice data.
If Field 11.025 is included in the record, then this field shall be present
only if DII = 1. This field may be used for individual snips, as well as concatenated snips.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
600000
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.026_1: Vocal Content Diary - Segment Identifier (SID)
Description:
Uniquely numbers the discontinuity to which the following items in the subfield apply. It is mandatory in each subfield.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
no commas
Format
n/a
Constraints
1 ≤ SID ≤ 600000, integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalContentDiaryInformation
NIEM Element: biom:SegmentID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
610
Type-11: Forensic and Investigatory Voice Data
11.026_2: Vocal Content Diary - Track And Channel Number List (TRK)
Description:
Contains the Track and Channel Number List. It is mandatory if TRC in Field 11.012: Physical media object / PMO or CHC of
Field 11.014: Codec / CDC is greater than one and lists all tracks or channels on the recording to which SID applies. No value
in this list should be greater than the value of TRC or CHC, whichever applies.
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
9999
Character Types
NS
Special Characters
For Traditional encoding,
the separator character “|”
is used between elements.
This is not applicable to
XML encoding.
Format
n/a
Constraints
Contains list of nonnegative integers
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalContentDiaryInformation/biom:TrackChannelLis
t
NIEM Element: biom:TrackID
XML Min/Max: 1 / 9999
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.026_3: Vocal Content Diary - Relative Start Time (RST)
Description:
It indicates in microseconds the time of the start of the discontinuity relative to the beginning of the voice recording contained in
this Type-11 record. It is mandatory for every discontinuity identified by an SID.
Field Minimum
1
Field Maximum
11
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ RST, integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalContentDiaryInformation
NIEM Element: biom:RelativeStartTimeInMSValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
611
Type-11: Forensic and Investigatory Voice Data
11.026_4: Vocal Content Diary - Relative End Time (RET)
Description:
It indicates in microseconds the time of the end of the discontinuity relative to the beginning of the voice recording contained in
this Type-11 record. It is mandatory for every discontinuity identified by an SID. If RET > RST, that indicates that the content
has been removed or is not present, but not redacted (masked).
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
RET > RST, integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalContentDiaryInformation
NIEM Element: biom:RelativeEndTimeInMSValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.026_5: Vocal Content Diary - Comment (COM)
Description:
Allows for comments of any type to be made on a segment.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalContentDiaryInformation
NIEM Element: biom:DiaryCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
612
Type-11: Forensic and Investigatory Voice Data
11.026_6: Vocal Content Diary - Tagged Data (TDT)
Description:
This optional field gives the date indicated on the original, contemporaneous capture of the voice recording in the segment
identified in this Type-11 record.
Field Minimum
Dependent on Encoding
Field Maximum
Dependent on Encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Dependent on Encoding
Special Characters
Format
Dependent on Encoding
Constraints
YYYYMMDD
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalContentDiaryInformation
NIEM Element: biom:TagStartDateTime/nc:DateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.026_7: Vocal Content Diary - Tagged Start Time (TST)
Description:
Time tagged on the original, contemporaneous capture of the recording in the segment identified.
Field Minimum
Dependent on Encoding
Field Maximum
Dependent on Encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Dependent on Encoding
Special Characters
Format
Dependent on Encoding
Constraints
YYYYMMDDhhmm
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalContentDiaryInformation
NIEM Element: biom:TagStartDateTime/nc:DateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
613
Type-11: Forensic and Investigatory Voice Data
11.026_8: Vocal Content Diary - Tagged End Time (TET)
Description:
Time tagged on original, contemporaneous capture of the data at the end of the segment identified.
Field Minimum
Dependent on Encoding
Field Maximum
Dependent on Encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Dependent on Encoding
Special Characters
Format
Dependent on Encoding
Constraints
YYYYMMDDhhmm
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalContentDiaryInformation
NIEM Element: biom:TagEndDateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.026_9: Vocal Content Diary - Original Recording Date (ORD)
Description:
Date of the original, contemporaneous capture of the voice recording in the segment identified. Optional.
Field Minimum
Dependent on Encoding
Field Maximum
Dependent on Encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Dependent on Encoding
Special Characters
Format
Dependent on Encoding
Constraints
YYYYMMDDhhmm
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalContentDiaryInformation
NIEM Element: biom:OriginalRecordingDate/nc:Date
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
614
Type-11: Forensic and Investigatory Voice Data
11.026_10: Vocal Content Diary - Segment Recording Start Time (SRT)
Description:
Local start time of the original, contemporaneous capture of the recording in the segment identified. This item may be different
from the value of TST if the tag is determined to be inaccurate.
Field Minimum
Dependent on Encoding
Field Maximum
Dependent on Encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Dependent on Encoding
Special Characters
Format
Dependent on Encoding
Constraints
YYYYMMDDhhmm
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalContentDiaryInformation
NIEM Element: biom:SegmentRecordingStartDateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.026_11: Vocal Content Diary - Segment Recording End Time (END)
Description:
Local end time of the original, contemporaneous capture of the recording in the segment identified. This item may be different
from the value of TST if the tag is determined to be inaccurate.
Field Minimum
Dependent on Encoding
Field Maximum
Dependent on Encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Dependent on Encoding
Special Characters
Format
Dependent on Encoding
Constraints
YYYYMMDDhhmm
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalContentDiaryInformation
NIEM Element: biom:SegmentRecordingEndDateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
615
Type-11: Forensic and Investigatory Voice Data
11.026_12: Vocal Content Diary - Time Source Description Text (TMD)
Description:
Reference for the values used in ORD, SRT and END.
Field Minimum
1
Field Maximum
300
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalContentDiaryInformation
NIEM Element: biom:TimeSourceDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.026_13: Vocal Content Diary - Timing Comments (TCOM)
Description:
Comments of any type to be made on the timings of the segment recording including the perceived accuracy of the values of
ORD, SRT and END.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalContentDiaryInformation
NIEM Element: biom:TimeCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
616
Type-11: Forensic and Investigatory Voice Data
11.027: Other Content - Other Content (OCON)
Description:
Indicates whether the recording content has been diarized, meaning that time markings are included, in Field 11.028: Other
content diary / OCD In order to indicate the segments of the recording that may contain sounds other than the voice of the
subject of the record that could assist in the investigation (such as the sound of an automobile accident in a recording).
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Code List: DISCONTINUITY INDICATOR CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:OtherContentInformation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.027_1: Other Content - Diarization Indicator (DII)
Description:
Code that indicates whether the voice recording is accompanied by a segment diary in Field 11.028 indicating speech
segments from the voice signal subject of the Type-11 record. It is mandatory if this field is used. A value of 0 indicates that
there is no accompanying diary and a value of 1 indicates the presence of Field 11.026: Vocal content diary / VCD.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
DII = 0 or 1
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:OtherContentInformation
NIEM Element: biom:DiarizationIndicatorCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
617
Type-11: Forensic and Investigatory Voice Data
11.027_2: Other Content - Diarization Authority (DAU)
Description:
An optional text field of up to 300 characters containing information about the agency that performed the diarization. Agencies
undertaking diarization activities on the original speech should log their actions by appending to this item and noting the
change of field contents in the Type-98 record and/or Field 11.902: Annotation information / ANN of this record. This
information item shall only appear if DII = 1.
Field Minimum
1
Field Maximum
300
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:OtherContentInformation
NIEM Element: biom:ProcessingAuthorityText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.027_3: Other Content - Comments (COM)
Description:
This optional field contains text information about the diarization activities undertaken on the voice data.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:OtherContentInformation
NIEM Element: biom:ProcessingCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
618
Type-11: Forensic and Investigatory Voice Data
11.028: Other Content Diary (OCD)
Description:
This field contains subfields that locate the segments within the recording of this Type-11 record that may be of interest for
investigatory purposes but are not focused upon speech. Although Field 11.027: Other content / OCON need not be present in
the record if this field is included in the record, it is highly recommended that it be present. If Field 11.027 is included in the
record, then this field shall be present only if DII = 1. This record type accommodates up to 600,000 segments.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:OtherContentDiaryInformation
XML Min/Max: 0 / 600000
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.028_0: Other Content Diary - Subfields: Repeating Sets Of Information Items (OCD_0)
Description:
This field contains subfields that locate the segments within the recording of this Type-11 record that may be of interest for
investigatory purposes but are not focused upon speech. Although Field 11.027: Other content / OCON need not be present in
the record if this field is included in the record, it is highly recommended that it be present. If Field 11.027 is included in the
record, then this field shall be present only if DII = 1. This record type accommodates up to 600,000 segments.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
600000
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
619
Type-11: Forensic and Investigatory Voice Data
11.028_1: Other Content Diary - Segment Identifier (SID)
Description:
Uniquely numbers the discontinuity to which the following items in the subfield apply. It is mandatory in each subfield.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
no commas
Format
n/a
Constraints
1 ≤ SID ≤ 600000, integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:OtherContentDiaryInformation
NIEM Element: biom:SegmentID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.028_2: Other Content Diary - Track And Channel Number List (TRK)
Description:
Contains the Track and Channel Number List. It is mandatory if TRC in Field 11.012: Physical media object / PMO or CHC of
Field 11.014: Codec / CDC is greater than one and lists all tracks or channels on the recording to which SID applies. No value
in this list should be greater than the value of TRC or CHC, whichever applies.
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
9999
Character Types
NS
Special Characters
For Traditional encoding,
the separator character “|”
is used between elements.
This is not applicable to
XML encoding.
Format
n/a
Constraints
Contains list of nonnegative integers
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:OtherContentDiaryInformation/biom:TrackChannelLis
t
NIEM Element: biom:TrackID
XML Min/Max: 1 / 9999
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
620
Type-11: Forensic and Investigatory Voice Data
11.028_3: Other Content Diary - Relative Start Time (RST)
Description:
It indicates in microseconds the time of the start of the discontinuity relative to the beginning of the voice recording contained in
this Type-11 record. It is mandatory for every discontinuity identified by an SID.
Field Minimum
1
Field Maximum
11
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ RST, positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:OtherContentDiaryInformation
NIEM Element: biom:RelativeStartTimeInMSValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.028_4: Other Content Diary - Relative End Time (RET)
Description:
It indicates in microseconds the time of the end of the discontinuity relative to the beginning of the voice recording contained in
this Type-11 record. It is mandatory for every discontinuity identified by an SID. If RET > RST, that indicates that the content
has been removed or is not present, but not redacted (masked).
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
RET > RST, integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:OtherContentDiaryInformation
NIEM Element: biom:RelativeEndTimeInMSValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
621
Type-11: Forensic and Investigatory Voice Data
11.028_5: Other Content Diary - Comment (COM)
Description:
Allows for comments of any type to be made on a segment.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:OtherContentDiaryInformation
NIEM Element: biom:DiaryCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.028_6: Other Content Diary - Tagged Data (TDT)
Description:
This optional field gives the date indicated on the original, contemporaneous capture of the voice recording in the segment
identified in this Type-11 record.
Field Minimum
Dependent on Encoding
Field Maximum
Dependent on Encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Dependent on Encoding
Special Characters
Format
Dependent on Encoding
Constraints
Dependent on Encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:OtherContentDiaryInformation
NIEM Element: biom:TagStartDateTime/nc:DateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
622
Type-11: Forensic and Investigatory Voice Data
11.028_7: Other Content Diary - Tagged Start Time (TST)
Description:
Time tagged on the original, contemporaneous capture of the recording in the segment identified.
Field Minimum
Dependent on Encoding
Field Maximum
Dependent on Encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Dependent on Encoding
Special Characters
Format
Dependent on Encoding
Constraints
Dependent on Encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:OtherContentDiaryInformation
NIEM Element: biom:TagStartDateTime/nc:DateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.028_8: Other Content Diary - Tagged End Time (TET)
Description:
Time tagged on original, contemporaneous capture of the data at the end of the segment identified.
Field Minimum
Dependent on Encoding
Field Maximum
Dependent on Encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Dependent on Encoding
Special Characters
Format
Dependent on Encoding
Constraints
Dependent on Encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:OtherContentDiaryInformation
NIEM Element: biom:TagEndDateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
623
Type-11: Forensic and Investigatory Voice Data
11.028_9: Other Content Diary - Original Recording Date (ORD)
Description:
Date of the original, contemporaneous capture of the voice recording in the segment identified. Optional.
Field Minimum
Dependent on Encoding
Field Maximum
Dependent on Encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Dependent on Encoding
Special Characters
Format
Dependent on Encoding
Constraints
Dependent on Encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:OtherContentDiaryInformation
NIEM Element: biom:OriginalRecordingDate/nc:Date
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.028_10: Other Content Diary - Segment Recording Start Time (SRT)
Description:
Local start time of the original, contemporaneous capture of the recording in the segment identified. This item may be different
from the value of TST if the tag is determined to be inaccurate.
Field Minimum
Dependent on Encoding
Field Maximum
Dependent on Encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Dependent on Encoding
Special Characters
Format
Dependent on Encoding
Constraints
Dependent on Encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:OtherContentDiaryInformation
NIEM Element: biom:SegmentRecordingStartDateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
624
Type-11: Forensic and Investigatory Voice Data
11.028_11: Other Content Diary - Segment Recording End Time (END)
Description:
Local end time of the original, contemporaneous capture of the recording in the segment identified. This item may be different
from the value of TST if the tag is determined to be inaccurate.
Field Minimum
Dependent on Encoding
Field Maximum
Dependent on Encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Dependent on Encoding
Special Characters
Format
Dependent on Encoding
Constraints
Dependent on Encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:OtherContentDiaryInformation
NIEM Element: biom:SegmentRecordingEndDateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.028_12: Other Content Diary - Time Source Description Text (TMD)
Description:
Reference for the values used in ORD, SRT and END.
Field Minimum
1
Field Maximum
300
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:OtherContentDiaryInformation
NIEM Element: biom:TimeSourceDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
625
Type-11: Forensic and Investigatory Voice Data
11.028_13: Other Content Diary - Timing Comments (TCOM)
Description:
Comments of any type to be made on the timings of the segment recording including the perceived accuracy of the values of
ORD, SRT and END.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:OtherContentDiaryInformation
NIEM Element: biom:TimeCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.032: Vocal Segment Geographical Information (SGEO)
Description:
Gives the geographical location of the primary subject of the Type-11 record at the beginning of that segment. If Field 11.025:
Vocal content / VOC is present, then this field shall only be present if DII = 1. This field shall only be present if Field 11.026:
Vocal content diary / VCD is present.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:SegmentGeographicalLocation
XML Min/Max: 0 / 600000
DoD EBTS 1.2:
April 2019
n/a
DoD EBTS 2.0
n/a
DoD EBTS 3.0:
n/a
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
n/a
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
626
Type-11: Forensic and Investigatory Voice Data
11.032_0: Vocal Segment Geographical Information - Subfield: Repeating Sets of Information Items
(SGEO_0)
Description:
Gives the geographical location of the primary subject of the Type-11 record at the beginning of that segment.
If Field
11.025: Vocal content / VOC is present, then this field shall only be present if DII = 1. This field shall only be present if Field
11.026: Vocal content diary / VCD is present.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
600000
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentGeographicalLocation
NIEM Element: biom:SegmentIDList
XML Min/Max: 1 / 1
DoD EBTS 1.2:
n/a
DoD EBTS 2.0
n/a
DoD EBTS 3.0:
n/a
DoD EBTS 4.1:
n/a
11.032_01: Vocal Segment Geographical Information - Segment Identifier List (SIL)
Description:
Segment identifiers to which the values in this subfield pertain. A value of 0 in this subfield indicates the segment geographical
information in this subfield shall be considered the default value for all segments not specifically identified in other occurrences
of this subfield. If multiple segments are identified, they are designated as integers in a list. It is mandatory in each subfield.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
1
Occurrence Maximum
600000
Character Types
NS
Special Characters
list of non-negative integers
For Traditional encoding,
the separator character “|”
is used between
elements.This is not
applicable to XML
encoding.
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentGeographicalLocation/biom:SegmentIDList
NIEM Element: biom:SegmentID
XML Min/Max: 1 / 600000
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
627
Type-11: Forensic and Investigatory Voice Data
11.032_02: Vocal Segment Geographical Information - Segment Cell Phone Tower Code (SCT)
Description:
Identifies the cell phone tower, if any, that relayed the audio data at the start of the segment or segments referred to in this
subfield. Optional.
Field Minimum
1
Field Maximum
100
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentGeographicalLocation
NIEM Element: biom:CellPhoneTowerCodeText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.032_03: Vocal Segment Geographical Information - Latitude Degree Value (LTD)
Description:
The second information item is latitude degree value (LTD). This is a value that specifies the degree of latitude. The value shall
be between -90 (inclusive) and +90 (inclusive). The degrees may be expressed as an integer (without a decimal) or a real
number including decimals. If decimals are present, then minutes and seconds shall be empty. Examples: Buenos Aires,
Argentina: -34 (with minutes LTM = 36) NIST, Gaithersburg, Maryland: 39.137627 (no LTM or LTS)
Field Minimum
1
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal,Minus Sign
Format
n/a
Constraints
-90 ≤ LTD ≤ 90
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentGeographicalLocation/nc:Location3DGeosp
atialCoordinate/nc:GeographicCoordinateLatitude
NIEM Element: nc:LatitudeDegreeValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
628
Type-11: Forensic and Investigatory Voice Data
11.032_04: Vocal Segment Geographical Information - Latitude Minute Value (LTM)
Description:
This information item is latitude minute value (LTM). This is a value that specifies a minute of a degree. The value shall be
between 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall be empty. Thus, the allowed special character is a
period. The minute value can be empty, even if the degree value is an integer. LTM and LGM are co-conditional, so they shall
both be present if either is present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LTM < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentGeographicalLocation/nc:Location3DGeosp
atialCoordinate/nc:GeographicCoordinateLatitude
NIEM Element: nc:LatitudeMinuteValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
11.032_05: Vocal Segment Geographical Information - Latitude Second Value (LTS)
Description:
The fourth information item is the latitude second value (LTS). This is a value that specifies a second of a minute. The integer
shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LTS < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentGeographicalLocation/nc:Location3DGeosp
atialCoordinate/nc:GeographicCoordinateLatitude
NIEM Element: nc:LatitudeSecondValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
629
Type-11: Forensic and Investigatory Voice Data
11.032_06: Vocal Segment Geographical Information - Longitude Degree Value (LGD)
Description:
The fifth information item is the longitude degree value (LGD). It is a value that specifies the degree of a longitude. The value
shall be between -180 (inclusive) and +180 (inclusive). If LTD is present, then LGD shall be present. The degrees may be
expressed as whole numbers (without a decimal) or real numbers including decimals. If decimals are present, then minutes
and seconds are empty. Examples: Buenos Aires, Argentina: -58 (with minutes LGM = 22), NIST, Gaithersburg, Maryland: 77.216032 (no LGM or LGS)
Field Minimum
1
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal,Minus Sign,Plus
Sign
Format
n/a
Constraints
-180 ≤ LGD ≤ 180
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentGeographicalLocation/nc:Location3DGeosp
atialCoordinate/nc:GeographicCoordinateLongitude
NIEM Element: nc:LongitudeDegreeValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.032_07: Vocal Segment Geographical Information - Longitude Minute Value (LGM)
Description:
The sixth information item is the longitude minute value (LGM). It is a value that specifies a minute of a degree. The value shall
be from 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall not appear. The minute value is empty, even if the
degree value is an integer. If LTM is present, then LGM shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LGM < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentGeographicalLocation/nc:Location3DGeosp
atialCoordinate/nc:GeographicCoordinateLongitude
NIEM Element: nc:LongitudeMinuteValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
630
Type-11: Forensic and Investigatory Voice Data
11.032_08: Vocal Segment Geographical Information - Longitude Second Value (LGS)
Description:
The seventh information item is the longitude second value (LGS). This is a value that specifies a second of a minute. The
integer shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer. If LTS is
present, then LGS shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LGS < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentGeographicalLocation/nc:Location3DGeosp
atialCoordinate/nc:GeographicCoordinateLongitude
NIEM Element: nc:LongitudeSecondValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.032_09: Vocal Segment Geographical Information - Elevation (ELE)
Description:
The eighth information item is elevation (ELE). It is expressed in meters. It is a numeric value. It is between -422 meters (Dead
Sea) and 8848 meters (Mount Everest). Allowed special characters are the negative sign and the period.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Minus Sign,Period
Format
n/a
Constraints
-422.000 ≤ ELE ≤ 8848.000;
real number
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentGeographicalLocation/nc:Location3DGeosp
atialCoordinate
NIEM Element: nc:LocationElevation/nc:MeasureDecimalValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
631
Type-11: Forensic and Investigatory Voice Data
11.032_10: Vocal Segment Geographical Information - Geodetic Datum Code (GDC)
Description:
The ninth information item is the geodetic datum code (GDC11). It is an alphanumeric value of 3 to 6 characters in length. This
information item is used to indicate which coordinate system was used to represent the values in information items 2 through
7. If no entry is made in this information item, then the basis for the values entered in the first eight information items shall be
WGS84, the code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values. If no entry is
made in this information item, then the basis for the values entered in the first eight information items shall be WGS84, the
code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values.
Field Minimum
3
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
see Look Up Codes
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentGeographicalLocation/nc:Location3DGeosp
atialCoordinate
NIEM Element: biom:GeodeticDatumCoordinateSystemCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.032_11: Vocal Segment Geographical Information - Geographic Coordinate Universal Transverse
Mercator Zone (GCM)
Description:
It is an alphanumeric value of 2 to 3 characters. This is a one or two digit UTM zone number followed by the 8 degree
latitudinal band designator (which is a single letter).
Field Minimum
2
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
One or two digits followed
by a single letter
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentGeographicalLocation
NIEM Element: nc:LocationUTMCoordinateValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
632
Type-11: Forensic and Investigatory Voice Data
11.032_12: Vocal Segment Geographical Information - Geographic Coordinate Universal Transverse
Mercator Easting (GCE)
Description:
The eleventh information item is the geographic coordinate universal transverse Mercator easting (GCE). It is an integer of 1 to
6 digits.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentGeographicalLocation
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.032_13: Vocal Segment Geographical Information - Geographic Coordinate Universal Transverse
Mercator Northing (GCN)
Description:
The twelfth information item is the geographic coordinate universal transverse Mercator northing (GCN). It is an integer of 1 to
8 digits.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentGeographicalLocation
NIEM Element: mo:MGRSCoordinateStringText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
633
Type-11: Forensic and Investigatory Voice Data
11.032_14: Vocal Segment Geographical Information - Geographic Reference Text (GRT)
Description:
It is a free form text describing a street address or other physical location (such as ‘Corner of Washington and Madison,
Geneva, NY’).
Field Minimum
1
Field Maximum
150
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Code List: GEOGRAPHIC COORDINATE DATUM CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentGeographicalLocation
NIEM Element: nc:LocationDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.032_15: Vocal Segment Geographical Information - Geographic Coordinate Other System Identifier (or
Landmark) (OSI)
Description:
A fourteenth optional information item geographic coordinate other system identifier (OSI) allows for other coordinate systems.
This information items specifies the system identifier. It is up to 10 characters in length. Examples are: • MGRS (Militar Grid
Reference System), • USNG (United States National Grid), • GARS (Global Area Reference System), • GEOREF (World
Geographic Reference), • LANDMARK landmark (e.g. hydant) and position relative to the landmark.
Field Minimum
1
Field Maximum
10
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Code List: GEOGRAPHIC COORDINATE DATUM CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentGeographicalLocation
NIEM Element: biom:GeographicLocationSystemName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
634
Type-11: Forensic and Investigatory Voice Data
11.032_16: Vocal Segment Geographical Information - Geographic Coordinate Other System Value (OCV)
Description:
A fifteenth optional information item, is the geographic coordinate other system value (OCV). It shall only be present if OSI is
present in the record. It can be up to 126 characters in length. If OSI is LANDMARK, OCV is free text and may be up to 126
characters. For details on the formatting of OCV for the other coordinate systems shown in OSI as examples, see http://earthinfo.nga.mil/GandG/coordsys/grids/referencesys.html .
Field Minimum
1
Field Maximum
126
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentGeographicalLocation
NIEM Element: biom:GeographicLocationText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.033: Vocal Segment Quality Values (SQV)
Description:
If Field 11.025: Vocal content / VOC is present, then this field shall only be present if DII = 1. This field shall only be present if
Field 11.026: Vocal content diary / VCD is present. If segments have multiple quality values based on different types of quality
assessments, a separate subfield is entered for each assessment.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:VocalSegmentQualityValue
XML Min/Max: 0 / 9
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
635
Type-11: Forensic and Investigatory Voice Data
11.033_0: Vocal Segment Quality Values - Subfield: Repeating Sets of Information Items (SQV_0)
Description:
Quality values based on different types of quality assessments,
Present if DII = 1.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
9
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalSegmentQualityValue
NIEM Element: biom:SegmentIDList
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.033_1: Vocal Segment Quality Values - Segment Identifier List (SIL)
Description:
Segment identifiers to which the values in this subfield pertain. A value of 0 in this subfield indicates the segment geographical
information in this subfield shall be considered the default value for all segments not specifically identified in other occurrences
of this subfield. If multiple segments are identified, they are designated as integers in a list. It is mandatory in each subfield.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
1
Occurrence Maximum
600000
Character Types
NS
Special Characters
For Traditional encoding,
the separator character “|”
is used between elements.
This is not applicable to
XML encoding.
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalSegmentQualityValue/biom:SegmentIDList
NIEM Element: biom:SegmentID
XML Min/Max: 1 / 600000
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
636
Type-11: Forensic and Investigatory Voice Data
11.033_2: Vocal Segment Quality Values - Quality Value (QVU)
Description:
Indicate the segment quality value between 0 (low quality) and 100 (high quality). A value of 255 indicates that quality was not
assessed.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
integer
Format
n/a
Constraints
0 ≤ QVU ≤ 100 or = 255
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalSegmentQualityValue
NIEM Element: biom:QualityValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.033_3: Vocal Segment Quality Values - Algorithm Vendor Identification (QAV)
Description:
Specifies the ID of the vendor of the quality assessment algorithm used to calculate the quality score. This 4-digit hex value is
assigned by IBIA and expressed as four characters. A value of 0000 indicates a vendor without a designation by IBIA. In such
case, an entry shall be made in COM of this subfield describing the algorithm and its owner/vendor.
Field Minimum
4
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
0000 ≤ QAV ≤ FFFF
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalSegmentQualityValue
NIEM Element: biom:QualityAlgorithmVendorID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
637
Type-11: Forensic and Investigatory Voice Data
11.033_4: Vocal Segment Quality Values - Algorithm Product Identification (QAP)
Description:
Specifies a numeric product code assigned by the vendor of the quality assessment algorithm.
Indicates which of the
vendor’s algorithms was used in the calculation of the quality score. A value of 0 indicates a vendor without a designation by
IBIA. In such case, an entry shall be made in COM of this subfield describing the algorithm and its owner/vendor.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
integer
Format
n/a
Constraints
0 ≤ QAP ≤ 65534
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalSegmentQualityValue
NIEM Element: biom:QualityAlgorithmProductID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.033_5: Vocal Segment Quality Values - Comments (COM)
Description:
Provides information about the quality assessment process, including a description of any unregistered quality assessment
algorithms used.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalSegmentQualityValue
NIEM Element: biom:VocalSegmentQualityCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
638
Type-11: Forensic and Investigatory Voice Data
11.034: Vocal Collision Identifier (VCI)
Description:
Field ndicating that a vocal collision (two or more persons talking at once) occurs within the segment. If Field 11.025: Vocal
content / VOC is present, then this field shall only be present if DII = 1. This field shall only be present if Field 11.026: Vocal
content diary / VCD is present.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
non-negative integer
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:VocalCollisionIDList
NIEM Element: biom:SegmentID
XML Min/Max: 1 / 600000
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.034_0: Vocal Collision Identifier - Subfield: Repeating Sets Of Information Items (VCI_0)
Description:
If Field 11.025: Vocal content / VOC is present, then this field shall only be present if DII = 1. This field shall only be present if
Field 11.026: Vocal content diary / VCD is present. This optional field indicates that a vocal collision (two or more persons
talking at once) occurs within the segment. This field has repeating values. Each value represents a separate segment. There
may be up to 600,000 segments identified in this field.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
1
Occurrence Maximum
600000
Character Types
N
Special Characters
list of non-negative integers
For Traditional encoding,
the separator character “|”
is used between elements.
This is not applicable to
XML encoding.
Format
n/a
Constraints
non-negative integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
639
Type-11: Forensic and Investigatory Voice Data
11.035: Vocal Segment Processing Priority (PPY)
Description:
This optional field only appears if Field 11.025: Vocal content / VOC exists in this record. Segments not identified should be
given the lowest priority.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:SegmentProcessingPriorityInformation
XML Min/Max: 0 / 9
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.035_0: Vocal Segment Processing Priority - Subfield: Repeating Sets Of Information Items (PPY_0)
Description:
Only appears if Field 11.025: Vocal content / VOC exists in this record.
priority.
Segments not identified should be given the lowest
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
9
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentProcessingPriorityInformation
NIEM Element: biom:SegmentIDList
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
640
Type-11: Forensic and Investigatory Voice Data
11.035_1: Vocal Segment Processing Priority - Segment Identifier List (SIL)
Description:
Segment identifiers to which the values in this subfield pertain. A value of 0 in this subfield indicates the segment geographical
information in this subfield shall be considered the default value for all segments not specifically identified in other occurrences
of this subfield. If multiple segments are identified, they are designated as integers in a list. It is mandatory in each subfield.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
1
Occurrence Maximum
600000
Character Types
NS
Special Characters
For Traditional encoding,
the separator character “|”
is used between elements.
This is not applicable to
XML encoding.
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentProcessingPriorityInformation/biom:Segmen
tIDList
NIEM Element: biom:SegmentID
XML Min/Max: 1 / 600000
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.035_2: Vocal Segment Processing Priority - Priority (PTY)
Description:
Indicates the priority with which the segments identified in this subfield should be processed. A value of 1 will indicate the
highest priority and 9 the lowest. This field is mandatory.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
positive integer
Format
n/a
Constraints
1 ≤ PTY ≤ 9
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentProcessingPriorityInformation
NIEM Element: biom:ProcessingPriorityValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
641
Type-11: Forensic and Investigatory Voice Data
11.036: Vocal Segment Content Description (VSCD)
Description:
This optional field shall only appear if Field 11.025: Vocal content / VOC exists in the record. Gives an assessment of the
content of the voice data within the identified segment and includes provision for semantic transcripts, phonetic transcriptions
and translations of the segment. At least one of the information items in addition to SIL shall be present in this field.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:SegmentContentInformation
XML Min/Max: 0 / 600000
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.036_0: Vocal Segment Content Description - Subfield: Repeating Sets Of Information Items (VSCD_0)
Description:
Gives an assessment of the content of the voice data within the identified segment and includes provision for semantic
transcripts, phonetic transcriptions and translations of the segment.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
600000
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
642
Type-11: Forensic and Investigatory Voice Data
11.036_1: Vocal Segment Content Description - Segment Identifier List (SIL)
Description:
Segment identifiers to which the values in this subfield pertain. A value of 0 in this subfield indicates the segment geographical
information in this subfield shall be considered the default value for all segments not specifically identified in other occurrences
of this subfield. If multiple segments are identified, they are designated as integers in a list. It is mandatory in each subfield.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
1
Occurrence Maximum
600000
Character Types
NS
Special Characters
For Traditional encoding,
the separator character “|”
is used between elements.
This is not applicable to
XML encoding.
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentContentInformation/biom:SegmentIDList
NIEM Element: biom:SegmentID
XML Min/Max: 1 / 600000
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.036_2: Vocal Segment Content Description - Transcript Text (TRN)
Description:
Contains a semantic transcription of the segment.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentContentInformation
NIEM Element: biom:SegmentTranscriptText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
643
Type-11: Forensic and Investigatory Voice Data
11.036_3: Vocal Segment Content Description - Transcript Language (LNG)
Description:
The third information item is the transcript language / LNG. It is optional but shall only be in the subfield if TRN is present in the
subfield. It states the 3 character ISO 639-3 code for the language of the translation included in this subfield.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
Value from ISO-639-3.
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentContentInformation
NIEM Element: biom:SegmentTranscriptLanguageCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.036_4: Vocal Segment Content Description - Phonetic Transcript Text (PTT)
Description:
Contains a phonetic transcription of the segment. This may be informal (based upon the language conventions of the record
creator), the International Phonetic Alphabet, the Americanist phonetic notation, or other system. The IPA extensions in
Unicode, such as ɣ or ʁ or ɽ, can thus be used.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
IPA extensions in Unicode
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentContentInformation
NIEM Element: biom:SegmentPhoneticTranscriptText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
644
Type-11: Forensic and Investigatory Voice Data
11.036_5: Vocal Segment Content Description - Phonetic Transcript Convention (PTC)
Description:
States the phonetic transcript convention.
Present only if PTT is present in the subfield.
Field Minimum
1
Field Maximum
100
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentContentInformation
NIEM Element: biom:PhoneticTranscriptConventionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.036_6: Vocal Segment Content Description - Translation Text (TLT)
Description:
Contains a translation of the segment into a language other than the one in which the original segment was spoken. If a text is
translated into multiple languages, a separate subfield is generated for each language.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentContentInformation
NIEM Element: biom:SegmentTranslationText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
645
Type-11: Forensic and Investigatory Voice Data
11.036_7: Vocal Segment Content Description - Translation Language (TLG)
Description:
Language of the translation. Present only if TRN is present. It states the 3 character ISO 639-3 code for the language of the
translation included in this subfield.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
Value from ISO-639-3.
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentContentInformation
NIEM Element: biom:SegmentTranslationLanguageCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.036_8: Vocal Segment Content Description - Segment Content Comment (COM)
Description:
Contains comments on the content of the segment.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentContentInformation
NIEM Element: biom:SegmentContentCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
646
Type-11: Forensic and Investigatory Voice Data
11.036_9: Vocal Segment Content Description - Transcript Authority Comment Text (TAC)
Description:
States the authority providing the transcription, translation or comments in TRN, PTT, TLT or COM.
If an automated
process was used to develop the transcript, information about the process (i.e., the automated algorithm used) should be
stated.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentContentInformation
NIEM Element: biom:TranscriptAuthorityCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.037: Vocal Segment Speaker Characteristics (SCC)
Description:
Gives an assessment of the characteristics of the voice within the segment, including intelligibility, emotional state and
impairment.
This field shall only appear if Field 11.025: Vocal content / VOC exists in the record. At least one of the
information items in addition to SIL shall be present in this field.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:SegmentSpeakerCharacteristicsInformation
XML Min/Max: 0 / 600000
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
647
Type-11: Forensic and Investigatory Voice Data
11.037_0: Vocal Segment Speaker Characteristics - Subfield: Repeating Sets Of Information Items (SCC_0)
Description:
Gives an assessment of the characteristics of the voice within the segment, including intelligibility, emotional state and
impairment.
This field shall only appear if Field 11.025: Vocal content / VOC exists in the record.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
600000
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.037_1: Vocal Segment Speaker Characteristics - Segment Identifier List (SIL)
Description:
Segment identifiers to which the values in this subfield pertain. A value of 0 in this subfield indicates the segment geographical
information in this subfield shall be considered the default value for all segments not specifically identified in other occurrences
of this subfield. If multiple segments are identified, they are designated as integers in a list. It is mandatory in each subfield.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
1
Occurrence Maximum
600000
Character Types
NS
Special Characters
For Traditional encoding,
the separator character “|”
is used between elements.
Format
n/a
Constraints
List of non-negative integers
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentSpeakerCharacteristicsInformation/biom:Se
gmentIDList
NIEM Element: biom:SegmentID
XML Min/Max: 1 / 600000
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
648
Type-11: Forensic and Investigatory Voice Data
11.037_2: Vocal Segment Speaker Characteristics - Speaker List (SPL)
Description:
List of unique identifiers for the speakers in the segments identified in SIL.
segment grouping.
List may have up to 9999 speakers per
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
9999
Character Types
U
Special Characters
For Traditional encoding,
the separator character “|”
is used between elements.
This is not applicable to
XML encoding.
Format
n/a
Constraints
List of non-negative integers
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentSpeakerCharacteristicsInformation/biom:Sp
eakerList
NIEM Element: biom:SpeakerID
XML Min/Max: 1 / 9999
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
649
Type-11: Forensic and Investigatory Voice Data
11.037_3: Vocal Segment Speaker Characteristics - Type-2 Record Cross Reference (T2C)
Description:
Contains the IDC value of the Type-2 record that contains relevant biographic information and other data concerning the
subject of this instance of the record.
This list may have up to 98 references (there is a maximum of 100 records in a
transaction; Type-1 is required and this record has an IDC value, leaving a maximum of 98 other possible records.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
98
Character Types
NS
Special Characters
For Traditional encoding,
the separator character “|”
is used between elements.
This is not applicable to
XML encoding.
Format
n/a
Constraints
1 ≤ T2C value ≤ 99, integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentSpeakerCharacteristicsInformation/biom:Ty
pe2CrossReferenceList
NIEM Element: biom:Type2CrossReferenceID
XML Min/Max: 1 / 98
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.037_4: Vocal Segment Speaker Characteristics - Impairment Level Number (IMP)
Description:
Indicates a subjective, observed level of neurological diminishment, whether from fatigue, disease, trauma, or the influence of
medication/substances, across the speech segments identified.
An integer between 0 (no noticed impairment) and 5
(significant), inclusive.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ IMP ≤ 5, integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentSpeakerCharacteristicsInformation
NIEM Element: biom:ImpairmentValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
650
Type-11: Forensic and Investigatory Voice Data
11.037_5: Vocal Segment Speaker Characteristics - Dominant Spoken Language Code (DSL)
Description:
3 character ISO 639-3 code for the dominant language in the segments identified in this subfield.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
Value from ISO-639-3.
Code List: 3 character ISO 639-3 code for the language of the translation included in this subfield.
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentSpeakerCharacteristicsInformation
NIEM Element: biom:DominantSpokenLanguageCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.037_6: Vocal Segment Speaker Characteristics - Language Proficiency Scale Number (LPS)
Description:
Rates the subjective estimation of the fluency of the language being spoken
proficiency)
Scale of 0 (no proficiency) to 9 (high
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 < =LPS ≤ 9
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentSpeakerCharacteristicsInformation
NIEM Element: biom:LanguageProficiencyValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
651
Type-11: Forensic and Investigatory Voice Data
11.037_7: Vocal Segment Speaker Characteristics - Speech Style Code (STY)
Description:
Code indicating the dominant style of speech within the segments. See Table 92 Speech Style Codes from ANSI/NIST-ITL
update 2015.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
See Table 92 Speech Style
Codes from ANSI/NIST-ITL
update 2015.
Code List: SPEECH STYLE CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentSpeakerCharacteristicsInformation
NIEM Element: biom:SpeechStyleCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.037_8: Vocal Segment Speaker Characteristics - Intelligibility Scale Code (INT)
Description:
Integer describing the subjective evaluation of the speech.
0 (unintelligible) to 9 (clear and fully intelligible)
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ INT ≤ 9, integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentSpeakerCharacteristicsInformation
NIEM Element: biom:IntelligibilityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
652
Type-11: Forensic and Investigatory Voice Data
11.037_9: Vocal Segment Speaker Characteristics - Familiarity Degree Code (FDC)
Description:
Indicates the perceived degree of familiarity between the data subject and the interlocutor.
familiarity to 5 indicating high familiarity/intimacy.
Ranges from 0 indicating no
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ FDC ≤ 5,integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentSpeakerCharacteristicsInformation
NIEM Element: biom:FamiliarityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.037_10: Vocal Segment Speaker Characteristics - Health Comment (HCM)
Description:
Notes any observable health issues impacting the data subject during the speech segment.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentSpeakerCharacteristicsInformation
NIEM Element: biom:HealthCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
653
Type-11: Forensic and Investigatory Voice Data
11.037_11: Vocal Segment Speaker Characteristics - Emotional State Code (EMC)
Description:
An integer giving a subjective estimation of the emotional state of the data subject for the data subject across the segments
identified in this subfield. Admissible emotional state codes are given in Table 93 Emotional State Codes in ANSI/NIST-ITL
update 2015. Only one value for this item is allowed across all of the segments identified in this subfield. If emotional state
code “9” or “10” is chosen to indicate “variable” or “other”, additional explanation may be included in the information item
(comments/COM) below.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
See Table 93 Emotional
State Codes from
ANSI/NIST-ITL update 2015.
Code List: EMOTIONAL STATE CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentSpeakerCharacteristicsInformation
NIEM Element: biom:EmotionalStateCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.037_12: Vocal Segment Speaker Characteristics - Vocal Effort Scale Number (VES)
Description:
Reports the subjective, perceived vocal effort of the subject across the identified segments
vocal effort) and 5 (screaming/crying)
Integer between 0 (very low
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ VES ≤ 5, integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentSpeakerCharacteristicsInformation
NIEM Element: biom:VocalEffortValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
654
Type-11: Forensic and Investigatory Voice Data
11.037_13: Vocal Segment Speaker Characteristics - Vocal Style Code (VSC)
Description:
Assesses the subjective predominant vocal style of the data subject across the identified segments. The vocal style code shall
be chosen from Table 94 Vocal Style Codes from ANSI/NIST-ITL update 2015.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
See Table 94 Vocal Style
Codes from ANSI/NIST-ITL
update 2015.
Code List: VOCAL STYLE CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentSpeakerCharacteristicsInformation
NIEM Element: biom:VocalStyleCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.037_14: Vocal Segment Speaker Characteristics - Recording Awareness Indicator (RAI)
Description:
Indicates whether the data subject is aware that a recording is being made. 0 indicates unknown, 1 indicates aware and 2
indicates unaware.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
RAI = 0, 1 or 2
Code List: RECORDING AWARENESS INDICATOR
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentSpeakerCharacteristicsInformation
NIEM Element: biom:RecordingAwarenessCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
655
Type-11: Forensic and Investigatory Voice Data
11.037_15: Vocal Segment Speaker Characteristics - Script Text (SCR)
Description:
Used to give the script used for read, prompted or repeated speech.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentSpeakerCharacteristicsInformation
NIEM Element: biom:ScriptText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.037_16: Vocal Segment Speaker Characteristics - Comments (COM)
Description:
Used to give additional information about the characteristic assessment process, including a description of any characteristic
assessment algorithms used, Notes on any known external stresses applicable to the data subject, and a description of how
the values in the items of this subfield were assigned.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentSpeakerCharacteristicsInformation
NIEM Element: biom:SpeechCharacteristicsCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
656
Type-11: Forensic and Investigatory Voice Data
11.038: Vocal Segment Channel (SCH)
Description:
Describes the transducer and transmission channel within the identified segments. This field shall only be present if Field
11.025: Vocal content / VOC appears in this record.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:SegmentChannelInformation
XML Min/Max: 0 / 600000
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.038_0: Vocal Segment Channel - Subfield: Repeating Sets Of Information Items (SCH_0)
Description:
Describes the transducer and transmission channel within the identified segments.
Only be present if Field 11.025: Vocal
content / VOC appears in this record. A value of 0 in this subfield indicates the segment geographical information in this
subfield is the default value for all segments not specifically identified in other occurrences of this subfield.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
600000
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
657
Type-11: Forensic and Investigatory Voice Data
11.038_1: Vocal Segment Channel - Segment Identifier List (SIL)
Description:
Segment identifiers to which the values in this subfield pertain. A value of 0 in this subfield indicates the segment geographical
information in this subfield shall be considered the default value for all segments not specifically identified in other occurrences
of this subfield. If multiple segments are identified, they are designated as integers in a list. It is mandatory in each subfield.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
1
Occurrence Maximum
600000
Character Types
NS
Special Characters
For Traditional encoding,
the separator character “|”
is used between elements.
This is not applicable to
XML encoding.
Format
n/a
Constraints
List of up to 600000 values;
non-negative integers
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentChannelInformation/biom:SegmentIDList
NIEM Element: biom:SegmentID
XML Min/Max: 1 / 600000
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.038_2: Vocal Segment Channel - Audio Capture Device Code (ACD)
Description:
A code indicating the audio capture device type. It is optional. It is an integer with values given in Table 95 Audio Capture
Device Type Codes in ANSI/NIST-ITL update 2015. A value of “2” indicates that more than one type of microphone is being
used simultaneously to collect the audio signal.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
See Table 95 Audio
Capture Device Codes from
ANSI/NIST-ITL update 2015.
Code List: AUDIO CAPTURE DEVICE CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentChannelInformation
NIEM Element: biom:AudioCaptureDeviceCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
658
Type-11: Forensic and Investigatory Voice Data
11.038_3: Vocal Segment Channel - Microphone Type Code (MTC)
Description:
The third information item is the microphone type code / MTC. It is optional. It is an integer that specifies the transducer type
from Table 96 Microphone Type Codes in ANSI/NIST-ITL update 2015. Transducer arrays using mixed transducer types shall
be designated “other”.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
MTC = 0 , 1, 2, 3 or 4
Code List: TRANSDUCER PRINCIPLE CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentChannelInformation
NIEM Element: biom:TransducerPrincipleCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.038_4: Vocal Segment Channel - Capture Environment Description Text (ENV)
Description:
Describes the acoustic environment of the recording.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentChannelInformation
NIEM Element: biom:AudioCaptureEnvironmentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
659
Type-11: Forensic and Investigatory Voice Data
11.038_5: Vocal Segment Channel - Transducer Distance (DST)
Description:
Specifies the approximate distance in centimeters, rounded to the nearest integer number of centimeters, between the speaker
in the identified segments and the transducer. A value of 0 will be used if the distance is less than one-centimeter.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ DST ≤ 99999, integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentChannelInformation
NIEM Element: biom:TransducerDistanceValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.038_6: Vocal Segment Channel - Acquisition Source Code (AQC)
Description:
Specifies the source from which the voice in the identified segments was received.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
See Table 121 Acquisition
Source from ANSI/NIST-ITL
update 2015.
Code List: ACQUISITION SOURCE CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentChannelInformation
NIEM Element: biom:AcquisitionSourceCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
660
Type-11: Forensic and Investigatory Voice Data
11.038_7: Vocal Segment Channel - Voice Modification Description Text (VMT)
Description:
Unrestricted string for a description of any digital masking between transducer and recording, disguisers or other attempts to
change the voice quality. Any processing techniques used on the recording should be indicated, such as Automated Gain
Control (AGC), noise reduction, etc.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentChannelInformation
NIEM Element: biom:TransductionAlterationDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.038_8: Vocal Segment Channel - Comments (COM)
Description:
Unrestricted string for additional information to identify or describe the transduction and transmission channels of the identified
segments.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:SegmentChannelInformation
NIEM Element: biom:ChannelCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
661
Type-11: Forensic and Investigatory Voice Data
11.051: Comments (COM)
Description:
Unrestricted text string that may contain comments of any type on the Type 11 record as a whole. This field should record any
intellectual property rights associated with any of the segments in the voice recording, any court orders related to the voice
recording and any administrative data not included in other fields.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail
NIEM Element: biom:AudioCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.902: Annotation Information (ANN)
Description:
Listing the operations performed on the original source in order to prepare it for inclusion in a biometric record type.
Repeating sets of information items M↑
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord
NIEM Element: biom:ProcessAnnotation
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
662
Type-11: Forensic and Investigatory Voice Data
11.902_0: Annotated Information - Subfields: Repeating Sets Of Information Items (ANN_0)
Description:
Listing the operations performed on the original source in order to prepare it for inclusion in a biometric record type.
Repeating sets of information items M↑
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
*
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.902_1: Annotation Information - Greenwich Mean Time (GMT)
Description:
This information item is the Greenwich Mean Time (GMT) when the annotation occured. The data is formatted as
YYYYMMDDhhmmssZ, where the Z is indicates the zone description of 0 hours. Time (GMT) units. This time is independent of
the actual time zone where the time and date is recorded.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
YYYYMMDDHHMMSSZ for Traditional Encoding
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessUTCDate/nc:ZuluDateTime
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
663
Type-11: Forensic and Investigatory Voice Data
11.902_2: Annotation Information - Processing Algorithm Name / Version (NAV)
Description:
The second information item of the Type-14 Annotated Information field shall contain an unformatted text string of up to 64
characters identifying the name and version of the processing algorithm or workstation.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessName
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.902_3: Annotation Information - Algorithm Owner (OWN)
Description:
The third information item Type-14 Annotated Information field shall contain an unformatted text string of up to 64 characters
with the contact information for the organization that owns the processing algorithm or latent workstation.
Field Minimum
1
Field Maximum
64
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessOwnerText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
664
Type-11: Forensic and Investigatory Voice Data
11.902_4: Annotation Information - Process Description (PRO)
Description:
The fourth and final information item of the Type-14 Annotated Information field shall contain an unformatted text string of up to
255 characters describing a process or procedure applied to the sample in this Type-XX record.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessDescriptionText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.993: Source Agency Name (SAN)
Description:
The name of the agency referred to in Field 11.004: Source agency / SRC.
Field Minimum
1
Field Maximum
125
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent:
itl:PackageVoiceDataRecord/biom:ForensicInvestigatoryVoiceDetail/biom:BiometricCapture/biom:CaptureOrganization
NIEM Element: nc:OrganizationName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
665
Type-11: Forensic and Investigatory Voice Data
11.994: External Reference File (EFR)
Description:
This conditional field shall be used to enter the URL/URI or other unique reference to a storage location for all digital
representations, if the data is not contained in Field 11.999: Voice record data / DATA. It may be a physical location, as well,
such as for analog recordings. If this field is used, Field 11.999 shall not be set. However, one of the two fields shall be present
in all instances of this record type unless Field 11.003: Audio object descriptor code /AOD is set to a value of 5. It is highly
recommended that the user state the format of the external file in Field 11.051: Comment / COM.
Field Minimum
1
Field Maximum
200
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord
NIEM Element: biom:SourceExternalFileReferenceText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.995: Associated Context (ASC)
Description:
This optional field refers to one or more Type 21 Records with the same ACN. Type 21 Records contain images that are NOT
used to derive the biometric data but that may be relevant to the collection of that data, such as the image of a document
authorizing redaction
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
255
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord
NIEM Element: biom:AssociatedContext
XML Min/Max: 0 / 255
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
666
Type-11: Forensic and Investigatory Voice Data
11.995_0: Associated Context - Subfields: Repeating Sets Of Information Items (ASC_0)
Description:
This optional field refers to one or more Type 21 Records with the same ACN. Type 21 Records contain images that are NOT
used to derive the biometric data but that may be relevant to the collection of that data, such as the image of a document
authorizing redaction
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
255
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.995_1: Associated Context - Associated Context Number (ACN)
Description:
The first information item for the Associated Context field for a particular Record Type-21. This is mandatory for each Field
xx.995, when the field is used. It contains an index to a particular instance of a Type-21 record in the transaction. This same
index value appears in the appropriate instance of Record Type-21 as Field 21.021: Associated context number (CAN). The
value of the CAN shall be a sequentially assigned a positive integer starting from one and incremented by one, not to exceed
255.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
n/a
Special Characters
None
Format
n/a
Constraints
1 ≤ ACN ≤ 255; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:AssociatedContext
NIEM Element: biom:ContextID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
667
Type-11: Forensic and Investigatory Voice Data
11.995_2: Associated Context - Associated Segment Position (ASP)
Description:
The first information item is the associated segment position (ASP). This provides a unique index to a segmentation.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
1 ≤ ASP ≤ 99; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:AssociatedContext
NIEM Element: biom:ImageSegmentID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.996: Hash (HAS)
Description:
Optional field xx.996, is designed for use in Record types 10 and above with a Field xx.999 storing the biometric data. It is
comprised of 64 characters representing hexadecimal values. Thus, each character may be a digit from “0” to “9” or a letter “A”
through “F”. See the latest version of the Federal Information Processing Standard 180, Secure Hash Standard for information
on computing SHA-256 hashes. At the time of this standard’s publication, FIPS 180-37 had been published. It is also possible
to use Field xx.996 to contain the hash for data stored externally, which is referenced in Field 20.994: External file reference
(EFR) and/or Field 21.994: External file reference (EFR). The ability to store files externally is new to this version of the
standard, and is only implemented for the two new record types referred to here. Use of the hash enables the receiver of the
data to perform quick searches of large databases to determine if the data already exist in the database. It is not intended as
an information assurance check. That is handled by Record Type-98: Information assurance record.
Field Minimum
64
Field Maximum
64
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord
NIEM Element: biom:DigitalAudioRecordHashValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
668
Type-11: Forensic and Investigatory Voice Data
11.997: Source Representation (SOR)
Description:
This optional field refers to a representation in Record Type-20 with the same SRN.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord
NIEM Element: biom:SourceInformation
XML Min/Max: 0 / 255
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.997_0: Source Representation - Subfields: Repeating Sets Of Information Items (SOR_0)
Description:
This optional field 13.997 is allowed in biometric data sample Record Types 10 and above that could have the biometric
sample derived from a source representation in Record Type-20. The biometric data is stored in Field 13.999.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
255
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
669
Type-11: Forensic and Investigatory Voice Data
11.997_1: Source Representation - Source Representation Number (SRN)
Description:
This is the first information item and is mandatory for each Field 11.997. It contains an index to a particular instance of a Type20 record in the transaction. This same index value appears in the appropriate instance of Record Type-20 as Field 20.021:
Source representation number / SRN. The value of the SRN shall be a sequentially assigned a positive integer starting from
one and incremented by one, not to exceed 255.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ SRN ≤ 255; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord/biom:SourceInformation
NIEM Element: biom:SourceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
11.999: Data - Voice Data (DATA)
Description:
If this field is used, Field 11.994: External file reference / EFR shall not be set. One of the two fields shall be present in this
record unless Field 11.003: Audio object descriptor code /AOD has a value of 5.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Base64
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Acti ve
XML Parent: itl:PackageVoiceDataRecord
NIEM Element: nc:Base64BinaryObject
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
670
Type-13: Variable-Resolution Latent Friction Ridge Image
13.001: Record Header (LEN)
Description:
The record header appears as the first field (xx.001) in each Record Type. It contains information particular to the encoding
format chosen, in order to enable proper reading of the record. In Traditional encoding, this field contains the record length in
bytes (including all information separators). In NIEM-conformant XML encoding, this field contains the RecordCategoryCode,
which is the numeric representation of the Record Type.
Field Minimum
T = 4; X = 1
Field Maximum
T = 8; X = 2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.002: Information Designation Character (IDC)
Description:
Each of the records present in a transaction, with the exception of the Type-1 record, shall include a field (xx.002) containing
the information designation character / IDC. The value of the IDC shall be a sequentially assigned positive integer starting
from zero and incremented by one up to a maximum of 99. IDC references are stated in Type-1 Field 1.003 Transaction
content (CNT) and shall be used to relate information items in the CNT field of the Type-1 record to the other records in the
transaction. Two or more records may share a single IDC solely to identify and link together records that pertain to different
representations of the same biometric trait.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ IDC ≤ 99; integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord
NIEM Element: biom:ImageReferenceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
671
Type-13: Variable-Resolution Latent Friction Ridge Image
13.003: Impression Type (IMP)
Description:
This mandatory field shall indicate the manner by which the friction ridge print was obtained.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
4 ≤ IMP ≤ 7 or 12 ≤ IMP ≤
15 or IMP = 28 or 32 ≤ IMP
≤ 39; integer; see Table 8 of
ANSI/NIST-ITL update 2015.
Code List: FRICTION RIDGE IMPRESSION CODES
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail
NIEM Element: itl:FrictionRidgeImpressionCaptureCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.004: Source Agency (SRC)
Description:
This is the identifier of the agency that actually created the record and supplied the information contained in it.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:CaptureOrganization
NIEM Element: nc:OrganizationIdentification/nc:IdentificationID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
672
Type-13: Variable-Resolution Latent Friction Ridge Image
13.005: Latent Capture Date (LCD)
Description:
This mandatory field shall contain the date that the latent biometric data contained in the record was captured.
Field Minimum
Field Maximum
Dependent upon encoding Dependent upon encoding
Character Types
N
Special Characters
Dependent upon encoding
Occurrence Minimum
1
Occurrence Maximum
1
Format
T = YYYYMMDD; X =
Constraints
Dependent upon encoding.
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLocatio
NIEM Element: biom:CaptureDate/nc:Date
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.006: Horizontal Line Length (HLL)
Description:
HLL defines the number of pixels contained on a single horizontal line of the image. The maximum horizontal size is limited to
65,535 pixels in Record Types-4 and 8, and to 99,999 for other record types. The minimum value is 10 pixels. The total image
size (HLL times VLL) must be able to be accommodated in Field xx.001 for Traditional encoding.
Field Minimum
2
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
10 ≤ HLL ≤ 99999; positive
integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail
NIEM Element: biom:HorizontalLineLengthPixelQuantity
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
673
Type-13: Variable-Resolution Latent Friction Ridge Image
13.007: Vertical Line Length (VLL)
Description:
VLL defines the number of pixels contained in a single vertical line in the image. The maximum vertical size is limited to 65,535
pixels in Record Types-4 and 8, and to 99,999 for other record types. The minimum value is 10 pixels. The total image size
(HLL times VLL) must be able to be accommodated in Field xx.001 for Traditional encoding.
Field Minimum
2
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
10 ≤ VLL ≤ 99999; positive
integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail
NIEM Element: biom:VerticalLineLengthPixelQuantity
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.008: Scale Units (SLC)
Description:
The image sampling frequency (pixel density). A value of “1” shall indicate pixels per inch. A value of “2” shall indicate pixels
per centimeter. A value of “0” in this field indicates that no scale is provided, and the quotient of THPS/TVPS shall provide the
pixel aspect ratio.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
SLC = 0, 1 or 2
Code List: SCALE UNIT CODES
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail
NIEM Element: biom:ImageScaleUnitsCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
674
Type-13: Variable-Resolution Latent Friction Ridge Image
13.009: Transmitted Horizontal Pixel Scale (THPS)
Description:
This is the integer pixel density used in the horizontal direction of the image if SLC has a value of “1” or “2”. If SLC has a value
of “0”, this information item shall contain the horizontal component of the pixel aspect ratio, up to 5 integer digits. For example,
if the SLC value = 1, then the value of THPS could be ‘1000’ for a 1000 ppi sensor. When using certain formats, such as PNG,
conversion from ppm (or other scales) may result in a decimal value. Since these fields require integer values, rounding should
be used. For example with the values 1.3, 1.5 and 1.8 the resulting THPS values would be 1, 2, and 2. Any value greater than
x.0 and less than x.5 would be rounded down to x, regardless of the number of significant digits to the right of the decimal.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail
NIEM Element: biom:ImageHorizontalPixelDensityValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.01: Transmitted Vertical Pixel Scale (TVPS)
Description:
This is the integer pixel density used in the vertical direction of the image if SLC has a value of “1” or “2”. If SLC has a value of
“0”, this information item shall contain the vertical component of the pixel aspect ratio, up to 5 integer digits. If SLC is 1 or 2,
then TVPS shall equal THPS. When using certain formats, such as PNG, conversion from ppm (or other scales) may result in
a decimal value. Since these fields require integer values, rounding should be used. For example with the values 1.3, 1.5 and
1.8 the resulting THPS values would be 1, 2, and 2. Any value greater than x.0 and less than x.5 would be rounded down to x,
regardless of the number of significant digits to the right of the decimal.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail
NIEM Element: biom:ImageVerticalPixelDensityValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
675
Type-13: Variable-Resolution Latent Friction Ridge Image
13.011: Compression Algorithm (CGA)
Description:
This is a mandatory field. It shall specify the algorithm used to compress the transmitted color or grayscale images. See Table
19 Compression codes of ANSI/NIST-ITL update 2015 for labels.
Field Minimum
3
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
CGA = NONE, JPEGL,
JP2L, or PNG
Code List: COMPRESSION CODES
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail
NIEM Element: biom:ImageCompressionAlgorithmCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.012: Bits Per Pixel (BPX)
Description:
This ASCII field shall contain the number of bits used to represent a pixel. This field shall contain an entry of “8” for normal
grayscale values of “0” to “255” or each RGB color component. Any entry in this field greater than “8” shall represent a
grayscale or color pixel component with increased precision.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
8 ≤ BPX ≤ 99
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail
NIEM Element: biom:ImageBitsPerPixelQuantity
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
676
Type-13: Variable-Resolution Latent Friction Ridge Image
13.013: Friction Ridge Generalized Position (FGP)
Description:
This field is mandatory. Each subfield shall contain one possible finger, palm or plantar position that may match the latent
image, up to a maximum of 6 possibilities. The code “0” shall be used to reference every finger position from 1 to 10, 16 and
17. The code “20” for “Unknown palm” shall be used to reference every listed palm print position. The code “60” for “Unknown
sole” shall be used for every listed plantar position. Code “18” shall be used if it is unknown whether the print is from a hand or
foot. Code “19” shall be used for a latent image that includes substantive portion of the medial or proximal segments of a
finger, or the extreme tip of a fingerprint. If code 19 is used, fields 13.014 and 13.015 shall be used. See Look Up Codes for
valid entries. See Table Table 9 of the ANSI/NIST-ITL update 2015 for labels.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
n/a
Code List: FRICTION RIDGE GENERALIZED POSITION CODES
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail
NIEM Element: biom:LatentFrictionRidgePositionCode
XML Min/Max: 1 / 6
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.013_0: Friction Ridge Generalized Position - Subfield: Repeating Sets Of Information Items (FGP_0)
Description:
This field is mandatory. Each subfield shall contain one possible finger, palm or plantar position that may match the latent
image, up to a maximum of 6 possibilities. The code “0” shall be used to reference every finger position from 1 to 10, 16 and
17. The code “20” for “Unknown palm” shall be used to reference every listed palm print position. The code “60” for “Unknown
sole” shall be used for every listed plantar position. Code “18” shall be used if it is unknown whether the print is from a hand or
foot. Code “19” shall be used for a latent image that includes substantive portion of the medial or proximal segments of a
finger, or the extreme tip of a fingerprint. If code 19 is used, fields 13.014 and 13.015 shall be used. See Look Up Codes for
valid entries.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
6
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ FGP ≤ 10, or 16 ≤ FGP
≤ 38, or 60 ≤ FGP ≤ 79 or
81 ≤ FGP ≤ 86; integer
Code List: FRICTION RIDGE GENERALIZED POSITION CODES
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: New Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
677
Type-13: Variable-Resolution Latent Friction Ridge Image
13.014: Search Position Descriptors (SPD)
Description:
Shall be present if and only if the finger position code "19" appears in Field 13.013. It is used to narrow the search of the latent
image in this record against a database. The lack of an XML element is a structural anomaly. There is no element to represent
the Field 13.014, and instead each information item repeats. This anomaly is retained for backward compatibility purposes.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: dod-ebts:FingerImpressionImage
NIEM Element: biom:FingerprintImageMajorCasePrint
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.014_0: Search Position Descriptors - Subfield: Repeating Sets Of Information Items (SPD_0)
Description:
Shall be present if and only if the finger position code "19" appears in Field 13.013. It is used to narrow the search of the latent
image in this record against a database.
The lack of an XML element is a structural anomaly. There is no element to
represent the Field 13.014, and instead each information item repeats. This anomaly is retained for backward compatibility
purposes.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
9
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: New Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
678
Type-13: Variable-Resolution Latent Friction Ridge Image
13.014_1: Search Position Descriptors - Probable Decimal Finger Position Code (PDF)
Description:
The first information item is the probable decimal finger position code / PDF taken from Table 9 of the ANSI/NIST-ITL update
2015.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ PDF ≤ 10, or PDF = 16
or 17
Code List: FRICTION RIDGE GENERALIZED POSITION CODES
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:FingerprintImageMajorCasePrint
NIEM Element: biom:FingerPositionCode
XML Min/Max: 1 / 9
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.014_2: Search Position Descriptors - Finger Image Code (FIC)
Description:
The second information item is finger image code(FIC). Latent images of full length fingers use codes FV1 through FV4. Other
allowable codes are EJI, TIP, PRX, DST and MED. See Table 10 of the ANSI/NIST-ITL update 2015 for valid entries.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
FIC = EJI, TIP, FV1, FV2,
FV3, FV4, PRX, DST or
MED
Code List: PRINT POSITION DESCRIPTORS
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:FingerprintImageMajorCasePrint
NIEM Element: biom:MajorCasePrintCode
XML Min/Max: 1 / 9
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
679
Type-13: Variable-Resolution Latent Friction Ridge Image
13.015: Print Position Coordinates (PPC)
Description:
This field may be present if and only if the finger position code “19” appears in Field 13.013: Friction ridge generalized position
/ FGP. It is an optional field. Individual full finger or segment definitions may be entered as separate subfields. For the case of
a fingertip, the first information item shall be “TIP”, and the second information item shall be “NA”. When used, this field shall
consist of six (6) mandatory information items describing the type or portion of the image contained in this record and its
location within an EJI. This information will describe either the location of the entire joint image, one full finger view, or
segment. Individual full finger or segment definitions may be repeated as repeating sets of information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:FingerprintImageMajorCasePrint
NIEM Element: biom:MajorCasePrintSegmentOffset
XML Min/Max: 0 / 12
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.015_0: - Subfield: Repeating Sets Of Information Items (PPC_0)
Description:
This field may be present if and only if the finger position code “19” appears in Field 13.013: Friction ridge generalized position
(FGP). It is an optional field. Individual full finger or segment definitions may be entered as separate subfields. For the case of
a fingertip, the first information item shall be “TIP”, and the second information item shall be “NA”. When used, this field shall
consist of six (6) mandatory information items describing the type or portion of the image contained in this record and its
location within an EJI. This information will describe either the location of the entire joint image, one full finger view, or
segment. Individual full finger or segment definitions may be repeated as repeating sets of information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
12
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: New Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
680
Type-13: Variable-Resolution Latent Friction Ridge Image
13.015_1: Print Position Coordinates - Full Finger View (FVC)
Description:
The first information item is the full finger view / FVC with values of “FV1” through “FV4”. Values of “FV1” to “FV4” specify the
perspective for each full finger view. For a fingertip, the first information item shall be “TIP”. FVC will contain the code “NA” if
only a proximal, distal, or medial segment is available.
Field Minimum
2
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
FVC = NA, TIP, FV1, FV2,
FV3 or FV4; see Look Up
Codes
Code List: PRINT POSITION DESCRIPTORS
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:FingerprintImageMajorCasePrint/biom:MajorCasePrintSegmentO
ffset
NIEM Element: biom:SegmentFingerViewCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.015_2: Print Position Coordinates - Location of Segment (LOS)
Description:
The second information item is used to identify the location of a segment / LOS within a full finger view. LOS will contain the
not applicable code “NA” if the image portion refers to a full finger view, tip or to the entire joint image locations. Otherwise, it
shall contain “PRX”, “DST”, “MED” for a proximal, distal, or medial segment, respectively.
Field Minimum
2
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
LOS = NA, PRX, DST or
MED; see Look Up Codes
Code List: PRINT POSITION DESCRIPTORS
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:FingerprintImageMajorCasePrint/biom:MajorCasePrintSegmentO
ffset
NIEM Element: biom:SegmentLocationCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
681
Type-13: Variable-Resolution Latent Friction Ridge Image
13.015_3: Print Position Coordinates - Left Horizontal Coordinate (LHC)
Description:
The third information item is the left horizontal coordinate / LHC. It is the horizontal offset in pixels to the left edge of the
bounding box relative to the origin positioned in the upper left corner of the image.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ LHC < HLL; integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:FingerprintImageMajorCasePrint/biom:MajorCasePrintSegmentO
ffset/biom:FingerprintCoordinate
NIEM Element: biom:SegmentLeftHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.015_4: Print Position Coordinates - Right Horizontal Coordinate (RHC)
Description:
The fourth information item is the right horizontal coordinate / RHC. It is the horizontal offset in pixels to the right edge of the
bounding box relative to the origin positioned in the upper left corner of the image.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
LHC < RHC < HLL; integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:FingerprintImageMajorCasePrint/biom:MajorCasePrintSegmentO
ffset/biom:FingerprintCoordinate
NIEM Element: biom:SegmentRightHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
682
Type-13: Variable-Resolution Latent Friction Ridge Image
13.015_5: Print Position Coordinates - Top Vertical Coordinate (TVC)
Description:
This information item is vertical offset (pixel counts down) to the top of the bounding box.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ TVC < VLL; integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:FingerprintImageMajorCasePrint/biom:MajorCasePrintSegmentO
ffset/biom:FingerprintCoordinate
NIEM Element: biom:SegmentTopVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.015_6: Print Position Coordinates - Bottom Vertical Coordinate (BVC)
Description:
The sixth information item is the bottom vertical coordinate / BVC. It is the vertical offset from the upper left corner of the image
down to the bottom of the bounding box. It is counted in pixels.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
TVC < BVC < VLL; integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:FingerprintImageMajorCasePrint/biom:MajorCasePrintSegmentO
ffset/biom:FingerprintCoordinate
NIEM Element: biom:SegmentBottomVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
683
Type-13: Variable-Resolution Latent Friction Ridge Image
13.016: Scanned Horizontal Pixel Scale (SHPS)
Description:
This ASCII field shall specify the horizontal pixel density used for scanning providing the SLC field contains a "1" or a "2".
Otherwise, it indicates the horizontal component of the pixel aspect ratio.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail
NIEM Element: biom:CaptureHorizontalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.017: Scanned Vertical Pixel Scale (SVPS)
Description:
This ASCII field shall specify the vertical pixel density used for scanning providing the SLC field contains a "1" or a "2".
Otherwise, it indicates the vertical component of the pixel aspect ratio.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail
NIEM Element: biom:CaptureVerticalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
684
Type-13: Variable-Resolution Latent Friction Ridge Image
13.018: Ruler or Scale Presence (RSP)
Description:
This optional field allows the user to state whether a ruler or other known scale is present in the image.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
None
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail
NIEM Element: biom:RulerScalePresenceInformation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
13.018_1: Ruler or Scale Presence - Ruler or Scale Units (RSU)
Description:
The first information item, ruler or scale units / RSU, indicates the units of measurement visible on the ruler or measurement
scale. IN = inches, MM = millimeters or BOTH = both inches and millimeters.
Field Minimum
2
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
RSP = IN, MM, BOTH; See
Look Up Codes
Code List: RULER OR SCALE UNIT CODES
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:RulerScalePresenceInformation
NIEM Element: biom:RulerScaleUnitCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
685
Type-13: Variable-Resolution Latent Friction Ridge Image
13.018_2: Ruler or Scale Presence - Ruler or Scale Make (RSM)
Description:
The second information item, ruler or scale make (RSM), lists the maker of the ruler or scale (if known).
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:RulerScalePresenceInformation
NIEM Element: biom:RulerScaleMakeText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
13.018_3: Ruler or Scale Presence - Ruler or Scale Model (RSO)
Description:
The third information item, ruler or scale model (RSO), lists the model of the ruler or scale (if known).
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:RulerScalePresenceInformation
NIEM Element: biom:RulerScaleModelText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
686
Type-13: Variable-Resolution Latent Friction Ridge Image
13.018_4: Ruler or Scale Presence - Standard Fingerprint Form Number (RSF)
Description:
The fourth information item, standard fingerprint form number (RSF) permits entry of a standard fingerprint form number such
as FD-249, FD-258 or C-216C. RSF is present if and only if none of the other three information items (RSU, RSM, or RSO) are
specified.
Field Minimum
1
Field Maximum
99
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail
NIEM Element: biom:StandardFingerprintFormNumberText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
13.019: Resolution Method (REM)
Description:
This optional field states the method used for determining the pixel density of the image. The second through the seventh
information items are mandatory if MDR = RULER and are optional if MDR = FORM. They shall not be used for other values of
MDR. When the known scale coordinates are used, the resolution can be calculated as the distance in pixels between points
A and B divided by KSL. The pixel counts used in SXA, SYA, SXB, SYB are zero-based. The top left pixel has coordinates
(0,0). If the transmitted pixel density of an image in Field 13.009: Transmitted horizontal pixel scale / THPS and Field 13.010:
Transmitted vertical pixel scale / TVPS differs from the scanned (original) pixel density stated in Field 13.016: Scanned
horizontal pixel scale / SHPS and Field 13.017: Scanned vertical pixel scale / SVPS, then the values in this field are with
respect to the scanned pixel density and shall not be recalculated to correspond to the transmitted pixel density.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail
NIEM Element: biom:ResolutionMethodInformation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
687
Type-13: Variable-Resolution Latent Friction Ridge Image
13.019_1: Resolution Method - Means of Determining Resolution (MDR)
Description:
The first information item, means of determining resolution / MDR, specifies whether the resolution is calculated (from a ruler or
known scale), estimated (by a human or computer), or is from a known source (such as a flatbed scanner or standard form).
Enter the CODE from Table 103 Means of determining resolution in ANSI/NIST-ITL update 2015.
Field Minimum
1
Field Maximum
9
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AS
Special Characters
None
Format
n/a
Constraints
MDR = FLATBED, FIXED,
RULER, FORM, ESTHUMAN, EST-AUTO
Code List: MEANS OF DETERMINING RESOLUTION CODES
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ResolutionMethodInformation
NIEM Element: biom:ResolutionMeansCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
13.019_2: Resolution Method - Known Scale Length (KSL)
Description:
The second information item, known scale units (KSL), specifies the length of the known scale from point A to point B. It may
contain a period.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Period
Format
n/a
Constraints
0.01 ≤ KSL ≤ 999.00;
maximum of two digits to
right of decimal
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ResolutionMethodInformation
NIEM Element: biom:ResolutionScaleLengthValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
688
Type-13: Variable-Resolution Latent Friction Ridge Image
13.019_3: Resolution Method - Known Scale Units (KSU)
Description:
The third information item, known scale units (KSU) indicates whether the known scales units are in inches or millimeters. IN =
inches, MM = millimeters.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
KSU = IN or MM
Code List: RULER OR SCALE UNIT CODES
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ResolutionMethodInformation
NIEM Element: biom:ResolutionScaleUnitCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
13.019_4: Resolution Method - Known Scale X Coordinate for Point A (SXA)
Description:
The fourth information item, known scale x coordinate for point A (SXA) is expressed in number of pixels from the left of the
image.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
Integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ResolutionMethodInformation
NIEM Element: biom:ResolutionScaleXCoordinateAValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
689
Type-13: Variable-Resolution Latent Friction Ridge Image
13.019_5: Resolution Method - Known Scale Y Coordinate for Point A (SYA)
Description:
The fifth information item, known scale y coordinate for point A (SYA) is expressed in number of pixels from the top of the
image.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
Integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ResolutionMethodInformation
NIEM Element: biom:ResolutionScaleYCoordinateAValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
13.019_6: Resolution Method - Known Scale X Coordinate for Point B (SXB)
Description:
The sixth information item, known scale x coordinate for point B (SXB) is expressed in number of pixels from the left of the
image.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
Integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ResolutionMethodInformation
NIEM Element: biom:ResolutionScaleXCoordinateBValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
690
Type-13: Variable-Resolution Latent Friction Ridge Image
13.019_7: Resolution Method - Known Scale Y Coordinate for Point B (SYB)
Description:
The seventh information item, known scale y coordinate for point B (SYB) is expressed in number of pixels from the top of the
image.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
Integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ResolutionMethodInformation
NIEM Element: biom:ResolutionScaleYCoordinateBValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
13.019_8: Resolution Method - Comment (COM)
Description:
The eighth information item, comment (COM), is a UNICODE text comment or description provided by the examiner about the
resolution method.
Field Minimum
1
Field Maximum
99
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
Integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ResolutionMethodInformation
NIEM Element: biom:ResolutionCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
691
Type-13: Variable-Resolution Latent Friction Ridge Image
13.020: Comment (COM)
Description:
The optional Comment field appears in many record types and may be used to insert free text information. It is not reserved
exclusively for log-related information but has historically often been used for this purpose. It is limited to a maximum of 126
characters. This maximum size was established in order to maintain consistency across encodings. The maximum size differed
in the 2007 and 2008 versions of the standard.
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail
NIEM Element: biom:ImageCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.024: Latent Quality Metric (LQM)
Description:
This optional field is used to specify one or more different metrics of latent image quality score data for the image stored in this
record.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail
NIEM Element: biom:FrictionRidgeImageQuality
XML Min/Max: 0 / 9
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
692
Type-13: Variable-Resolution Latent Friction Ridge Image
13.024_0: Latent Quality Metric (LQM_0)
Description:
This optional field is used to specify one or more different metrics of latent image quality score data for the image stored in this
record.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
9
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: New Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.024_1: Latent Quality Metric - Friction Ridge Metric Position (FRMP)
Description:
The first information item is the entry in Field 13.013: Friction ridge generalized position (FGP). This information item is called
the friction ridge metric position (FRMP) to differentiate it from FGP.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
See Table 9 Friction ridge
position code &
recommended image
dimensions from
ANSI/NIST-ITL update 2015.
Code List: FRICTION RIDGE GENERALIZED POSITION CODES
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:FrictionRidgeImageQuality
NIEM Element: biom:LatentFrictionRidgePositionCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
693
Type-13: Variable-Resolution Latent Friction Ridge Image
13.024_2: Latent Quality Metric - Quality Value (QVU)
Description:
This information item shall contain the integer image quality score between 0 and 100 (inclusive) assigned to the image data
by a quality algorithm. Higher values indicate better quality. An entry of “255” shall indicate a failed attempt to calculate a
quality score. An entry of “254” shall indicate that no attempt to calculate a quality score was made.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ QVU ≤ 100 or QVU =
254 or 255; integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:FrictionRidgeImageQuality
NIEM Element: biom:QualityValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.024_3: Latent Quality Metric - Algorithm Vendor Identification (QAV)
Description:
This information item shall specify the ID of the vendor of the quality algorithm used to calculate the quality score. This 4-digit
hex value is assigned by IBIA and expressed as four ASCII characters. The IBIA shall maintain the Vendor Registry of CBEFF
Biometric Organizations that will map the value in this field to a registered organization.
Field Minimum
4
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
0000 ≤ QAV ≤ FFFF
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:FrictionRidgeImageQuality
NIEM Element: biom:QualityAlgorithmVendorID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
694
Type-13: Variable-Resolution Latent Friction Ridge Image
13.024_4: Latent Quality Metric - Algorithm Product Identification (QAP)
Description:
This information item shall specify a numeric product code assigned by the vendor of the quality algorithm, which may be
registered with the IBIA, but it is not required to be registered. It indicates which of the vendor’s algorithms was used in the
calculation of the quality score. This field contains the ASCII representation of the integer product code and should be within
the range 1 to 65535.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ QAP ≤ 65535; positive
integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:FrictionRidgeImageQuality
NIEM Element: biom:QualityAlgorithmProductID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.046: Image Subject Condition (SUB)
Description:
This field is optional. This field is particularly useful if the image is obtained from a deceased person. However, its use is not
limited to such circumstances. Some implementation domains support the submission of fingerprints taken from deceased
individuals as latent prints, due to the quality of the friction ridges and the resulting images. In such cases, SSC is specified as
D. For latent images taken from a surface, the value is typically X.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail
NIEM Element: biom:SubjectExistentialDetails
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
695
Type-13: Variable-Resolution Latent Friction Ridge Image
13.046_1: Image Subject Condition - Subject Status Code (SSC)
Description:
The first information item is mandatory if this field is present. It is subject status code (SSC). Possible entries are: X = Status of
individual unknown; A = Data obtained from a living person – such as a victim or person unable to identify themselves; or D =
Data obtained from a non-living person (deceased)
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
SSC = X, A, or D
Code List: SUBJECT STATUS CODES
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:SubjectExistentialDetails
NIEM Element: biom:SubjectExistentialStatusCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
13.046_2: Image Subject Condition - Subject Body Status Code (SBSC)
Description:
The second information item shall be entered if and only if SSC is D. It is subject body status code (SBSC). Its purpose is to
indicate whether the information relates to an entire corpse or a separate body part. The numeric value is selected from the
descriptors below: 1 = Whole or 2 = Fragment
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
SBSC = 1 or 2
Code List: SUBJECT BODY STATUS CODES
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:SubjectExistentialDetails
NIEM Element: biom:SubjectBodyStatusCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
696
Type-13: Variable-Resolution Latent Friction Ridge Image
13.046_3: Image Subject Condition - Subject Body Class Code (SBCC)
Description:
The third information item shall be entered if and only if SSC is D. It is subject body class code (SBCC). The numeric value is
selected from the descriptors below: 1 = Natural Tissue or 2 = Decomposed
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
SBCC = 1 or 2
Code List: SUBJECT BODY CLASS CODES
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:SubjectExistentialDetails
NIEM Element: biom:SubjectBodyClassCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
13.047: Capture Organization Name (CON)
Description:
This field is optional. Note that this can be different from the agency entered in Field 13.004: Source agency (SRC) and Field
13.993: Source agency name (SAN). SRC and SAN describe the agency that created the record. Since the record may have
been forwarded by another agency to the final destination, Field 1.008: Originating agency identifier (ORI) is used to indicate
the transmitting organization. In many implementation domains, there are a limited number of transmission organizations that
can send data. Therefore, the agency listed in SRC may send the transaction to another location that has access rights to the
final destination. This intermediary may add information to the transaction, as well. The final transmitting organization code is
listed in Field 1.008: Originating agency identifier (ORI). Its name may be entered in Originating agency name (OAN) in Field
1.017: Agency names (ANM).
Field Minimum
1
Field Maximum
1000
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:CaptureOrganization
NIEM Element: nc:OrganizationUnitName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
697
Type-13: Variable-Resolution Latent Friction Ridge Image
13.200-13.900: User-Defined Fields (UDF)
Description:
These fields are user-definable fields. Their size and content shall be defined by the user and be in accordance with the
receiving agency.
Field Minimum
user-defined
Field Maximum
user-defined
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
user-defined
Special Characters
user-defined
Format
Constraints
user-defined
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord
NIEM Element: itl:UserDefinedFields
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
13.901: Friction Ridge Capture Technology (FCT)
Description:
This is an optional field. It is a two-digit code from signifying the type of technology that was used to capture the print for
transmission. See Section 7.7.4.5 of ANSI/NIST-ITL update 2015 for more detail and the meanings of the codes. For latent
prints conveyed in Type-13 records, the only valid codes are: 0, 18, 19, 20, 21 and 22.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
FCT = 0, 18, 19, 20, 21 or
22
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail
NIEM Element: biom:FrictionRidgeCaptureTechnologyCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
698
Type-13: Variable-Resolution Latent Friction Ridge Image
13.902: Annotated Information (ANN)
Description:
This is an optional field, listing the operations performed on the original source in order to prepare it for inclusion in a biometric
record type.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord
NIEM Element: biom:ProcessAnnotation
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.902_0: Annotated Information - Subfield: Repeating Sets Of Information Items (ANN_0)
Description:
This is an optional field, listing the operations performed on the original source in order to prepare it for inclusion in a biometric
record type.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
*
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: New Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
699
Type-13: Variable-Resolution Latent Friction Ridge Image
13.902_1: Annotated Information - Greenwich Mean Time (GMT)
Description:
This information item is the Greenwich Mean Time (GMT) when the annotation occured. The data is formatted as
YYYYMMDDhhmmssZ, where the Z is indicates the zone description of 0 hours. Time (GMT) units. This time is independent of
the actual time zone where the time and date is recorded.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
YYYYMMDDHHMMSSZ for Traditional Encoding
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessUTCDate/nc:DateTime
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.902_2: Annotated Information - Processing Algorithm Name / Version (NAV)
Description:
The second information item of the Type-14 Annotated Information field shall contain an unformatted text string of up to 64
characters identifying the name and version of the processing algorithm or workstation.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessName
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
700
Type-13: Variable-Resolution Latent Friction Ridge Image
13.902_3: Annotated Information - Algorithm Owner (OWN)
Description:
The third information item Type-14 Annotated Information field shall contain an unformatted text string of up to 64 characters
with the contact information for the organization that owns the processing algorithm or latent workstation.
Field Minimum
1
Field Maximum
64
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessOwnerText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.902_4: Annotated Information - Process Description (PRO)
Description:
The fourth and final information item of the Type-14 Annotated Information field shall contain an unformatted text string of up to
255 characters describing a process or procedure applied to the sample in this Type-XX record.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessDescriptionText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
701
Type-13: Variable-Resolution Latent Friction Ridge Image
13.903: Device Unique Identifier (DUI)
Description:
The DUI shall contain a string uniquely identifying the device or source of the data. This field shall be one of: Host PC MAC
address, identified by the first character “M”, or Host PC processor ID, identified by the first character “P”. Note: ANSI/NIST ITL
1-2011 has deleted the options for “Serial number or No serial number” from Field 17.017, since it is available in the Make /
Model / Serial Number field.
Field Minimum
13
Field Maximum
16
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
Any
Format
n/a
Constraints
first character = M or P
Code List: DEVICE UNIQUE IDENTIFIER CODES
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.904: Make/Model/Serial Number (MMS)
Description:
The MMS contains the make, model and serial number for the capture device. It shall consist of three information items. Each
information item shall be 1 to 50 characters. Any or all information items may indicate that information is unknown with the
value “0”.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
702
Type-13: Variable-Resolution Latent Friction Ridge Image
13.904_1: Make/Model/Serial Number - Make (MAK)
Description:
The name of the manufacturer for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceMakeText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.904_2: Make/Model/Serial Number - Model (MOD)
Description:
The model number for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceModelText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
703
Type-13: Variable-Resolution Latent Friction Ridge Image
13.904_3: Make/Model/Serial Number - Serial Number (SER)
Description:
The serial number for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceSerialNumberText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.993: Source Agency Name (SAN)
Description:
This is an optional field. It may contain up to 125 Unicode characters. It is the name of the agency referenced in Field 13.004:
Source agency / SRC.
Field Minimum
1
Field Maximum
125
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:CaptureOrganization
NIEM Element: nc:OrganizationName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
704
Type-13: Variable-Resolution Latent Friction Ridge Image
13.994: External File Reference (EFR)
Description:
This conditional field shall be used to enter the URL/URI or other unique reference to a storage location for all digital
representations, if the data is not contained in Field 13.999: Latent friction ridge image / DATA. If this field is used, Field 13.999
shall not be set. However, one of the two fields shall be present in all instances of this record type. It is highly recommended
that the user state the format of the external file in Field 13.020: Comment / COM.
Field Minimum
1
Field Maximum
200
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord
NIEM Element: biom:SourceExternalFileReferenceText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
13.995: Associated Context (ASC)
Description:
This optional field refers to one or more Type 21 Records with the same ACN. Type 21 Records contain images that are NOT
used to derive the biometric data in Field 13.999: Latent friction ridge image (DATA) but that may be relevant to the collection
of that data, such as general scenes of the area where a latent print was found.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord
NIEM Element: biom:AssociatedContext
XML Min/Max: 0 / 255
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
705
Type-13: Variable-Resolution Latent Friction Ridge Image
13.995_0: Associated Context - Subfield: Repeating Sets Of Information Items (ASC_0)
Description:
This optional field refers to one or more Type 21 Records with the same ACN. Type 21 Records contain images that are NOT
used to derive the biometric data in Field 13.999: Latent friction ridge image (DATA) but that may be relevant to the collection
of that data, such as general scenes of the area where a latent print was found.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
255
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: New Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.995_1: Associated Context - Associated Context Number (ACN)
Description:
The first information item for the Associated Context field for a particular Record Type-21. This is mandatory for each Field
xx.995, when the field is used. It contains an index to a particular instance of a Type-21 record in the transaction. This same
index value appears in the appropriate instance of Record Type-21 as Field 21.021: Associated context number (CAN). The
value of the CAN shall be a sequentially assigned a positive integer starting from one and incremented by one, not to exceed
255.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
n/a
Special Characters
None
Format
n/a
Constraints
1 ≤ ACN ≤ 255; positive
integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:AssociatedContext
NIEM Element: biom:ContextID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
706
Type-13: Variable-Resolution Latent Friction Ridge Image
13.995_2: Associated Context - Associated Segment Position (ASP)
Description:
The first information item is the associated segment position (ASP). This provides a unique index to a segmentation.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
1 ≤ ASP ≤ 99; positive
integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:AssociatedContext
NIEM Element: biom:ImageSegmentID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.996: Hash (HAS)
Description:
Optional field xx.996, is designed for use in Record types 10 and above with a Field xx.999 storing the biometric data. It is
comprised of 64 characters representing hexadecimal values. Thus, each character may be a digit from “0” to “9” or a letter “A”
through “F”. See the latest version of the Federal Information Processing Standard 180, Secure Hash Standard for information
on computing SHA-256 hashes. At the time of this standard’s publication, FIPS 180-37 had been published. It is also possible
to use Field xx.996 to contain the hash for data stored externally, which is referenced in Field 20.994: External file reference
(EFR) and/or Field 21.994: External file reference (EFR). The ability to store files externally is new to this version of the
standard, and is only implemented for the two new record types referred to here. Use of the hash enables the receiver of the
data to perform quick searches of large databases to determine if the data already exist in the database. It is not intended as
an information assurance check. That is handled by Record Type-98: Information assurance record.
Field Minimum
64
Field Maximum
64
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord
NIEM Element: biom:ImageHashValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
707
Type-13: Variable-Resolution Latent Friction Ridge Image
13.997: Source Representation (SOR)
Description:
This optional field refers to a representation in Record Type-20 with the same SRN from which the data in Field 13.999: Latent
friction ridge image (DATA) was derived.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord
NIEM Element: biom:SourceInformation
XML Min/Max: 0 / 255
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.997_0: Source Representation - Subfield: Repeating Sets Of Information Items (SOR_0)
Description:
This optional field 13.997 is allowed in biometric data sample Record Types 10 and above that could have the biometric
sample derived from a source representation in Record Type-20. The biometric data is stored in Field 13.999.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
255
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: New Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
708
Type-13: Variable-Resolution Latent Friction Ridge Image
13.997_1: Source Representation - Source Representation Number (SRN)
Description:
This is the first information item and is mandatory for each Field 13.997. It contains an index to a particular instance of a Type20 record in the transaction. This same index value appears in the appropriate instance of Record Type-20 as Field 20.021:
Source representation number / SRN. The value of the SRN shall be a sequentially assigned a positive integer starting from
one and incremented by one, not to exceed 255.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ SRN ≤ 255; positive
integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:SourceInformation
NIEM Element: biom:SourceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.997_2: Source Representation - Reference Segment Position (RSP)
Description:
The second information item is the reference segment position / RSP. This optional field provides a unique index to a
segmentation.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ RSP ≤ 99; positive
integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:SourceInformation
NIEM Element: biom:ImageSegmentID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
709
Type-13: Variable-Resolution Latent Friction Ridge Image
13.998: Geographic Sample Acquisition Location (GEO)
Description:
This optional field contains the location where the fingerprint sample was acquired – not where it is stored.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a, BiometricCaptureType
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail
NIEM Element: biom:GeographicSampleAcquisitionLocation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.998_01: Geographic Sample Acquisition Location - Universal Time Entry (UTE)
Description:
The coordinated universal time (UTC) where the biometric sample was collected. This time is independent of the actual time
zone where the time and date is recorded. The date is YYYYMMDDhhmmssZ, where the Z is indicates the zone description of
0 hours. If sample collection time is unknown, set it to "00000000000000Z."
Field Minimum
dependent on encoding
Field Maximum
dependent on encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLocatio
NIEM Element: biom:CaptureUTCDateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
710
Type-13: Variable-Resolution Latent Friction Ridge Image
13.998_02: Geographic Sample Acquisition Location - Latitude Degree Value (LTD)
Description:
The second information item is latitude degree value (LTD). This is a value that specifies the degree of latitude. The value shall
be between -90 (inclusive) and +90 (inclusive). The degrees may be expressed as an integer (without a decimal) or a real
number including decimals. If decimals are present, then minutes and seconds shall be empty. Examples: Buenos Aires,
Argentina: -34 (with minutes LTM = 36) NIST, Gaithersburg, Maryland: 39.137627 (no LTM or LTS)
Field Minimum
1
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal,Minus Sign
Format
n/a
Constraints
-90 ≤ LTD ≤ 90
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLocatio
n/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLatitude
NIEM Element: nc:LatitudeDegreeValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.998_03: Geographic Sample Acquisition Location - Latitude Minute Value (LTM)
Description:
This information item is latitude minute value (LTM). This is a value that specifies a minute of a degree. The value shall be
between 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall be empty. Thus, the allowed special character is a
period. The minute value can be empty, even if the degree value is an integer. LTM and LGM are co-conditional, so they shall
both be present if either is present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LTM < 60
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLocatio
n/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLatitude
NIEM Element: nc:LatitudeMinuteValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
711
Type-13: Variable-Resolution Latent Friction Ridge Image
13.998_04: Geographic Sample Acquisition Location - Latitude Second Value (LTS)
Description:
The fourth information item is the latitude second value (LTS). This is a value that specifies a second of a minute. The integer
shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LTS < 60
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLocatio
n/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLatitude
NIEM Element: nc:LatitudeSecondValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.998_05: Geographic Sample Acquisition Location - Longitude Degree Value (LGD)
Description:
The fifth information item is the longitude degree value (LGD). It is a value that specifies the degree of a longitude. The value
shall be between -180 (inclusive) and +180 (inclusive). If LTD is present, then LGD shall be present. The degrees may be
expressed as whole numbers (without a decimal) or real numbers including decimals. If decimals are present, then minutes
and seconds are empty. Examples: Buenos Aires, Argentina: -58 (with minutes LGM = 22), NIST, Gaithersburg, Maryland: 77.216032 (no LGM or LGS)
Field Minimum
1
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal,Minus Sign,Plus
Sign
Format
n/a
Constraints
-180 ≤ LGD ≤ 180
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLocatio
n/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLongitude
NIEM Element: nc:LongitudeDegreeValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
712
Type-13: Variable-Resolution Latent Friction Ridge Image
13.998_06: Geographic Sample Acquisition Location - Longitude Minute Value (LGM)
Description:
The sixth information item is the longitude minute value (LGM). It is a value that specifies a minute of a degree. The value shall
be from 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall not appear. The minute value is empty, even if the
degree value is an integer. If LTM is present, then LGM shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LGM < 60
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLocatio
n/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLongitude
NIEM Element: nc:LongitudeMinuteValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.998_07: Geographic Sample Acquisition Location - Longitude Second Value (LGS)
Description:
The seventh information item is the longitude second value (LGS). This is a value that specifies a second of a minute. The
integer shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer. If LTS is
present, then LGS shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LGS < 60
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLocatio
n/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLongitude
NIEM Element: nc:LongitudeSecondValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
713
Type-13: Variable-Resolution Latent Friction Ridge Image
13.998_08: Geographic Sample Acquisition Location - Elevation (ELE)
Description:
The eighth information item is elevation (ELE). It is expressed in meters. It is a numeric value. It is between -422 meters (Dead
Sea) and 8848 meters (Mount Everest). Allowed special characters are the negative sign and the period.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Minus Sign,Period
Format
n/a
Constraints
-422.000 ≤ ELE ≤ 8848.000;
real number
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLocatio
n/nc:Location3DGeospatialCoordinate
NIEM Element: nc:LocationElevation/nc:MeasureDecimalValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.998_09: Geographic Sample Acquisition Location - Geodetic Datum Code (GDC)
Description:
The ninth information item is the geodetic datum code (GDC11). It is an alphanumeric value of 3 to 6 characters in length. This
information item is used to indicate which coordinate system was used to represent the values in information items 2 through
7. If no entry is made in this information item, then the basis for the values entered in the first eight information items shall be
WGS84, the code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values. If no entry is
made in this information item, then the basis for the values entered in the first eight information items shall be WGS84, the
code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values.
Field Minimum
3
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
see Look Up Codes
Code List: GEOGRAPHIC COORDINATE DATUM CODE
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLocatio
n/nc:Location3DGeospatialCoordinate
NIEM Element: biom:GeodeticDatumCoordinateSystemCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
714
Type-13: Variable-Resolution Latent Friction Ridge Image
13.998_10: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Zone (GCM)
Description:
It is an alphanumeric value of 2 to 3 characters. This is a one or two digit UTM zone number followed by the 8 degree
latitudinal band designator (which is a single letter).
Field Minimum
2
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
One or two digits followed
by a single letter
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLocatio
NIEM Element: nc:LocationUTMCoordinateValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.998_11: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Easting (GCE)
Description:
The eleventh information item is the geographic coordinate universal transverse Mercator easting (GCE). It is an integer of 1 to
6 digits.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLocatio
NIEM Element: mo:MGRSCoordinateStringText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
715
Type-13: Variable-Resolution Latent Friction Ridge Image
13.998_12: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Northing (GCN)
Description:
The twelfth information item is the geographic coordinate universal transverse Mercator northing (GCN). It is an integer of 1 to
8 digits.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLocatio
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.998_13: Geographic Sample Acquisition Location - Geographic Reference Text (GRT)
Description:
It is a free form text describing a street address or other physical location (such as ‘Corner of Washington and Madison,
Geneva, NY’).
Field Minimum
1
Field Maximum
150
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail
NIEM Element: nc:LocationDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
716
Type-13: Variable-Resolution Latent Friction Ridge Image
13.998_14: Geographic Sample Acquisition Location - Geographic Coordinate Other System Identifier (OSI)
Description:
A fourteenth optional information item geographic coordinate other system identifier (OSI) allows for other coordinate systems.
This information items specifies the system identifier. It is up to 10 characters in length. Examples are: • MGRS (Militar Grid
Reference System), • USNG (United States National Grid), • GARS (Global Area Reference System), • GEOREF (World
Geographic Reference), • LANDMARK landmark (e.g. hydant) and position relative to the landmark.
Field Minimum
1
Field Maximum
10
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLocatio
NIEM Element: biom:GeographicLocationSystemName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
13.998_15: Geographic Sample Acquisition Location - Geographic Coordinate Other System Value (OCV)
Description:
A fifteenth optional information item, is the geographic coordinate other system value (OCV). It shall only be present if OSI is
present in the record. It can be up to 126 characters in length. If OSI is LANDMARK, OCV is free text and may be up to 126
characters. For details on the formatting of OCV for the other coordinate systems shown in OSI as examples, see http://earthinfo.nga.mil/GandG/coordsys/grids/referencesys.html .
Field Minimum
1
Field Maximum
126
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent:
itl:PackageLatentImageRecord/biom:FrictionRidgeDetail/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLocatio
NIEM Element: biom:GeographicLocationText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
717
Type-13: Variable-Resolution Latent Friction Ridge Image
13.999: Latent Friction Ridge Image (DATA)
Description:
This conditional field, if present, contains the latent image. If this field is used, Field 13.994: External file reference / EFR shall
not be set. One of these two fields shall be present in this record. See Section 7.2 of ANSI/NIST ITL update 2015 for details.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
B
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2013 (Type-13)
Status: Active
XML Parent: itl:PackageLatentImageRecord
NIEM Element: nc:Base64BinaryObject
XML Min/Max: 0 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.001: Record Header (LEN)
Description:
The record header appears as the first field (xx.001) in each Record Type. It contains information particular to the encoding
format chosen, in order to enable proper reading of the record. In Traditional encoding, this field contains the record length in
bytes (including all information separators). In NIEM-conformant XML encoding, this field contains the RecordCategoryCode,
which is the numeric representation of the Record Type.
Field Minimum
T = 4; X = 1
Field Maximum
T = 8; X = 2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
718
Type-14: Variable-Resolution Fingerprint Image
14.002: Information Designation Character (IDC)
Description:
Each of the records present in a transaction, with the exception of the Type-1 record, shall include a field (xx.002) containing
the information designation character / IDC. The value of the IDC shall be a sequentially assigned positive integer starting
from zero and incremented by one up to a maximum of 99. IDC references are stated in Type-1 Field 1.003 Transaction
content (CNT) and shall be used to relate information items in the CNT field of the Type-1 record to the other records in the
transaction. Two or more records may share a single IDC solely to identify and link together records that pertain to different
representations of the same biometric trait.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ IDC ≤ 99; integer≤
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord
NIEM Element: biom:ImageReferenceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.003: Impression Type (IMP)
Description:
This dependent field shall indicate the manner by which the fingerprint was obtained. This field is mandatory if an image is
present in Field 14.999: Fingerprint image / DATA or referenced in Field 14.994: External file reference / EFR. Otherwise it is
absent.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ IMP ≤ 3, IMP = 8, 20 ≤
IMP ≤ 29, 40 ≤ IMP ≤ 41;
integer
Code List: FRICTION RIDGE IMPRESSION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: itl:FrictionRidgeImpressionCaptureCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
719
Type-14: Variable-Resolution Fingerprint Image
14.004: Source Agency (SRC)
Description:
This mandatory field is the identifier of the agency that actually created the record and supplied the information contained in it.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:ImageCaptureDetail/biom:CaptureOrganiza
tion
NIEM Element: nc:OrganizationIdentification/nc:IdentificationID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.005: Fingerprint Capture Date (FCD)
Description:
This mandatory field shall contain the local date that the fingerprint data contained in the record was captured.
Field Minimum
Field Maximum
Dependent upon encoding Dependent upon encoding
Character Types
N
Special Characters
None
Occurrence Minimum
1
Occurrence Maximum
1
Format
T = YYYYMMDD; X =
Constraints
Dependent upon encoding.
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:ImageCaptureDetail
NIEM Element: biom:CaptureDate/nc:Date
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
720
Type-14: Variable-Resolution Fingerprint Image
14.006: Horizontal Line Length (HLL)
Description:
This field is mandatory if an image is present in Field 14.999: Fingerprint image / DATA or referenced in Field 14.994: External
file reference / EFR. Otherwise it is absent. HLL defines the number of pixels contained on a single horizontal line of the image.
The maximum horizontal size is limited to 65,535 pixels in Record Types-4 and 8, and to 99,999 for other record types. The
minimum value is 10 pixels. The total image size (HLL times VLL) must be able to be accommodated in Field xx.001 for
Traditional encoding.
Field Minimum
2
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
10 ≤ HLL ≤ 99999; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:HorizontalLineLengthPixelQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.007: Vertical Line Length (VLL)
Description:
This field is mandatory if an image is present in Field 14.999: Fingerprint image / DATA or referenced in Field 14.994: External
file reference / EFR. Otherwise it is absent. VLL defines the number of pixels contained in a single vertical line in the image.
The maximum vertical size is limited to 65,535 pixels in Record Types-4 and 8, and to 99,999 for other record types. The
minimum value is 10 pixels. The total image size (HLL times VLL) must be able to be accommodated in Field xx.001 for
Traditional encoding.
Field Minimum
2
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
10 ≤ VLL ≤ 99999; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:VerticalLineLengthPixelQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
721
Type-14: Variable-Resolution Fingerprint Image
14.008: Scale Units (SLC)
Description:
This field is mandatory if an image is present in Field 14.999: Fingerprint image / DATA or referenced in Field 14.994: External
file reference / EFR. Otherwise it is absent. The image sampling frequency (pixel density). A value of “1” shall indicate pixels
per inch. A value of “2” shall indicate pixels per centimeter. A value of “0” in this field indicates that no scale is provided, and
the quotient of THPS/TVPS shall provide the pixel aspect ratio.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ SLC ≤ 2, See Look Up
Codes
Code List: SCALE UNIT CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:ImageScaleUnitsCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.009: Transmitted Horizontal Pixel Scale (THPS)
Description:
This field is mandatory if an image is present in Field 14.999: Fingerprint image / DATA or referenced in Field 14.994: External
file reference / EFR. Otherwise it is absent. This is the integer pixel density used in the horizontal direction of the image if SLC
has a value of “1” or “2”. If SLC has a value of “0”, this information item shall contain the horizontal component of the pixel
aspect ratio, up to 5 integer digits. For example, if the SLC value = 1, then the value of THPS could be ‘1000’ for a 1000 ppi
sensor. When using certain formats, such as PNG, conversion from ppm (or other scales) may result in a decimal value. Since
these fields require integer values, rounding should be used. For example with the values 1.3, 1.5 and 1.8 the resulting THPS
values would be 1, 2, and 2. Any value greater than x.0 and less than x.5 would be rounded down to x, regardless of the
number of significant digits to the right of the decimal.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:ImageHorizontalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
722
Type-14: Variable-Resolution Fingerprint Image
14.01: Transmitted Vertical Pixel Scale (TVPS)
Description:
This field is mandatory if an image is present in Field 14.999: Fingerprint image / DATA or referenced in Field 14.994: External
file reference / EFR. Otherwise it is absent. This is the integer pixel density used in the vertical direction of the image if SLC
has a value of “1” or “2”. If SLC has a value of “0”, this information item shall contain the vertical component of the pixel aspect
ratio, up to 5 integer digits. If SLC is 1 or 2, then TVPS shall equal THPS. When using certain formats, such as PNG,
conversion from ppm (or other scales) may result in a decimal value. Since these fields require integer values, rounding should
be used. For example with the values 1.3, 1.5 and 1.8 the resulting THPS values would be 1, 2, and 2. Any value greater than
x.0 and less than x.5 would be rounded down to x, regardless of the number of significant digits to the right of the decimal.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:ImageVerticalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.011: Compression Algorithm (CGA)
Description:
This field is mandatory if an image is present in Field 14.999: Fingerprint image / DATA or referenced in Field 14.994: External
file reference / EFR. Otherwise it is absent. It shall specify the algorithm used to compress the transmitted grayscale images.
See Table 19 Compression codes of ANSI/NIST-ITL update 2015 for labels.
Field Minimum
3
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
see Look Up Codes
Code List: COMPRESSION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:ImageCompressionAlgorithmCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
723
Type-14: Variable-Resolution Fingerprint Image
14.012: Bits Per Pixel (BPX)
Description:
This field is mandatory if an image is present in Field 14.999: Fingerprint image / DATA or referenced in Field 14.994: External
file reference / EFR. Otherwise it is absent. This ASCII field shall contain the number of bits used to represent a pixel. This field
shall contain an entry of “8” for normal grayscale values of “0” to “255” or each RGB color component. Any entry in this field
greater than “8” shall represent a grayscale or color pixel component with increased precision.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
8 ≤ BPX ≤ 99
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:ImageBitsPerPixelQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.013: Friction Ridge Generalized Position (FGP)
Description:
This mandatory field is used in Record types dealing with friction ridges. It specifies which friction ridge biometric sample was
collected.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
n/a
Special Characters
None
Format
n/a
Constraints
n/a
Code List: FRICTION RIDGE POSITION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:ExemplarFingerPositionCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
724
Type-14: Variable-Resolution Fingerprint Image
14.013_0: Friction Ridge Generalized Position - Subfields: Repeating values (FGP)
Description:
This field is used in Record types dealing with friction ridges. It specifies which friction ridge biometric sample was collected.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ FGP ≤ 19, or FGP = 33,
or FGP = 36 or 40 ≤ FGP ≤
54; integer; see Look Up
Codes
Code List: FRICTION RIDGE POSITION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.014: Print Position Descriptors (PPD)
Description:
This ASCII field shall be present if and only if the finger position code "19" appears in Field 14.013: Finger ridge generalized
position / FGP. This field shall consist of two information items. The first is the probable decimal finger position code (0-10).
The second information item is the code to indicate the portion of the EJI or tip image that is stored as a single image in the
database. There may be up to 17 such images for a single finger. Images of full-length fingers use codes FV1 through FV4.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
725
Type-14: Variable-Resolution Fingerprint Image
14.014_1: Print Position Descriptors - Decimal Finger Position Code (DFP)
Description:
The first information item of 14.014 Print Position Descriptors with value of 1 to 10, inclusive or 16 or 17.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ DFP ≤ 10 or DFP = 16
or 17; see Look Up Codes
Code List: FRICTION RIDGE POSITION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageMajorCasePrint
NIEM Element: biom:FingerPositionCode
XML Min/Max: 1 / 9
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.014_2: Print Position Descriptors - Finger Image Code (FIC)
Description:
The second information item indicates the portion of the database to search. Full-length finger joint images use codes FV1
through FV4. Multiple portions of the EJI may be listed in a separate subfield.
Field Minimum
3
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
D
Format
n/a
Constraints
EJI, TIP, TPP, FV1, FV2,
FV3, FV4, PRX, DST or
MED from table 10
Code List: PRINT POSITION DESCRIPTORS
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageMajorCasePrint
NIEM Element: biom:MajorCasePrintCode
XML Min/Max: 1 / 9
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
726
Type-14: Variable-Resolution Fingerprint Image
14.015: Print Position Coordinates (PPC)
Description:
This field describes the type or portion of the latent image contained in this record and its location within an entire joint image.
If finger position code “19” appears in Finger Position field, this set may optionally contain offsets to
the locations for the
bounding box of the EJI, each of the full finger views, or segments within the EJI. When used, this field shall consist of six (6)
mandatory information items describing the type or portion of the image contained in this record and its location within an EJI.
This information will describe either the location of the entire joint image, one full finger view, or segment. Individual full finger
or segment definitions may be repeated as repeating sets of information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageMajorCasePrint
NIEM Element: biom:MajorCasePrintSegmentOffset
XML Min/Max: 0 / 12
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.015_0: Print Position Coordinates - Subfields: Repeating sets of information items (PPC_0)
Description:
This field describes the type or portion of the latent image contained in this record and its location within an entire joint image.
If finger position code “19” appears in Finger Position field, this setmay optionally contain offsets to
the locations for the
bounding box of the EJI, each of the full finger views, or segments within the EJI. When used, this field shall consist of six (6)
mandatory information items describing the type or portion of the image contained in this record and its location within an EJI.
This information will describe either the location of the entire joint image, one full finger view, or segment. Individual full finger
or segment definitions may be repeated as repeating sets of information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
12
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
727
Type-14: Variable-Resolution Fingerprint Image
14.015_1: Print Position Coordinates - Full Finger View (FVC)
Description:
This information item is the number of the full finger view with values of "FV1" through "FV4". Values of “FV1” to “FV4” specify
the bounding coordinates for each full finger view. For the case of a fingertip, this information item shall be “TIP” or "TPP". FVC
will contain the code “NA” if only a proximal, distal or medial segment is available.
Field Minimum
2
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
FVC = NA, FV1, FV2, FV3,
FV4 TIP or TPP; see Look
Up Codes
Code List: PRINT POSITION DESCRIPTORS
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageMajorCasePrint/biom:Maj
orCasePrintSegmentOffset
NIEM Element: biom:SegmentFingerViewCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.015_2: Print Position Coordinates - Location of Segment (LOS)
Description:
This information item is used to identify the location of a segment within a full finger view. It will contain the not applicable code
“NA” if the image portion refers to a full finger view or to the entire joint image locations. It shall contain “PRX”, “DST”, “MED”
for a proximal, distal, or medial segment.
Field Minimum
2
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
LOS = NA, PRX, DST or
MED; see Look Up Codes
Code List: PRINT POSITION DESCRIPTORS
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageMajorCasePrint/biom:Maj
orCasePrintSegmentOffset
NIEM Element: biom:SegmentLocationCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
728
Type-14: Variable-Resolution Fingerprint Image
14.015_3: Print Position Coordinates - Left Horizontal Coordinate (LHC)
Description:
The third information item is the left horizontal coordinate / LHC. It is the horizontal offset in pixels to the left edge of the
bounding box relative to the origin positioned in the upper left corner of the image.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ LHC < HLL; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageMajorCasePrint/biom:Maj
orCasePrintSegmentOffset
NIEM Element: biom:SegmentLeftHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.015_4: Print Position Coordinates - Right Horizontal Coordinate (RHC)
Description:
The fourth information item is the right horizontal coordinate / RHC. It is the horizontal offset in pixels to the right edge of the
bounding box relative to the origin positioned in the upper left corner of the image.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
LHC < RHC < HLL; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageMajorCasePrint/biom:Maj
orCasePrintSegmentOffset
NIEM Element: biom:SegmentRightHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
729
Type-14: Variable-Resolution Fingerprint Image
14.015_5: Print Position Coordinates - Top Vertical Coordinate (TVC)
Description:
The fifth information item is the top vertical coordinate / TVC. The vertical offset (pixel counts down) to the top of the bounding
box.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ TVC < VLL; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageMajorCasePrint/biom:Maj
orCasePrintSegmentOffset
NIEM Element: biom:SegmentTopVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.015_6: Print Position Coordinates - Bottom Vertical Coordinate (BVC)
Description:
The sixth information item is the bottom vertical coordinate / BVC. It is the vertical offset from the upper left corner of the image
down to the bottom of the bounding box. It is counted in pixels.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
TVC < BVC < VLL; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageMajorCasePrint/biom:Maj
orCasePrintSegmentOffset
NIEM Element: biom:SegmentBottomVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
730
Type-14: Variable-Resolution Fingerprint Image
14.016: Scanned Horizontal Pixel Scale (SHPS)
Description:
This field is a dependent field if an image is present in Field 14.999: Fingerprint image / DATA or referenced in Field 14.994:
External file reference / EFR. Otherwise it is absent. This ASCII field shall specify the horizontal pixel density used for scanning
providing the SLC field contains a "1" or a "2". Otherwise, it indicates the horizontal component of the pixel aspect ratio, up to 5
integer digits.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:ImageCaptureDetail
NIEM Element: biom:CaptureHorizontalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.017: Scanned Vertical Pixel Scale (SVPS)
Description:
This field is a dependent field if an image is present in Field 14.999: Fingerprint image / DATA or referenced in Field 14.994:
External file reference / EFR. Otherwise it is absent. This ASCII field shall specify the vertical pixel density used for scanning
providing the SLC field contains a "1" or a "2". Otherwise, it indicates the vertical component of the pixel aspect ratio, up to 5
integer digits. Note that density is directly related to resolution. If SLC is 1 or 2 and SHPS is entered, then SVPS shall equal
SHPS.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:ImageCaptureDetail
NIEM Element: biom:CaptureVerticalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
731
Type-14: Variable-Resolution Fingerprint Image
14.018: Amputated or Bandaged (AMP)
Description:
This optional field shall specify if one or more fingers are amputated or bandaged. This field shall consist of one subfield for
each amputated or missing finger. Each subfield shall contain two information items. Multiple amputated or unprintable finger
positions may each be entered as a separate repeating subfield. This field is to be used anytime there are fewer than
expected printable fingers in a submission (e.g., less than four in a left or right slap or less than two in a two-thumb slap). A
scarred finger should be printed and the SR code used. XX shall be used only when a partial print exists due to amputation;
therefore it contains some friction ridge detail. UP shall be used with the complete block where an image was to be
transmitted, but there is no image due to amputation or total lack of friction ridge detail (such as with a bandage). An image
with a scar should not be marked XX or UP. SR is used to denote a complete scar when the scarred pattern could have been
any of the three general pattern types (e.g., loop, whorl and arch). If all fingers for a specific slap are missing, the AMP codes
for each missing finger shall be specified, and the image shall be sent or not in accordance to the agreement of the
interchanging agencies.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:FingerprintImageFingerMissing
XML Min/Max: 0 / 5
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.018_0: Amputated or Bandaged - Subfield: Repeating sets of information items (AMP_0)
Description:
This optional field shall specify if one or more fingers are amputated or bandaged. This field shall consist of one subfield for
each amputated or missing finger. Multiple amputated or unprintable finger positions may each be entered as a separate
repeating subfield. This field is to be used anytime there are fewer than expected printable fingers in a submission (e.g., less
than four in a left or right slap or less than two in a two-thumb slap). A partially scarred finger should be printed. XX shall be
used only when a partial print exists due to amputation; therefore it contains some friction ridge detail. UP shall be used with
the complete block where an image was to be transmitted, but there is no image due to amputation or total lack of friction
ridge detail (such as with a bandage). An image with a scar should not be marked XX or UP.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
5
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
732
Type-14: Variable-Resolution Fingerprint Image
14.018_1: Amputated or Bandaged - Friction Ridge Amputation or Bandaged Position (FRAP)
Description:
The first information item is the friction ridge amputated or bandaged position / FRAP between 1 and 10 or 16 or 17 as chosen
from Table 9 of the ANSI/NIST-ITL update 2015.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ FRAP ≤ 10 or FRAP =
16 or 17; see Look Up
Codes
Code List: FRICTION RIDGE POSITION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageFingerMissing
NIEM Element: biom:FingerPositionCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
14.018_2: Amputated or Bandaged - Amputated or Bandaged Code (ABC)
Description:
The second item is the amputated or bandaged code / ABC, also known as the AMPCD. This information item provides the
code that describes the reason the finger's image is missing. See Table 105 Amputation / bandaged fingerprinting codes in
ANSI/NIST-ITL update 2015 for allowable indicators.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
ABC = XX, UP or SR; See
Look Up Codes
Code List: AMPUTATED OR BANDAGED CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageFingerMissing
NIEM Element: biom:FingerMissingCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
733
Type-14: Variable-Resolution Fingerprint Image
14.02: Comment (COM)
Description:
The optional Comment field appears in many record types and may be used to insert free text information. It is not reserved
exclusively for log-related information but has historically often been used for this purpose. It is limited to a maximum of 126
characters. This maximum size was established in order to maintain consistency across encodings. The maximum size differed
in the 2007 and 2008 versions of the standard.
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:ImageCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.021: Finger Segment Position(s) (SEG)
Description:
This optional field shall contain offsets to the locations of image segments containing the individual fingers within the flat
images of simultaneous fingers from each hand or the two simultaneous thumbs. The offsets are relative to the origin
positioned in the upper left corner of the image. The horizontal offsets (X) are the pixel counts to the right, and the vertical
offsets (Y) are the pixel counts down. A finger segment is defined by the FINGER NUMBER The five information items within a
finger segment definition are separated by the “US” separator. Individual finger segment definitions are separated. This field
shall only be present if FGP = 13, 14, 15 or 40-54 from Table 9 as entered in Field 14.013: Friction ridge generalized position /
FGP. The subfield occurs at least once, and may be repeated if more than one algorithm is used to segment the image. Each
subfield contains five information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:FingerprintImageSegmentPositionSquare
XML Min/Max: 0 / 5
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
734
Type-14: Variable-Resolution Fingerprint Image
14.021_0: Finger Segment Position(s) (SEG_0)
Description:
This ASCII field shall contain offsets to the locations of image segments containing the individual fingers within the flat images
of the four simultaneous fingers from each hand or the two simultaneous thumbs. The offsets are relative to the origin
positioned in the upper left corner of the image. The horizontal offsets (X) are the pixel counts to the right, and the vertical
offsets (Y) are the pixel counts down. A finger segment is defined by the FINGER NUMBER The five information items within a
finger segment definition are separated by the “US” separator. Individual finger segment definitions are separated. If more than
one algorithm is used to segment the image, successive sets finger segmentation positions
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
5
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
14.021_1: Finger Segment Position(s) - Friction Ridge Segment Position (FRSP)
Description:
The first information item is the friction ridge segment position / FRSP with values of 1 to 10 or 16 or 17 selected from Table 9
of the ANSI/NIST-ITL update 2015.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ FRSP ≤ 10 or FRSP =
16 or 17
Code List: FRICTION RIDGE POSITION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageSegmentPositionSquare
NIEM Element: biom:FingerPositionCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
735
Type-14: Variable-Resolution Fingerprint Image
14.021_2: Finger Segment Position(s) - Left Horizontal Coordinate (LHC)
Description:
The second information item is the left horizontal coordinate value / LHC. It is the horizontal offset in pixels to the left edge of
the bounding box relative to the origin positioned in the upper left corner of the image.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ LHC < HLL; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageSegmentPositionSquare
NIEM Element: biom:SegmentLeftHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.021_3: Finger Segment Position(s) - Right Horizontal Coordinate (RHC)
Description:
The third information item is the right horizontal coordinate value / RHC. It is the horizontal offset in pixels to the right edge of
the bounding box relative to the origin positioned in the upper left corner of the image.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
LHC < RHC < HLL; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageSegmentPositionSquare
NIEM Element: biom:SegmentRightHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
736
Type-14: Variable-Resolution Fingerprint Image
14.021_4: Finger Segment Position(s) - Top Vertical Coordinate (TVC)
Description:
The fourth information item is the top vertical coordinate value / TVC. The vertical offset (pixel counts down) to the top of the
bounding box.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ TVC < VLL; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageSegmentPositionSquare
NIEM Element: biom:SegmentTopVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.021_5: Finger Segment Position(s) - Bottom Vertical Coordinate (BVC)
Description:
The fifth information item is the bottom vertical coordinate value / BVC. It is the vertical offset from the upper left corner of the
image down to the bottom of the bounding box. It is counted in pixels.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
TVC < BVC < VLL; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageSegmentPositionSquare
NIEM Element: biom:SegmentBottomVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
737
Type-14: Variable-Resolution Fingerprint Image
14.022: NIST Quality Metric (NQM)
Description:
This ASCII field shall contain the NIST Fingerprint Image Quality (NFIQ) scores for the individual finger(s) derived from the slap
impressions or individual rolled fingerprints. It consists of two information items. These two information items are separated.
Individual finger quality definitions are separated.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:FingerprintImageNISTQuality
XML Min/Max: 0 / 5
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.022_0: NIST Quality Metric (NQM_0)
Description:
This ASCII field shall contain the NIST Fingerprint Image Quality (NFIQ) scores for the individual finger(s) derived from the slap
impressions or individual rolled fingerprints. It consists of two information items. The first item is the finger number between
one and ten. The second item is the quality score which is a quantitative expression of the predicted AFIS matcher accuracy
performance of the fingerprint image. The scores range from "1" for the best quality im image. A "254" indicates that no score
was ever computed while an entry of "255" shall indicate a failed attempt to calculate the image quality metric. These two
information items are separated. Individual finger quality definitions are separated.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
5
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
738
Type-14: Variable-Resolution Fingerprint Image
14.022_1: NIST Quality Metric - Friction Ridge NIST Quality Position (FRNP)
Description:
The first item is the friction ridge NIST quality position / FRNP between one and ten or 16 or 17, as chosen from Table 9 of the
ANSI/NIST-ITL update 2015.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ FRNP ≤ 10 or FGP = 16
or 17; see Look Up Codes
Code List: FRICTION RIDGE POSITION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:FingerprintImageNISTQualityitl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/
NIEM Element: biom:FingerPositionCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.022_2: NIST Quality Metric - NIST Image Quality Score (IQS)
Description:
This information item is the NIST image quality score / IQS which is a quantitative expression of the predicted AFIS matcher
accuracy performance of the fingerprint image. The scores range from "1" for the best quality image, to "5" for the worst quality
image. A "254" indicates that no score was ever computed while an entry of "255" shall indicate a failed attempt to calculate
the image quality metric.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ IQS ≤ 5 or IQS = 254 or
255; integer
Code List: NIST IMAGE QUALITY SCORE CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageNISTQuality
NIEM Element: biom:NISTQualityMeasure
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
739
Type-14: Variable-Resolution Fingerprint Image
14.023: Segmentation Quality Metric (SQM)
Description:
This ASCII field provides a measure of estimated correctness regarding the accuracy of the location of the segmented finger
within the right or left four finger (which may include extra digits, if applicable) or two thumbs slap image. A subfield shall exist
for each segmented finger [2015n>] and quality algorithm combination (up to 9 algorithms are allowed for each finger).
[<2015n]. Each subfield consists of four information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:FingerprintImageSegmentationQuality
XML Min/Max: 0 / 45
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.023_0: Segmentation Quality Metric - Subfield: Repeating sets of information items (SQM_0)
Description:
This ASCII field provides a measure of estimated correctness regarding the accuracy of the location of the segmented finger
within the right or left four finger or two thumbs slap image. For each segmented finger, this field shall contain four information
items separated. The first information item is the finger number between one and ten. The other three items identify a quality
score and the algorithm used to create the quality score. T recipient of the quality score to differentiate between quality scores
generated by different algorithms and adjust for any differences in processing or analysis as necessary.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
45
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
740
Type-14: Variable-Resolution Fingerprint Image
14.023_1: Segmentation Quality Metric - Friction Ridge Segment Quality Position (FRQP)
Description:
The first information item is the friction ridge segment quality position / FRQP between one and ten or 16 or 17, as chosen from
Table 9 of the ANSI/NIST-ITL update 2015. The FRQP values shall be in the set of either the FRSP or FRAS values contained
in this record.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ FRQP ≤ 10 or FRQP =
16 or 17; see Look Up
Codes
Code List: FRICTION RIDGE POSITION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageSegmentationQuality
NIEM Element: biom:FingerPositionCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.023_2: Segmentation Quality Metric - Quality Value (QVU)
Description:
This information item shall contain the integer image quality score between 0 and 100 (inclusive) assigned to the image data
by a quality algorithm. Higher values indicate better quality. An entry of “255” shall indicate a failed attempt to calculate a
quality score. An entry of “254” shall indicate that no attempt to calculate a quality score was made.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ QVU ≤ 100 or QVU =
254 or 255; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageSegmentationQuality
NIEM Element: biom:QualityValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
741
Type-14: Variable-Resolution Fingerprint Image
14.023_3: Segmentation Quality Metric - Algorithm Vendor Identification (QAV)
Description:
This information item shall specify the ID of the vendor of the quality algorithm used to calculate the quality score. This 4-digit
hex value is assigned by IBIA and expressed as four ASCII characters. The IBIA shall maintain the Vendor Registry of CBEFF
Biometric Organizations that will map the value in this field to a registered organization.
Field Minimum
4
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
0000 ≤ QAV ≤ FFFF
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageSegmentationQuality
NIEM Element: biom:QualityAlgorithmVendorID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.023_4: Segmentation Quality Metric - Algorithm Product Identification (QAP)
Description:
This information item shall specify a numeric product code assigned by the vendor of the quality algorithm, which may be
registered with the IBIA, but it is not required to be registered. It indicates which of the vendor’s algorithms was used in the
calculation of the quality score. This field contains the ASCII representation of the integer product code and should be within
the range 1 to 65535.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ QAP ≤ 65535; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageSegmentationQuality
NIEM Element: biom:QualityAlgorithmProductID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
742
Type-14: Variable-Resolution Fingerprint Image
14.024: Fingerprint Quality Metric (FQM)
Description:
This optional field shall specify one or more different metrics of fingerprint image quality score data for the image stored in this
record. The meaning attributed to this metric must be defined and interpreted by the producer of the scoring algorithm or by the
person or system used to assign the metric to the fingerprint image. The metric may be a predictor of AFIS matcher accuracy
performanc indicate a value associated with the quality of the fingerprint image for a particular function. A subfield shall exist
for each segmented finger and quality algorithm combination (up to 9 algorithms are allowed for each finger). Each subfield
consists of four information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:FingerprintImageQuality
XML Min/Max: 0 / 45
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.024_0: Fingerprint Quality Metric - Subfield: Repeating sets of information items (FQM_0)
Description:
This ASCII field is used to specify one or more different metrics of fingerprint image quality score data for the image stored in
this record. The meaning attributed to this metric must be defined and interpreted by the producer of the scoring algorithm or
by the person or system used to assign the metric to the fingerprint image. The metric may be a predictor of AFIS matcher
accuracy performanc indicate a value associated with the quality of the fingerprint image for a particular function. This field
may contain one or more subfields, each consisting of four information items separated. The first information item is the finger
number. The other algorithm used to create the quality score. This information is useful to enable the recipient of the quality
score to differentiate between quality scores generated by different algorithms and adjust for any differences in processing or
analysis as neces
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
45
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
743
Type-14: Variable-Resolution Fingerprint Image
14.024_1: Fingerprint Quality Metric - Friction Ridge Metric Position (FRMP)
Description:
The first information item is the friction ridge metric position / FRMP between one and ten or 16 or 17, as chosen from Table 9
of the ANSI/NIST-ITL update 2015.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ FRMP ≤ 10 or FGP = 16
or 17; see Look Up Codes
Code List: FRICTION RIDGE POSITION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageQuality
NIEM Element: biom:FingerPositionCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.024_2: Fingerprint Quality Metric - Quality Value (QVU)
Description:
This information item shall contain the integer image quality score between 0 and 100 (inclusive) assigned to the image data
by a quality algorithm. Higher values indicate better quality. An entry of “255” shall indicate a failed attempt to calculate a
quality score. An entry of “254” shall indicate that no attempt to calculate a quality score was made.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ QUV ≤ 100 or QVU =
254 or 255; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageQuality
NIEM Element: biom:QualityValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
744
Type-14: Variable-Resolution Fingerprint Image
14.024_3: Fingerprint Quality Metric - Algorithm Vendor Identification (QAV)
Description:
This information item shall specify the ID of the vendor of the quality algorithm used to calculate the quality score. This 4-digit
hex value is assigned by IBIA and expressed as four ASCII characters. The IBIA shall maintain the Vendor Registry of CBEFF
Biometric Organizations that will map the value in this field to a registered organization.
Field Minimum
4
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
0000 ≤ QAV ≤ FFFF
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageQuality
NIEM Element: biom:QualityAlgorithmVendorID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.024_4: Fingerprint Quality Metric - Algorithm Product Identification (QAP)
Description:
This information item shall specify a numeric product code assigned by the vendor of the quality algorithm, which may be
registered with the IBIA, but it is not required to be registered. It indicates which of the vendor’s algorithms was used in the
calculation of the quality score. This field contains the ASCII representation of the integer product code and should be within
the range 1 to 65535.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ QAP ≤ 65535; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageQuality
NIEM Element: biom:QualityAlgorithmProductID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
745
Type-14: Variable-Resolution Fingerprint Image
14.025: Alternate Finger Segment Position (ASEG)
Description:
This optional field is an alternate approach to describing the locations for each of the image segments of the individual fingers
within a flat image containing the capture of four (or more if extra digits exist on the hand) simultaneous fingers or two
simultaneous thumbs. This field uses an n-vertex polygon to encompass each finger image segment, where “n” is between 3
and 99. The order of the vertices must be in their consecutive order around the perimeter of the polygon, either clockwise or
counterclockwise. No two vertices may occupy the same location. The polygon side defined by the last subfield and the first
subfield shall complete the polygon. The polygon must be a simple, plane figure with no sides crossing and no interior holes.
This field shall consist of up to five subfields: the segmentation for each finger is represented in a different subfield.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:FingerprintImageSegmentPositionPolygon
XML Min/Max: 0 / 5
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
746
Type-14: Variable-Resolution Fingerprint Image
14.025_0: Alternate Finger Segment Position - Subfield: Repeating sets of information items (ASEG_0)
Description:
This ASCII field is an alternate approach to describing the locations for each of the image segments of the individual fingers
within a flat image containing the capture of four simultaneous fingers or two simultaneous thumbs. This field uses an n-vertex
polygon to encompass each finger image segment, where “n” is between 3 and 99. The order of the vertices must be in their
consecutive order around the perimeter of the polygon, either clockwise or counterclockwise. No two verti location. The
polygon side defined by the last subfield and the first subfield shall complete the polygon. The polygon must be a simple, plane
figure with no sides crossing and no interior holes. This field shall consist of one to four subfields. Each sub between 1 and 10,
the total number of vertices of the polygon encompassing the finger, and the set of consecutive vertices. Each vertex shall be
represented as horizontal and vertical pixel offsets relative to the origin positioned in the upper left corne are the pixel counts to
the right, and the vertical offsets (Y) are the pixel counts down from the origin.A minimum of three points is required to describe
a finger location. The finger number, the number of vertices, each X coordinate, and each Y coordin Subfields representing
each finger are separated.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
5
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageSegmentPositionPolygon
NIEM Element: biom:PositionPolygonVertex
XML Min/Max: 3 / 99
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
747
Type-14: Variable-Resolution Fingerprint Image
14.025_1: Alternate Finger Segment Position - Friction Ridge Alternate Segment Position (FRAS)
Description:
The first information item (friction ridge alternate segment position / FRAS) is the finger number from Table 9 of the ANSI/NISTITL update 2015.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ FRAS ≤ 10 or FRAS =
16 or 17; see Look Up
Codes
Code List: FRICTION RIDGE POSITION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageSegmentPositionPolygon
NIEM Element: biom:FingerPositionCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.025_2: Alternate Finger Segment Position - Number of Points (NOP)
Description:
Specifies the number of vertices.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
3 ≤ NOP ≤ 99; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageSegmentPositionPolygon
NIEM Element: biom:PositionPolygonVertexQuantity
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
748
Type-14: Variable-Resolution Fingerprint Image
14.025_3: Alternate Finger Segment Position - Horizontal Point Offset (HPO)
Description:
The pixel counts to the right.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
3
Occurrence Maximum
NOP
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ HPO < HLL; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageSegmentPositionPolygon/
biom:PositionPolygonVertex
NIEM Element: biom:PositionHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.025_4: Alternate Finger Segment Position - Vertical Point Offset (VPO)
Description:
The pixel counts down from the origin.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
3
Occurrence Maximum
NOP
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ VPO < VLL; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:FingerprintImageSegmentPositionPolygon/
biom:PositionPolygonVertex
NIEM Element: biom:PositionVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
749
Type-14: Variable-Resolution Fingerprint Image
14.026: Simultaneous Capture (SCF)
Description:
This optional field allows the user to link together fingerprint images that were captured simultaneously. Note that this is
different from the IDC. This is used, for instance, when individual flat print are captured on different platens simultaneously.
Such images should not be stitched together for transmission as a single multiple-finger print image, but they should be coded
with the same SCF value to indicate that they were captured simultaneously, and that there is little possibility of a mistaken
fingerprint code. The SCF is a 1-based numeric index that is incremented for each simultaneously captured set of images, and
shall be omitted otherwise.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ SCF ≤ 255; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:FingerprintSimultaneousCaptureID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.027: Stitched Image Flag (SIF)
Description:
This field signifies that images captured separately were stitched together to form a single image. This field is mandatory if an
image has been stitched, and the value shall be set to 'Y'. Otherwise, this field shall not appear in the record. This field is not
intended to apply to a single rolled image.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
SIF = Y
Code List: STITCHED IMAGE CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:FingerprintImageStitchedIndicator
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
750
Type-14: Variable-Resolution Fingerprint Image
14.030: Device Monitoring Mode (DMM)
Description:
This field provides information describing the level of human monitoring associated with the biometric sample capture. This
field will contain alphabetic values from Table 6 Device monitoring mode from ANSI/NIST-ITL update 2015 to indicate the
monitoring mode of the biometric sample capture device.
Field Minimum
7
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
see Table 6
Code List: CAPTURE DEVICE MONITORING MODE CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:ImageCaptureDetail
NIEM Element: biom:CaptureDeviceMonitoringModeCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.031: Subject Acquisition Profile - Fingerprint (FAP)
Description:
The profile levels for fingerprint acquisition are optional and are based upon those listed in the Mobile ID Best Practice
Recommendation.
Field Minimum
2
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
FAP = 10, 20, 30, 40, 45,
50, 60, 145, 150 or 160;
integer; see table 14
Code List: FINGERPRINT ACQUISITION PROFILE CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:FingerprintImageAcquisitionProfileCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
751
Type-14: Variable-Resolution Fingerprint Image
14.046: Image Subject Condition (SUB)
Description:
This field is optional. There may be different values for SUB in different instances of Type-14 records. For example, some
images may have been acquired antemortem, while others were accquired post-mortem. This field describes the condition of
the subject at the time of imaging.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
None
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:SubjectExistentialDetails
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
14.046_1: Image Subject Condition - Subject Status Code (SSC)
Description:
This information item is mandatory if this field is present. It is subject status code / SSC. Possible entries are: X = Status of
individual unknown, A = Data obtained from a living person – such as a victim or person unable to identify themselves or D =
Data obtained from a non-living person (deceased)
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
SSC = X, A, or D
Code List: SUBJECT STATUS CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:SubjectExistentialDetails
NIEM Element: biom:SubjectExistentialStatusCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
752
Type-14: Variable-Resolution Fingerprint Image
14.046_2: Image Subject Condition - Subject Body Status Code (SBSC)
Description:
This information item shall be entered if and only if SSC is D. It is subject body status code / SBSC. Its purpose is to indicate
whether the information relates to an entire corpse or a separate body part. The numeric value is selected from these
descriptors: 1 = Whole or 2 = Fragment
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
SBSC = 1 or 2
Code List: SUBJECT BODY STATUS CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:SubjectExistentialDetails
NIEM Element: biom:SubjectBodyStatusCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
14.046_3: Image Subject Condition - Subject Body Class Code (SBCC)
Description:
This information item shall be entered if and only if SSC is D. It is subject body class code/ SBCC. The numeric value is
selected from these descriptors: 1 = Natural Tissue or 2 = Decomposed
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
SBCC = 1 or 2
Code List: SUBJECT BODY CLASS CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:SubjectExistentialDetails
NIEM Element: biom:SubjectBodyClassCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
753
Type-14: Variable-Resolution Fingerprint Image
14.047: Capture Organization Name (CON)
Description:
This field is optional. Note that this can be different from the agency entered in Field 14.004: Source agency / SRC and Field
14.993: Source agency name / SAN. SRC and SAN describe the agency that created the record. Since the record may have
been forwarded by another agency to the final destination, Field 1.008: Originating agency identifier / ORI is used to indicate
the transmitting organization. In many implementation domains, there are a limited number of transmission organizations that
can send data. Therefore, the agency listed in SRC may send the transaction to another location that has access rights to the
final destination. This intermediary may add information to the transaction, as well. The final transmitting organization code is
listed in Field 1.008: Originating agency identifier / ORI. Its name may be entered in Originating agency name /OAN in Field
1.017: Agency names / ANM.
Field Minimum
1
Field Maximum
1000
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
none
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:ImageCaptureDetail/biom:CaptureOrganiza
tion
NIEM Element: nc:OrganizationUnitName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
14.901: Friction Ridge Capture Technology (FCT)
Description:
This is an optional field. It is a one or two-digit code signifying the type of technology that was used to capture the print for
transmission. For exemplar prints conveyed in Type-14 records, the only valid codes are 0 through 7, inclusive and 9 through
17 inclusive.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ FCT ≤ 7 or 9 ≤ FCT ≤
17; see Table 11
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail
NIEM Element: biom:FrictionRidgeCaptureTechnologyCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
754
Type-14: Variable-Resolution Fingerprint Image
14.902: Annotated Information (ANN)
Description:
This optional field is used to store annotation, logging, or processing information associated with one or more processing
algorithms or latent workstations (other than the FBI developed ULW).
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord
NIEM Element: biom:ProcessAnnotation
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.902_0: Annotated Information (ANN_0)
Description:
This optional field is used to store annotation, logging, or processing information associated with one or more processing
algorithms or latent workstations (other than the FBIdeveloped ULW).
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
Unlimited
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
755
Type-14: Variable-Resolution Fingerprint Image
14.902_1: Annotated Information - Greenwich Mean Time (GMT)
Description:
This information item is the Greenwich Mean Time (GMT) when the annotation occured. The data is formatted as
YYYYMMDDhhmmssZ, where the Z is indicates the zone description of 0 hours. Time (GMT) units. This time is independent of
the actual time zone where the time and date is recorded.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
YYYYMMDDHHMMSSZ for Traditional Encoding
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessUTCDate/nc:DateTime
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.902_2: Annotated Information - Processing Algorithm Name / Version (NAV)
Description:
The second information item of the Type-14 Annotated Information field shall contain an unformatted text string of up to 64
characters identifying the name and version of the processing algorithm or workstation.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessName
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
756
Type-14: Variable-Resolution Fingerprint Image
14.902_3: Annotated Information - Algorithm Owner (OWN)
Description:
The third information item Type-14 Annotated Information field shall contain an unformatted text string of up to 64 characters
with the contact information for the organization that owns the processing algorithm or latent workstation.
Field Minimum
1
Field Maximum
64
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessOwnerText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.902_4: Annotated Information - Process Description (PRO)
Description:
The fourth and final information item of the Type-14 Annotated Information field shall contain an unformatted text string of up to
255 characters describing a process or procedure applied to the sample in this Type-XX record.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessDescriptionText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
757
Type-14: Variable-Resolution Fingerprint Image
14.903: Device Unique Identifier (DUI)
Description:
The DUI shall contain a string uniquely identifying the device or source of the data. This field shall be one of: Host PC MAC
address, identified by the first character “M”, or Host PC processor ID, identified by the first character “P”. Note: ANSI/NIST ITL
1-2011 has deleted the options for “Serial number or No serial number” from Field 17.017, since it is available in the Make /
Model / Serial Number field.
Field Minimum
13
Field Maximum
16
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
Any
Format
n/a
Constraints
first character = M or P
Code List: DEVICE UNIQUE IDENTIFIER CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.904: Make/Model/Serial Number (MMS)
Description:
The MMS contains the make, model and serial number for the capture device. It shall consist of three information items. Each
information item shall be 1 to 50 characters. Any or all information items may indicate that information is unknown with the
value “0”.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
758
Type-14: Variable-Resolution Fingerprint Image
14.904_1: Make/Model/Serial Number - Make (MAK)
Description:
The name of the manufacturer for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceMakeText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.904_2: Make/Model/Serial Number - Model (MOD)
Description:
The model number for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceModelText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
759
Type-14: Variable-Resolution Fingerprint Image
14.904_3: Make/Model/Serial Number - Serial Number (SER)
Description:
The serial number for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceSerialNumberText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.993: Source Agency Name (SAN)
Description:
This is an optional field. It may contain up to 125 Unicode characters. It is the name of the agency referenced in Field 14.004:
Source agency / SRC for record types 9-99.
Field Minimum
1
Field Maximum
125
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageFingerImpressionImageRecord/biom:FingerImpressionImageDetail/biom:ImageCaptureDetail/biom:CaptureOrganiza
tion
NIEM Element: nc:OrganizationName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
760
Type-14: Variable-Resolution Fingerprint Image
14.994: External File Reference (EFR)
Description:
This conditional field shall be used to enter the URL/URI or other unique reference to a storage location for all digital
representations, if the data is not contained in Field 14.999: Fingerprint image / DATA. If this field is used, Field 14.999 shall
not be set. Only one of the two fields may be present in all instances of this record type. It is highly recommended that the user
state the format of the external file in Field 14.021: Comment / COM. Neither Field 14.994 nor Field 14.999 need be in the
record when Field 14.018: Amputated or bandaged / AMP has a value of “UP”.
Field Minimum
1
Field Maximum
200
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord
NIEM Element: biom:SourceExternalFileReferenceText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
14.995: Associated Context (ASC)
Description:
Optional field 14.995 is contained in biometric data sample Record Types 10 and above that may have instances of Record
Type-21 linked to it. Record Type-21 stores images and/or recordings that are not the actual source of the biometric data
contained in another Record Type, but do show the context of the biometric data. An example would be a photograph of a
glass that had latent prints on it. This is because there may be multiple instances of associated context records associated with
a single biometric sample.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord
NIEM Element: biom:AssociatedContext
XML Min/Max: 0 / 255
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
761
Type-14: Variable-Resolution Fingerprint Image
14.995_0: Associated Context (ASC_0)
Description:
Optional field 14.995 is contained in biometric data sample Record Types 10 and above that may have instances of Record
Type-21 linked to it. Record Type-21 stores images and/or recordings that are not the actual source of the biometric data
contained in another Record Type, but do show the context of the biometric data. An example would be a photograph of a
glass that had latent prints on it. This is because there may be multiple instances of associated context records associated with
a single biometric sample.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
255
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
14.995_1: Associated Context Number (ACN)
Description:
The first information item for the Associated Context field for a particular Record Type-21. This is mandatory for each Field
14.995, when the field is used. It contains an index to a particular instance of a Type-21 record in the transaction. This same
index value appears in the appropriate instance of Record Type-21 as Field 21.021: Associated context number / CAN. The
value of the CAN shall be a sequentially assigned a positive integer starting from one and incremented by one, not to exceed
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ ACN ≤ 255, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:AssociatedContext
NIEM Element: biom:ContextID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
762
Type-14: Variable-Resolution Fingerprint Image
14.995_2: Associated Context Number - Associated Segment Position (ASP)
Description:
The first information item is the associated segment position / ASP. This provides a unique index to a segmentation.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
1 ≤ ASP ≤ 99, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:AssociatedContext
NIEM Element: biom:ImageSegmentID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.996: Hash (HAS)
Description:
Optional field 14.996, is designed for use in Record types 10 and above with a Field xx.999 storing the biometric data. It is
comprised of 64 characters representing hexadecimal values. This field shall contain the hash value of the data in Field
14.999: Thus, each character may be a digit from “0” to “9” or a letter “A” through “F”. See the latest version of the Federal
Information Processing Standard 180, Secure Hash Standard for information on computing SHA-256 hashes. At the time of
this standard’s publication, FIPS 180-37 had been published. It is also possible to use Field xx.996 to contain the hash for data
stored externally, which is referenced in Field 20.994: External file reference / EFR and /or Field 21.994: Ex The ability to store
files externally is new to this version of the standard, and is only implemented for the two new record types referred to here.
Use of the hash enables the receiver of the data to perform quick searches of large databases to determine database. It is not
intended as an information assurance check. That is handled by Record Type-98: Information assurance record.
Field Minimum
64
Field Maximum
64
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord
NIEM Element: biom:ImageHashValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
763
Type-14: Variable-Resolution Fingerprint Image
14.997: Source Representation (SOR)
Description:
This optional field 14.997 is allowed in biometric data sample Record Types 10 and above that could have the biometric
sample derived from a source representation in Record Type-20. The biometric data is stored in Field 14.999.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord
NIEM Element: biom:SourceInformation
XML Min/Max: 0 / 255
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.997_0: Source Representation - Subfield: Repeating sets of information items (SOR_0)
Description:
This optional field 14.997 is allowed in biometric data sample Record Types 10 and above that could have the biometric
sample derived from a source representation in Record Type-20. The biometric data is stored in Field 14.999.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
255
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
764
Type-14: Variable-Resolution Fingerprint Image
14.997_1: Source Representation - Source Representation Number (SRN)
Description:
This is the first information item and is mandatory for each Field xx.997. It contains an index to a particular instance of a Type20 record in the transaction. This same index value appears in the appropriate instance of Record Type-20 as Field 20.021:
Source representation number / SRN. The value of the SRN shall be a sequentially assigned a positive integer starting from
one and incremented by one, not to exceed 255.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ SRN ≤ 255; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:SourceInformation
NIEM Element: biom:SourceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.997_2: Source Representation - Reference Segment Position (RSP)
Description:
The second information item is the reference segment position / RSP. This optional field provides a unique index to a
segmentation.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ RSP ≤ 99; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord/biom:SourceInformation
NIEM Element: biom:ImageSegmentID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
765
Type-14: Variable-Resolution Fingerprint Image
14.998: Geographic Sample Acquisition Location (GEO)
Description:
This optional field contains the location where the fingerprint sample was acquired – not where it is stored.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a, BiometricCaptureType
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.998_1: Geographic Sample Acquisition Location - Universal Time Entry (UTE)
Description:
The coordinated universal time (UTC) where the biometric sample was collected. This time is independent of the actual time
zone where the time and date is recorded. The date is YYYYMMDDhhmmssZ, where the Z is indicates the zone description of
0 hours. If sample collection time is unknown, set it to "00000000000000Z."
Field Minimum
dependent on encoding
Field Maximum
dependent on encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: biom:CaptureUTCDateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
766
Type-14: Variable-Resolution Fingerprint Image
14.998_2: Geographic Sample Acquisition Location - Latitude Degree Value (LTD)
Description:
The second information item is latitude degree value (LTD). This is a value that specifies the degree of latitude. The value shall
be between -90 (inclusive) and +90 (inclusive). The degrees may be expressed as an integer (without a decimal) or a real
number including decimals. If decimals are present, then minutes and seconds shall be empty. Examples: Buenos Aires,
Argentina: -34 (with minutes LTM = 36) NIST, Gaithersburg, Maryland: 39.137627 (no LTM or LTS)
Field Minimum
1
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal,Minus Sign
Format
n/a
Constraints
-90 ≤ LTD ≤ 90
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longer formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.998_3: Geographic Sample Acquisition Location - Latitude Minute Value (LTM)
Description:
This information item is latitude minute value (LTM). This is a value that specifies a minute of a degree. The value shall be
between 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall be empty. Thus, the allowed special character is a
period. The minute value can be empty, even if the degree value is an integer. LTM and LGM are co-conditional, so they shall
both be present if either is present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LTM < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longer formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
767
Type-14: Variable-Resolution Fingerprint Image
14.998_4: Geographic Sample Acquisition Location - Latitude Second Value (LTS)
Description:
The fourth information item is the latitude second value (LTS). This is a value that specifies a second of a minute. The integer
shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LTS < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longer formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.998_5: Geographic Sample Acquisition Location - Longitude Degree Value (LGD)
Description:
The fifth information item is the longitude degree value (LGD). It is a value that specifies the degree of a longitude. The value
shall be between -180 (inclusive) and +180 (inclusive). If LTD is present, then LGD shall be present. The degrees may be
expressed as whole numbers (without a decimal) or real numbers including decimals. If decimals are present, then minutes
and seconds are empty. Examples: Buenos Aires, Argentina: -58 (with minutes LGM = 22), NIST, Gaithersburg, Maryland: 77.216032 (no LGM or LGS)
Field Minimum
1
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal,Minus Sign,Plus
Sign
Format
n/a
Constraints
-180 ≤ LGD ≤ 180
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longer formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
768
Type-14: Variable-Resolution Fingerprint Image
14.998_6: Geographic Sample Acquisition Location - Longitude Minute Value (LGM)
Description:
The sixth information item is the longitude minute value (LGM). It is a value that specifies a minute of a degree. The value shall
be from 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall not appear. The minute value is empty, even if the
degree value is an integer. If LTM is present, then LGM shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LGM < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longer formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.998_7: Geographic Sample Acquisition Location - Longitude Second Value (LGS)
Description:
The seventh information item is the longitude second value (LGS). This is a value that specifies a second of a minute. The
integer shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer. If LTS is
present, then LGS shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LGS < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longer formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
769
Type-14: Variable-Resolution Fingerprint Image
14.998_8: Geographic Sample Acquisition Location - Elevation (ELE)
Description:
The eighth information item is elevation (ELE). It is expressed in meters. It is a numeric value. It is between -422 meters (Dead
Sea) and 8848 meters (Mount Everest). Allowed special characters are the negative sign and the period.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Minus Sign,Period
Format
n/a
Constraints
-422.000 ≤ ELE ≤ 8848.000;
real number
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longer formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.998_9: Geographic Sample Acquisition Location - Geodetic Datum Code (GDC)
Description:
The ninth information item is the geodetic datum code (GDC11). It is an alphanumeric value of 3 to 6 characters in length. This
information item is used to indicate which coordinate system was used to represent the values in information items 2 through
7. If no entry is made in this information item, then the basis for the values entered in the first eight information items shall be
WGS84, the code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values. If no entry is
made in this information item, then the basis for the values entered in the first eight information items shall be WGS84, the
code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values.
Field Minimum
3
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
see Look Up Codes
Code List: GEOGRAPHIC COORDINATE DATUM CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longer formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
770
Type-14: Variable-Resolution Fingerprint Image
14.998_10: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Zone (GCM)
Description:
It is an alphanumeric value of 2 to 3 characters. This is a one or two digit UTM zone number followed by the 8 degree
latitudinal band designator (which is a single letter).
Field Minimum
2
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
One or two digits followed
by a single letter
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationUTMCoordinateValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.998_11: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Easting (GCE)
Description:
The eleventh information item is the geographic coordinate universal transverse Mercator easting (GCE). It is an integer of 1 to
6 digits.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationUTMCoordinateValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
771
Type-14: Variable-Resolution Fingerprint Image
14.998_12: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Northing (GCN)
Description:
The twelfth information item is the geographic coordinate universal transverse Mercator northing (GCN). It is an integer of 1 to
8 digits.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationUTMCoordinateValue
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.998_13: Geographic Sample Acquisition Location - Geographic Reference Text (GRT)
Description:
It is a free form text describing a street address or other physical location (such as ‘Corner of Washington and Madison,
Geneva, NY’).
Field Minimum
1
Field Maximum
150
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: biom:GeographicLocationText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
772
Type-14: Variable-Resolution Fingerprint Image
14.998_14: Geographic Sample Acquisition Location - Geographic Coordinate Other System Identifier (OSI)
Description:
A fourteenth optional information item geographic coordinate other system identifier (OSI) allows for other coordinate systems.
This information items specifies the system identifier. It is up to 10 characters in length. Examples are: • MGRS (Militar Grid
Reference System), • USNG (United States National Grid), • GARS (Global Area Reference System), • GEOREF (World
Geographic Reference), • LANDMARK landmark (e.g. hydant) and position relative to the landmark.
Field Minimum
1
Field Maximum
10
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: biom:GeographicLocationSystemName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
14.998_15: Geographic Sample Acquisition Location - Geographic Coordinate Other System Value (OCV)
Description:
A fifteenth optional information item, is the geographic coordinate other system value (OCV). It shall only be present if OSI is
present in the record. It can be up to 126 characters in length. If OSI is LANDMARK, OCV is free text and may be up to 126
characters. For details on the formatting of OCV for the other coordinate systems shown in OSI as examples, see http://earthinfo.nga.mil/GandG/coordsys/grids/referencesys.html .
Field Minimum
1
Field Maximum
126
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
773
Type-14: Variable-Resolution Fingerprint Image
14.999: Fingerprint Image (DATA)
Description:
This conditional field, if present, contains the fingerprint image. If field 14.994: External file reference / EFR is present in the
record, then this field shall not appear. See Section 7.2 of ANSI/NIST ITL update 2015 for details. Neither Field 14.999 nor
Field 14,994 need be present in the record when Field 14.018: Amputated or bandaged / AMP has a value of “UP”. [<2015n]
Some domains and application profiles may still require an image in this field (such as the word “Amputated”).
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
B
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageFingerImpressionImageRecord
NIEM Element: nc:Base64BinaryObject
XML Min/Max: 0 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.001: Record Header (LEN)
Description:
The record header appears as the first field (xx.001) in each Record Type. It contains information particular to the encoding
format chosen, in order to enable proper reading of the record. In Traditional encoding, this field contains the record length in
bytes (including all information separators). In NIEM-conformant XML encoding, this field contains the RecordCategoryCode,
which is the numeric representation of the Record Type.
Field Minimum
T = 4; X = 1
Field Maximum
T = 8; X = 2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: dod-ebts:RecordCategoryCode
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
774
Type-15: Variable-Resolution Palmprint Image
15.002: Information Designation Character (IDC)
Description:
Each of the records present in a transaction, with the exception of the Type-1 record, shall include a field (xx.002) containing
the information designation character (IDC). The value of the IDC shall be a sequentially assigned positive integer starting
from zero and incremented by one up to a maximum of 99. IDC references are stated in Type-1 Field 1.003 Transaction
content (CNT) and shall be used to relate information items in the CNT field of the Type-1 record to the other records in the
transaction. Two or more records may share a single IDC solely to identify and link together records that pertain to different
representations of the same biometric trait.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ IDC ≤ 99; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.003: Impression Type (IMP)
Description:
This mandatory field shall indicate the manner by which the friction ridge print was obtained.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
IMP = 10, 11, 24, 25, 28,
29, 41 or 42
Code List: FRICTION RIDGE IMPRESSION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:biom:FingerImpressionImageDetailType
NIEM Element: biom:ImpressionCaptureCategoryCodeType
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
775
Type-15: Variable-Resolution Palmprint Image
15.004: Source Agency (SRC)
Description:
This is the identifier of the agency that actually created the record and supplied the information contained in it.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:TransactionOriginatingAgency
NIEM Element: itl:TransactionAgencyType
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.005: Palmprint Capture Date (PCD)
Description:
This ASCII field shall contain the date that the palmprint image contained in the record was captured. The date shall appear as
eight digits in the format YYYYMMDD.
Field Minimum
Dependent on encoding
Field Maximum
Dependent on encoding
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
Dependent on encoding
Special Characters
None
Format
YYYYMMDD
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmPrintImageDetailType
NIEM Element: biom:CaptureDate
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
776
Type-15: Variable-Resolution Palmprint Image
15.006: Horizontal Line Length (HLL)
Description:
HLL defines the number of pixels contained on a single horizontal line of the image. The maximum horizontal size is limited to
65,535 pixels in Record Types-4 and 8, and to 99,999 for other record types. The minimum value is 10 pixels. The total image
size (HLL times VLL) must be able to be accommodated in Field xx.001 for Traditional encoding.
This field is mandatory if
an image is present in Field 17.999: Iris image data (DATA). Otherwise it is absent.
Field Minimum
2
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
10 ≤ HLL ≤ 99999; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmPrintImageDetailType
NIEM Element: biom:HorizontalLineLengthPixelQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.007: Vertical Line Length (VLL)
Description:
VLL defines the number of horizontal lines contained in the image. The maximum vertical size is limited to 65,535 pixels in
Record Types-4 and 8, and to 99,999 for other record types. The minimum value is 10 pixels.
This field is mandatory if an
image is present in Field 17.999: Iris image data (DATA). Otherwise it is absent.
Field Minimum
2
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
10 ≤ VLL ≤ 99999; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmPrintImageDetailType
NIEM Element: biom:VerticalLineLengthPixelQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
777
Type-15: Variable-Resolution Palmprint Image
15.008: Scale Units (SLC)
Description:
This field is the image sampling frequency (pixel density). A value of “1” shall indicate pixels per inch. A value of “2” shall
indicate pixels per centimeter. A value of “0” in this field indicates that no scale is provided, and the quotient of THPS/TVPS
shall provide the pixel aspect ratio. For contact exemplar friction ridge images, a value of 1 or 2 shall be specified. For a value
of 1 or 2, the transmitted horizontal and vertical scales shall be the same. A value of 1 or 2 shall also be specified for latent
friction ridge prints if the lifted latent print is transmitted directly from a scanner. If the latent print is contained in a photograph,
a value of 1 or 2 shall be entered only if the image of the latent was captured with a scale measurement visible in the image
and the pixels across an inch or centimeter can be calculated – given the known characteristics of the camera and its distance
from the latent print. A value of 0 for a latent print indicates that the true ppi value of the image is not known. For non-contact
images of body parts, SLC shall be set to 0 unless the object being imaged is a fixed distance from the capture device and the
ppi or ppmm values for the capture device are accurately known at that fixed distance. (An example might be an iris capture
device with a very small effective capture zone). NGI-DOC-01078-10.0 - For A value of “0” in this field indicates that no scale
is provided, and NGI will reject transactions containing this value.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ SLC ≤ 2; integer
Code List: SCALE UNIT CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmPrintImageDetailType
NIEM Element: biom:ImageScaleUnitsCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
778
Type-15: Variable-Resolution Palmprint Image
15.009: Transmitted Horizontal Pixel Scale (THPS)
Description:
This is the integer pixel density used in the horizontal direction of the image if SLC has a value of “1” or “2”. If SLC has a value
of “0”, this information item shall contain the horizontal component of the pixel aspect ratio, up to 5 integer digits. For example,
if the SLC value = 1, then the value of THPS could be ‘1000’ for a 1000 ppi sensor.
When using certain formats, such as
PNG, conversion from ppm (or other scales) may result in a decimal value. Since these fields require integer values, rounding
should be used. Any value greater than x.0 and less than x.5 would be rounded down to x, regardless of the number of
significant digits to the right of the decimal.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmPrintImageDetailType
NIEM Element: biom:ImageHorizontalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.01: Transmitted Vertical Pixel Scale (TVPS)
Description:
This is the integer pixel density used in the vertical direction of the image if SLC has a value of “1” or “2”. If SLC has a value of
“0”, this information item shall contain the vertical component of the pixel aspect ratio, up to 5 integer digits. If SLC is 1 or 2,
then TVPS shall equal THPS.
When using certain formats, such as PNG, conversion from ppm (or other scales) may result
in a decimal value. Since these fields require integer values, rounding up at .5 should be used. For example with the values
1.3, 1.5 and 1.8 the resulting TVPS values would be 1, 2, and 2.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmPrintImageDetailType
NIEM Element: biom:ImageVerticalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
779
Type-15: Variable-Resolution Palmprint Image
15.011: Compression Algorithm (CGA)
Description:
This is a mandatory field. It shall specify the algorithm used to compress the transmitted color or grayscale images.
Field Minimum
3
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
See Table 19 Compression
codes in ANSI/NIST-ITL
update 2015.
Code List: COMPRESSION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:ImageCompressionAlgorithmText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.012: Bits Per Pixel (BPX)
Description:
This ASCII field shall contain the number of bits used to represent a pixel. This field shall contain an entry of “8” for normal
grayscale values of “0” to “255” or each RGB color component. Any entry in this field greater than “8” shall represent a
grayscale or color pixel component with increased precision.
For color, BPX represents the total number of bits per pixel
(not per color).
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
8 ≤ BPX ≤ 99
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmPrintImageDetailType
NIEM Element: biom:ImageBitsPerPixelQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
780
Type-15: Variable-Resolution Palmprint Image
15.013: Friction Ridge Generalized Position (FGP)
Description:
This field is used in Record types dealing with friction ridges. It specifies which friction ridge biometric sample was collected.
This field shall contain the palm print position that matches the palm print image. Valid codes range from 20 to 38, or 81 to
86228.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
20 ≤ FGP ≤ 38 or 81 ≤ FGP
≤ 86; see Look Up Codes
Format
n/a
Constraints
n/a
Code List: FRICTION RIDGE POSITION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Missing from biom:PalmPrintDetailType
NIEM Element: biom:PalmPositionCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.016: Scanned Horizontal Pixel Scale (SHPS)
Description:
This ASCII field shall specify the horizontal pixel density used for scanning providing the SLC field contains a "1" or a "2".
Otherwise, it indicates the horizontal component of the pixel aspect ratio.
This field is used if the transmission pixel scale
differs from the original image scale, as listed in Transmitted horizontal pixel scale (THPS).
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmPrintImageDetailType
NIEM Element: biom:CaptureHorizontalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
781
Type-15: Variable-Resolution Palmprint Image
15.017: Scanned Vertical Pixel Scale (SVPS)
Description:
This ASCII field shall specify the vertical pixel density used for scanning providing the SLC field contains a "1" or a "2".
Otherwise, it indicates the vertical component of the pixel aspect ratio.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmPrintImageDetailType
NIEM Element: biom:CaptureVerticalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.018: Amputated or Bandaged (AMP)
Description:
This optional field shall specify if one or more fingers are amputated or bandaged. This field shall consist of one subfield for
each amputated or missing finger. Each subfield shall contain two information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmPrintImageDetailType
NIEM Element: biom:PalmprintImageMissingArea
XML Min/Max: 0 / 9
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
782
Type-15: Variable-Resolution Palmprint Image
15.018_0: Amputated or Bandaged - Subfields: Repeating sets of information items (AMP_0)
Description:
This optional field shall specify if one or more fingers are amputated or bandaged. This field shall consist of one subfield for
each amputated or missing finger. Each subfield shall contain two information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
9
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmprintImageMissingArea
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
15.018_1: Amputated or Bandaged - Friction Ridge Amputation or Bandage Position (FRAP)
Description:
The first information item of the amputated and bandaged field indicating the friction ridge position between 21 and 38 or 81
through 86.
This information item is called the friction ridge amputated or bandaged position / FRAP to differentiate it from
FGP.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
21 ≤ FRAP ≤ 38 or 81 ≤
FRAP ≤ 86; see Look Up
Codes
Code List: PALM POSITION (NIST)
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmprintImageMissingArea
NIEM Element: biom:PalmPositionCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
783
Type-15: Variable-Resolution Palmprint Image
15.018_2: Amputated or Bandaged - Amputated or Bandaged Code (ABC)
Description:
This information item provides the code that describes the reason the finger's image is missing.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
ABC = XX or UP
Code List: AMPUTATED OR BANDAGED CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmprintImageMissingArea
NIEM Element: biom:PalmMissingAreaReasonCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.02: Comment (COM)
Description:
The optional Comment field appears in many record types and may be used to insert free text information. It is not reserved
exclusively for log-related information but has historically often been used for this purpose. It is limited to a maximum of 126
characters. This maximum size was established in order to maintain consistency across encodings. The maximum size differed
in the 2007 and 2008 versions of the standard.
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmPrintImageDetailType
NIEM Element: biom:ImageCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
784
Type-15: Variable-Resolution Palmprint Image
15.021: Palm Segment Position (SEG)
Description:
Contains offsets to the locations of image segments containing the individual fingers within the flat images of simultaneous
fingers from each hand or the two simultaneous thumbs. This field shall only be present if FGP = 20, 21, 23, 37, 38, 83 or 84
from as entered in Field 15.013: Friction ridge generalized position (FGP).
The subfield occurs at least once, and may be
repeated if more than one algorithm is used to segment the image.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:FingerImpressionImageDetailType
NIEM Element: biom:FingerprintImageSegmentPositionSquare
XML Min/Max: 0 / 17
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
15.021_0: Palm Segment Position - Subfields: Repeating sets of information items (SEG_0)
Description:
Contains offsets to the locations of image segments containing the individual fingers within the flat images of simultaneous
fingers from each hand or the two simultaneous thumbs. This field shall only be present if FGP = 20, 21, 23, 37, 38, 83 or 84
from as entered in Field 15.013: Friction ridge generalized position (FGP).
The subfield occurs at least once, and may be
repeated if more than one algorithm is used to segment the image.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
17
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:FingerprintImageSegmentPositionSquare
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
785
Type-15: Variable-Resolution Palmprint Image
15.021_1: Palm Segment Position - Friction Ridge Segment Position (FRSP)
Description:
The first information item is the friction ridge segment position / FRSP with values of 22, 24 – 36, 81, 82, 85 or 86 selected.
This information item is called the friction ridge segment position / FRSP to differentiate it from FGP.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
FSRP = 22, 24-36, 81, 82,
85 or 86; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:FingerprintImageSegmentPositionSquare
NIEM Element: biom:PalmPositionCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
15.021_5: Palm Segment Position - Bottom Vertical Coordinate Value (BVC)
Description:
This field contained the vertical offset from the upper left corner of the image down to the bottom of the bounding box.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
TVC < BVC < VLL; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:FingerprintImageSegmentPositionSquare
NIEM Element: biom:SegmentBottomVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
786
Type-15: Variable-Resolution Palmprint Image
15.021_2: Palm Segment Position - Left Horizontal Coordinate Value (LHC)
Description:
This field described the horizontal offset in pixels to the left edge of the bounding box relative to the origin positioned in the
upper left corner of the image.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ LHC < HLL; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:FingerprintImageSegmentPositionSquare
NIEM Element: biom:SegmentLeftHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
15.021_3: Palm Segment Position - Right Horizontal Coordinate Value (RHC)
Description:
This field describes the horizontal offset in pixels to the right edge of the bounding box relative to the origin positioned in the
upper left corner of the image.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
LHC < RHC < HLL; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:FingerprintImageSegmentPositionSquare
NIEM Element: biom:SegmentRightHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
787
Type-15: Variable-Resolution Palmprint Image
15.021_4: Palm Segment Position - Top Vertical Coordinate Value (TVC)
Description:
This field contains the vertical offset (pixel counts down) to the top of the bounding box.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ TVC < VLL; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:FingerprintImageSegmentPositionSquare
NIEM Element: biom:SegmentTopVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
15.023: Scanned Vertical Pixel Scale (SVPS)
Description:
This ASCII field shall specify the vertical pixel density used for scanning providing the SLC field contains a "1" or a "2".
Otherwise, it indicates the vertical component of the pixel aspect ratio.
This field is used if the transmission pixel scale
differs from the original image scale, as listed in Transmitted Vertical Pixel Scale (TVPS).
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: FBI EBTS
Status: Active
XML Parent: biom:CaptureVerticalPixelDensityValue
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
788
Type-15: Variable-Resolution Palmprint Image
15.024: Palm Quality Metric (PQM)
Description:
This ASCII set is used to specify one or more different metrics of palm image quality score data for the image stored in this
record. The meaning attributed to this metric must be defined and interpreted by the producer of the scoring algorithm or by the
person or system used to assign the metric to the palm print image. This field may contain one or more subfields, each
consisting of four information items.The first information item is the palm code. The other three items identify a quality score
and the algorithm used to create the quality score. This information is useful to enable the recipient of the quality score to
differentiate between quality scores generated by different algorithms and adjust for any differences in processing or analysis
as necessary. Valid codes range from 20 to 38, and 81 to 86.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmPrintImageDetailType
NIEM Element: biom:PalmprintImageQuality
XML Min/Max: 0 / 9
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.024_0: Palm Quality Metric - Subfields: Repeating sets of information items (PQM_0)
Description:
This ASCII set is used to specify one or more different metrics of palm image quality score data for the image stored in this
record. The meaning attributed to this metric must be defined and interpreted by the producer of the scoring algorithm or by the
person or system used to assign the metric to the palm print image. This field may contain one or more subfields, each
consisting of four information items.The first information item is the palm code. The other three items identify a quality score
and the algorithm used to create the quality score. This information is useful to enable the recipient of the quality score to
differentiate between quality scores generated by different algorithms and adjust for any differences in processing or analysis
as necessary. Valid codes range from 20 to 38, and 81 to 86.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
9
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmprintImageQuality
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
789
Type-15: Variable-Resolution Palmprint Image
15.024_1: Palm Quality Metric - Friction Ridge Metric Position (FRMP)
Description:
The first information item of a quality metric field indicating the friction ridge position.
81 to 86
Valid codes range from 20 to 38, and
Field Minimum
2
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
20 ≤ FRMP ≤ 38 or 81 ≤
FRMP ≤ 86; positive integer
Code List: FRICTION RIDGE POSITION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmPositionCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.024_2: Palm Quality Metric - Quality Value (QVU)
Description:
This information item shall contain the integer image quality score between 0 and 100 (inclusive) assigned to the image data
by a quality algorithm. Higher values indicate better quality. An entry of “255” shall indicate a failed attempt to calculate a
quality score. An entry of “254” shall indicate that no attempt to calculate a quality score was made.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ QVU ≤ 100 or QVU =
254 or 255; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmprintImageQuality
NIEM Element: biom:QualityValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
790
Type-15: Variable-Resolution Palmprint Image
15.024_3: Palm Quality Metric - Algorithm Vendor Identification (QAV)
Description:
This information item shall specify the ID of the vendor of the quality algorithm used to calculate the quality score. This 4-digit
hex value is assigned by IBIA and expressed as four ASCII characters. The IBIA shall maintain the Vendor Registry of CBEFF
Biometric Organizations that will map the value in this field to a registered organization.
Field Minimum
4
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
0000 ≤ QAV ≤ FFFF
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmprintImageQuality
NIEM Element: biom:QualityAlgorithmVendorID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.024_4: Palm Quality Metric - Algorithm Product Identification (QAP)
Description:
This information item shall specify a numeric product code assigned by the vendor of the quality algorithm, which may be
registered with the IBIA, but it is not required to be registered. It indicates which of the vendor’s algorithms was used in the
calculation of the quality score. This field contains the ASCII representation of the integer product code and should be within
the range 1 to 65535.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ QAP ≤ 65535; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmprintImageQuality
NIEM Element: biom:QualityAlgorithmProductID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
791
Type-15: Variable-Resolution Palmprint Image
15.03: Device Monitoring Mode (DMM)
Description:
This field provides information describing the human monitoring operation of the image capture device. This field will contain
an entry from to indicate the monitoring mode of the biometric sample capture device.
Field Minimum
7
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
See Table 6 Device
monitoring mode in
ANSI/NIST-ITL update 2015.
Code List: CAPTURE DEVICE MONITORING MODE CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:CaptureDeviceMonitoringModeCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.031: Subject Acquisition Profile_Palm Print (PAP)
Description:
This optional field lists the PAP levels associated with palm print acquisition devices.
Field Minimum
2
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
PAP = 70, 80, 170 or 180
see Lookup Values
Code List: Table 16
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
792
Type-15: Variable-Resolution Palmprint Image
15.046: Image Subject Condition (SUB)
Description:
This field is optional. This field is particularly useful if the image is obtained from a deceased person. However, its use is not
limited to such circumstances. Some implementation domains support the submission of fingerprints taken from deceased
individuals as latent prints, due to the quality of the friction ridges and the resulting images. In such cases, SSC is specified as
D. For latent images taken from a surface, the value is typically X.
There may be different values for SUB in different
instances of Type-15 records.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmprintImageQuality
NIEM Element: biom:SubjectExistentialDetails
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
15.046_1: Image Subject Condition - Subject Status Code (SSC)
Description:
The first information item is mandatory if this field is present. It is subject status code (SSC).
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
SSC = X, A or D
Code List: SUBJECT STATUS CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:SubjectExistentialDetails
NIEM Element: biom:SubjectExistentialStatusCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
793
Type-15: Variable-Resolution Palmprint Image
15.046_2: Image Subject Condition - Subject Body Status Code (SBSC)
Description:
The second information item shall be entered if and only if SSC is D. It is subject body status code (SBSC). Its purpose is to
indicate whether the information relates to an entire corpse or a separate body part.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
SBSC = 1 or 2
Code List: SUBJECT BODY STATUS CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:SubjectExistentialDetails
NIEM Element: biom:SubjectBodyStatusCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
15.046_3: Image Subject Condition - Subject Body Class Code (SBCC)
Description:
The third information item shall be entered if and only if SSC is D. It is subject body class code (SBCC).
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
SBCC = 1 or 2
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:SubjectExistentialDetails
NIEM Element: biom:SubjectBodyClassCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
794
Type-15: Variable-Resolution Palmprint Image
15.047: Capture Organization Name (CON)
Description:
This field is optional. Note that this can be different from the agency entered in Field 13.004: Source agency (SRC) and Field
13.993: Source agency name (SAN). SRC and SAN describe the agency that created the record. Since the record may have
been forwarded by another agency to the final destination, Field 1.008: Originating agency identifier (ORI) is used to indicate
the transmitting organization. In many implementation domains, there are a limited number of transmission organizations that
can send data. Therefore, the agency listed in SRC may send the transaction to another location that has access rights to the
final destination. This intermediary may add information to the transaction, as well. The final transmitting organization code is
listed in Field 1.008: Originating agency identifier (ORI). Its name may be entered in Originating agency name (OAN) in Field
1.017: Agency names (ANM).
The final transmitting organization code is listed in Field 1.008: Originating agency identifier /
ORI. Its name may be entered in Originating agency name /OAN in Field 1.017: Agencynames / ANM.
Field Minimum
1
Field Maximum
1000
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:PalmprintImageQuality
NIEM Element: nc:OrganizationUnitName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
15.200: Image Source Code (ISC)
Description:
This optional numeric field indicates to which source the included image belongs. This field allows images from multiple
biometric sets that use the same record type to be distinguishable. Two different values are used for the Palmprint card to
distinguish between the index finger image on the front of the card and the index finger that is part of the set of five finger
images on the back of the card. Livescan palm capture should use value
Field Minimum
0
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
*
Character Types
N
Special Characters
None
Format
n/a
Constraints
ISC = 1, 2, 3, or 4
Code List: ISC CODE
Source: FBI EBTS
Status: Active
XML Parent: fbi-ebts:ImageSourceCode
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
795
Type-15: Variable-Resolution Palmprint Image
15.901: Friction Ridge Capture Technology (FCT)
Description:
This is an optional field. It is a one or two-digit code signifying the type of technology that was used to capture the print for
transmission. See Section 7.7.4.5 for more detail and the meanings of the codes. For exemplar prints conveyed in Type-15
records, the only valid codes are 0 through 7, inclusive and 9 through 17 inclusive.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ FCT ≤ 7 or 9 ≤ FCT ≤
17; see Lookup code
Code List: Table 11
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
15.902: Annotated Information (ANN)
Description:
This is an optional field, listing the operations performed on the original source in order to prepare it for inclusion in a biometric
record type.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:ProcessAnnotation
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
796
Type-15: Variable-Resolution Palmprint Image
15.902_0: Annotated Information - Subfields: Repeating sets of information items (ANN_0)
Description:
This optional field is used to store annotation, logging, or processing information associated with one or more processing
algorithms, processes, or latent workstations (other than the FBI-developed ULW). If present, this text shall consist of one or
more subfields comprised of a set of information items. Four mandatory items comprise a subfield.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
Unlimited
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:ProcessAnnotation
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
15.902_1: Annotated Information - Greenwich Mean Time (GMT)
Description:
This information item is the Greenwich Mean Time (GMT) when the processing occured. The data is formatted as
YYYYMMDDhhmmssZ, where the Z is indicates the zone description of 0 hours. Time (GMT) units. This time is independent of
the actual time zone where the time and date is recorded.
Field Minimum
15
Field Maximum
15
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
YYYYMMDDHHMMSSZ for Traditional Encoding
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:ProcessAnnotation
NIEM Element: biom:ProcessUTCDate
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
797
Type-15: Variable-Resolution Palmprint Image
15.902_2: Annotated Information - Processing Algorithm Name / Version (NAV)
Description:
This information item shall contain text identifying the name and version of the processing algorithm, application, procedure, or
workstation.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:ProcessAnnotation
NIEM Element: biom:ProcessName
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.902_3: Annotated Information - Algorithm Owner (OWN)
Description:
This information item shall contain an unformatted text string of up to 64 characters with the contact information for the
organization that owns the processing algorithm or latent workstation. Where there is no 'algorithm owner,' enter N/A.
Field Minimum
1
Field Maximum
64
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:ProcessAnnotation
NIEM Element: biom:ProcessOwnerText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
798
Type-15: Variable-Resolution Palmprint Image
15.902_4: Annotated Information - Process Description (PRO)
Description:
This information item field shall contain text describing a process or procedure applied to the sample in this Type-9 record.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:ProcessAnnotation
NIEM Element: biom:ProcessDescriptionText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.903: Device Unique Identifier (DUI)
Description:
The DUI shall contain a string uniquely identifying the device or source of the data. This field shall be one of the following: a
Host PC MAC address (identified by the first character “M”), a Host PC processor ID (identified by the first character “P”).
since it is available in the Make / Model / Serial Number field.
Field Minimum
13
Field Maximum
16
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
Any
Format
n/a
Constraints
first character = M or P
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:CaptureDevice
NIEM Element: biom:DeviceID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
799
Type-15: Variable-Resolution Palmprint Image
15.904: Make/Model/Serial Number (MMS)
Description:
The MMS contains the make, model and serial number for the capture device. It shall consist of three information items. Each
information item shall be 1 to 50 characters. Unknown information may be indicated with the value "0." Any or all information
items may indicate that information is unknown with the value “0”.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:BiometricCapture
NIEM Element: biom:CaptureDevice
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.904_1: Make/Model/Serial Number - Make (MAK)
Description:
The name of the manufacturer for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:DeviceType
NIEM Element: biom:DeviceMakeText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
800
Type-15: Variable-Resolution Palmprint Image
15.904_2: Make/Model/Serial Number - Model (MOD)
Description:
The model number for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:DeviceType
NIEM Element: biom:DeviceModelText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.904_3: Make/Model/Serial Number - Serial Number (SER)
Description:
The serial number for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:DeviceType
NIEM Element: biom:DeviceSerialNumberText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
801
Type-15: Variable-Resolution Palmprint Image
15.993: Source Agency Name (SAN)
Description:
This is an optional field. It may contain up to 125 Unicode characters. It is the name of the agency referenced in Field xx.004:
Source agency / SRC for record types 9-99.
Field Minimum
1
Field Maximum
125
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:BiometricCapture
NIEM Element: biom:CaptureOrganization
XML Min/Max: 0 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.994: External File Reference (EFR)
Description:
This conditional field shall be used to enter the URL/URI or other unique reference to a storage location for all digital
representations, if the data is not contained in Field 15.999: Palm print image / DATA. If this field is used, Field 15.999: Palm
print image / DATA shall not be set. However, one of the two fields shall be present in all instances of this record type. It is
highly recommended that the user state the format of the external file in Field 15.020: Comment / COM. Type-15 records
generally contain an image in Field 15.999: Palm print image / DATA, or an external reference to an image in Field 15.994:
External file reference / EFR, but not both. Fields 15.994 and 15.999 are optional only if Field 15.018: Amputated or bandaged
/ AMPhas a value of “UP”. Fields 15.003, and 15.006 through 15.012 are mandatory if either Field 15.994 or 15.999 is used.
Field Minimum
1
Field Maximum
200
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: No EFR tag in XSD
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
802
Type-15: Variable-Resolution Palmprint Image
15.995: Associated Context (ASC)
Description:
This optional field refers to one or more Type 21 Records with the same ACN. Type 21 Records contain images that are NOT
used to derive the biometric data in Field 13.999: Latent friction ridge image (DATA) but that may be relevant to the collection
of that data, such as general scenes of the area where a latent print was found.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:AssociatedContext
XML Min/Max: 0 / 255
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.995_0: Associated Context - Subfields: Repeating sets of information items (ASC_0)
Description:
This optional field refers to one or more Type 21 Records with the same ACN. Type 21 Records contain images that are NOT
used to derive the biometric data in Field 13.999: Latent friction ridge image (DATA) but that may be relevant to the collection
of that data, such as general scenes of the area where a latent print was found.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
255
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:AssociatedContext
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
803
Type-15: Variable-Resolution Palmprint Image
15.995_1: Associated Context - Associated Context Number (ACN)
Description:
The first information item for the Associated Context field for a particular Record Type-21. This is mandatory for each Field
xx.995, when the field is used. It contains an index to a particular instance of a Type-21 record in the transaction. This same
index value appears in the appropriate instance of Record Type-21 as Field 21.021: Associated context number (CAN). The
value of the CAN shall be a sequentially assigned a positive integer starting from one and incremented by one, not to exceed
255.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ ACN ≤ 255; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:AssociatedContext
NIEM Element: biom:ContextID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.995_2: Associated Context - Associated Segment Position (ASP)
Description:
The first information item is the associated segment position (ASP). This provides a unique index to a segmentation.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
1 ≤ ASP ≤ 99; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:AssociatedContext
NIEM Element: biom:ImageSegmentID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
804
Type-15: Variable-Resolution Palmprint Image
15.996: Hash (HAS)
Description:
Optional field xx.996, is designed for use in Record types 10 and above with a Field xx.999 storing the biometric data. It is
comprised of 64 characters representing hexadecimal values. Thus, each character may be a digit from “0” to “9” or a letter “A”
through “F”. See the latest version of the Federal Information Processing Standard 180, Secure Hash Standard for information
on computing SHA-256 hashes. At the time of this standard’s publication, FIPS 180-37 had been published. It is also possible
to use Field xx.996 to contain the hash for data stored externally, which is referenced in Field 20.994: External file reference
(EFR) and/or Field 21.994: External file reference (EFR). The ability to store files externally is new to this version of the
standard, and is only implemented for the two new record types referred to here. Use of the hash enables the receiver of the
data to perform quick searches of large databases to determine if the data already exist in the database. It is not intended as
an information assurance check. That is handled by Record Type-98: Information assurance record.
Field Minimum
64
Field Maximum
64
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:ImageHashValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.997: Source Representation (SOR)
Description:
This optional field refers to a representation in Record Type-20 with the same SRN from which the data in Field 13.999: Latent
friction ridge image (DATA) was derived.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:SourceInformationType
XML Min/Max: 0 / 255
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
805
Type-15: Variable-Resolution Palmprint Image
15.997_0: Source Representation - Subfields: Repeating sets of information items (SOR_0)
Description:
This optional field refers to a representation in Record Type-20 with the same SRN from which the data in Field 13.999: Latent
friction ridge image (DATA) was derived.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
255
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:SourceInformationType
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
15.997_1: Source Representation - Source Representation Number (SRN)
Description:
This is the first information item and is mandatory for each Field xx.997. It contains an index to a particular instance of a Type20 record in the transaction. This same index value appears in the appropriate instance of Record Type-20 as Field 20.021:
Source representation number (SRN). The value of the SRN shall be a sequentially assigned a positive integer starting from
one and incremented by one, not to exceed 255.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ SRN ≤ 255; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:SourceInformationType
NIEM Element: biom:SourceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
806
Type-15: Variable-Resolution Palmprint Image
15.997_2: Source Representation - Reference Segment Position (RSP)
Description:
The first information item is the reference segment position (RSP). This provides a unique index to a segmentation.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ RSP ≤ 99; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:SourceInformationType
NIEM Element: biom:ImageSegmentID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.998: Geographic Sample Acquisition Location (GEO)
Description:
This optional field contains the location where the iris sample/original source/context information was acquired – not where it is
stored.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
807
Type-15: Variable-Resolution Palmprint Image
15.998_01: Geographic Sample Acquisition Location - Universal Time Entry (UTE)
Description:
The coordinated universal time (UTC) where the biometric sample was collected. This time is independent of the actual time
zone where the time and date is recorded. The date is YYYYMMDDhhmmssZ, where the Z is indicates the zone description of
0 hours. If sample collection time is unknown, set it to "00000000000000Z."
Field Minimum
dependent on encoding
Field Maximum
dependent on encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: biom:CaptureUTCDateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.998_02: Geographic Sample Acquisition Location - Latitude Degree Value (LTD)
Description:
The second information item is latitude degree value (LTD). This is a value that specifies the degree of latitude. The value shall
be between -90 (inclusive) and +90 (inclusive). The degrees may be expressed as an integer (without a decimal) or a real
number including decimals. If decimals are present, then minutes and seconds shall be empty. Examples: Buenos Aires,
Argentina: -34 (with minutes LTM = 36) NIST, Gaithersburg, Maryland: 39.137627 (no LTM or LTS)
Field Minimum
1
Field Maximum
9
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal,Minus Sign
Format
n/a
Constraints
-90 ≤ LTD ≤ 90
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
808
Type-15: Variable-Resolution Palmprint Image
15.998_03: Geographic Sample Acquisition Location - Latitude Minute Value (LTM)
Description:
This information item is latitude minute value (LTM). This is a value that specifies a minute of a degree. The value shall be
between 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall be empty. Thus, the allowed special character is a
period. The minute value can be empty, even if the degree value is an integer. LTM and LGM are co-conditional, so they shall
both be present if either is present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LTM < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.998_04: Geographic Sample Acquisition Location - Latitude Second Value (LTS)
Description:
The fourth information item is the latitude second value (LTS). This is a value that specifies a second of a minute. The integer
shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LTS < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
809
Type-15: Variable-Resolution Palmprint Image
15.998_05: Geographic Sample Acquisition Location - Longitude Degree Value (LGD)
Description:
The fifth information item is the longitude degree value (LGD). It is a value that specifies the degree of a longitude. The value
shall be between -180 (inclusive) and +180 (inclusive). If LTD is present, then LGD shall be present. The degrees may be
expressed as whole numbers (without a decimal) or real numbers including decimals. If decimals are present, then minutes
and seconds are empty. Examples: Buenos Aires, Argentina: -58 (with minutes LGM = 22), NIST, Gaithersburg, Maryland: 77.216032 (no LGM or LGS)
Field Minimum
1
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal,Minus Sign,Plus
Sign
Format
n/a
Constraints
-180 ≤ LGD ≤ 180
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.998_06: Geographic Sample Acquisition Location - Longitude Minute Value (LGM)
Description:
The sixth information item is the longitude minute value (LGM). It is a value that specifies a minute of a degree. The value shall
be from 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall not appear. The minute value is empty, even if the
degree value is an integer. If LTM is present, then LGM shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LGM < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
810
Type-15: Variable-Resolution Palmprint Image
15.998_07: Geographic Sample Acquisition Location - Longitude Second Value (LGS)
Description:
The seventh information item is the longitude second value (LGS). This is a value that specifies a second of a minute. The
integer shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer. If LTS is
present, then LGS shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LGS < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.998_08: Geographic Sample Acquisition Location - Elevation (ELE)
Description:
The eighth information item is elevation (ELE). It is expressed in meters. It is a numeric value. It is between -422 meters (Dead
Sea) and 8848 meters (Mount Everest). Allowed special characters are the negative sign and the period.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Minus Sign,Period
Format
n/a
Constraints
-422.000 ≤ ELE ≤ 8848.000;
real number
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
811
Type-15: Variable-Resolution Palmprint Image
15.998_09: Geographic Sample Acquisition Location - Geodetic Datum Code (GDC)
Description:
The ninth information item is the geodetic datum code (GDC11). It is an alphanumeric value of 3 to 6 characters in length. This
information item is used to indicate which coordinate system was used to represent the values in information items 2 through
7. If no entry is made in this information item, then the basis for the values entered in the first eight information items shall be
WGS84, the code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values. If no entry is
made in this information item, then the basis for the values entered in the first eight information items shall be WGS84, the
code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values.
Field Minimum
3
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
see Look Up Codes
Code List: GEOGRAPHIC COORDINATE DATUM CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.998_10: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Zone (GCM)
Description:
It is an alphanumeric value of 2 to 3 characters. This is a one or two digit UTM zone number followed by the 8 degree
latitudinal band designator (which is a single letter).
Field Minimum
2
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
One or two digits followed
by a single letter
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationUTMCoordinateValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
812
Type-15: Variable-Resolution Palmprint Image
15.998_11: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Easting (GCE)
Description:
The eleventh information item is the geographic coordinate universal transverse Mercator easting (GCE). It is an integer of 1 to
6 digits.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationUTMCoordinateValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.998_12: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Northing (GCN)
Description:
The twelfth information item is the geographic coordinate universal transverse Mercator northing (GCN). It is an integer of 1 to
8 digits.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationUTMCoordinateValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
813
Type-15: Variable-Resolution Palmprint Image
15.998_13: Geographic Sample Acquisition Location - Geographic Reference Text (GRT)
Description:
It is a free form text describing a street address or other physical location (such as ‘Corner of Washington and Madison,
Geneva, NY’).
Field Minimum
1
Field Maximum
150
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: biom:GeographicLocationText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.998_14: Geographic Sample Acquisition Location - Geographic Coordinate Other System Identifier (OSI)
Description:
A fourteenth optional information item geographic coordinate other system identifier (OSI) allows for other coordinate systems.
This information items specifies the system identifier. It is up to 10 characters in length. Examples are: • MGRS (Militar Grid
Reference System), • USNG (United States National Grid), • GARS (Global Area Reference System), • GEOREF (World
Geographic Reference), • LANDMARK landmark (e.g. hydant) and position relative to the landmark.
Field Minimum
1
Field Maximum
10
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: biom:GeographicLocationSystemName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
814
Type-15: Variable-Resolution Palmprint Image
15.998_15: Geographic Sample Acquisition Location - Geographic Coordinate Other System Value (OCV)
Description:
A fifteenth optional information item, is the geographic coordinate other system value (OCV). It shall only be present if OSI is
present in the record. It can be up to 126 characters in length. If OSI is LANDMARK, OCV is free text and may be up to 126
characters. For details on the formatting of OCV for the other coordinate systems shown in OSI as examples, see http://earthinfo.nga.mil/GandG/coordsys/grids/referencesys.html .
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
15.999: Palm print Image (DATA)
Description:
This field contains the palm print image. It shall contain an image, unless Field 15.018: Amputated or bandaged / AMP has a
value of “UP”. In the latter case, the field is optional.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
B
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: nc:Base64BinaryObject
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
815
Type-17: Iris Image Data
17.001: Record Header (LEN)
Description:
The record header appears as the first field (xx.001) in each Record Type. It contains information particular to the encoding
format chosen, in order to enable proper reading of the record. In Traditional encoding, this field contains the record length in
bytes (including all information separators). In NIEM-conformant XML encoding, this field contains the RecordCategoryCode,
which is the numeric representation of the Record Type.
Field Minimum
T = 4; X = 1
Field Maximum
T = 8; X = 2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.002: Information Designation Character (IDC)
Description:
This mandatory field shall contain the IDC assigned to this Type-17 record as listed in the information item IDC for this record
in Field 1.003: Transaction content / CNT.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ IDC ≤ 99; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord
NIEM Element: biom:ImageReferenceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
816
Type-17: Iris Image Data
17.003: Eye Label (ELR)
Description:
This mandatory field shall contain an identifier for the eye represented by the image in the record. An entry of “0” in this field
indicates that it is undefined which eye is present in this record. An entry of “1” in this field indicates that the image in this
record is the subject's right eye. An entry of “2” in this field indicates that the image in this record is the subject's left eye.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
ELR = 0,1 or 2
Code List: FEATURE IDENTIFIER CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:IrisEyePositionCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.004: Source Agency (SRC)
Description:
This mandatory field is the identifier of the agency that actually created the record and supplied the information contained in it.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:ImageCaptureDetail/biom:CaptureOrganization
NIEM Element: nc:OrganizationIdentification/nc:IdentificationID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
817
Type-17: Iris Image Data
17.005: Iris Capture Date (ICD)
Description:
This mandatory field shall contain the date that the iris biometric data contained in the record was captured.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
Encoding Specific
Special Characters
None
Format
YYYYMMDD for Traditional
Encoding and YYYY-MMDD for XML.
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:ImageCaptureDetail
NIEM Element: biom:CaptureDate/nc:Date
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.006: Horizontal Line Length (HLL)
Description:
HLL defines the number of pixels contained on a single horizontal line of the image. The maximum horizontal size is limited to
65,535 pixels in Record Types-4 and 8, and to 99,999 for other record types. The minimum value is 10 pixels. For Traditional
encoding, therecord size is limited by the maximum allowed value for Field 17.001 and the total image size in bytes must be
able to be accommodated in that field. This field is mandatory if an image is present in Field 17.999: Iris image data / DATA.
Otherwise it is absent.
Field Minimum
2
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
10 ≤ HLL ≤ 99999; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:HorizontalLineLengthPixelQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
818
Type-17: Iris Image Data
17.007: Vertical Line Length (VLL)
Description:
VLL defines the number of pixels contained in a single vertical line in the image. The maximum vertical size is limited to 65,535
pixels in Record Types-4 and 8, and to 99,999 for other record types. The minimum value is 10 pixels. This field is mandatory if
an image is present in Field 17.999: Iris image data / DATA. Otherwise it is absent.
Field Minimum
2
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
10 ≤ VLL ≤ 99999, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:VerticalLineLengthPixelQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.008: Scale Units (SLC)
Description:
The image sampling frequency (pixel density). A value of “1” shall indicate pixels per inch. A value of “2” shall indicate pixels
per centimeter. A value of “0” in this field indicates that no scale is provided, and the quotient of THPS/TVPS shall provide the
pixel aspect ratio. This field is mandatory if an image is present in Field 17.999: Iris image data / DATA. Otherwise it is absent.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ SLC ≤ 2, integer
Code List: SCALE UNIT CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:ImageScaleUnitsCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
819
Type-17: Iris Image Data
17.009: Transmitted Horizontal Pixel Scale (THPS)
Description:
This is the integer pixel density used in the horizontal direction of the image if SLC has a value of “1” or “2”. If SLC has a value
of “0”, this information item shall contain the horizontal component of the pixel aspect ratio, up to 5 integer digits. For example,
if the SLC value = 1, then the value of THPS could be ‘1000’ for a 1000 ppi sensor. When using certain formats, such as PNG,
conversion from ppm (or other scales) may result in a decimal value. Since these fields require integer values, rounding should
be used. For example with the values 1.3, 1.5 and 1.8 the resulting THPS values would be 1, 2, and 2. Any value greater than
x.0 and less than x.5 would be rounded down to x, regardless of the number of significant digits to the right of the decimal. This
field is mandatory if an image is present in Field 17.999: Iris image data / DATA. Otherwise it is absent.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:ImageHorizontalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.01: Transmitted Vertical Pixel Scale (TVPS)
Description:
This is the integer pixel density used in the vertical direction of the image if SLC has a value of “1” or “2”. If SLC has a value of
“0”, this information item shall contain the vertical component of the pixel aspect ratio, up to 5 integer digits. If SLC is 1 or 2,
then TVPS shall equal THPS. When using certain formats, such as PNG, conversion from ppm (or other scales) may result in
a decimal value. Since these fields require integer values, rounding up at .5 should be used. For example with the values 1.3,
1.5 and 1.8 the resulting TVPS values would be 1, 2, and 2. This field is mandatory if an image is present in Field 17.999: Iris
image data / DATA. Otherwise it is absent.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:ImageVerticalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
820
Type-17: Iris Image Data
17.011: Compression Algorithm (CGA)
Description:
This field is mandatory if an image is present in Field 17.999: Iris image data / DATA. Otherwise it is absent. It shall specify the
algorithm used to compress the transmitted color or grayscale images. While JPEG was allowed in prior versions of this
standard, it shall not be allowed for new images. Implementers may want to support JPEG decoding for handling legacy
images. If legacy images were stored in JPEG, they should be converted to PNG prior to transmission, with this transformation
noted in Field 17.902: Annotation information / ANN. The baseline JPEG algorithm (ISO/IEC 10918) shall not be used for Type17 iris images. It has been shown that both false non-match and false match rates increase due to the presence of tiling
artifacts introduced by JPEG's discrete cosine transform.
Field Minimum
3
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
CGA = NONE, PNG, JP2 or
JP2L
Code List: COMPRESSION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:ImageCompressionAlgorithmCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.012: Bits Per Pixel (BPX)
Description:
This field is mandatory if an image is present in Field 17.999: Iris image data / DATA. Otherwise it is absent. This field shall
contain the number of bits used to represent a pixel. This field shall contain an entry of “8” for normal grayscale values of “0” to
“255” or each RGB color component. Any entry in this field greater than “8” shall represent a grayscale or color pixel
component with increased precision. A maximum of 2 digits is allowed for this field. For color, BPX represents the total number
of bits per pixel (not per color). For instance, BPX=24 represents a 24-bit RGB image using 8 bits for each color.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
8 ≤ BPX ≤ 99
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:ImageBitsPerPixelQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
821
Type-17: Iris Image Data
17.013: Color Space (CSP)
Description:
This field is mandatory if an image is present in Field 17.999: Iris image data / DATA. Otherwise it is absent. It shall contain an
entry from Table 28 Color spaces of ANSI/NIST-ITL update 2015. If Field 17.025: Effective acquisition spectrum / EAS is set to
“NIR” this field shall be set to “GRAY”.
Field Minimum
3
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
See Table 28 Color spaces
from ANSI/NIST-ITL update
2015
Code List: COLOR SPACE CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:ImageColorSpaceCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.014: Rotation Angle of Eye (RAE)
Description:
This optional field shall indicate the in-plane rotation angle of the iris. Such rotation can be caused by head tilt, camera tilt, and
also by the common natural rotation of the eye itself. The rotation angle of the eye encoded in this field is defined here in
terms of roll of the subject's head. The angle is defined, and measured in degrees, as the angle between a line joining the pupil
or iris centers of the left and right eyes, and the horizontal axis of the imaging system. an angle is positive for counterclockwise rotation, as seen from the camera, of this line relative to the camera’s horizontal axis. The value “FFFF” indicates
rotation angle of eye is undefined. The in-plane eye rotation angle shall be recorded as angle = round (65535 * angle / 360)
modulo 65535. This is encoded as a hexadecimal value. For encoding angular orientation of an eye not directed toward the
camera, see Field 17.041: Frontal gaze (GAZ). It may be difficult to estimate rotation using a monocular camera. In such
cases, the rotation uncertainty encoded in Field 17.015: Rotation uncertainty (RAU) will be appropriately larger.
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
0000 ≤ RAE ≤ FFFF
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:IrisEyeRotationAngleValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
822
Type-17: Iris Image Data
17.015: Rotation Uncertainty (RAU)
Description:
This optional field shall indicate the uncertainty in the in-plane eye rotation given in Field 17.014: Rotation angle of eye (RAE).
The rotation uncertainty is non-negative and equal to [round (65535 * uncertainty / 180)]. The uncertainty is measured in
degrees and is the absolute value of maximum error. The value “FFFF” indicates that uncertainty is undefined. Note that this is
encoded as a hexadecimal value. This field is mandatory if Field 17.014: Rotation angle of eye (RAE) is present.
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
0000 ≤ RAU≤ FFFF
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:IrisEyeRotationUncertaintyValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.016: Image Property Code (IPC)
Description:
This set shall contain the image property code. It shall contain three information items. The first information item shall indicate
the horizontal orientation code. The second information item shall indicate the vertical orientation code. The third information
item shall indicate the specific scan type. Each information item shall be one character.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:IrisImageCapture
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
823
Type-17: Iris Image Data
17.016_1: Image Property Code - Horizontal Orientation Code (IHO)
Description:
This field shall be one of: “0” for Undefined, “1” for Base, or “2” for Flipped. “Base” orientation refers to images corresponding
to the view facing the subject, where the nasal side of subject’s left eye or outer edge of the subject’s right eye is on the left
side the of image. “Flipped” orientation refers to images where the orientation is opposite from that described for “Base”.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ IHO ≤ 2, integer
Code List: IMAGE ORIENTATION CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageCapture
NIEM Element: biom:IrisImageHorizontalOrientationCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.016_2: Image Property Code - Vertical Orientation Code (IVO)
Description:
This shall be one of: “0” for Undefined, “1” for Base, or “2” for Flipped. “Base” orientation refers to images where the superior
(top) edge of the eye is at the top of the image. “Flipped” orientation refers to images where the orientation is opposite from
that described for “Base”.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ IVO ≤ 2, integer
Code List: IMAGE ORIENTATION CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageCapture
NIEM Element: biom:IrisImageVerticalOrientationCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
824
Type-17: Iris Image Data
17.016_3: Image Property Code - Specific Scan Type (IST)
Description:
This shall be one of: “0” for Undefined and “1” for Progressive. “Progressive” indicates that the image was captured using
progressive scanning, in which case all image lines are generated sequentially. “2” for Interlace Frame, or “3” for Interlace
fields are deprecated and shall not be used in records claiming conformance to this version of the standard.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
IST = 0 or 1; X =
biom:ImageScanCategoryC
odeType
Code List: SCAN TYPE CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageCapture
NIEM Element: biom:IrisImageScanCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.017: Device Unique Identifier (DUI)
Description:
The DUI shall contain a string uniquely identifying the device or source of the data. This field shall be one of: Host PC MAC
address, identified by the first character “M”, or Host PC processor ID, identified by the first character “P”. Note: ANSI/NIST ITL
1-2011 has deleted the options for “Serial number or No serial number” from Field 17.017, since it is available in the Make /
Model / Serial Number field.
Field Minimum
13
Field Maximum
16
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
Any
Format
n/a
Constraints
first character = M or P
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
825
Type-17: Iris Image Data
17.019: Make/Model/Serial Number (MMS)
Description:
This is an optional field. The MMS contains the make, model and serial number for the capture device. It shall consist of three
information items. Each information item shall be 1 to 50 characters. Unknown information may be indicated with the value "0."
Any or all information items may indicate that information is unknown with the value “0”.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.019_1: Make/Model/Serial Number - Make (MAK)
Description:
The name of the manufacturer for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceMakeText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
826
Type-17: Iris Image Data
17.019_2: Make/Model/Serial Number - Model (MOD)
Description:
The model number for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceModelText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.019_3: Make/Model/Serial Number - Serial Number (SER)
Description:
The serial number for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceSerialNumberText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
827
Type-17: Iris Image Data
17.02: Eye Color (ECL)
Description:
This is an optional field that shall specify the subject's eye color or 'XXX' if it is unusual or unnatural, such as is the case when
colored contact lenses are present and the ‘real’ eye color cannot be ascertained, or unknown from the image (as is the case
with infra-red images).
Field Minimum
3
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
See Table 29 Eye color
codes from ANSI/NIST-ITL
update 2015
Code List: ALPHA EYE COLOR CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: j:PersonEyeColorCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.021: Comment (COM)
Description:
The optional Comment field appears in many record types and may be used to insert free text information. It is not reserved
exclusively for log-related information but has historically often been used for this purpose. It is limited to a maximum of 126
characters. This maximum size was established in order to maintain consistency across encodings. The maximum size differed
in the 2007 and 2008 versions of the standard.
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:ImageCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
828
Type-17: Iris Image Data
17.022: Scanned Horizontal Pixel Scale (SHPS)
Description:
This optional ASCII field shall specify the horizontal pixel density used for scanning of the original image / impression providing
that the SLC field contains a “1” or “2”. Otherwise, this shall indicate the horizontal component of the pixel aspect ratio, up to 5
integer digits. This field is used if the transmission pixel scale differs from the original image scale, as listed in Transmitted
horizontal pixel scale (THPS). Note that density is directly related to resolution.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:ImageCaptureDetail
NIEM Element: biom:CaptureHorizontalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.023: Scanned Vertical Pixel Scale (SVPS)
Description:
This optional ASCII field shall specify the horizontal pixel density used for scanning of the original image / impression providing
that the SLC field contains a “1” or “2”. Otherwise, this shall indicate the vertical component of the pixel aspect ratio, up to 5
integer digits. This field is used if the transmission pixel scale differs from the original image scale, as listed in Transmitted
vertical pixel scale (TVPS). Note that density is directly related to resolution. If SLC is 1 or 2 and SHPS is entered, then SVPS
shall equal SHPS.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:ImageCaptureDetail
NIEM Element: biom:CaptureVerticalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
829
Type-17: Iris Image Data
17.024: Image Quality Score (IQS)
Description:
This optional field shall specify one or more different metrics of image quality score data for the image stored in this record.
Each subfield shall contain three information items. They identify a quality score and the algorithm used to create the quality
score. This information is useful to enable the recipient of the quality score to differentiate between quality scores generated by
different algorithms and adjust for any differences in processing or analysis as necessary.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:ImageQuality
XML Min/Max: 0 / 9
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.024: Image Quality Score - Subfields: Repeating sets of information items (IQS_0)
Description:
This ASCII field shall specify a quality score data for the iris image stored in this record. Each subfield shall contain three
information items. They identify a quality score and the algorithm used to create the quality score. This information is useful to
enable the recipient of the quality score to differentiate between quality scores generated by different algorithms and adjust for
any differences in processing or analysis as necessary.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
9
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
830
Type-17: Iris Image Data
17.024_1: Image Quality Score - Quality Value (QVU)
Description:
This information item shall contain the integer image quality score between 0 and 100 (inclusive) assigned to the image data
by a quality algorithm. Higher values indicate better quality. An entry of “255” shall indicate a failed attempt to calculate a
quality score. An entry of “254” shall indicate that no attempt to calculate a quality score was made.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ QVU ≤ 100 or QVU =
254 or 255, integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:ImageQuality
NIEM Element: biom:QualityValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.024_2: Image Quality Score - Algorithm Vendor Identification (QAV)
Description:
This information item shall specify the ID of the vendor of the quality algorithm used to calculate the quality score. This 4-digit
hex value is assigned by IBIA and expressed as four ASCII characters. The IBIA shall maintain the Vendor Registry of CBEFF
Biometric Organizations that will map the value in this field to a registered organization.
Field Minimum
4
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
0000 ≤ QAV ≤ FFFF
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:ImageQuality
NIEM Element: biom:QualityAlgorithmVendorID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
831
Type-17: Iris Image Data
17.024_3: Image Quality Score - Algorithm Product Identification (QAP)
Description:
This information item shall specify a numeric product code assigned by the vendor of the quality algorithm, which may be
registered with the IBIA, but it is not required to be registered. It indicates which of the vendor’s algorithms was used in the
calculation of the quality score. This field contains the ASCII representation of the integer product code and should be within
the range 1 to 65535.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1≤ QAP ≤ 65535, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:ImageQuality
NIEM Element: biom:QualityAlgorithmProductID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.025: Effective Acquisition Spectrum (EAS)
Description:
This optional field indicates the acquisition spectrum used in capturing the iris image. The acquisition spectrum is the effective
acquisition spectrum, which is limited by both the lighting spectrum and the spectrum limitations of the acquisition device: it is
defined by the overlap of the two spectra. This field contains an alphabetic entry selected from the column “Value” in Table 109
Effective acquisition spectrum codes from ANSI/NIST-ITL update 2015.
Field Minimum
3
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
See Table 109 Effective
acquisition spectrum codes
from ANSI/NIST-ITL update
2015
Code List: LIGHTING SPECTRUM ACQUISITION CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageAcquisitionLightingSpectrum
NIEM Element: biom:AcquisitionLightingSpectrumCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
832
Type-17: Iris Image Data
17.026: Iris Diameter (IRD)
Description:
This field shall specify the expected iris diameter in pixels. This value may assist the processing algorithm(s) in the automated
examination of the image. IRD need not be the measured value of the diameter. It may range in value from 10 to 9999,
inclusive.
Field Minimum
2
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
10 ≤ IRD ≤ 9999; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:IrisDiameterPixelQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.027: Specified Spectrum Value (SSV)
Description:
This field shall only be present if Field 17.025: Effective acquisition spectrum (EAS) has a value of 'DEFINED'. It is comprised
of two information items: Spectrum lower bound and Spectrum upper bound.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
833
Type-17: Iris Image Data
17.027_1: Specified Spectrum Value - Spectrum Lower Bound (LOW)
Description:
It is a three or four digit entry indicating the lower frequency bound in nm (rounded to the nearest 10 nm).
Field Minimum
3
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
500 ≤ LOW, positive integer
evenly divisible by 10
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageAcquisitionLightingSpectrum
NIEM Element: biom:AcquisitionLightingSpectrumLowerMeasure
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.027_2: Specified Spectrum Value - Spectrum Upper Bound (HIG)
Description:
It is a three or four digit entry indicating the upper frequency bound in nm (rounded to the nearest 10 nm).
Field Minimum
3
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
510 ≤ HIG, positive integer
evenly divisible by 10
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageAcquisitionLightingSpectrum
NIEM Element: biom:AcquisitionLightingSpectrumUpperMeasure
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
834
Type-17: Iris Image Data
17.028: Damaged or Missing Eye (DME)
Description:
This optional field shall specify if one or both eyes are unable to provide usable iris images. The eye position is specified in
Field 17.003: Eye Label / ELR. This field shall contain a code from Table 110 Missing or damaged eye codes from ANSI/NISTITL update 2015. “UC” should be entered if the eye is physically present, but a usable iris image cannot be captured. An
example is when the eye is swollen shut due to injury.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
DME = MA or UC
Code List: MISSING AND DAMAGED EYE CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:IrisImageMissingReasonCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.030: Device Monitoring Mode (DMM)
Description:
This field provides information describing the level of human monitoring associated with the biometric sample capture. This
field will contain alphabetic values from Table 6 Device monitoring mode from ANSI/NIST-ITL update 2015 to indicate the
monitoring mode of the biometric sample capture device.
Field Minimum
7
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
See Table 6 Device
monitoring mode from
ANSI/NIST-ITL update 2015
Code List: CAPTURE DEVICE MONITORING MODE CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:ImageCaptureDetail
NIEM Element: biom:CaptureDeviceMonitoringModeCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
835
Type-17: Iris Image Data
17.031: Subject Acquisition Profile - IRIS (IAP)
Description:
This optional field lists the IAP level associated with the iris acquisition device. A device used to capture iris images shall be
based upon near-infrared wavelength capture, approximately 700 to 900 nm. Some systems may use a portion of this range,
which is acceptable. Iris image capture devices typically provide infrared lighting using LEDs to illuminate the iris. The
illumination is in a range partly visible to the human eye. Illumination shall be compliant with illumination standard IEC 825-1
and safety specification ISO 60825-1. The illumination wavelengths shall have > 90% of energy within the 700-900 nm band;
and > 35 % of energy in the 800-900 nm. band.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
IAP = 20, 30 or 40
Code List: IRIS SUBJECT ACQUISITION PROFILE CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:IrisImageAcquisitionProfileCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
836
Type-17: Iris Image Data
17.032: Iris Storage Format (ISF)
Description:
This optional field shall indicate the storage format of the iris image. The value shall be a single digit corresponding to the
column "ISF code." ISF format code 1 is designated for high resolution outputs. ISF level 2 is the format output in most
commerical iris acquisition systems and corresponds to the dimensions of the Video Graphics Array (VGA). Image storage
formats 3 and 7 are typically prepared by client software: ISF 3 images are cropped; and ISF 7 images are both cropped and
masked. These operations, used in conjunction with the standardized compression schemes, afford reduced record sizes. All
of the formats establish geometric specifications. For ISF = 1 and 2, there are minimum margin requirements specified in terms
of the estimated iris radius, R (see Table 111). For ISF = 3 and 7, there are exact margin requirements. These requirements
support accurate localization of the iris boundaries. In order to be considered acceptable as non-intrusive and to avoid
excessive geometric distortion, the minimum distance between the iris capture device’s lens and the subject’s eye must be at
least 100 millimeters. In order to provide an acceptable level of usability and ease of alignment, the camera must allow for
some variability in the position of the iris center relative to the camera. This is consistent with ISO/IEC 19794-6 and ISO/IEC
29794-6 specification concerning image margin requirements. The vertical margin shall be > 0.2 times the radius of the iris.
The horizontal margin shall be > 0.6 times the radius.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
ISF = 1, 2, 3 or 7
Code List: IRIS STORAGE FORM CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:IrisImageStorageFormatCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
837
Type-17: Iris Image Data
17.033: Iris Pupil Boundary (IPB)
Description:
This optional field defines the pupillary boundary, between the iris and pupil. A path is a filed containing a set of coordinates,
Paths can be defined as a cricle, ellipse, closed path (polygon), or open path. A circle only requires 2 points to define it. An
ellipse requires 3 points to define. Open paths (also called contours or polylines) and closed paths (polygons) on an image are
comprised of a set of vertices. For each, the order of the vertices shall be in their consecutive order along the length of the
path, either clockwise or counterclockwise. (A straight line of only two points may start at either end). A path may not have any
sides crossing. No two vertices shall occupy the same position. There may be up to 99 vertices.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:IrisImageIrisPupilBoundary
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.033_1: Boundary Code (BYC)
Description:
Defines the shape of a boundary of a feature within an image.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
BYC = C, E or P
Code List: BOUNDARY DEFINITION CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageIrisPupilBoundary
NIEM Element: biom:IrisBoundaryShapeCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
838
Type-17: Iris Image Data
17.033_2: Iris Pupil Boundary - Number of Points (NOP)
Description:
Specifies the number of vertices.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
2 ≤ NOP ≤ 99; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageIrisPupilBoundary
NIEM Element: biom:ImageFeatureVertexQuantity
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.033_3: Iris Pupil Boundary - Horizontal Point Offset (HPO)
Description:
The pixel counts to the right.
for a total of NOP pairs.
HPO and VPO information items are repeated as pairs, in order by point following the path –
Field Minimum
1
Field Maximum
5
Occurrence Minimum
2
Occurrence Maximum
NOP
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ HPO < HLL; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageIrisPupilBoundary/biom:ImageFeatureVertex
NIEM Element: biom:PositionHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
839
Type-17: Iris Image Data
17.033_4: Iris Pupil Boundary - Vertical Point Offset (VPO)
Description:
The pixel counts down from the origin.
the path – for a total of NOP pairs.
HPO and VPO information items are repeated as pairs, in order by point following
Field Minimum
1
Field Maximum
5
Occurrence Minimum
2
Occurrence Maximum
NOP
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ VPO < VLL, integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageIrisPupilBoundary/biom:ImageFeatureVertex
NIEM Element: biom:PositionVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.034: Iris Sclera Boundary (ISB)
Description:
This optional field defines the limbic boundary, between the iris and sclera.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:IrisImageIrisScleraBoundary
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
840
Type-17: Iris Image Data
17.034_1: Iris Sclera Boundary - Boundary Code (BYC)
Description:
Defines the shape of a boundary of a feature within an image.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
BYC = C, E or P
Code List: BOUNDARY DEFINITION CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageIrisScleraBoundary
NIEM Element: biom:IrisBoundaryShapeCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.034_2: Iris Sclera Boundary - Number of Points (NOP)
Description:
Specifies the number of vertices.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
2 ≤ NOP ≤ 99, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageIrisScleraBoundary
NIEM Element: biom:ImageFeatureVertexQuantity
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
841
Type-17: Iris Image Data
17.034_3: Iris Sclera Boundary - Horizontal Point Offset (HPO)
Description:
The pixel counts to the right.
for a total of NOP pairs.
HPO and VPO information items are repeated as pairs, in order by point following the path –
Field Minimum
1
Field Maximum
5
Occurrence Minimum
2
Occurrence Maximum
NOP
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ HPO < HLL, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageIrisScleraBoundary/biom:ImageFeatureVertex
NIEM Element: biom:PositionHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.034_4: Iris Sclera Boundary - Vertical Point Offset (VPO)
Description:
The pixel counts down from the origin.
the path – for a total of NOP pairs.
HPO and VPO information items are repeated as pairs, in order by point following
Field Minimum
1
Field Maximum
5
Occurrence Minimum
2
Occurrence Maximum
NOP
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ VPO < VLL, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageIrisScleraBoundary/biom:ImageFeatureVertex
NIEM Element: biom:PositionVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
842
Type-17: Iris Image Data
17.035: Upper Eyelid Boundary (UEB)
Description:
This optional field defines the boundary between the upper eyelid and the eye. This is an open path.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:IrisImageIrisUpperEyelidBoundary
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.035_1: Upper Eyelid Boundary - Boundary Code (BYC)
Description:
Defines the shape of a boundary of a feature within an image.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
BYC = P
Code List: BOUNDARY DEFINITION CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageIrisUpperEyelidBoundary
NIEM Element: biom:IrisBoundaryShapeCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
843
Type-17: Iris Image Data
17.035_2: Upper Eyelid Boundary - Number of Points (NOP)
Description:
Specifies the number of vertices.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
3 ≤ NOP ≤ 99, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageIrisUpperEyelidBoundary
NIEM Element: biom:ImageFeatureVertexQuantity
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.035_3: Upper Eyelid Boundary - Horizontal Point Offset (HPO)
Description:
The pixel counts to the right.
for a total of NOP pairs.
HPO and VPO information items are repeated as pairs, in order by point following the path –
Field Minimum
1
Field Maximum
5
Occurrence Minimum
2
Occurrence Maximum
NOP
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ HPO < HLL, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageIrisUpperEyelidBoundary/biom:ImageFeatureVertex
NIEM Element: biom:PositionHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
844
Type-17: Iris Image Data
17.035_4: Upper Eyelid Boundary - Vertical Point Offset (VPO)
Description:
The pixel counts down from the origin.
the path – for a total of NOP pairs.
HPO and VPO information items are repeated as pairs, in order by point following
Field Minimum
1
Field Maximum
5
Occurrence Minimum
2
Occurrence Maximum
NOP
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ VPO < VLL, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageIrisUpperEyelidBoundary/biom:ImageFeatureVertex
NIEM Element: biom:PositionVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.036: Lower Eyelid Boundary (LEB)
Description:
This optional field defines the boundary between the lower eyelid and the eye. This is an open path.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:IrisImageIrisLowerEyelidBoundary
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
845
Type-17: Iris Image Data
17.036_1: Lower Eyelid Boundary - Boundary Code (BYC)
Description:
Defines the shape of a boundary of a feature within an image.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
BYC = P
Code List: BOUNDARY DEFINITION CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageIrisLowerEyelidBoundary
NIEM Element: biom:IrisBoundaryShapeCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.036_2: Lower Eyelid Boundary - Number of Points (NOP)
Description:
Specifies the number of vertices
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
3 ≤ NOP ≤ 99, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageIrisLowerEyelidBoundary
NIEM Element: biom:ImageFeatureVertexQuantity
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
846
Type-17: Iris Image Data
17.036_3: Lower Eyelid Boundary - Horizontal Point Offset (HPO)
Description:
The pixel counts to the right.
for a total of NOP pairs.
HPO and VPO information items are repeated as pairs, in order by point following the path –
Field Minimum
1
Field Maximum
5
Occurrence Minimum
2
Occurrence Maximum
NOP
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ HPO < HLL, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageIrisLowerEyelidBoundary/biom:ImageFeatureVertex
NIEM Element: biom:PositionHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.036_4: Lower Eyelid Boundary - Vertical Point Offset (VPO)
Description:
The pixel counts down from the origin.
the path – for a total of NOP pairs.
HPO and VPO information items are repeated as pairs, in order by point following
Field Minimum
1
Field Maximum
5
Occurrence Minimum
2
Occurrence Maximum
NOP
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ VPO < VLL, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageIrisLowerEyelidBoundary/biom:ImageFeatureVertex
NIEM Element: biom:PositionVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
847
Type-17: Iris Image Data
17.037: Non-eyelid Occlusions - Non-eyelid Occlusions (NEO)
Description:
This optional field defines the outline and contents of any non-eyelid occlusions that partially or totally blocks the image of the
iris. It is a polygon. Each point on the polygon is represented by a pair of information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:IrisImageOcclusion
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.037_0: Non-eyelid Occlusions - Subfields: Repeating sets of information items information items
(NEO_0)
Description:
This optional field defines the outline and contents of any non-eyelid occlusions that partially or totally blocks the image of the
iris. It is a contour or a polygon.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
Unlimited
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
848
Type-17: Iris Image Data
17.037_1: Non-eyelid Occlusions - Occlusion Opacity (OCY)
Description:
The first information item contains the alphabetic code from Table 32: Occlusion opacity from ANSI/NIST-ITL update 2015.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
OCY = T, I, L or S
Code List: OCCLUSION OPACITY CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageOcclusion
NIEM Element: biom:IrisImageOcclusionOpacityCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.037_2: Non-eyelid Occlusions - Occlusion Type (OCT)
Description:
The second information item contains the alphabetic code from Table 33: Occlusion type from ANSI/NIST-ITL update 2015.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
OCT = L, S, C, R or O
Code List: OCCLUSIONS CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageOcclusion
NIEM Element: biom:IrisImageOcclusionCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
849
Type-17: Iris Image Data
17.037_3: Non-eyelid Occlusions - Number of Points (NOP)
Description:
Specifies the number of vertices.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
3 ≤ NOP ≤ 99, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageOcclusion
NIEM Element: biom:ImageFeatureVertexQuantity
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.037_4: Non-eyelid Occlusions - Horizontal Point Offset (HPO)
Description:
The pixel counts to the right.
for a total of NOP pairs.
HPO and VPO information items are repeated as pairs, in order by point following the path –
Field Minimum
1
Field Maximum
5
Occurrence Minimum
3
Occurrence Maximum
NOP
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ HPO < HLL, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageOcclusion/biom:ImageFeatureVertex
NIEM Element: biom:PositionHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
850
Type-17: Iris Image Data
17.037_5: Non-eyelid Occlusions - Vertical Point Offset (VPO)
Description:
The pixel counts down from the origin.
the path – for a total of NOP pairs.
HPO and VPO information items are repeated as pairs, in order by point following
Field Minimum
1
Field Maximum
5
Occurrence Minimum
3
Occurrence Maximum
NOP
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ VPO < VLL, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:IrisImageOcclusion/biom:ImageFeatureVertex
NIEM Element: biom:PositionVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.040: Range (RAN)
Description:
This optional field contains the estimated distance from the lens of the camera to the iris. It shall be measured in centimeters.
Field Minimum
1
Field Maximum
7
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:IrisImageRangeMeasure
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
851
Type-17: Iris Image Data
17.041: Frontal Gaze (GAZ)
Description:
This optional field describes the metric that estimates the degree of eye(s) sight-angle relative to the camera. The angle shall
be reported in degrees and defined as between: The optical axis of the eye, and a line connecting the optical center of the eye
and the optical center of the camera. This measure is inclusive of both head angular orientation and eye-gaze angle relative to
the head. The inclusive approach for gaze direction is not intended to be representative of the possible difficulty with iris
segmentation due to non-frontal head orientation. Hence, two images with the same frontal gaze, but significantly different
frontal head orientation may perform differently with different segmentation and matching algorithms. Note that iris image
recognition systems typically rely upon having a small gaze angle in the image. While not prohibited in this standard, it is
strongly discouraged that gaze angles greater than 15 degrees be used for enrollment or matching.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
0 ≤ GAZ ≤ 90, integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail
NIEM Element: biom:IrisImageGazeAngleMeasure
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.902: Annotated Information (ANN)
Description:
This is an optional field, listing the operations performed on the original source in order to prepare it for inclusion in a biometric
record type.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord
NIEM Element: biom:ProcessAnnotation
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
852
Type-17: Iris Image Data
17.902_0: Annotated Information - Subfields: Repeating sets of information items (ANN_0)
Description:
This optional field is used to store annotation, logging, or processing information associated with one or more processing
algorithms, processes, or latent workstations (other than the FBI-developed ULW). If present, this text shall consist of one or
more subfields comprised of a set of information items. Four mandatory items comprise a subfield.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
Unlimited
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
17.902_1: Annotated Information - Greenwich Mean Time (GMT)
Description:
This information item is the Greenwich Mean Time (GMT) when the processing occured. The data is formatted as
YYYYMMDDhhmmssZ, where the Z is indicates the zone description of 0 hours. Time (GMT) units. This time is independent of
the actual time zone where the time and date is recorded.
Field Minimum
15
Field Maximum
15
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
YYYYMMDDHHMMSSZ for Traditional Encoding
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessUTCDate/nc:DateTime
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
853
Type-17: Iris Image Data
17.902_2: Annotated Information - Processing Algorithm Name / Version (NAV)
Description:
This information item shall contain text identifying the name and version of the processing algorithm, application, procedure, or
workstation.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessName
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.902_3: Annotated Information - Algorithm Owner (OWN)
Description:
This information item shall contain an unformatted text string of up to 64 characters with the contact information for the
organization that owns the processing algorithm or latent workstation. Where there is no 'algorithm owner,' enter N/A.
Field Minimum
1
Field Maximum
64
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessOwnerText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
854
Type-17: Iris Image Data
17.902_4: Annotated Information - Process Description (PRO)
Description:
This information item field shall contain text describing a process or procedure applied to the sample in this Type-9 record.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessDescriptionText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.993: Source Agency Name (SAN)
Description:
This is an optional field. It may contain up to 125 Unicode characters. It is the name of the agency referenced in Field 17.004:
Source agency / SRC.
Field Minimum
1
Field Maximum
125
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:IrisImageDetail/biom:ImageCaptureDetail/biom:CaptureOrganization
NIEM Element: nc:OrganizationName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
855
Type-17: Iris Image Data
17.994: External File Reference (EFR)
Description:
This conditional field shall be used to enter the URL/URI or other unique reference to a storage location for all digital
representations, if the data is not contained in Field 17.999: Iris image data / DATA. If this field is used, Field 17.999 shall not
be set. However, one of the two fields shall be present in all instances of this record type. It is highly recommended that the
user state the format of the external file in Field 17.021: Comment / COM.Field 17.994 has been added to allow an iris
image to be in a location that can be remotely accessed. Field 17.999 may still used to transmit the image in the record. These
two fields are mutually exclusive. Only one may appear in the record.
Field Minimum
1
Field Maximum
200
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: New - Active
XML Parent: itl:PackageIrisImageRecord
NIEM Element: biom:SourceExternalFileReferenceText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
17.995: Associated Context (ASC)
Description:
This optional field refers to one or more Type 21 Records with the same ACN. Type 21 Records contain images that are NOT
used to derive the biometric data in Field 17.999: Latent friction ridge image (DATA) but that may be relevant to the collection
of that data, such as general scenes of the area where a latent print was found.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord
NIEM Element: biom:AssociatedContext
XML Min/Max: 0 / 255
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
856
Type-17: Iris Image Data
17.995_0: Associated Context - Subfields: Repeating sets of information items (ASC_0)
Description:
This optional field refers to one or more Type 21 Records with the same ACN. Type 21 Records contain images that are NOT
used to derive the biometric data in Field 17.999: Latent friction ridge image (DATA) but that may be relevant to the collection
of that data, such as general scenes of the area where a latent print was found.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
255
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
17.995_1: Associated Context - Associated Context Number (ACN)
Description:
The first information item for the associated context number / ACN for a particular Record Type-21. This is mandatory for each
Field xx.995, when the field is used. It contains an index to a particular instance of a Type-21 record in the transaction. This
same index value appears in the appropriate instance of Record Type-21 as Field 21.021: Associated context number (ACN).
The value of the ACN shall be a sequentially assigned a positive integer starting from one and incremented by one, not to
exceed 255.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ ACN ≤ 255, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:AssociatedContext
NIEM Element: biom:ContextID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
857
Type-17: Iris Image Data
17.995_2: Associated Context - Associated Segment Position (ASP)
Description:
The first information item in Field xx.995 is optional. It is the associated segment position / ASP. It contains the index to a
particular set of segmentation coordinates of the associated context data. This same segmentation index value appears in
Record Type-21 as the associated segment position / ASP in Field 21.016: Segments / SEG. There may be up to 99 segments
listed in Field 21.016, but only the relevant segment is contained in Field xx.995.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
1 ≤ ASP ≤ 99, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:AssociatedContext
NIEM Element: biom:ImageSegmentID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.996: Hash (HAS)
Description:
This optional field shall contain the hash value of the data in Field 17.999: Iris image data / DATA of this record, calculated
using SHA-256.
Field Minimum
64
Field Maximum
64
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord
NIEM Element: biom:ImageHashValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
858
Type-17: Iris Image Data
17.997: Source Representation (SOR)
Description:
This optional field refers to a representation in Record Type-20 with the same SRN from which the data in Field 17.999: Iris
image data / DATA was derived.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord
NIEM Element: biom:SourceInformation
XML Min/Max: 0 / 255
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.997_0: Source Representation - Subfields: Repeating sets of information items (SOR_0)
Description:
This optional field refers to a representation in Record Type-20 with the same SRN from which the data in Field 13.999: Latent
friction ridge image (DATA) was derived.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
255
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
859
Type-17: Iris Image Data
17.997_1: Source Representation - Source Representation Number (SRN)
Description:
This is the first information item and is mandatory for each Field xx.997. It contains an index to a particular instance of a Type20 record in the transaction. This same index value appears in the appropriate instance of Record Type-20 as Field 20.021:
Source representation number (SRN). The value of the SRN shall be a sequentially assigned a positive integer starting from
one and incremented by one, not to exceed 255.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ SRN ≤ 255, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:SourceInformation
NIEM Element: biom:SourceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.997_2: Source Representation - Reference Segment Position (RSP)
Description:
The first information item is the reference segment position (RSP). This provides a unique index to a segmentation.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ RSP ≤ 99, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord/biom:SourceInformation
NIEM Element: biom:ImageSegmentID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
860
Type-17: Iris Image Data
17.998: Geographic Sample Acquisition Location (GEO)
Description:
This optional field contains the location where the iris sample was acquired – not where it is stored.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a, BiometricCaptureType
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.998_01: Geographic Sample Acquisition Location - Universal Time Entry (UTE)
Description:
The coordinated universal time (UTC) where the biometric sample was collected. This time is independent of the actual time
zone where the time and date is recorded. The date is YYYYMMDDhhmmssZ, where the Z is indicates the zone description of
0 hours. If sample collection time is unknown, set it to "00000000000000Z."
Field Minimum
dependent on encoding
Field Maximum
dependent on encoding
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: biom:CaptureUTCDateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
861
Type-17: Iris Image Data
17.998_02: Geographic Sample Acquisition Location - Latitude Degree Value (LTD)
Description:
The second information item is latitude degree value (LTD). This is a value that specifies the degree of latitude. The value shall
be between -90 (inclusive) and +90 (inclusive). The degrees may be expressed as an integer (without a decimal) or a real
number including decimals. If decimals are present, then minutes and seconds shall be empty. Examples: Buenos Aires,
Argentina: -34 (with minutes LTM = 36) NIST, Gaithersburg, Maryland: 39.137627 (no LTM or LTS)
Field Minimum
1
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal,Minus Sign
Format
n/a
Constraints
-90 ≤ LTD ≤ 90
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longe formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.998_03: Geographic Sample Acquisition Location - Latitude Minute Value (LTM)
Description:
This information item is latitude minute value (LTM). This is a value that specifies a minute of a degree. The value shall be
between 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall be empty. Thus, the allowed special character is a
period. The minute value can be empty, even if the degree value is an integer. LTM and LGM are co-conditional, so they shall
both be present if either is present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal,Minus Sign,Plus
Sign
Format
n/a
Constraints
0 ≤ LTM < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longe formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
862
Type-17: Iris Image Data
17.998_04: Geographic Sample Acquisition Location - Latitude Second Value (LTS)
Description:
The fourth information item is the latitude second value (LTS). This is a value that specifies a second of a minute. The integer
shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LTS < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longe formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.998_05: Geographic Sample Acquisition Location - Longitude Degree Value (LGD)
Description:
The fifth information item is the longitude degree value (LGD). It is a value that specifies the degree of a longitude. The value
shall be between -180 (inclusive) and +180 (inclusive). If LTD is present, then LGD shall be present. The degrees may be
expressed as whole numbers (without a decimal) or real numbers including decimals. If decimals are present, then minutes
and seconds are empty. Examples: Buenos Aires, Argentina: -58 (with minutes LGM = 22), NIST, Gaithersburg, Maryland: 77.216032 (no LGM or LGS)
Field Minimum
1
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal,Minus Sign,Plus
Sign
Format
n/a
Constraints
-180 ≤ LGD ≤ 180
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longe formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
863
Type-17: Iris Image Data
17.998_06: Geographic Sample Acquisition Location - Longitude Minute Value (LGM)
Description:
The sixth information item is the longitude minute value (LGM). It is a value that specifies a minute of a degree. The value shall
be from 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall not appear. The minute value is empty, even if the
degree value is an integer. If LTM is present, then LGM shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LGM < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longe formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.998_07: Geographic Sample Acquisition Location - Longitude Second Value (LGS)
Description:
The seventh information item is the longitude second value (LGS). This is a value that specifies a second of a minute. The
integer shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer. If LTS is
present, then LGS shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LGS < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longe formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
864
Type-17: Iris Image Data
17.998_08: Geographic Sample Acquisition Location - Elevation (ELE)
Description:
The eighth information item is elevation (ELE). It is expressed in meters. It is a numeric value. It is between -422 meters (Dead
Sea) and 8848 meters (Mount Everest). Allowed special characters are the negative sign and the period.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Minus Sign,Period
Format
n/a
Constraints
-422.000 ≤ ELE ≤ 8848.000;
real number
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longe formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.998_09: Geographic Sample Acquisition Location - Geodetic Datum Code (GDC)
Description:
The ninth information item is the geodetic datum code (GDC11). It is an alphanumeric value of 3 to 6 characters in length. This
information item is used to indicate which coordinate system was used to represent the values in information items 2 through
7. If no entry is made in this information item, then the basis for the values entered in the first eight information items shall be
WGS84, the code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values. If no entry is
made in this information item, then the basis for the values entered in the first eight information items shall be WGS84, the
code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values.
Field Minimum
3
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
see Look Up Codes
Code List: GEOGRAPHIC COORDINATE DATUM CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longe formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
865
Type-17: Iris Image Data
17.998_10: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Zone (GCM)
Description:
It is an alphanumeric value of 2 to 3 characters. This is a one or two digit UTM zone number followed by the 8 degree
latitudinal band designator (which is a single letter).
Field Minimum
2
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
One or two digits followed
by a single letter
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationUTMCoordinateValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.998_11: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Easting (GCE)
Description:
The eleventh information item is the geographic coordinate universal transverse Mercator easting (GCE). It is an integer of 1 to
6 digits.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationUTMCoordinateValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
866
Type-17: Iris Image Data
17.998_12: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Northing (GCN)
Description:
The twelfth information item is the geographic coordinate universal transverse Mercator northing (GCN). It is an integer of 1 to
8 digits.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationUTMCoordinateValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.998_13: Geographic Sample Acquisition Location - Geographic Reference Text (GRT)
Description:
It is a free form text describing a street address or other physical location (such as ‘Corner of Washington and Madison,
Geneva, NY’).
Field Minimum
1
Field Maximum
150
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: biom:GeographicLocationText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
867
Type-17: Iris Image Data
17.998_14: Geographic Sample Acquisition Location - Geographic Coordinate Other System Identifier (OSI)
Description:
A fourteenth optional information item geographic coordinate other system identifier (OSI) allows for other coordinate systems.
This information items specifies the system identifier. It is up to 10 characters in length. Examples are: • MGRS (Militar Grid
Reference System), • USNG (United States National Grid), • GARS (Global Area Reference System), • GEOREF (World
Geographic Reference), • LANDMARK landmark (e.g. hydant) and position relative to the landmark.
Field Minimum
1
Field Maximum
10
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: biom:GeographicLocationSystemName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
17.998_15: Geographic Sample Acquisition Location - Geographic Coordinate Other System Value (OCV)
Description:
A fifteenth optional information item, is the geographic coordinate other system value (OCV). It shall only be present if OSI is
present in the record. It can be up to 126 characters in length. If OSI is LANDMARK, OCV is free text and may be up to 126
characters. For details on the formatting of OCV for the other coordinate systems shown in OSI as examples, see http://earthinfo.nga.mil/GandG/coordsys/grids/referencesys.html .
Field Minimum
1
Field Maximum
126
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
868
Type-17: Iris Image Data
17.999: Iris Image Data (DATA)
Description:
This field contains the iris image. See Section 7.2 of ANSI/NIST ITL update 2015 for details. If Field 17.994: External file
reference / EFR is present in this record, then this field shall not appear. Neither this field or Field 17.994: External file
reference / EFR shall be present in this record when Field 17.028: Damaged or missing eye / DME is in this record (indicating
an eye is missing or is unable to provide a usable iris image). Some domains and application profiles may require a field with a
'substitute image' such as the words 'Missing Eye'.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
B
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageIrisImageRecord
NIEM Element: nc:Base64BinaryObject
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.001: Record Header (LEN)
Description:
The record header appears as the first field (xx.001) in each Record Type. It contains information particular to the encoding
format chosen, in order to enable proper reading of the record. In Traditional encoding, this field contains the record length in
bytes (including all information separators). In NIEM-conformant XML encoding, this field contains the RecordCategoryCode,
which is the numeric representation of the Record Type.
Field Minimum
T = 4; X = 1
Field Maximum
T = 8; X = 2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: dod-ebts:ImageCaptureType
NIEM Element: od-ebts:RecordCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
869
Type-18: DNA Data
18.002: Information Designation Character (IDC)
Description:
Each of the records present in a transaction, with the exception of the Type-1 record, shall include a field (xx.002) containing
the information designation character / IDC. The value of the IDC shall be a sequentially assigned positive integer starting
from zero and incremented by one up to a maximum of 99. IDC references are stated in Type-1 Field 1.003 Transaction
content (CNT) and shall be used to relate information items in the CNT field of the Type-1 record to the other records in the
transaction. Two or more records may share a single IDC solely to identify and link together records that pertain to different
representations of the same biometric trait.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤IDC ≤99; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord
NIEM Element: biom:ImageReferenceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.003: DNA Laboratory Setting (DLS)
Description:
This field is mandatory. The first information item is mandatory. The remaining information items are optional for all unit types.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNALaboratory
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
870
Type-18: DNA Data
18.003_1: DNA Laboratory Setting - Unit Type (UTY)
Description:
The first information item unit type / UTY is mandatory and contains a numeric value from Table 113 DNA laboratory setting
(DLS) from ANSI/NIST-ITL Update: 2015.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤UTY≤4; integer
Code List: DNA LABORATORY SETTING UNIT TYPE CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNALaboratory
NIEM Element: biom:DNALaboratoryUnitCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.003_2: DNA Laboratory Setting - Lab Type (LTY)
Description:
The second information item is the lab type / LTY. It is mandatory if the value for UTY is 1 or 2. It is not entered otherwise.
When present, this information item contains a single character describing the laboratory that processed the DNA: G =
Government, I = Industry, O = Other laboratory, U = Unknown.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
LTY = G, I, O or U
Code List: DNA LABORATORY SETTING LAB TYPE CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNALaboratory
NIEM Element: biom:DNALaboratoryCategoryCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
871
Type-18: DNA Data
18.003_3: DNA Laboratory Setting - Accreditation Information (ACC)
Description:
The third information item is the accreditation information / ACC. It is mandatory if the value for UTY is 1 or 2. It shall not be
entered otherwise. When present, this information item shall contain a minimum of one numeric character if the value is 0 or a
minimum of two characters (one numeric followed immediately by one alpha character if the lab is accredited). If the laboratory
has an unknown accreditation status, three numeric characters '255' are entered. The values in this information item shall be
separated individually by commas between accreditation and scope pairings. More than one accreditation and scope of
accreditation is permitted. Allowable numeric values are: 0 = No Accreditation, 1 = ISO Accreditation, 2 = GLP, Accreditation, 3
= AABB Accreditation, 4 = ISO/ILAC Guide 19 Accreditation, 5 = ASCLD Lab Accreditation, 6 = Other 255 = Unknown. The
scope of accreditation is incorporated as an alphabetic code immediately following the accreditation body / source numeric
value. The scope of accreditation is for what type of DNA technology that the laboratory is accredited. These are: N = Nuclear,
M = Mitochondrial, D = Database O = Other.
Field Minimum
1
Field Maximum
35
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
Comma
Format
n/a
Constraints
Numeric (0,1,2,3,4,5,6 or
255). It may be followed by
an alpha string (N, M, D
and/or O). That may be
followed by up to 5 more
such strings, each
separated by a comma. The
entire string is treated as a
single information item.
Code List: DNA LABORATORY SETTING ACCREDITATION STATUS CODE and DNA LABORATORY ACCREDITATION
SCOPE CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNALaboratory
NIEM Element: biom:DNALaboratoryAccreditation
XML Min/Max: 0 / 6
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
872
Type-18: DNA Data
18.003_4: DNA Laboratory Setting - Name of the Organization (NOO)
Description:
The fourth information item is the name of the organization / NOO that originally processed the DNA data. This may be
different from the entry in Field 18.004: Source Agency / SRC. This is an optional information item. It is entered in Unicode
characters and is unlimited in length.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNALaboratory
NIEM Element: nc:OrganizationName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.003_5: DNA Laboratory Setting - Point of Contact (POC)
Description:
This information item is the point of contact / POC who composed the DNA record metadata. This is an optional information
item that could include the name, telephone number and e-mail address of the person responsible for this record submission.
This information item may be up to 200 Unicode characters.
Field Minimum
1
Field Maximum
200
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNALaboratory
NIEM Element: nc:OrganizationPrimaryContactInformation/nc:ContactInformationDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
873
Type-18: DNA Data
18.003_6: DNA Laboratory Setting - Code of Sending Country (CSC)
Description:
The sixth information item is optional. It is the ISO-3166-1 code of the sending country / CSC. This is the code of where the
DNA was processed, not necessarily the nation of the agency entered in Field 18.004: Source agency / SRC. All three formats
specified in ISO-3166-1 are allowed (Alpha2, Alpha3 and Numeric). A country code is either 2 or 3 characters long. CSC
defaults to ISO-3166-1 coding. If GENC used, then the version of that alternate code is entered in Field 1.018: Geographic
name set / GNS, which applies to ALL country codes in all records within the transaction.
The DoD EBTS 4.0 default for this
field is the GENC three character alpha codelist (genc:CountryAlpha3CodeType).
Field Minimum
2
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
If Field 1.018: Geographic
name set / GNS is present,
then value is from the
alternate GENC set
specified in that field.
Otherwise, the value is from
ISO-3166-1.
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNALaboratory
NIEM Element: biom:DNALaboratoryProcessingCountry
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.003_7: DNA Laboratory Setting - International Organization Name (ION)
Description:
The seventh information item is optional. It is the international organization name / ION of the submitting organization. This is
completed if the DNA was processed by an organization that is not affiliated with a country (such as a multinational
organization). This optional information item is the name/acronym of an organization, and may be up to 100 Unicode
characters.
Field Minimum
1
Field Maximum
100
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNALaboratory
NIEM Element: biom:DNALaboratoryInternationalOrganizationName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
874
Type-18: DNA Data
18.004: Source Agency (SRC)
Description:
This mandatory field is the identifier of the agency that actually created the record and supplied the information contained in it.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture/biom:CaptureOrganization
NIEM Element: nc:OrganizationIdentification/nc:IdentificationID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.005: Number of Analysis Flag (NAL)
Description:
This mandatory field indicates whether the DNA record contains multiple data analyses or a single data analysis. Possible
entries are: 0="Multiple" or 1="Single".
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
NAL = 0 or 1
Code List: DNA LABORATORY NUMBER OF ANALYSES CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNAAnalysisQuantityCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
875
Type-18: DNA Data
18.006: Sample Donor Information (SDI)
Description:
This field is mandatory. It indicates if the DNA information contained in the record is from the subject of the transaction or from
another person (the subject of the record), that is being sent to assist in establishing or verifying the identity of the subject of
the transaction. Each subject of a record may have a distinct Type-2 record contained in the transaction. If that is the case, it
is highly recommended that Field 18.992: Type-2 Record cross reference / T2C be used to link the Type-18 record to the
appropriate Type-2 record. Note that multiple Type-18 records may be included in a single transaction; only one record may
have a value of 0 for the first information item.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNADonor
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.006_1: Sample Donor Information - DNA Sample Donor (DSD)
Description:
The allowed numeric values for the first mandatory information item DNA sample donor / DSD are: 0 = Subject of the record is
also the subject of the transaction, 1 = Claimed, purported or validated relative (subject of the record is known to be a different
person than the subject of the transaction), 2 = Unknown source (subject of the record may be different but need not be
different than the subject of the transaction – such as when a dismembered body part's DNA is to be compared against the
DNA of the body part already established to be associated with subject of the transaction).
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
DSD = 0, 1 or 2
Code List: DNA SAMPLE DONOR CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNADonor
NIEM Element: biom:DNADonorCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
876
Type-18: DNA Data
18.006_2: Sample Donor Information - Gender ID (GID)
Description:
The second information item is the gender ID / GID. This is an optional single character identifier of "M" or "F" or "U". "U"
indicates unknown. GID may be set based on self-assignment by the specimen donor. The GID may not match the results from
the Amelogenin or for other valid cases.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
GID = M, F or U
Code List: DNA SAMPLE DONOR GENDER
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNADonor
NIEM Element: nc:PersonSexText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.006_3: Sample Donor Information - Date of Last Contact (DLC)
Description:
The third information item, date of last contact / DLC is an optional date field. The local date is recorded as YYYYMMDD. Note
that this may be a different date than the corresponding GMT, due to time zone differences.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Encoding Specific
Special Characters
Colon, Period
Format
YYYYMMDDhh:mm:ss.sss
Constraints
N/A
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNADonor
NIEM Element: biom:DNADonorLastContactDate/nc:Date
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
877
Type-18: DNA Data
18.006_4: Sample Donor Information - Donor Date of Birth (DOB)
Description:
The fourth information item, date of birth / DOB, is an optional date field. The local date is recorded as YYYYMMDD. Note that
this may be a different date than the corresponding GMT, due to time zone differences.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Encoding Specific
Special Characters
Colon, Period
Format
YYYYMMDDhh:mm:ss.sss
Constraints
N/A
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNADonor
NIEM Element: nc:PersonBirthDate/nc:Date
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.006_5: Sample Donor Information - Ethnic Group (EGP)
Description:
The fifth information item is the ethnic group / EGP. It is an optional string of 50 Unicode characters used to describe the ethnic
group to which the subject belongs.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNADonor
NIEM Element: nc:PersonEthnicityText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
878
Type-18: DNA Data
18.006_6: Sample Donor Information - Dental Records Available (DRA)
Description:
The sixth information item is optional and indicates if dental records are available for the subject (dental records available /
DRA). This information item shall be entered only if DSD = 0. Allowed numeric values are: 0 = No, 1 = Yes 2 = Unknown.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
DRA = 0, 1 or 2; nonnegative integer
Code List: DENTAL RECORD AVAILABLE INDICATION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNADonor
NIEM Element: biom:DNADonorDentalRecordsAvailableCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.006_7: Sample Donor Information - Sample Collection Location Description (LLC)
Description:
The seventh optional information item is the sample collection location description / LLC. It is an optional string of up to 4000
Unicode characters.
Field Minimum
1
Field Maximum
4000
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNADonor
NIEM Element: biom:DNADonorCollectionLocationDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
879
Type-18: DNA Data
18.006_8: Sample Donor Information - Sample Donor Status (SDS)
Description:
The eighth optional information item is the sample donor status / SDS. This information item will include whether or not the
sample donor is deceased, missing or unknown. Normally, this item would only be used for the sample associated with the
subject of the transaction (SDI = 0), but it could be possible to use it in other cases, such as a hair sample from a deceased
relative. It could also be 'unknown' for the purported relative’s status, but DNA samples were available for that individual (such
as blood sample previously collected). Allowed numeric values are: 0 = Deceased, 1 = Missing Person 2 = Unknown.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
SDS = 0, 1 or 2; nonnegative integer
Code List: DNA SAMPLE DONOR STATUS CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNADonor
NIEM Element: biom:DNADonorStatusCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.007: Claimed Or Purported Relationship (COPR)
Description:
This field is mandatory if the value for [DNA Sample Donor / DSD] is equal to 1 [Claimed, purported or validated relative]. It is a
numeric value selected from the “Relationship code” column of Table 114 Relationship table in ANSI/NIST-ITL Update: 2015.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
1 ≤COPR ≤7; positive
integer
Code List: RELATIONSHIP CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNAClaimedRelationshipCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
880
Type-18: DNA Data
18.008: Validated Relationship (VRS)
Description:
This field is optional and is a numeric value selected from the “Relationship code” column of Table 114 Relationship table in
ANSI/NIST-ITL Update: 2015. This information item is completed based upon a comparison of the subject’s DNA with the DNA
of the person with whom the relationship is claimed or purported. It is only filled in if DSD = 1. This information item is
completed based upon a comparison of the subject’s DNA with the DNA of the person with whom the relationship is claimed or
purported. It is only filled in if [Donor Status Description] DSD = 1 [Claimed or Purported Relationship].
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤VRS ≤7; positive integer
Code List: RELATIONSHIP CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNAValidatedRelationshipCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.009: Pedigree Information (PED)
Description:
This optional field contains information and structure associated with the pedigree.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNAPedigree
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
881
Type-18: DNA Data
18.009_1: Pedigree Information - Pedigree ID (PID)
Description:
The first information item is the pedigree ID / PID. It is a character string of up to 24 Unicode characters. It is mandatory if this
field is used and it indicates the identity of the pedigree determined and held at the laboratory that originates the pedigree.
Field Minimum
1
Field Maximum
24
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAPedigree
NIEM Element: biom:DNAPedigreeID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.009_2: Pedigree Information - Pedigree Member ID (PMI)
Description:
The second information item is the pedigree member ID / PMI. It is a unique reference within the pedigree. It is mandatory if
this field is used. This information item refers to the subject of the transaction. It is a character string of up to 6 Unicode
characters. This information item shall also provide the ability to link pedigree information.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAPedigree
NIEM Element: biom:DNAPedigreeMemberIndexNumeric
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
882
Type-18: DNA Data
18.009_3: Pedigree Information - Pedigree Member Status (PMS)
Description:
The third information item is the pedigree member status / PMS. It is mandatory if 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 = Known or U =
Unknown.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
PMS = K or U
Code List: PEDIGREE MEMBER STATUS CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAPedigree
NIEM Element: biom:DNAPedigreeMemberStatusCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.009_4: Pedigree Information - Sample Identifier (SID)
Description:
The fourth information item is the DNA sample identifier / SID for the transaction. It is not an identifier within the pedigree
chain, unlike the following two identifiers or the PID. It is a character string of 24 characters or less. This information item
relates the sample in this record to the pedigree.
Field Minimum
1
Field Maximum
24
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAPedigree
NIEM Element: biom:DNAPedigreeSampleID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
883
Type-18: DNA Data
18.009_5: Pedigree Information - Father Identifier (FID)
Description:
The fifth information item is the father identifier / FID. It is optional and is a numeric value of 3 digits or less that is unique within
the pedigree. This information item is the father identified as related to the sample indicated in the PMI item.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAPedigree
NIEM Element: biom:DNAPedigreeFatherIndexNumeric
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.009_6: Pedigree Information - Mother Identifier (MID)
Description:
The sixth information item is the mother identifier / MID. It is optional and is a numeric value of 3 digits or less that is unique
within the pedigree. This information item is the mother identified as related to the sample indicated in the PMI item.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAPedigree
NIEM Element: biom:DNAPedigreeMotherIndexNumeric
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
884
Type-18: DNA Data
18.009_7: Pedigree Information - Pedigree Comment (PCM)
Description:
The seventh optional information item is the pedigree comment / PCM. It is up to 2000 Unicode characters.
Field Minimum
1
Field Maximum
2000
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAPedigree
NIEM Element: biom:DNAPedigreeCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.01: Sample Type (STY)
Description:
This mandatory field contains two information items. The first represents the origination cell type from where the sample was
collected (sample cellular type / SCT). The second information item is the sample origin / SMO.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNASampleOrigin
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
885
Type-18: DNA Data
18.010_1: Sample Type - Sample Cellular Type (SCT)
Description:
This information item represents the origination cell type from where the sample was collected (sample cellular type / SCT). It
is mandatory and shall contain a numeric value selected from the 'Cellular code' column of Table 115 of ANSI/NIST-ITL
Update: 2015.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤STY ≤11; positive integer
Code List: DNA SAMPLE CELLULAR CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNASampleOrigin
NIEM Element: biom:DNACellularCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.010_2: Sample Type - Sample Origin (SMO)
Description:
The second information item is the sample origin / SMO. It is an optional item of a string of 2 characters describing where the
sample was obtained. It contains one of the following values: NS = Not Specified, WB = Whole Body or BP = Body Part.
Field Minimum
2
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
SMO = NS, WB or BP
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNASampleOrigin
NIEM Element: biom:DNASampleOriginCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
886
Type-18: DNA Data
18.011: Sample Typing Information (STI)
Description:
This mandatory field represents the technology utilized to type the DNA sample. A repeating subfield with the following
information item shall comprise this field.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
n/a
Code List: DNA SAMPLE TYPING AVAILABILITY CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNATypingTechnologyCategoryCode
XML Min/Max: 1 / 5
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.011_0: Sample Typing Information - Subfields: Repeating sets of information items (STI_0)
Description:
Each subfield shall contain a number from the following list: 0 = Nuclear (indicates presence of Field 18.016: Autosomal STR,
X-STR and Y-STR / STR), 1 = mtDNA (indicates presence of Field 18.017: Mitochondrial DNA data / DMD), 2 =
electropherogram data (indicates presence of Field 18.019: Electropherogram description / EPD), 3 = electropherogram ladder
(indicates presence of Field 18.023: Electropherogram ladder / EPL) or 4 = user-defined profile data (indicates the presence of
Field 18.018: DNA user-defined profile data / UDP).
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
5
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤STI ≤4; non-negative
integer
Code List: DNA SAMPLE TYPING AVAILABILITY CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
887
Type-18: DNA Data
18.012: Sample Collection Method (SCM)
Description:
This field contains a description of the method used to collect the DNA sample. It is a character string up to 255 characters.
Field Minimum
1
Field Maximum
255
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNASampleCollectionMethodText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.013: Sample Collection Date (SCD)
Description:
This mandatory field contains the date and time that the sample was collected.
Field Minimum
15
Field Maximum
15
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
YYYYMMDDhhmmssZ
Constraints
Description points to 7.7.2.2
YYYYMMDDhhmmssZ,
where the Z is indicates the
zone description of 0 hours
format. Consider naming as
"Sample Collection
DateTime"
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture
NIEM Element: biom:CaptureDate/nc:Date
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
888
Type-18: DNA Data
18.014: Profile Storage Date (PSD)
Description:
This mandatory field contains date and time the sample was collected.
Field Minimum
15
Field Maximum
15
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
YYYYMMDDhhmmssZ
Constraints
Description points to 7.7.2.2
YYYYMMDDhhmmssZ,
where the Z is indicates the
zone description of 0 hours
format. Consider naming as
"PROFILE STORAGE
DATETIME".
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNAProfileStorageDate/nc:Date
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.015: DNA Profile Data (DPD)
Description:
This is a mandatory field. It contains information and structure associated with the DNA profile data.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNAProfile
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
889
Type-18: DNA Data
18.015_1: DNA Profile Data - Profile Type (PTP)
Description:
The first information item is mandatory. It is the profile type / PTP. It is a numerical value. Allowable values are 0 = Person or 1
= Stain.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
PTP = 0 or 1
Code List: DNA PROFILE TYPE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAProfile
NIEM Element: biom:DNAProfileCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.015_2: DNA Profile Data - Result (RES)
Description:
The second information item is optional and is the result / RES. It is entered with a numeric value selected from Table 116
DNA Result Codes from ANSI/NIST-ITL Update: 2015.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤RES ≤10 integer
Code List: DNA PROFILE RESULT CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAProfile
NIEM Element: biom:DNAProfileResultCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
890
Type-18: DNA Data
18.015_3: DNA Profile Data - Profile ID (PRF)
Description:
The third information item is mandatory and is the profile ID / PRF. It is a character string with a unique party identification. This
information item is used to uniquely identify the profile or sample for which the transaction is based. It is a maximum of 64
alphanumeric characters.
Field Minimum
1
Field Maximum
64
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAProfile
NIEM Element: biom:DNAProfileID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.015_4: DNA Profile Data - Supplemental Message (SUP)
Description:
The optional fourth information item is a supplemental message / SUP. This information item states if this transaction is a
supplemental message to a previous transmission. It is an alphanumeric string containing up to 100 characters.
Field Minimum
1
Field Maximum
100
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAProfile
NIEM Element: biom:DNAProfileSupplementalText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
891
Type-18: DNA Data
18.015_5: DNA Profile Data - DNA Profile Comment (DPC)
Description:
The optional fifth information item is a DNA profile comment / DPC. It is up to 100 Unicode characters.
Field Minimum
1
Field Maximum
100
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAProfile
NIEM Element: biom:DNAProfileCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.016: Autosomal STR, X-STR and Y-STR Profile (STR)
Description:
This optional field may be comprised of as many subfields as there are combinations of data type and locus type reported. This
field is only present if Field 18.011: Sample typing Information / STI has a subfield with the value 0.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNASTRProfile
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
892
Type-18: DNA Data
18.016_0: Autosomal STR, X-STR and Y-STR Profile (STR_0)
Description:
This field may be comprised of as many subfields as there are combinations of data type and locus type reported. This field is
only present if Field 18.011: Sample typing Information / STI has a subfield with the value 0.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
Unlimited
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.016_1: Autosomal STR, X-STR and Y-STR Profile - DNA STR Type (DST)
Description:
The first information item is mandatory. It is the DNA STR type / DST. It has one of the following numeric values: 0 =
Autosomal STR Profile, 1 = X-STR Profile or 2 = Y-STR Profile.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
DST = 0, 1 or 2
Code List: DNA STR TYPE CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNASTRProfile
NIEM Element: biom:DNASTRProfileCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
893
Type-18: DNA Data
18.016_2: Autosomal STR, X-STR and Y-STR Profile - DNA Locus Reference (DLR)
Description:
The second information item is mandatory. It is the DNA locus reference / DLR. The current valid loci for Autosomal, Y and XSTRs are maintained by NIST and are available at http://www.nist.gov/itl/iad/ig/ansi_standard.cfm. This information item is an
integer entry with up to 3 characters per locus.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤DLR ≤200; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNASTRProfile
NIEM Element: biom:DNALocusReferenceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.016_3: Autosomal STR, X-STR and Y-STR Profile - Allele Indicator (ALL)
Description:
The third information item, allele indicator / ALL, is mandatory. It is a numeric entry containing a zero if no allele is found.
Otherwise it is filled with a 1.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
ALL = 0 or 1
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNASTRProfile
NIEM Element: biom:DNAAlleleIndicator
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
894
Type-18: DNA Data
18.016_4: Autosomal STR, X-STR and Y-STR Profile - Locus Analysis Indicator (LAI)
Description:
The fourth information item is mandatory. It is the locus analysis indicator / LAI. It is a numeric entry, containing a zero if not
analyzed. Otherwise it contains a 1.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
LAI = 0 or 1
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNASTRProfile
NIEM Element: biom:DNALocusAnalysisIndicator
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.016_5: Autosomal STR, X-STR and Y-STR Profile - Precise Call Determination (PCDT)
Description:
The fifth information item is mandatory. It is the precise call determination / PCDT. It is a numeric entry containing a zero if the
precise call cannot be determined, due to an uncertainty in the call. Otherwise it contains a 1.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
PCDT = 0 or 1
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNASTRProfile
NIEM Element: biom:DNAPreciseCallIndicator
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
895
Type-18: DNA Data
18.016_6: Autosomal STR, X-STR and Y-STR Profile - Allele Call 1 (AL1)
Description:
The sixth information item shall have a value if ALL is 1. It shall be empty if ALL is 0. It is the allele call 1 / AL1. This is the
allele call for the locus reference as indicated by the value of DLR. It contains up to 4 characters, such as “11” or “23.3”.
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Period
Format
n/a
Constraints
integer > 0; or real number
with one digit to right of
decimal
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNASTRProfile
NIEM Element: biom:DNAAlleleCall1Text
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.016_7: Autosomal STR, X-STR and Y-STR Profile - Allele Call 2 (AL2)
Description:
The seventh information item is conditional upon the value of ALL being 1. It is the allele call 2 / AL2. This is the allele call for
the locus reference as indicated by the value of DLR. It contains up to 4 characters, such as “11” or “23.3”. It may only appear
if AL1 is used; since there are cases with only one allele in a call, it is possible that AL1 will have a value in this field and AL2
will not have a value. It shall be empty if AL1 is empty.
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Period
Format
n/a
Constraints
integer > 0; or real number
with one digit to right of
decimal
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNASTRProfile
NIEM Element: biom:DNAAlleleCall2Text
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
896
Type-18: DNA Data
18.016_8: Autosomal STR, X-STR and Y-STR Profile - Allele Call 3 (AL3)
Description:
The eighth information item is optional but shall not appear unless ALL=1. It is the allele call 3 / AL3. This is the allele call for
the locus reference DLR. It contains up to 4 characters, such as “11” or “23.3”. This is not used for mixtures, but is for the rare
case of a tri-allele. The information item allele call 3 / AL3 shall only appear if information items AL1 and AL2 are present.
Field Minimum
1
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Period
Format
n/a
Constraints
integer > 0; or real number
with one digit to right of
decimal
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNASTRProfile
NIEM Element: biom:DNAAlleleCall3Text
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.016_9: Autosomal STR, X-STR and Y-STR Profile - Batch ID (BID)
Description:
The ninth information item is the batch ID / BID. This optional information item shall contain an identifier for the batch to which
a locus belongs. This may be referred to as the gel or plate identifier. A specimen may have loci from multiple batches. The
BID shall be up to 32 Unicode characters.
Field Minimum
1
Field Maximum
32
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNASTRProfile
NIEM Element: biom:DNABatchID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
897
Type-18: DNA Data
18.016_10: Autosomal STR, X-STR and Y-STR Profile - Electropherogram Cross Reference (ECR)
Description:
The tenth information item is optional. It is called the electropherogram cross reference / ECR and has the same value as the
electropherogram image reference / EIR from the appropriate subfield of Field 18.019: Electropherogram description / EPD
that is associated with the information in this field and particular subfield instance (if there is such an electropherogram present
in this instance of the record).
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNASTRProfile
NIEM Element: biom:DNAElectropherogramID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.016_11: Autosomal STR, X-STR and Y-STR Profile - Ladder Cross Reference (LCR)
Description:
The eleventh information item is optional. It is called the ladder cross reference / LCR and has the same value as the ladder
image reference / LIR from the appropriate subfield of Field 18.023: Electropherogram ladder / EPL that is associated with the
in and particular subfield instance (if there is such a ladder present in this instance of the record).
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNASTRProfile
NIEM Element: biom:DNAElectropherogramLadderID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
898
Type-18: DNA Data
18.016_12: Autosomal STR, X-STR and Y-STR Profile - Kit ID (KID)
Description:
The twelfth information item is the kit ID / KID. This mandatory information item contains a number that references the kit used
to process the DNA described in this record. The numeric values for specific kits are contained in the table of kits maintained
by NIST at: http://www.nist.gov/itl/iad/ig/ansi_standard.cfm. The values to be entered are those in the “Reference Number”
column. The KID value shall be represented as 0 for a non-listed kit. If a non-listed kit is used (KID = 0), then the following
three information items are mandatory.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤KID ≤999; integer
Code List: DNA KIT ID CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNASTRProfile/biom:DNAKit
NIEM Element: biom:DNAKitReferenceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.016_13: Autosomal STR, X-STR and Y-STR Profile - Kit Name (KNM)
Description:
The thirteenth information item is the kit name / KNM. This is an alphanumeric value of up to 32 Unicode characters. KNM shall
be entered if KID = 0.
Field Minimum
1
Field Maximum
32
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNASTRProfile/biom:DNAKit
NIEM Element: biom:DNAKitName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
899
Type-18: DNA Data
18.016_14: Autosomal STR, X-STR and Y-STR Profile - Manufacturer (KMF)
Description:
The fourteenth information item is the manufacturer / KMF. It is an alphanumeric value of up to 32 Unicode characters. KMF
shall be entered if KID = 0.
Field Minimum
1
Field Maximum
32
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNASTRProfile/biom:DNAKit
NIEM Element: biom:DNAKitManufacturerName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.016_15: Autosomal STR, X-STR and Y-STR Profile - Description of the Kit (with part or catalog number)
(KDS)
Description:
The fifteenth information item is the description of the kit (with part or catalog number) / KDS. This is up to 128 Unicode
characters. KDS shall be entered if KID = 0.
Field Minimum
1
Field Maximum
128
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNASTRProfile/biom:DNAKit
NIEM Element: biom:DNAKitDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
900
Type-18: DNA Data
18.017: Mitochondrial DNA Data (DMD)
Description:
To accommodate the differences in how mtDNA types are derived (differences from reference), the interpretation issue is
avoided in this standard by dividing the control region into 2 regions (even though HV3 exists) to ensure any insertions
/deletions/C-stretches are included. This method enables any receiver of the data to use it in a way to which they are
accustomed (either using the full sequence or interpreting the full sequence according to their own methodology). The resultant
data use would then be fully consistent with the receiver’s database and enable processing. This is an optional field, but if it is
entered, all information items are mandatory. This field is only present if Field 18.011: Sample typing information / STI has a
subfield with the value 1.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNAMitochondrialData
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.017_1: Mitochondrial DNA Data - Mito Control Region 1 (MT1)
Description:
This information item is the mito control region 1 / MT1. It is defined as inclusive of HV1, starting at 16024 and ending at
16569. The string may have up to 400 insertions. This string length allows for insertions in HV1. Each character is an IUPAC
value from Table 117 from ANSI/NIST-ITL Update: 2015 or a sequence value: A, G, C or T.
Field Minimum
1
Field Maximum
946
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AS
Special Characters
Comma
Format
n/a
Constraints
character string from Table
117 IUPAC DNA codes
from ANSI/NIST-ITL
Update: 2015 or a
sequence value: A, G, C or
T
Code List: IUPAC DNA CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAMitochondrialData
NIEM Element: biom:DNAMitoControlRegion1Text
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
901
Type-18: DNA Data
18.017_2: Mitochondrial DNA Data - Mito Control Region 2 (MT2)
Description:
The second information item is the mito control region 2 / MT2 is defined as inclusive of HV2 and HV3, starting at 1 and ending
at 576. Up to 400 insertions may be specified . Each character is an IUPAC value from ANSI/NIST-ITL Update: 2015 or a
sequence value: A, G, C or T.
Field Minimum
1
Field Maximum
977
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AS
Special Characters
Comma
Format
n/a
Constraints
character string from Table
117 IUPAC DNA codes
from ANSI/NIST-ITL
Update: 2015 or a
sequence value: A, G, C or
T
Code List: IUPAC DNA CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAMitochondrialData
NIEM Element: biom:DNAMitoControlRegion2Text
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.017_3: Mitochondrial DNA Data - Base Composition Starting Point (BSP)
Description:
The third information item is the base composition starting point / BSP. This entry is numeric, up to 5 digits. Starting point is the
base position (rCRS) where the primer pair starts interrogating the mitochondrial DNA.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAMitochondrialData
NIEM Element: biom:DNAMitoBaseStartNumeric
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
902
Type-18: DNA Data
18.017_4: Mitochondrial DNA Data - Base Composition Ending Point (BEP)
Description:
The fourth information item is the base composition ending point / BEP. This entry is numeric, up to 5 digits. Ending point is the
base position (rCRS) where the primer pair stops interrogating the mitochondrial DNA.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer; BEP > BSP
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAMitochondrialData
NIEM Element: biom:DNAMitoBaseEndNumeric
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.017_5: Mitochondrial DNA Data - Base Composition A Length (BCA)
Description:
The fifth information item is the base composition A length / BCA. It is a numerical value of up to two digits. A represents the
number of adenines in the region being amplified.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAMitochondrialData
NIEM Element: biom:DNAMitoBaseAdenineQuantity
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
903
Type-18: DNA Data
18.017_6: Mitochondrial DNA Data - Base Composition G Length (BCG)
Description:
The sixth information item is the base composition G length / BCG. It is a numerical value of up to two digits. G represents the
number of guanines in the region being amplified
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAMitochondrialData
NIEM Element: biom:DNAMitoBaseGuanineQuantity
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.017_7: Mitochondrial DNA Data - Base Composition C Length (BCC)
Description:
The seventh information item is the base composition C length / BCC. It is a numerical value of up to two digits. C represents
the number of cytosines in the region being amplified.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAMitochondrialData
NIEM Element: biom:DNAMitoBaseCytosineQuantity
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
904
Type-18: DNA Data
18.017_8: Mitochondrial DNA Data - Base Composition T Length (BCT)
Description:
The eighth information item is the base composition T length / BCT. It is a numerical value of up to two digits. T represents the
number of thymines in the region being amplified.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAMitochondrialData
NIEM Element: biom:DNAMitoBaseThymineQuantity
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.018: DNA User-Defined Profile (UDP)
Description:
This optional field is user-defined, when data other than Autosomal STR, X-STR, Y-STR, mtDNA or an electropherogram is
included as part of the transaction. The sender shall provide the receiver with a description of the field contents. This field is
only present if Field 18.011: Sample typing Information / STI has a subfield with the value 4.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNAUserDefinedProfileAbstract
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
905
Type-18: DNA Data
18.018_0: DNA User-Defined Profile - Subfields: Repeating sets of information items (UDP_0)
Description:
This field is user-defined, when data other than Autosomal STR, X-STR, Y-STR, mtDNA or an electropherogram is included as
part of the transaction. The sender shall provide the receiver with a description of the field contents. This field is only present if
Field 18.011: Sample typing Information / STI has a subfield with the value 4.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
Unlimited
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.019: Electropherogram Description (EPD)
Description:
This optional field contains a subfield for each electropherogram. This field is only present if Field 18.011: Sample typing
Information / STI has a subfield with value 2.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNAElectropherogram
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
906
Type-18: DNA Data
18.019_0: Electropherogram Description - Subfields: Repeating sets of information items (EPD_0)
Description:
This field contains a subfield for each electropherogram. This field is only present if Field 18.011: Sample typing Information /
STI has a subfield with value 2.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
Unlimited
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.019_1: Electropherogram Description - Electropherogram Image Reference (EIR)
Description:
The first information item is the electropherogram image reference / EIR. It shall contain an alphanumeric reference up to 8
characters, which is unique for each image. If none has been assigned, enter 999. This is a unique identifier.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
If none assigned enter 999
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAElectropherogram
NIEM Element: biom:DNAElectropherogramID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
907
Type-18: DNA Data
18.019_2: Electropherogram Description - Electropherogram Storage Type (EST)
Description:
The second information item is the electropherogram storage type / EST. This is a character string of up to 4 characters,
representing the file type suffix for the electropherogram. The data is stored in “fsa”, “hid” or “----”. The dashes may be
substituted with character strings for other format types as they become available.
Field Minimum
1
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
“fsa”, “hid” or “----”, dashes
may be substituted with
character strings for other
format types as they
become available.
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAElectropherogram
NIEM Element: biom:DNAElectropherogramFileStorageText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.019_3: Electropherogram Description - Image Data Descriptor (IDD)
Description:
The third information item is the image data descriptor / IDD of the electropherogram contained in this subfield. If the data is
stored externally, enter the filename. This is a Unicode string of up to 200 characters.
Field Minimum
1
Field Maximum
200
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAElectropherogram
NIEM Element: biom:DNAElectropherogramDataDescriptionText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
908
Type-18: DNA Data
18.019_4: Electropherogram Description - Electropherogram Data (ELPD)
Description:
The fourth information item is the electropherogram data/ ELPD. This shall be stored in base-64 format.
Field Minimum
2
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
Base64
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAElectropherogram
NIEM Element: biom:DNAElectropherogramBinaryObject
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.019_5: Electropherogram Description - Electropherogram Screenshot (EPS)
Description:
The fifth information item is optional. It is the electropherogram screenshot / EPS. This may be an image captured during the
analysis. This shall be stored in base-64 format.
Field Minimum
2
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Base64
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAElectropherogram
NIEM Element: biom:DNAElectropherogramScreenshotImage/nc:Base64BinaryObject
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
909
Type-18: DNA Data
18.020: DNA Genotype Distribution (DGD)
Description:
This field contains informative genotype representation type of DNA information. It is an optional field. The entry is numeric: 0 =
Likelihood 1 = Probability.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
DGD = 0 or 1
Code List: DNA GENOTYPE DISTROBUTION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNAGenotypeDistributionCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.021: DNA Genotype Allele Pair (GAP)
Description:
This field is only present if Field 18.020: DNA Genotype Distribution / DGD has a value. It is used for low-template, mixture or
stain scenarios only. It is comprised of a repeating subfield that occurs once for each allele pair. Allele calls are captured in
Field 18.016: Autosomal STR, X-STR and Y-STR profile / STR.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNAGenotypeAllelePair
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
910
Type-18: DNA Data
18.021_0: DNA Genotype Allele Pair - Subfields: Repeating sets of information items (GAP_0)
Description:
This field is only present if Field 18.020: DNA Genotype Distribution / DGD has a value. It is used for low-template, mixture or
stain scenarios only. It is comprised of a repeating subfield that occurs once for each allele pair. Allele calls are captured in
Field 18.016: Autosomal STR, X-STR and Y-STR profile / STR.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
Unlimited
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.021_1: DNA Genotype Allele Pair - Genotype Locus Reference (GLR)
Description:
The first information item is the genotype locus reference / GLR. The current valid loci for Autosomal, Y and X-STRs are
maintained by NIST and are available at http://www.nist.gov/itl/iad/ig/ansi_standard.cfm . The GLR is a numeric entry with up to
3 characters per locus. The maximum value of 200 listed in Table 112 from ANSI/NIST-ITL Update: 2015 is to allow for
potential additions to the loci reference table.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤GLR ≤200; positive
integer
Code List: DNA LOCI CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAGenotypeAllelePair
NIEM Element: biom:DNALocusReferenceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
911
Type-18: DNA Data
18.021_2: DNA Genotype Allele Pair - Allele Pair (ALP)
Description:
The second information item is the allele pair / ALP. This is a numeric information item containing the allele pair data of up to 9
numeric characters separated by a comma between values. An example is “14,23.3” or “22.1,23.3”
Field Minimum
3
Field Maximum
9
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
NS
Special Characters
Comma, period
Format
n/a
Constraints
digits, one comma, and upt
to 2 periods allowed
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAGenotypeAllelePair
NIEM Element: biom:DNAGenotypeAllelePairText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.021_3: DNA Genotype Allele Pair - Genotype Numerical Weight (GNW)
Description:
The third information item is the genotype numerical weight / GNW. It is a non-negative real number up to 5 characters
(including a period) ranging from 0 to 1. An example is “0.114”.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
NS
Special Characters
Period
Format
n/a
Constraints
0 ≤GNW ≤1; non-negative
real number up to 5
characters, which may have
a period
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAGenotypeAllelePair
NIEM Element: biom:DNALocusGenotypeProbabilityValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
912
Type-18: DNA Data
18.022: Comment (COM)
Description:
This information item allows a free text comment or description to be provided by the examiner about the referenced field and
subfield in this instance of a Type-18 record.
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNACommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.023: Electropherogram Ladder (EPL)
Description:
This optional field contains a repeating subfield for a ladder / control sample. This field is only present if Field 18.011: Sample
typing Information / STI has a subfield with the value 3.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample
NIEM Element: biom:DNAElectropherogramLadder
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
913
Type-18: DNA Data
18.023_0: Electropherogram Ladder - Subfields: Repeating sets of information items (EPL_0)
Description:
This field contains a repeating subfield for a ladder / control sample. This field is only present if Field 18.011: Sample typing
Information / STI has a subfield with the value 3.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
Unlimited
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.023_1: Electropherogram Ladder - Ladder Image Reference (LIR)
Description:
The first information item is the ladder image reference / LIR. It shall contain an alphanumeric reference up to 8 characters,
which is unique for each image. If none has been assigned, enter 999. This is a unique identifier.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAElectropherogramLadder
NIEM Element: biom:DNAElectropherogramID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
914
Type-18: DNA Data
18.023_2: Electropherogram Ladder - Ladder Storage Type (LST)
Description:
The second information item is the ladder storage type / LST. This is a string of up to 4 characters, representing the file type
suffix for the electropherogram. The data is stored in “fsa”, “hid” or “----“ The dashes may be substituted with character strings
for other format types as they become available.
Field Minimum
1
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAElectropherogramLadder
NIEM Element: biom:DNAElectropherogramFileStorageText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.023_3: Electropherogram Ladder - Ladder Image Data Descriptor (LDD)
Description:
The third information item is the ladder image data descriptor / LDD of the electropherogram contained in this subfield. If the
data is stored externally, enter the filename. This is an alphanumeric string with special characters allowed. An example is
“NIST Run 5 Well A07 12 Jan 11”
Field Minimum
1
Field Maximum
200
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAElectropherogramLadder
NIEM Element: biom:DNAElectropherogramDataDescriptionText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
915
Type-18: DNA Data
18.023_4: Electropherogram Ladder - Ladder Electropherogram Data (LEPD)
Description:
The fourth information item is the ladder electropherogram data/ LEPD. This shall be stored in base-64 format.
Field Minimum
2
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
Base64
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAElectropherogramLadder
NIEM Element: biom:DNAElectropherogramBinaryObject
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.023_5: Electropherogram Ladder - Ladder Electropherogram Screenshot (LES)
Description:
The fifth information item is optional. It is the ladder electropherogram screenshot / LES. This may be an image captured
during the analysis. This shall be stored in base-64 format.
Field Minimum
2
Field Maximum
Unlimited
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Base64
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:DNAElectropherogramLadder
NIEM Element: biom:DNAElectropherogramScreenshotImage/nc:Base64BinaryObject
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
916
Type-18: DNA Data
18.902: Annotation Information (ANN)
Description:
This is an optional field, listing the operations performed on the original source in order to prepare it for inclusion in a biometric
record type.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord
NIEM Element: biom:ProcessAnnotation
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
18.902_0: Annotation Information - Subfields: Repeating sets of information items (ANN_0)
Description:
This optional field is used to store annotation, logging, or processing information associated with one or more processing
algorithms, processes, or latent workstations (other than the FBI-developed ULW). If present, this text shall consist of one or
more subfields comprised of a set of information items. Four mandatory items comprise a subfield.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
Unlimited
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
917
Type-18: DNA Data
18.902_1: Annotation Information - Greenwich Mean Time (GMT)
Description:
This information item is the Greenwich Mean Time (GMT) when the processing occured. The data is formatted as
YYYYMMDDhhmmssZ, where the Z is indicates the zone description of 0 hours. Time (GMT) units. This time is independent of
the actual time zone where the time and date is recorded.
Field Minimum
15
Field Maximum
15
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
YYYYMMDDHHMMSSZ for Traditional Encoding
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessUTCDate/nc:DateTime
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
18.902_2: Annotation Information - Processing Algorithm Name / Version (NAV)
Description:
This information item shall contain text identifying the name and version of the processing algorithm, application, procedure, or
workstation.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessName
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
918
Type-18: DNA Data
18.902_3: Annotation Information - Algorithm Owner (OWN)
Description:
This information item shall contain an unformatted text string of up to 64 characters with the contact information for the
organization that owns the processing algorithm or latent workstation. Where there is no 'algorithm owner,' enter N/A.
Field Minimum
1
Field Maximum
64
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessOwnerText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
18.902_4: Annotation Information - Process Description (PRO)
Description:
This information item field shall contain text describing a process or procedure applied to the sample in this Type-9 record.
Field Minimum
1
Field Maximum
Unlimited
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessDescriptionText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
919
Type-18: DNA Data
18.992: Type-2 Record Cross Reference (T2C)
Description:
This is an optional field. When used, it contains the IDC value of the Type-2 record that contains relevant biographic
information and other data concerning the subject of this instance of the record, who may be different from the subject of the
transaction.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤T2C≤99; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord
NIEM Element: biom:Type2CrossReferenceID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
18.993: Source Agency Name (SAN)
Description:
This is an optional field. It may contain up to 125 Unicode characters. It is the name of the agency referenced in Field 18.004:
Source agency / SRC.
Field Minimum
1
Field Maximum
125
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture/biom:CaptureOrganization
NIEM Element: nc:OrganizationName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
920
Type-18: DNA Data
18.995: Associated Context (ASC)
Description:
This is a mandatory field comprised of two information items. The first information item is mandatory. It is file type / FTY. If the
associated context file is a digital file, this shall contain the suffix indicating the file type. If it is an analog file, enter ‘ANALOG’.
For digital data stored in other formats (such as digital tape) that do not have computer file names and suffixes, enter ‘OTHER’.
The second information item is decoding instructions / DEI. It is optional and contains free text up to 1000 characters.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord
NIEM Element: biom:AssociatedContext
XML Min/Max: 0 / 255
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.995_0: Associated Context - Subfields: Repeating sets of information items (ASC_0)
Description:
This optional field refers to one or more Type 21 Records with the same ACN. Type 21 Records contain images that are NOT
used to derive the biometric data in Field 13.999: Latent friction ridge image (DATA) but that may be relevant to the collection
of that data, such as general scenes of the area where a latent print was found.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
255
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: N/A
NIEM Element: N/A
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
921
Type-18: DNA Data
18.995_1: Associated Context - Associated Context Number (ACN)
Description:
The first information item contains the associated context number / ACN for the Associated Context field for a particular Record
Type-21. This is mandatory for each Field xx.995, when the field is used. It contains an index to a particular instance of a Type21 record in the transaction. This same index value appears in the appropriate instance of Record Type-21 as Field 21.021:
Associated context number (ACN). The value of the CAN shall be a sequentially assigned a positive integer starting from one
and incremented by one, not to exceed 255.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ACN ≤255; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:AssociatedContext
NIEM Element: biom:ContextID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.995_2: Associated Context - Associated Segment Position (ASP)
Description:
The second information item in Field xx.995 is optional. It is the associated segment position / ASP. It contains the index to a
particular set of segmentation coordinates of the associated context data. This same segmentation index value appears in
Record Type-21 as the associated segment position / ASP in Field 21.016: Segments / SEG. There may be up to 99 segments
listed in Field 21.016, but only the relevant segment is contained in Field xx.995.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
1 ≤ASP ≤99; positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:AssociatedContext
NIEM Element: biom:ImageSegmentID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
922
Type-18: DNA Data
18.998: Geographic Sample Acquisition Location (GEO)
Description:
This optional field contains the location where the DNA was acquired – not where it is stored.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture
NIEM Element: biom:GeographicSampleAcquisitionLocation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.998_01: Geographic Sample Acquisition Location - Universal Time Entry (UTE)
Description:
The coordinated universal time (UTC) where the biometric sample was collected. This time is independent of the actual time
zone where the time and date is recorded. The date is YYYYMMDDhhmmssZ, where the Z is indicates the zone description of
0 hours. If sample collection time is unknown, set it to "00000000000000Z."
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
YYYYMMDDHHMMSSZ for Traditional Encoding
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture/biom:GeographicSampleAcquisitionLocation
NIEM Element: biom:CaptureUTCDateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
923
Type-18: DNA Data
18.998_02: Geographic Sample Acquisition Location - Latitude Degree Value (LTD)
Description:
The second information item is latitude degree value (LTD). This is a value that specifies the degree of latitude. The value shall
be between -90 (inclusive) and +90 (inclusive). The degrees may be expressed as an integer (without a decimal) or a real
number including decimals. If decimals are present, then minutes and seconds shall be empty. Examples: Buenos Aires,
Argentina: -34 (with minutes LTM = 36) NIST, Gaithersburg, Maryland: 39.137627 (no LTM or LTS)
Field Minimum
1
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal,Minus Sign,Plus
Sign
Format
n/a
Constraints
-90 ≤LTD ≤90
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture/biom:GeographicSampleAcquisitionLocation/nc:Location3DG
eospatialCoordinate/nc:GeographicCoordinateLatitude
NIEM Element: nc:LatitudeDegreeValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.998_03: Geographic Sample Acquisition Location - Latitude Minute Value (LTM)
Description:
This information item is latitude minute value (LTM). This is a value that specifies a minute of a degree. The value shall be
between 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall be empty. Thus, the allowed special character is a
period. The minute value can be empty, even if the degree value is an integer. LTM and LGM are co-conditional, so they shall
both be present if either is present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤LTM < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture/biom:GeographicSampleAcquisitionLocation/nc:Location3DG
eospatialCoordinate/nc:GeographicCoordinateLatitude
NIEM Element: nc:LatitudeMinuteValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
924
Type-18: DNA Data
18.998_04: Geographic Sample Acquisition Location - Latitude Second Value (LTS)
Description:
The fourth information item is the latitude second value (LTS). This is a value that specifies a second of a minute. The integer
shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤LTS < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture/biom:GeographicSampleAcquisitionLocation/nc:Location3DG
eospatialCoordinate/nc:GeographicCoordinateLatitude
NIEM Element: nc:LatitudeSecondValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.998_05: Geographic Sample Acquisition Location - Longitude Degree Value (LGD)
Description:
The fifth information item is the longitude degree value (LGD). It is a value that specifies the degree of a longitude. The value
shall be between -180 (inclusive) and +180 (inclusive). If LTD is present, then LGD shall be present. The degrees may be
expressed as whole numbers (without a decimal) or real numbers including decimals. If decimals are present, then minutes
and seconds are empty. Examples: Buenos Aires, Argentina: -58 (with minutes LGM = 22), NIST, Gaithersburg, Maryland: 77.216032 (no LGM or LGS)
Field Minimum
1
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal,Minus Sign,Plus
Sign
Format
n/a
Constraints
-180 ≤LGD ≤180
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture/biom:GeographicSampleAcquisitionLocation/nc:Location3DG
eospatialCoordinate/nc:GeographicCoordinateLongitude
NIEM Element: nc:LongitudeDegreeValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
925
Type-18: DNA Data
18.998_06: Geographic Sample Acquisition Location - Longitude Minute Value (LGM)
Description:
The sixth information item is the longitude minute value (LGM). It is a value that specifies a minute of a degree. The value shall
be from 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall not appear. The minute value is empty, even if the
degree value is an integer. If LTM is present, then LGM shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤LGM < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture/biom:GeographicSampleAcquisitionLocation/nc:Location3DG
eospatialCoordinate/nc:GeographicCoordinateLongitude
NIEM Element: nc:LongitudeMinuteValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.998_07: Geographic Sample Acquisition Location - Longitude Second Value (LGS)
Description:
The seventh information item is the longitude second value (LGS). This is a value that specifies a second of a minute. The
integer shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer. If LTS is
present, then LGS shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤LGS < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture/biom:GeographicSampleAcquisitionLocation/nc:Location3DG
eospatialCoordinate/nc:GeographicCoordinateLongitude
NIEM Element: nc:LongitudeSecondValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
926
Type-18: DNA Data
18.998_08: Geographic Sample Acquisition Location - Elevation (ELE)
Description:
The eighth information item is elevation (ELE). It is expressed in meters. It is a numeric value. It is between -422 meters (Dead
Sea) and 8848 meters (Mount Everest). Allowed special characters are the negative sign and the period.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Minus Sign,Period
Format
n/a
Constraints
-422.000 < ELE < 8848.000;
real number
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture/biom:GeographicSampleAcquisitionLocation/nc:Location3DG
eospatialCoordinate
NIEM Element: nc:LocationElevation/nc:MeasureDecimalValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
927
Type-18: DNA Data
18.998_09: Geographic Sample Acquisition Location - Geodetic Datum Code (GDC)
Description:
The ninth information item is the geodetic datum code (GDC11). It is an alphanumeric value of 3 to 6 characters in length. This
information item is used to indicate which coordinate system was used to represent the values in information items 2 through
7. If no entry is made in this information item, then the basis for the values entered in the first eight information items shall be
WGS84, the code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values. If no entry is
made in this information item, then the basis for the values entered in the first eight information items shall be WGS84, the
code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values.
Field Minimum
3
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
value from Geographic
coordinate datum code
values in ANSI/NIST-ITL
Update: 2015
Code List: GEOGRAPHIC COORDINATE DATUM CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture/biom:GeographicSampleAcquisitionLocation/nc:Location3DG
eospatialCoordinate
NIEM Element: biom:GeodeticDatumCoordinateSystemCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.998_10: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Zone (GCM)
Description:
It is an alphanumeric value of 2 to 3 characters. This is a one or two digit UTM zone number followed by the 8 degree
latitudinal band designator (which is a single letter).
Field Minimum
2
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
One or two digits followed
by a single letter
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture/biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationUTMCoordinateValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
928
Type-18: DNA Data
18.998_11: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Easting (GCE)
Description:
The eleventh information item is the geographic coordinate universal transverse Mercator easting (GCE). It is an integer of 1 to
6 digits.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture/biom:GeographicSampleAcquisitionLocation
NIEM Element: mo:MGRSCoordinateStringText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.998_12: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Northing (GCN)
Description:
The twelfth information item is the geographic coordinate universal transverse Mercator northing (GCN). It is an integer of 1 to
8 digits.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture/biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
929
Type-18: DNA Data
18.998_13: Geographic Sample Acquisition Location - Geographic Reference Text (GRT)
Description:
It is a free form text describing a street address or other physical location (such as ‘Corner of Washington and Madison,
Geneva, NY’).
Field Minimum
1
Field Maximum
150
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture/biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
18.998_14: Geographic Sample Acquisition Location - Geographic Coordinate Other System Identifier (OSI)
Description:
A fourteenth optional information item geographic coordinate other system identifier (OSI) allows for other coordinate systems.
This information items specifies the system identifier. It is up to 10 characters in length. Examples are: • MGRS (Militar Grid
Reference System), • USNG (United States National Grid), • GARS (Global Area Reference System), • GEOREF (World
Geographic Reference), • LANDMARK landmark (e.g. hydant) and position relative to the landmark.
Field Minimum
1
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture/biom:GeographicSampleAcquisitionLocation
NIEM Element: biom:GeographicLocationSystemName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
930
Type-18: DNA Data
18.998_15: Geographic Sample Acquisition Location - Geographic Coordinate Other System Value (OCV)
Description:
A fifteenth optional information item, is the geographic coordinate other system value (OCV). It shall only be present if OSI is
present in the record. It can be up to 126 characters in length. If OSI is LANDMARK, OCV is free text and may be up to 126
characters. For details on the formatting of OCV for the other coordinate systems shown in OSI as examples, see http://earthinfo.nga.mil/GandG/coordsys/grids/referencesys.html .
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageDNARecord/biom:DNASample/biom:BiometricCapture/biom:GeographicSampleAcquisitionLocation
NIEM Element: biom:GeographicLocationText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.001: Record Header (LEN)
Description:
The record header appears as the first field (xx.001) in each Record Type. It contains information particular to the encoding
format chosen, in order to enable proper reading of the record. In Traditional encoding, this field contains the record length in
bytes (including all information separators). In NIEM-conformant XML encoding, this field contains the RecordCategoryCode,
which is the numeric representation of the Record Type.
Field Minimum
T = 4; X = 1
Field Maximum
T = 8; X = 2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord
NIEM Element: itl:Transaction
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
931
Type-20: Source Representation
20.002: Information Designation Character (IDC)
Description:
Each of the records present in a transaction, with the exception of the Type-1 record, shall include a field (xx.002) containing
the information designation character / IDC. The value of the IDC shall be a sequentially assigned positive integer starting
from zero and incremented by one up to a maximum of 99. IDC references are stated in Type-1 Field 1.003 Transaction
content (CNT) and shall be used to relate information items in the CNT field of the Type-1 record to the other records in the
transaction. Two or more records may share a single IDC solely to identify and link together records that pertain to different
representations of the same biometric trait.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ IDC ≤ 99 integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord
NIEM Element: biom:ImageReferenceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.003: SRN Cardinality (CAR)
Description:
This mandatory field indicates how this record is being used. It describes the cardinality: one to one (S), one to many (D), or
many-to-one (M) of how the source representation record relates to other record(s) within the transaction. See table 120 CAR
values in ANSI/NIST-ITL Update: 2015 for additional information.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
CAR = S, D, or M
Code List: CARDINALITY CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord
NIEM Element: biom:SourceRecordCardinalityCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
932
Type-20: Source Representation
20.004: Source Agency (SRC)
Description:
This is a mandatory field. See Section 7.6 of the ANSI/NIST-ITL 1-2011 Update: 2015 for details. The source agency name
may be entered in Field 21.993: Source agency name / SAN.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail/biom:ImageCaptureDetail/biom:CaptureOrganization
NIEM Element: nc:OrganizationIdentification/nc:IdentificationID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.005: Source Representation Date (SRD)
Description:
This optional field shall contain the local date and time that the source representation contained in the record was captured. It
may not be possible to know the exact date of imagery capture. In such a case, specify the date to the level known. For
traditional encoding, fill the unknown portions of the date with zeros. For XML, use a date element with the correct level of
precision. Field 20.022: Imagery capture date range estimate/ICDR should be used in conjunction with this field.
Field Minimum
Encoding Dependent
Field Maximum
Encoding Dependent
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Encoding Dependent
Special Characters
None
Format
n/a
Constraints
Encoding Dependent
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail/biom:ImageCaptureDetail
NIEM Element: biom:CaptureDate/nc:Date
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
933
Type-20: Source Representation
20.006: Horizontal Line Length (HLL)
Description:
This field is mandatory if a 2D still image is contained in this instance of the record. Otherwise it shall be omitted. HLL defines
the number of pixels contained on a single horizontal line of the image. The maximum horizontal size is limited to 65,535 pixels
in Record Types-4 and 8, and to 99,999 for other record types. The minimum value is 10 pixels. The total image size (HLL
times VLL) must be able to be accommodated in Field xx.001 for Traditional encoding.
Field Minimum
2
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
10 ≤ HLL ≤ 99999; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail
NIEM Element: biom:HorizontalLineLengthPixelQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.007: Vertical Line Length (VLL)
Description:
This field is mandatory if a 2D still image is contained in this instance of the record. Otherwise it shall be omitted. VLL defines
the number of horizontal lines contained in the image. The maximum vertical size is limited to 65,535 pixels in Record Types-4
and 8, and to 99,999 for other record types. The minimum value is 10 pixels.
Field Minimum
2
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
11 ≤ HLL ≤ 99999; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail
NIEM Element: biom:VerticalLineLengthPixelQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
934
Type-20: Source Representation
20.008: Scale Units (SLC)
Description:
This field is mandatory if a 2D still image is contained in this instance of the record. Otherwise it shall be omitted. The image
sampling frequency (pixel density). A value of “1” shall indicate pixels per inch. A value of “2” shall indicate pixels per
centimeter. A value of “0” in this field indicates that no scale is provided, and the quotient of THPS/TVPS shall provide the pixel
aspect ratio. For non-contact images of body parts, SLC shall be set to 0 unless the object being imaged is a fixed distance
from the capture device and the ppi or ppmm values for the capture device are accurately known at that fixed distance.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
SLC = 0, 1 or 2; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail
NIEM Element: biom:ImageScaleUnitsCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.009: Transmitted Horizontal Pixel Scale (THPS)
Description:
This field is mandatory if a 2D still image is contained in this instance of the record. Otherwise it shall be omitted. This is the
integer pixel density used in the horizontal direction of the image if SLC has a value of “1” or “2”. If SLC has a value of “0”, this
information item shall contain the horizontal component of the pixel aspect ratio, up to 5 integer digits. For example, if the SLC
value = 1, then the value of THPS could be ‘1000’ for a 1000 ppi sensor.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail
NIEM Element: biom:ImageHorizontalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
935
Type-20: Source Representation
20.010: Transmitted Vertical Pixel Scale (TVPS)
Description:
This field is mandatory if a 2D still image is contained in this instance of the record. Otherwise it shall be omitted. This is the
integer pixel density used in the vertical direction of the image if SLC has a value of “1” or “2”. If SLC has a value of “0”, this
information item shall contain the vertical component of the pixel aspect ratio, up to 5 integer digits. If SLC is 1 or 2, then TVPS
shall equal THPS.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail
NIEM Element: biom:ImageVerticalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.011: Compression Algorithm (CGA)
Description:
This field is mandatory if a 2D still image is contained in this instance of the record. Otherwise it shall be omitted. This is a
mandatory field. It shall specify the algorithm used to compress the transmitted color or grayscale images.
Field Minimum
3
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
Value from Table 19
Compression codes in
ANSI/NIST-ITL 1-2011
Update: 2015
Code List: COMPRESSION CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail
NIEM Element: biom:ImageCompressionAlgorithmCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
936
Type-20: Source Representation
20.012: Bits Per Pixel (BPX)
Description:
This field is mandatory if a 2D still image is contained in this instance of the record. Otherwise it shall be omitted. This ASCII
field shall contain the number of bits used to represent a pixel. This field shall contain an entry of “8” for normal grayscale
values of “0” to “255” or each RGB color component. Any entry in this field greater than “8” shall represent a grayscale or color
pixel component with increased precision.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
8 ≤ BPX ≤ 99
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail
NIEM Element: biom:ImageBitsPerPixelQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.013: Color Space (CSP)
Description:
It shall contain an entry from the lookup codes below. This field is mandatory if a 2D still image is contained in this instance of
the record. Otherwise it shall be omitted. If the color image type cannot be determined, an entry of “RGB” shall be entered in
this field.
Field Minimum
3
Field Maximum
4
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
Value from Color Spaces in
ANSI/NIST-ITL 1-2011
Update: 2015
Code List: COLOR SPACES CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail
NIEM Element: biom:ImageColorSpaceCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
937
Type-20: Source Representation
20.014: Acquisition Source (AQS)
Description:
This mandatory field shall specify and describe the acquisition source. The following information items may be repeated for up
to 9 sources.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord
NIEM Element: biom:SourceAcquisition
XML Min/Max: 1 / 9
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.014_0: Acquisition Source - Subfields: Repeating sets of information items (AQS_0)
Description:
This mandatory field shall specify and describe the acquisition source. The information items may be repeated for up to 9
sources.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
9
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord
NIEM Element: biom:SourceAcquisition
XML Min/Max: 1 / 9
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
938
Type-20: Source Representation
20.014_1: Acquisition Source - Acquisition Source Type (AQT)
Description:
The first information item, Acquisition source type (AQT), is mandatory and it shall be a numeric entry selected from the
“attribute code’ column of the Acquisition Source codelist in ANSI/NIST-ITL Update: 2015.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
Value from Acquisition
source in ANSI/NIST-ITL 12011 Update: 2015
Code List: ACQUISITION SOURCE CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceAcquisition
NIEM Element: biom:AcquisitionSourceCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.014_2: Acquisition Source - Analog to Digital Conversion (A2D)
Description:
The second information item is mandatory if the acquisition source is analog, and the data is stored in digital format. It is a text
field, analog to digital conversion (A2D), that describes the analog to digital equipment used to transform the source. This field
should address parameters used, such as sample rate, if known.
Field Minimum
1
Field Maximum
200
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceAcquisition
NIEM Element: biom:AcquisitionDigitalConversionDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
939
Type-20: Source Representation
20.014_3: Acquisition Source - Radio Transmission Format Description (FDN)
Description:
The third information item is mandatory if the AQT is 23 or 24. It is a text field, radio transmission format description (FDN). It is
optional for other radio transmission codes.
Field Minimum
1
Field Maximum
200
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceAcquisition
NIEM Element: biom:AcquisitionRadioTransmissionFormatDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.014_4: Acquisition Source - Acquisition Special Characteristics (AQSC)
Description:
The fourth information item is optional. It is a free text field, acquisition special characteristics (AQSC) that is used to describe
any specific conditions not mentioned in the [Acquisition Source] table. An example would be a nearinfrared camera outputting
images in visible wavelengths.
Field Minimum
1
Field Maximum
200
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceAcquisition
NIEM Element: biom:AcquisitionSpecialCharacteristicsText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
940
Type-20: Source Representation
20.015: Source Representation Format (SFT)
Description:
This is a mandatory field comprised of two information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord
NIEM Element: biom:SourceFileFormat
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.015_1: Source Representation Format - File Type (FTY)
Description:
The first information item is mandatory. It is file type (FTY). If the source representation is a digital file, this shall contain the
suffix indicating the file type (such as JPG). If it is an analog file, enter ‘ANALOG’. For digital data stored in other formats (such
as digital tape), enter ‘OTHER’.
Field Minimum
3
Field Maximum
6
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceFileFormat
NIEM Element: biom:SourceFileCategoryText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
941
Type-20: Source Representation
20.015_2: Source Representation Format - Decoding Instructions (DEI)
Description:
The second information item is decoding instructions (DEI). It is optional and contains free text up to 1000 characters.
Field Minimum
1
Field Maximum
1000
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceFileFormat
NIEM Element: biom:SourceFileDecodingInstructionsText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.016: Segments (SEG)
Description:
This optional field shall consist of a subfield for each segment of a 2D image to be defined. Each subfield consists of a series
of information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail
NIEM Element: biom:ImageSegment
XML Min/Max: 0 / 99
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
942
Type-20: Source Representation
20.016_0: Segments - Subfields: Repeating sets of information items (SEG_0)
Description:
This optional field shall consist of a subfield for each segment of a 2D image to be defined. Each subfield consists of a series
of information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
99
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail
NIEM Element: biom:ImageSegment
XML Min/Max: 0 / 99
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.016_1: Segments - Reference Segment Position (RSP)
Description:
The first information item is the reference segment position / RSP. This provides a unique index to a segmentation.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ RSP ≤ 99, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail/biom:ImageSegment
NIEM Element: biom:ImageSegmentID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
943
Type-20: Source Representation
20.016_2: Segments - Internal File Reference Pointer (IPT)
Description:
This information item is the internal file reference pointer (IPT). It is set to 0 if the source representation is a single file. If the
external file referenced in Field 20.994: External file reference (EFR) or Field 21.994: External file reference (EFR) is a PDF,
video, or presentation file, or has multiple locations where a sample may be located, this information item is the reference to
the particular instance, such as page, video frame, or slide number used to derive the image transmitted in other record types.
If a particular frame is chosen and there is no further image segmentation needed, the following information items shall not be
used.
Field Minimum
1
Field Maximum
15
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail/biom:ImageSegment
NIEM Element: biom:ImageSegmentInternalFileLocationText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.016_3: Segments - Number of Points (NOP)
Description:
Specifies the number of vertices. HPO and VPO are repeated as pairs, in order by point following the path, up to the final
point – for a total of NOP pairs.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
3 ≤ NOP ≤ 99, positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail/biom:ImageSegment
NIEM Element: biom:PositionPolygonVertexQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
944
Type-20: Source Representation
20.016_4: Segments - Horizontal Point Offset (HPO)
Description:
The pixel counts to the right. HPO and VPO are repeated as pairs, in order by point following the path, up to the final point –
for a total of NOP pairs.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
NOP
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ HPO ≤ HLL, nonnegative integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail/biom:ImageSegment/biom:PositionPolygonVertex
NIEM Element: biom:PositionHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.016_5: Segments - Vertical Point Offset (VPO)
Description:
The pixel counts down from the origin.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
NOP
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ VPO ≤ VLL, nonnegative integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail/biom:ImageSegment/biom:PositionPolygonVertex
NIEM Element: biom:PositionVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
945
Type-20: Source Representation
20.017: Scanned Horizontal Pixel Scale (SHPS)
Description:
This field is mandatory if a 2D still image is contained in this instance of the record. Otherwise it shall be omitted. This ASCII
field shall specify the horizontal pixel density used for scanning providing the SLC field contains a "1" or a "2". Otherwise, it
indicates the horizontal component of the pixel aspect ratio, up to 5 integer digits. This field is used if the transmission pixel
scale differs from the original image scale, as listed in Transmitted horizontal pixel scale / THPS. Note that density is directly
related to resolution.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
Positive Integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail/biom:ImageCaptureDetail
NIEM Element: biom:CaptureHorizontalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.018: Scanned Vertical Pixel Scale (SVPS)
Description:
This field is mandatory if a 2D still image is contained in this instance of the record. Otherwise it shall be omitted. This ASCII
field shall specify the vertical pixel density used for scanning providing the SLC field contains a "1" or a "2". Otherwise, it
indicates the vertical component of the pixel aspect ratio, up to 5 integer digits. Note that density is directly related to
resolution. If SLC is 1 or 2 and SHPS is entered, then SVPS shall equal SHPS. This field is used if the transmission pixel scale
differs from the original image scale, as listed in Transmitted vertical pixel scale / TVPS.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
Positive Integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail/biom:ImageCaptureDetail
NIEM Element: biom:CaptureVerticalPixelDensityValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
946
Type-20: Source Representation
20.019: Time Index (TIX)
Description:
This is a conditional field. If the record contains video or audio, it shall contain the start and end times of segments within the
file. This field shall contain two information items, time index start /TIS and time index end / TIE for the start and end times of
segments within a video or audio file, measured in hh:mm:ss.sss. This field is comprised of one or more subfields. Each
repeating subfield corresponds to a single segment, with a starting and end time as separate information items. This data is
handled differently for each encoding. The zero time index shall be clearly indicated on the source, unless it is the absolute
beginning of the file.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail
NIEM Element: biom:TimeSegment
XML Min/Max: 0 / 99
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.019_0: Time Index - Subfields: Repeating sets of information items (TIX_0)
Description:
This is a conditional field. If the record contains video or audio, it shall contain the start and end times of segments within the
file. This field shall contain two information items, time index start /TIS and time index end / TIE for the start and end times of
segments within a video or audio file, measured in hh:mm:ss.sss. This field is comprised of one or more subfields. Each
repeating subfield corresponds to a single segment, with a starting and end time as separate information items. This data is
handled differently for each encoding. The zero time index shall be clearly indicated on the source, unless it is the absolute
beginning of the file.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
99
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail
NIEM Element: biom:TimeSegment
XML Min/Max: 0 / 99
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
947
Type-20: Source Representation
20.019_1: Time Index - Time Index Start (TIS)
Description:
For Type-20 or Type-21 records containing video or audio, this information item of the Time Index field shall contain the start
times of segments within a video or audio file, measured in hh:mm:ss.sss where ss.sss refers to the seconds and milliseconds.
Field Minimum
12
Field Maximum
12
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
NS
Special Characters
n/a
Format
n/a
Constraints
TIS ≥ zero time index
(00:00:00.000)
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail/biom:TimeSegment
NIEM Element: biom:TimeSegmentStartTime
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.019_2: Time Index - Time Index End (TIE)
Description:
For Type-20 or Type-21 records containing video or audio, this information item of the Time Index field shall contain the end
times of segments within a video or audio file, measured in hh:mm:ss.sss where ss.sss refers to the seconds and milliseconds.
Field Minimum
12
Field Maximum
12
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
NS
Special Characters
n/a
Format
n/a
Constraints
TIE > TIS
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail/biom:TimeSegment
NIEM Element: biom:TimeSegmentEndTime
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
948
Type-20: Source Representation
20.020: Comment (COM)
Description:
The optional Comment field may be used to insert comments or other text information with the representation standard.
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord
NIEM Element: biom:SourceCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.021: Source Representation Number (SRN)
Description:
This mandatory field contains a reference number for the source representation stored in this record. Note that the segment
references are contained in Field 20.016: Segments (SEG) if they exist. The value for SRN in Field 20.021 corresponds to the
SRN that may be referenced as the first information item in the SOR field of other Record Types. The SRN is a positive integer
that uniquely refers to a particular instance of Record Type-20. It is an integer, numbered sequentially beginning at one and
incremented for each instance of Record Type-20.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ SRN ≤ 255; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord
NIEM Element: biom:SourceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
949
Type-20: Source Representation
20.022: Imagery Capture Date Range Estimate (ICDR)
Description:
This is the amount of time (plus and minus) of which SRD is the center point during which the image data could have been
originally collected. In Traditional format, it is entered in the format as YyyMmmDdd. It is possible to enter only a year, month
and/or day range, such as D5, meaning that the actual date of collection is estimated to be 5 days plus or minus from that
specified in SRD. Leading zeros need not be entered. For XML implementations, this element is represented using an XML
duration type with the format PnYnMnDTnHnMnS, P indicates that there is a date value range and T indicates that there is a
time value range. Under P, nY is the number of years, nM is the numbers of months, nD is the number of days. Under T, nH is
the number of hours, nM is the number of minutes, and nS is the number of seconds.
Field Minimum
2
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
Time measure indicator
followed by 1 or 2 digits.
May be concatenated, with
larger time units first. Units:
Y year, M month, D day
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail/biom:ImageCaptureDetail
NIEM Element: biom:CaptureDateEstimateRangeDuration
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.101: Voice Engine Mode Export (MODEL_EXPORT)
Description:
Information set returned with the Speaker Candidate Results (SCR) response TOT as a result of the SID - Speaker
Identification request TOT. The information set contains results regarding matches against the stored voice engine model.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: DoD EBTS v4.0
Status: Active
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
950
Type-20: Source Representation
20.101_1: Voice Engine Mode Export - Model Identifier (MODEL_EXPORT_1)
Description:
Identifier for the Exported Model File
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: DoD EBTS v4.0
Status: Active
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
20.101_2: Voice Engine Mode Export - Model Export Software Version (MODEL_EXPORT_2)
Description:
Software version of the voice model engine generating the model and running the voice match comparison alogorithm.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: DoD EBTS v4.0
Status: Active
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
951
Type-20: Source Representation
20.101_3: Voice Engine Mode Export - Model Export Software Name (MODEL_EXPORT_3)
Description:
Name of the software voice model engine generating the model and running the voice match comparison alogorithm.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: DoD EBTS v4.0
Status: Active
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
20.101_4: Voice Engine Mode Export - Model Export Associated Type 2 Reference (MODEL_EXPORT_4)
Description:
Transaction Identification Character (IDC) for the Type 2 record associated with the exported model.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: DoD EBTS v4.0
Status: Active
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
952
Type-20: Source Representation
20.101_5: Voice Engine Mode Export - Model Export Comment (MODEL_EXPORT_5)
Description:
Comment Text Regarding Model Export
Field Minimum
1
Field Maximum
255
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: DoD EBTS v4.0
Status: Active
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
20.101_6: Voice Engine Mode Export - Model Export Software Vendor (MODEL_EXPORT_6)
Description:
Text that specifies the software code vendor name
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: DoD EBTS v4.0
Status: Active
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
953
Type-20: Source Representation
20.902: Annotated Information (ANN)
Description:
This is an optional field, listing the operations performed on the original source in order to prepare it for inclusion in a biometric
record type.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord
NIEM Element: biom:ProcessAnnotation
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.902_0: Annotated Information - Subfields: Repeating sets of information items (ANN_0)
Description:
This optional field is used to store annotation, logging, or processing information associated with one or more processing
algorithms, processes, or latent workstations (other than the FBI-developed ULW). If present, this text shall consist of one or
more subfields comprised of a set of information items. Four mandatory items comprise a subfield.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
*
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord
NIEM Element: biom:ProcessAnnotation
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
954
Type-20: Source Representation
20.902_1: Annotated Information - Greenwich Mean Time (GMT)
Description:
This information item is the Greenwich Mean Time (GMT) when the processing occured. The data is formatted as
YYYYMMDDhhmmssZ, where the Z is indicates the zone description of 0 hours. Time (GMT) units. This time is independent of
the actual time zone where the time and date is recorded.
Field Minimum
15
Field Maximum
15
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
YYYYMMDDHHMMSSZ for Traditional Encoding
Constraints
Encoding Dependent
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessUTCDate/nc:DateTime
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
20.902_2: Annotated Information - Processing Algorithm Name / Version (NAV)
Description:
This information item shall contain text identifying the name and version of the processing algorithm, application, procedure, or
workstation.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessName
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
955
Type-20: Source Representation
20.902_3: Annotated Information - Algorithm Owner (OWN)
Description:
This information item shall contain an unformatted text string of up to 64 characters with the contact information for the
organization that owns the processing algorithm or latent workstation. Where there is no 'algorithm owner,' enter N/A.
Field Minimum
1
Field Maximum
64
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessOwnerText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.902_4: Annotated Information - Process Description (PRO)
Description:
This information item field shall contain text describing a process or procedure applied to the sample in this Type-9 record.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessDescriptionText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
956
Type-20: Source Representation
20.903: Device Unique Identifier (DUI)
Description:
This is an optional field. The DUI shall contain a string uniquely identifying the device or source of the data. This field shall be
one of the following: a Host PC MAC address (identified by the first character “M”), a Host PC processor ID (identified by the
first character “P”).
Field Minimum
13
Field Maximum
16
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
Any
Format
n/a
Constraints
First character = M or P
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail/biom:ImageCaptureDevice
NIEM Element: biom:DeviceID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.904: Make/Model/Serial Number (MMS)
Description:
This is an optional field. The MMS contains the make, model and serial number for the capture device. It shall consist of three
information items. Each information item shall be 1 to 50 characters. Any or all information items may indicate that information
is unknown with the value “0”.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:ImageCaptureType
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
957
Type-20: Source Representation
20.904_1: Make/Model/Serial Number - Make (MAK)
Description:
The name of the manufacturer for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail/biom:ImageCaptureDevice
NIEM Element: biom:DeviceMakeText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.904_2: Make/Model/Serial Number - Model (MOD)
Description:
The model number for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail/biom:ImageCaptureDevice
NIEM Element: biom:DeviceModelText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
958
Type-20: Source Representation
20.904_3: Make/Model/Serial Number - Serial Number (SER)
Description:
The serial number for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail/biom:ImageCaptureDevice
NIEM Element: biom:DeviceSerialNumberText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.993: Source Agency Name (SAN)
Description:
This is an optional field. It may contain up to 125 Unicode characters. It is the name of the agency referenced in Field 20.004:
Source agency / SRC.
Field Minimum
1
Field Maximum
125
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageSourceRepresentationRecord/biom:SourceMediaDetail/biom:ImageCaptureDetail/biom:CaptureOrganization
NIEM Element: nc:OrganizationName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
959
Type-20: Source Representation
20.994: External File Reference (EFR)
Description:
This conditional field shall be used to enter the URL / URI or other unique reference to a storage location for all source
representations, if the data is not contained in Field 20.999: Associated context data (DATA). If this field is used, Field 20.999
shall not be set. However, one of the two fields shall be present in all instances of this record type. A non-URL reference might
be similar to: “Case 2009:1468 AV Tape 5”. It is highly recommended that the user state the format of the external file in Field
20.020: Comment / COM.
Field Minimum
1
Field Maximum
200
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord
NIEM Element: biom:SourceExternalFileReferenceText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.995: Associated Context (ASC)
Description:
Optional field xx.995 is contained in biometric data sample Record Types 10 and above that may have instances of Record
Type-21 linked to it. Record Type-21 stores images and/or recordings that are not the actual source of the biometric data
contained in another Record Type, but do show the context of the biometric data. An example would be a crime scene
photograph showing the location of a glass that had latent prints on it. However, the close-up image of the latent prints could
appear in a Type-20 record (since that is the image that the individual fingerprint images are derived from), with the segmented
individual images appearing in Type-13 records. This field consists of a maximum of 255 repeating subfields, each of which
contains two information items, as described below. There may be multiple instances of associated context records associated
with a single biometric sample. Figure 2 illustrates relationships of the fields and information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord
NIEM Element: biom:AssociatedContext
XML Min/Max: 0 / 255
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
960
Type-20: Source Representation
20.995_0: Associated Context - Subfields: Repeating sets of information items (ASC_0)
Description:
This optional field refers to one or more Type 21 Records with the same ACN. Type 21 Records contain images that are NOT
used to derive the biometric data in Field 13.999: Latent friction ridge image (DATA) but that may be relevant to the collection
of that data, such as general scenes of the area where a latent print was found.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
255
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord
NIEM Element: biom:AssociatedContext
XML Min/Max: 0 / 255
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.995_1: Associated Context - Associated Context Number (ACN)
Description:
The first information item for the associated context number / ACN for a particular Record Type-21. This is mandatory for each
Field xx.995, when the field is used. It contains an index to a particular instance of a Type-21 record in the transaction. This
same index value appears in the appropriate instance of Record Type-21 as Field 21.021: Associated context number (ACN).
The value of the ACN shall be a sequentially assigned a positive integer starting from one and incremented by one, not to
exceed 255.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ ACN ≤ 255; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:AssociatedContext
NIEM Element: biom:ContextID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
961
Type-20: Source Representation
20.995_2: Associated Context - Associated Segment Position (ASP)
Description:
The first information item in Field xx.995 is optional. It is the associated segment position / ASP. It contains the index to a
particular set of segmentation coordinates of the associated context data. This same segmentation index value appears in
Record Type-21 as the associated segment position / ASP in Field 21.016: Segments / SEG. There may be up to 99 segments
listed in Field 21.016, but only the relevant segment is contained in Field xx.995.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
1 ≤ ASP ≤ 99; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord/biom:AssociatedContext
NIEM Element: biom:ImageSegmentID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.996: Hash (HAS)
Description:
This is an optional field. It shall contain the hash value of the source representation in the external file reference in Field
20.994: External file reference / EFR or the 2D still image or other biometric data in Field 20.999: Source representation data /
DATA of this record, calculated using SHA-256.
Field Minimum
64
Field Maximum
64
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord
NIEM Element: biom:ImageHashValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
962
Type-20: Source Representation
20.998: Geographic Sample Acquisition Location (GEO)
Description:
This optional field contains the location where the original source was acquired – not where it is stored.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.998_01: Geographic Sample Acquisition Location - Universal Time Entry (UTE)
Description:
The coordinated universal time (UTC) where the biometric sample was collected. This time is independent of the actual time
zone where the time and date is recorded. The date is YYYYMMDDhhmmssZ, where the Z is indicates the zone description of
0 hours. If sample collection time is unknown, set it to "00000000000000Z."
Field Minimum
Encoding Dependent
Field Maximum
Encoding Dependent
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Encoding Dependent
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: biom:CaptureUTCDateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
963
Type-20: Source Representation
20.998_02: Geographic Sample Acquisition Location - Latitude Degree Value (LTD)
Description:
The second information item is latitude degree value (LTD). This is a value that specifies the degree of latitude. The value shall
be between -90 (inclusive) and +90 (inclusive). The degrees may be expressed as an integer (without a decimal) or a real
number including decimals. If decimals are present, then minutes and seconds shall be empty. Examples: Buenos Aires,
Argentina: -34 (with minutes LTM = 36) NIST, Gaithersburg, Maryland: 39.137627 (no LTM or LTS)
Field Minimum
1
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal,Minus Sign,Plus
Sign
Format
n/a
Constraints
-90 ≤ LTD ≤ 90
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longer formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.998_03: Geographic Sample Acquisition Location - Latitude Minute Value (LTM)
Description:
This information item is latitude minute value (LTM). This is a value that specifies a minute of a degree. The value shall be
between 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall be empty. Thus, the allowed special character is a
period. The minute value can be empty, even if the degree value is an integer. LTM and LGM are co-conditional, so they shall
both be present if either is present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LTM < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longer formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
964
Type-20: Source Representation
20.998_04: Geographic Sample Acquisition Location - Latitude Second Value (LTS)
Description:
The fourth information item is the latitude second value (LTS). This is a value that specifies a second of a minute. The integer
shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
None
Format
n/a
Constraints
0 ≤ LTS < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longer formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.998_05: Geographic Sample Acquisition Location - Longitude Degree Value (LGD)
Description:
The fifth information item is the longitude degree value (LGD). It is a value that specifies the degree of a longitude. The value
shall be between -180 (inclusive) and +180 (inclusive). If LTD is present, then LGD shall be present. The degrees may be
expressed as whole numbers (without a decimal) or real numbers including decimals. If decimals are present, then minutes
and seconds are empty. Examples: Buenos Aires, Argentina: -58 (with minutes LGM = 22), NIST, Gaithersburg, Maryland: 77.216032 (no LGM or LGS)
Field Minimum
1
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal,Minus Sign,Plus
Sign
Format
n/a
Constraints
-180 ≤ LGD ≤ 180
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longer formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
965
Type-20: Source Representation
20.998_06: Geographic Sample Acquisition Location - Longitude Minute Value (LGM)
Description:
The sixth information item is the longitude minute value (LGM). It is a value that specifies a minute of a degree. The value shall
be from 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall not appear. The minute value is empty, even if the
degree value is an integer. If LTM is present, then LGM shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LGM < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longer formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.998_07: Geographic Sample Acquisition Location - Longitude Second Value (LGS)
Description:
The seventh information item is the longitude second value (LGS). This is a value that specifies a second of a minute. The
integer shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer. If LTS is
present, then LGS shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
None
Format
n/a
Constraints
0 ≤ LGS < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longer formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
966
Type-20: Source Representation
20.998_08: Geographic Sample Acquisition Location - Elevation (ELE)
Description:
The eighth information item is elevation (ELE). It is expressed in meters. It is a numeric value. It is between -422 meters (Dead
Sea) and 8848 meters (Mount Everest). Allowed special characters are the negative sign and the period.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Minus Sign,Period
Format
n/a
Constraints
-422.000 ≤ ELE ≤
8848.000; real number
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longer formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.998_09: Geographic Sample Acquisition Location - Geodetic Datum Code (GDC)
Description:
The ninth information item is the geodetic datum code (GDC11). It is an alphanumeric value of 3 to 6 characters in length. This
information item is used to indicate which coordinate system was used to represent the values in information items 2 through
7. If no entry is made in this information item, then the basis for the values entered in the first eight information items shall be
WGS84, the code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values. If no entry is
made in this information item, then the basis for the values entered in the first eight information items shall be WGS84, the
code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values.
Field Minimum
3
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
Value from Geographic
coordinate datum code
values in ANSI/NIST-ITL 12011 Update: 2015
Code List: GEOGRAPHIC COORDINATE DATUM CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: Latitute data no longer formatted
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
967
Type-20: Source Representation
20.998_10: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Zone (GCM)
Description:
It is an alphanumeric value of 2 to 3 characters. This is a one or two digit UTM zone number followed by the 8 degree
latitudinal band designator (which is a single letter).
Field Minimum
2
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
One or two digits followed
by a single letter
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationUTMCoordinateValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.998_11: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Easting (GCE)
Description:
The eleventh information item is the geographic coordinate universal transverse Mercator easting (GCE). It is an integer of 1 to
6 digits.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationUTMCoordinateValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
968
Type-20: Source Representation
20.998_12: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Northing (GCN)
Description:
The twelfth information item is the geographic coordinate universal transverse Mercator northing (GCN). It is an integer of 1 to
8 digits.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationUTMCoordinateValue
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.998_13: Geographic Sample Acquisition Location - Geographic Reference Text (GRT)
Description:
It is a free form text describing a street address or other physical location (such as ‘Corner of Washington and Madison,
Geneva, NY’).
Field Minimum
1
Field Maximum
150
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: biom:GeographicLocationText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
969
Type-20: Source Representation
20.998_14: Geographic Sample Acquisition Location - Geographic Coordinate Other System Identifier (OSI)
Description:
A fourteenth optional information item geographic coordinate other system identifier (OSI) allows for other coordinate systems.
This information items specifies the system identifier. It is up to 10 characters in length. Examples are: • MGRS (Militar Grid
Reference System), • USNG (United States National Grid), • GARS (Global Area Reference System), • GEOREF (World
Geographic Reference), • LANDMARK landmark (e.g. hydant) and position relative to the landmark.
Field Minimum
1
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: biom:GeographicLocationSystemName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
20.998_15: Geographic Sample Acquisition Location - Geographic Coordinate Other System Value (OCV)
Description:
A fifteenth optional information item, is the geographic coordinate other system value (OCV). It shall only be present if OSI is
present in the record. It can be up to 126 characters in length. If OSI is LANDMARK, OCV is free text and may be up to 126
characters. For details on the formatting of OCV for the other coordinate systems shown in OSI as examples, see http://earthinfo.nga.mil/GandG/coordsys/grids/referencesys.html .
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
970
Type-20: Source Representation
20.999: Source Representation Data (DATA)
Description:
If this field is used, Field 20.994: External file reference / EFR shall not be set. However, one of the two fields shall be present
in all instances of this record type. In Traditional format, this field shall be the last field in the record layout.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
B
Special Characters
None
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageSourceRepresentationRecord
NIEM Element: nc:Base64BinaryObject
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.001: Record Header (LEN)
Description:
The record header appears as the first field (xx.001) in each Record Type. It contains information particular to the encoding
format chosen, in order to enable proper reading of the record. In Traditional encoding, this field contains the record length in
bytes (including all information separators). In NIEM-conformant XML encoding, this field contains the RecordCategoryCode,
which is the numeric representation of the Record Type.
Field Minimum
T = 4; X = 1
Field Maximum
T = 8; X = 2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord
NIEM Element: itl:Transaction
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
971
Type-21: Associated Context
21.002: Information Designation Character (IDC)
Description:
This mandatory field shall contain the IDC assigned to this Type-21 record as listed in the information item IDC for this record
in Field 1.003: Transaction content / CNT.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤IDC ≤99; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord
NIEM Element: biom:ImageReferenceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.004: Source Agency (SRC)
Description:
This is a mandatory field. The source agency name may be entered in Field 21.993: Source agency name / SAN.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture/biom:CaptureOrganization
NIEM Element: nc:OrganizationIdentification/nc:IdentificationID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
972
Type-21: Associated Context
21.005: Associated Context Date (ACD)
Description:
This optional field shall contain the date and time that the context representation contained in the record was captured. It may
not be possible to know the exact date of imagery capture. In such a case, specify the date to the level known and fill the rest
of the date with zeros. For traditional encoding, fill the unknown portions of the date with zeros. For XML, use a date element
with the correctlevel of precision.Field 21.022: Imagery capture date range estimate/ ICDR should be used in conjunction
with this field.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Encoding Specific
Special Characters
Colon, Period
Format
YYYYMMDDhh:mm:ss.sss
Constraints
N/A
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture
NIEM Element: biom:CaptureDate/nc:Date
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.006: Medical Device Information (MDI)
Description:
This field is designed to allow the transmission of information concerning medically implanted devices or devices used by an
individual externally that may be discovered in or on unknown deceased and may assist in the person's identification. Each
subfield is comprised of six information items, any combination of which may be entered. Each subfield describes a single
device (such as a pacemaker or an artificial knee).
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail
NIEM Element: biom:MedicalDevice
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
973
Type-21: Associated Context
21.006_0: Medical Device Information - Subfields: Repeating sets of information items (MDI_0)
Description:
This field is designed to allow the transmission of information concerning medically implanted devices or devices used by an
individual externally that may be discovered in or on unknown deceased and may assist in the person's identification. Each
subfield is comprised of six information items, any combination of which may be entered. Each subfield describes a single
device (such as a pacemaker or an artificial knee).
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
*
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail
NIEM Element: biom:MedicalDevice
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
21.006_1: Medical Device Information - Type of Device (TYP)
Description:
The first information item is the type of device / TYP. It is optional. A typical entry may be 'metal plate in right arm' or 'external
leg brace for left leg'.
Field Minimum
1
Field Maximum
500
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:MedicalDevice
NIEM Element: biom:DeviceCategoryText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
974
Type-21: Associated Context
21.006_2: Medical Device Information - Device Manufacturer (MFG)
Description:
The second information item is the device manufacturer / MFG. It is optional.
Field Minimum
1
Field Maximum
500
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:MedicalDevice
NIEM Element: biom:DeviceManufacturerText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
21.006_3: Medical Device Information - Device Make (MAK)
Description:
The third information item is the device make / MAK. It is optional.
Field Minimum
1
Field Maximum
500
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:MedicalDevice
NIEM Element: biom:DeviceMakeText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
975
Type-21: Associated Context
21.006_4: Medical Device Information - Device Model (MOD)
Description:
The fourth information item is the device model / MOD. It is optional.
Field Minimum
1
Field Maximum
500
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:MedicalDevice
NIEM Element: biom:DeviceModelText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
21.006_5: Medical Device Information - Device Serial Number (SER)
Description:
The fifth information item is the device serial number / SER. It is optional.
Field Minimum
1
Field Maximum
500
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:MedicalDevice
NIEM Element: biom:DeviceSerialNumberText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
976
Type-21: Associated Context
21.006_6: Medical Device Information - Comments (COM)
Description:
The sixth information item is optional. It is any comment / COM concerning the device.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:MedicalDevice
NIEM Element: biom:DeviceDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
21.015: Associated Context Format (AFT)
Description:
This is a mandatory field comprised of two information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord
NIEM Element: biom:ContextFileFormat
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
977
Type-21: Associated Context
21.015_1: Associated Context Format - File Type (FTY)
Description:
The first information item is mandatory. It is file type / FTY. If the associated context file is a digital file, this shall contain the
suffix indicating the file type. If it is an analog file, enter ‘ANALOG’. For digital data stored in other formats (such as digital tape)
that do not have computer file names and suffixes, enter ‘OTHER’. Examples of suffixes indicating file types are: WAV and
TXT. There are many file extensions in common use, depending upon the type of data.
Field Minimum
3
Field Maximum
6
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextFileFormat
NIEM Element: biom:ContextFileCategoryText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.015_2: Associated Context Format - Decoding Instructions (DEI)
Description:
The second information item is decoding instructions / DEI. It is optional and contains free text up to 1000 characters.
Field Minimum
1
Field Maximum
1000
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextFileFormat
NIEM Element: biom:ContextFileDecodingInstructionsText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
978
Type-21: Associated Context
21.016: Segments (SEG)
Description:
This optional field shall consist of a subfield for each segment to be defined. Each subfield consists of a series of information
items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail
NIEM Element: biom:ImageSegment
XML Min/Max: 0 / 99
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.016_0: Segments - Subfields: Repeating sets of information items (SEG_0)
Description:
This optional field shall consist of a subfield for each segment to be defined. Each subfield consists of a series of information
items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
99
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail
NIEM Element: biom:ImageSegment
XML Min/Max: 0 / 99
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
979
Type-21: Associated Context
21.016_1: Segments - Associated Segment Position (ASP)
Description:
The first information item is the associated segment position / ASP. This provides a unique index to a segmentation.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
1 ≤ASP ≤99; positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:ImageSegment
NIEM Element: biom:ImageSegmentID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.016_2: Segments - Internal File Reference Pointer (IPT)
Description:
The second information item is the internal file reference pointer/ IPT. It is set to 0 if the source representation is a single file. If
the external file referenced in Field 20.994: External file reference / EFR or Field 21.994: External file reference / EFR is a
PDF, video, or presentation file, or has multiple locations where a sample may be located, this information item is the
reference to the particular instance, such as page, video frame, or slide number used to derive the image transmitted in other
record types. If a particular frame is chosen and there is no further image segmentation needed, the following information
items shall not be used. This entry is free text with any special characters are allowed.
Field Minimum
1
Field Maximum
15
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:ImageSegment
NIEM Element: biom:ImageSegmentInternalFileLocationText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
980
Type-21: Associated Context
21.016_3: Segments - Number of Points (NOP)
Description:
Specifies the number of vertices.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
3 ≤NOP ≤99; positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:ImageSegment
NIEM Element: biom:PositionPolygonVertexQuantity
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.016_4: Segments - Horizontal Point Offset (HPO)
Description:
The pixel counts to the right.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
NOP
Character Types
N
Special Characters
None
Format
n/a
Constraints
non-negative integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:ImageSegment/biom:PositionPolygonVertex
NIEM Element: biom:PositionHorizontalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
981
Type-21: Associated Context
21.016_5: Segments - Vertical Point Offset (VPO)
Description:
The pixel counts down from the origin.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
0
Occurrence Maximum
NOP
Character Types
N
Special Characters
None
Format
n/a
Constraints
non-negative integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:ImageSegment/biom:PositionPolygonVertex
NIEM Element: biom:PositionVerticalCoordinateValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.019: Time Index (TIX)
Description:
This field is mandatory for records containing video or audio, but not 2D still images. If the record contains video or audio, it
shall contain the start and end times of segments within the file. For records containing video or audio, this field shall contain
two information items, time index start /TIS and time index end / TIE for the start and end times of segments within a video or
audio file. This field is comprised of one or more subfields. Each repeating subfield corresponds to a single segment, with a
starting and end time as separate information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail
NIEM Element: biom:TimeSegment
XML Min/Max: 0 / 99
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
982
Type-21: Associated Context
21.019_0: Time Index - Subfields: Repeating sets of information items (TIX_0)
Description:
This field is mandatory for records containing video or audio, but not 2D still images. If the record contains video or audio, it
shall contain the start and end times of segments within the file. For records containing video or audio, this field shall contain
two information items, time index start /TIS and time index end / TIE for the start and end times of segments within a video or
audio file. This field is comprised of one or more subfields. Each repeating subfield corresponds to a single segment, with a
starting and end time as separate information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
99
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail
NIEM Element: biom:TimeSegment
XML Min/Max: 0 / 99
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
21.019_1: Time Index - Time Index Start (TIS)
Description:
For records containing video or audio, this information item of the Time Index field shall contain the start times of segments
within a video or audio file, measured in hh:mm:ss.sss where ss.sss refers to the seconds and milliseconds.
Field Minimum
12
Field Maximum
12
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
NS
Special Characters
n/a
Format
n/a
Constraints
TIS ≥ 0 time index
(00:00:00.000)
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:TimeSegment
NIEM Element: biom:TimeSegmentStartTime
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
983
Type-21: Associated Context
21.019_2: Time Index - Time Index End (TIE)
Description:
For records containing video or audio, this information item of the Time Index field shall contain the end times of segments
within a video or audio file, measured in hh:mm:ss.sss where ss.sss refers to the seconds and milliseconds.
Field Minimum
12
Field Maximum
12
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
NS
Special Characters
n/a
Format
n/a
Constraints
TIE > TIS
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:TimeSegment
NIEM Element: biom:TimeSegmentEndTime
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.020: Comment (COM)
Description:
This optional field may be used to insert comments or other text information with the representation data.
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord
NIEM Element: biom:ContextCommentText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
984
Type-21: Associated Context
21.021: Associated Context Number (ACN)
Description:
This mandatory field contains a reference number for the context representation stored in this record. Note that the segment
references are contained in Field 21.016: Segments / SEG, if they exist. This number corresponds to the ACN that may be
referenced as the first information item in the ASC field of other Record Types. The ACN is a positive integer that uniquely
refers to a particular instance of Record Type-21. It is a positive integer, numbered sequentially beginning at one and
incremented for each instance of Record Type-21.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ACN ≤255; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord
NIEM Element: biom:ContextID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
985
Type-21: Associated Context
21.022: Image Capture Date Range Estimate (ICDR)
Description:
This is the amount of time (plus and minus) of which ACD is the center point during which the image data could have been
originally collected. In Traditional format, it is entered in the format as YyyMmmDdd. It is possible to enter only a year, month
and/or day range, such as D5 meaning that the actual date of collection is estimated to be 5 days plus or minus from that
specified in ACD. Leading zeros need not be entered. For XML implementations, this element is represented using an XML
duration type with the format PnYnMnDTnHnMnS, P indicates that there is a date value range and T indicates that there is a
time value range. Under P, nY is the number of years, nM is the numbers of months, nD is the number of days. Under T, nH is
the number of hours, nM is the number of minutes, and nS is the number of seconds.
Field Minimum
2
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
Time measure indicator
followed by 1 or 2 digits.
May be concatenated, with
larger time units first. Units:
Y year, M Month, D Day
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture
NIEM Element: biom:CaptureDateEstimateRangeDuration
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
21.046: Image Subject Condition (SUB)
Description:
This field is optional. There may be different values for SUB in different instances of Type-14 records. For example, some
images may have been acquired antemortem, while others were accquired post-mortem. This field describes the condition of
the subject at the time of the imaging.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail
NIEM Element: biom:SubjectExistentialDetails
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
986
Type-21: Associated Context
21.046_1: Image Subject Condition - Subject Status Code (SSC)
Description:
This information item is mandatory if this field is present. It is subject status code / SSC. Possible entries are: X = Status of
individual unknown; A = Data obtained from a living person – such as a victim or person unable to identify themselves; D =
Data obtained from a non-living person.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
SSC = X, A, or D
Code List: SUBJECT STATUS CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:SubjectExistentialDetails
NIEM Element: biom:SubjectExistentialStatusCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
21.046_2: Image Subject Condition - Subject Body Status Code (SBSC)
Description:
This information item shall be entered if and only if SSC is D. It is subject body status code / SBSC. Its purpose is to indicate
whether the information relates to an entire corpse or a separate body part. The numeric value is selected from the descriptors
below: 1 = Whole; 2 = Fragment.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
SBSC = 1 or 2
Code List: SUBJECT BODY STATUS CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:SubjectExistentialDetails
NIEM Element: biom:SubjectBodyStatusCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
987
Type-21: Associated Context
21.046_3: Image Subject Condition - Subject Body Class Code (SBCC)
Description:
This information item shall be entered if and only if SSC is D. It is subject body class code/ SBCC. The numeric value is
selected from the descriptors below: 1 = Natural Tissue; 2 = Decomposed; 3 = Skeletal.
Field Minimum
1
Field Maximum
1
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
SBCC = 1, 2 or 3
Code List: SUBJECT BODY CLASS CODES
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:SubjectExistentialDetails
NIEM Element: biom:SubjectBodyClassCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
21.047: Capture Organization Name (CON)
Description:
This field is optional. Note that this can be different from the agency entered in Field 21.004: Source agency / SRC and Field
21.993: Source agency name / SAN. SRC and SAN describe the agency that created the record. Since the record may have
been forwarded by another agency to the final destination, Field 1.008: Originating agency identifier / ORI is used to indicate
the transmitting organization. In many implementation domains, there are a limited number of transmission organizations
that can send data. Therefore, the agency listed in SRC may send the transaction to another location that has access rights to
the final destination. This intermediary may add information to the transaction, as well. The final transmitting organization code
is listed in Field 1.008: Originating agency identifier / ORI. Its name may be entered in Originating agency name /OAN in Field
1.017: Agency names / ANM.
Field Minimum
1
Field Maximum
1000
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture/biom:CaptureOrganization
NIEM Element: nc:OrganizationUnitName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
988
Type-21: Associated Context
21.902: Annotated Information (ANN)
Description:
This optional field is used to store annotation, logging, or processing information associated with one or more processing
algorithms, processes, or latent workstations (other than the FBI-developed ULW). If present, this text shall consist of one or
more subfields comprised of a set of information items. Four mandatory items comprise a subfield.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord
NIEM Element: biom:ProcessAnnotation
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.902_0: Annotated Information - Subfields: Repeating sets of information items (ANN_0)
Description:
This optional field is used to store annotation, logging, or processing information associated with one or more processing
algorithms, processes, or latent workstations (other than the FBI-developed ULW). If present, this text shall consist of one or
more subfields comprised of a set of information items. Four mandatory items comprise a subfield.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
*
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord
NIEM Element: biom:ProcessAnnotation
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
989
Type-21: Associated Context
21.902_1: Annotated Information - Greenwich Mean Time (GMT)
Description:
This information item is the Greenwich Mean Time (GMT) when the processing occured. The data is formatted as
YYYYMMDDhhmmssZ, where the Z is indicates the zone description of 0 hours. Time (GMT) units. This time is independent of
the actual time zone where the time and date is recorded.
Field Minimum
15
Field Maximum
15
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
YYYYMMDDHHMMSSZ for Traditional Encoding
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessUTCDate/nc:DateTime
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.902_2: Annotated Information - Processing Algorithm Name / Version (NAV)
Description:
This information item shall contain text identifying the name and version of the processing algorithm, application, procedure, or
workstation.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessName
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
990
Type-21: Associated Context
21.902_3: Annotated Information - Algorithm Owner (OWN)
Description:
This information item shall contain an unformatted text string of up to 64 characters with the contact information for the
organization that owns the processing algorithm or latent workstation. Where there is no 'algorithm owner,' enter N/A.
Field Minimum
1
Field Maximum
64
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessOwnerText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.902_4: Annotated Information - Process Description (PRO)
Description:
This information item field shall contain text describing a process or procedure applied to the sample in this Type-9 record.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessDescriptionText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
991
Type-21: Associated Context
21.993: Source Agency Name (SAN)
Description:
This is an optional field. It may contain up to 125 Unicode characters. It is the name of the agency referenced in Field 21.004:
Source agency / SRC.
Field Minimum
1
Field Maximum
125
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture/biom:CaptureOrganization
NIEM Element: nc:OrganizationName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.994: External File Reference (EFR)
Description:
This conditional field shall be used to enter the URL / URI or other unique reference to a storage location for all associated
context files EXCEPT 2D still images. If this field is used, Field 21.999: Associated context data / DATA shall not be set.
However, one of the two fields shall be present in all instances of this record type. It is an alphanumeric entry, with special
characters allowed. A non-URL reference might be similar to: “Case 2009:1468 AV Tape 5”. It is highly recommended that the
user state the format of the external file in Field 21.020: Comment / COM.
Field Minimum
1
Field Maximum
200
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord
NIEM Element: biom:SourceExternalFileReferenceText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
992
Type-21: Associated Context
21.996: Hash (HAS)
Description:
This optional field shall contain the hash value of the context representation in the external file reference in Field 21.994:
External file reference / EFR or the 2D still image or other data stored in Field 21.999: Associated context data / DATA of this
record, calculated using SHA-256.
Field Minimum
64
Field Maximum
64
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord
NIEM Element: biom:ImageHashValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.998: Geographic Sample Acquisition Location (GEO)
Description:
This optional field contains the location where the iris sample/original source/context information was acquired – not where it is
stored.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture
NIEM Element: biom:GeographicSampleAcquisitionLocation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
993
Type-21: Associated Context
21.998_01: Geographic Sample Acquisition Location - Universal Time Entry (UTE)
Description:
The coordinated universal time (UTC) where the biometric sample was collected. This time is independent of the actual time
zone where the time and date is recorded. The date is YYYYMMDDhhmmssZ, where the Z is indicates the zone description of
0 hours. If sample collection time is unknown, set it to "00000000000000Z."
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Encoding Specific
Special Characters
None
Format
YYYYMMDDHHMMSSZ for Traditional Encoding
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture/biom:GeographicSampleAcquisitionLoc
ation
NIEM Element: biom:CaptureUTCDateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.998_02: Geographic Sample Acquisition Location - Latitude Degree Value (LTD)
Description:
The second information item is latitude degree value (LTD). This is a value that specifies the degree of latitude. The value shall
be between -90 (inclusive) and +90 (inclusive). The degrees may be expressed as an integer (without a decimal) or a real
number including decimals. If decimals are present, then minutes and seconds shall be empty. Examples: Buenos Aires,
Argentina: -34 (with minutes LTM = 36) NIST, Gaithersburg, Maryland: 39.137627 (no LTM or LTS)
Field Minimum
1
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal, Minus Sign, Plus
Sign
Format
n/a
Constraints
-90 ≤LTD ≤90
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture/biom:GeographicSampleAcquisitionLoc
ation/nc:Location3DGeospatialCoordinate
NIEM Element: nc:LatitudeDegreeValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
994
Type-21: Associated Context
21.998_03: Geographic Sample Acquisition Location - Latitude Minute Value (LTM)
Description:
This information item is latitude minute value (LTM). This is a value that specifies a minute of a degree. The value shall be
between 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall be empty. Thus, the allowed special character is a
period. The minute value can be empty, even if the degree value is an integer. LTM and LGM are co-conditional, so they shall
both be present if either is present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LTM < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture/biom:GeographicSampleAcquisitionLoc
ation/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLatitude
NIEM Element: nc:LatitudeMinuteValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.998_04: Geographic Sample Acquisition Location - Latitude Second Value (LTS)
Description:
The fourth information item is the latitude second value (LTS). This is a value that specifies a second of a minute. The integer
shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
None
Format
n/a
Constraints
0 ≤ LTS < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture/biom:GeographicSampleAcquisitionLoc
ation/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLatitude
NIEM Element: nc:LatitudeSecondValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
995
Type-21: Associated Context
21.998_05: Geographic Sample Acquisition Location - Longitude Degree Value (LGD)
Description:
The fifth information item is the longitude degree value (LGD). It is a value that specifies the degree of a longitude. The value
shall be between -180 (inclusive) and +180 (inclusive). If LTD is present, then LGD shall be present. The degrees may be
expressed as whole numbers (without a decimal) or real numbers including decimals. If decimals are present, then minutes
and seconds are empty. Examples: Buenos Aires, Argentina: -58 (with minutes LGM = 22), NIST, Gaithersburg, Maryland: 77.216032 (no LGM or LGS)
Field Minimum
1
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal, Minus Sign, Plus
Sign
Format
n/a
Constraints
-180 ≤ LGD ≤180
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture/biom:GeographicSampleAcquisitionLoc
ation/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLongitude
NIEM Element: nc:LongitudeDegreeValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.998_06: Geographic Sample Acquisition Location - Longitude Minute Value (LGM)
Description:
The sixth information item is the longitude minute value (LGM). It is a value that specifies a minute of a degree. The value shall
be from 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall not appear. The minute value is empty, even if the
degree value is an integer. If LTM is present, then LGM shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LGM < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture/biom:GeographicSampleAcquisitionLoc
ation/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLongitude
NIEM Element: nc:LongitudeMinuteValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
996
Type-21: Associated Context
21.998_07: Geographic Sample Acquisition Location - Longitude Second Value (LGS)
Description:
The seventh information item is the longitude second value (LGS). This is a value that specifies a second of a minute. The
integer shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer. If LTS is
present, then LGS shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
None
Format
n/a
Constraints
0 ≤ LGS < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture/biom:GeographicSampleAcquisitionLoc
ation/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLongitude
NIEM Element: nc:LongitudeSecondValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.998_08: Geographic Sample Acquisition Location - Elevation (ELE)
Description:
The eighth information item is elevation (ELE). It is expressed in meters. It is a numeric value. It is between -422 meters (Dead
Sea) and 8848 meters (Mount Everest). Allowed special characters are the negative sign and the period.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Minus Sign,Period
Format
n/a
Constraints
-422.000 < ELE < 8848.000;
real number
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture/biom:GeographicSampleAcquisitionLoc
ation/nc:Location3DGeospatialCoordinate
NIEM Element: nc:LocationElevation/nc:MeasureDecimalValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
997
Type-21: Associated Context
21.998_09: Geographic Sample Acquisition Location - Geodetic Datum Code (GDC)
Description:
The ninth information item is the geodetic datum code (GDC11). It is an alphanumeric value of 3 to 6 characters in length. This
information item is used to indicate which coordinate system was used to represent the values in information items 2 through
7. If no entry is made in this information item, then the basis for the values entered in the first eight information items shall be
WGS84, the code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values. If no entry is
made in this information item, then the basis for the values entered in the first eight information items shall be WGS84, the
code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values.
Field Minimum
3
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
See Table 7 Geographic
coordinate datum code
values of the ANSI/NISTITL 1-2011 Update: 2015.
Code List: GEOGRAPHIC COORDINATE DATUM CODE
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture/biom:GeographicSampleAcquisitionLoc
ation/nc:Location3DGeospatialCoordinate
NIEM Element: biom:GeodeticDatumCoordinateSystemCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
998
Type-21: Associated Context
21.998_10: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Zone (GCM)
Description:
It is an alphanumeric value of 2 to 3 characters. This is a one or two digit UTM zone number followed by the 8 degree
latitudinal band designator (which is a single letter).
Field Minimum
2
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
One or two digits followed
by a single letter
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture/biom:GeographicSampleAcquisitionLoc
ation
NIEM Element: nc:Location3DGeospatialCoordinate
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.998_11: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Easting (GCE)
Description:
The eleventh information item is the geographic coordinate universal transverse Mercator easting (GCE). It is an integer of 1 to
6 digits.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture/biom:GeographicSampleAcquisitionLoc
ation
NIEM Element: nc:LocationUTMCoordinateValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
999
Type-21: Associated Context
21.998_12: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Northing (GCN)
Description:
The twelfth information item is the geographic coordinate universal transverse Mercator northing (GCN). It is an integer of 1 to
8 digits.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture/biom:GeographicSampleAcquisitionLoc
ation
NIEM Element: mo:MGRSCoordinateStringText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.998_13: Geographic Sample Acquisition Location - Geographic Reference Text (GRT)
Description:
It is a free form text describing a street address or other physical location (such as ‘Corner of Washington and Madison,
Geneva, NY’).
Field Minimum
1
Field Maximum
150
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture/biom:GeographicSampleAcquisitionLoc
ation
NIEM Element: nc:LocationDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1000
Type-21: Associated Context
21.998_14: Geographic Sample Acquisition Location - Geographic Coordinate Other System Identifier (OSI)
Description:
A fourteenth optional information item geographic coordinate other system identifier (OSI) allows for other coordinate systems.
This information items specifies the system identifier. It is up to 10 characters in length. Examples are: • MGRS (Militar Grid
Reference System), • USNG (United States National Grid), • GARS (Global Area Reference System), • GEOREF (World
Geographic Reference), • LANDMARK landmark (e.g. hydant) and position relative to the landmark.
Field Minimum
1
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture/biom:GeographicSampleAcquisitionLoc
ation
NIEM Element: biom:GeographicLocationSystemName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
21.998_15: Geographic Sample Acquisition Location - Geographic Coordinate Other System Value (OCV)
Description:
A fifteenth optional information item, is the geographic coordinate other system value (OCV). It shall only be present if OSI is
present in the record. It can be up to 126 characters in length. If OSI is LANDMARK, OCV is free text and may be up to 126
characters. For details on the formatting of OCV for the other coordinate systems shown in OSI as examples, see http://earthinfo.nga.mil/GandG/coordsys/grids/referencesys.html .
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageAssociatedContextRecord/biom:ContextMediaDetail/biom:BiometricCapture/biom:GeographicSampleAcquisitionLoc
ation
NIEM Element: biom:GeographicLocationText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1001
Type-21: Associated Context
21.999: Associated Context Data (DATA)
Description:
If this field is used, Field 21.994: External file reference / EFR shall not be set. However, one of the two fields shall be present
in all instances of this record type. It is mandatory for a 2D still image. See Section 7.2 of ANSI/NIST ITL 1-2011 for details.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
B
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageAssociatedContextRecord
NIEM Element: nc:Base64BinaryObject
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
98.001: Record Header (LEN)
Description:
The record header appears as the first field (xx.001) in each Record Type. It contains information particular to the encoding
format chosen, in order to enable proper reading of the record. In Traditional encoding, this field contains the record length in
bytes (including all information separators). In NIEM-conformant XML encoding, this field contains the RecordCategoryCode,
which is the numeric representation of the Record Type.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
Encoding Specific
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord
NIEM Element: itl:Transaction
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1002
Type-98: Information Assurance
98.002: Information Designation Character (IDC)
Description:
This mandatory field shall contain the IDC assigned to this Type-98 record as listed in the information item IDC for this record
in Field 1.003: Transaction content / CNT.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤IDC ≤99; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationAssuranceRecord
NIEM Element: biom:ImageReferenceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
98.003: IA Data Format Owner (DFO)
Description:
This mandatory field shall contain a four digit hex value assigned by an authoritative body which denotes the vendor, standards
body, working group, or industry consortium that has defined the format of the information assurance data. The IA data format
owner and Field 98.005: IA data format type / DFT, when used in combination with one another uniquely identify the specific
format of the IA content. This IA data format definition may be published (public) or unpublished (non-public).
Field Minimum
4
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationAssuranceRecord
NIEM Element: biom:AssuranceFormatOwnerID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1003
Type-98: Information Assurance
98.004: Source Agency (SRC)
Description:
This is a mandatory field. This is the identifier of the agency that actually created the record and supplied the information
contained in it. The source agency name may be entered in Field 98.993: Source agency name / SAN.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationAssuranceRecord/biom:AssuranceOrganization
NIEM Element: nc:OrganizationIdentification/nc:IdentificationID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
98.005: IA Data Format Type (DFT)
Description:
This mandatory field shall be used to identify the value assigned by the format owner (DFO) to represent the specific IA data
format as specified by the format owner. This may be a nonstandard, unpublished data format or a data format that has been
standardized by an industry group, consortium, or standards body.
Field Minimum
1
Field Maximum
20
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationAssuranceRecord
NIEM Element: biom:AssuranceFormatDescriptorText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1004
Type-98: Information Assurance
98.006: IA Data Creation Date (DCD)
Description:
This mandatory field shall contain the date and time that IA data was created. The date and time shall appear as GMT format.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
Dependent upon encoding,
nc:DateType
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationAssuranceRecord
NIEM Element: biom:AssuranceUTCDateTime
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
98.900: Audit Log (ALF)
Description:
This optional field contains a series of repeating subfields. One complete audit statement (subfield of ALF) shall be completed
for each modified datum. If this field appears, then Field 98.901 Audit revision number / ARN shall also be in the record.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationAssuranceRecord
NIEM Element: biom:AssuranceLogEntry
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1005
Type-98: Information Assurance
98.900_0: Audit Log - Subfields: Repeating sets of information items (ALF_0)
Description:
Each repeating subfield shall be composed of the following information items: event / EVT is the first information item. It is
mandatory and shall contain textual information describing the event that occurred to the ANSI/NIST-ITL record/field, and shall
be chosen from the following controlled vocabulary: Added, Modified, Deleted, Corrupted. event reason / EVR is the second
information item. It states the rationale behind the Event that occurred. This information item is optional and should be
populated with up to 200 Unicode characters. information identifier / IID is the third information item. It is mandatory and
identifies the field/subfield/information item that has been affected by the Event. It is defined as the concatenation of the IDC, a
comma, the Field Number in the standard, a comma, the repeat count of the subfield (default = NA), a comma, and the
information item mnemonic (if it exists). If a repeating subfield or information item does not exist, enter a “NA”. Examples:
17,10.014,NA,BBC; 3,9.373,4,NA; 8,10.024,2,QVU. For repeating pairs of information items, the repeat count of the
information item may follow the mnemonic. This value is also used to specify an item in a list. This position need not be filled
with NA if it is not relevant. Third repeating pair example for the first element of the pair (HPO): 5,10.033,1,HPO,3. Example for
the fifteenth item in the list (MARC): 29,12.011,1,MARC,15. Note that for Record Type-1 the IDC value is NA. For the case
when a repeated subfield is removed, the entry for the repeat field number is the original repeat set count, preceded by a
negative; the information item mnemonic is entered as “NA”. When an information item is removed, the mnemonic is preceded
by a negative. When an optional field is removed, the field number is preceded by a minus. Even though subfields and
information items may have been in the field, the field number is followed by “NA,NA” so that the subfields and information
items do not have to be individually listed. 12,10.024,-2,NA; 6,18.016,NA,-AL3; 5,-14.024,NA,NA. If two records of the same
type have the same IDC, then the IDC value can be suffixed by an indicator of the sequence of the affected record with the
transaction. For example, if there were two Type-14 records with the same IDC (indicating that it is the same image – for
instance one RAW and the other losslessly compressed as explained in Section 7.3.1 Information designation character / IDC),
the second one within the transaction sequentially would be referenced as 7-2 for the IDC. A reference of 7 is equivalent to 71. agent / AGT is the fourth information item. It is mandatory and shall contain information describing the entity (Agent)
responsible for the EVT that affected the object identified by the IID. [2015a>] Up to 200 Unicode characters are allowed. old
value / OLD is the fifth information item. It is optional. When used, it shall contain the original value of the location in the
transaction referenced in IID before it was affected by the event (EVT).
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
*
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationAssuranceRecord
NIEM Element: biom:AssuranceLogEntry
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1006
Type-98: Information Assurance
98.900_1: Audit Log - Event (EVT)
Description:
Event / EVT is the first information item. It is mandatory and shall contain textual information describing the event that occurred
to the ANSI/NIST-ITL record/field, and shall be chosen from the following controlled vocabulary: Added, Modified, Deleted,
Corrupted.
Field Minimum
5
Field Maximum
9
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
A
Special Characters
None
Format
n/a
Constraints
EVT = Added, Modified,
Deleted or Corrupted
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationAssuranceRecord/biom:AssuranceLogEntry
NIEM Element: biom:AssuranceLogEventCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
98.900_2: Audit Log - Event Reason (EVR)
Description:
Event reason / EVR is the second information item. It states the rationale behind the Event that occurred. This information item
is optional and should be populated with up to 200 Unicode characters.
Field Minimum
1
Field Maximum
200
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
integer
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationAssuranceRecord/biom:AssuranceLogEntry
NIEM Element: biom:AssuranceLogEventReasonText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1007
Type-98: Information Assurance
98.900_3: Audit Log - Information Identifier (IID)
Description:
Information identifier / IID is the third information item. It is mandatory and identifies the field/subfield/information item that has
been affected by the Event. It is defined as the concatenation of the IDC, a comma, the Field Number in the standard, a
comma, the repeat count of the subfield (default = NA), a comma, and the information item mnemonic (if it exists). If a
repeating subfield or information item does not exist, enter a “NA”. Examples: 17,10.014,NA,BBC; 3,9.373,4,NA;
8,10.024,2,QVU. For repeating pairs of information items, the repeat count of the information item may follow the mnemonic.
This value is also used to specify an item in a list. This position need not be filled with NA if it is not relevant. Third repeating
pair example for the first element of the pair (HPO): 5,10.033,1,HPO,3.Example for the fifteenth item in the list (MARC):
29,12.011,1,MARC,15. Note that for Record Type-1 the IDC value is NA. For the case when a repeated subfield is removed,
the entry for the repeat field number is the original repeat set count, preceded by a negative; the information item mnemonic is
entered as “NA”. When an information item is removed, the mnemonic is preceded by a negative. When an optional field is
removed, the field number is preceded by a minus. Even though subfields and information items may have been in the field,
the field number is followed by “NA,NA” so that the subfields and information items do not have to be individually listed.
12,10.024,-2,NA; 6,18.016,NA,-AL3; 5,-14.024,NA,NA. If two records of the same type have the same IDC, then the IDC value
can be suffixed by an indicator of the sequence of the affected record with the transaction. For example, if there were two Type14 records with the same IDC (indicating that it is the same image – for instance one RAW and the other losslessly
compressed as explained in Section 7.3.1 Information designation character / IDC), the second one within the transaction
sequentially would be referenced as 7-2 for the IDC. A reference of 7 is equivalent to 7-1.
Field Minimum
12
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
ANS
Special Characters
None
Format
n/a
Constraints
Comma-separated values
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationAssuranceRecord/biom:AssuranceLogEntry
NIEM Element: biom:AssuranceLogEventLocationText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1008
Type-98: Information Assurance
98.900_4: Audit Log - Agent (AGT)
Description:
Agent / AGT is the fourth information item. It is mandatory and shall contain information describing the entity (Agent)
responsible for the EVT that affected the object identified by the IID. Up to 200 Unicode characters are allowed.
Field Minimum
1
Field Maximum
200
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationAssuranceRecord/biom:AssuranceLogEntry
NIEM Element: biom:AssuranceLogAgentText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
98.900_5: Audit Log - Old Reference (OLD)
Description:
Old value / OLD is the fifth information item. It is optional. When used, it shall contain the original value of the location in the
transaction referenced in IID before it was affected by the event (EVT).
Field Minimum
Dependent upon the format
of IID
Field Maximum
Value of datum prior to
EVT referenced by IID
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
Dependent upon the format
of IID
Special Characters
None
Format
n/a
Constraints
Dependent upon the format
of IID
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationAssuranceRecord/biom:AssuranceLogEntry
NIEM Element: biom:AssuranceLogEventOriginalValueText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1009
Type-98: Information Assurance
98.901: Audit Log - Audit Revision Number (ARN)
Description:
This field is mandatory if Field 98.900: Audit log / ALF appears in the record. It contains a unique reference to the revision
within the revision history. It is numeric, with up to 3 digits. Revision “x” may contain multiple events, each of which is recorded
as a discrete modification (requiring a separate subfield in ARN). Thus, a different revision, with its corresponding log of
modifications (recorded in ARN) requires a separate instance of Record Type-98.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ARN ≤999; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationAssuranceRecord
NIEM Element: biom:AssuranceAuditRevisionID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
98.993: Source Agency Name (SAN)
Description:
This is an optional field. It may contain up to 125 Unicode characters. It is the name of the agency referenced in Field 98.004.
Field Minimum
1
Field Maximum
125
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationAssuranceRecord/biom:AssuranceOrganization
NIEM Element: nc:OrganizationName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1010
Type-99: CBEFF Biometric Data
99.001: Record Header (LEN)
Description:
The record header appears as the first field (xx.001) in each Record Type. It contains information particular to the encoding
format chosen, in order to enable proper reading of the record. In Traditional encoding, this field contains the record length in
bytes (including all information separators). In NIEM-conformant XML encoding, this field contains the RecordCategoryCode,
which is the numeric representation of the Record Type.
Field Minimum
T = 4; X = 1
Field Maximum
T = 8; X = 2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
positive integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageInformationRecord
NIEM Element: itl:Transaction
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.002: Information Designation Character (IDC)
Description:
Each of the records present in a transaction, with the exception of the Type-1 record, shall include a field (xx.002) containing
the information designation character / IDC. The value of the IDC shall be a sequentially assigned positive integer starting
from zero and incremented by one up to a maximum of 99. IDC references are stated in Type-1 Field 1.003 Transaction
content (CNT) and shall be used to relate information items in the CNT field of the Type-1 record to the other records in the
transaction. Two or more records may share a single IDC solely to identify and link together records that pertain to different
representations of the same biometric trait.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ IDC ≤ 99; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord
NIEM Element: biom:ImageReferenceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1011
Type-99: CBEFF Biometric Data
99.004: Source Agency (SRC)
Description:
This is a mandatory field. See Section 7.6 of the ANSI/NIST-ITL 1-2011 Update: 2015 for details. The source agency name
may be entered in Field 21.993: Source agency name / SAN.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail/biom:CaptureOrganization
NIEM Element: nc:OrganizationIdentification/nc:IdentificationID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.005: Biometric Capture Date (BCD)
Description:
This ASCII field shall contain the date and time that the biometric sample was captured. The date and time shall appear as
fifteen digits in the format YYYYMMDDhhmmssZ. The YYYY characters shall represent the year the image was captured; the
MM characters shall be the tens and units values of the month; the DD characters shall be the tens and units values of the day
in the month; the hh characters shall be the tens and units values of the hour of the day in 24-hour format; the mm characters
shall be the tens and units values of the the DD characters shall be the tens and units values of the day in the month; the hh
characters shall be the tens and units values of the hour of the day in 24-hour format; the mm characters shall be the tens and
units values of the minute within the hour; the ss characters shall be the tens and units values of the second of the minute; and
“Z” denotes Coordinated Universal Time, which is abbreviated UTC. For example, December 15, 2000 at 5 AM, 35 minutes
and 30 seconds is expressed as 20001215053530Z. The complete date must be a legitimate date.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
YYYYMMDDhhmmssZ
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail
NIEM Element: biom:CaptureDate/nc:Date
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1012
Type-99: CBEFF Biometric Data
99.100: CBEFF Header Version (HDV)
Description:
This mandatory ASCII field shall be used to identify the version of CBEFF specification to which this record conforms. The
format is two characters for major version number followed by two characters for minor version. The version of CBEFF in
INCITS 398-2005 represented by the string ‘0101’ (major version ‘01’ and minor version ‘01’).
Field Minimum
T = 4, X = 3
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
HDV = 0101
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage
NIEM Element: biom:CBEFFVersionID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.101: Biometric Type (BTY)
Description:
This ASCII field shall be used to identify the type of biometric technology. This mandatory field adopts the values presented in
CBEFF with the addition of two leading zeros for future expansion. Table 127 of the ANSI/NIST-ITL 1-2011 Update: 2015 lists
the current biometric type codes for modalities not covered in this standard with specific Record Types assigned to them.
Field Minimum
T = 8, X = 1
Field Maximum
8
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
Value from Table 127 from
the ANSI/NIST-ITL 1-2011
Update: 2015
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage
NIEM Element: biom:CBEFFCategoryCode
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1013
Type-99: CBEFF Biometric Data
99.102: Biometric Data Quality (BDQ)
Description:
This optional field is used to specify a quality score for the biometric data stored in the BDB in this record. The three
information items identify a quality score and the algorithm used to create the quality score. This information is useful to
enable the recipient of the quality score to differentiate between quality scores generated by different algorithms and adjust for
any differences in processing or analysis as necessary.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage
NIEM Element: biom:ImageQuality
XML Min/Max: 0 / 9
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.102_0: Biometric Data Quality - Subfields: Repeating sets of information items (BDQ_0)
Description:
This optional field is used to specify a quality score for the biometric data stored in the BDB in this record. The three
information items identify a quality score and the algorithm used to create the quality score. This information is useful to
enable the recipient of the quality score to differentiate between quality scores generated by different algorithms and adjust for
any differences in processing or analysis as necessary.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
9
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage
NIEM Element: biom:ImageQuality
XML Min/Max: 0 / 9
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1014
Type-99: CBEFF Biometric Data
99.102_1: Biometric Data Quality - Quality Value (QVU)
Description:
This information item shall contain the integer image quality score between 0 and 100 (inclusive) assigned to the image data
by a quality algorithm. Higher values indicate better quality. An entry of “255” shall indicate a failed attempt to calculate a
quality score. An entry of “254” shall indicate that no attempt to calculate a quality score was made.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
0 ≤ QUV ≤ 100 or QVU =
254 or 255; integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageQuality
NIEM Element: biom:QualityValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.102_2: Biometric Data Quality - Algorithm Vendor Identification (QAV)
Description:
This information item shall specify the ID of the vendor of the quality algorithm used to calculate the quality score. This 4-digit
hex value is assigned by IBIA and expressed as four ASCII characters. The IBIA shall maintain the Vendor Registry of CBEFF
Biometric Organizations that will map the value in this field to a registered organization.
Field Minimum
4
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
0000 ≤ QAV ≤ FFFF
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageQuality
NIEM Element: biom:QualityAlgorithmVendorID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1015
Type-99: CBEFF Biometric Data
99.102_3: Biometric Data Quality - Algorithm Product Identification (QAP)
Description:
This information item shall specify a numeric product code assigned by the vendor of the quality algorithm, which may be
registered with the IBIA, but it is not required to be registered. It indicates which of the vendor’s algorithms was used in the
calculation of the quality score. This field contains the ASCII representation of the integer product code and should be within
the range 1 to 65535.
Field Minimum
1
Field Maximum
5
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ QAP ≤ 65535; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageQuality
NIEM Element: biom:QualityAlgorithmProductID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.103: BDB Format Owner (BFO)
Description:
This mandatory ASCII field shall be used to denote the vendor, standards body, working group, or industry consortium that has
defined the format of the biometric data (in the BDB). In a CBEFF structure the BDB Format Owner and Format Type, when
used in combination, uniquely identify the specific format of the BDB content. The format and content of the BDB is “owned” by
the CBEFF Client (see Section 6.1 of the CBEFF standard). This BDB format definition may be published (public) or
unpublished (non-public). A CBEFF requirement is that format owners register with IBIA for an assigned identifier of the format
owner. The number is guaranteed to be unique. Refer to the CBEFF standard, Section 6, “CBEFF Patrons and Clients,” for
registration information. The four hex digits assigned by IBIA shall be represented by a string of four ASCII characters.
Field Minimum
4
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage
NIEM Element: biom:CBEFFFormatOwnerID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1016
Type-99: CBEFF Biometric Data
99.104: BDB Format Type (BFT)
Description:
This mandatory ASCII field shall be used to identify the value assigned by the format owner to represent the specific BDB
Format as specified by the format owner. This may be a nonstandard, unpublished data format or a data format that has been
standardized by an industry group, consortium, or standards body. The registration of the Format Type value is recommended
but not required. Refer to the CBEFF standard, Section 6, “CBEFF Patrons and Clients,” for registration information. The four
hex digits assigned by the format owner shall be represented by a string of four ASCII characters.
Field Minimum
4
Field Maximum
4
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
H
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage
NIEM Element: biom:CBEFFFormatCategoryID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.902: Annotated Information (ANN)
Description:
This is an optional field, listing the operations performed on the original source in order to prepare it for inclusion in a biometric
record type.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord
NIEM Element: biom:ProcessAnnotation
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1017
Type-99: CBEFF Biometric Data
99.902_0: Annotated Information - Subfields: Repeating sets of information items (ANN_0)
Description:
This is an optional field, listing the operations performed on the original source in order to prepare it for inclusion in a biometric
record type.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
Unlimited
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord
NIEM Element: biom:ProcessAnnotation
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
99.902_1: Annotated Information - Greenwich Mean Time (GMT)
Description:
This information item is the Greenwich Mean Time (GMT) when the processing occured. Some newer record types using this
format refer to the data as UTC. The data is formatted as YYYYMMDDhhmmssZ, where the Z is indicates the zone description
of 0 hours. This time is independent of the actual time zone where the time and date is recorded.
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
YYYYMMDDhhmmssZ for Traditional Encoding
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessUTCDate/nc:DateTime
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1018
Type-99: CBEFF Biometric Data
99.902_2: Annotated Information - Processing Algorithm Name / Version (NAV)
Description:
This information item shall contain text identifying the name and version of the processing algorithm, application, procedure, or
workstation
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
n/a
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessName
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.902_3: Annotated Information - Algorithm Owner (OWN)
Description:
This information item shall contain an unformatted text string of up to 64 characters with the contact information for the
organization that owns the processing algorithm or latent workstation. Where there is no 'algorithm owner,' enter N/A.
Field Minimum
1
Field Maximum
64
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessOwnerText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1019
Type-99: CBEFF Biometric Data
99.902_4: Annotated Information - Process Description (PRO)
Description:
This information item field shall contain text describing a process or procedure applied to the sample in this Type-9 record.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:ProcessAnnotation
NIEM Element: biom:ProcessDescriptionText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.903: Device Unique Identifier (DUI)
Description:
The DUI shall contain a string uniquely identifying the device or source of the data. This field shall be one of the following: a
Host PC MAC address (identified by the first character “M”), or Host PC processor ID (identified by the first character “P”).
Field Minimum
13
Field Maximum
16
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
ANS
Special Characters
Any
Format
n/a
Constraints
First character = M or P
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1020
Type-99: CBEFF Biometric Data
99.904: Make/Model/Serial Number (MMS)
Description:
This is an optional field. The MMS contains the make, model and serial number for the capture device. It shall consist of three
information items. Each information item shall be 1 to 50 characters. Any or all information items may indicate that information
is unknown with the value “0”.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.904_1: Make/Model/Serial Number - Make (MAK)
Description:
The name of the manufacturer for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceMakeText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1021
Type-99: CBEFF Biometric Data
99.904_2: Make/Model/Serial Number - Model (MOD)
Description:
The model number for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceModelText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.904_3: Make/Model/Serial Number - Serial Number (SER)
Description:
The serial number for the capture device.
Field Minimum
1
Field Maximum
50
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail/biom:CaptureDevice
NIEM Element: biom:DeviceSerialNumberText
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1022
Type-99: CBEFF Biometric Data
99.993: Source Agency Name (SAN)
Description:
This is an optional field. It may contain up to 125 Unicode characters. It is the name of the agency referenced in Field xx.004:
Source agency / SRC for record types 9-99.
Field Minimum
1
Field Maximum
125
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail/biom:CaptureOrganization
NIEM Element: nc:OrganizationName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.995: Associated Context (ASC)
Description:
Optional field xx.995 is contained in biometric data sample Record Types 10 and above that may have instances of Record
Type-21 linked to it. Record Type-21 stores images and/or recordings that are not the actual source of the biometric data
contained in another Record Type, but do show the context of the biometric data. An example would be a crime scene
photograph showing the location of a glass that had latent prints on it. However, the close-up image of the latent prints could
appear in a Type-20 record (since that is the image that the individual fingerprint images are derived from), with the segmented
individual images appearing in Type-13 records. This field consists of a maximum of 255 repeating subfields, each of which
contains two information items, as described below. There may be multiple instances of associated context records associated
with a single biometric sample. Figure 2 illustrates relationships of the fields and information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord
NIEM Element: biom:AssociatedContext
XML Min/Max: 0 / 255
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1023
Type-99: CBEFF Biometric Data
99.995_0: Associated Context - Subfields: Repeating sets of information items (ASC_0)
Description:
Optional field xx.995 is contained in biometric data sample Record Types 10 and above that may have instances of Record
Type-21 linked to it. Record Type-21 stores images and/or recordings that are not the actual source of the biometric data
contained in another Record Type, but do show the context of the biometric data. An example would be a crime scene
photograph showing the location of a glass that had latent prints on it. However, the close-up image of the latent prints could
appear in a Type-20 record (since that is the image that the individual fingerprint images are derived from), with the segmented
individual images appearing in Type-13 records. This field consists of a maximum of 255 repeating subfields, each of which
contains two information items, as described below. There may be multiple instances of associated context records associated
with a single biometric sample. Figure 2 illustrates relationships of the fields and information items.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
255
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord
NIEM Element: biom:AssociatedContext
XML Min/Max: 0 / 255
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
DoD EBTS 4.1:
Yes
99.995_1: Associated Context - Associated Context Number (ACN)
Description:
The first information item for the associated context number / ACN for a particular Record Type-21. This is mandatory for each
Field xx.995, when the field is used. It contains an index to a particular instance of a Type-21 record in the transaction. This
same index value appears in the appropriate instance of Record Type-21 as Field 21.021: Associated context number (ACN).
The value of the ACN shall be a sequentially assigned a positive integer starting from one and incremented by one, not to
exceed 255.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
n/a
Format
n/a
Constraints
1 ≤ ACN ≤ 255; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:AssociatedContext
NIEM Element: biom:ContextID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1024
Type-99: CBEFF Biometric Data
99.995_2: Associated Context - Associated Segment Position (ASP)
Description:
The first information item in Field xx.995 is optional. It is the associated segment position / ASP. It contains the index to a
particular set of segmentation coordinates of the associated context data. This same segmentation index value appears in
Record Type-21 as the associated segment position / ASP in Field 21.016: Segments / SEG. There may be up to 99 segments
listed in Field 21.016, but only the relevant segment is contained in Field xx.995.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ ASP ≤ 99; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:AssociatedContext
NIEM Element: biom:ImageSegmentID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.996: Hash (HAS)
Description:
This optional firld shall contain the hash value of the data in Field 99.999: Biometric data block / DATA of this record,
calculated using SHA-256.
Field Minimum
64
Field Maximum
64
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
H
Special Characters
n/a
Format
n/a
Constraints
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord
NIEM Element: biom:ImageHashValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1025
Type-99: CBEFF Biometric Data
99.997: Source Representation (SOR)
Description:
This optional field refers to a representation in Record Type-20 with the same SRN.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord
NIEM Element: biom:SourceInformation
XML Min/Max: 0 / 255
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.997_0: Source Representation - Subfields: Repeating sets of information items (SOR_0)
Description:
This optional field refers to a representation in Record Type-20 with the same SRN from which the data in Field 13.999: Latent
friction ridge image (DATA) was derived.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
1
Occurrence Maximum
255
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord
NIEM Element: biom:SourceInformation
XML Min/Max: 0 / 255
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
No
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1026
Type-99: CBEFF Biometric Data
99.997_1: Source Representation - Source Representation Number (SRN)
Description:
This is the first information item and is mandatory for each Field xx.997. It contains an index to a particular instance of a Type20 record in the transaction. This same index value appears in the appropriate instance of Record Type-20 as Field 20.021:
Source representation number (SRN). The value of the SRN shall be a sequentially assigned a positive integer starting from
one and incremented by one, not to exceed 255.
Field Minimum
1
Field Maximum
3
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ SRN ≤ 255; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:SourceInformation
NIEM Element: biom:SourceID
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.997_2: Source Representation - Reference Segment Position (RSP)
Description:
The first information item is the reference segment position (RSP). This provides a unique index to a segmentation.
Field Minimum
1
Field Maximum
2
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
1 ≤ RSP ≤ 99; positive
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:SourceInformation
NIEM Element: biom:ImageSegmentID
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1027
Type-99: CBEFF Biometric Data
99.998: Geographic Sample Acquisition Location (GEO)
Description:
This optional field contains the location where the biometric sample was acquired – not where it is stored.
Field Minimum
n/a
Field Maximum
n/a
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
n/a
Special Characters
n/a
Format
n/a
Constraints
n/a
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail
NIEM Element: biom:GeographicSampleAcquisitionLocation
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.998_01: Geographic Sample Acquisition Location - Universal Time Entry (UTE)
Description:
The coordinated universal time (UTC) where the biometric sample was collected. This time is independent of the actual time
zone where the time and date is recorded. The date is YYYYMMDDhhmmssZ, where the Z is indicates the zone description of
0 hours. If sample collection time is unknown, set it to "00000000000000Z."
Field Minimum
Encoding Specific
Field Maximum
Encoding Specific
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
YYYYMMDDHHMMSSZ for Traditional Encoding
Constraints
Dependent upon encoding
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLoca
tion
NIEM Element: biom:CaptureUTCDateTime
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1028
Type-99: CBEFF Biometric Data
99.998_02: Geographic Sample Acquisition Location - Latitude Degree Value (LTD)
Description:
The second information item is latitude degree value (LTD). This is a value that specifies the degree of latitude. The value shall
be between -90 (inclusive) and +90 (inclusive). The degrees may be expressed as an integer (without a decimal) or a real
number including decimals. If decimals are present, then minutes and seconds shall be empty. Examples: Buenos Aires,
Argentina: -34 (with minutes LTM = 36) NIST, Gaithersburg, Maryland: 39.137627 (no LTM or LTS)
Field Minimum
1
Field Maximum
9
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal, Minus Sign, Plus
Sign
Format
n/a
Constraints
-90 ≤ LTD ≤ 90
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLoca
tion/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLatitude
NIEM Element: nc:LatitudeDegreeValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.998_03: Geographic Sample Acquisition Location - Latitude Minute Value (LTM)
Description:
This information item is latitude minute value (LTM). This is a value that specifies a minute of a degree. The value shall be
between 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall be empty. Thus, the allowed special character is a
period. The minute value can be empty, even if the degree value is an integer. LTM and LGM are co-conditional, so they shall
both be present if either is present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LTM < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLoca
tion/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLatitude
NIEM Element: nc:LatitudeMinuteValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1029
Type-99: CBEFF Biometric Data
99.998_04: Geographic Sample Acquisition Location - Latitude Second Value (LTS)
Description:
The fourth information item is the latitude second value (LTS). This is a value that specifies a second of a minute. The integer
shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
None
Format
n/a
Constraints
0 ≤ LTS < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLoca
tion/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLatitude
NIEM Element: nc:LatitudeSecondValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.998_05: Geographic Sample Acquisition Location - Longitude Degree Value (LGD)
Description:
The fifth information item is the longitude degree value (LGD). It is a value that specifies the degree of a longitude. The value
shall be between -180 (inclusive) and +180 (inclusive). If LTD is present, then LGD shall be present. The degrees may be
expressed as whole numbers (without a decimal) or real numbers including decimals. If decimals are present, then minutes
and seconds are empty. Examples: Buenos Aires, Argentina: -58 (with minutes LGM = 22), NIST, Gaithersburg, Maryland: 77.216032 (no LGM or LGS)
Field Minimum
1
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal, Minus Sign, Plus
Sign
Format
n/a
Constraints
-180 ≤ LGD ≤ 180
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLoca
tion/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLongitude
NIEM Element: nc:LongitudeDegreeValue
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1030
Type-99: CBEFF Biometric Data
99.998_06: Geographic Sample Acquisition Location - Longitude Minute Value (LGM)
Description:
The sixth information item is the longitude minute value (LGM). It is a value that specifies a minute of a degree. The value shall
be from 0 (inclusive) to 60 (exclusive). The minute value may be expressed as an integer (without a decimal) or as a real
number including decimals. If decimals are present then seconds shall not appear. The minute value is empty, even if the
degree value is an integer. If LTM is present, then LGM shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Decimal
Format
n/a
Constraints
0 ≤ LGM < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLoca
tion/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLongitude
NIEM Element: nc:LongitudeMinuteValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.998_07: Geographic Sample Acquisition Location - Longitude Second Value (LGS)
Description:
The seventh information item is the longitude second value (LGS). This is a value that specifies a second of a minute. The
integer shall be 0 (inclusive) to 60 (exclusive). The second value is empty, even if the minute value is an integer. If LTS is
present, then LGS shall be present.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
None
Format
n/a
Constraints
0 ≤ LGS < 60
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLoca
tion/nc:Location3DGeospatialCoordinate/nc:GeographicCoordinateLongitude
NIEM Element: nc:LongitudeSecondValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1031
Type-99: CBEFF Biometric Data
99.998_08: Geographic Sample Acquisition Location - Elevation (ELE)
Description:
The eighth information item is elevation (ELE). It is expressed in meters. It is a numeric value. It is between -422 meters (Dead
Sea) and 8848 meters (Mount Everest). Allowed special characters are the negative sign and the period.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
NS
Special Characters
Minus Sign,Period
Format
n/a
Constraints
-422.000 ≤ ELE ≤ 8848.000;
real number
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLoca
tion/nc:Location3DGeospatialCoordinate
NIEM Element: nc:LocationElevation/nc:MeasureDecimalValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.998_09: Geographic Sample Acquisition Location - Geodetic Datum Code (GDC)
Description:
The ninth information item is the geodetic datum code (GDC11). It is an alphanumeric value of 3 to 6 characters in length. This
information item is used to indicate which coordinate system was used to represent the values in information items 2 through
7. If no entry is made in this information item, then the basis for the values entered in the first eight information items shall be
WGS84, the code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values. If no entry is
made in this information item, then the basis for the values entered in the first eight information items shall be WGS84, the
code for the World Geodetic Survey 1984 version - WGS 84 (G873). See look up codes for values.
Field Minimum
3
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
see Look Up Codes
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
nc:Location3DGeospatialCoordinateitl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail/bio
m:GeographicSampleAcquisitionLocation/
NIEM Element: biom:GeodeticDatumCoordinateSystemCode
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1032
Type-99: CBEFF Biometric Data
99.998_10: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Zone (GCM)
Description:
It is an alphanumeric value of 2 to 3 characters. This is a one or two digit UTM zone number followed by the 8 degree
latitudinal band designator (which is a single letter).
Field Minimum
2
Field Maximum
3
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
AN
Special Characters
None
Format
n/a
Constraints
One or two digits followed
by a single letter
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/
biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationUTMCoordinateValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.998_11: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Easting (GCE)
Description:
The eleventh information item is the geographic coordinate universal transverse Mercator easting (GCE). It is an integer of 1 to
6 digits.
Field Minimum
1
Field Maximum
6
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/
biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationUTMCoordinateValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1033
Type-99: CBEFF Biometric Data
99.998_12: Geographic Sample Acquisition Location - Geographic Coordinate Universal Transverse
Mercator Northing (GCN)
Description:
The twelfth information item is the geographic coordinate universal transverse Mercator northing (GCN). It is an integer of 1 to
8 digits.
Field Minimum
1
Field Maximum
8
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
N
Special Characters
None
Format
n/a
Constraints
integer
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/
biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLocation
NIEM Element: nc:LocationUTMCoordinateValue
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.998_13: Geographic Sample Acquisition Location - Geographic Reference Text (GRT)
Description:
It is a free form text describing a street address or other physical location (such as ‘Corner of Washington and Madison,
Geneva, NY’).
Field Minimum
1
Field Maximum
150
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLoca
tion
NIEM Element: nc:LocationDescriptionText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1034
Type-99: CBEFF Biometric Data
99.998_14: Geographic Sample Acquisition Location - Geographic Coordinate Other System Identifier (OSI)
Description:
A fourteenth optional information item geographic coordinate other system identifier (OSI) allows for other coordinate systems.
This information items specifies the system identifier. It is up to 10 characters in length. Examples are: • MGRS (Militar Grid
Reference System), • USNG (United States National Grid), • GARS (Global Area Reference System), • GEOREF (World
Geographic Reference), • LANDMARK landmark (e.g. hydant) and position relative to the landmark.
Field Minimum
1
Field Maximum
10
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLoca
tion
NIEM Element: biom:GeographicLocationSystemName
XML Min/Max: 0 / 1
DoD EBTS 1.2:
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
DoD EBTS 4.1:
Yes
99.998_15: Geographic Sample Acquisition Location - Geographic Coordinate Other System Value (OCV)
Description:
A fifteenth optional information item, is the geographic coordinate other system value (OCV). It shall only be present if OSI is
present in the record. It can be up to 126 characters in length. If OSI is LANDMARK, OCV is free text and may be up to 126
characters. For details on the formatting of OCV for the other coordinate systems shown in OSI as examples, see http://earthinfo.nga.mil/GandG/coordsys/grids/referencesys.html .
Field Minimum
1
Field Maximum
126
Occurrence Minimum
0
Occurrence Maximum
1
Character Types
U
Special Characters
Any
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent:
itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage/biom:ImageCaptureDetail/biom:GeographicSampleAcquisitionLoca
tion
NIEM Element: biom:GeographicLocationText
XML Min/Max: 0 / 1
DoD EBTS 1.2:
April 2019
No
DoD EBTS 2.0
No
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
Integrated Data Dictionary (IDD) for DoD EBTS v4.1
1035
Type-99: CBEFF Biometric Data
99.999: Biometric Data Block (DATA)
Description:
This mandatory field contains the CBEFF Biometric Data Block (BDB). See Section 7.2 of ANSI/NIST ITL 1-2011 Update: 2015
for details.
Field Minimum
1
Field Maximum
*
Occurrence Minimum
1
Occurrence Maximum
1
Character Types
B
Special Characters
None
Format
n/a
Constraints
None
Source: ANSI/NIST ITL 1-2011 Update: 2015
Status: Active
XML Parent: itl:PackageCBEFFBiometricDataRecord/biom:CBEFFImage
NIEM Element: nc:Base64BinaryObject
XML Min/Max: 1 / 1
DoD EBTS 1.2:
April 2019
Yes
DoD EBTS 2.0
Yes
DoD EBTS 3.0:
Yes
UNCLASSIFIED - DISTRIBUTION UNLIMITED
DoD EBTS 4.1:
Yes
| File Type | application/pdf |
| Author | Dale, Adam [USA] |
| File Modified | 2024-10-29 |
| File Created | 2019-03-22 |