Versions Compared

Key

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

OpenNCP Weekly Sprint Meeting

25th Jun 15:00 to 16: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

...

  • Support OpenNCP 1.1.3 (used in 4th PPT-slot as May 27th - June 7th
  • Release OpenNCP 2.0.0 > 19 June (Thursday)

10º Sprint: 24June > 5June 5July (2 weeks)  > in Progress

  • Goal 1: PAC + HCER > Audit Trail Messages (Compliance)
  • Goal 2: HCER > Document Automated Tests (Quality)
  • //Goal 3: PAC + HCER >

...

  • PS + PAC > Document & Transactions Automated Tests (Quality)
  • //Goal 4: eP/eD > Document & Transactions Automated Tests (Quality)

 

Current SPRINT -

FI: ??? Goal 1;

PT: Goal 2;

SW: NO availability;

CH: ??

Agenda

1. OpenNCP Support

2. OpenNCP 2.0.1 Planning

...

5. TSAM-sync adaptation for CTS2 compliance

 

Location

NetViewer + VOIP

Participants:

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

...

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

 

MEETING NOTES

1. OpenNCP Support

Are there other issues needed to be solved for Operation or PPT?

Jira Legacy
serverJIRA (openncp.atlassian.net)
serverId5eab37ce-f509-3cbb-9925-c13d0f8d6d44
keyCOMA-7

Jira Legacy
serverJIRA (openncp.atlassian.net)
serverId5eab37ce-f509-3cbb-9925-c13d0f8d6d44
keyDATA-6

2. OpenNCP 2.0.1 Planning

  • Quality and Compliance?

  • Currently the PAC and HCER have no Audit Logs;
    • IMPLEMENT Audit Logs;

  • Currently the PAC and HCER don't have IHE messages and document;
    • IMPLEMENT automated tests, regarding the automated
    • HCER Transactions may need new validators;

 

2. HCER QA Stage

The service implementation is complete.

...

+++++++++++

...

+++++++++++

...

 

...

epSOS 2.0 Services Messages Validators

  • - What is the current status of the epSOS 2.0 services message validators (specially HCER and MRO);
    - Is there any time frame for the readiness and availability of those validators at the EVSClient?

    I'm asking this questions because we have reached a development level in which the produced messages require validation, so that we can fine tune our implementation.
    This issue intends to represent the task of develop and make the validators available for further usage, and can be closed once they're ready for use by the OpenNCP team.

  • https://support.epsos.cz/issues/312

  • Eric Poiseau

    Marcelo, Konstantin is correct. The validation of the CDA document is available in the EVS Client application under the epSOS -> CDA menu entry. Concerning the validation of the transactions specific to the document MRO and HCER we have not yet found where they are specified ! if any one can point us to the right document where the new transactions are specified, then we will see how to add them in the XDStarClient simulator and we will also add the validation.

Follow: in the epSOS issue tracker;

 

...


 

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

 

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

 

...

  • Raise PRIORITY on the issue and bring people to give the needed answers;

  • Automated tests
    • Can be done to epSOS 1 services;
    • Partially to new services;

 

4. MRO Service Specification discussion

  • LKM: Ask for the specification team to clarify and meet with the development team;

5. epSOS2: TSAM-sync 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.
  • Arnaud:
    • Spec last update was in May;
    • Specs were shared with CareCom;
  • Marcello Melgara
    • Needed a formal validation from Spec in order to obtain vendors/industry alignment;
    • Platform independent specification (SOAP or REST implementation decision);
  •  LKM
    • Stand by wait for: MM, Arnaud and other, for starting the validation of the specification

NEXT Steps

 [MF - ToDo] Release OpenNCP 2.0.0
  • Resolve BLOCKING ISSUES
  • TEST artefacts
  • Publish artefacts
    [LKM - in Progres]  LKM: wait for information from Posam about the newTransformation Manager;
    [MF - in Progress] Clarification on the status from the - epSOS 2.0 Services Messages Validators
  • [Joerg Caumanns] Transactions (https://support.epsos.cz/issues/312)
    • Specification providing for IHE develop Validatores;
  • Documents (https://support.epsos.cz/issues/312)
    • IHE validators already available for HCER and MRO
  • [Joerg Caumanns] Audit Trails
  • Specification Clarification
  • Specification providing for IHE develop Validatores;
    [MM+AG] TSAM-sync adaptation for CTS2 complianceWork for start the validation of the specification
    •   Norbert: please stand by pushing this feature to development. Wait for decision on priorities and importance about this feature;

    NEXT Steps


    • [LKM - ToDo] Licinio Schedule 'next' meeting - proposed date June 25thJuly 2nd, 2013, 15h00 10h00 CET