The database schema can contain site-specific custom fields. The system default database schema includes a number of custom fields per database table. These can be remove if unused. Additional fields can be added during first install or any time after.
Some strict rules apply, including
The defined schema, meaning the configuration files defined in this section, must be identical throughout the server hierarchy. Since a server must be in a defined state before these files can be edited, auto-propagation of these files is not possible.
The system must be stopped and all pending operations completed or terminated before editing the schema files.
Some custom database field names, IDs and other settings must be unique across the database, meaning the same value cannot be used by multiple database tables.
Some special features of the custom database schema:
Support for record types. For example, you can create a string, numeric, date and other fields having the properties commonly found for their field types. Most DICOM types are supported, but not all.
Support for multi-field records.
Custom fields are available for coercion, calculated fields and HL7 configuration.
Moving data from one database field to another is supported, but requires eRAD eRAD support assistance to move the data after the required database fields exist.
Database configuration must be performed by a certified system administrator or eRAD eRAD support personnel. Contact your support representative to discuss options for customizing your database.