SIST EN ISO 18618:2025

Dentistry - Interoperability of CAD/CAM systems (ISO 18618:2025)

This document specifies an extensible markup language (XML) format to facilitate the transfer of dental case data and CAD/CAM data between software systems.

Zahnheilkunde - Interoperabilität der CAD/CAM-Systeme (ISO 18618:2025)

Dieses Dokument legt das Format für eine erweiterbare Auszeichnungssprache (XML) fest, um die Übertragung von dentalen Anwendungsdaten und CAD/CAM-Daten zwischen den Softwaresystemen zu erleichtern.

Médecine bucco-dentaire - Interopérabilité des systèmes de CFAO (ISO 18618:2025)

Le présent document spécifie un format de langage de balisage extensible (XML) destiné à faciliter le transfert des données de cas dentaires et des données de CFAO entre les systèmes logiciels.

Zobozdravstvo - Medobratovalnost sistemov CAD/CAM (ISO 18618:2025)

Ta dokument določa obliko razširljivega označevalnega jezika (XML) za lažji prenos zobozdravstvenih podatkov in podatkov CAD/CAM med različnimi sistemi programske opreme.

General Information

• Status: Published
• Public Enquiry End Date: 30-Jul-2024
• Publication Date: 24-Sep-2025
• ICS: 11.060.01 - Dentistry in general
• ICS: 35.240.80 - IT applications in health care technology
• Technical Committee: VAZ - Healthcare
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Sep-2025
• Due Date: 06-Nov-2025
• Completion Date: 25-Sep-2025
• Ref Project: EN ISO 18618:2025 - Dentistry - Interoperability of CAD/CAM systems (ISO 18618:2025)

Relations

• Replaces: SIST EN ISO 18618:2023 - Dentistry - Interoperability of CAD/CAM Systems (ISO 18618:2022)
• Effective Date: 01-Oct-2025

Overview

SIST EN ISO 18618:2025 (ISO 18618:2025) - "Dentistry - Interoperability of CAD/CAM systems" - specifies an XML format and accompanying XML Schema (XSD) to enable reliable transfer of dental case data and CAD/CAM data between software systems. The third edition (2025) updates the IDS (Interface for Dental CAD/CAM Systems) schema and example XML for modern digital dental products (crowns, inlays, implants, orthodontics, dentures, removables). It has been adopted as a European standard (EN ISO 18618:2025).

Key technical topics and requirements

• XML-based data model: Standardized document structure (IDS) for transactions such as submissions, queries, updates and notifications; supports traceability and source identification.
• XML Schema (XSD 1.1): Normative XML schema included (Annex A) and example schemas (Annex B) to validate IDS documents.
• Defined transaction nodes: Elements for originator, provider, broker, DataQuery, DeliveryRequest, CADDataCatalogue, DentistCatalogue, FileCatalogue and extensibility points (ExtraInfo) for proprietary or experimental XML.
• Data security & storage: Requirements and guidance for safeguarding case data and managing storage (see Clause 4).
• Naming & numbering: Rules for consistent naming and the numbering system for teeth and oral areas (ISO 3950 referenced) to ensure unambiguous clinical references.
• Measurement units: Standardized units and formats for dimensional and numerical data (Clause 7).
• Restrictions & validation: Additional constraints on IDS XML documents and validation rules to promote interoperability and prevent ambiguous implementations.
• Normative references: Integration with related standards such as ISO 1942 (vocabulary), ISO 3166-1 (country codes), ISO 16443 (dental implant vocabulary), ISO 18739 (CAD/CAM process chain) and W3C XML/XSD specifications.

Practical applications and who uses this standard

• Dental software developers building practice management, CAD design, CAM milling, and lab management systems to ensure data exchange compatibility.
• Dental laboratories and manufacturers to receive orders and deliver digital designs or finished restorations in a validated, vendor-neutral format.
• Dental clinics and practices to submit cases, receive digital deliveries, and maintain traceability across multiple providers.
• Middleware/broker services that consolidate, route or split orders between originators and providers.
• Integrators and IT architects in healthcare who need to implement secure, standards-based workflows for digital dentistry.
• Regulatory and QA teams referencing the standard for compliance, testing and interoperability certification.

Related standards

• ISO 1942, ISO 3166-1, ISO 3950, ISO 16443, ISO 18739, W3C XML 1.0, W3C XSD 1.1. These provide vocabulary, identification, tooth numbering and XML foundation required for ISO 18618 implementations.

For implementation details and the full normative XML schema, consult the official ISO/CEN national standard documents.

Standards Content (Sample)

SLOVENSKI STANDARD
01-november-2025
Nadomešča:
SIST EN ISO 18618:2023
Zobozdravstvo - Medobratovalnost sistemov CAD/CAM (ISO 18618:2025)
Dentistry - Interoperability of CAD/CAM systems (ISO 18618:2025)
Zahnheilkunde - Interoperabilität der CAD/CAM-Systeme (ISO 18618:2025)
Médecine bucco-dentaire - Interopérabilité des systèmes de CFAO (ISO 18618:2025)
Ta slovenski standard je istoveten z: EN ISO 18618:2025
ICS:
11.060.01 Zobozdravstvo na splošno Dentistry in general
35.240.80 Uporabniške rešitve IT v IT applications in health care
zdravstveni tehniki technology
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EN ISO 18618
EUROPEAN STANDARD
NORME EUROPÉENNE
August 2025
EUROPÄISCHE NORM
ICS 11.060.01 Supersedes EN ISO 18618:2022
English Version
Dentistry - Interoperability of CAD/CAM systems (ISO
18618:2025)
Médecine bucco-dentaire - Interopérabilité des Zahnheilkunde - Interoperabilität der CAD/CAM-
systèmes de CFAO (ISO 18618:2025) Systeme (ISO 18618:2025)
This European Standard was approved by CEN on 3 July 2025.

CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this
European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by
translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management
Centre has the same status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2025 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 18618:2025 E
worldwide for CEN national Members.

Contents Page
European foreword . 3

European foreword
This document (EN ISO 18618:2025) has been prepared by Technical Committee ISO/TC 106
"Dentistry" in collaboration with Technical Committee CEN/TC 55 “Dentistry” the secretariat of which
is held by DIN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by February 2026, and conflicting national standards
shall be withdrawn at the latest by February 2026.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
This document supersedes EN ISO 18618:2022.
Any feedback and questions on this document should be directed to the users’ national standards
body/national committee. A complete listing of these bodies can be found on the CEN website.
According to the CEN-CENELEC Internal Regulations, the national standards organizations of the
following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland,
Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of
North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and the
United Kingdom.
Endorsement notice
The text of ISO 18618:2025 has been approved by CEN as EN ISO 18618:2025 without any modification.

International
Standard
ISO 18618
Third edition
Dentistry — Interoperability of
2025-08
CAD/CAM systems
Médecine bucco-dentaire — Interopérabilité des systèmes de CFAO
Reference number
ISO 18618:2025(en) © ISO 2025
ISO 18618:2025(en)
© ISO 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
ii
ISO 18618:2025(en)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
3.1 General terms .1
3.2 Terms relating to XML content .2
4 Data security and storage methods . 5
5 Naming . 5
6 Numbering system for teeth and areas of the oral cavity . 5
7 Measurement units . 6
8 Additional restrictions on IDS XML documents . 6
9 XSD Description . 6
Annex A (normative) XML schema for IDS . 7
Annex B (informative) Examples of XML schema for IDS . 61
Bibliography .70

iii
ISO 18618:2025(en)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee
has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
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 ISO 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).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes 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 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. ISO 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.
This document was prepared by Technical Committee ISO/TC 106, Dentistry, Subcommittee SC 9, DentalCAD/
CAM systems, in collaboration with the European Committee for Standardization (CEN) Technical Committee
CEN/TC 55, Dentistry, in accordance with the Agreement on technical cooperation between ISO and CEN
(Vienna Agreement).
This third edition cancels and replaces the second edition (ISO 18618:2022), which has been technically
revised.
The main change compared to the previous edition is as follows:
— The XML schema for IDS (interface for dental CAD/CAM systems) examples of interoperability of digital
dental products relating to inlay, onlay, crown, dental implant systems, removables, dental appliances,
orthodontics, and dentures have been updated in Annex A due to the fast nature of the software system
innovation and the need for ongoing testing.
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.

iv
ISO 18618:2025(en)
Introduction
Manufacturers of dental CAD/CAM systems differ in how they exchange manufacturing information and
three-dimensional data. This causes difficulty in data processing, design processes and manufacturing
processes for users of those systems. In order to overcome these interoperability issues, this document has
been prepared to facilitate open interoperability between CAD/CAM systems in dentistry.

v
International Standard ISO 18618:2025(en)
Dentistry — Interoperability of CAD/CAM systems
1 Scope
This document specifies an extensible markup language (XML) format to facilitate the transfer of dental
case data and CAD/CAM data between software systems.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO 1942, Dentistry — Vocabulary
ISO 3166-1, Codes for the representation of names of countries and their subdivisions — Part 1: Country code
ISO 3950, Dentistry — Designation system for teeth and areas of the oral cavity
ISO 16443, Dentistry — Vocabulary for dental implants systems and related procedure
ISO 18739, Dentistry — Vocabulary of process chain for CAD/CAM systems
W3C — Extensible Markup Language (XML) 1.0 (Fifth Edition), November 2008
W3C XML Schema Definition Language (XSD) 1.1, April 2012
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 1942, ISO 16443, ISO 18739, W3C
XML 1.0, W3C XML XSD 1.1 and the following apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1 General terms
3.1.1
broker
entity that acts as a middleman or intermediary
Note 1 to entry: Such entities take multiple orders from multiple sources and consolidate them into a single order for a
provider. Alternatively, they take single orders from an originator and split them among multiple providers. They also
pass orders between originators and providers.

ISO 18618:2025(en)
3.1.2
interface for dental CAD/CAM systems
IDS
nodes immediately within the enveloping root element that provide traceability and source identification
features as well as information on how to reply to a document transaction
Note 1 to entry: The IDS schema organizes the IDS document into structures for specific transactions. The structures
represent a submission, a query, an update of a previous submission, a notification of an event or status change and a
series of catalogues. A single IDS document can contain a combination of different transaction nodes or consist of only
a single transactional node.
3.1.3
originator
entity (organization or person) that is responsible for creating the current document, order or submission
Note 1 to entry: An originator is typically a dental practice. In some cases, an originator is a dental laboratory that is
outsourcing work to another laboratory.
3.1.4
provider
entity that is responsible for supplying the services or products that are being requested in an order
Note 1 to entry: An entity can be a company, a laboratory.
Note 2 to entry: A provider is typically a dental laboratory or manufacturer.
3.2 Terms relating to XML content
3.2.1
brokerID
identifiers used by a broker (3.1.1) to identify itself, or by an originator (3.1.3) and a provider (3.1.4) to
identify a broker
3.2.2
CADDataCatalogue
collection of nodes describing CAD data associated with one or more of either the orders or restorations, or both
Note 1 to entry: A CADDataCatalogue can include either a digital scan or design files, or both.
3.2.3
case
set of one or more orders for dental appliances, products or services, all of which are submitted for a single patient
EXAMPLE A case can contain one order for a crown and another order for a bridge.
3.2.4
catalogue
data that are referenced in other elements or areas
Note 1 to entry: Catalogues are subdivided by the data they group, which makes them easier to manage and reference.
3.2.5
character data
CDATA
certain portion of the document that is a general single character, rather than a non-character or character
with a more specific, limited structure
Note 1 to entry: CDATA is used for distinct, but related, purposes in the markup languages SGML and XML.

ISO 18618:2025(en)
3.2.6
DataQuery
method to request data from another system or entity
Note 1 to entry: DataQuery provides elements to define the data elements to be searched or matched on as well as
elements to define the data requested in response.
3.2.7
DeliveryRequest
information for the out-going, finished order, which is sent to the originator (3.1.3) (or an originator’s agent)
as a separate delivery
Note 1 to entry: A delivery is either physical or electronic, or both.
3.2.8
dentist
node that defines the responsible clinician who requested the order
3.2.9
DentistCatalogue
collection of dentist (3.2.8) nodes that provides attributes and elements to define the dentists being
referenced in the interface for dental CAD/CAM systems (3.1.2) schema
Note 1 to entry: The definition can include billing information and license information.
3.2.10
ExtraInfo
child node that can be used to extend the schema with undefined XML
Note 1 to entry: Many of the elements contain child nodes with the suffix “ExtraInfo” (e.g. ,
). These elements are intended to be areas that can be used to extend the defined schema with
proprietary or undefined XML.
EXAMPLE 1 An implementation can use one (or more) of these elements to embed XML that is only of use to the
implementer for an internal workflow.
EXAMPLE 2 Another use can be two business partners using these elements to experiment with XML they intend to
propose for future versions or to pass proprietary XML they have previously defined between themselves.
Note 2 to entry: The interface dental CAN/CAM system (IDS) (3.1.2) schema and XML schema definition ignore
the contents of these so they are not validated as part of the IDS schema. If these elements are used, it is highly
recommended that any XML be enclosed within some proprietary element tag so that if the XML document passes
through multiple handlers, there are no conflicts. For example:


data specific and of use only to “MyCompany”…


3.2.11
FileCatalogue
collection of nodes that describe files associated with the , or CAD data (scans,
design files, etc.)
3.2.12
host service
system that receives the interface for dental CAD/CAM systems (3.1.2) document and processes the contents

ISO 18618:2025(en)
3.2.13
IDMapCatalogue
collection of nodes which provide a means of defining alternate identifiers for key elements
within the interface for dental CAD/CAM systems (3.1.2)
3.2.14
notification
means for publishing or returning a defined status, event or message related to an order
Note 1 to entry: Within the notification node is an untyped element that can be defined in accordance with the needs
of the parties exchanging information.
3.2.15
order
request for a self-contained dental appliance, service or product that is being requested by an originator
Note 1 to entry: Each order in a case can be created or manufactured by a different provider. Each order contains its
own delivery (or reply) instruction nodes.
3.2.16
OrderCatalogue
collection of nodes that provide attributes and elements necessary to define or describe an order
Note 1 to entry: An often contains one or more nodes but can omit these nodes when not needed.
3.2.17
parcel
physical package that is mailed
3.2.18
patient
node that defines the person for whom a case is being manufactured
Note 1 to entry: Patient information is not a mandatory part of the interface for dental CAD/CAM systems (3.1.2) schema.
3.2.19
PatientCatalogue
collection of nodes that provide attributes and elements to define patients that are referenced in
the or elements
Note 1 to entry: Because patients are referenced in either multiple nodes or multiple nodes, or both,
the patient information is grouped into a catalogue.
3.2.20
prescription
written directive from the dentist or responsible clinician to the supplier specifying the product that should
be manufactured for the patient
3.2.21
ProductCatalogue
means for a provider (3.1.4) or broker (3.1.1) to publish the products that are available for ordering
Note 1 to entry: The node provides attributes and elements to define a product, includes multiple descriptions in
different languages and specifies ordering options and variations.
3.2.22
productSKU
product stocking unit used by manufacturers to identify their products to their internal systems
3.2.23
providerID
identifier used by a broker (3.1.1) and an originator (3.1.3) to identify a provider (3.1.4), or by a provider to
identify itself
ISO 18618:2025(en)
3.2.24
submission
batch or group of one or more described in the interface for dental CAD/CAM systems (IDS) (3.1.2)
document
Note 1 to entry: In traditional (non-digital) dentistry, a submission is equivalent to receiving a physical package [parcel
(3.2.17)] containing one or more cases. In the digital IDS realm, the submission represents any combination of one or
more either physical or digital, or both, cases that are being submitted to a provider for production.
3.2.25
universally unique identifier
UUID
label used for identifying key elements
Note 1 to entry: UUIDs are denoted in the document as string(36) to correspond to the XML schema definition for the
UUIDTypeDef. 128-bit (16 bytes) number represented as a 36-character string of its hexadecimal presentation (32
characters + separators including leading 0 values) in the format: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.
Note 2 to entry: An within the of the document provides a means of equating the UUID with
alternate identifiers that carry external meaning, such as a laboratory management system interface for dental CAD/
CAM systems (IDS) (3.1.2) for a dentist, case or patient.
Note 3 to entry: UUID values can have multiple alternate IDS in the but each UUID is defined only once and
used on a single key element.
EXAMPLE If the UUID “107face6-fc51-4366-805d-2ee23014d835” is assigned to the dentist “Smith”, it is possible
that UUID value is not used on any other element as a key identifier and can only be used as a reference in other
elements needing to associate with that specific dentist.
3.2.26
update
means to send an abbreviated set of data elements to refresh or modify a previously submitted
Note 1 to entry: Update contains elements that allow the update to match expected values in addition to providing the
new values.
4 Data security and storage methods
The internet has proven to be an effective means of communication, yet its vulnerability to interception
raises issues of privacy, authentication and integrity of the communicated message. Therefore, data security
is of utmost importance to users of dental information systems.
Health records are personal and private, so dental practitioners are expected to understand the security
issues associated with data at rest and data in transit.
NOTE This document is not intended to explain security concepts and the risks associated with the maintenance
of data in storage and transit, and over an internet connection. The ADA Standards Committee on Dental Informatics
has published a series of technical reports that provide dental practitioners with guidelines in addressing issues of
security of data in storage and transmission over the internet.
A ZIP file format is recommended for transport of the IDS XML file and related files. However, implementation
of a file container is the responsibility of the implementer.
5 Naming
The file name shall end with a .ids extension. The file name can be prepended with any naming convention
that the user desires.
6 Numbering system for teeth and areas of the oral cavity
In this document, the numbering of teeth and areas of the oral cavity shall be based on ISO 3950.

ISO 18618:2025(en)
7 Measurement units
All units are in millimetres unless otherwise specified.
8 Additional restrictions on IDS XML documents
In addition to the information provided in Clause 3 to Clause 7, a valid IDS document shall also meet the
following requirements:
a) The total size of the document shall not exceed 2 MB.
b) The document shall contain a unique identifier for ProviderIDs.
c) The document shall contain a unique identifier for BrokerIDs.
9 XSD Description
The definition of the elements of the XSD schema provided in Annex A shall be used. A sample XML schema
of IDS is shown in Annex B. The XSD definition document shall be downloaded from: https:// standards .iso
.org/ iso/ 18618/ ed -3/ en/ .

ISO 18618:2025(en)
Annex A
(normative)
XML schema for IDS
A.1 General
This annex provides a description of the IDS schema. The following conventions are used in this annex:
a) An asterisk (*) denotes a required XML node or attribute. Unless marked with an asterisk, all nodes and
attributes are considered optional. Some optional nodes have required attributes, which means that if
the node is present at all, the attributes marked with * are also present.
b) For nodes and attributes of type “String,” the allowed length of the string is unlimited unless the length
is specified [e.g. String(100)].
c) The data type “Datetime UTC” implies a date and time value, as defined in ISO 8601-1.
d) All data types refer to the XML schema data types: string, integer, Boolean, datetime, etc.
A.2 XML schema for IDS root
The detailed information of XML schema for IDS root and subdirectories are given from Table A.1, Table A.2
and Table A.3.
Table A.1 — Description of the root directory of IDS
IDS *
The root node for all IDS documents.
Attribute Data type Description
IDSVersion * String(10) The version identifier of the XML schema of the message.
IDSUUID * String(36) A globally unique identifier for the IDS message.
Table A.2 — Description of the directory of IDS/IDSSource
IDS/IDSSource
An optional node describing the system from which the document originates.
Attribute Data type Description
HostName String(100) The network name of the source host system creating and sending the mes-
sage.
IPAddress String(15) An IPv4 address of the source host system creating and sending the message.
IPAddress6 String(45) An IPv6 address of the source host system creating and sending the message.
MACAddress String(15) A MAC address of the source host system creating and sending the message.
OperatorID String(100) A network user identifier for the user account on the source host system cre-
ating and sending the message.
NetworkDomain String(100) A network name identifier for the domain containing the system sending the
message.
ApplicationName String(100) A value indicating the application (by name) that was used to generate or
originate the IDS message.
SystemName String(100) A value indicating the system (by name) that the IDS document originated in.

ISO 18618:2025(en)
TTabablele A A.22 ((ccoonnttiinnueuedd))
IDS/IDSSource
An optional node describing the system from which the document originates.
Attribute Data type Description
SystemID String(100) A value indicating the originating system by identifier or version.
SubSystemName String A value identifying the name of the subsystem originating the message.
SubSystemID String A value indicating the originating subsystem by identifier or version.
SystemVersion String The software or system version information from the system originating the
message.
Table A.3 — Description of the directory of IDS/IDSReplies/ReplyTo
IDS/IDSReplies/ReplyTo
An element specifying address information used for IDS message responses.
Attribute Data type Description
Address String(200) The text of an address. The address itself can be in one of a variety of for-
mats.
AddressType String(5) An enumerated value identifying the format of the address provided. Ac-
ceptable values are:
—  URL
—  WCF
—  MSMQ
—  IPV4
—  IPV6
—  UNC
A.3 XML schema for IDS request
The detailed information of XML schema for IDS request and subdirectories are given from
Table A.4 to Table A.34.
Table A.4 — Root directory of IDS/Submission
IDS/Submission *
The root node for the submission XML.
Attribute Data type Description
UUID * String(36) A globally unique identifier for this submission. This UUID can change for
each new submission and should be provided by the originator.
DateUTCSubmitted Datetime UTC The date and time that the submission was first submitted to the receiver.
DateUTCReceived Datetime UTC The date and time that the submission was received by the receiver. This
value is populated by the receiver (broker or provider) and should be omit-
ted (or left blank) on new submissions.

ISO 18618:2025(en)
Table A.5 — Description of the directory of IDS/Submission/Originator
IDS/Submission/Originator *
Contains information describing the person or business entity that has created the .
Attribute Data type Description
UUID * String(36) A unique identifier for this element that can be used by reference elsewhere in
the document. It should be defined within the along with
any alternate identifiers from external (non IDS) sources.
Name * String(255) Name of the originator.
BusinessType String(3) A three-character code signifying the originator’s entity type. Valid values are:
—  LAB: laboratory
—  DOC: dentist
—  SRV: broker or intermediary service
—  OTH: other
FacilityID String(50) The originator’s identifier for the facility where this originated.
FacilityUTCOffset Time The UTC offset for this originator facility. This is an [hh]:time value, repre-
sented at the midnight plus/minus the UTC offset. For example, a facility in the
Eastern Time Zone has a value of 00:00:00-05:00.
Table A.6 — Description of the directory of IDS/Submission/Originator/Address
IDS/Submission/Originator/Address
The postal address of the originator.
Attribute Data type Description
Street1 * String(125) Line 1 of the street address.
Street2 String(125) Line 2 of the street address.
City * String(125) The name of the city or town.
State String(64) A two-character state code (in the US) or up to 64 characters for a postal
zone, other region (and sub-region) name, such as province, department,
canton or county area outside the US.
PostalCode String(100) The postal code.
Country * String(3) Three-character country code signifying the originator’s country. The value
shall conform to the specifications on Alpha-3 codes outlined in ISO 3166-1.
Table A.7 — Description of the directory of IDS/Submission/Originator/BillingAddress
IDS/Submission/Originator/BillingAddress
The billing address of the originator.
Attribute Data type Description
Street1 * String(125) Line 1 of the street address.
Street2 String(125) Line 2 of the street address.
City * String(125) The name of the city or town.
State String(64) A two-character state code (in the US) or up to 64 characters for a postal
zone, other region (and sub-region) name, such as province, department,
canton or county area outside the US.
PostalCode String(100) The postal code.
Country * String(3) Three-character country code signifying the originator’s country. The value
shall conform to the specifications on Alpha-3 codes outlined in ISO 3166-1.

ISO 18618:2025(en)
Table A.8 — Description of the directory of IDS/Submission/Originator/Contact
IDS/Submission/Originator/Contact
The originator’s contact information.
Attribute Data type Description
Name String(255) Contact person’s name.
Phone String(255) Contact phone number (business).
Fax String(255) Contact fax number.
MobilePhone String(255) Contact mobile number.
Email String(255) Contact email address.
Table A.9 — Description of the directory of IDS/Submission/Originator/Localization
IDS/Submission/Originator/Localization
The originator’s localization preferences.
Attribute Data type Description
1)
Language String(4) A four-character code for language as defined in ISO 639-4.
DecimalSymbol String(1) The symbol to use for decimals.
DigitGrouping String(1) The character to use for digit grouping.
CurrencyCode String(3) The three-character currency code for the preferred currency as defined
in ISO 4217, e.g. “USD” for US dollar.
CurrencySymbol String(5) The symbol to use for currency values.
Table A.10 — Description of the directory of IDS/Submission/Originator/OriginatorExtraInfo
IDS/Submission/Originator/OriginatorExtraInfo
A node allowing for un-validated XML data to augment the data. This node is a character data (CDATA)
marked block and is not validated by the XML schema. It is recommended that any additional or proprietary data
added to this node be embedded within custom identifying XML tags so that additional data can be added by differ-
ent systems or partners minimizing the risk of breaking the IDS structures.
Table A.11 — Description of the directory of IDS/Submission/Broker
IDS/Submission/Broker *
Information describing the person or business entity that is brokering the .
Attribute Data type Description
UUID String(36) Unique identifier for the broker.
BrokerIDOriginator String(50) The identifier used internally by the originator to refer to the broker.
BrokerIDProvider String(50) The identifier used internally by the provider (assuming there is only
one provider) for the broker.
BrokerIDBroker String(50) The identifier used internally by the broker for itself, if applicable.
Name * String(255) Name of the broker.
BusinessType String(3) A three-character code signifying the broker’s entity type. Valid values
are:
—  LAB: laboratory
—  DOC: dentist
—  SRV: broker or intermediary service
—  OTH: other
FacilityID String(50) The broker’s identifier for the facility where this submission was re-
ceived.
1) Cancelled and replaced by ISO 639:2023.

ISO 18618:2025(en)
TTabablele A A.1111 ((ccoonnttiinnueuedd))
IDS/Submission/Broker *
Information describing the person or business entity that is brokering the .
Attribute Data type Description
FacilityUTCOffset Time The UTC offset for this broker facility. This is an [hh]: time value, repre-
sented at the midnight plus/minus the UTC offset. For example, a facility
in the Eastern Time Zone have a value of 00:00:00-05:00.
SubSystemName String(50) The name of the broker’s sub-system that received this submission.
SubSystemID String(50) The identifier of the broker’s sub-system that received this submission.
Table A.12 — Description of the directory of IDS/Submission/Broker/Address
IDS/Submission/Broker/Address
The postal address of the broker.
Attribute Data type Description
Street1 * String(125) Line 1 of the street address.
Street2 String(125) Line 2 of the street address.
City * String(125) The name of the city or town.
State String(64) A two-character state code (in the US) or up to 64 characters for a postal
zone, other region (and sub-region) name, such as province, department,
canton or county area outside the US.
PostalCode String(100) The postal code.
Country * String(3) Three-character country code signifying the originator’s country. The
value shall conform to the specifications on Alpha-3 codes outlined in
ISO 3166-1.
Table A.13 — Description of the directory of IDS/Submission/Broker/Contact
IDS/Submission/Broker/Contact
The broker’s contact information.
Attribute Data type Description
Name String(255) Contact person’s name.
Phone String(255) Contact phone number (business).
Fax String(255) Contact fax number.
MobilePhone String(255) Contact mobile number.
Email String(255) Contact email address.
Table A.14 — Description of the directory of IDS/Submission/Broker/Localization
IDS/Submission/Broker/Localization
The broker’s localization preferences.
Attribute Data type Description
Language String(4) A four-character code for language as defined in ISO 639-4.
DecimalSymbol String(1) The symbol to use for decimals.
DigitGrouping String(1) The character to use for digit grouping.
CurrencyCode String(3) The three-character currency code for the preferred currency as
defined in ISO 4217, e.g. “USD” for US dollar.
CurrencySymbol String(5) The symbol to use for currency values.

ISO 18618:2025(en)
Table A.15 — Description of the directory of IDS/Submission/Broker/BrokerExtraInfo
IDS/Submission/Broker/BrokerExtraInfo
A node allowing for un-validated XML data to augment the data. This node is a CDATA marked block and is
not validated by the XML schema. It is recommended that any additional or proprietary data added to this node be
embedded within custom identifying XML tags so that additional data can be added by different systems or partners
minimizing the risk of breaking the IDS structures.
Table A.16 — Description of the directory of IDS/Submission/Providers
IDS/Submission/Providers
A node containing a list of sub-nodes. Any provider represented anywhere in this shall
have a node here.
Table A.17 — Description of the directory of IDS/Submission/Providers/Provider
IDS/Submission/Providers/Provider
A node describing a single provider.
Attribute Data type Description
ProviderIDOriginator * String(50) The identifier used by the originator to identify this provider.
ProviderIDProvider String(50) The identifier used by the provider to identify itself.
ProviderIDBroker String(50) The identifier used by the broker to identify this provider.
Name String(255) The name of the provider.
BusinessType String(3) A three-character code designating what type of business the provid-
er is (e.g. LAB). Enumeration choices include:
—  LAB: laboratory
—  DOC: dentist
—  SRV: broker or intermediary service
—  OTH: other
FacilityID String(50) The provider’s identifier for the facility where this submission origi-
nated.
FacilityUTCOffset Time The UTC offset for this provider facility, expressed in h.
SubSystemName String(50) The name of the provider’s sub-system that generated this submis-
sion.
SubSystemID String(50) The identifier of the provider’s sub-system that generated this sub-
mission.
Table A.18 — Description of the directory of IDS/Submission/Providers/Provider/Address
IDS/Submission/Providers/Provider/Address
The provider’s address.
Attribute Data type Description
Street1 * String(125) Line 1 of the street address.
Street2 String(125) Line 2 of the street address.
City * String(125) The name of the city or town.
State String(64) A two-character state code (in the US) or up to 64 characters for a
postal zone, other region (and sub-region) name, such as province,
department, canton or county area outside the US.
PostalCode String(100) The postal code.
Country * String(3) Three-character country code signifying the originator’s country.
The value shall conform to the specifications on Alpha-3 codes
outlined in ISO 3166-1.
ISO 18618:2025(en)
Table A.19 — Description of the directory of IDS/Submission/Providers/provider/Contact
IDS/Submission/Providers/Provider/Contact
The provider’s contact information.
Attribute Data type Description
Name String(255) Contact person’s name.
Phone String(255) Contact phone number.
Fax String(255) Contact fax number.
MobilePhone String(255) Contact mobile number.
Email String(255) Contact email address.
Table A.20 — Description of the directory of IDS/Submission/Providers/Provider/Localization
IDS/Submission/Providers/Provider/Localization
The provider’s localization preferences.
Attribute Data type Description
Language String(4) A four-character code for language as defined in ISO 639-4.
DecimalSymbol String(1) The symbol to use for decimals.
DigitGrouping String(1) The character to use for digit grouping.
CurrencyCode String(3) The three-character currency code for the preferred currency
as defined in ISO 4217, e.g. “USD” for US dollar.
CurrencySymbol String(5) The symbol to use for currency values.
Table A.21 — Description of the directory of IDS/Submission/Products
IDS/Submission/Products
A node containing a list of all the products referenced in any of the nodes of the current . Any
product represented anywhere in this submission shall have a node here.
The products listed here are products that are part of an , not products that are defined in the alogue> which are a publication of products available by a provider.

ISO 18618:2025(en)
Table A.22 — Description of the directory of IDS/Submission/Products/Product
IDS/Submission/Products/Product
A node containing information about a single product to be used in this .
Attribute Data type Description
ProductIDOriginator * String(50) The identifier used internally by the originator for this product.
ProductIDProvider String(50) The identifier used internally by the provider for this product, if
applicable.
ProductIDBroker String(50) The identifier used internally by the broker for this product, if
applicable.
ProductType * String(75) A code designating the type of product. The definitions of valid
values are as follows:
—  FULLCROWN: monolithic restoration;
—  34CROWN: crown with 3/4 coverage of the tooth structure;
—  ABUTMENT: customized implant abutment;
—  ABUTMENTWAXUP: diagnostic waxup over an abutment;
—  ANATOMICALCOPING: coping created by an offset from an
already designed full crown;
—  ANATOMICALPONTIC: pontic created by an offset from an
already designed full pontic;
—  TEMPCROWN: temporary crown;
—  BRIDGE: multi-unit restoration;
—  DIGITALMODEL: model prepared by additive manufacturing
or subtractive manufacturing process;
—  ORTHODONTIC: appliance for orthodontic;
—  DENTALAPPLIANCE: appliance except orthodontic;
—  REMOVABLE: denture, partial denture, customtray;
—  CLASP: clasp engaging a tooth;
—  COPING: substructure of a crown;
—  CROWN: crown composed of more than one component;
—  CROWNPONTIC: pontic
...