Roadmaps

Overview

At the 6/8/2016 OEMR organization board meeting, it was decided to create a Roadmap Committee to begin looking at pursuing community driven roadmaps. There are 2 separate entities, the OpenEMR Project and the OEMR organization, which will have separate roadmaps. However, since the main goal of the OEMR organization is to the support the OpenEMR project, it makes sense to develop roadmaps for both of them in unison. There is also a roadmap that is specific to OpenEMR modernization which is being used to drive the OpenEMR modernization project.

OpenEMR Project Roadmap

??? means this is up for debate (ie. does it belong in the roadmap)

Data validation and security

1. Client-side validation library (COMPLETED and in OpenEMR 4.3.1)
2. Client-side validation for Layout-Based forms (COMPLETED and in OpenEMR 4.3.1)
3. Database fields meta-dictionary ???
4. Server-side validation

Enterprise readyness

1. Smartcard support and single sign-on (SSO) ???
2. PSR-3 logger ???
3. Data versioning as audit tool (i.e. store versions of data) ???

Framework

• (Note more details on the Framework project can be found on the Modernization Roadmap)

1. Asset manager to allow custom CSS and JS files in a selected location. (PLANNED BY Matrix)
2. Introduce PSR-4 autoloader (COMPLETED and in OpenEMR 4.3.1)
3. Package management for 3rd party client side libraries (COMPLETED and in OpenEMR 4.3.1)
4. Consolidate 3rd party client side libraries (WORK IS ONGOING by Brady and Craig)
5. Package management for 3rd party PHP libraries ( html2pdf, phpmailer, etc. ) (WORK IS ONGOING by Scott)
6. Consolidate PHP (including PDF) libraries (WORK IS ONGOING by Scott)
7. Normalize directory structure
8. Migrate code to DAO(data access objects) models (integrate models for all major objects)
9. Separate Templating from code (ie. MVC)

Functionality

1. Authorization enhancements
2. Support for Microsoft Office document format based templates
3. Support direct integration with cameras and scanners ???
4. Support interfacing with lab equipment ???
5. Multi-clinic support improved

Future proofing

1. Migrate the legacy smarty code from 2.x to 3.x (or migrate the legacy code to another mvc)
2. Truly installable modules
3. PHP7 support (COMPLETED and in OpenEMR 4.2.2)
4. Support of InnoDB, including code changes, migration script (COMPLETED and in OpenEMR 4.3.1)

QA and testing

1. Manual Testing Scripts (WORK IS ONGOING by Matthew)
2. Unit tests where possible
3. Automatic build with code scanning

I18N and L10N

1. RTL support (COMPLETED and in OpenEMR 4.2.2)
2. Allow different Insurance models

Security

1. One web root ???
2. Isolate installation and patch scripts into their own folder ???

Calendar

1. Facility level calendar management (working hours)
2. National holidays support (COMPLETED and in OpenEMR 4.3.1)
3. Configurable weekends (COMPLETED and in OpenEMR 4.3.1)

Performance

1. Use document thumbnails (COMPLETED and in OpenEMR 4.3.1)
2. speed up Globals
3. speed up Installation script

UI, UX

1. Adoption of Bootstrap Framework (WORK MAY BE RESTARTED by Practice Provider)
2. Replace date picker widget for newer, accessible version.

OEMR Organization Roadmap

Overview

Below is just a possible starting point.

Maintain organization

1. Ensure maintain non-profit status.
2. Ensure up to date on taxes.
3. Ensure adequate number of board meetings which are attended by adequate number of board members to ensure business and motions are completed in a timely fashion.
4. Ensure all meetings, business by the board, and the organization accounting are transparent and can be followed easily by the public.
5. Ensure ongoing organization budget.

Fund-raising

1. Donations.
   • Users.
   • Vendors/companies.
   • Public.
2. Grants.
3. Crowdsourcing.
4. Other Opportunities.

Presence/brand

1. OEMR organization Logo.
2. OEMR organization Website.

Support OpenEMR Project

1. Support the OpenEMR roadmap(via funding etc.).
2. Champion the OpenEMR project.
3. Support OpenEMR project autonomy.

Forums threads

Roadmap Committee