A.5.3.7 DICOM Instances Transferred

A.5.3.7 DICOM Instances Transferred (Current)
Prev	A.5.3 DICOM Specific Audit Messages	Next

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 DICOM Instances message. The Begin Transferring DICOM Instances message conveys the intent to store SOP Instances, while the DICOM 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: EventIdentification	EventID	M	EV (110104, DCM, "DICOM Instances Transferred")
	EventActionCode	M	Enumerated Value: C (Create) if the receiver did not hold copies of the SOP 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: ActiveParticipant 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: ActiveParticipant 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: ActiveParticipant 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.
Participant Object: ParticipantObjectIdentification Studies being transferred (1..N)	ParticipantObjectTypeCode	M	Shall be: 2 System Object
	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	MC	Required if ParticipantObjectQuery is not present.
	ParticipantObjectQuery	MC	Required if ParticipantObjectName is not present.
	ParticipantObjectDetail	U	Not specialized.
	ParticipantObjectDescription	U	Not specialized.
	SOPClass	MC	See Section A.5.2.
	Accession	U	Not specialized.
	NumberOfInstances	U	Not specialized.
	Instances	U	Not specialized.
	Encrypted	U	Not specialized.
	Anonymized	U	Not specialized.
Participant Object: ParticipantObjectIdentification Patient (1)	ParticipantObjectTypeCode	M	Shall be: 1 Person
	ParticipantObjectTypeCodeRole	M	Shall be: 1 Patient
	ParticipantObjectDataLifeCycle	U	Not specialized.
	ParticipantObjectIDTypeCode	M	Shall be: 2 Patient Number
	ParticipantObjectSensitivity	U	Not specialized.
	ParticipantObjectID	M	The patient ID.
	ParticipantObjectName	M	The patient name.
	ParticipantObjectDetail	U	Not specialized.
	ParticipantObjectDescription	U	Not specialized.

Prev	Up	Next
A.5.3.6 DICOM Instances Accessed	Home	A.5.3.8 DICOM Study Deleted