Reference Application Road Map
- Darius Jazayeri
- Burke Mamlin
- Achint Sethi
Obsolete
This page has become obsolete. See the Technical Roadmap for current information.
Vision
Our current goal is to get a decent starter feature set into the OpenMRS Reference EMR and have it tested and packaged into a new standalone in time for the 2013 OpenMRS Implementers Conference in October 2013.
Reference Implementations
Before we consider a feature to be complete, we believe it should be tested in production in a real-life OpenMRS implementation. That would be the "reference implementation" for the feature in question. It would provide feedback about the specific requirements and user experience of the feature, and help define the feature's future needs.
The tables below indicate both the status of coding up a feature in the RefApp codebase, as well as whether we've identified a reference implementation for that feature, and its status there.
(At present, Mirebalais plays an out-sized role here, but the goal is to have different reference implementations for different features. We still need to define a process around this.)
OpenMRS 2.1
Feature | Description | Status | Reference Implementation |
|---|---|---|---|
Manage & view patient allergies (e.g., on the patient dashboard) | in development (90%)
|
| |
Faster and predictable demo data | In Development (90%)
|
| |
Support for incorporating implementation-specific forms using HTML Form Entry and XForms | Done
|
|
Future Features
Feature | Description | Status | Reference Implementation |
|---|---|---|---|
Demonstrates the reporting framework by allowing you view a report containing some summary statistics for your system. | not done
| done Implemented in Mirebalais with PIH-specific code. Needs to be ported to RefApp codebase | |
CIEL Dictionary | Including CIEL dictionary (or most of it) out of the box | not done
|
|
Manage your users & providers, including roles & privileges, disable accounts, etc. | in development
| done Implemented in Mirebalais. Needs design review and porting to RefApp codebase | |
Avoid giving all API privileges to users | NOT DONE
|
| |
Basic support for retrospective data entry within the Reference Application | not done
| not done | |
| In Progress |
| |
Problem List | Manage & view patient problems (e.g., on the patient dashboard and integrated with diagnosis capture) | not done | not done |
Anonymous Patients | Support for unnamed John Doe patients | not done | done Implemented in Mirebalais. Needs to be ported to RefApp codebase |
Clinician Facing Patient Dashboard (v2) | Patient summary and dashboard designed for doctors and nurses | not done | not done |
Merge Patients | Merge duplicate patient records into one. | not done | done Implemented in Mirebalais. Needs to be ported to RefApp codebase |
Test Patients | Support for tagging & recognizing test/fake patients, so they can be ignored within reports. | not done | done Implemented in Mirebalais. Needs to be ported to RefApp codebase |
Patient Lookup (v2) | Search for a patient by name or ID | not done | not done |
Additional Administrative Functions | Concept Management, Manage Locations, App Manager, ... | not done | not done |
Simple Dispensing | A form to record medication dispensing events within the patient record | in design in progress | not done |
Registration (v2) | Add new patients to the system | not done | not done |
Decision Support (v1) | The first trivial example of providing decision-support feedback (includes significant design and back-end discussions) |
|
|
Clinical Encounter | Record the entire clinical transaction piece-by-piece as part of a Session, as opposed to via a Form. |
|
|
Patient Lists | e.g. "My Patients", "Inpatients on Service XYZ", etc. (Related to RA-202.) |
|
|
Program Enrollments | v1: capturing this data; v2: drive available forms/actions based on program state |
|
|
Easy Chart Review / Flowsheets | Reviewing the patient's whole electronic record for data points of interest (also has been called "Chart Search") |
|
|
See also