Page tree
Skip to end of metadata
Go to start of metadata

The purpose of this page is to provide a detailed understanding on the current status of work items in progress related to OpenNCP, with special focus on Wave 3 and 2019.

The first release candidate of OpenNCP for wave 3 is planned to be made available by .

This page is updated, at least, once per month and used during OpenNCP related meetings to monitor progress.

Last update:  Jul 19, 2019 11:14

Governance of this Work Items Registry

  • The Work Items (requirements) are REQUESTED by the Steering WG.
  • The Technical WG is requested to analyse and design the best fit solution.

Implementations is up to eHDSI Solution Provider and any developers coming from MS or industry.

For the full description of the work items, a specific page should be created (child to the current page) and follow, if possible, the "Product Requirement" page template

Previous versions of this page and list: 

Work ITEMS


Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

#WORK ITEMOBJECTIVE5Service or Artefact1Short description (and output)Type2

Priority3

STATUS4

EFFORT7NEXT STEPSASSIGNED TO6
1Provide a Quick Start Guide for Developers1.aOpenNCP Documentation

Facilitate access to source code repositories

Provide build instructions

Improvement

(Wave 3)

DONE


OUTCOME:

https://ec.europa.eu/cefdigital/wiki/x/UzKHAw

2Provide a Quick Start Guide for System Admin1.aOpenNCP Documentation

Improve the OpenNCP Installation Overview

  • Facilitate access to deployable artefacts
  • provide instructions regarding key configuration items
Improvement

Wave 3

IN PROGRESS

0.1PM
  • Writing the Quick Start Guide based on TWG recommendation
  • Clarification needed by steering
3Guidelines on Deployment Schemes1.aeHDSI Guidelines
  • (e.g. 1 server, multiple servers, load balancers, environments[DEV, TEST, PrePROD, PROD] );
  • Guidelines on generated data (audit trails and logs: eadc, atna, NRO & NRR, test logs); and recommendations on maintenance actions.
  • Database connection pools segregated by Application/component/context/server
New feature

Wave 3

IN PROGRESS

0.2PM
  • Review current proposal made based on STW comments
4Guidelines OIDs usage in eHDSI and in particular for NCPeHs1.aeHDSI Guidelines

Provide to eHDSI stakeholders a clear picture on the use of OIDs in Core Services as well as Generic Services (NCPeH services)

New feature

Wave 3

IN PROGRESS

0.3PM
  • Releasing Confluence page of OIDs guidelines based on TWG recommendation.
5Review configuration files and database properties1.bOpenNCP Technology
  • suppress duplicates and
  • think at a global configuration tool (current configuration files are designed for allowing the replacement of any component independently, which is not used)
  • Avoid file reference in database, prefer JNDI for web applications, use convention over configuration
  • INVESTIGATE if ATNA requirements for SECURE NODE configuration are being fulfilled by current implementation.
Improvement

Wave 3

IMPEDED


  • Waiting feedback from the task responsible.
    Not participating anymore to the TWG.
  • Remind Asip
6Deploying wars on tomcat or running jars should work out of the box or only with only minimal documented setup.1.cOpenNCP Technology
Improvement

<<2019>>

NOT STARTED



OpenNCP Technical WG
7Avoid database creation by wars/jars and publish SQL scripts instead.1.cOpenNCP Technology
Improvement

Wave 3

NOT STARTED

0.5PM
  • Planned during the summer 2019 + related to the task: official Oracle database support from OpenNCP
8OpenNCP Technology Release "packaging" - Virtual Machine
1.cOpenNCP Technology
  • INVESTIGATE the possibility to provide (and maintain) fully configured Virtual Machine with OpenNCP key configs.
New feature

(Wave 3)

NOT STARTED


  • No real request for this topic. TWG propose to remove this item from the list.
OpenNCP Technical WG
9OpenNCP Technology Release "packaging" - Dockerfiles1.cOpenNCP Technology
  • INVESTIGATE the possibility to provide (and maintain) Dockerfiles as OpenNCP deployment reference.
New feature

Next Waves

NOT STARTED


  • No real request for this topic.
    TWG propose to remove this item from the list.
OpenNCP Technical WG
10Organise bi-weekly meetings for all community - raising awareness on key topics and developments1.dOpenNCP Community

Organise OpenNCP Community meetings according to the defined policies (frequency): https://ec.europa.eu/cefdigital/wiki/x/miEZAg

  • Steering WG (monthly)
  • Technical WG (monthly)
  • Community (bi-weekly)
  • Task Forces (when needed)
Routine Operation

<<2019>>


IN PROGRESS


Meetings calendar: https://ec.europa.eu/cefdigital/wiki/x/zCAZAg

Meetings minutes: https://ec.europa.eu/cefdigital/wiki/x/-yEZAg

OpenNCP Steering WG

OpenNCP Technical WG

11

Organise 2019 OpenNCP Boot Camp

1.dOpenNCP Community

20 to 24 of May, 2019, Warsaw (Poland)

Event Page: https://ec.europa.eu/cefdigital/wiki/x/WqaCB

Routine Operation

<<2019>>


DONE


Preparation of event page

Elaborate Draft programme

Upon for Registration

produce consolidated programme

OpenNCP Steering WG
12Wave 1: maintain (bug fix) OpenNCP 2.5.x2.aOpenNCP Technology
  • 2.5.5   (planned ) Wave 1 - Operation ready (to be used by Wave 1 NCPeHs)
  • 2.5.z HOT FIXES (until Jun 2019, when all NCPeH must update to x.y.x - Wave 2 Specs)
Improvement

<<2019>>



DONE


Maintenance planned until end of June 2019

Current release:

2.5.5 - Wave 1 Operation Ready Hotfix

Solution Provider
13Wave 2: release, update and maintain (bug fix) OpenNCP 3.0.x2.bOpenNCP Technology
  • 3.0.0   (planned ) Wave 2 - Stable
  • 3.0.z  Wave 2 - Operation Ready
    • [MANDATORY FOR OPERATION FROM JULY 2019 onwards]
    • to be used by Wave 1 and 2 NCPeHs
  • x.y.z HOT FIXES (until Jun 2020, when all NCPeH must update to 2.7.x - Wave 3 Specs)
  • 3.1.0  
Improvement

Next Waves


DONE


Maintenance planned until end of June 2020

Current release:

3.0.0.RC2 - Wave 2 Realease Candidate

3.1.0 - Wave 2 Operation Ready

Solution Provider
14Wave 3: release, update and maintain (bug fix) OpenNCP x.y.z2.bOpenNCP Technology
  • 4.0.0.RC1 Wave 3 - Release Candidate 1
  • 4.0.0.RC2 Wave 3 - Release Candidate 2
  • 4.0.0  Wave 3 - Stable
  • x.y.z  Wave 3 - Operation Ready
New feature

Wave 3

IN PROGRESS

3PM
  • Implementation of Wave 3 release has just started


15Perform SECURITY testing and describe NCPeH TG vulnerabilities3.aOpenNCP Technology
  • Design test plan
  • Perform tests
  • Report on results
New feature

(Wave 3)

IMPEDED


Depends on Security Team availabilityOpenNCP Technical WG
16Perform PERFORMANCE/LOAD testing and describe NCPeH capacity3.aOpenNCP Technology
  • Design test plan
  • Perform tests
  • Report on results
  • Confirm fining on known issue of capacity bottleneck
New feature

Next Waves


NOT STARTED


Depends on Security Team availabilityOpenNCP Technical WG
17Establish an ISSUE log with issues affecting routine operations3.a

OpenNCP Community

  • Transparently document any know issues regarding OpenNCP technology
    • (notifications enabled so that all system admins are aware)
  • ?? Define a "SLA" for issues affecting routine operations
Improvement

Wave 3

NOT STARTED


This artefact has to be clarified as it might be also out of the scope of the Service Provider or TWG. Current issues affecting OpenNCP are available and public across JIRA and release notes.OpenNCP Steering WG
18Increase support of technology stacks used in production environments3.aOpenNCP TechnologySupport Oracle DatabaseImprovement

Wave 3

IN PROGRESS

1PM

Agreed upon the support to be provided.

Implement Oracle database support for Wave 3 releases

Service Provider
19Split read/write database access3.aOpenNCP Technology(specify which user each component is using).Improvement

(Wave 3)

NOT STARTED


  • Consider as optional and low priority
OpenNCP Technical WG
20Avoid logs creation in database as it is happening in the protocol terminators (client and server).3.aOpenNCP Technology

Consider:

a) configuration tool or

b) raise sys admin awareness of possible configs where to store log files.

Improvement

(Wave 3)

IN PROGRESS

0.1PM
  • LogBack DG mechanism has been removed.
  • Writing Confluence page explaining the logging into OpenNCP (point b).
OpenNCP Technical WG
21Improve eADC report/export functionality3.aOpenNCP Technology
  • Consider the possibility for an automatic creation of a CSV file
Improvement

(Wave 3)


IN PROGRESS

0.4PM
  • Analysis on goind based on current and future KPIs.
OpenNCP Technical WG
22Enable "standalone/on the fly" verifications (CDA) to detect and prevent system degradation3.bOpenNCP Technology
  • Define, implement and enable a set of critical verifications to be performed by the NCPeH TG whenever a transaction takes place (in routine operations)
  • Evaluate the possibility to integrate [part of] the CDA validator as a standalone tool distributed with the releases (in order to run it locally on the NCP node)
Improvement

(Wave 3)

NOT STARTED


Clarification needed from the SWG about the expectationOpenNCP Technical WG
23Establish a NCPeH AVAILABILITY SERVICE (Heart beat service) 3.cOpenNCP Technology
  • for sake of monitoring and early detection of NCPeH TG unavailability and automatic service availability discovery
  • The service should go beyond a network availability (i.e. PING) it should verify as many as possible of the technical layers in NCPeH (i.e. network availability, application server, specific web service, and main database communication: (the answer should provide a list of the services available in that NCPeH, thus enabling an automatic configuration of the portals as they would know who has which scenario operational)
New feature

(Wave 3)


NOT STARTED


Might be consider as out of scope for Service Provider.OpenNCP Technical WG
24Establish a clear methodology for development activities4.aOpenNCP Community
Improvement

(Wave 3)

NOT STARTED


Not relevant as all the development activities are supported by DG Santé and MS are not participating actively to the implementation.development activities are performed according DG Santé methodology.

OpenNCP Steering WG
25Ensure that a freshly checkouted OpenNCP project compile & pass every unit test without configuration4.aOpenNCP Technology
Improvement

(Wave 3)

NOT STARTED


Not relevant at this time (blocked by item 26)eHDSI Solution Provider
26Design and implement unit tests for Key OpenNCP components4.aOpenNCP Technology
New feature

(Wave 3)

NOT STARTED


Not high priority currentlyeHDSI Solution Provider
27Review and re-activate OpenNCP Continuous Integration service4.aOpenNCP Technology(automated tests are necessary, it is not possible to test everything manually)Improvement(Wave 3)


NOT STARTED


Not relevant at this timeeHDSI Solution Provider
28Advocate and reinforce the relevance of having a eHDSI Test Platform (i.e. Gazelle) accessible through TESTA.4.aTest Framework
Improvement(Wave 3)


IN PROGRESS


  • Migration process under evaluation and test.
29Establish a clear methodology for support activities4.aOpenNCP Community
Improvement

(Wave 3)

IN PROGRESS


Prepare Draft OpenNCP Dev&Ops development management method.

Consolidate OpenNCP Dev&Ops development management method.

OpenNCP Steering WG
30Define a procedure to Quality Assure the released artefacts4.bOpenNCP Technology
Improvement(Wave 3)


NOT STARTED



OpenNCP Steering WG
31Create matrix or data flow diagram for internal and external OpenNCP exchanges4.cOpenNCP Documentation

Provider clear documentation about:

  • Which are the components included in OpenNCP
  • Dependencies between components
  • Internal (for other components) and External (for other applications) APIs
Improvement

Wave 3

NOT STARTED

0.1PM
  • Planned in August 2019
OpenNCP Technical WG
32

Improve documentation on National Connector

4.cOpenNCP DocumentationProvide clear documentation about APIs to be used while integration the NCPeH with CLINICAL DATA REPOSITORIES in the national infrastructure, as well main workflows, business and security considerations.Improvement

Wave 3

IMPEDED


Expectation not clear
33Improve documentation on Client Connector4.cOpenNCP Documentation

Provide clear documentation about APIs to be used by PORTALS in the national infrastructure, as well main workflows, business and security considerations.

  • If any, decouple any core functionality from the existing TEST PORTALS.
Improvement

Wave 3

IMPEDED


Expectation not clear
34Document every maven module roles4.dOpenNCP Documentation
Improvement

(Wave 3)

IMPEDED


Expectation not cleareHDSI Solution Provider
35Fix most critical/blocking Sonar alerts.4.dOpenNCP Technology.Improvement

(Wave 3)

DONE (READY TO BE RELEASED)


FIXED IN VERSION 2.5.5

https://ec.europa.eu/cefdigital/wiki/x/Ny9HB

eHDSI Solution Provider
36Make the OpenNCP agnostic to the type of CDA exchanged3.dOpenNCP TechnologyEven if already doing this in theory, the source code needs to be reviewed in order to check if this is really happening and to additionally perform improvements, e.g., rename "getPrescription" methods to "getDocument", do not expect specific eP/eD/PS OIDs, etcImprovement

Next Waves


NOT STARTED


??? STW needs to clarify thisOpenNCP Technical WG
37OpenNCP-Gateway security improvements3.aOpenNCP Technology OpenNCP-Gateway this component needs proper security implementation (e.g., credentials management, segregation of accesses, etc) and secure deployment (usage of TLS/SSL, etc, can be part of the deployment recommendations of SO-1).Improvement

<<2019>>

NOT STARTED



OpenNCP Technical WG
38OpenATNA-Viewer (keep or deprecate)3.aOpenNCP Technology

Decide if the OpenATNA-Viewer is to be kept/enabled.

This component doesn't have any authentication mechanism. Proper secure deployment (TLS/SSL, etc) could also be recommended (SO-1). Other option is to disable it and add its functionalities to the OpenNCP-Gateway. I'm not sure but I think MS like Finland have implemented smartcard authentication in this tool, learn from their experience.

Improvement

<<2019>>

NOT STARTED



OpenNCP Technical WG
39Error handling improvement3.aOpenNCP Technology

Add a bullet for "Error handling improvement". I believe the need for this will be quickly raised as soon as the first issues in Operation show up. Check some old discussions about this in Error Handling messages and Error messages handling. This issue is also part of the eP Cluster Work Items (Error handling improvement), where it has been better described.

  • The root causes of errors/warnings should be captured in eADC data to enable proper analysis
Improvement

(Wave 3)

IMPEDED


  • Waiting input from eP and Ps Clusters about the Errors Workflows.
  • Technical analysis blocked by eP & PS Clusters (Jerome SUBIGER )


OpenNCP Technical WG
40Make it possible for a Country A to publish an image (or images) regarding the Identification Card to be used by the system.3.dOpenNCP Technology
  • The purpose of this new property is to become available for Country B to use it at Portal level to asset the HP while identifying the identity trait to be used in the Patient Demographic query.
  • Double check with the initiative "Communication Materials" which actions are already in place and if this feature should be automated through the SMP or if other technical support (confluence space) will be used to share this configurations between countries.
  • Take in consideration that other materials can also be shared.
New featureNext Waves

NOT STARTED





Legend

1Service or Artefact2Type: 3Priority: 4STATUS:5OBJECTIVE6ASSIGNED TO7EFFORT
  • OpenNCP Technology
  • OpenNCP Documentation
  • OpenNCP Community
  • Interoperability Specifications
  • Test Framework
  • Audit Framework
  • eHDSI Guidelines
  • New feature
  • Improvement
  • Proof of Concept (PoC)
  • Bug Fix
  • Routine Operation
  • Wave 3: Must be ready on time for Wave 3 (30 April 2019 Release Candidate)
  • (Wave 3): If possible, ready for Wave 3; 
  • <<2019>> - should be completed until the end of 2019
  • Next Waves: In preparation for next waves

NOT STARTED

IN PROGRESS

IMPEDED

QUALITY ASSURANCE

DONE (READY TO BE RELEASED)


  1. Simplify the distribution and deployment of OpenNCP Technology
    1. Review the installation manual
    2. Reduce the configuration burden
    3. Provide a easy deployable solution
    4. Ramp-Up OpenNCP knowledge and experience
  2. Release new versions of OpenNCP as necessary for
    1. Routine Operations
    2. Testing purposes
  3. Increase OpenNCP technology robustness for routine operations
    1. Prepare OpenNCP to reach Technology Readiness Level Level 8 (currently assessed by Solution Provider as Level 7)
    2. Enable standalone/on the fly verifications (CDA) to detect and prevent system degradation
    3. Establish a NCPeH AVAILABILITY SERVICE (Heart beat service) for sake of monitoring and early detection of NCPeH TG unavailability and automatic service availability discovery
    4. Increase OpenNCP scalability and flexibility to deal with new use cases.
  4. Establish well defined Quality Assurance mechanisms for OpenNCP Development procedures and Released Artefacts
    1. Formalise and increase quality of development related procedures
    2. Design release quality assurance procedure
    3. Improve OpenNCP architecture and APIs description
    4. Improve Code Quality

  • eHDSI Solution Provider
  • OpenNCP Steering WG
  • OpenNCP Technical WG
  • OpenNCP Task Force
  • Member States

Amount of Person Month necessary to complete the task.

PM = Person Month

1 PM = 160hours per month

Examples

0,05 = 8 hours

0,1 =  16 hours

0,25 PM: 40 hours

0,5 PM: 80 hours

1.0 PM: 160 hours



  • No labels

1 Comment

  1. Hi Licinio, we have update working item N°5, but cannot update status, please review & update accordingly. Thank you very much. Have a great day.

    Dylan.