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

Highlights:

Table of Contents

1. Test Framework - Current Release

Framework ComponentLast UpdatePURPOSEOPEN POINTS

Test framework (1.2.2)

 


Describe the overall strategy and methodology for eHDSI Conformance and Functional testing.

  • Applicable for Wave 2 Test events


 

Support NCPeH participating in Test Events by providing guidelines and tools to facilitate the performance and management of test activities


  • Bug fixing on CDA Scrutiny Validators and Simulators (for pre-PAT use)

eHDSI Test Data (0.1.0)

September 2018

Provide documents to be used as reference for approval of the services
Certificates validation guidelines (1.0.0)

 

Provide guidelines to NCPeHs deploying CEF eDel. PKI certificates on how to prepared the validation of those certificates.
NCPeH Technical Gateway test instance

 

Provide a test partner (available through internet) allowing any deploying NCPeH to perform early tests regarding the interactions with another NCPeH Technical Gateway.

1.1 Previous releases

Test Framework ComponentDATEPURPOSEOPEN POINTS

Test Framework (1.2.0)

eHDSI Testing Platform (1.2.0)

 


Describe the overall strategy and methodology in eHDSI Conformance and Functional testing

TARGET:  eHDSI Wave 2 - Operation Ready [to be used in October 2018 Preparatory-PPT]

For Public Comment

Test Framework (1.1.0)

eHDSI Testing Platform (1.1.0)

 

eHDSI Wave 1 - Operation Ready (2017, June and September test events)
  • Scenario based Functional Testing

 

Support NCPeH participating in Test Events in selecting the right tests according to the national deployment planV1.0.0
Critical Test Data samples (0.1.0)

 

Provide documents to be used as reference for approval of the servicesRequire further refinement
Certificates validation guidelines (0.1.0)

 

Provide guidelines to NCPeHs deploying CEF eDel. PKI certificates on how to prepared the validation of those certificates.Temporary, until the validator is updated to reduce this need.
Test Framework (1.0.0)

 

The objective of the eHDSI Testing Framework is to describe the test strategy used in order to conformance test:

a) the NCPeH technical gateway (e.g. peer to peer workflow tests),

b) the clinical documents exchange (e.g. documents scrutiny tests),

c) the Functional use cases (e.g. end to end functional testing).

Functional Testing missing

Critical Test Data

 

Support NCPeH participating in Test Events in selecting the right tests according to the national deployment plan




2. Test Sessions Roadmap

EVENTWaveDATESTATUSMORE INFO
eHDSI Production Environment testingW4

to  3 months

TBC


eHDSI Upgrade-PPTW3 > W4

to  4 weeks

TBC


eHDSI Formal-PPTW4

to  5 weeks

TBC


eHDSI Production Environment testingW3

to  5 months

TBC


eHDSI Preparatory-PPTW4

to  5 weeks

TBC


eHDSI Connectivity (TESTA & Central Services)W4

to  2 weeks

TBC


eHDSI Upgrade-PPTW2 > W3

 to 4 weeks

TBC


eHDSI Formal-PPTW3

 to 5 weeks

  • Func. E2E: 24 to 28 of Feb, 2020

TBC


eHDSI Production Environment testingW2

 to 3 months

TBC


eHDSI Preparatory-PPTW3

  to  5 weeks

  • Func. E2E: 21 to 25 of Oct, 2019

TBC


eHDSI Connectivity (TESTA & Central Services)W3

From to  5 weeks


PLANNING


Week 1 (3 to 7 Jun) - Registration and Pre-Requisites verification

  • Wave 1>2 - Upgrade
  • Wave 2 - Re-TESTING
  • Wave 3 - Connectivity

Week 2 (10 to 14 Jun) - Connectivity

  • Wave 1>2 - Upgrade
  • Wave 2 - Re-TESTING
  • Wave 3 - Connectivity

Week 3 (17 to 21 Jun) - pre-PAT (Conformance testing)

  • Wave 1>2 - Upgrade
  • Wave 2 - Re-TESTING

Week 4 (24 to 28 Jun) - PAT (Conformance testing)

  • Wave 1>2 - Upgrade
  • Wave 2 - Re-TESTING

Week 5 (1 to 5 Jul) - Functional End-2-End

  • Wave 1>2 - Upgrade
  • Wave 2 - Re-TESTING
eHDSI Upgrade-PPTW1 > W2
eHDSI Re-TESTINGW2
OpenNCP Boot CAMPW3 (Wx)

to  

PERFORMED

eHDSI Formal-PPTW2

 to 5 weeks

PERFORMED

https://ec.europa.eu/cefdigital/wiki/x/noRqB
eHDSI Production Environment testingW1

 to 5 months

IN PROGRESS

performed by NCPeHs authorised to start routine operations
eHDSI CDA Scrutiny - Test SessionW2December 2019

NO NEED

Considered not needed and was replaced of ad hoc verifications
eHDSI Ad-Hoc-PPTW1

 to 5 weeks

PERFORMED

https://ec.europa.eu/cefdigital/wiki/x/35gSB
eHDSI Preparatory-PPTW2

 to 5 weeks

PERFORMED

https://ec.europa.eu/cefdigital/wiki/x/35gSB
eHDSI Re-TESTINGW1

 to 3 weeks

PERFORMED

https://ec.europa.eu/cefdigital/wiki/x/3q6-Aw
TESTA & Central Services ConnectivityW2

 to 1 week

PERFORMED

Not available
eHDSI 2018 Technical Boot-CampW1/2/3/4

 to 2 days

PERFORMED

https://ec.europa.eu/cefdigital/wiki/x/2tVUAw
eHDSI Formal-PPTW1

 to  5 weeks

PERFORMED

https://ec.europa.eu/cefdigital/wiki/x/RRjoAg
TESTA & Central Services ConnectivityW1

 to 1 week

PERFORMED

https://ec.europa.eu/cefdigital/wiki/x/B6NUAw
eHDSI Preparatory-PPTW1

 to  5 weeks

PERFORMED

https://ec.europa.eu/cefdigital/wiki/x/GRHoAg
eHDSI Preparatory-PPTW1

to  2 weeks

PERFORMED

https://ec.europa.eu/cefdigital/wiki/x/vhytAg
IHE CATW1

to 1 week

PERFORMED

Event Announcement (marketing)

Technical Support (technical hands on)

eHDSI 2017 Technical Boot-Camp

to 3 days

PERFORMED

https://ec.europa.eu/cefdigital/wiki/x/4kkZAg



  • No labels

4 Comments

  1. Shouldn't the last table include the Wave 1 Ad-hoc Projectathon?

    1. Hello Joao


      We definitely should. Thank you very much for reporting it.

      • Just added it as follow up to your remark.


      I took also the opportunity to map in time the roadmap of test events for Wave 1, 2, 3 and 4.

      • The dates are TBC (to be confirmed) but they represent an educated guess based on past experience.
      • The dates will be confirmed closer (a couple months in advance) to the events.


      Once again, thank you for providing feedback and contributing for the continuous improvement of the knowledge base content.

      1. Thank you, please notice that the end date of the first eHDSI Preparatory-PPT W1 is wrongly set to 26/09, while it should be 23/06.

        1. Well spotted.

          The year was also wrongly set up to 2016. Just updated.

          Please let us know if you find any further remarks.