EN ISO 18618:2018

SLOVENSKI STANDARD
01-september-2018
Zobozdravstvo - Skladno delovanje sistemov CAD/CAM (ISO 16818:2018)
Dentistry - Interoperability of CAD/CAM-systems (ISO 16818:2018)
Zahnheilkunde - Interoperabilität der CAD/CAM-Systeme (ISO 16818:2018)
Médecine bucco-dentaire - Interopérabilité des systèmes de CFAO (ISO 18618:2018)
Ta slovenski standard je istoveten z: EN ISO 18618:2018
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
June 2018
EUROPÄISCHE NORM
ICS 11.060.01
English Version
Dentistry - Interoperability of CAD/CAM systems (ISO
18618:2018)
Médecine bucco-dentaire - Interopérabilité des Zahnheilkunde - Interoperabilität der CAD/CAM-
systèmes de CFAO (ISO 18618:2018) Systeme (ISO 18618:2018)
This European Standard was approved by CEN on 3 May 2018.

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, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey 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
© 2018 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 18618:2018 E
worldwide for CEN national Members.

Contents Page
European foreword . 3

European foreword
This document (EN ISO 18618:2018) 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 December 2018, and conflicting national standards
shall be withdrawn at the latest by December 2018.
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.
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, Former Yugoslav Republic of Macedonia,
France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta,
Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and the United Kingdom.
Endorsement notice
The text of ISO 18618:2018 has been approved by CEN as EN ISO 18618:2018 without any modification.

INTERNATIONAL ISO
STANDARD 18618
First edition
2018-05
Dentistry — Interoperability of CAD/
CAM systems
Médecine bucco-dentaire — Interopérabilité des systèmes de CFAO
Reference number
ISO 18618:2018(E)
©
ISO 2018
ISO 18618:2018(E)
© ISO 2018
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: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2018 – All rights reserved

ISO 18618:2018(E)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Data security and storage methods . 5
5 Naming . 5
6 Tooth numbering system . 5
7 Measurement units . 5
8 Additional restrictions on IDS XML documents . 6
9 XSD Description . 6
Annex A (normative) XML Schema for IDS . 7
Annex B (informative) Examples .53
Bibliography .64
ISO 18618:2018(E)
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 documents 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).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www .iso .org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on 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 the following
URL: www .iso .org/iso/foreword .html.
This document was prepared by Technical Committee ISO/TC 106, Dentistry, Subcommittee SC 9, CAD/
CAM Systems.
iv © ISO 2018 – All rights reserved

ISO 18618:2018(E)
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.
The International Organization for Standardization (ISO) draws attention to the fact that it is claimed
that compliance with this document may involve the use of a patent.
ISO takes no position concerning the evidence, validity and scope of this patent right.
The holder of this patent right has assured ISO that he/she is willing to negotiate licences under
reasonable and non-discriminatory terms and conditions with applicants throughout the world. In this
respect, the statement of the holder of this patent right is registered with ISO.
This document is based on the open source Universal Dental Exchange (UDX) standard created by the
Open Exchange Dental Interoperability Group (OXDIG). The UDX specification is licensed under the
Open Software License version 3.0. Users who wish to implement this document must obtain an open
source license agreement from the licensor. The licensor will grant a worldwide, royalty-free, non-
exclusive, sublicensable license upon request.
The licensor may be contacted at:
OXDIG LLC
4141 MacArthur Boulevard
Newport Beach, CA 92660 USA
Web: http: //www .oxdig .org
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights other than those identified above. ISO shall not be held responsible for identifying any or
all such patent rights.
INTERNATIONAL STANDARD ISO 18618:2018(E)
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 codes
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
ISO 19429:2015, Dentistry — Designation system for dental implants’ after ‘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, 2012
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 1942, ISO 16443, ISO 18739,
W3C XML1.0, W3C XSD 1.1and the following apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— IEC Electropedia: available at http: //www .electropedia .org/
— ISO Online browsing platform: available at https: //www .iso .org/obp
NOTE 1 Throughout the IDS (interface for dental CAD/CAM systems) schema there are terms that have special
meaning or definition. Understanding the use of these terms is the key to well-defined IDS documents that all
parties can understand universally.
NOTE 2 The IDS schema defines several peer level nodes immediately within the enveloping root
element that organizes the IDS document into structures for specific transactions. They represent a submission,
a query, an update of a previous submission, a notification of an event or status change and a series of catalogs.
A single IDS document can contain a combination of different transaction nodes or consist of only a single
transactional node.
NOTE 3 In addition to the transactional nodes mentioned above, the IDS schema also defines several nodes
that provide traceability and source identification features as well as provide information on how to reply to a
document transaction.
3.1 General terms
ISO 18618:2018(E)
3.1.1
broker
entity that acts as a middleman or intermediary
Note 1 to entry: Such organizations may take multiple orders from multiple sources and consolidate them into
a single order for a Provider or they may take single orders from an originator and split them among multiple
providers or they may just pass orders through between originators and providers.
3.1.2
originator
entity (organization or person) that is responsible for creating the current document, order,
submission, etc.
Note 1 to entry: As such, they are the “originator” of the data being exchanged.
Note 2 to entry: Most often an originator would be a dental practice. In some cases, an originator may be a dental
laboratory that is outsourcing work to another lab.
3.1.3
provider
entity (company, lab, etc.) that is responsible for providing the services or products that are being
requested in an order
Note 1 to entry: Most often, this would be a dental laboratory or manufacturer.
3.2 Terms and definitions relating to XML content
3.2.1
CADDataCatalog
collection of nodes describing CAD data associated with one or more of the orders and/or restorations
Note 1 to entry: It can include digital scan and/or design files, etc.
3.2.2
case
set of one or more orders for dental appliances, products or services, all of which are being submitted
for a single patient
EXAMPLE A case might contain one order for a crown, and another order for a bridge.
3.2.3
catalogs
data that are referenced in other elements or areas
Note 1 to entry: The catalogs are subdivided by the data they are grouping, making it easier to manage and
reference.
3.2.4
DeliveryRequest
information for the out-going, finished order, which will be sent to the originator (or an originator’s
agent) as a separate delivery
Note 1 to entry: A delivery may be physical, electronic, or both.
3.2.5
dentist
dentist or responsible clinician who requested the order
2 © ISO 2018 – All rights reserved

ISO 18618:2018(E)
3.2.6
DentistCatalog
collection of dentist (3.2.5) nodes that provides attribute and elements to define the dentists being
referenced within this document
Note 1 to entry: The definition can include billing information, license information, etc.
3.2.7
ExtraInfo
child node that can be used to extend the schema with undefined XML
EXAMPLE Many of the elements will contain child nodes with the suffix “ExtraInfo” (i.e. ,
, etc. These sections are intended to be areas that can be used to extend the defined schema
with proprietary or undefined XML. For example, an implementation may use one (or more) of these sections to
embed XML that is only of use to the implementer for an internal workflow. Another use could be two business
partners using these sections to experiment with XML they intend to propose for future versions or to pass
proprietary XML they have previously defined between themselves. The IDS schema and XSD will ignore the
contents of these sections so they will not be validated as part of the IDS schema. It is highly recommended that
if these sections are used, that any XML be enclosed within some proprietary element tag so that if the XML
document passes through multiple handlers there are no conflicts:


data specific and of use only to “MyCompany”…


3.2.8
FileCatalog
collection of nodes that describe files associated with the , or CAD data
(scans, design files, etc.)
3.2.9
host service
system that receives the IDS document and processes the contents
3.2.10
IdMapCatalog
collection of nodes which provide a means of defining alternate identifiers for key
elements within the IDS
3.2.11
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 according to the needs of
the parties exchanging information.
3.2.12
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 might be created or manufactured by a different provider. Each order
contains its own delivery (or reply) instruction nodes.
ISO 18618:2018(E)
3.2.13
OrderCatalog
collection of nodes that provide attributes and elements necessary to define or describe an order
Note 1 to entry: An will often contain one or more nodes but may omit those nodes when
not needed.
3.2.14
parcel
physical package that is mailed
3.2.15
patient
patient for whom a case is being manufactured
Note 1 to entry: Patient info is not a mandatory part of the IDS schema.
3.2.16
PatientCatalog
collection of nodes that provide attributes and elements to define patients that are referenced
in the or elements
Note 1 to entry: Because patients may be referenced in multiple nodes and/or multiple nodes the
patient information is grouped into a catalog.
3.2.17
prescription
written directive from the dentist or responsible clinician to the supplier specifying the product that
should be manufactured for the patient
3.2.18
ProductCatalog
means for a provider or broker to publish the products that will be available for ordering
Note 1 to entry: The node provides attribute and elements to define a product, include multiple descriptions in
different languages and specify ordering options and variations.
3.2.19
ProductSKU
product stocking unit used my manufacturers to identify their products to their internal systems
3.2.20
DataQuery
method to request data from another system or entity
Note 1 to entry: It 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.21
submission
batch or group of one or more described in the IDS document
Note 1 to entry: In traditional (non digital) dentistry a submission would be equivalent to receiving a physical
package [parcel (3.2.14)] containing one or more cases. In the digital IDS realm, the submission may represent any
combination of one or more physical and/or digital cases that are being “submitted” to a provider for production.
4 © ISO 2018 – All rights reserved

ISO 18618:2018(E)
3.2.22
UUID
universally unique identifier. It will be denoted in the document as string(36) to correspond to the
xsd 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 1 to entry: UUIDs are a means of identifying key elements within the document.
Note 2 to entry: An section within the section of the document provides a means of equating
the UUID with alternate identifiers that carry external meaning, such as a lab management system ids for a
dentist, case or patient.
Note 3 to entry: UUID values can have multiple alternate ids in the section but each UUID shall be
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”, that
UUID value may not be used on any other element as a key identifier and may only be used as a reference in other
elements needing to associate with that specific dentist.
3.2.23
update
means to send an abbreviated set of data elements to update or modify a previously submitted
Note 1 to entry: It 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.
Because of the personal and private nature of health records, the dental practitioner needs to understand
the security issues associated with “data at rest” and “data in transit.” 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 (American Dental Association) 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 left up to the implementer.
5 Naming
The file name shall end with an .ids extension. The file name can be prepended with any naming
convention that the user desires.
6 Tooth numbering system
Throughout the entire document, the tooth number system shall be based on ISO 3950 for tooth
numbering.
7 Measurement units
All units are in millimetres unless otherwise specified.
ISO 18618:2018(E)
8 Additional restrictions on IDS XML documents
In addition to the schema provided above, a valid IDS document shall also meet the following
requirements.
a) The total length of the document shall not exceed 2 megabytes (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. The XSD definition
document is available by e-mailing standards@ada .org.
6 © ISO 2018 – All rights reserved

ISO 18618:2018(E)
Annex A
(normative)
XML Schema for IDS
A.1 General
NOTE Below is a description of the IDS schema. Please note the following conventions 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. Note that some optional nodes have required attributes,
which means that if the node is present at all, then those 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 DateTime value, stored in ISO 8601.
d) All data types refer to the XML schema data types: string, integer, boolean, dateTime, etc.
A.2 XML schema for IDS root section
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.
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 message.
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 creating 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 gen-
erate or originate the IDS message.
SystemName String(100) A value indicating the system (by name) that the IDS document
originated in.
SystemID String(100) A value indicating the originating system by identifier or version.
ISO 18618:2018(E)
SubSystemName String An identifying name of a 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 origi-
nating the message.
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 may be one of a variety
of formats.
AddressType String(5) An Enumerated value identifying the format of the address pro-
vided. Acceptable values are:
—  URL
—  WCF
—  MSMQ
—  IPV4
—  IPV6
—  UNC
A.3 XML schema for IDS request
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 would
change for each new submission and should be provided by the
Originator.
DateUTCSubmit- DateTime UTC The date and time the Submission was first submitted to the
ted receiver.
DateUTCReceived DateTime UTC The date and time the Submission was actually received by the re-
ceiver. This value will be populated by the receiver (Broker or Pro-
vider) and should be omitted (or left blank) on new submissions.
IDS/Submission/Originator *
Contains information describing the person or business entity that has created the Submission.
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 Catalog> section along with any alternate identifiers from external
(non IDS) sources.
Name * String (255) Name of the Originator.
8 © ISO 2018 – All rights reserved

ISO 18618:2018(E)
BusinessType String (3) A three-character code signifying the Originator’s entity type. Valid
values are as follows:
LAB — Lab
DOC — Dentist
SRV — A Broker or intermediary service
OTH — Other
FacilityId String (50) The Originator’s Id for the facility where this Submission originated.
FacilityUTCOff- Time The UTC Offset for this Originator facility. Note that this is an xs: time
set value, represented at the Midnight plus/minus the UTC Offset. For
example, a Facility in the Eastern time zone would have a value of
00:00:00-05:00.
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 (Zipcode in the US).
Country * String(3) Three-character country code signifying the Originator’s country.
The value should conform to the ISO 3166-1 Alpha-3 standard.
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 (Zipcode in the US).
Country * String(3) Three-character country code signifying the Originator’s country.
The value should conform to the ISO 3166-1 Alpha-3 standard.
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(254) Contact email address.
ISO 18618:2018(E)
IDS/Submission/Originator/Localization
The Originator’s localization preferences.
Attribute Data Type Description
Language String(4) A 4 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 3-character ISO 4217 currency code for the preferred cur-
rency (e.g. “USD” for US. Dollar).
CurrencySymbol String(5) The symbol to use for currency values.
IDS/Submission/Originator/OriginatorExtraInfo
A Node allowing for un-validated XML data to augment the Originator data. This node is a CDATA
marked block and will not be validated by the XML schema. It is suggested that any additional or pro-
prietary data added to this node, be embedded within custom identifying XML tags so that additional
data may be added by different systems or partners minimizing the risk of breaking the IDS structures.
IDS/Submission/Broker *
Contains information describing the person or business entity that is brokering the Submission.
Attribute Data Type Description
UUID String(36) Unique identifier for the broker.
BrokerIdOrigina- String (50) The Id used internally by the Originator to refer to Broker.
tor
BrokerIdProvider String (50) The Id used internally by the Provider (assuming there is only
one Provider) for the Broker.
BrokerIdBroker String (50) The Id 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 as follows:
LAB — Lab
DOC —Dentist
SRV — A Broker or intermediary service
OTH — Other
FacilityId String (50) The Broker’s Id for the facility where this Submission was
received.
FacilityUTCOffset Integer The UTC Offset for this Broker facility. Note that this is an xs:
time value, represented at the Midnight plus/minus the UTC
Offset. For example, a Facility in the Eastern time zone would
have a value of 00:00:00-05:00.
SubSystemName String(50) The name of the Broker’s sub-system that received this sub-
mission.
SubSystemId String(50) The Id of the Broker’s sub-system that received this submission.
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.
10 © ISO 2018 – All rights reserved

ISO 18618:2018(E)
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 (Zipcode in the US).
Country * String(3) Three-character country code signifying the Originator’s
country. The value should conform to the ISO 3166-1 Alpha-3
standard.
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(254) Contact email address.
IDS/Submission/Broker/Localization
The Broker’s localization preferences.
Attribute Data Type Description
Language String(4) A 4-character ISO 639-4 code for the preferred language.
DecimalSymbol String(1) The symbol to use for Decimals.
DigitGrouping String(1) The character to use for digit grouping.
CurrencyCode String (3) The 3-character ISO 4217 currency code for the preferred
currency (e.g. “USD” for US. Dollar).
CurrencySymbol String(5) The symbol to use for currency values.
IDS/Submission/Broker/BrokerExtraInfo
A Node allowing for un-validated XML data to augment the Broker data. This node is a CDATA marked
block and will not be validated by the XML schema. It is suggested that any additional or proprietary
data added to this node, be embedded within custom identifying XML tags so that additional data
may be added by different systems or partners minimizing the risk of breaking the IDS structures.
IDS/Submission/Providers
A node containing a list of Provider sub-nodes. Any Provider represented anywhere in this Submis-
sion shall have a node here.
IDS/Submission/Providers/Provider
A node describing a single Provider.
Attribute Data Type Description
ProviderIdOriginator * String(50) The Id used by the Originator to identify this Provider.
ProviderIdProvider String(50) The Id used by the Provider to identify itself.
ProviderIdBroker String(50) The Id used by the Broker to identify this Provider.
Name String(255) The name of the Provider.
ISO 18618:2018(E)
BusinessType String(3) A three-character code designating what type of business
the Provider is. (Example: LAB).
Enumeration Choices:
LAB — Lab
DOC — Dentist
SRV — A Broker or intermediary service
OTH — Other
FacilityId String (50) The Provider’s Id for the facility where this Submission
originated.
FacilityUTCOffset Integer The UTC Offset (in hours) for this Provider facility.
SubSystemName String(50) The name of the Provider’s sub-system that generated this
submission.
SubSystemId String(50) The Id of the Provider’s sub-system that generated this sub-
mission.
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 char-
acters 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 should conform to the ISO 3166-1
Alpha-3 standard.
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(254) Contact email address.
IDS/Submission/Providers/Provider/Localization
The Provider’s localization preferences.
Attribute Data Type Description
Language String(4) A 4-character ISO 639-4 code for the preferred language.
DecimalSymbol String(1) The symbol to use for Decimals.
12 © ISO 2018 – All rights reserved

ISO 18618:2018(E)
DigitGrouping String(1) The character to use for digit grouping.
CurrencyCode String (3) The 3-character ISO 4217 currency code for the pre-
ferred currency (e.g. “USD” for US. Dollar).
CurrencySymbol String(5) The symbol to use for currency values.
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.
NOTE  The products listed here are products that are part of an and should NOT be con-
fused with products defined in the section which are a publication of products
available by a Provider.
IDS/Submission/Products/Product
A node containing information about a single Product to be used in this Submission.
Attribute Data Type Description
ProductIdOriginator * String (50) The Id used internally by the Originator for this
Product.
ProductIdProvider String (50) The Id used internally by the Provider for this
Product, if applicable.
ProductIdBroker String (50) The Id used internally by the Broker for this
Product, if applicable.
ProductType * String(75) A code designating the type of product. Valid
values are in quotes (“”) definitions follow:
“FULLCROWN” — Monolithic Restoration.
“34CROWN” — Crown with 3/4 Coverage of the
tooth structure
“ABUTMENT” — Custom 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
ISO 18618:2018(E)
“CLASP” — Clasp engaging a tooth
“COPING” — Substructure of a crown
“CROWN” — Crown composed of more than one
component.
“CROWNPONTIC” — Pontic that is a full crown
and a not a substructure.
“INLAY” — Inlay
“ONLAY” — Onlay
“OTHER” — Any other type of restoration not
included in the enumerated list.
“PONTIC” — Substructure for a Pontic used in
a bridge.
“POSTANDCORE” — Post and Core
“TELESCOPECROWN” — Telescopic Crown con-
sisting of multiple subtructures
“VENEER” — Veneer
“WAXUP” — Diagnostic Waxup
ProductDescription String Description of the product.
IDS/Submission/ParcelIn
A node describing the parcel that was sent for this submission item.
Attribute (Element) Data Type Description
CarrierCode * String (50) Code designating the postal carrier used to mail the
submission item. Examples values are as follows:
USPS — US. Postal Service
UPS — United Parcel Service
FEDEX — FedEx
DHL — DHL Express
ONTRAC — OnTrac
OTH — (Other Carrier)
CarrierServiceType String(150) The grade of Carrier service used to send the Parcel (e.g.
“Priority Overnight”).
CarrierTrackingId String(255) The carrier tracking Id of the submission item.
DateUTCMailed DateTime UTC The date and time that the Parcel was sent.
DateUTCExpected DateTime UTC The date and time that the Parcel is expected to arrive
at the provider.
IDS/Submission/Description
A free-form text description of the contents of the parcel.
14 © ISO 2018 – All rights reserved

ISO 18618:2018(E)
IDS/Submission/ParcelIn/Address
A node containing information about the address where the original Parcel was mailed. Note that this
node is optional. If it is not provided, then the Provider’s default address will be assumed.
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 should conform to the ISO 3166-1 Alpha-3
standard.
IDS/Submission/Cases *
An enveloping node containing one or more Case sub-nodes.
IDS/Submission/Cases/Case *
A node describing a single Case in the submission item.
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 section along with any alternate
identifiers from external (non IDS) sources.
CaseDateUTCCreated DateTime UTC The date and time the Case was actually created by the
Provider. This value will be populated by the Provider and
should be omitted (or left blank) on new submissions.
CaseDateUTCSubmit- DateTime UTC The date and time the Case was first submitted to a Provider
ted or Broker.
CaseDateUTCReceived DateTime UTC The date and time the Case was actually received by the
Provider (or Broker).
IDS/Submission/Cases/Case/Patient
A element referencing a patient for this Case.
Attribute Data Type Description
ReferenceID * String(36) A reference ID to a UUID of a patient defined within the tientCatalog> section.
IDS/Submission/Cases/Case/Orders *
A node containing a list of Order sub-nodes for the Case.
IDS/Submission/Cases/Case/Orders/Order *
A node describing a single Order in the submission item.
Attribute Data Type Description
ReferenceID String(36) A reference UUID identifying an within the
section.
SIST EN
...