How flattering to know that this blog still gets so many daily hits!  KenyaEMR development and deployment is going strong.

I've asked those at I-TECH currently managing the Kenya work if they are maintaining a public blog elsewhere (I don't think I've heard it mentioned on the design calls).  If I get a link, I'll post it here.

Bill

KenyaEMR Release 2012.2.1

As anticipated, we have released KenyaEMR 2012.2.1. This is a minor update to the 2012.2 release and includes the following:

• ARV Drug Regimen remodeling and improved UI 
• Combined registration home and scheduling page into single dashboard 
• Added CD4% to medical summary chart 
• Improved user interface design elements (graphics and layout) for easier user interaction 
• Improved software administration interface to monitor system 
• Multiple bug fixes 
• Updates to current version of OpenMRS modules 

These features are outlined in more detail, along with the priorities and dates for the next release, in the Roadmap at http://tiny.cc/KenyaEMRreleases

You can view a working demo of the release at: https://demo.kenyaemr.org/openmrs/login.htm

Login is demo/demo.

Rowan has created a zipped version of the modules to update any existing servers, otherwise you will build a fresh virtual machine appliance for new installations. Please let us know if you have any issues with accessing the code.

KenyaEMR Release 2012.2 - Minimum Implementable Release (Woohoo!)

I’m excited to let you know that the team released KenyaEMR 2012.2. We are considering this the MIR - minimum implementable release.  This will be the first release that is going to be implemented into any of the facilities in Kenya - starting this week!  Main features included are as follows:

• Patient Registration 
• HIV C&T - MOH 257 
• TB Program C&T – TB Card 
• Obstetric History 
• Family History 
• Lab Results 
• Patient Summary with Trending 
• Limited Patient Scheduling and Calendar 
• Phase I Decision Support including Clinical Alerts 
• Phase I Retrospective Data Entry 
• National and Facility Level Reporting 
• Role Based Access and Workflows 
• User and System Administration Functions 
• Standard Build System, Virtual Appliance (Virtual Machine) 
• Versioning System in Banner 

These features are outlined in more detail in the Roadmap at http://tiny.cc/KenyaEMRreleases

You can view a working demo of the release at: https://demo.kenyaemr.org/openmrs/login.htm
Login is demo/demo.

Please let us know if you have any issues with accessing the code.

Once in a blue moon

Not much updating in July, but lots of progress.

Presented our KenyaEMR work to MOH early in the month (very well received)

Working on a few things:
1) expanding development resources
2) moving from the current rapid process to the development processes we already use for OpenELIS and iSante (more on that as those changes take effect)
3) paying a bit more attention to our communication through the site, this blog, etc.

See the demo system (June 26 posting link still valid) to set a sense of changes and progress.

Updated demo

Sorry for the lack of posts recently. I'm working on too many things simultaneously...

I updated the demo server this morning with the latest code, which includes a lot of UX fixes Bill and I discussed. We don't have the latest forms that Vincent has built in yet. I'll get to that as soon as I can.

Also, the demo server now has a new IP address:

https://69.91.227.20/openmrs
user: demo
pass: demo

Do we want a location hierarchy?

OpenMRS supports the idea of a location hierarchy. Is this something we want to use?

Imagine we do an installation at Amani Hospital. Is there any point in recording that certain encounters take place at different sub-locations? E.g. "Amani Hospital - Outpatient Clinic", "Amani Hospital - Outpatient Pharmacy", etc.

I'm assuming this is not helpful, but someone should let me know if they think it will be. :-)

The only reason I ask at all is because I've always sort-of wanted to use the feature, but never had a chance...

Default encounter dates and locations

A note to everyone who's working on HTML forms: make sure they all have the right default date and location set when being filled out, by doing something like this:

<encounterDate default="now" showTime="true"/><encounterLocation default="GlobalProperty:kenyaemr.defaultLocation"/>

It's important that we include times in our encounters, to support our point-of-care use case, and because if we don't set encounter times, they won't be assigned to visits correctly. (I just described this to Rajib in India on the OpenMRS developers list here.)


Getting the default location from a global property won't actually work until version 1.9.5 of HTML Form Entry is released, since I just made the fix today. (There are a bunch of open tickets in HFE 1.9.5, but I think we're going to need to push the versions back and release something including this specific fix before we deploy anywhere.)