Have you implemented OpenMRS? Please participate in the Implementation Site Survey. If you already have, thank you!
OpenMRS is an electronic medical record platform. Basically we provide an API and data model for storing and analyzing patient-level data, and a reference application that's used in 40+ mostly-developing countries. The system includes "core" code and pluggable "modules" that allow very powerful extensions of functionality, and UI-level customization.
4-5 June 2011
To try OpenMRS on your laptop and play with web service calls, download the OpenMRS 1.9-SNAPSHOT Standalone. Unzip this file and run the included JAR file to start OpenMRS. The login username is "admin" and the password is "Admin123".
Also see branch set up for this: TODO: create + link to branch here
We have an ongoing Multiple providers per encounter project that is targeted for OpenMRS 1.9. Some India-based Thoughtworkers have done some initial tickets in this project.
From my quick analysis, the following tickets will provide a minimal coherent, demo-able version of this new feature (if we enter some data via sql inserts):
Time permitting, these would make the demo less "minimal" (and avoid the need for sql inserts in the demo):
Thoughtworks has been helping to develop a module to view patient data within OpenMRS.
We are redoing our UI from scratch in OpenMRS version 2.0 (see OpenMRS 2.0 User Interface Redesign). We're still in the early stages, and it's probably a bit early to do what I'm proposing here, but here are some potential code-jam ideas:
We want a fixed element of the UI where we can inform/remind the user of ongoing tasks and processes. For example:
We've explored doing this as a "taskbar" panel at the center-top of each page through this mockup and this prototype implementation.
Is this a good approach in general? If not, what alternative approaches should we consider? If so, what are some points we should keep in mind while implementing this UI element? What standard interactions does it need?
Often, the pages in our UI will display elements that have additional descriptive metadata we don't display by default, and sometimes their own "view/edit" page as well. We'd like the user to be able to get access to this additional descriptive metadata, without leaving the current page, to avoid breaking the flow of their actual task. Some possibilities:
For example the page to view an encounter would display short forms of these items, with possible additional information
Or a patient's page might list the patient's last 5 encounters. In this case you might want to preview the encounter, but you might also want to navigate to it.
What's a good common UI interaction that will unobtrusively allow people to get additional info about visible items? How do we avoid confusion if some of those same items may also be navigated to? Advantages/disadvantages/alternatives to in-place (e.g. tool-tip) vs fixed location (e.g. preview pane)?
In the new UI we would like to use a coherent, attractive, set of icons to represent different OpenMRS verbs and objects.
We'd want to use these in: