The Roadmap describes the major features planned for the Interoperability Layer according to estimated timeline.

NOTE: This roadmap is constantly being reviewed and and will likely change as it is refined and as other requirements are defined and additional use cases introduced.


2018 Roadmap

 Q1 (Jan-Mar)Q2 (Apr-Jun)Q3 (Jul-Sep)Q4 (Oct-Dec)
Reference application development

Ensure full conformance to following IHE profiles:

  • MHD
  • PIXm
  • PDQm
  • ATNA
   
DocumentationSupporting documentation    
Design Workflows

 

   
Implement new workflows in reference implementation

 

   
Laboratory test new workflows

 

   

2017 Roadmap

 Q1 (Jan-Mar)Q2 (Apr-Jun)Q3 (Jul-Sep)Q4 (Oct-Dec)
Reference application development

Version 3.4.0 released on 23rd March

This is a new minor release of the OpenHIM. This release contains the following:

  • Large transaction that are updated via the API can now be truncated
  • Fix some weird numbers in transaction reporting
  • Node v4 and above in now required
  • Conflict detection between clients and role names
  • Bug fixes and performance improvements

See a full list of changes here.

aaaaaaaaaaaaaaaaaaaa

 

aaaaaaaaaaaaaaaaaa

Version 4.0.0.due for release

This OpenHIM release will contain:

  • Update node to version 9
  • Update Travis autodeploy
  • Remove unnecessary dependencies that broke with Node upgrade
  • Add HTTP Channel type method selector feature
  • Add Audit-trail for changes to the endpoints
Documentation   Version 4.0.0. documentation on Readthedocs This will include updated and expanded Implementers Guide and Specifications.

  

2016 Roadmap

 Q1 (Jan-Mar)Q2 (Apr-Jun)Q3 (Jul-Sep)Q4 (Oct-Dec)
Reference application development

Version 1.5.0 released on 16th Feb

This is a new minor release of the OpenHIM with a number of key changes.

 

Version 2.0.0 released on 2nd June 2016.

This is a new release of the OpenHIM
with some important breaking changes including

  • Revised authorisation system.
  • Default mediator channels are now not added
    automatically, they must be installed manually
    via the API or console. This give the user
    better control of how mediators act.
  • The OpenHIM now trusts the common
    rootCAs when verifying a clients certificate so it means that self signed certificates aren't required for clients.

Version 3.1.0 released on 12th September 2016.

This is a new major release of the OpenHIM. For a full list of changes see here

Version 3.0.0 released on 2nd August 2016.

This is a new breaking change release of the OpenHIM. For a full list of changes see here

Version 3.3.1 released on18th November .

Includes a minor packaging fix.

Version 3.3.0 released on18th November .

This is a new minor release of the OpenHIM.

To see all changes, click here

Version 3.2.1 released on1st November

 This is a new minor release of the OpenHIM. See a full list of changes here

2015 Roadmap

 Q1 (Jan-Mar) 2015Q2 (Apr-Jun) 2015Q3 (Jul-Sep) 2015Q4 (Oct-Dec) 2015
Workflow development
  • Discuss and design the ICP interaction workflow (see ICP white paper)
  • Alerting transaction - triggered by ICP perhaps
  • PDQm adaption to v2
  • How does the TS fit into the IL workflows
  • Consent management
  • How to better describe the IL services - do we need more detailed component architectures? (some of hidden transaction eg ATNA, consent)
  • Discuss and design the ICP interaction workflow (see ICP white paper)
  • Alerting transaction - triggered by ICP perhaps
  • PDQm adaption to v2
  • How does the TS fit into the IL workflows
  • Consent management
  • How to better describe the IL services - do we need more detailed component architectures? (some of hidden transaction eg ATNA, consent)
  • Discuss ODD Support
  • Discuss MHD support
  • Discuss ADX support
  • Discuss basic privacy and consent support
Reference application development 

Version 1.2 released on 30th April

See release notes here

Version 1.3 released on 20th July

see release notes here

Improved documentation for mediators and enhanced repository - due 30th September

IHE Connectathon preparation
Documentation  Focus on documentation to make it easier to get started with mediators 
Laboratory testing of workflow / reference application    

 

2014 Roadmap

 Q1 (Jan-Mar) 2014Q2 (Apr-Jun) 2014Q3 (Jul-Sep) 2014Q4 (Oct-Dec) 2014
Workflow development
  • Discuss and design the ICP interaction workflow
  • What does the IL need to do for OpenHIE version 1
  • Discuss and design the ICP interaction workflow (see ICP white paper)
  • Alerting transaction - triggered by ICP perhaps
  • Should the arch decouple the content to the transport
Reference application development
  • Refine OpenHIM core engine
  • Refine OpenHIM web management console
  • Develop mediator plug-in architecture
  • Develop mediator base scaffolding
  • Update save encounter mediator
  • Build support for secure sockets in the reference application
Laboratory testing of workflow / reference application

 

 

  • Begin deploying new OpenHIM core to RHIE preprod and other RSA work preprod
  • Deploy to OpenHIE demo server
  • No labels

1 Comment

  1. Derek Ritz

    Hi all.

    I'm putting the "Care Guidelines" references at attachments to our IL Roadmap page because of how much I believe lighting up the Integrated Care Pathways (ICP) support will be woven into and impact our IL evolution. I've attached two documents to this post:

    • the Every Woman Every Child guideline document (loooong version), which provides a really comprehensive description of the if/then logic behind WHO's maternal, newborn, and child health (MNCH) guidelines and what triggers care escalation (e.g. referral to hospital, etc.) or care plan changes (e.g. PMTCT protocols, etc.). The file is here: WHO MNCH guidelines
    • the WHO's recommended schedule of childhood vaccinations provides the guidelines for which immunizations should be given and when. This guideline is used by many countries (including Canada) to inform the schedule of vaccine administration. Not all countries are providing the same vaccine battery – it varies depending on many factors – but for the suite of basic vaccines the WHO guideline is quite universally followed. The file is here: Immunization_routine_table2.pdf

    I hope these guidelines, which we will (over the coming weeks) start to translate into BPMN, will provide us with a ready way to "dip a toe in the water" re: the weaving of ICP support into the very fabric of OpenHIE.

    Warmest regards,

    Derek.

This work is licensed under a Creative Commons Attribution 4.0 International License.