OpenNCP Weekly Sprint Meeting

8th October 10:00 to 11:30 CET

Work RoadMap - epSOS 2 Services

1º Sprint: 28Jan > 8 Fev (2 weeks) > Completed
2º Sprint: 11Fev > 22Fev (2 weeks) > Completed
3º Sprint: 25Fev > 8Mar (2 weeks) > Completed
4º Sprint: 11Mar > 22Mar (2 weeks) Completed

5º Sprint: 25Mar > 8Apr (2 weeks) Completed

6º Sprint: 22Apr> 3May (2 weeks) > Completed

7º Sprint: 6May> 17May (2 weeks) > Completed

8º Sprint: 20May> 31May (2 weeks) > Completed

9º Sprint: 3June> 14June (2 weeks) > Completed

10º Sprint: 24June > 19July (4 weeks) > Completed

Release OpenNCP 2.0.1 > ~~31 July, 2013 (Wednesday)~~ 6th August

Release OpenNCP V2.0.2 > 2013-09-12 Transformation Manager + Emergency Scenario + Bug Fixing

5ª PPT [in progress]

OpenNCP V2.0.3 (after PPT) 2013-10-16 OPERATION Ready for: PAC + HCER epSOS 2 Services

11º Sprint: 15Oct > 28Oct (2 weeks) [plan]

OpenNCP V2.1.0 2013-10-30 PPT Ready for: MRO + TSAM-sync (adaptation for CTS2 compliance)

??ª PPT [recommended]

OpenNCP V2.1.1 (after PPT) 2013-12-05 OPERATION Ready for: ??

Agenda

a) Specification presentation > TSAM-sync (adaptation for CTS2 compliance) - Continuation

b) 5º PPT slot - progress monitoring

Location

Skype (sirLicman) + Jira Board + MeetingWords (http://meetingwords.com/cbNZ5L1OQq)

Participants:

Aarne Roosi <Aarne.Roosi@affecto.com>,

Alexander Berler <a.berler@gnomon.com.gr>,

Anders Nyström <Anders.Nystrom@apotekensservice.se>,

Arnaud Gaudinat <arnaud.gaudinat@hesge.ch>,

Belani Hrvoje <Hrvoje.Belani@hzzo.hr>,

[yes] Gareth Woodham <Gareth.Woodham@apotekensservice.se>,

Gergely Heja <heja.gergely@eski.hu>,

[yes] Giorgio Cangioli <giorgio.cangioli@gmail.com>,

Ljubi Igor <Igor.Ljubi@hzzo.hr>,

[yes] Ivo Pinheiro <ivo.pinheiro@iuz.pt>,

Juergen Wehnert <juergen.wehnert@gematik.de>,

Konstantin Hypponen <konstantin.hypponen@kela.fi>,

Oskari Kettinen <oskari.kettinen@kela.fi>,

Jussi Lemmetty <jussi.lemmetty@kela.fi>,

[yes] Kostas Karkaletsis <k.karkaletsis@gnomon.com.gr>,

[yes] Licinio Mano <licinio.mano@iuz.pt>,

Maarten Festen <maarten.festen@ihe-europe.net>

[yes] Marcello Melgara <Marcello.Melgara@cnt.lispa.it>,

[yes] Marcelo Fonseca <marcelo.fonseca@iuz.pt>,

Mate Beštek <mate.bestek@gmail.com>,

Milada Kovarova <Milada.Kovarova@posam.sk>,

Mika Myllyvirta <mika.myllyvirta@kela.fi>,

Mindaugas Ajauskas <mindaugas.ajauskas@lispa.it>,

[yes] Norbert Repas <norbert.repas@elga.gv.at>,

Patrick Ruch <Patrick.Ruch@unige.ch>,

[yes] Per Loubjerg <consult@loubjerg.dk>,

Tomaz Cebular <Tomaz.Cebular@ivz-rs.si>,

Steen Manniche <steen@manniche.net>,

Stefan Gustafsson <stefan.gustafsson@callistaenterprise.se>,

Stéphane Spahni <stephane.spahni@hcuge.ch>,

Annika Sonne Hansen <ash@carecom.eu>,

MEETING NOTES

a) Specification presentation > TSAM-sync (adaptation for CTS2 compliance) - continuation

Specifications have been defined, in two distinct documents, in term of:

1. Conformance Functional Profile based on the HL7 CTS2 SFM > https://service.projectplace.com/pp/pp.cgi/r891876146

2. Conformance Implementation Profile based on the OMG CTS2 PIM/PSM > https://service.projectplace.com/pp/pp.cgi/r891876139

Relevant for implementation;

Platform independent and Platform Specific;

The document states the WHAT to be implemented > https://service.projectplace.com/pp/pp.cgi/r891876139

The HOW to be implementeded > http://informatics.mayo.edu/svn/trunk/cts2/spec/psm/rest/html/cts2.html

MAIN WORKFLOW (simple approach) - Ask to the Terminology Server:

CFP Document: 4-Example: a possible scenario (page 28)

1) Please give me all the value sets used in epSOS;

2) Then we take the valuesets and then we select the active ValueSets version - provide the members of the valueSet;

3) Get detail about that Concept/Entity

Includes Tranlation as well as other information (e.g. designation);

3.5.3 EntityDescriptionReadService

3.5.3.1 read

4) Get full details about the code system and codesystem version > http://serverRoot//codesystem/{codesystemid} (using previously obtained ID in step 3)

3.5.7 CodeSystemVersionCatalogReadService

3.5.8 CodeSystemCatalogReadService

5) Handle possible mapping (What the code system to map?)

Request all the map that may be used for epSOS in a specific country;

Request the CURRENTLY EFFECTIVE MAP version that need to be used in epSOS (current version of the MAP);

6) Request detail about the MAP that will include:

MAPSET (relation between the SOURCE code and the TARGET code);

What can be removed from a CTS2 Query (in order to reduce complexity) and be managed externaly (e.g. filters);

---

Enhancements to the previous scenario - EVALUATE

?) What has been updated, so that we can sync only the modifications (in order to improve the efficiency of the sync process);

Reference Framework (focus on this > having in mind the CLIENT component)

CTS2 Development framework: http://informatics.mayo.edu/cts2/framework/

REST implementation (real implementation): http://informatics.mayo.edu/cts2/index.php/REST

HSSP (HL7 + OMG) CTS2 Specifications

CTS2 and HL7 SFM (Service Functional Model : functional specification )

The following sections describe how the CTS2 Platform Independent Model (PIM) aligns with the HL7 Service Functional Model (SFM): http://informatics.mayo.edu/cts2/index.php/CTS2_and_HL7_SFM

CTS2 OMG© (Platform Indipendent Model and Platform Specific Model (including also the REST Platform Specific Model): http://informatics.mayo.edu/svn/trunk/cts2/spec/psm/rest/html/cts2.html

Other framework (research only if time available)

LexEVS - is the central EVS terminology server, developed by the Mayo Clinic with NCI and other support.

https://wiki.nci.nih.gov/display/LexEVS/LexEVS

https://wiki.nci.nih.gov/display/LexEVS/LexEVS+6.0+CTS2+Guide

Testing Servers

[to CareCom] If, and in case, what they are able to support of the OMG CTS2 REST implementaion Does HealthTearm support CTS2? REST Implementation?

Mayo Clinic >

PHAST (= Ana Estelrich) >

POSAM input (by Milada Kovarova)

To the topic of TSAM sync adoption, as the structure of LTR (Local terminology Server) won't change, there will be no changes in TM or TSAM module. We are out of the game ;-).

However, maybe you will have to face with filling LTR database.

As we've designed the original LTR, if you need some explanations what are current tables and attributes and why it is as it is, I would be glad to help (I hope my memory still reaches such a long time ago).

+++++++++++++++++++++++++++++

IMPLEMENTATION

TSAM-sync > is the only component that need to be modified;

Are the DAOs the only part of the current implementation that we can reuse?

What documentation is there on what it is build today, how it works, in order to extend the current implementation?

https://code.google.com/p/epsos-common-components/source/browse/userdoc-environment/EPSOS-TSAM-Synchronizer.pdf?repo=tsam-sync (Design Specification)

LTR Database

Already build a diagram (the current database schema)

Man Power Available:

SE: Oct: 4-8h week;

Gnomon: Oct & mid Nov: few hours available;

PT: 1 person per Month > Oct. / Nov. / Dec.

Start MRO Development;

FI: ??

?? Who else is available for collaborating in the development team??

MRO DEV EFFORT

> 20h Portal > Add support for searching this kind of Documents

> 20h CDA display Tool > Make sure it is compatible with the MRO CDA document or need extension.

> 16h Protocal Terminators: client side: Add differentiation in the classcode (Service Wrapper)

> 16h Protocal Terminators: server side: extend the national interface for search MRO documents (new method)

> 32h Integration tests (mock objects and IHE validators - MRO validator available)

> 24h Documentation, for updating the thw wiki and integration guide

Sprint: Start 15Oct > Ends by 28Oct;

Quality Assurance

It is possible to collect all the transaction messages into an XML file.

Norbert would like to present up to the next F2F Meeting a refined approach to QA. This approach icudes a semi-sync conversation process (messaging) between NCP A NCP B (incl NC MOCK!) artifact and remote Gazelle services.

Kostas has wrtitten a LOG4J config file that already grabs the messages and store them in a database

This mechanism can be re-used to obtain the messages in order to validate them (in the CI environment automated process);

It can also be adopted officially as a common way to obtain the messages in a PPT or PAT scenario;

b) 5º PPT slot - progress monitoring

- PT: m2m test are DONE; e2e test started (1 completed);

- IT: not know - so far;

- Reported some constraints with Croatia > namely in the Central Services configurations (no file uploaded);

- SE: "no peer" tests aready passed (except audit scrutinies) started the WF tests; e2e tests on thursday

- LU: already completed test with PT, CH, EE > some problems in the validation of some messages;

OpenISSUES - in OpenNCP Support Board (https://openncp.atlassian.net/secure/RapidBoard.jspa?rapidView=2)

https://openncp.atlassian.net/browse/OPENNCP-31 > Assigned to Eric, but already solved with some recomendation;

LKM > move to QA;

https://openncp.atlassian.net/browse/PT-355 > Assigned to Konstantin;

NEXT Steps

[Giorgio] Provide the initial design from LTR database scheme;

[Marcello] Suggest "Reverse Engineering" in order to understand the current scheme, and compare it with the "DOC" to understand the initial rationale for the design;

[Giorgio] Undesrtand the maturity of PAST implementation;

[Marcello] Undesrtand if Mayo Clinic is available for testing scenarios and understand if there are any license constraints with the "CTS2 Development framework";

[Norbert] Check possibility for providing inputs regarding AT CTS2 implementation (Peter Brosch, Kathrin Trunner);

[Norbert] A refined approach to QA via a semi-sync process;

[LKM] Build Wikipage with all the knowledge gathered around CTS2 > also including Candiate Design of implementation > visual overview on components, operations and workflow;

[Norbert + Fonseca] Work on Quality Assurance mechanisms, namely by providing a clear perspective on what could and MUST be developed, regarding transactions;

[LKM] next meeting > 15Oct > 10h00 CET (inform Juergen and Milan, to confirm that the TPM meeting is moved from the 15th to the 16th)

Browser not supported