Potential users frequently tell us the OpenEMR looks old and out of date. They are correct and some discussion about this had occurred off and on. MI2 has been funded to re-factor the UI of OpenEMR and we are actively working on that. We have about 100 hrs into it so far. The new code is running as ajax / jquery on top of OpenEMR in order to make sure that it does not, functionally, impact the system.
We are very focused on cleaing up the work flow and the look and feel to smooth out the user experience and to standardize the layout of screens and reports so users are not confused by differing selection buttons/links/descriptions etc. The overview and design of the project are here:
I will get public demo system online and announced later in the week and start posting some of the technical details and issues here and on the wiki. All the work is being done against the development tip and we are integrating it into our development regularly.
The long view is to drop the frames. The first pass is less dramatic. First for continuity and because there are places where the user needs to see two things at once. Like at login (Calendar/Notes). We are considering changing it from frames to the more accepted (modern?) use of ‘divs’ to support that need.
Most of the other places frames are in use have been replaced by model popups and tabbed views.
Happy to demo it. I’ll drop you a line of the forum
Just an ignorant question - if you are making a “layer” atop the OpenEMR, could that not be used to capture data entered with a timestamp? That would be most all that would be required to allow a “recording” on a remote pseudo-server which would have a copy of the prior day’s dataset, but need not have real-time connectivity. It would work by itself, with its own updates, etc from those inputs, until it connected again. Once that connectivity did occur, the saved “transactions” could be posted to the central server, which could then post the updated “current real” to the remote. Again, my need is to provide for usability un areas where wifi WAN is simply not reliable or fast enough. Thoughts? Specific applications include my wife’s house call practice, EMT’s, home care in general, and the African “country” plan I read here about earlier.
Very nice. I’m especially interested in the , which is very similar to my proposal after a discussion with Jeremy on e-prescribing outlined here:
This would be the perfect (in my opinion) “seed” of your frameworks and changes to get into the cvs. Then would make the developmental route to e-prescribing development much more clear.