The OHIE Facility Registry Community is a free and open initiative comprised of individuals, NGOs, and governments seeking to leverage facility registries to improve health outcomes in resource limited settings. A registry achieves this by providing a focused service to collect, curate, store and distribute standardized and current facility and resource data to the diverse network of eHealth and mHealth systems in a country.
The Facility Registry Community is equipped to provide field tested, open source, and scalable technology and implementation solutions to create a facility registry using local requirements and industry standards. These are formed out of field experience gained from implementations ongoing in countries such as Rwanda and Tanzania.
Reliable and accurate facility information will help you manage your resources better, so you can ensure patients receive a higher quality of care.
Send patients to the closest and most reliable health facility, by utilizing up-to-date information about existing clinical infrastructure and services.
Identify and address the gaps in your health services and infrastructure,by analyzing the geographic distribution and coverage of health facilities.
Define your data & permissions, track changes, access, and maintain your master facility list from any device. You can also integrate with other system.
We are collaborating to make facility data easier to manage and to ensure that facility registry tools and services can easily and effectively share facility data in a simpler, manageable, secure, and scalable way. If you would like to join the technical discussion, please join our Facility Registry Community to contribute to the Facility Registry API or work with the Reference Facility Registry Tool.
Meet other implementors to learn from their experiences and work on common goals. Join Our Community Group
Learn about best practices and access expertise, technologies and standards around facility registries. Visit Our Wiki Page
The OpenHIE community has drafted an Implementation Guide based on the experience of implementers and technologists active in our community. It’s a open resource to help guide full implementations or small enhancements.
The implementation process begins by first identifying the current stakeholders and motivations driving interest in a health facility registry. This step is intended to answer the question: Why do we want a new or different facility registry? By defining the goals and objective of the core stakeholders, subsequent activities are rooted in their needs.
A facility registry should be responsive to users’ needs and the local context. User stories and data specifications are two ways to describe: “What will the facility registry achieve and How should it operate?”. A primary objective of this guide is to promote and facilitate a country driven and user requirements based process. The ideal solution will be responsive to users’ needs and their context. To complete the activities in Step 2, an in-country meeting of stakeholders is highly recommended and can expedite the process.
Using the draft data specifications and user stories from Step 2 as the foundation to move forward, the next step is to initiate an agile and iterative development process of the facility registry. The main outcome from this step is the implementation a tangible first version of the new or updated registry.
Once an initial version of the facility registry is implemented, a process of resolving the remaining the prioritized user stories will begin. The iterative development of the tool should be ongoing and also incorporate new stakeholders and/or user stories as they are identified. Close collaboration between technical and non-technical stakeholders is key to agile development to ensure technical solutions align with users needs. The core outcome from this step is a facility registry with the user stories completed to create a minimally viable tool.
After completion of Step 4, the facility registry will be at a point ready to be scaled more broadly among users and other systems that can provide or consume facility data. The goal of this step is to engage nationally with users and systems to ensure the management and institutional processes are in place for ongoing curation, governance, and data utilization.
After scaling the facility registry and initiating the core integrations, it should be expected that requirements and requests for the registry will evolve over time. For this reason, ongoing support and continued agile/iterative strategies should remain in place. This can be organized by the roles of the technical support and implementation teams to triage requests for data, system enhancements, integrations, operations support or general troubleshooting among users.
The facility registry community is made up of a diverse group of organizations and individuals interested in supporting facility registries. If you want to learn more about facility registries, what OpenHIE is, or what our community is working on, feel free to reach out to us and get connected! There are a couple different ways to get started:
1: Email the community organizers
2: Join and follow our facility registry community group
3: Join one of our facility registry community meetings
Every 4 weeks the OHIE FR community meets via google hangouts. Details on the agenda and link for the hangout are shared ahead of each meeting via the facility registry community google group (https://groups.google.com/forum/#!forum/facility-registry).