1 / 14

Creating a Modern Electronic Medical Records (EMR) System TJHSST Senior Research Project

This research project focuses on transforming electronic medical records (EMR) systems by introducing a more user-friendly interface, enhanced database design, and improved text entries. The system utilizes open-source MySQL backend technology, implements a graphical user interface, and allows for efficient data entry through templates. The study explores various UI experiments, such as autocomplete features and PHP automation of template design. The goal is to create a modern and competitive EMR system by integrating a WYSIWYG editor for easy template creation and incorporating image upload capabilities for attaching scanned files.

rtoni
Download Presentation

Creating a Modern Electronic Medical Records (EMR) System TJHSST Senior Research Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Creating a Modern Electronic Medical Records (EMR) System TJHSST Senior Research Project Computer Systems Lab 2009-2010 Jeremy Chaikind Period 2

  2. Introduction • Healthcare Reform – doctors have to change too • Paper charts → Electronic Charts • Electronic Medical Records – EMR • What's out there: • Constricting database designs • Text-heavy UI • Cost : ~$5000 – $15000 per physician

  3. Mander EMR System • Open Source MySQL backend • ACID-compliant “transactions” • Highly expandable – Relational Model and Hierarchical Model • Graphical User Interface – browser based • Coded in HTML, CSS, Javascript, etc. • Graphical templates for data entry – based on paper templates • WYSIWYG use for text-based entry

  4. Database Design • Relational Database Model • Data are divided into many specialized tables based on what set of attributes are stored • A single, unique ID # links all records for the same person

  5. Hierarchical Model

  6. Templates Initially - Hard Coded template for Dr. Kern • Initially in hand-coded HTML, test inputs only

  7. kern1.html – hand-coded HTML

  8. UI Experiments • Autocomplete • Compare with Practice Partners' “Quick Texts” feature • Begin typing and the program will read from the database and return the words that you could be typing

  9. UI Experiments • JSON Autocomplete • Based on a set of functions by Jason Koenig (Pd. 5) • Implements Javascript Object Notation to return suggestions as an array • Enables better manipulation of returned data • Semicolon-spliced suggestions

  10. Templates (again) • PHP automation of template design • Approximate a coding language for templates • Cleaner to read than hand-coded HTML • Easy use of tables for organization • Logical next step (after the school year): integration with a WYSIWYG to allow easy template creation

  11. Templates (again) • The test: use the PHP library to create another template • Dr. Faye Rosenbaum, neurology • Tab-based vs. Table-based • Difference in Coding Time

  12. rosenbaum1.html – PHP-generated

  13. Alternate Entry Modes WYSIWYG [what you see is what you get] using TinyMCE to allow formatted note entry Image upload for attaching scanned files

  14. So What? • Is it ready to compete in the marketplace? • But: • Relational model/hierarchical model → greater expandability • GUI features like autocomplete • Graphical Templates – hand-coded to function-based • AND text-style notes • ?a modern EMR prototype

More Related