Wiki Spaces

Documentation
Projects
Resources

Get Help from Others

Q&A: Ask OpenMRS
Discussion: OpenMRS Talk
Real-Time: IRC Chat | Slack

Documentation

Page tree
Skip to end of metadata
Go to start of metadata

Overview

OpenMRS is a free, open source electronic medical record system (EMR) designed for use in the developing world. It supports health care delivery and research on every continent.

Are you looking for an electronic medical record system to use at your site? Would you like to know more about OpenMRS' capabilities? We suggest you begin with Getting Started with OpenMRS. The Getting Started guide introduces the software's features.  It will help you evaluate if OpenMRS is a good clinical, technical, and organizational solution for your needs.

'Where is OpenMRS being used?' 'What technologies is OpenMRS built on?' 'What new features are planned?'  The OpenMRS FAQ  answers these questions and more.

Next Steps

Try the software with the OpenMRS demo installations, or install it on your own server.

Look at the Implementers Guide for the details of starting an OpenMRS project at your site.   

Do you have more questions?  There are many resources for the OpenMRS community.

  • No labels

8 Comments

  1. Unknown User (michael)

    Some other ideas:

    • Where is OpenMRS being used and by whom?
    • Who is using OpenMRS for XYZ?
    • Can I do XYZ with OpenMRS?
    • How is OpenMRS licensed and can I build on top of it?
  2. Unknown User (bwolfe)

    • Why OpenMRS?
    • Quickstart Guide?
  3. Unknown User (jblaya)

    I would change the order. Put data model and architecture at the end.  Also, I agree with Michael to put concretely where and what OpenMRS is being used.

    and the can I build on top of it, should address both open and proprietary things.

    Finally, I would put

    OpenMRS and mobile solutions

  4. Unknown User (jriley)

    Let's imagine I'm New and Curious.  What's my motivation in this scene?
    I'm affiliated with a health facility. Maybe we have no records, maybe our old system isn't working any more. Our recordkeeping is painful enough that I'm looking for a new system. For some reason (we're small? we don't want to spend the money?) we are looking at free software instead of buying a commercial one and paying consultants. I'm either nontechnical but know there's got to be something out there, or a little technical, like a computer-savvy friend or IT staff.  I'm not a programmer. 
     
    What can OpenMRS  do for me?  Can it solve my problem?
    How much does it cost? 
    What are the organizational requirements to run OpenMRS? (a fulltime admin, so many data entry clerks, etc.)
    What do I need to get started?
    I like Michael's suggestions re: what are other people doing with it, and Ben's suggestion for Why OpenMRS. . 
    Data model and architecture don't belong here. Describe the benefits of it, but don't tell New And Curious about how the magic happens. If they want to know, they'll click through to the technical pages.  If they're an engineer, they started on those pages and arrived here later.
    I see the words "framework" and "data dictionary" a lot. Those ideas need to be unpacked and explained in terms of the results, not the mechanisms.  OpenMRS is flexible.  It was written so every health facility can use the ideas and terminology that they use at their site, in their local language.  They can make electronic forms that collect the same information that their paper forms do. The basic installation is very plain, but there are plugins for different kinds of features. New And Curious can install the plugins that are most useful for their facility, e.g. TB module, ID cards, Mirth messaging, etc.  If there's a custom need, and the implementing site has a Java programmer, they can develop their own plugins.
    I think it's important to be up front about the tradeoff between flexibility and setup effort. This isn't an out-of-the-box solution.  You don't get stuck with terminology or forms that don't match how you work -- but you have to make your own. There's a very active community who'll share what they know, but there's no support line to call if something breaks.   The tradeoff doesn't belong in an intro page, but it should show up somewhere.  Maybe there should be a page for "Is OpenMRS Right For Me?".
    Let's imagine I'm New and Curious.  What's my motivation in this scene?

    I'm affiliated with a health facility. Maybe we have no records, maybe our old system isn't working any more. Our recordkeeping is painful enough that I'm looking for a new system. For some reason (we're small? we don't want to spend the money?) we are looking at free software instead of buying a commercial one and paying consultants. I'm either nontechnical but know there's got to be something out there, or a little technical, like a computer-savvy friend or IT staff.  I'm not a programmer. 

    What can OpenMRS  do for me?  Can it solve my problem?

    How much does it cost? 

    What are the organizational requirements to run OpenMRS? (a fulltime admin, so many data entry clerks, etc.)

    What do I need to get started?

    I like Michael's suggestions re: what are other people doing with it, and Ben's suggestion for Why OpenMRS. . 

    Data model and architecture don't belong here. Describe the benefits of it, but don't tell New And Curious about how the magic happens. If they want to know, they'll click through to the technical pages.  If they're an engineer, they started on those pages and arrived here later.

    I see the words "framework" and "data dictionary" a lot. Those ideas need to be unpacked and explained in terms of the results, not the mechanisms.  OpenMRS is flexible.  It was written so every health facility can use the ideas and terminology that they use at their site, in their local language.  They can make electronic forms that collect the same information that their paper forms do. The basic installation is very plain, but there are plugins for different kinds of features. New And Curious can install the plugins that are most useful for their facility, e.g. TB module, ID cards, Mirth messaging, etc.  If there's a custom need, and the implementing site has a Java programmer, they can develop their own plugins.

    I think it's important to be up front about the tradeoff between flexibility and setup effort. This isn't an out-of-the-box solution. The setup effort means an organization needs more technical expertise. You don't get stuck with terminology or forms that don't match how you work -- but you have to make your own. There's a very active community who'll share what they know, but there's no support line to call if something breaks.   The tradeoff doesn't belong in an intro page, but it should show up somewhere.  Perhaps add a page for "Is OpenMRS Right For Me?".

  5. Questions posed by Gaurav on OpenMRS Answers:

    • We want to Migrate to OpenMRS, what are the hardware(which) requirements for x number of patients?
    • How can we start?
    • How many functionalities are there?
    • I have this requirement, what module should we install?
    • We want to have this feature developed, is their anyone else who wants to collaborate with us and needs a similar type of functionality added?
    • What's the minimum man-hours required?
  6. Unknown User (gauravpaliwal)

    Also if it is ethically okey then we can also have a comparison chart of OpenMRS with other open source EMR's .

  7. Unknown User (jriley)

    There was some good stuff in the first draft that belongs elsewhere. Copying it here so I can find a new home for it later.

    • Why OpenMRS?
      • Cost
      • Functions
      • Comparison Chart
    • Who is using OpenMRS for XYZ?
    • Can I do XYZ with OpenMRS?
    • What do I need to get started?
      • What are the hardware requirements for x number of patients?
    • Which module is right for my needs?  -- move to implementers, may be addressed enough in getting started
      • OpenMRS and mobile solution?
      • Want to have a feature developed, is their anyone else who wants to collaborate with us and needs a similar type of functionality added?
    • is this addressed in detail in the guide?
      • What are the organizational requirements to run OpenMRS? (a full time admin, so many data clerks, etc.)
      • Minimum man-hours required?
      • Quickstart Guide - Quick Installation Guide?
      • How is OpenMRS licensed and can I build on top of it?
        • Address open and propretary things
  8. Unknown User (jimmyawilder)

    I am new to Open MRS and would like to help with documentation.  I am a member of a group of students in an OSS class  and we have been tasked with contributing to Open MRS through documentation.  We've been looking at issues in JIRA and have tried to claim an issue (TRUNK 2929), but we are unable to determine how to actually work on the issue.  Where can I find instructions or a tutorial to show me how to do get involved?