You can submit eSignature credentials as a binding eSignature if you have Sign role action permission.
If you are an externally authenticated user from iMedidata or another Identity Provider (IDP) who submits eSignature credentials in Rave:
You must enter your iMedidata or IDP credentials when submitting eSignature in Rave.
On submission, iMedidata or IDP authenticates validity of signature and passes the information back to Rave.
If you are an iMedidata user and your eSignature fails after five unsuccessful attempts, your session will end and you will be directed to the iMedidata login page.
If you are an IDP user, the number of failed login attempts is determined by your IDP rules. On an unsuccessful login attempt, your session will end and you will be directed back to your portal.
Note: The new eSig control, Save and Sign button and the signature popup window on the subject grid, subject calendar, and eCRF pages are available to Rave 5.6.4 and above, iMedidata, and IDP users. The eSig field signatures will continue to be available as well. However, iMedidata and IDP users cannot use the subject grid or the the subject calendar to batch sign forms with eSig field signatures.
Navigate to a Study > Site > Subject > A form that requires signature.
Note: To confirm that the data that is captured is accurate, a Rave user will require two items of identification - PIN and User ID, as the first part of the electronic signature. Two parameters - 2 part eSignature Identification Option and Continuous eSignature Time out Interval are assigned in the Configuration module to meet this requirement. If both the identification option and time out interval are set in the Configuration module, the first signing and any subsequent signature later than the time out interval will require both the PIN and the user ID to be entered. If the time out interval is not set, Rave will only require the password to confirm verification for any subsequent signature.
Click Sign and Save.
Enter User Name and Password in the eSignature popup window.
Click Sign and Save.
The form displays the user's full name, user ID, and date. The status of the data points on the form changes to Complete.
Rave updates the following depending on whether you sign a form, folder, or subject:
Signing a subject signs all folders, forms, and data points for the subject that requires signature.
Signing a folder signs all forms and data points within that folder that requires signature.
Signing a form signs all data points on the form that requires signature.
All eSignature activities are captured in the audit trail. Audit will include: User ID, User full name, date and time for each data page, whether you signed using User ID and password or PIN and password or password only.
Note: If a data point changes on a form (including unit changes and derived fields that are marked as "Break signature" in Architect), the signature on that data point requires signature again. The status of the record, page, instance, and subject resets to require signature. On a previously signed page, only changed data points require signature. Similarly, if a form is signed and a log line is inactivated, the page requires signature again.
You can eSign a subject from the subject or grid view pages, sign a folder or form, and/or all folders or forms requiring signature from the grid view page. See Related Topics.
Copyright © 2014 Medidata Solutions, Inc. All rights reserved.