A.5.3.7 DICOM Instances Transferred

This message describes the event of the completion of transferring DICOM SOP Instances between two Application Entities. This message may only include information about a single patient.

Note: This message may have been preceded by a Begin Transferring Instances message. The Begin Transferring Instances message conveys the intent to store SOP Instances, while the Instances Transferred message records the completion of the transfer. Any disagreement between the two messages might indicate a potential security breach.

Table A.5.3.7-1 Audit Message for DICOM Instances Transferred

Real World Entities Field Name Opt. Value Constraints
Event EventID M EV (110104, DCM, “DICOM Instances Transferred”)
EventActionCode M Enumerated Value: C = (create) if the receiver did not hold copies of the instances transferred R = (read) if the receiver already holds copies of the SOP Instances transferred, and has determined that no changes are needed to the copies held. U = (update) if the receiver is altering its held copies to reconcile differences between the held copies and the received copies. If the Audit Source is either not the receiver, or otherwise does not know whether or not the instances previously were held by the receiving node, then use “R” = (Read).
EventDateTime M Shall be the time when the transfer has completed
EventOutcomeIndicator M not specialized
EventTypeCode U not specialized

Active Participant: Process that sent the data (1) UserID M not specialized
AlternativeUserID U not specialized
UserName U not specialized
UserIsRequestor M not specialized
RoleIDCode M EV (110153, DCM, “Source Role ID”)
NetworkAccessPointTypeCode U not specialized
NetworkAccessPointID U not specialized

Active Participant: The process that received the data. (1) UserID M not specialized
AlternativeUserID U not specialized
UserName U not specialized
UserIsRequestor M not specialized
RoleIDCode M EV (110152, DCM, “Destination Role ID”)
NetworkAccessPointTypeCode U not specialized
NetworkAccessPointID U not specialized
Active Participant: Other participants that are known, especially third parties that are the requestor (0..N) UserID M not specialized
AlternativeUserID U not specialized
UserName U not specialized
UserIsRequestor M not specialized
RoleIDCode U not specialized
NetworkAccessPointTypeCode U not specialized
NetworkAccessPointID U not specialized
Participating Object: Studies being transferred (1..N) ParticipantObjectTypeCode M Shall be: 2 = system
ParticipantObjectTypeCodeRole M Shall be: 3 = report
ParticipantObjectDataLifeCycle U not specialized
ParticipantObjectIDTypeCode M EV (110180, DCM, “Study Instance UID”)
ParticipantObjectSensitivity U not specialized
ParticipantObjectID M The Study Instance UID
ParticipantObjectName U not specialized
ParticipantObjectQuery U not specialized
ParticipantObjectDetail U Not specialized
ParticipantObjectDescription U Not specialized
SOPClass MC See Table A.5.2-1
Accession U not specialized
NumberOfInstances U not specialized
Instances U not specialized
Encrypted U not specialized
Anonymized U not specialized
Participating Object: Patient (1) ParticipantObjectTypeCode M Shall be: 1 = person
ParticipantObjectTypeCodeRole M Shall be: 1 = patient
ParticipantObjectDataLifeCycle U not specialized
ParticipantObjectIDTypeCode M Shall be: 2 = patient ID
ParticipantObjectSensitivity U not specialized
ParticipantObjectID M The patient ID
ParticipantObjectName U The patient name
ParticipantObjectQuery U not specialized
ParticipantObjectDetail U not specialized
ParticipantObjectDescription U not specialized