Versions Compared

Old Version 18

changes.mady.by.user Linda Taylor

Saved on

compared with

New Version 19

changes.mady.by.user Linda Taylor

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 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) 2015Q2 Q3 (Jul-Sep) 2015Q3 Q4 (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) 2014Q1 (Jan-Mar) 2015
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
  • 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)
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