Difference between revisions of "User:Matthew Vita"

From OpenEMR Project Wiki
Line 13: Line 13:
: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.
: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.


[combine bullet list]
** [https://www.google.com with definition]  
** with definition  
** [with definition https://www.google.com]
::- definition
::- definition
** creates empty space
** creates empty space

Revision as of 18:06, 12 August 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.
- definition
    • creates empty space
[www.google.com Affordable Medical Devices Connectivity]
Units Support'
Team Tasks Management
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
Frontend User Interface Rework
Telemedicine Support
Speech Dictation Documentation