The OpenHIE Meet-Up on Wednesday, December 14 at the Global Digital Health Forum had two simple goals:
One, to gather those working in different components and areas of OpenHIE’s architecture – or at least those working in health information systems – to explain some of the technical challenges they are facing.
Secondly, to find areas of collaboration with other participants to help solve these challenges.
We knew no challenges would be solved at the short breakfast meeting. But simply connecting the more than 20 participants from a variety of implementing groups provided an opportunity to strengthen the community built around OpenHIE.
IntraHealth International organized the meeting as an un-conference, which put the responsibility on the attendees to provide topics and lead discussions in a collaborative and open fashion. A number of people proposed discussion topics, and in the end, four participants initiated separate discussions:
Paul Biondich of Regenstrief Institute opened the meeting with a short welcome. Afterwards, attendees were invited to join the table of their choosing. In un-conference fashion, attendees were reminded they could participate as much as they liked, but the higher amount of participation would increase the quality of discussions.
Intro to OpenHIE: A wide ranging discussion, filled with OpenHIE novices and experts, covered the main components of OpenHIE and the fundamentals of its community. Members from teams working in two South American countries were in attendance, signaling interest in a region without much OpenHIE activity.
Expanding knowledge of OpenHIE in Sub-Saharan Africa: Anecdotal evidence shows that many eHealth practitioners working in Africa lack comfortability of talking about OpenHIE with their peers. The table discussed a few methods to increase knowledge and confidence, including study tours (where informatics professionals in one country travel to another country to discuss OpenHIE planning, performance and lessons learned) and creating a regional task force to increase training and dialog around OpenHIE. Increasing the amount of OpenHIE toolkit documentation was also discussed. A push to speak about OpenHIE use cases at the upcoming HELINA conference on April 23 to 26, 2017 in Burundi.
AeHIN history, processes used, next steps: Alvin Marcelo provided an overview of AeHIN and some lessons learned as the network has expanded. He overviewed the process AeHIN uses for assisting governments in South and Southeast Asia in the development of their health information systems and described both what is needed to continue to provide this support and AeHIN’s vision for the future.
OpenHIE Registries and Supply Chain Management: The conversation centered on aligning registries used by the health system and health care delivery with those used by supply chain practitioners. The link between young children and vaccine transactions is one example: Once a baby is born, she will appear in a health care delivery registry (like DHIS2) and a vaccine registry. Could the young child’s clinic record be leveraged for supply chain databases? Discussions also took place about attempting to align locations (of health centers) within a facility database with those used by supply chain registries.
After nearly one hour of conversation, each table reported out their findings and next steps. Business cards and contact information were exchanged along with promises to keep in touch and move the discussion to the next level. The participants then went off to join the final day of the Global Digital Health Forum.
Post by: John Liebhardt
We are pleased to announce the release of OpenHIE version 1.0 today, 05/15/15!
OpenHIE 1.0 includes exemplar open-source software that supports a collection of tested health information exchange (HIE) integration workflows that support common health care patterns. OpenHIE workflows specify interactions between Point-of-Service (PoS) applications and the HIE, as well as interactions between components that make up OpenHIE’s software architecture. OpenHIE 1.0 is not just software – it also includes a variety of informational artifacts and documentation. For details on how you can download, install and upgrade from your previous installations, please see our Release Notes Page.
Shaun (OpenHIE Chief Architect)
This week I was in Washington DC for the inaugural FHIR terminology services connectathon. This was the first of its kind: a connectathon focused on the terminology services portion of the FHIR specification.
The following organizations were represented:
The focus of the connectathon was on the two simplest operations in the terminology services API:
Hi there, I have put together a proposal of content for the new OpenHIE website: https://docs.google.com/document/d/1pHSFeDrIrStUJrPHswyfJCvrqAyLHE2fC_LsE09oENk/edit?usp=sharing Can I ask you to review and comment? I would love to deliver a 1st version to Jamie by the Friday morning (Oslo time
Source:: HMIS Mailing List
Hi All Just a reminder that there is a Shared Health Record Community call today Tuesday 24th February at *9 am EST / **4 pm CAT*. *Call Agenda:* – Feedback from Bangladesh trip and OpenSRP – CF – Implementation guide for the SHR – LT – Any other business Please remember to si
Source:: SHR Mailing List
Dear openHMIS community members, Tomorrow is our bi-weekly HMIS community call 🙂 Please suggest any item you want to discuss during this call *AGENDA*: – *HANGOUT*: https://plus.google.com/hangouts/_/event/clujo5f73ncevtjm0q0rr01pqs8?authuser=0&hl=en-GB If you would prefer to dial in p
Source:: HMIS Mailing List
Hi everyone, We will be having our Architecture call on Friday, February 27th, 2015 at 10:00AM Eastern Time (regardless of Daylight Saving Time or Standard Time). Agenda * OHIE v1 Update * IHE: broader goals and what we expect from working with IHE * What code systems
Source:: Arch Mailing List
Hi Everyone, An OpenHIE Facility Registry Meeting is scheduled for today at 11am EST. We will be having the typical Google Hangout. I will send out the Google hangout link shortly before the meeting starts. Notional topics will include, but are not limited to: 1) First Steps in how we wi
Source:: FR Mailing List