Primary mentor

Jan Flowers / Jim Sibley

Backup mentor

Bill Lober

Assigned to

Rahul Akula


OpenMRS allows you to store and access patient-level medical data in a flexible and configurable way. But a true, large-scale electronic medical record requires multiple software applications, all interoperating together. A large hospital might use OpenMRS for the clinical patient record, and a separate Laboratory Information System to store detailed information about specimens and samples. Or a national-scale medical record might have OpenMRS running as a centralized database-of-record, with multiple mobile applications connecting to it.

What these situations have in common is that when systems interoperate, one typically behaves as a Master Patient Index, allowing others to query it to find patient records.
At the MEDINFO 2010 conference, we demonstrated the potential for interoperability between OpenMRS and OpenELIS (an open-source Laboratory Information System). We wanted to describe and show a scenario where OpenMRS would be providing the master patient index and OpenELIS would be able to access patient demographic information from the OpenMRS database to avoid the necessity for dual data entry of that information into both systems. As the framework for this interoperability, we decided to implement the standards developed by the Integrating the Healthcare Enterprise (IHE) initiative. We successfully created a working demonstration of the concept, but more work is needed to make this interoperability link suitable for production use.


The purpose of this project is to complete the work started on developing the Patient Demographics Query (PDQ) Supplier module for OpenMRS. The PDQ Supplier module should be able to receive queries from external applications, parse those queries and perform searches against the patient tables in the database and finally, return demographic content for patients matching the search query criteria.

Required Skills


  1. Fully parse and handle basic query parameters (first and last name).
  2. Use dynamic/configurable values instead of hard-coded ones for the required message segments.

Extra Credit/Wish List

  1. Handle additional types of queries other than just first and last name (address, gender, wildcards).
  2. Handle PDQ continuation queries ("give me results 11-20", etc.).
  3. Add ability to register a patient.
  4. Add the ability to restrict the ability to query to specific institutions only (via configuration options page).

Project Plan

April 25 – May 23
May 24 – June 13
June 13 -- July 1
July 1 – July 18
July 18 – July 25
July 25 – August 1
August 1 – August 22