Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

Primary mentor

~janflowersUnlicensed user / ~jsibley Unlicensed user

Backup mentor

Bill Lober

Assigned to

~arahulkmit Unlicensed user

Background

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.

...

  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

...

Milestones

...

  • Mid-Term milestones
    1. Remove all hard-coded pieces and use standard HL/7 parsing (HAPI).
    2. Get the module to a point where it can successfully handle a simple query using first and last name and return the appropriate results over HTTP(S).

...