[this is a cross-post to the devs and general project list]
Hi all -
As you know we are working on many fronts in the FRED project.
This is an update to let you know what are some of the effort areas that have been going on in October, and the progress made with them. I think we all owe a big thanks to the folks in all the participating organizations for moving things forward. Note we link to some working google docs below; ask for access if you want it. Everything is work in progress.
Overall project charter
The first one has been establishing the goals and roadmap for '13 - writing up a draft and starting to sign up partners for it. That concept sheet stays true to the original intent of FRED I believe, but adds the importance of supporting country implementation as a goal of the project; and attempts to provide clear metrics for what we are aiming for as a collective by end of next year. Reality is always more amazing than planned, but having initial bearings make sure we all know what we are going into. Everyone in this group has both thought leadership and implementation responsibilities, so those initial directions will be reviewed with the whole group in time. Feel free to chime in the early drafts here:
Mission, Strategies, Objectives, Risks, Example Activities and Deliverables
As we start getting more exposure (e.g. OSCON, country implementations, PEPFAR and other funders meeting each other etc) it is important to have a simple explanation of what this effort is all about for the world.
We have started working on a communications frame whose content will be used for an online landing page and brochure-like material. This will then be part of a larger OHIE communication effort, but it is important to make sure people understand these are building blocks for their health information system - can be used separately but are ‘better together’. Our main audience is implementing countries - which breaks down into an ecosystem of MOH officials, MOH data managers, local tech support groups, international tech-savy NGOs and funders. We ned to create content that is simple & coherent for the areas where these folks’ interests intersect; and specialized pages to address the information needs that are not shared (e.g. some folks will want to see what is the process of implementing this - others will want to see API references).
Regenstrief has brought in a group called PSA to work on supporting this effort; we need to coordinate a bit more; but I’m sure we’ll converge. In the meantime please chime in here if you are interested - this is a very early draft! but it will give you a sense of how we are thinking about it.
Audiences, Goals, Content Areas - very early draft
I was very happy this week as we had a great technical call, in preparation to close up a v1.0 soon. We organized some of the pending discussion items/proposals into a backlog, and we are taking votes in making things in or out of scope of the v1.0 API. Next call we will start the voting process to ‘accept’ spec elements into the 0.9 draft; to make sure we all know what the ‘latest good’ from which to do proposals. Tightening our workflow will not only make these calls more efficient, and in my perception, more enjoyable; but also will create an environment where additional folks can engage as they want.
It is really nice to see a clear and prioritized list of tech items to be discussed; and folks from Columbia, HISP, Dimagi and InSTEDD taking votes by raising hands on a Google Hangout. BTW, this hangout worked well and I suggest we move onto that as a platform for the future calls; if there are no concerns we'll update the invite with Kelly.
We have reviewed the user stories and created a prototype configuration of their data dictionary in the staging cloud instance of resource map, as a ‘sandbox’ from which to be able to get feedback from them. It is important to learn from the Tz experience as we are trying to find the optimal materials for implementing countries to assess, implement and evaluate HIE components efficiently; and we will be distilling approaches that can be used by other OHIE components. We also don’t want to get ahead of ourselves and over-engineer an engagement into a waterfall process that would be unnecessarily error-prone and lengthy for countries. The theme is to advance pragmatically, simultaneously applying and harvesting proven practices that can help the next cycle and country.
Overall project management
As a note, there is much budget & proposal work going on for the continuation of Rwanda’s reference implementation work under RHEA, and if you see me oscillate in availability in the public coordination of this these weeks it’s because I’m pulled into some of that admin work. It is important our funders understand the value of this activity, that they support it well so it’s set up for success, and also that they appreciate how much has been achieved so far, relative to the rest of whats going on in the ehealth world. I still think we can do much better but small & real steps will get us there.
Thanks all sorry for the long email but these are good efforts by a lot of people and it’s nice to see them converging.
For November, our activities will be:
Continuing work on the overall charter; and communications efforts
Closing on API 1.0 specs, and start any coding required
Dimagi, HISP and Columbia will start describing scenarios for interaction with FR to be implemented for demonstrations in the upcoming months
Getting to the next step for Tanzania evaluation; circling back to them with the configuration and getting their feedback
Thanks all for your contributions and look forward to the next set of activities!
Eduardo Jezierski, InSTEDD, CTO