You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Overview

The OHIE’19 Hackonnect-a-thon is scheduled for Friday 8th November.

The OpenHIE Connectathon is a merger of two exciting types of meetings. This is a technical space for software teams and architects to engage and get their “hands-in” or “on” OpenHIE itself and see it materialised. Combining the principles of a connectathon and a hackathon we are excited to provide a space for teams to connect their existing tools to OpenHIE workflows and use-cases as well as give the community an opportunity to propose low hanging fruit use cases for the groups to work on. Recognising that many attendees may be new to OpenHIE there is no better way than actively engaging in designing, developing, configuring, implementing and connecting to an OpenHIE architecture to learn the fundamentals and build the relationships that you will need going forward.

Review of OHIE ‘18 Hackonnnect-a-thon

Objectives

The attendees of the Hackonnect-a-thon are aiming to:

  • 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

So what does this really mean/look like?

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.


SLACK Channel

Registration link for slack team.  Once you register, join the #ohie-hackonnect-athon channel. 

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.

HIE Component Tooling

Component GroupTool / SolutionOrganisation / ContactDescriptionOnline Demo/Sandbox
IOLOpenHIM (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 available to advise of how mediators and additions can be made.

TBD
SHR

HEARTH

(https://github.com/jembi/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
CR / MPI



FR



LMISOpenLMIS (www.openlmis.org)VillageReach, OpenLMIS Community

OpenLMIS is an electronic logistics management information system that manages and automates logistics processes at over 10,000 health facilities across 9 country implementations in Africa. In the OpenHIE landscape, key areas of interoperability are: Facility Master Data, Product Master Data, and pushing data out to HMIS and third-party reporting/dashboard/analytics tools.

Connectathon offering:

OpenLMIS is available at a demo site in the cloud with a documented REST JSON API. This demo site is available for teams to log in and access the APIs to demonstrate integrations.

TBD
HWR



TSOpen Concept Lab (OCL)Regenstrief/Apelon

OCL provides cloud-based community-driven terminology management. OCL lowers implementation barriers by 1) providing access to major terminologies, such as the Columbia University eHealth Laboratory's interface terminology (CIEL, utilized in OpenMRS) and other international standards like ICD-10 and 2) supporting standards based operations to enable interoperability.

Connectathon offering:

OCL is available at a demo site for teams to utilize on various levels, from exploring how standardized terminologies and indicators can be represented to testing out the REST API and initial FHIR Terminology Services.

TBD
UHCopenIMIS (www.openimis.org)

openIMIS Community

openIMIS is an open-source MIS designed to facilitate the move towards Universal Health Coverage (UHC) by supporting the management of various types of social health protection schemes, including management of policies - financial information but also included medical supplies and services -, insurees - incl. Enrollment and renewals - and claims.

Connectathon offering:

A connectathon instance will be available to analyse and demonstrate ongoing work to develop integrations with POS applications and potential OpenHIE registry components.

TBD
HMISDHIS2 (www.dhis2.org)JSI

DHIS2 is a tool for health information collection, management, analysis and reporting. It is the current reference software for the HMIS component within the openHIE architecture.

Connectathon offering:

A sandbox instance of the latest version of DHIS2 software will be available locally and on the cloud specifically for use within the connectathon/hackathon.

TBD
POS (mobile)CHT Core Framework (communityhealthtoolkit.org)Medic Mobile (medicmobile.org)

The Community Health Toolkit includes resources to support full-featured, scalable digital health apps that equip health workers to provide better primary health care in their communities. The Core Framework can support many languages, run offline when needed, and work with basic phones (via SMS), smartphones, tablets, and computers. App developers are able to define health system roles, permissions and reporting hierarchies, and make use of five highly configurable areas of functionality: messaging, task and schedule management, decision support workflows, longitudinal person profiles, and analytics.

Connectathon Offering:  

A sandbox environment and a few teammates from Medic Mobile will be available to connect with other components in the ecosystem.

TBD
POS (mobile)CommCareJSI

CommCare is an open source mobile platform designed for data collection, client management, decision support, and behavior change communication. CommCare's mobile application is used by client-facing community health workers in visits as a data collection and educational tool and includes optional audio, image, and video prompts. Users access the application-building platform through the website which Dimagi operates on a cloud-based server.

Connectathon Offering:  

A sandbox environment of CommCare will be available in the cloud for use to connect with other components in the ecosystem.

TBD

Current Challenges

Taking into account systems and teams attending we are looking for groups and members to list out the current challenges that they are posing to the attendees. Please add your challenges/hacking ideas below

TitleDescriptionAmbassador
OpenHIM Mediator DevelopmentTutorial and training on developing an OpenHIM mediator.Jembi Health Systems
CommCare - DHIS2 Interface

Automate data exchange between CommCare and DHIS2 using the OpenHIM, to limit duplication of efforts and data entry errors for health workers  collecting community health information using the CommCare mobile app and managing aggregate data on CommCare server and in DHIS2.

The two systems (CommCare and DHIS2) have the same organization unit structure and data elements which will make the data exchange process less complicated.

JSI
openIMIS Data Exchange and InteroperabilityTBDopenIMIS Community
Community Health ToolkitThe Community Health Toolkit (CHT) includes resources to support full-featured, scalable digital health apps that equip health workers to provide better primary health care in their communities. This stream will look at opportunities to incorporate the CHT into the OpenHIE framework as a mobile POS, interfacing with HIE components e.g. - creating a patient, health worker, or facility in the CHT could create the corresponding records in the Client Registry, Health Worker Registry, or Facility Registry.

(Medic Mobile) Michael Kohn

Computable Care GuidelinesTBDCCG Working Group, WHO
DHIS2/FR - Administrative Area Registry InterfaceDevelop an interface between DHIS2 or Facility Registry with the Administrative Area Registry used in Tanzania.Oswald Luoga

Lightning Talks

Lightning talks are a 5-10 min presentation that allows you to present your challenge, product, tool etc to the technical community. The goal is to get your ideas out into the forum and call persons to chat to you during the event. Please put down your topic and a description of what it is about and your details so that we can schedule the talks. If you are looking for a slide guideline it is max 5 slides (prefer 1-3).

TopicPresenter
OpenHIM - a rapidly scalable interoperability layer

Jembi Health Systems

Community Health Toolkit (CHT)

Michael Kohn (MedicMobile)

Schedule

TBC

  • No labels