Difference between revisions of "Roadmaps"

From OpenEMR Project Wiki
(Remote Patient Vitals Module)
 
(56 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=Overview=
:At the [[OEMR_wiki_page#June_8.2C_2016|6/8/2016 OEMR organization board meeting]], it was decided to create a [[OEMR_wiki_page#Roadmap_Committee|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.
<br>
=OpenEMR Project Roadmap=
=OpenEMR Project Roadmap=
===Overview===
:As a very nice starting point, blatantly copied the roadmap by Matrix on the [[Matrix_Perspective|Matrix Perspective]] wiki page.


=== Data validation and security ===
==Description==
# Client-side validation library
# Client-side validation for Layout-Based forms
# Database fields meta-dictionary
# Server-side validation


=== Enterprise readyness ===
:This core roadmap addresses new development efforts that will benefit outpatient and inpatient users alike. Roadmap items include hybrid inpatient/outpatient support, advanced billing, Fast Healthcare Interoperability Resources (FHIR) integration, modern cloud offerings, ability to perform quality reporting, low-cost medical devices connectivity, and more. This mixture of user-facing and "under the hood" technology enhancements have been identified as important by our users. By working together on one well-defined roadmap, our community and platform will continue shining around the globe.
# Smartcard support and single sign-on (SSO)
# PSR-3 logger
# Data versioning as audit tool (i.e. store versions of data )


=== Framework ===
:OEMR (non-profit backer of OpenEMR) and our vibrant community is dedicated to responding to user needs and setting our priorities to be consistent with the requests of our colleagues abroad. Regardless of if you or a clinician, developer, documenter, tester, or translator, you are essential in the successful execution of this roadmap.
# Asset manager to manage CSS and JS files in single location.
# Consolidate jQuery versions
# 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>
# Package management for 3rd party PHP libraries ( html2pdf, phpmailer, etc. )
# Consolidate PDF libraries
# Separate Templating from code


=== Functionality ===
==Core Features==
# 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 ===
:These projects make up the roadmap and can be worked on independently. Requirements and tasks management can be found by visiting each forum link, which can be thought of as the "top of the tree" that links tasks, people, chat boards, resources, and relevant code branches.
# Truly installable modules
# PHP7 support <span style="color:green">(COMPLETED and in OpenEMR 4.2.2)</span>
# Support of InnoDB, including code changes, migration script <span style="color:green">(COMPLETED and in OpenEMR 4.3.1)</span>


=== QA and testing ===
:: '''• [https://community.open-emr.org/t/affordable-medical-devices-connectivity/8865 Affordable Medical Devices Connectivity]'''
# Automated tests using Selenium
:: '''• [https://community.open-emr.org/t/units-support/8723 Units Support]'''
# Unit tests where possible
:: '''• [https://community.open-emr.org/t/team-tasks-management/8872 Team Tasks Management]'''
# Automatic build with code scanning
:: * DONE - '''[https://community.open-emr.org/t/proposed-ub04-cms-1450-claims/8747 Advanced Billing]'''
:: '''• [https://community.open-emr.org/t/fast-healthcare-interoperability-resources-fhir-integration/8220 Fast Healthcare Interoperability Resources (FHIR) Integration]'''
:: '''• [https://community.open-emr.org/t/modern-cloud-solutions/8869 Modern Cloud Solutions]'''
:: '''• [https://community.open-emr.org/t/mips/9013 Quality Reporting]'''
:: '''• [https://community.open-emr.org/t/realistic-test-data-generation/8866 Realistic Test Data Generation]'''
:: '''• [https://community.open-emr.org/t/clinical-intelligence-dashboards/8871 Clinical Intelligence Dashboards]'''
:: '''• [https://community.open-emr.org/t/intelligent-chart-summarization/8573 Intelligent Chart Summarization]'''
:: '''• [https://community.open-emr.org/t/backend-modernization-project/8870 Normalized Code Directory Structure]'''
:: '''• [https://community.open-emr.org/t/backend-modernization-project/8870 Separation of Business Logic Code]'''
:: '''• [https://community.open-emr.org/t/module-framework-development/8851 Module Framework]'''
:: '''• [https://community.open-emr.org/t/bootstrap-standard/8263 Frontend User Interface Rework]'''
:: '''• [https://community.open-emr.org/t/telemedicine-video-support/8868 Telemedicine Support]'''
:: '''• [https://community.open-emr.org/t/speech-dictation/8670/7?u=matthewvita Speech Dictation Documentation]'''
:: '''• [https://community.open-emr.org/t/picture-archiving-and-communication-system-pacs/8867 Picture Archiving and Communication System (PACS)]'''
:: '''• [https://community.open-emr.org/t/medical-administration-record/8309 Medical Administration Record]'''
:: '''• [https://community.open-emr.org/t/remote-patient-vitals-module/9411 Remote Patient Vitals Module]'''


=== I18N and L10N ===
# RTL support <span style="color:green">(COMPLETED and in OpenEMR 4.2.2)</span>
# Allow different Insurance models


=== Security ===
<br />
# One web root
:''(Upon project completion, simply note (DONE) at the front of the entry)''
# Isolate installation and patch scripts into their own folder


=== Calendar ===
==Something Missing?==
# Facility level calendar management (working hours)
# National holidays support
# Configurable weekends <span style="color:green">(COMPLETED and in OpenEMR 4.3.1)</span>


=== Performance ===
:At the [[OEMR_wiki_page#June_8.2C_2016|6/8/2016 OEMR organization board meeting]], it was decided to create a [[OEMR_wiki_page#Roadmap_Committee|Roadmap Committee]] to begin looking at pursuing community driven roadmaps. There are 2 separate entities, the OpenEMR Project and the OEMR organization, which have separate roadmaps. However, since the main goal of the OEMR organization is to support the OpenEMR project, it makes sense to develop roadmaps for both of them in unison. If you feel something is missing from this roadmap, please contact the committee. If it is deemed "mission critical" (such as the existing items), it will be added. If it not "mission critical", it will be added to [[Active Projects|Active Projects & Projects Needing Developers]] listing.
# Use document thumbnails
# speed up Globals
# speed up Installation script


=== UI, UX ===
# Adoption of Bootstrap Framework
# Replace date picker widget for newer, accessible version.
<br>
<br>


Line 85: Line 59:
#Donations.
#Donations.
#*Users.
#*Users.
#**Implement registration for OpenEMR users.
#*Vendors/companies.
#*Vendors/companies.
#*Public.
#*Public.
#Grants.
#Grants.
#Crowdsourcing.
#Crowdsourcing.
#Other Opportunities.


===Presence/brand===
===Presence/brand===
Line 97: Line 73:
#Support the OpenEMR roadmap(via funding etc.).
#Support the OpenEMR roadmap(via funding etc.).
#Champion the OpenEMR project.
#Champion the OpenEMR project.
#Support OpenEMR project autonomy.
<br>
<br>
=Forums threads=
:[https://sourceforge.net/p/openemr/discussion/oemr_501c3/thread/998b6170/ Roadmap Committee]

Latest revision as of 05:39, 15 December 2017

OpenEMR Project Roadmap

Description

This core roadmap addresses new development efforts that will benefit outpatient and inpatient users alike. Roadmap items include hybrid inpatient/outpatient support, advanced billing, Fast Healthcare Interoperability Resources (FHIR) integration, modern cloud offerings, ability to perform quality reporting, low-cost medical devices connectivity, and more. This mixture of user-facing and "under the hood" technology enhancements have been identified as important by our users. By working together on one well-defined roadmap, our community and platform will continue shining around the globe.
OEMR (non-profit backer of OpenEMR) and our vibrant community is dedicated to responding to user needs and setting our priorities to be consistent with the requests of our colleagues abroad. Regardless of if you or a clinician, developer, documenter, tester, or translator, you are essential in the successful execution of this roadmap.

Core Features

These projects make up the roadmap and can be worked on independently. Requirements and tasks management can be found by visiting each forum link, which can be thought of as the "top of the tree" that links tasks, people, chat boards, resources, and relevant code branches.
Affordable Medical Devices Connectivity
Units Support
Team Tasks Management
* DONE - Advanced Billing
Fast Healthcare Interoperability Resources (FHIR) Integration
Modern Cloud Solutions
Quality Reporting
Realistic Test Data Generation
Clinical Intelligence Dashboards
Intelligent Chart Summarization
Normalized Code Directory Structure
Separation of Business Logic Code
Module Framework
Frontend User Interface Rework
Telemedicine Support
Speech Dictation Documentation
Picture Archiving and Communication System (PACS)
Medical Administration Record
Remote Patient Vitals Module



(Upon project completion, simply note (DONE) at the front of the entry)

Something Missing?

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 have separate roadmaps. However, since the main goal of the OEMR organization is to support the OpenEMR project, it makes sense to develop roadmaps for both of them in unison. If you feel something is missing from this roadmap, please contact the committee. If it is deemed "mission critical" (such as the existing items), it will be added. If it not "mission critical", it will be added to Active Projects & Projects Needing Developers listing.


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.
      • Implement registration for OpenEMR 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