Pinned Repositories
openmrs-module-bahmniapps
Bahmni EMR Frontend code for Clinicians and staff members, written in Angular.JS and React
checkoutService
getIndexedDbSize
jsonforms-with-redux
openmrs-core
OpenMRS API and web application code
openmrs-module-emrapi
Higher-level APIs to support building EMR functionality in OpenMRS, to supplement the data-level APIs in the OpenMRS core.
openmrs-module-idgen
Provides patient identifier generation for other OpenMRS modules
openmrs-module-legacyui
The legacy user interface for OpenMRS 1.9 is chiefly comprised of administrative functions and the patient dashboard. Apparently, a new and more contemporary UI has been introduced via a UI framework and the legacy UI is kept around for administrative functions that are not yet implemented in the new UI. To retire the Legacy UI as planned, it is required to move the implementations and modules that still rely on it in order to maintain backwards compatibility. The main idea behind this project is to move legacy UI functions into an OpenMRS module that these implementations can install until they are able to migrate away from it, since most of the implementations of OpenMRS around the world are running OpenMRS 1.9.
openmrs-core
OpenMRS API and web application code
openmrs-module-emrapi
Higher-level APIs to support building EMR functionality in OpenMRS, to supplement the data-level APIs in the OpenMRS core.
chethandeshpande's Repositories
chethandeshpande/checkoutService
chethandeshpande/getIndexedDbSize
chethandeshpande/jsonforms-with-redux
chethandeshpande/openmrs-core
OpenMRS API and web application code
chethandeshpande/openmrs-module-emrapi
Higher-level APIs to support building EMR functionality in OpenMRS, to supplement the data-level APIs in the OpenMRS core.
chethandeshpande/openmrs-module-idgen
Provides patient identifier generation for other OpenMRS modules
chethandeshpande/openmrs-module-legacyui
The legacy user interface for OpenMRS 1.9 is chiefly comprised of administrative functions and the patient dashboard. Apparently, a new and more contemporary UI has been introduced via a UI framework and the legacy UI is kept around for administrative functions that are not yet implemented in the new UI. To retire the Legacy UI as planned, it is required to move the implementations and modules that still rely on it in order to maintain backwards compatibility. The main idea behind this project is to move legacy UI functions into an OpenMRS module that these implementations can install until they are able to migrate away from it, since most of the implementations of OpenMRS around the world are running OpenMRS 1.9.