Default features supported in OpenMRS (Reference Application)


I am a software developer, but I am new at OpenMRS, and I hope to keep working on it to become an OpenMRS developer. I read the implementation guide and developer guide, but there are some information I haven’t gotten yet, so I need your help to clarify them, please.

1- The Reference application seems good, but to use it in real facility we need much more features, for example: I need the doctor to write the medicines for the patient so the pharmacist could see them in the patient’s profile directly and dispense these meds from the pharmacy directly. Another example may be the laboratory tests, so the doctor order specific test for the patient. So, my question is: Does OpenMRS by default has features to get the examples (Drugs order, tests orders,…) I mentioned, or OpenMRS is a basic framework and I should develop all modules I need by myself?

  1. I did not find enough documentations of forms supported by OpenMRS (which doest not require to write a module). So, I need to know, what are the applications in which I can use these forms, for example:
  • Can I use the forms to make new form linked to certain patient, for example, can I design form to get the meds order by doctors, and the pharmacist could see it?
  • Can I use the forms to get aggregated data by the facility (e.g: monthly report for some program)?
  1. Can I add new widget to patient’s dashboard in Reference Application, like the default widgets (DIAGNOSIS, VITALS, RECENT VISITS, …) without writing new module?

I am sorry for those too much questions, but as I noticed, OpenMRS does not have many resources for starters, and I hope that I can help more in the future.

Thanks in advance.

1 Like

Did you get a chance to look at bahmni?

Hello dkayiwa, and thank you for your reply.

Actually, yes I did, but there were a lot of customization and other frameworks linking, and I am thinking of working with the original source (OpenMRS), so I always keep with the updates and get more stable and simple application. Another reason is the more customization and using other applications the more errors could happen which requires you to know everything happens in the system to be prepared for any problem happens.

Thank you again.

You do not have to use all those external systems if you do not want to. Bahmni allows you to go for only what you need, and makes you aware of the fact that you can link to any of those system whenever you need to. It is very stable and a big number of implementations already have it in production.

As for doing forms without creating a module, you can take a look at these:

Thank you for your reply. I think I will spend more time on Bahmni to see its features.

Thanks for your advice.