Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
 
TypeAdministered ByCurrent MechanismDesired MechanismDeveloped By
Address HierarchyData AdministratorLegacy UIAdmin UIImplementer
BedData AdministratorSQLAdmin UIImplementer
Care Setting----

Diagnoses
Chief Complaints 

Data AdministratorRuby, CSVAdmin UI, Meta Data SharingClinical Data Curator
Observation concepts Legacy UIAdmin UI, Meta Data Sharing
BedsSQLOpenMRS Admin UI
Care Setting?-

Problems
Diagnoses
Chief Complaints

Ruby, CSVOpenMRS Admin UI
CSV file import
Meta Data Sharing

Observations
Concepts
Concept Sets

Legacy UI
Prepackaged concept sets provided via liquibase by Bahmni

OpenMRS Admin UI
CSV file import
Meta Data Sharing

Reference Terms
ICD Reference terms
ICD drug references 
CSV file imported by implementerCSV file imported by implementer
Bahmni to package ICD csv file in default_config
Concept ClassesUsing defaults from OpenMRS
New classes added by Bahmni
Legacy UI

Using defaults from OpenMRS
Delete classes added by Bahmni
Legacy UI 

DrugsCSV file imported in Reference Data
Reference Data UI
CSV file imported in OpenMRS
OpenMRS Admin UI
(Price managed via OpenERP)
Providers
Providers, Users
Their roles and privileges
Legacy UIOpenMRS Admin UI 
Services
Encounter Types
Location
(Their mapping) 
. In Patient ET provided by EMR API
. Bahmni provides (Registration, Radiology, Investigation,
LAB_RESULT, Patient Document, VALIDATION_NOTES)
. Location managed via Legacy UI
. Mapping created via SQL by implementer
. In Patient ET provided by EMR API
. Bahmni provides (Registration, Radiology,
LAB_RESULT, Patient Document)
. Implementer creates ET, Locations, mapping
via OpenMRS Admin UI
Patient
Patient identifier
Patient attributes
Patient address 
 OpenMRS Admin UI
Program
Program
Observation Template, Program mapping
Legacy UI

OpenMRS Admin UI

Scheduled JobsLegacy UILegacy UI
Visit
Visit Type
Visit Attributes 
Legacy UIOpenMRS Admin UI