IRT Logo

School-owned Administrative Systems & Technology

IRT provides systems analysis, design and build services to support the administrative requirements of the School of Medicine. Generally, Administrative Systems & Technology developed by IRT are commissioned by the Dean’s Office and fulfill business requirements that are unique to the School of Medicine or not supported by the central University systems. IRT Administrative Systems also provides business analysis, training, report development and consulting services to SoM. Systems currently under development or support include:

  • MESA2 (Med Student Admissions, Version 2): See more information here.

  • Historical Faculty Appointments and Salary (HFAS): HFAS is a Med School system currently under development. It relies on data from PeopleSoft Faculty Events and HR to replace the SoM mainframe-based application retired in Nov 2003 (see MFASS below) and eliminate dual entry into two systems. Central to the design of this system is a database containing Med School-specific data and reference tables that allow us to link our historical data from MFASS with data from PeopleSoft Faculty Events and HR. Dean’s Office and departmental users will access reports via Brio ReportMart queries that join the two data sources behind the scenes to produce reports containing faculty members’ full appointment and salary history.

Systems being retired this year due to mainframe shutdown

  • MESA1 – Original Med School Admissions system (Spires/Prism). Replaced by MESA2 (see above)
  • MFASS – Med School Faculty Appointment and Salary Setting (Spires-Prism). Replaced by HFAS (see above)
  • Med-SUFED – Med School Space Utilization Database. Replaced by new central University systems including FAMIS Space Management (see above)

Limited support for local departmental systems

In addition, IRT provides limited support for applications developed by individual Dean’s Office units. This support consists of hosting the application in the IRT Data Center and/or programming enhancements that the users cannot do themselves. Examples of these systems include:

  • FMPro BioSciences Admissions (OSA)
  • Paradox SQL Server applications in Office of Student Affairs (OSA)
  • FMPro Med School Course Catalog (OSA)
  • FMPro “Fellowmaker” system (OSA)
  • FMPro Faculty Appointment Tracking system (Faculty Affairs)
  • FMPro “FacultyMaker” system: faculty salary analyses for Provost Office (Finance)