Multiple questions about Bahmni from VecnaCares team

Software Bahmni
1

Hi guys, These are questions from the VecnaCares team, as they continue working on placing Bahmni on the clinipak.

What does the location selection do? Can you limit what options show on landing page based on the location? Can you tie users to certain locations? Can we limit which visits a person can be sent to based on demographic information (OPD, emergency, etc.)? Can multiple vitals measurements be recorded? Can access to certain areas of the SW be limited by user so someone who logins only sees limited info if assigned to a certain group? Can we reduce the multiple databases into one database (Postgres and SQL into one database)?

1 Like
2

Can access to certain areas of the SW be limited by user so someone who logins only sees limited info if assigned to a certain group?

Based on the information on the wiki page [ Security Roles and Privileges > EMR Security and Access Control (OpenMRS) ] the access limitations for the EMR component can be controlled by the assignment on roles within OpenMRS.

The documentation for the role configuration of OpenERP and OpenELIS is “(…) currently In-Progress. Over the next few months, content will be added to it.”

3
  1. What does the location selection do?

There are different sorts of locations that have different implications in Bahmni.

  • Visit Location: Every instance must have a visit location. It can be a the root of the hierarchy (e.g. the Hospitals physical location).
  • Login Location: under a visit location, you can have multiple locations where a user may login at.
  • All encounters created will have the “Login Location” associated to it
  • When a visit gets created, the “visit location” which is higher up the hierarchy of the “login location”, gets associated with the visit. e.g. You may login at OPD-1, and capture some observation for a patient. The encounter locations will be “OPD-1”, but the visit location will be the “Hospital”.

Read more here: https://bahmni.atlassian.net/wiki/display/BAH/Visits%2C+Encounters+and+Locations https://bahmni.atlassian.net/wiki/display/BAH/Visit+Location

  1. Can you limit what options show on landing page based on the location? No.

  2. Can you tie users to certain locations? No

  3. Can we limit which visits a person can be sent to based on demographic information (OPD, emergency, etc.)? No. Curious though, as I don’t understand why you will want to differentiate visit type based on demographic info.

  4. Can multiple vitals measurements be recorded? Yes. I am assuming - multiple vitals meaning RR, Pulse, Temp etc. Just set up a form accordingly. Or setup different forms - if filled up at different times of the course of treatment or by different person.

  5. Can access to certain areas of the SW be limited by user so someone who logins only sees limited info if assigned to a certain group? Yes. Categorize privilege in role, assign role(s) to user, restrict app/extension point access by privileges. However in certain cases, this is not possible. For example: You can’t restrict forms by specific user privilege.

  6. Can we reduce the multiple databases into one database (Postgres and SQL into one database)? I so wish!! OpenMRS requires MySQL. and OpenERP/ELIS/Dcm4Che require Postgres!

1 Like
4

Just to add one thing to Angshuman’s comments: by writing code, almost anything is possible.

If your question is about what will work out of the box when you install Bahmni on a CliniPak today, then it’s as Angshu described. But in the longer run, we’d love to collaborate with your dev team so you can add these features to the Bahmni product.

1 Like