ISO 18618:2018 歯科 — CAD/CAMシステムの相互運用性 | ページ 6

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.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

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

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

3.2.8

FileCatalog

collection of <IDSFile> nodes that describe files associated with the <Case>, <Order> 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 <IdMapItem> 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.

3.2.13

OrderCatalog

collection of <Order> nodes that provide attributes and elements necessary to define or describe an order

Note 1 to entry: An <Order> will often contain one or more <Restoration> 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 <Patient> nodes that provide attributes and elements to define patients that are referenced in the <Order> or <Case> elements

Note 1 to entry: Because patients may be referenced in multiple <Order> nodes and/or multiple <Case> 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 <Cases> 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.

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 <IdMap> section within the <Catalogs> 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 <IdMap> section but each UUID shall be defined only once and used on a single key element.

3.2.23

update

means to send an abbreviated set of data elements to update or modify a previously submitted <Order>

Note 1 to entry: It contains elements that allow the update to match expected values in addition to providing the new values.