You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

E-Signature 21 Code of Federal Regulation Validity

in Journeys 1 comment

Does anyone have Oracle's official standpoint on their validation process for e-signatures or their confirmation that they are legally valid in all jurisdictions? Essentially we need to confirm the native e-signature documents configured in Journeys (report created in BI) meets 21 Code of Federal Regulation  - part 1: which details the criteria under which electronic records and signatures are considered to be trustworthy and equivalent to paper records.  I know there was a new way to configure the e-signature piece released with 24B (reference attached here) and need to ensure that the previous configuration is still legally valid.

 

In our current configuration, an employee can select "see document" in the Journey task which will download the report generated out of BI and already have their signature, I.P. address, and the date of signature attached 

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!