Page tree

Versions Compared

Key

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

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 4 and 2020.

The first release candidate of OpenNCP for Wave 4 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: 

Last updated

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.

Table of Contents



Table of Contents


Previous versions of this page and list: 

Approach to Work Items refinement


The following categories were identified. The existing items were grouped using these categories and the following priorities were set for each category.

  1. Change Proposals
  2. Security (CIA) Improvements
  3. OpenNCP Software Testing
  4. OpenNCP Interoperability Testing
  5. Configuration Improvements
  6. Release Management
  7. Documentation/ Guidelines Improvements 
  8. Generic Improvements and Other Work Items 

Next steps:

  • Core functionality - items with high impact on the core functionality.
    • Solution Provider will focus on the items in this category.
  • Non-Core functionality - items with medium/low/no impact on the core functionality.
    • MS will be asked to contribute to the items in this category.
  • Priority 1 (High), 2 (Medium), 3 (Low) inside each category, depending on the needs of the Community.
    • To be prioritized by the OpenNCP Steering WG.
  • Some functionalities are already implemented at MS level and could be integrated in the reference implementation.
    • Ask MS (survey?) which functionalities they developed could benefit the OpenNCP Reference Implementation.

1. Change Proposals Implementation for Wave 4


The change proposals must be considered with priority within an eHDSI release lifecycle.

#

Core/

Non-Core

WORK ITEM TITLEShort description (and output)Priority

CURRENT STATUS / Planned Release Date (Wave)

NEXT STEPSJIRA Detailed Issues
1CoreInteroperability Specifications - Implement CP-036

CP-eHealthDSI-036_Enable dispensation discard operation

  • NCPeH Architecture documents
  • Audit Trails Profile
  • XDR Profile
1

Status
colourYellow
titleIn Progress
 / Wave 4

OpenNCP RC v5.0.0 was released beginning of July 2020. The new KPI defined for the Dispense Discard operation will be implemented in the next release.

EHNCP-1955 - Implementation of Dispense Discard KPI  OPEN OPEN

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1944

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1389

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1259

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1258


2CoreInteroperability Specifications - Implement CP-042CP-eHealthDSI-042: Implement International Search Mask
  • Identity Management Specifications

Make it possible for a Country A to publish an image (or images) regarding the Identification Card to be used by the system.

  • 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 is needed. - Confluence space will be used to share these configurations between countries.
  • Take into consideration that other materials can also be shared.
1

Status
colourGreen
titleImplemented
 / Wave 4 (OpenNCP v5.0.0 RC)

  •   From Solution Provider, this new feature might be took in consideration after a priority has been assigned by the steering. A draft CP is currently ongoing and this request might be handled at the same time.
  •  This request is now included in the change proposal on the ISM topic. 

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1905


3Non-CoreOpenNCP and epSOSWeb PORTALS - Implement CP-035

CP-eHealthDSI-035_Set as mandatory Nature of Patient Summary

2

n/a

OpenNCP Test Portals are not maintained by the Solution Provider and should not be used by MS in Routine Operation as such, as they do not meet the necessary security or other requirements. The Portals are only used for OpenNCP testing purposes.

SP maintains 2 Test Portals, because MS are using both of them.

To be discussed with MS and clarify the situation of the OpenNCP Portals. Two options are suggested by the OpenNCP Steering WG:

  1. SP does not maintain the Portals anymore (both versions are deprecated) and creates a new Test Portal (to be used for testing purposes only).
  2. SP keeps only one Portal and integrates it in the official release of OpenNCP.

Normal MS behavior: They use the current Test Portals in Production. To be discussed to what extent MS customized/ improved the Test Portals solution. Some MS started developing their own solutions.

: OpenNCP Portals will only be used for Solution Provider testing purposes, this implementation was not intended to be used by MS.


4Non-CoreOpenNCP and epSOSWeb PORTALS - Implement CP-036CP-eHealthDSI-036_Enable dispensation discard operation2

n/a

: OpenNCP Portals will only be used for Solution Provider testing purposes, this implementation was not intended to be used by MS.


5
CP-eHealthDSI-033: Enable indicating dosage period length



Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1912

6
CP eHealthDSI 035



Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1895


2. Security (CIA) Improvements Implementation


#

Core/

Non-Core

WORK ITEM TITLEShort description (and output)Priority

CURRENT STATUS / Planned Release Date (Wave)

NEXT STEPSJIRA Detailed Issues
1Non-CoreEstablish an NCPeH AVAILABILITY SERVICE (Heart beat service)
  • 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)
2

Status
titleNot started

eHDSI Technical Workgroup needs more info about the expectation of this item.

(Not relevant at this time)

Might be consider as out of scope for Service Provider.

: Even if it requires high effort, it would be an important feature for MS in routine operations.

  • A step by step approach should be considered: first, a static Confluence page to share the info, then an automatic solution with part of the information etc.

2Core

OpenNCP Security improvements

  • 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).
1

Status
colourRed
titleImpeded

(depending on SP resources)

eHDSI Technical Workgroup needs more info about the expectation of this item.

  •  Details on the current SP work to be provided (JIRA issues). - Jerome SUBIGER

Add link to JIRA from Renaud. - Jerome SUBIGER

3CoreSplit read/write database access
  • Database connection pools segregated by Application/ component/ context/ server. - Read-only access to DB will be introduced (new feature).
  • Currently, there is no possibility to split read/write access on the DB. Specify which user each component is using.
3

Status
titleNot started

  • Consider as optional and low priority.

: Item was clarified by Jerome SUBIGER and moved in this category from the ''Documentation/ Guidelines'' category.

: In case needed, architecture has to be changed. - Which components need to be protected?

  •  Configuration can be customized by MS. - Input on how to segregate the read/write DB access to be provided by Jerome SUBIGER.
  •  Database connection pools segregated by Application/ component/ context/ server. - Currently this exists, request to be clarified byAntoine CHAUDIERES - Info sent on  

4CoreOpenATNA-Viewer and eADC improvements
  • 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.

Provide a secured UI to access the ATNA messages and eADC KPIs - improve the security of the ATNA messages:

  • INVESTIGATE if ATNA requirements for SECURE NODE configuration are being fulfilled by the current implementation.
  • Possibility to access the eADC component and export the KPIs.

Improve eADC report/export functionality:

  • Consider the possibility for an automatic creation of a CSV file.
1

Status
colourRed
titleImpeded

(depending on SP resources)

eHDSI Technical Workgroup needs more info about the expectation of this item.

  •  : Details on the current SP work to be provided (JIRA issues) - by Jerome SUBIGER

Analysis on going in the TWG, based on current and future KPIs.

: Solution Provider started working on this item.

: The ''Improve eADC report/export functionality'' was agreed to be merged with this item.



3. OpenNCP Software Testing


#

Core/

Non-Core

WORK ITEM TITLEShort description (and output)Priority

CURRENT STATUS / Planned Release Date (Wave)

NEXT STEPSJIRA Detailed Issues
1

Non-Core 

Perform SECURITY testing and describe NCPeH TG vulnerabilities
  • Design test plan
  • Perform tests
  • Report on results
1

Status
colourYellow
titleIn Progress

Depends on Security Team availability. NL could help on this item.

SP believes that this type of tests depend heavily on MS National Infrastructure and implementation, as the tests at OpenNCP Reference Implementation level might not be relevant (as it is emulating the National Connectors).

: Questionnaire for MS was created in Confluence: https://ec.europa.eu/cefdigital/wiki/x/hAOZDw


2Non- CorePerform PERFORMANCE/LOAD testing and describe NCPeH capacity
  • Design test plan
  • Perform tests
  • Report on results
  • Confirm fining on known issue of capacity bottleneck
1

Status
colourYellow
titleIn Progress

Depends on Security Team availability. NL could help on this item.

SP believes that this type of tests depend heavily on MS National Infrastructure and implementation, as the tests at OpenNCP Reference Implementation level might not be relevant (as it is emulating the National Connectors).

: To wait for FR, IE and LU test results investigation on this matter, before opening the discussion with the OpenNCP Community.


3CoreDesign and implement Integration tests for Key OpenNCP components

Integration tests are useful and should be considered with priority - input is needed from all MS, in order to reuse the available CDAs and keep the tests relevant

1

Status
titleNot started

To be considered by SP.

Not relevant at this time

: Technical WG recommends to extend the scope of this item to include the integration tests as well. Steering WG agrees with this approach.

: At the moment and with the current implementation, SP cannot design unit tests. Some unit tests could still be designed for some components, but they are not considered relevant.

  • The integration tests should be more fit for current eHDSI purpose, if input from MS is used.

4CoreDesign and implement Unit tests for Key OpenNCP components

Unit tests are deprecated and they bring no added value at the moment

3

Status
titleNot started

To be considered by SP.

: Redesign of the Unit tests will be considered in the future, with a lower priority and depending on the availability of the SP team.

: Useful to design Unit Tests for new components, not for the past implementation.


5CoreDefine a procedure to Quality Assurance the released artefacts

Describe the process and strategy on SP side to ensure the quality check of the OpenNCP artefacts being released.

2

Status
titleNot started

To be considered by SP.

eHDSI Technical Workgroup needs more info about the expectation of this item.

: Description of the item was added.



4. OpenNCP Interoperability Testing


#

Core/

Non-Core

WORK ITEM TITLEShort description (and output)Priority

CURRENT STATUS / Planned Release Date (Wave)

NEXT STEPSJIRA Detailed Issues
1Core

Having the Interoperability Validations (CDA, XDS Metadata) embedded in the OpenNCP

(Enable "standalone/on the fly" verifications (CDA) to detect and prevent system degradation)
  • 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)
1

Status
colourRed
titleImpeded

IHE implementation needed.

eHDSI Technical Workgroup needs more info about the expectation of this item.

Clarification needed from the SWG about the expectation.

  • To which level of detail would we like to go (CDA, XDS messages etc.)?

: Rationale for this implementation: Possibility to continuously check/ validate the messages in Production (for security reasons) - what cannot be detected by current testing.


2Non- CoreAdvocate and reinforce the relevance of having an eHDSI Test Platform (i.e. Gazelle) accessible through TESTA

eHDSI Test platform is currently deployed on an EC Amazon infrastructure with mappings available only over Internet. Aim of this item is to provide an access from Testa network for Member State.

3

Status
colourBlue
titleIn Progress

  • Portability of eHDSI Test platform on Testa ongoing.
  • Current issue: eHDSI Test Platform cannot support currently two environments working in parallel (over TESTA and Internet).


5. Configuration Improvements


#

Core/

Non-Core

WORK ITEM TITLEShort description (and output)Priority

CURRENT STATUS / Planned Release Date (Wave)

NEXT STEPSJIRA Detailed Issues
1CoreReview configuration files and database properties

Simplify/improve the Configuration - two parts: OpenNCP configuration and Access to OpenNCP Gateway (ATNA, KPIs, OpenNCP Properties, SMP Editor)

  • 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.


2

Status
colourYellow
titleIn Progress

  • Waiting feedback from the task responsible.
    Not participating anymore to the TWG.
  • Remind ASIP

 Update expected from the TWG:

  • For the first part: the OpenNCP configurations cannot be improved more, because of the current architecture (each module has its own configuration) and technology used.
  • For the second part, work is in progress:

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1082

  •  Avoid file reference in database, prefer JNDI for web applications, use convention over configuration - To be clarified by Antoine CHAUDIERES



2CoreDeploying wars on tomcat or running jars should work out of the box or with only minimal documented setup

Be able to test/use each OpenNCP component independently.

3

Status
colourRed
titleImpeded

Cannot be improved, because of the current architecture and technology used.

  • It would facilitate the testing and automation testing of OpenNCP components.

3CoreAvoid database creation by wars/jars and publish SQL scripts instead
  • Currently, there is only one process using this script (ATNA).
  • Refactoring of the ATNA component is needed, which implies high effort.
2

Status
colourGreen
titleDone
 / TBD

Planned during the summer 2019 + related to the task: official Oracle database support from OpenNCP.

  •  : OpenNCP Database Initializer has been implemented. - JIRA to be provided by Jerome SUBIGER

4Non-CoreOpenNCP Technology Release "packaging" - Dockerfiles

INVESTIGATE the possibility to provide (and maintain) Dockerfiles as OpenNCP deployment reference.

3

Status
titleNot started

  • Might be considered.
  • No real request for this topic.
    TWG propose to remove this item from the list. - opinion not applicable anymore, we should reuse what MS implemented.

: Dockerfiles facilitates the deployment. Ask MS to share their implementation of Docker.

  •  IE will share their implementation - Eamon COYNE - Can this implementation be shared and integrated in OpenNCP?

5Non-CoreIncrease support of technology stacks (WebLogic) used in production environments 
3

Status
titleNot started

  • Low priority.
  • Rationale for prioritization: Only ES is currently using this technology stack. High effort  is needed to support this technology stack.
  • The approach is that the MS which needs the technology stack, implements the solution and does a hand-over to the OpenNCP Community.

6
Evolve and upgrade the OpenNCP default infrastructure (e.g., Tomcat, MySQL, migration from Oracle Java to Open JDK)
?

Status
titleNot started


EHNCP-1957 - OpenNCP default infrastructure evolution and upgrade OPEN


6. Release Management


#

Core/

Non-Core

WORK ITEM TITLEShort description (and output)Priority

CURRENT STATUS / Planned Release Date (Wave)

NEXT STEPSJIRA Detailed Issues
1CoreReview and re-activate the OpenNCP Continuous Integration service

Automated tests are necessary, it is not possible to test everything manually.

2

Status
titleNot started

Not relevant at this time

: Depending on the progress of the creation/usage of Integration tests. 




7. Documentation/Guidelines Improvements


#

Core/

Non-Core

WORK ITEM TITLEShort description (and output)Priority

CURRENT STATUS / Planned Release Date (Wave)

NEXT STEPSJIRA Detailed Issues
1Non-CoreProvide a Quick Start Guide for System Admin

Improve the OpenNCP Installation Overview

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

Status
colourBlue
titlein progress

Writing the Quick Start Guide based on TWG recommendation

  •  Ask MS who already have such a guide to provide it as input - Jerome SUBIGER

2Non-CoreGuidelines on Deployment Schemes
  • (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.
3

Status
colourBlue
titleIn Progress

  • Review current proposal made based on STW comments
  • From SP, it is difficult to provide specific guidelines, as they depend on the specificity of each MS.

SP already provided a description (Confluence page) of what EC has in place in order to implement and test the solution.

  •  Provide a Confluence page/template where MS could describe their own architecture/ implementation (traffic needs, server capacity, test environments etc.) - template to be presented in the OpenNCP Community meetings - Simona-Maria TIPLEA

3Non-CoreGuidelines OIDs usage in eHDSI and in particular for NCPeHs

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

3

Status
colourBlue
titlein progress

  • Releasing Confluence page of OIDs guidelines based on TWG recommendation.

4Non-Core

Improve documentation on National Connector

Provide clear documentation about APIs to be used while integrating the NCPeH with CLINICAL DATA REPOSITORIES in the national infrastructure, as well main workflows, business and security considerations.3

Status
titleNot started

eHDSI Technical Workgroup needs more info about the expectation of this item.

: Solution Provider considers that this item can only provide information on the scope of eHDSI and not beyond, as we have no knowledge as concerns the MS national infrastructure.


5Non-CoreImprove documentation on Client Connector

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.
3

Status
titleNot started

eHDSI Technical Workgroup needs more info about the expectation of this item.

: Solution Provider considers that this item can only provide information on the scope of eHDSI and not beyond, as we have no knowledge as concerns the MS national infrastructure.


6Non-CoreDocument every maven module roles

Status
colourRed
titleImpeded

eHDSI Technical Workgroup needs more info about the expectation of this item.

: Solution Provider suggests to remove this item from the Backlog, as Maven tool is used in a standard way in eHDSI. The details about the specific eHDSI components are already described in the following document:



8. Generic Improvements and Other Work Items


#

Core/

Non-Core

WORK ITEM TITLEShort description (and output)Priority

CURRENT STATUS / Planned Release Date (Wave)

NEXT STEPSJIRA Detailed Issues
1




: Improvements from JIRA agreed to be considered for W5 OpenNCP Stable Release (v5.1.0) to be added here. - Jerome SUBIGER

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1957

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1952

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1946

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1942

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1909

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1878

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1958

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1852

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1730

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1755

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1741

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1730

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1675

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1663

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1587

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1532

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1510

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1504

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1494

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1488

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1485

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1349

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1256

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1195

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-1141

Jira
serverCEF Digital Tracker
serverId0efbb216-d112-3760-b195-d6de284e38c7
keyEHNCP-953



Implemented Work Items


#

Core/

Non-Core

WORK ITEM TITLEShort description (and output)Priority

Release Date (Wave)

NEXT STEPSJIRA Detailed Issues
1








Deprecated Work Items


#

Core/

Non-Core

WORK ITEM TITLEShort description (and output)PriorityNEXT STEPS
1n/aCreate matrix or data flow diagram for internal and external OpenNCP exchanges

Provider clear documentation about:

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

eHDSI Technical Workgroup needs more info about the expectation of this item.

: Solution Provider considers that this item is answered by the eHDSI Architecture documentation below. We suggest to remove this item from the Backlog.

: Agreed to be removed.

2n/aOrganize bi-weekly meetings for all community - raising awareness on key topics and developments

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)
n/a

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

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

: Agreed to be removed.


3n/aEstablish an ISSUE log with issues affecting routine operations
  • Transparently document any known issues regarding OpenNCP technology.
    • (notifications enabled so that all system admins are aware)
  • ?? Define a "SLA" for issues affecting routine operations.
n/a

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.

  • To be clarified.

: Solution Provider considers this as part of the Support activities. It should be removed from this backlog.

: Agreed to be removed.

  • First part to be considered under the Operations/Support activities.
  • SLA part to be raised at the appropriate Governance level by the concerned MS (e.g., eHMSEG).
4n/aEstablish a clear methodology for eHDSI Support activities


n/a

eHDSI Technical Workgroup needs more info about the expectation of this item.

Prepare Draft OpenNCP Dev&Ops development management method.

Consolidate OpenNCP Dev&Ops development management method.

: Solution Provider considers this as part of the Support activities. It should be removed from this backlog.

: Agreed to be removed.

5n/aMake the OpenNCP code generic to the type of CDA document exchangedEven 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, etc.n/a

eHDSI Technical Workgroup needs more info about the expectation of this item.

: Solution Provider suggests to remove this item from the Backlog, as this is an implementation decision following the IHE Technical Framework.

: Agreed to be removed. We can still exchange different types of CDAs with the current implementation using the current or new IHE profiles, which meand that OpenNCP implementation is already agnostic of CDA exchanged. As regards the code, it cannot be made more generic than it is now.

6Non-CoreError handling improvement

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.
2
  • A task force leaded by the eP cluster is ongoing about this topic. So the TWG needs priority and clarification/request for change on this topic.
  •  Technical WG will provide some Technical Guidelines on this topic.
  • : Agreed to be removed, as it is now being investigated as part of the PS and eP Clusters work items. A change proposal is expected in this case.