The “device” is set of components organized to perform a task rather than a specific physical instance. For simple devices there may be one physical device corresponding to the Data Model device. But for complex equipment there may be many physical parts to one “device”.
The “device” is the collection of physical entities that supports a collection of Application Entities. It is uniquely associated with these entities and vice versa. It is also uniquely associated with the network connections and vice versa. In a simple workstation with one CPU, power connection, and network connection the “device” is the workstation.
An example of a complex device is a server built from a network of multiple computers that have multiple network connections and independent power connections. This would be one device with one application entity and multiple network connections. Servers like this are designed so that individual component computers can be replaced without disturbing operations. The Application Configuration Data Model does not describe any of this internal structure. It describes the network connections and the network visible Application Entities. These complex devices are usually designed for very high availability, but in the unusual event of a system shutdown the “device” corresponds to all the parts that get shut down.
Table H.1-2 Attributes of Device Object
|Device Name||1||A unique name (within the scope of the LDAP database) for this device. It is restricted to legal LDAP names, and not constrained by DICOM AE Title limitations.|
|Description||0..1||Unconstrained text description of the device.|
|Manufacturer||0..1||Should be the same as the value of Manufacturer (0008,0070) in SOP instances created by this device.|
|Manufacturer Model Name||0..1||Should be the same as the value of Manufacturer Model Name (0008,1090) in SOP instances created by this device.|
|Software Version||0..N||Should be the same as the values of Software Versions (0018,1020) in SOP instances created by this device.|
|Station Name||0..1||Should be the same as the value of Station Name (0008,1010) in SOP instances created by this device.|
|Device Serial Number||0..1||Should be the same as the value of Device Serial Number (0018,1000) in SOP instances created by this device.|
|Primary Device Type||0..N||Represents the kind of device and is most applicable for acquisition modalities. Types should be selected from the list of code values (0008,0100) for Context ID 30 in PS3.16 when applicable.|
|Institution Name||0..N||Should be the same as the value of Institution Name (0008,0080) in SOP Instances created by this device.|
|Institution Address||0..N||Should be the same as the value of Institution Address (0008,0081) attribute in SOP Instances created by this device.|
|Institutional Department Name||0..N||Should be the same as the value of Institutional Department Name (0008,1040) in SOP Instances created by this device.|
|Issuer of Patient ID||0..1||Default value for the Issuer of Patient ID (0010,0021) for SOP Instances created by this device. May be overridden by the values received in a worklist or other source.|
|Related Device Reference||0..N||The DNs of related device descriptions outside the DICOM Configuration hierarchy. Can be used to link the DICOM Device object to additional LDAP objects instantiated from other schema and used for separate administrative purposes.|
|Authorized Node Certificate Reference||0..N||The DNs for the certificates of nodes that are authorized to connect to this device. The DNs need not be within the DICOM configuration hierarchy.|
|This Node Certificate Reference||0..N||The DNs of the public certificate(s) for this node. The DNs need not be within the DICOM configuration hierarchy.|
|Vendor Device Data||0..N||Device specific vendor configuration information|
|Installed||1||Boolean to indicate whether this device is presently installed on the network. (This is useful for pre-configuration, mobile vans, and similar situations.)|
The “Authorized Node Certificate Reference” is intended to allow the LDAP server to provide the list of certificates for nodes that are authorized to communicate with this device. These should be the public certificates only. This list need not be complete. Other network peers may be authorized by other mechanisms.
The “This Node Certificate Reference” is intended to allow the LDAP server to provide the certificate(s) for this node. These may also be handled independently of LDAP.
Note: A device may have multiple Primary Device Type entries. It may be a multifunctional device, e.g. combined PET and CT. It may be a cascaded device, e.g. image capture and ultrasound.
Table H.1-3 Child Objects of Device Object
|Network Application Entity||1..N||The application entities available on this device (see Section H.1.1.2)|
|Network Connection||1..N||The network connections for this device (see Section H.1.1.3)|