70 likes | 201 Views
Clinical Research Management System (CRMS) IT Overview August 2011. Diana Gumas – Director of Clinical and Clinical Research IT. CRMS Agenda. Current Use Current Features Technology Highlights CRMS Strategic Objectives Q&A. CRMS – Current Use.
E N D
Clinical Research Management System (CRMS) IT Overview August 2011 Diana Gumas – Director of Clinical and Clinical Research IT
CRMS Agenda • Current Use • Current Features • Technology Highlights • CRMS Strategic Objectives • Q&A
CRMS – Current Use • Mandatory for all studies that could result in a patient bill • Usage Statistics Reported Monthly – As of Aug 1, 2011:
Technology Highlights • Developed in partnership with Medical Decision Logics (MDLogix) • Web-based application • Ruby on Rails front end • XSB Expert System for protocol / patient calendar • Microsoft SQL Server database • Hopkins-developed Reporting Server • Hopkins-developed Interfaces • Login via Johns Hopkins enterprise logins or Shibboleth • Servers hosted at Johns Hopkins Data Center • Hopkins IT staffing: 1 project manager and 1 database administrator • Leverage Central IT processes and support groups
CRMS Future Strategic Objectives • Facilitate Use by Affiliates & Clinical Research Network • Improved security for multi-site studies • Interface to new Epic EMR System • Studies & Patients on Study to Epic • Test results for study patients from Epic to CRMS Case Report Forms • Easier ability to see future appointments • Expand interface to eIRB • Expand CRMS’ Utility for the Research Community • Additional Reports • Additional Interfaces • Sponsor billing via MDLogix Financial Module (?)