This week I start working on a project to help gather medical information in villages throughout Rwanda, so the project I’ve been working on for the past couple of months is officially over. I’ve written my postmortem and had a chance to recuperate from the travel (including the airline losing my baggage in London and a screaming three year old on an eight hour flight — horror stories best only hinted at).
But this last project looks as if it was about as successful as I could hope for, so indulge me a few moments while I tell you what we did.
While medical information is gathered throughout Uganda, reports are regularly written, and analysis is frequently done, sharing information between health care workers and officials is problematic. Until now, there was only one small central library at the Ministry of Health which held only a single stand-alone PC for accessing and reading electronic documents.
To make matters worse, the proprietary software for storing and accessing the electronic documents only accepted PDFs, so anything a doctor wrote in, say, Microsoft Word had to be converted before it could be used in the system.
With the help of the Knowledge Management (KM) team at IntraHealth, a few of us on the Informatics team put together a Joomla+KnowledgeTree combination that would allow health care workers and officials to upload any Office document, collaborate around them, and easily access them from any networked computer.
My work centered on the integration and initial set up of the software — putting it all together in a way that made the KM people happy. And, frankly, much of that work isn’t any different than what I could be doing in almost any Tech Shop or corporate environment. And for a while, it was like any software project, full of frustrations and delays. While KnowledgeTree was an obviously mature piece of software, I found some of its idiosyncrasies irritating and some of its capabilities anemic.
The real difference — the real satisfaction — came when I was finally able to sit down with the librarian at the Ministry of Health in Uganda and I heard him say “This is great, it is so much better and easier to than our current system! And we don’t have convert all our files to PDF first!”
It was a relief to hear those words. Until then, doubt still lingered. But after that meeting, while there was still a lot of work to be done and a lot of work that I wouldn’t be able to complete, now I knew that we had a successful, even worthwhile, product.
Even better, the technical people I worked with and trained as well as the Ministry workers all understood the usefulness and had the same goal in mind: fostering adoption of the new “electronic library” throughout Uganda.
Now, back to the work. Hopefully I’ll have another success story in a few months.
Posted by
Mark Hershberger on 8/14/2008 • Tags: Africa, Capacity Building, FOSS, Information Systems, Tools
No Comments Yet
Add Yours
I’ve had the opportunity to follow the development of OpenID and related technologies from afar for a couple years. Watching the good work of some friends who have developed ClaimID has opened my eyes to what the hurdles are in keeping a unique identity as we move more and more digital.
Here’s the problem: Identity on the web can be nefarious at best. An email address is at its heart temporary and often not the only unique email one person might have. Who hasn’t either contemplated or actually dumped an email address after a particularly bad week of spam? Identities are also defined online by the many services and sites we might have a login for. Yet these are usually different IDs - we can’t be sure of a person’s identity by looking at various accounts.
ClaimID is a great example of a way to combat this by allowing a person to manage their online identity themselves. Further, they are doing so by using the very simple and elegant OpenID protocol. The concept of OpenID being that we have a unique identity which allows us to log in to various services and sites with one single ID by allowing the services to retrieve credentials from a trusted identity provider of the user’s choosing. This last part being key: “of the user’s choosing”.
OpenID is still very much in a phase where, although it is being adopted by some well known services, it is still in roll-out. Although this means we can’t use our OpenIDs in many places yet, the tools for developers to add OpenID support are available and ready for use.
This could be very important for our work here at IntraHealth. This week there have been a couple of different projects plans come up which have made me think about how we could use OpenID. In both cases it comes down to patient records and tracking. The thought of such use in places like Uganda has made me step back and wonder why this type of implementation hasn’t been talked about much in Western medical records and services development. Perhaps it has and I have missed it, nonetheless I do feel like a tool like OpenID could present the beginnings of the type of security which is needed to provide patients and health care givers records online or on handheld devices.
The trick here is creating the trusted identity provider. In the case of the Ugandan projects we could propose that the Ministry of Health become a trusted provider for a Ugandan citizens “Medical ID”. This ID could then be used on the already growing list of servers and applications which have to have unique identifiers for their patients. The same system could also be used to identify health workers as they pass from systems like iHRIS Qualify to a training center’s application - therefore more easily (and automatically) updating either system’s records on what type of training the health worker has completed. The beauty of the OpenID process is that, if implemented correctly, it allows the patient or worker to be in charge of their own identity and who they trust with the creation and storage of that identity. As long as we keep them first in any design, they win.
Posted by
David Mason on 1/14/2008 • Tags: Design, Development, Software, Technology, Tools
No Comments Yet
Add Yours
