You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"The DDCC:VS Generation Service...shall generate and sign a DDCC Document"
However, since a DDCC Document's Bundle.signature is not required, any validation using this profile will not check for the existence of a signature, which seems to be an integral part of the Submit Health Event response.
There are clearly reasons why signature cannot be required (i.e. the DDCCDocument cannot have a signature before it is signed). Therefore we propose creating a new DDCCDocumentSigned profile that would allow for the validation of a signed DDCC Document, as is expected by the response of a Submit Health Event transaction.
The text was updated successfully, but these errors were encountered:
According to the Expected Actions of a Submit Health Event transaction:
"The DDCC:VS Generation Service...shall generate and sign a DDCC Document"
However, since a DDCC Document's
Bundle.signature
is not required, any validation using this profile will not check for the existence of a signature, which seems to be an integral part of the Submit Health Event response.There are clearly reasons why signature cannot be required (i.e. the DDCCDocument cannot have a signature before it is signed). Therefore we propose creating a new DDCCDocumentSigned profile that would allow for the validation of a signed DDCC Document, as is expected by the response of a Submit Health Event transaction.
The text was updated successfully, but these errors were encountered: