Research Master ID
SiteNew Features and Bug Fixes (
v1version 1.2.5)
1.
(RMID
/SPARC API) Upgrade to Ruby on Rails 5.1.5In this release, the RMID/SPARC API framework has been updated to use Rails 5.1.5, for maintenance and better performance.
2. (SPARC API) Remove Custom DB connection
The SPARC API previously had its own database, but now pulls data directly from the SPARCRequest production site to improve accuracy.
3. (RMID) Audit Trail Feature
An audit table, with its related features, has been added to the RMID application. The audit trail feature enables tracking of creation, updates, and destroys of records, by both users and the Application Programming Interfaces (APIs).
4. (RMID) Improved Protocol Update Method
Previously there were scenarios where the PI name displayed for protocols associated to a Research Master record were different from the current PI name shown in SPARCRequest, or eIRB. These scenarios were caused by the PI change in different systems not being updated in the RMID back-end. The protocol update method has been since improved to compare every protocol-level field and then determine whether an update to the protocol record is needed.
5. (RMID) Research Master PI Update and Notification According to Verified eIRB Record
When a RMID is used in the eIRB system and the corresponding eIRB record has been in an approved and beyond status, in addition to the titles of the Research Master record, the Primary PI-associated data (Name and netID) are now also updated accordingly.
In addition, the system is now sending automatic emails to the previous PI, creator, as well as the updated PI of the record, to notify users of the PI change when the PI on the research master record is updated according to the eIRB record.
6. (RMID) Admin Message Feature
In the event a RMID administrative user needs to contact the user(s) of a Research Master record, there is now a "Send Notification" button available on each record . With this new feature, admins can now send messages to the creator and PI of the RMID record to their MUSC email addresses directly if desired.
Notification Window for Admin Users
Example Notification Email
7. (RMID) Edit Button Bug Fix
In this release, a potential security issue has been fixed where an admin user could change the property of a disabled "Edit" button on a Research Master record from the browser console and make it editable. This bug has since been fixed, and even admin users are not able to edit a verified record.
8. (RMID) Associated Popup Bug Fix
Previously, when clicking on an existing RMID, a pop-up box did not appear for those that had no associated records. This bug has since been fixed and the pop-up box now appears for all Research Master records (see below for screenshots).
RMID with Associated Protocols
RMID without Associated Protocols
9. (RMID) CoeUs Record Association Display Bug Fix
Previously, when moving the association of a SPARC protocol from using one RMID (i.e RMID#1) to the another RMID (i.e. RMID#200), associated CoeUs record(s) (i.e. MIT Award Number 020045-001) were also removed inadvertently from the displayed association of the original RMID (i.e. RMID 1). The removal of the CoeUs association was not intended and should not have been dissociated from the RMID (i.e. RMID 1). This association bug has since been fixed.
Before Changing RMID in SPARCRequest
After Changing RMID in SPARCRequest
10. (RMID) Automatic Filter Added for Special Characters
To avoid the errors caused by special characters for systems that are not compatible with them (such as Epic) and improve the data consistency, automatic filters have been added for special characters and excessive blanks in the text fields of RMID.
Example Text Fields with Special Characters
After Automatic Filtering
11. (RMID) NetID Information Added to Users Table
In this release, the NetID column has been added to the users table. This column was added to establish ground work in the upcoming releases to condense the Primary PI information from different systems into linked users' records, which will improve the system efficiency. The primary PI on the Research Master record itself has been mapped and linked to the corresponding user, based upon this data structure change.
Copyright © 2017-2018 MUSC Foundation for Research Development) Visual Indicators Added for Associated Protocols from Different Systems
In this release, visual indicators have been added to better represent the association of protocols from different systems to the Research Master record:
- Color legends have been added to indicate whether there are protocols associated, and the different colors represent different systems, blue for SPARCRequest, green for eIRB, and red for COEUS.
- The same color legends are also displayed next to the corresponding protocol types after the user clicks on the RMID record and enters the "Associated Protocols" popup window.
- The "Associated Protocols" popup window now also displays the RMID number associated in the title. (i.e. "RMID: 1")
2. (RMID) Additional eIRB Fields Added in Backend
In this release, the three eIRB dates (Initial eIRB Approval Date, Current eIRB Approval Date, eIRB Expiration Date), besides Pro#, are now pulled into the RMID backend and exposed via the RMID API. These fields were added in order to be shared back to auto-fill SPARCRequest.
3. (RMID) Holding PI Information for Completed eIRB Studies
In this release, use cases have been discussed by RMID stakeholders for when a PI moves to a new institution. The PI move caused issues updating eIRB profiles for studies that were already completed. In this release, logic was added to the eIRB/RMID API, so that PI-related fields (First Name, Last Name, net_id) are not updated for eIRB protocols under "Completed" state. This was done to keep the integrity of user data, since eIRB PI updates the RMID PI, which is linked with MUSC identity management systems and are restricted to MUSC employees (with their musc.edu email and netID).
4. (RMID/eIRB API) Updated eIRB Connection Configuration and Refresh Schedule
The RMID/eIRB API configurations on both the production and staging sites have been updated to coincide with the recently updated eIRB server settings.
With the upgraded eIRB database, it is now possible to get fresh data more frequently without slowing down systems. From this release, the RMID/eIRB API is scheduled to update every hour (7:05, 8:05, etc), in order to shorten the reaction time. By changing the update schedule, the RMID system will better reflect the eIRB updates.
5. (RMID) COEUS Project ID Added to RMID/COEUS API
The project ID field from COEUS (i.e. the UDAK "Project Key") has been added to the RMID/COEUS API to update the RMID backend. This was done as preparation to display this information to frontend users, and auto-fill the (partial) UDAK number in SPARCRequest in the future.
6. (RMID) Improved API Performance and Status Notification Mechanism
To better observe the API status between RMID and other connected systems, the following improvements have been made to the hourly refresh job from RMID to SPARC, eIRB and COEUS systems:
1). Exception handling to capture failures and real-time notification to the development team;
2). Optimization for better efficiency of the protocol association and PI update logic;
3). Start and completion notifications have been added (on the development Slack channel for development team).
7. (RMID) PRISM API Integration and Auto-fill PI Department
The Provost Information System (PRISM) is the database managed by MUSC provost office for all MUSC investigators, and is the record-of-truth system for the PI's main appointment department. In order to pull the department information directly from the source and auto-fill for users who are in that system for more accurate affiliations, we have established the RMID/PRISM API to pull in department information when a PI is searched and chosen for an RMID record.
- When a user creates or edits a Research Master record and chooses a PI from the search results, and that PI exists in PRISM, his/her affiliated department is now auto-filled, and the field become disabled (non-editable).
- When a user creates or edits a Research Master record and fills out the PI, and that PI does not exist in PRISM, the department field is still editable to allow manual entry.
8. (RMID) Storing PRISM Department Information on RMID Users
With the newly established RMID/PRISM API, we are now pulling and storing the department information (if it exists) with the logged-in RMID user through the API, for future reporting purposes. Furthermore, we are working on migrating/cleaning up previously manually entered PI department information in RMID according to PRISM data in the next release.
9. (RMID) Duplicated NetID Bug Fix
There was a previous bug that stored the same NetID for a dozen pairs of users in RMID. This bug has since been fixed.
11. (RMID) Repetitive Auditing Entries Bug Fix
The RMID audit trail was previously recording hundreds of the same entries for the same data row because of flawed logic. In this production, the bug has been fixed.