Configuration - Merge Healthcare

Merge DICOM Toolkit Reference Manual
20
Remarks
MC_Add_Private_Attribute adds an attribute that does not exist in the Data
Dictionary (a private attribute) to an existing message. A message can have
private attributes and still conform to DICOM, as long as the attributes are not
equivalent to and do not replace standard attributes. Private attributes are stored
in an odd-number Group (the high-order portion of a DICOM tag). An identifying
PrivateCode must be supplied to differentiate one owner’s block of private
attributes from another in any given Group. Since the attribute is not in the Data
Dictionary, it is necessary to supply the value representation of the attribute’s
values: ValueRep.
Return Value
One of these enumerated MC_STATUS codes define in “mcstatus.h”:
Value Meaning
MC_NORMAL_COMPLETION The function completed normally.
MC_NULL_POINTER_PARM PrivateCode was NULL.
MC_INVALID_MESSAGE_ID MsgFileItemID is not a valid message
object ID, file object ID, or item object
ID.
MC_NOT_FOUND There is no private block identified by
PrivateCode.
MC_INVALID_GROUP Group is not an odd number.
MC_INVALID_VR_CODE ValueRep is invalid.
MC_TAG_ALREADY_EXISTS The private attribute already exists in the
message object.
MC_SYSTEM_ERROR An unexpected, potentially serious,
problem was detected in the operating
environment. A message describing the
error has been written to the Merge
DICOM Toolkit log file.
See Also
MC_Add_Standard_Attribute MC_Delete_Attribute
MC_Add_Private_Attribute MC_Delete_Private_Attribute
MC_Add_Nonstandard_Attribute MC_Delete_Private_Block
MC_Delete_Range