OpenNCP Weekly Sprint Meeting

2nd October 14:00 to 14:30 CET

~~27th September 10:00 to 11:00 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) > in Progress

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

ROADMAP

[in progress]

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

[stand By for specifications]

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

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

Agenda

a) Specification presentation > MRO

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

Location

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

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>,

[HAS LEFT PROJECT!] Fredrik Dahlman <fredrik.dahlman@cag.se>,

[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>,

[yes] Konstantin Hypponen <konstantin.hypponen@kela.fi>,

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

[yes] Jussi Lemmetty <jussi.lemmetty@kela.fi>,

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

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

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

Marcello Melgara <Marcello.Melgara@cnt.lispa.it>,

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

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

[yes] Milada Kovarova <Milada.Kovarova@posam.sk>,

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

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

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

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

Per Loubjerg <consult@loubjerg.dk>,

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

Steen Manniche <steen@manniche.net>,

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

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

MEETING NOTES

a) Specification presentation > MRO

MRO specifications: https://service.projectplace.com/pp/pp.cgi/r886748542

?This document is based on the Common Module document https://service.projectplace.com/pp/pp.cgi/r911404315 Document that substantially just says look at the D 3.9.1 B1 V 1.4 specifications

MRO > Subset of PS, should include information about medication and allergies (most important drug allergies);

- Optionally can have: imonization, pregnancy history, coded social history, coded vital signs

- The current document for MRO its the same as the PS but with different section Optionallity;

- 2 mandatory sections >

- 5 optional sections >

MRO

XCA, similar to the

Biggest effort will be the country for creating the services;

Interaction module use for PS:

General Context UC description 1.4.3, section 4.3

pag 20 and following;

Role Base access

PS only by physician

eP only Pharmacist

MRO only Pharmacist

What tool should be used for visualize the MRO

- We can start by the PS visualizer???

Audit manager:

- What nedds to be added?

- Using the same that the ones for PS but declaring that the document is a MRO;

Transformation Manager - MRO

- Are there any sample documents??

-- Not yet... but we can can produce it by changing the PS and leave the mandatories and optional sections;

ASK Marcello Megara if some country as already produced and MRO document;

- Plan B: Milada will provide an example document...

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

New version of OpenNCP v2.1.0

Commit changes to develop branch

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

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

1. Conformance Functional Profile based on the HL7 CTS2 SFM

2. Conformance Implementation Profile based on the OMG CTS2 PIM/PSM

Documents are available in the epSOS Project Repository in the following folder https://service.projectplace.com/pp/pp.cgi/r891874661.

The Conformance Functional Profile document includes an introductive section providing an overview of the epSOS semantic services and related architecture (current and potentially future) in which that profile is supposed to be used.

For your purpose you can focus on the Conformance Implementation Profile https://service.projectplace.com/pp/pp.cgi/r891876139

CTS2 - standardized terminology sevices

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

3 strategy for implementation

SOAP implementation

If this

REST implementation (real implementation)

If this: devlopment framework: http://informatics.mayo.edu/cts2/index.php/REST

TSAM-sync purpose (actual)

-

SCOPE from this development

- Syncronising LTR with central services using CTS2 interfaces;

- Assume that SERVER filters are managed in a different way (e.g. when we ask for a value set, the service will reply with a value set from epSOS)

CareCom does not delivers this interfaces;

- Where can we find a server to test with?

-- ??? Maybe: Mayo Clinic or PHAST (= Ana Estelrich)

-- Need to start from the SERVER > what does it implement??' how will that influence the TSAM-sync implementations;

The Servers exist (at least for rest implementations), but not as test servers.

???- Marcello or Giorgio will entering in contact with both providers for this fo assess their availability for providing a test service

1.1 Functional Profiles

[EN] FP_READ – the implementation supports direct read access for artifacts of the associated structural profile.

[EN] FP_QUERY – the implementation supports search and enumerate access for artifacts of the associated structural profile.

[EF (+)] FP_TEMPORAL – the system supports the ability to read and query (as supported by the service) the service in the context of a date and time different.

//valuesets

http://informatics.mayo.edu/svn/trunk/cts2/spec/psm/rest/html/cts2.html#id1171374346762

//valueset/{valuesetid}/definitions

http://informatics.mayo.edu/svn/trunk/cts2/spec/psm/rest/html/cts2.html#id1171374348687

//entity

http://informatics.mayo.edu/svn/trunk/cts2/spec/psm/rest/html/cts2.html#id1171374284251

look TSAM-sync > and understand size, and from there estimate the effort for the new;

- the currect TSAM-sync is more like an importer....

-- New implementation > should fill the currect TSAM-sync (is this an open source component??? proprietary interface???);

----- Marcello Melgara assures that TSAM-sync is OPEN SOURCE completly

-- New implementation >

MUST INVOLVE ANNIKA from CareCom;