Difference between revisions of "Roadmaps"
From OpenEMR Project Wiki
Bradymiller (talk | contribs) |
Bradymiller (talk | contribs) |
||
Line 9: | Line 9: | ||
=== Data validation and security === | === Data validation and security === | ||
# Client-side validation library | # Client-side validation library | ||
# Client-side validation for Layout-Based forms | # Client-side validation for Layout-Based forms <span style="color:green">(Code Review Requested)</span> | ||
# Database fields meta-dictionary | # Database fields meta-dictionary | ||
# Server-side validation | # Server-side validation | ||
=== Enterprise readyness === | === Enterprise readyness === |
Revision as of 09:20, 19 June 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 a very nice starting point, blatantly copied the roadmap by Matrix on the Matrix Perspective wiki page.
Data validation and security
- Client-side validation library
- Client-side validation for Layout-Based forms (Code Review Requested)
- Database fields meta-dictionary
- Server-side validation
Enterprise readyness
- Smartcard support and single sign-on (SSO)
- PSR-3 logger
- Data versioning as audit tool (i.e. store versions of data )
Framework
- Asset manager to manage CSS and JS files in single location.
- Consolidate jQuery versions
- Introduce PSR-4 autoloader
- Package management for 3rd party client side libraries (COMPLETED and in OpenEMR 4.3.1)
- Package management for 3rd party PHP libraries ( html2pdf, phpmailer, etc. )
- Consolidate PDF libraries
- Separate Templating from code
Functionality
- Authorization enhancements
- Support for Microsoft Office document format based templates
- Support direct integration with cameras and scanners
- Support interfacing with lab equipment
- Multi-clinic support
Future proofing
- Truly installable modules
- PHP7 support (COMPLETED and in OpenEMR 4.2.2)
- Support of InnoDB, including code changes, migration script (COMPLETED and in OpenEMR 4.3.1)
QA and testing
- Automated tests using Selenium
- Unit tests where possible
- Automatic build with code scanning
I18N and L10N
- RTL support (COMPLETED and in OpenEMR 4.2.2)
- Allow different Insurance models
Security
- One web root
- Isolate installation and patch scripts into their own folder
Calendar
- Facility level calendar management (working hours)
- National holidays support
- Configurable weekends (COMPLETED and in OpenEMR 4.3.1)
Performance
- Use document thumbnails
- speed up Globals
- speed up Installation script
UI, UX
- Adoption of Bootstrap Framework
- Replace date picker widget for newer, accessible version.
OEMR Organization Roadmap
Overview
- Below is just a possible starting point.
Maintain organization
- Ensure maintain non-profit status.
- Ensure up to date on taxes.
- 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.
- Ensure all meetings, business by the board, and the organization accounting are transparent and can be followed easily by the public.
- Ensure ongoing organization budget.
MU2 certification and infrastructure
MU3 certification and infrastructure
Fund-raising
- Donations.
- Users.
- Vendors/companies.
- Public.
- Grants.
- Crowdsourcing.
Presence/brand
- OEMR organization Logo.
- OEMR organization Website.
Support OpenEMR Project
- Support the OpenEMR roadmap(via funding etc.).
- Champion the OpenEMR project.