L_LTDIC_API L_UINT16 L_DicomCreateSignature (hDS, pItem, pszPrivateKeyFile, pszCertificateFile, pszPassword, ppSignatureItem, pszMacTransferSyntax, uMacAlgorithm, pElementsToSign, uCount, uSecurityProfile, uReserved);
Creates a Digital Signature in the Data Set.
A DICOM handle.
Pointer to a DICOMELEMENT structure that specifies an Item of a Sequence of Items in the Data Set. The Digital Signature will be created in this Item. If this parameter is set to NULL, the Digital Signature will be created in the main Data Set.
Character string that contains the name of the file that stores the private key that will be used to encrypt the Message Authentication Code (MAC). The function accepts private keys from files in any of the following formats:
Use the parameter pszPassword to specify the password if the private key is stored encrypted.
Character string that contains the name of the file that stores the digital certificate of the signer. This will be the Certificate of Signer (0400,0115). If more than one digital certificate is stored in the file, the first one will be used. For the last format (PKCS#12), use the parameter pszPassword to specify the password if the digital certificate is stored encrypted. This parameter is ignored for the rest of the formats. The function will fail if the specified private key doesnt match the public key of the digital certificate. The function accepts X.509 digital certificates from files in any of the following formats:
|PEM||(usually .pem, .cer, or .crt)|
|DER||(usually .cer or .crt)|
|PKCS#7 PEM||(usually .pem)|
|PKCS#7 DER||(usually .p7b or .spc)|
|PKCS#12||(usually .pfx or .p12)|
Character string that contains the password to be used if the private key is stored encrypted. The password will also be used for the PKCS#12 digital certificates. Set this parameter to NULL if no password is required.
Pointer to a pointer to a DICOMELEMENT structure. In case of success, *ppSignatureItem is updated with a pointer to the new Digital Signatures Sequence Item that corresponds to the newly created Digital Signature. This parameter can be set to NULL.
Character string that contains the MAC Calculation Transfer Syntax UID (0400,0010). This is the Transfer Syntax in which the Data Elements included in the MAC calculation should be encoded. This parameter can be set to NULL. See the Comments for more details.
Value that specifies the MAC Algorithm (0400,0015). This is the algorithm that should be used to generate the MAC. Possible values are:
|DICOM_MAC_ALGORITHM_RIPEMD160|| Use the RACE Integrity Primitives Evaluation (RIPEMD-160) hash function (recommended).|
|DICOM_MAC_ALGORITHM_SHA1|| Use the Secure Hash Algorithm (SHA-1) hash function.|
|DICOM_MAC_ALGORITHM_MD5|| Use the Message Digest 5 (MD5) hash function.|
Pointer to an array that contains the Tags of the Data Elements to be signed. The number of Tags in the array is given by the parameter uCount. If the Digital Signature is being created in the main Data Set (pItem is NULL), only Data Elements on the root of the Data Set may be referenced by the Tags. Similarly, if the Digital Signature is being created in an Item of a Sequence of Items, only Data Elements under this Item may be referenced by the Tags. This parameter can be set to NULL. See the Comments for more details.
Value that specifies the number of Tags in the array specified by the parameter pElementsToSign.
Value that specifies the Digital Signature Security Profile with which to conform when creating the Digital Signature. Possible values are:
|DICOM_SECURITY_PROFILE_NONE|| Do not conform to any Digital Signature Security Profile.|
|DICOM_SECURITY_PROFILE_BASE_RSA|| Conform to the Base Rivest-Shamir-Adleman (RSA) Digital Signature Profile.|
|DICOM_SECURITY_PROFILE_CREATOR_RSA|| Conform to the Creator RSA Digital Signature Profile.|
|DICOM_SECURITY_PROFILE_AUTHORIZATION_RSA|| Conform to the Authorization RSA Digital Signature Profile.|
See the Comments for more details.
Reserved for future use. This must be set to 0.
|DICOM_SUCCESS||The function was successful.|
|<> DICOM_SUCCESS||An error occurred. Refer to Return Codes.|
A Digital Signature can be created in the main Data Set as well as in an Item of a Sequence of Items. Pass NULL for the parameter pItem if you want to create the Digital Signature in the main Data Set or specify an Item in the Data Set to create the Digital Signature in that Item.
The parameter pszMacTransferSyntax specifies the Transfer Syntax in which the Data Elements included in the Message Authentication Code (MAC) calculation should be encoded. This Transfer Syntax must explicitly include the Value Representation (Explicit VR) and it must use the Little Endian Byte ordering. If the specified Transfer Syntax doesnt fulfill this condition, the function will behave as if the parameter were set to NULL.
If pszMacTransferSyntax is set to NULL, the function will use the Transfer Syntax in which the Data Set is currently encoded if this Transfer Syntax fulfills the condition mentioned in the previous paragraph. If it doesnt, the function will use the Explicit VR Little Endian Transfer Syntax.
You can use the parameters pElementsToSign and uCount to specify the Data Elements to be covered by the new Digital Signature. These Data Elements, which are indicated by their Tags, must be on the root of the Data Set if pItem is set to NULL. If pItem specifies an Item, then they must be located immediately under that Item. Any Tag that doesnt specify an existing Data Element in the expected location will be ignored. Also, any Tag that specifies a Data Element that cannot be signed according to the standard will be ignored as well.
If pElementsToSign is set to NULL, or if uCount is set to 0, the function will sign all the Data Elements that can be signed according to the standard and that exist on the root of the Data Set, if pItem is set to NULL, or immediately under the Item specified by pItem.
Digital Signature Security Profiles put restrictions and add specifications. For example, the Rivest-Shamir-Adleman (RSA) Security Profiles require the use of RSA encryption. Therefore, the function will fail if one of these Security Profiles is used while the specified keys are DSA keys. Another example is that the Creator and Authorization RSA Digital Signature Profiles require that, as a minimum, certain Data Elements must be signed if they exist. Therefore, if one of these Security Profiles is used, the function will sign any existing Data Element that is required, even if this Data Element is not included in the array specified by pElementsToSign.
Required DLLs and Libraries
L_INT DicomCreateSignatureExample(HDICOMDS hDS)
// Create a Digital Signature in the main Data Set
L_UINT16 uRet = L_DicomCreateSignature(hDS,
MAKE_IMAGE_PATH(TEXT("Sample Private Key.pem")),
if (uRet == DICOM_SUCCESS)
MessageBox(NULL, TEXT("The Digital Signature was created successfully."), TEXT("Sample"), MB_OK);
wsprintf(szMsg, TEXT("An error occurred [Error: %hu]."), uRet);
MessageBox(NULL, szMsg, TEXT("Sample"), MB_OK);
// Save the signed Data Set
uRet = L_DicomSaveDS(hDS,MAKE_IMAGE_PATH(TEXT("Signed.dcm")), 0);
if (uRet != DICOM_SUCCESS)
// Examine the Digital Signature we just created
// Refer to the example of L_DicomVerifySignature for the
// function DicomVerifySignatureExample
uRet = (L_UINT16) DicomVerifySignatureExample(hDS, pSignatureItem);