Difference between revisions of "Roadmaps"

From OpenEMR Project Wiki
Line 19: Line 19:


=== Framework ===
=== Framework ===
# Asset manager to allow custom CSS and JS files in a selected location. <span style="color:red">(Code Review Requested)</span>
# Asset manager to allow custom CSS and JS files in a selected location.
# Introduce PSR-4 autoloader
# Introduce PSR-4 autoloader
# [[Bower|Package management for 3rd party client side libraries]] <span style="color:green">(COMPLETED and in OpenEMR 4.3.1)</span>
# [[Bower|Package management for 3rd party client side libraries]] <span style="color:green">(COMPLETED and in OpenEMR 4.3.1)</span>

Revision as of 07:30, 15 July 2016

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.


OpenEMR Project Roadmap

Overview

As the starting point, copied the roadmap by Matrix on the Matrix Perspective wiki page.

Data validation and security

  1. Client-side validation library
  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

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

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

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
  2. Automated testing using Selenium
  3. Unit tests where possible
  4. 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
  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
  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.

MU2 certification and infrastructure

MU3 certification and infrastructure

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.