HPMA User Guide
Table 34: CMS X Database Component Attributes (cont.)Attribute | Type / Units | Description | C | T | Alarm |
|
|
|
|
|
|
| Connections | Count | Number of open database |
|
| N/A |
|
| connections. |
|
|
|
|
|
|
|
|
|
| InnoDB Tablespace |
|
|
|
| |
|
|
|
|
|
|
| Allocated | Bytes | The amount of disk space allo- |
|
| N/A |
| Tablespace |
| cated to the metadata database. |
|
|
|
|
|
|
|
|
|
| Free | Bytes | The amount of space remaining in |
|
| DBSF |
Tablespace |
| the metadata database. |
|
|
|
|
|
|
|
|
|
1 Rates are calculated by tracking the last five events. The elapsed time over all five events is converted into events per second.
DICOM
DICOM is optional This component of the CMS reports on managed DICOM content. on the HPMA.
Table 35: CMS X DICOM Component AttributesAttribute | Type / Units | Description | C | T | Alarm |
|
|
|
|
|
|
| Studies | Count | Total unique DICOM studies |
|
| N/A |
|
| managed by the system. Note that |
|
|
|
|
| duplicates are identified by a full |
|
|
|
|
| match of DICOM study tags. If |
|
|
|
|
| some tags are missing or different, |
|
|
|
|
| the study is considered unique. |
|
|
|
|
| This may lead to a higher number |
|
|
|
|
| than expected. |
|
|
|
|
|
|
|
|
|
| Instances | Count | Total DICOM instances (images) |
|
| N/A |
|
| managed by the system, excluding |
|
|
|
|
| duplicates. |
|
|
|
|
|
|
|
|
|
The Synchronization component provides information on message processing and data transmission dating back to the day the CMS was first started. The Synchronization component is useful for viewing detailed statistics about the rate that data is being processed and sent
98
HP Medical Archive