V2.0
23-May-2023
Page 3 of 14
The form must be completed by the External Reviewer as it includes an attestation. The attestation
indicates they have read and understand Yale University's Information Technology Appropriate Use Policy.
Site Staff who create review sessions should share this policy with their External Reviewers prior to
requesting they complete the User Access Request Form. External Reviewers must attest that they will
complete the role-appropriate eReg training prior to being granted access to the system. External
Reviewers must agree to use eReg only for work-related business, to not share their eReg password with
anyone and to not let anyone use eReg while logged into their account. External Reviewers must also
agree to only share the information obtained within eReg with personnel who have a legitimate work-
related need for the information.
Once an account is created, the External Reviewer will retain access to the system until eReg Support Staff
receives a request to inactivate the External Reviewer’s account or after 200 days of not logging into eReg,
whichever comes first. Should more than 200 days elapse between Review Sessions for an External
Reviewer or if the External Reviewer forgets their password, the account can be reactivated by contacting
eReg Suppo
rt (
eReg.Supp[email protected]u). Site Staff or the External Reviewer may make this request directly.
Should an External Reviewer’s eReg access need to be terminated immediately for any reason, please
contact eReg Support (eReg.Support@yale.edu) for assistance. Site Staff who create the Review Session
can revoke access to regulatory and essential documents and/ or SOPs immediately by deleting the
Review Session. Refer to the Deleting a Review Session section below for more information on how to
delete a Review Session.
Creating a Review Session
On the Review Sessions landing page, click + New Review Session to open the Create Review Session pop-
up window.
In the Create Review Session pop-up window, complete the required fields which are marked with an
asterisk. Please note the Name of the session must be unique. We suggest including the review type and
a protocol identifier for the Name such as ‘Interim Monitoring Visit #[X] for [Protocol Identifier]’, ‘Site
Initiation Visit for [Protocol Identifier] or ‘Sponsor Audit for [Protocol Identifier]’.
A Stop Date for the Review Session is not required; however, we recommend entering a Stop Date so that
the Reviewer(s) does not have continuous access to the regulatory and essential documents for that
protocol and any SOPs included in the Review Session. If both a Start Date and Stop Date are entered for
the Review Session, the dates must be unique. A Review Session cannot be set up to start and stop on the
same day.