...
Connect existing tools to OpenHIE foundational registries
Learn how to implement workflows within their tools
Jointly work together to implement common use-cases within an OpenHIE architecture
Self-organise into learning sessions and create breakaway groups to discuss topics / show ideas
Great so what does this really mean/look like?
Well we are looking forward to the attendees (that is you, the participant) bringing their technical strengths to the table and bringing their systems to engage with others in the field. These sessions are focused at providing the space for the architects, the analysts, the developers and the integrators within the communities to meet and discuss how to solve active problems as well as start on the fundamentals of connecting systems. We are expecting a combination of the following to emerge:
- Focused technical discussions around how best to engage with the deeper aspects of data exchange on a fundamental standards level and workflows.
- Generating sequence diagrams and talking about what data systems curate and what would be available in the other systems and documented models and technical specifications to get it there.
- Bringing your technical questions and started projects/code to any persons representing tools and technologies and engaging with them and others on how best to architect and develop the solution
- Bring your code and application and your development skills to the table and try to connect to systems that are present and possibly consume an OpenHIE workflow and share data with other system
- Learn more about the technical nature and how to model things in FHIR and or how others have done it
- Design decisions that impact scale and speed as wells as how different implementers select different development patterns and architectures to solve their challenges.
- And other discussions that flow.
So what will be available to connect to and test against?
This space is a technical space and we encourage participants to "put their hands up" as to what they will be brining and what they will be making available to the participants to engage with. Depending on the number of participants we are considering scheduling a lightning session where groups can rapidly (5min/5 slides) present their tools as an intro. Currently the following teams and tools have put their hands up to be at the event and have technologies available.
| Component Group | Tool / Solution | Organisation / Contact | Description | Online Demo/Sandbox |
|---|---|---|---|---|
| IOL | OpenHIM (www.openhim.org) | Jembi Health Systems (www.jembi.org) | The OpenHIM is an interoperability layer that facilitates OpenHIE workflows. It allows easy configuration and setting up of channels and endpoints that allow systems to connect and exchange information. The use of mediators allows implementer/developers to add logic and custom flows to the channels. This is the current reference technology for the IOL community of OpenHIE. Connectathon offering: The OpenHIM will be setup and available for teams to create their own channels and the Jembi team be avaiable to advise of how mediators and additions can be made | TBD |
| *New | SHR | HEARTH | Jembi Health Systems (www.jembi.org ) | HEARTH is Jembi's HL7 FHIR server that serves as an SHR on many of Jembi's internal projects. This FHIR server allows for FHIR resource management and has been used in multiple ways to manage more than just patient health data; such as patient management, facility mangement etc. Connectathon offering: HEARTH will be setup and available for teams to leverage and engage with the endpoints that include the storage and retrieval of FHIR resources from the tool | TBD |
| *New | OpenCRVS (www.opencrvs.org) | Jembi Health Systems (www.jembi.org ) | Plan International (https://plan-international.org/) | OpenCRVS is an open offering to countries who are looking for a means to better manage Cival Registration and Vital Statiscs (CRVS) needs. The Plan and Jembi team have developed a first version/prototype of the tool based on the OpenHIE architecture and have modeled interfaces to other systems using FHIR. Connectathon offering: OpenCRVS will be available for teams to discuss how best to leverage data as well as how to create CRVS event notifications (such as birth notifications) from other health systems | TBD |
The schedule
The connect-a-thon schedule follows a looser flow than a formal agenda with the introduction sessions being sharp and pointed to get the teams aligned to the technical tasks at hand. For the duration of the event all 3 rooms will be open and available for teams to engage in and create breakaway sessions of informal discussions and learnings. Leveraging the unconferencing style the attendees will propose and create their own agendas and topics and “vote with their feet” as to what is of interest.
...