Interested is participating in the Google Summer of Code program? Please see the GSOC wiki page.

Wiki Spaces

Documentation
Projects
Resources

Get Help from Others

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

Resources

Skip to end of metadata
Go to start of metadata

Download demo data

A sample anonymized data set, including 5,000 patients and 500,000 observations, is available for the following Platform releases (note that demo data for OpenMRS Platform releases and will not work for OpenMRS Reference Application releases):

  File Modified
ZIP Archive demo-2.0.1.sql.zip OpenMRS Platform 2.0.1 demo dataset 2016-11-21 by Daniel Kayiwa

  File Modified
ZIP Archive demo-1.12.0.sql.zip 2016-03-21 by Bharat Akkinepalli

  File Modified
ZIP Archive demo-1.11.0.sql.zip 2015-02-08 by Kaweesi Joseph

  File Modified
ZIP Archive demo-1.11.0.sql.zip 2015-02-08 by Kaweesi Joseph

When installing this demo data, the initial password for the user 'admin' is 'Admin123'. You should change the password after installing the demo data.

Use the following MySQL queries to create your database and import the data, then deploy OpenMRS:

Download large demo data

This is a very large dataset that can require a long time to install and/or upgrade. We include for developers needing to do performance testing; however, in most cases, the smaller demo datasets will not only meet your needs, but will be less painful/slow to work with. This large demo data set contains thousands of patients and the addition of program data.

  File Modified
ZIP Archive large-demo-data-1.9.7.sql.zip 2015-08-12 by Willa Mhawila
ZIP Archive large-demo-data-1.8.0.sql.zip Latest Large data set - see note below 2011-10-25 by Burke Mamlin

 

Older versions

For 1.4 and below, you will need to run the update-to-latest-mysqldiff.sql for that version after running this sql file.

  File Modified
ZIP Archive demo-1.9.0.zip OpenMRS 1.9.0 demo dataset 2014-09-22 by Wyclif Luyima
ZIP Archive Demo-1.8.0.sql.zip OpenMRS 1.8.0 demo dataset 2011-10-25 by Burke Mamlin
ZIP Archive Demo-1.7.1.sql.zip OpenMRS 1.7.1 demo dataset 2011-02-07 by Michael Downey
ZIP Archive Demo-1.7.0.sql.zip OpenMRS 1.7.0 demo dataset 2011-06-19 by Wyclif Luyima
File Demo-1.6.0.sql.zip OpenMRS 1.6.0 demo dataset 2010-11-29 by Michael Downey
File Demo-1.4.0.23-mysql.zip OpenMRS 1.4.0.23 demo dataset 2010-11-29 by Michael Downey
File Demo-1.3.3-mysql.zip OpenMRS 1.3.3 demo dataset 2010-11-29 by Michael Downey
File Demo-1.2-mysql.zip OpenMRS 1.2 demo dataset 2010-11-29 by Michael Downey
File Openmrs-demo-sql-1.1.0.zip OpenMRS 1.1.0 demo dataset 2010-11-29 by Michael Downey
File Openmrs-demo-sql-1.0.54.zip OpenMRS 1.0.54 demo dataset 2010-11-29 by Michael Downey
ZIP Archive demo-1.11.0.sql.zip 2015-02-08 by Kaweesi Joseph

  • No labels

15 Comments

  1. The first time I tried to import this demo data, I got an error related to the patientflags_tag_displaypoint table. I don't remember exactly what the error was. For my database that table was empty, so I dropped it and then was able to import the demo data file with no problems.

  2. Hi Mike,

     

    Thanks for working on this, I thought we want to have demo data not to specify a db, i.e a user should be able to import it into any db named anything else besides openmrs without having to edit anything in the script.

    1. Yes, that's what I would have liked to see too.  I didn't add that demo data set (you did, didn't you?), I just ran it on my machine yesterday and noticed that it dropped and created a database named openmrs, rather than just using the current database.  So, if you can fix that bug in the demo data script, you can feel free to remove my warning comment above (smile)

  3. Ah! ok, I will try to edit the script later today

  4. I did a successful install of OpenMRS 1.9.3 Enterprise WAR Package version with the initial demo data, with java version 1.7.0_03, tomcat 6.0.35 and mysql 5.5.31 on Ubuntu Server 12.04.2 LTS.

     

    mysql> SELECT username FROM users;

    +----------+

    | username |

    +----------+

    |                |

    | daemon |

    +----------+

    2 rows in set (0.01 sec)

     

    mysql> SELECT system_id FROM users;

    +-----------+

    | system_id |

    +-----------+

    | admin |

    | daemon |

    +-----------+

    2 rows in set (0.00 sec)

     

    mysql> SELECT given_name, COUNT(*) FROM person_name;

    +------------+----------+

    | given_name | COUNT(*) |

    +------------+----------+

    | Horatio | 3 |

    +------------+----------+

    1 row in set (0.00 sec)

     

    I was able to login with the admin account and browse around.

     

    Then i decided to download and load demo-data into mysql

    mysql> use openmrs;
    mysql> source demo-1.9.0.sql

    mysql> SELECT COUNT(*) FROM person_name;

    +----------+

    | COUNT(*) |

    +----------+

    |     5284 |

    +----------+

    1 row in set (0.01 sec)

    I restarted tomcat6
    When i log in with the admin/test account i get the following error;
    The following error occurred at startup: 
    Unable to start OpenMRS. Error thrown was: Should not be here because updates were run previously
    org.openmrs.module.ModuleException: Unable to start OpenMRS. Error thrown was: Should not be here because updates were run previously.

    And also i assume there should be an admin user in the users table, but this is my results.

    mysql> SELECT username FROM users;

    +----------+

    | username |

    +----------+

    | NULL |

    | daemon |

    +----------+

    2 rows in set (0.01 sec)

     

    mysql> SELECT system_id FROM users;

    +-----------+

    | system_id |

    +-----------+

    | admin |

    | daemon |

    +-----------+

    2 rows in set (0.00 sec)


    I have tried different scenarios to resolve this issue, and the only the option i was left with is to drop the database and restart the 'initialsetup' process with an empty database.

    After doing so and reloading demo-1.9.0.sql, i am back to this same point again.

     

    Any help is kindly appreciated.

    1. Which version of OpenMRS did you install?

      1. Hi Daniel

        I installed the OpenMRS 1.9.3 Enterprise WAR Package version

  5. To finally get OpenMRS 1.9.3 war package going with demo data demo-1.9.0.sql, with java version 1.7.0_03, tomcat 6.0.35 and mysql 5.5.31 on Ubuntu Server 12.04.2 LTS, i had to approach the

    installation like an upgrade. I am not sure if this is what i should have done initially, but i did not see instruction as to whether or not.

    1.  Undeploy OpenMRS if already running
    2. Remove the previous openmrs-runtime-properties file, and ther files and folders in /usr/share/tomcat6/.OpenMRS
    3. Create a new openmrs database
      mysql -u -p;
      mysql> CREATE DATABASE openmrs;
    4. load the demo-data, source demo-1.9.0.sql
      mysql> use openmrs;
      mysql> source /home/jawara/mysql/demo-data/demo-1.9.0.sql
    5. Deploy openmrs in tomcatWeb Application Manager
    6. Open web browser and go to openmrs url to start the initial setup.
      http://xxxx:8080/openmrs

     

    Initial set up options:

    • English
    • Advanced
      Step 1 of 5
    • Set Database connection and Yes then set Database name
      Step 2 of 5
    • No, No, Yes then set Username and Password
      Step 3 of 5
    • Yes, Yes
      Step 4 of 5
      Step 5 of 5
    • Set information
    • Overview of settings
    • Task to execute; Update the database

     

    ## Errors

    A core module failed to start, 'core'

    Solution:

    Restarted tomcat and Retried the install set up options process

    http://xxxx:8080/openmrs

     

    When installing this demo data, the initial password for the user 'admin' is 'test'. You should change the password after installing the demo data.

    ## Error

    At this point i was unable to login, the default credentials did not work.

    Solution:

    Reset forgotten admin password from openmrs-guide.pdf.


    SELECT DATABASE()

    mysql> SELECT user_id,system_id,username FROM users;

    +---------+-----------+----------+

    | user_id | system_id | username |

    +---------+-----------+----------+

    | 1 | admin | NULL |

    | 2 | daemon | daemon |

    +---------+-----------+----------+

    2 rows in set (0.00 sec)

     

    mysql> SELECT username FROM users WHERE user_id = 1;

    mysql> SELECT username FROM users WHERE system_id = 'admin';

    +----------+

    | username |

    +----------+

    | NULL |

    +----------+

    1 row in set (0.01 sec)

     

    MySQL UPDATE command:

    ### admin username

    mysql> UPDATE users SET username = 'admin' WHERE system_id = 'admin';

    Query OK, 1 row affected (0.00 sec)

    Rows matched: 1 Changed: 1 Warnings: 0

     

    mysql> SELECT user_id,system_id,username FROM users WHERE system_id = 'admin';

    +---------+-----------+----------+

    | user_id | system_id | username |

    +---------+-----------+----------+

    | 1 | admin | admin |

    +---------+-----------+----------+

    1 row in set (0.01 sec)

     

    ### password

    mysql> UPDATE users SET password = '4a1750c8607d0fa237de36c6305715c223415189' WHERE system_id = 'admin';

    Query OK, 1 row affected (0.00 sec)

    Rows matched: 1 Changed: 1 Warnings: 0

     

    mysql> SELECT user_id,system_id,username,password FROM users WHERE system_id = 'admin';

    +---------+-----------+----------+------------------------------------------+

    | user_id | system_id | username | password |

    +---------+-----------+----------+------------------------------------------+

    | 1 | admin | admin | 4a1750c8607d0fa237de36c6305715c223415189 |

    +---------+-----------+----------+------------------------------------------+

    1 row in set (0.00 sec)

     

    ### salt

    mysql> UPDATE users SET salt = 'c788c6ad82a157b712392ca695dfcf2eed193d7f' WHERE system_id = 'admin';

    Query OK, 1 row affected (0.01 sec)

    Rows matched: 1 Changed: 1 Warnings: 0

     

    mysql> SELECT user_id,system_id,username,salt FROM users WHERE system_id = 'admin';

    +---------+-----------+----------+------------------------------------------+

    | user_id | system_id | username | salt |

    +---------+-----------+----------+------------------------------------------+

    | 1 | admin | admin | c788c6ad82a157b712392ca695dfcf2eed193d7f |

    +---------+-----------+----------+------------------------------------------+

    1 row in set (0.01 sec)

     

    ##### Launch OpenMRS

    http://xxxx.xxx.xxx.xxx:8080/openmrs/

    admin/test

     

    There was an error starting the module: Logic Module ('Reading' this alert 'reads' it for all recipients)

    You have <span id="unreadAlertSize">1</span> unread alert You have 1 unread alert

     

    So far seems to be working  fine.

  6. There is one thing that needs to be changed. I created a new database (given it another name other openmrs) and when I ran "source demo_file.sql" I noticed it dropped and created a new database using name "openmrs". I think this is not good because I actually already had another database by the same name. This is not desirable at all. The script should not assume that people do not have openmrs already. Imagine the frustration having your database dropped when you need it the most!!

    Note: I ran into this using demo.1.9.0.zip file.

  7. Definitely agree with Ahmed.

    I just installed OpenEMR to be able to use openMRS.  During openemr install i chose to name the database openmrs.  All the login configuration is setup with that.

    Then source demo-1.10.0.sql blew it away and when I login i get 

    Failure during database access! Check server error log

      

    1. OpenEMR is a completely different application, made by a different open source project, and is not compatible with OpenMRS.

      1. I think my point still stands though. 

  8. I've been trying, without success, to incorporate demo data into my OpenMRS 2 installation.  I managed to get OpenMRS 1.11.5 working with the data in demo-1.11.0.sql.zip, but when I attempt to apply the OpenMRS 2 modules, many of the modules fail to load.  I can provide specifics if needed, but I suspect this is a known issue.

    Is there any way to accomplish this?

    Thanks in advance.

    1. As you suspect, the OpenMRS 2.x Reference Application is not compatible with the demo data on this page. The application includes a way to generate demo patients, and I just added (a small bit of) documentation about this on the OpenMRS Reference Application 2.x Implementer Documentation page.

    2. David Triglianos, the 1.11.0 demo data file works only for the openmrs platform, applying the OpenMRS 2.x modules will not work just as you have encountered. If you are interested in setting up large data for the OpenMRS reference application i suggest running the reference application standalone since it is shipped with its own demo data though not sure whether it contains as much data as you may need.

      Otherwise you can post the failure messages so that we can look into them and solve them with you, that way we can have another demo data file uploaded that resolves those issues