MD Connect was the next major phase of CurrConn for the Faculty of Medicine, University of Melbourne.

Conceptually MD Connect consisted of Core and Apps. The objective was to have a stable system-wide feature set (Core) where new functionalities (Apps) could be implemented quicker. Core handled the elementary functionalities like authentication, routing, security, user-group management, etc., while Apps extended MD Connect's capabilities for a specific purpose, audience and/or duration, e.g. announcement, timetabling, messaging and academic-based conferences or events.

An App's use-case was Electronic Health Records (EHR). Students from different clinical schools are required to create and submit electronic-based health records after consultation with patients. The EHR is then submitted by each student to be assessed by their respective academic assessors of the faculty with pre-defined marking rubrics. After the completion of the assessment, the result will then be released to the students. All of these are handled by an App within MD Connect utilising Core's user-management.


Online (login Page)


  • Information Architecture
  • Wireframe, Prototype and Interface Design
  • Front-end Development
  • MD Connect Support and Maintenance


MD Connect: Manage Timetable UI interface research MD Connect: Manage Timetable component sketches MD Connect: Manage Timetable wireframes MD Connect: Manage Timetable wireframes MD Connect: Electronic Health Records concepts and features brandstorming. MD Connect: Electronic Health Records prototypes with feedback discussion feedbacks. MD Connect: Electronic Health Records student interfaces. MD Connect: Electronic Health Records assessor interfaces. MD Connect: ePortfolio wireframes. MD Connect: ePortfolio interfaces.