OpenNCP Weekly Sprint Meeting
11th Jun 15:00 to 16:00 CET
- reschedule for > 12th Jun 10:30 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) (<- both weeks, or perhaps just the last week could be the code freeze?) Completed
- Release date: 25March (Monday) > OpenNCP 2.0.0 > Postpone
5º Sprint: 25Mar > 8Apr (2 weeks) Completed
- Release date: 10Apr (Thursday) > OpenNCP 1.1.2 > Completed (Release Notes)
- Release date: 11Apr (Thursday) > OpenNCP 2.0.0 > Postpone
6º Sprint: 22Apr> 3May (2 weeks) > Completed
- Release date: 8May (Wednesday) > OpenNCP 1.1.3 > Completed (Release Notes)
7º Sprint: 6May> 17May (2 weeks) > Completed
- Release date: 22 May (Thursday) > OpenNCP 2.0.0 (Postpone)
8º Sprint: 20May> 31May (2 weeks) > Completed
9º Sprint: 3June> 14June (2 weeks) > in Progress
- Support OpenNCP 1.1.3 (used in 4th PPT-slot as May 27th - June 7th)
- Release OpenNCP 2.0.0 > 19 June (Thursday)
Agenda
1. PAC QA Stage
2. HCER QA Stage
3. epSOS 2.0 Audit Trail EventIDs (Discussion of Roadmap)
4. 4PPT OpenNCP usage feedback
5. OpenNCP Support
6. epSOS2: TSAM adaptation for CTS2 compliance
Location
NetViewer + VOIP (Netviewe session number: 369 152 647)
Participants:
MEETING NOTES
1. PAC QA Stage
- The service implementation is complete.
- What needs to be done in order to allow end-2-end test?
-- Solve: TM-47 (Stéphane will check with Arnaud - can work on it only on the 17th of June) -- Dependency: How to TEST?
-- Dependency: How to access auditing compliance ?
--- Do we need to test transactions on the PAC workflow?
--- The transactions are the same used in the Identification Service and Patient Service, but the AUDIT messages need to be produced according new SPECS.
---- Probably there is the need to chage some AUDIT messages, but WE MUST take in account that PAC service is reusing transactions from previous epSOS 1 services, and for that we must keep compliance or have a clear strategy for replacing AUDIT messages.
-- The Audit Trail messages need to be revised for epSOS 2 Services accordingly the SPECS.
--- The SPECS are available but still not implemented.
---- There are ISSUES that IMPED implementation.
2. HCER QA Stage
- The service implementation is complete.
+++++++++++
(by Eric) Dear All
the IHE Europe development team is pleased to let you know the availability of the the MRO and HCER validator from the EVS Client application : http://gazelle.ihe.net/EVSClient
Please let us know if you find any issues. +++++++++++
- What needs to be done in order to allow end-2-end test?
- Make use of the Updated Transformation Manager (TM-43);
- Model Based Validator - in the new TSAM
- LKM: check the release by Posam frothe new Transformation Manager;
- Validate the produced document and messages (accordingly with the new HCER IHE validator.)
- The AUDIT Trail issues also applies to this service as well as for all epSOS 2 services.
3. epSOS 2.0 Audit Trail EventIDs (Discussion of Roadmap)
-- The adoption of new EventIDs does not seem to bring any issue apart from the following line:
--- We need to report to the specification team that there is no information about the related transaction on each EventID (e.g. "XCA::CrossGatewayQuery" will replace "epsosPatientService::List" and "epsosOrderService::List", therefore it would not be possible to distinguish them) - perhaps it should be that way, but further clarification is needed.
- [To-Do] LKM: Ask for clarification to the specification team about the missing transaction info on Audit Messages details
4. 4PPT OpenNCP usage feedback
- No issues were raised.
- General feedback is really positive, having in mind that all the participating PN accomplished the PPT goal.
- Regarding OpenNCP no difficulties have been reported....
- Some feedback from Mustafa about the 4th PPT
- Do all PN participating in the 4PPT used the OpenNCP?
- Probably YES;
- Who were the PN participating? Malta, Slovenia, Croatia; Hungary;
- The OpenNCP has provided an 1.1.4 branch, for Hot Fixes that may arise for the 4th PPT.
- The branch was not used, so it may be closed, and there is no need to merge it with the OpenNCP 2.0.0.
5. OpenNCP Support
1. Mika has fixed the database connection leaks, changes are in develop branch. (INT-62 and TSAM-1)
- PT: Had some evidences of this problem in our training environment;
- PT needs to restart the Application Server (Apache) very often regarding some leaks;
2. During the merge of 1.1.3 and develop branches some functionality was lost, check INT-63.
BLOCKING ISSUES TO SOLVE
6. epSOS2: TSAM adaptation for CTS2 compliance
- Arnaud and Giorgio were not present.
- As they are key person on this issue, it discussion has been post pone for the next meeting.
NEXT Steps
- [Done] MF: Ask Eric for information about the HCER web-service validator.
- [Done] MM: Disseminate email about: "News about OpenNCP2.0.0 and request for contributions"
- [Done] MF: Ask for clarification to the specification team about the missing transaction info on Audit Messages details
- ++++++++++++++++++++++
From: Marcelo Fonseca <marcelo.fonseca@iuz.pt>
Subject: Clarification on new Audit Messages specifications
Date: 12 June, 2013 12:35:23 PM GMT+01:00
To: Jörg Caumanns <joerg.caumanns@fokus.fraunhofer.de>, Sören Bittins <soeren.bittins@fokus.fraunhofer.de>
Cc: Marcello Melgara <marcello.melgara@cnt.lispa.it>, Giorgio Cangioli <giorgio.cangioli@gmail.com>, Gareth Woodham <Gareth.Woodham@apotekensservice.se>, Konstantine Hypponen (finland) <konstantin.hypponen@kela.fi>, Kostas Karkaletsis <k.karkaletsis@gnomon.com.gr>, Répás, Norbert <norbert.repas@elga.gv.at>, Stéphane Spahni <stephane.spahni@hcuge.ch>, arnaud gaudinat <arnaud.gaudinat@hesge.ch>, Ivo Pinheiro <ivo.pinheiro@iuz.pt>, Licínio Mano <licinio.mano@iuz.pt>
Dear Jörg Caumanns, Sören Bittins
The OpenNCP team is about to start implementing the new specifications for Audit Messages and we need some clarification on the following items
- The new specifications for Event details (ID's, Names) do not clarify which transaction / document is involved (e.g. "XCA::CrossGatewayQuery" now replaces "epsosPatientService::List" and "epsosOrderService::List", therefore it is not possible to distinguish them)) - is there any information present in the audit message that allows to distinguish which document was involved?
- That also applies to the provision of data - with the new "ITI-41" event ID, we only have the "XDR::ProvideandRegisterDocumentSet-b" event name, therefore both dispensation and HCER services will produce the same audit message.
Thank you very much for your attention.
Best Regards,
--
Marcelo Fonseca
epSOS - Portuguese Technical Team
- ++++++++++++++++++++++
- [To-Do] LKM: check the release by Posam frothe newTransformation Manager;
- [Done] Kostas: Bring knowledge about the CDA display tool - render the information for HcP.
- [in Progress] Clarification on the status from the - epSOS 2.0 Services Messages Validators
- [To-Do] Licinio Schedule 'next' meeting - proposed date June 18th, 2013, 10h00 CET