-
Notifications
You must be signed in to change notification settings - Fork 242
Attribute Update Policy
Below values and their descriptions indicate the behavior of update policy for attributes already extracted into the DB. These are applicable in following cases :
- On receive of subsequent DICOM objects of existing Series/Study/Patient. Related configuration Attribute Update Policy on respective Attribute Filters for each of the specified Series / Study / Patient Attribute Entity
- On receive of further updates of existing modality worklist items or modality performed procedure steps or unified worklist items. Related configuration Attribute Update Policy on respective Attribute Filters for MWL / MPPS / UPS
- On receive of Link Instances with MWL entry service requests triggered by REST clients or archive UI. Effective on configuration of Link MWL Entry Update Policy.
- On receive of Copy Instances to Study or Move Instances to Study service requests triggered by REST clients or archive UI. Effective on configuration of Copy Move Update Policy.
-
SUPPLEMENT : The attributes will be overwritten. Attributes not present in original dataset will be supplemented. Any extra attributes with not null values will be added.
-
MERGE : The attributes will be overwritten. Attribute values will be written from new dataset. Any attributes with not null values, shall not be overwritten by attributes with null values.
-
OVERWRITE : The attributes will be overwritten. Attribute values if null in new dataset, will be nullified in original dataset. Any attributes with not null values, shall be overwritten by attributes with null values.
-
REPLACE : The attributes will be completely overwritten.
-
PRESERVE : The attributes will be preserved. Nullify attributes in the new dataset which are not present in the original dataset. Any extra attributes will be nullified.
DCM4CHEE 5 Documentation