Default Field Name
Description
Analysis
Additional information, as determined by your institution
Application Code
Unique code to identify the Ethics record
This can be configured to allow the users to enter a value manually or to auto-generate the code. For details, see: User Code Configuration
Application Title *
Mandatory
Name of the ethics application
This can be formatted as required. See: Text editing toolbar
Benefits
Beneficial outcomes from performing the research
Clearance Purpose
Ethics clearance purpose
Closed off Record?
Indicates whether the application is closed
Comments
Any further comments
Complete?
Indicates whether the application has been completed
Conditions of Approval
List of conditions that must be met before the application can be approved
Confidential?
Indicates whether the ethics application is confidential and can only be seen by those with permission to view confidential records
Current?
Yes by default
Indicates if the application is currently active
If the application is no longer active, slide this to No.
Date Applied
Date the application was lodged
Date Approved
Date the application was approved
Date Closed Off
Date the application was closed
Date Reapproved
Date the application was reapproved
Date Rejected
Date the application was rejected
Date Transferred
Date the application was transferred
End Date
Date the research project related to the application finishes/finished
Ethics Category *
Mandatory
Relevant ethics category for the application, from a defined list
The list depends on your Ethics Category Access assigned to your user record.
Experiment Summary
Summary of the research project related to the application
File Reference
File reference number, for example, if a hard copy file exists for the application
Folio Reference
Physical location or folio number, for example, if a hard copy file exists for the application
GMO Dealings Type *
Mandatory if the Ethics Category is for biosafety
Genetically Modified Organism dealings for the application or research
Objective Code
Research objective code, from a defined list
Objective Details
Research objective details
Other Risks
Further details of risks involved
Primary Committee
Read only
Committee marked as Primary Committee for the ethics application in the Committees related item
Primary Contact
Read only
Person marked as the Primary Contact for the application in the Investigators related item
Primary Org. Unit
Read only
Org. unit marked as Primary for the application in the Org. Units related item
Received Date
Date the application was received
Repeated Study?
Indicates if this will be a repeated study
Repeated Study Justification
Details to justify the repeated study
Repeated Use of Subjects?
Indicates if this will repeat the use of subjects
Repeated Use Justification
Details to justify the repeat use of subjects for the research
Research Location
Where the research will be performed
Review Date
Date the application was reviewed
Risks
Description of the known risks involved in performing the research
Special Alternative Technique
Any relevant special, alternative techniques that will be used
Start Date
Date the research project related to the application begins/began
Status
Status of the eForm application, from a defined list
Administrators: This is updated after details in the eForm are pushed to the core record after the Push to Database Tables activity is executed in the workflow
If a core record is created without an eForm application, this may display as Not Specified unless a default is set for the category group (see Source).
Examples: Pending, Submitted for Review, Reviewed, Approved
Version
Indicates a version of the record
If the version is empty, no version of the record exists. If the version is 0, this is the original record based on which the version was created. The record will be non-current if a higher version of the record exists. Only one version of the same record can be current at any time.
To find all versions
of the same project, you may be able to use Advanced search using
the application code, depending on your access permissions. For
more, see: Copy RME records
and versions.