Difference between revisions of "User:Matthew Vita"
From OpenEMR Project Wiki
Matthew Vita (talk | contribs) |
Matthew Vita (talk | contribs) |
||
(48 intermediate revisions by the same user not shown) | |||
Line 11: | Line 11: | ||
: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. | ||
:: '''• [https://community.open-emr.org/t/affordable-medical-devices-connectivity/8865 Affordable Medical Devices Connectivity]''' | |||
:: '''• [https://community.open-emr.org/t/units-support/8723 Units Support]''' | |||
:: '''• [https://community.open-emr.org/t/team-tasks-management/8872 Team Tasks Management]''' | |||
:: '''• [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]''' | |||
:: '''• 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)]''' | |||
<br /> | |||
:''(Upon project completion, simply note (DONE) at the front of the entry)'' | |||
==Something Missing?== | |||
: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. | |||
== | |||
Latest revision as of 00:41, 13 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.
- • 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
- • Module Framework
- • Frontend User Interface Rework
- • Telemedicine Support
- • Speech Dictation Documentation
- • Picture Archiving and Communication System (PACS)
- (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.