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

Compare with Current View Page History

« Previous Version 15 Next »

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.

2015 Roadmap

 Q1 (Apr-Jun) 2015Q2 (Jul-Sep) 2015Q3 (Oct-Dec) 2015Q4
(Jan-Mar 2016)
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 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
 
  • No labels