DICOM PS3.17 2025a - Explanatory Information |
---|
To maintain synchronization between the image repository and other electronic medical record systems, the PACS may support updates to patient, order, and procedure data that correspond to data managed by those other EMR systems. The PACS may also update Series and Instance level information as part of quality control processes. Examples of metadata updates include correction of patient name, change of patient ID, update of procedure descriptions or codes to a standard format, or correction of body part laterality. Such updates are managed by processes outside the scope of the DICOM Standard.
See, for example, the [IHE RAD TF-1] Patient Information Reconciliation (PIR) Integration Profile.
A common PACS implementation stores received SOP Instances to disk in the DICOM File Format, but any metadata updates are retained in its database and not propagated to the stored instances. Applications that use non-DICOM protocols to access the files of stored SOP Instances must therefore also have access to current metadata.
The Inventory SOP Instance provides the current metadata for the stored instances, and the values in the Attributes of the Inventory are considered authoritative. Therefore, the producer of the Inventory should ensure that it is created with current values, and the Item Inventory DateTime (0008,0404) records the time at which those values were extracted from the PACS database and were correct. Note, however, that the values in the Inventory may become outdated due to updates subsequent to Item Inventory DateTime (0008,0404).
An optional additional capability is for the Inventory to record the provenance of metadata updates in the Original Attributes Sequence (0400,0561). While the current correct values are in the Attributes of the Inventoried Studies Sequence (0008,0423), the Original Attributes Sequence (0400,0561) records the prior (replaced) values, the DateTime of the change, and the identity of the modifying system.
In Composite IODs, Attributes of the Study, Series, and Instance levels are all encoded in the top level Data Set. The Original Attributes Sequence is defined in the SOP Common Module, and it aggregates all changes at any level of the information model. However, in the Inventory IOD the Original Attributes Sequence (0400,0561) is defined separately at the Study, Series, and Instance levels, so that it can record updates at the higher levels without needing to replicate into the records for each referenced Instance.
As an example, Table YYYY.7-2c shows what would be a portion of an Inventory SOP Instance for a study where the Patient's Name (0010,0010) was updated based on a master patient index, and one series was updated with a Body Part Examined (0018,0015) that had been missing in the data received from the modality.
When updating the stored SOP Instance with the metadata values from the Inventory, the items of the Original Attributes Sequences at the Study, Series, and Instance levels from the Inventory are added to the items (if any) already in the Original Attributes Sequence of the stored SOP Instance. While there may be duplication, duplicate Items are not an issue for the audit purposes of the Original Attributes Sequence.
DICOM PS3.17 2025a - Explanatory Information |
---|