ISO/IEC 19794-14:2022/Amd 1:2025

Information technology — Biometric data interchange formats — Part 14: DNA data — Amendment 1: Conformance requirements

Technologies de l'information — Formats d'échange de données biométriques — Partie 14: Données ADN — Amendement 1: Exigences de conformité

General Information

• Status: Published
• Publication Date: 06-Mar-2025
• ICS: 35.240.15 - Identification cards. Chip cards. Biometrics
• Technical Committee: ISO/IEC JTC 1/SC 37 - Biometrics
• Drafting Committee: ISO/IEC JTC 1/SC 37 - Biometrics
• Current Stage: 6060 - International Standard published
• Start Date: 07-Mar-2025
• Due Date: 07-Mar-2025
• Completion Date: 07-Mar-2025

Relations

• Amends: ISO/IEC 19794-14:2022 - Information technology — Biometric data interchange formats — Part 14: DNA data
• Effective Date: 11-Feb-2023

Standards Content (Sample)

International
Standard
ISO/IEC 19794-14
Second edition
Information technology —
2022-10
Biometric data interchange
formats —
AMENDMENT 1
2025-03
Part 14:
DNA data
AMENDMENT 1: Conformance
requirements
Technologies de l'information — Formats d'échange de données
biométriques —
Partie 14: Données ADN
AMENDEMENT 1: Exigences de conformité
Reference number
ISO/IEC 19794-14:2022/Amd. 1:2025(en) © ISO/IEC 2025

ISO/IEC 19794-14:2022/Amd. 1:2025(en)
© ISO/IEC 2025
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
© ISO/IEC 2025 – All rights reserved
ii
ISO/IEC 19794-14:2022/Amd. 1:2025(en)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical activity.
ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations,
governmental and non-governmental, in liaison with ISO and IEC, also take part in the work.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of document should be noted. This document was drafted in accordance with the editorial rules of the ISO/
IEC Directives, Part 2 (see www.iso.org/directives or www.iec.ch/members_experts/refdocs).
ISO and IEC draw attention to the possibility that the implementation of this document may involve the
use of (a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any
claimed patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had not
received notice of (a) patent(s) which may be required to implement this document. However, implementers
are cautioned that this may not represent the latest information, which may be obtained from the patent
database available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held
responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www.iso.org/iso/foreword.html.
In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 37, Biometrics.
A list of all parts in the ISO/IEC 19794 series can be found on the ISO and IEC websites.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/national-committees.

© ISO/IEC 2025 – All rights reserved
iii
ISO/IEC 19794-14:2022/Amd. 1:2025(en)
Information technology — Biometric data interchange
formats —
Part 14:
DNA data
AMENDMENT 1: Conformance requirements

Clause B.1
Add the following paragraph at the end of the clause:
The Biometric Conformance Test Software (BioCTS) is a freeware developed by the National Institute of
Standards and Technology (NIST) to perform conformance tests for various parts of the ISO/IEC 19794
series. One of the supported International Standards is ISO/IEC 19794-14:2022. The software is available
for download at https:// www .nist .gov/ itl/ csd/ biometrics -resource -center/ biometric -conformance -test
-software -biocts/ biocts -isoiec.

B.2.2
Add the following text at the end of subclause B.2.2:
Within Table B.1, a differentiation between requirements and other provisions is indicated through the use
of the prefixes "R-x" (requirements) and "P-x" (other provisions). Requirements are mandatory provisions,
which are critical for ensuring compliance and are non-negotiable. Other provisions offer options or
permissions rather than mandates, giving users discretion in certain situations.
Table B.1
Replace the table with the following:

© ISO/IEC 2025 – All rights reserved
ISO/IEC 19794-14:2022/Amd. 1:2025(en)

© ISO/IEC 2025 – All rights reserved
Table B.1 — Summary of Level 1 and Level 2 requirements and options
Requirement/ Subclause Requirement/Provision summary Level Status IUT sup- Supported Test
Provision ID reference port range result
R-1 6.1 XML documents encoding DNA data shall validate against the XML sche- 1 M
ma definition in Clause A.1.
P-2 6.3.1 A DNA data XML document (DnaData field) may contain a list of rep- 1 O
resentations (Representations field).
P-3 6.3.1 A DNA data XML document (DnaData field) may contain a list of pedi- 1 O
grees (Pedigrees field).
R-4 6.3.2.2 In an XML document following this document, the version field shall con- 2 M
tain major version 4 and minor revision 0.
R-5 6.3.2.3 When communication direction is “Response”, the transaction field shall 2 M
contain a TransactionProcessingStatus field.
R-6 6.3.2.3 When communication direction is “Response”, the transaction field shall 2 M
contain a TransactionProcessingMessage field.
R-7 6.3.2.3 When communication direction is “Response”, the transaction field shall 2 M
contain a RespondingToRequestId field.
P-8 6.3.2.4 A sending party of the DNA data XML document (SendingParty field) may 1 O
contain an OrganizationCode field.
P-9 6.3.2.4 A sending party of the DNA data XML document (SendingParty field) may 1 O
contain an OrganizationPOCName field.
P-10 6.3.2.4 A category of the sending or receiving party (PartyCategory field) may 1 O
contain a UnitCategory field.
P-11 6.3.2.4 A category of the sending or receiving party (PartyCategory field) may 1 O
contain a UnitLocation field.
P-12 6.3.2.5 A receiving party of the DNA data XML document (ReceivingParty field) 1 O
may contain an OrganizationCode field.
P-13 6.3.2.5 A receiving party of the DNA data XML document (ReceivingParty field) 1 O
may contain an OrganizationPOCName field.
R-14 6.3.3.1 When the communication direction is “Request”, the representation shall 2 M
contain a Request field.
R-15 6.3.3.1 When the communication direction is “Response”, the representation 2 M
shall contain a Response field.
P-16 6.3.3.1 A DNA data representation (Representation field) may contain a CaseUr- 1 O
gencyIndicator field.
P-17 6.3.3.1 A DNA data representation (Representation field) may contain a Supple- 1 O
mentaryMessage field.
ISO/IEC 19794-14:2022/Amd. 1:2025(en)

© ISO/IEC 2025 – All rights reserved
Table B.1 (continued)
Requirement/ Subclause Requirement/Provision summary Level Status IUT sup- Supported Test
Provision ID reference port range result
R-18 6.3.3.2 If RequestCategory is “Other”, then Description shall exist, cannot be null 2 M
or zero-length string, and shall contain text since details shall be includ-
ed in the Description field.
P-19 6.3.3.2 A DNA request (Request field) may contain a UserDefined field. 1 O
P-20 6.3.3.2 A DNA request (Request field) may contain a Description field. 1 O
P-21 6.3.3.2 A user defined request (UserDefined field) may contain a TypeCode field. 1 O
R-22 6.3.3.3 If ResponseCategory is “Other”, then Description shall exist, cannot be 2 M
null or zero-length string, and shall contain text since details shall be
included in the Description field.
R-23 6.3.3.3 If ResponseCategory is “MatchCandidate”, the Response field shall con- 2 M
tain a RespondingToProfileId field.
R-24 6.3.3.3 If the response contains a pedigree, the Pedigrees/ Pedigree/ Response 2 M
field shall contain a RespondingToPedigreeId field. Although the XSD
technically permits RespondingToPedigreeId to appear under DnaData/
Representations/ Representation, this requirement is intended to ensure
that the RespondingToPedigreeId is specifically included in the pedigree
response, rather than in the Representation.
P-25 6.3.3.3 A DNA response (Response field) may contain a UserDefined field. 1 O
P-26 6.3.3.3 A DNA response (Response field) may contain a MatchQuality field. 1 O
P-27 6.3.3.3 A DNA response (Response field) may contain a Description field. 1 O
P-28 6.3.3.4 A DNA profile identification block (DnaProfileIdBlock field) may contain 1 O
a CountryCode field.
P-29 6.3.3.4 A DNA profile identification block (DnaProfileIdBlock field) may contain 1 O
a FederalStateCode field.
P-30 6.3.3.4 A DNA profile identification block (DnaProfileIdBlock field) may contain 1 O
an OrganizationCode field.
R-31 6.3.3.6 If RepresentationCategory is “Other”, then SupplementaryMessage shall 2 M
exist, cannot be null or zero-length string, and shall contain text since
details shall be included in the SupplementaryMessage field.
P-32 6.3.3.7.1 The donor of a DNA data representation (RepresentationDonor field) may 1 O
contain a DonorVitalStatus field.
P-33 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain a DateAndTimeOfA- 1 O
nalysis field.
P-34 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain a BatchId field. 1 O
P-35 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain a KitId field. 1 O

ISO/IEC 19794-14:2022/Amd. 1:2025(en)

© ISO/IEC 2025 – All rights reserved
Table B.1 (continued)
Requirement/ Subclause Requirement/Provision summary Level Status IUT sup- Supported Test
Provision ID reference port range result
P-36 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain an ErrorMessage 1 O
field.
P-37 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain a DnaDataComment 1 O
field.
P-38 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain a SampleCollection- 1 O
Date field.
P-39 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain a SampleCellKind 1 O
field.
P-40 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain a SampleCollection- 1 O
Method field.
P-41 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain a SampleCollection- 1 O
Party field.
P-42 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain a SampleCollection- 1 O
Location field.
P-43 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain a SampleCollec- 1 O
tionGeoLocation field.
P-44 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain a DnaExpertSystem 1 O
field.
P-45 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain a DnaAnalysisParty 1 O
field.
P-46 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain a ProfilePartialIndi- 1 O
cator field.
P-47 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain an InstrumentManu- 1 O
facturer field.
P-48 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain an InstrumentSeri- 1 O
alId field.
P-49 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain an InstrumentSoft- 1 O
wareVersion field.
P-50 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain an InstrumentModel 1 O
field.
P-51 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain a LowTemplateD- 1 O
naIndicator field.
R-52 6.3.3.10.1 When DNA typing technology is “STR”, the DNA data block shall contain a 2 M
LociInformation field.
ISO/IEC 19794-14:2022/Amd. 1:2025(en)

© ISO/IEC 2025 – All rights reserved
Table B.1 (continued)
Requirement/ Subclause Requirement/Provision summary Level Status IUT sup- Supported Test
Provision ID reference port range result
R-53 6.3.3.10.1 When DNA typing technology is “mtDNA”, the DNA data block shall con- 2 M
tain a MitoFragments field.
P-54 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain a DnaFsaList field. 1 O
P-55 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain an Electrophero- 1 O
gram field.
P-56 6.3.3.10.1 A DNA data block (DnaDataBlock field) may contain a VendorSpecificDa- 1 O
taType field.
R-58 6.3.3.10.2 If DnaTypingTechnology is “Other”, then DnaDataComment shall exist, 2 M
cannot be null or zero-length string, and shall contain text since details
shall be included in the DnaDataComment field.
P-59 6.3.3.10.4 The party responsible for a DNA data analysis (DnaAnalysisParty field) 1 O
may contain an OrganizationCode field.
P-60 6.3.3.10.4 The party responsible for a DNA data analysis (DnaAnalysisParty field) 1 O
may contain an OrganizationPOCName field.
R-61 6.3.3.10.7 If LabCertificationValue is “Other”, then DnaDataComment shall exist, 2 M
cannot be null or zero-length string, and shall contain text since details
shall be included in the DnaDataComment field.
R-62 6.3.3.10.7 If ScopeOfAccreditation is “Other”, then DnaDataComment shall exist, 2 M
cannot be null or zero-length string, and shall contain text since details
shall be included in the DnaDataComment field.
R-63 6.3.3.10.11 If SampleCellKind is “Other”, then DnaDataComment shall exist, cannot 2 M
be null or zero-length string, and shall contain text since details shall be
included in the DnaDataComment field.
P-64 6.3.3.10.13 The party responsible for the sample’s collection (SampleCollectionParty 1 O
field) may contain an OrganizationCode field.
P-65 6.3.3.10.13 The party responsible for the sample’s collection (SampleCollectionParty 1 O
field) may contain an OrganizationPOCName field.
R-66 6.3.3.10.18 If InstrumentManufacturer is “Other”, then DnaDataComment shall exist, 2 M
cannot be null or zero-length string, and shall contain text since details
shall be included in the DnaDataComment field.
R-67 6.3.3.10.21 If InstrumentModel is “Other”, then DnaDataComment shall exist, cannot 2 M
be
...