http://ec-wacs.adobeconnect.com/openncp/ Room Passcode: markus.kalliola or michele.foucart ------------------------------------------------------------------------------------------------ If you have never attended an Adobe Connect meeting before: Test your connection: http://ec-wacs.adobeconnect.com/common/help/en/support/meeting_test.htm Get a quick overview: http://www.adobe.com/products/adobeconnect.html Adobe, the Adobe logo, Acrobat and Adobe Connect are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. ------------------------------------------------------------------------------------------------
See the 2 documents attached in e-mail sent on 18/02/16 "epSOS CTS2 based specifications":
WP3A_epSOS_EED_TSAMSync-CFP_v0 07
WP3A_epSOS_EED_TSAMSync-CIP_v0 05 (2)
Meeting Notes:
Housekeeping
Objective of the meeting:
Migration path to onboard the value set... in order to allow the NCP to work
Amongst the pre-requisites:
TS CTS2
OpenNCP CTS2
...
TS fullfilment of CTS2 from OpenNCP perspective
Possible approaches:
list the functionalities that we need (service translation etc.
Peter is mentioning an xls listing the functionalities we need
Highlights in HL7 specs: Mapping the functionalities in HL7 specs and technical binding with OMG services
Proceed incrementally, see following steps, from the functional point of view (reaching something "working" as today)
From API point of view: recreate the current situation in order to allow the NCP to work TS independant (without Carecom)
Instead of TS Sync => use standard ops
To be sure that we reach the working state (from the functional point of view) without investing in new APIs...
Users part - which is another topic
Of course the end point of the server needs to be changed.
Agreement on the incremental approach
Specs of TSAM
Giorgio Cangioli proposes to find the specs and reference implementation of the client part.
From that FH Dortmund to assess if ok or directly go to step 1?
we can check if it conforms to the info of the TS...
identifyer of the concept, identifyer of the term, the status of the concept, language... info that need to be handled, ref to the code system, id of the value set...
As soon as we have the specific rule, we can discuss on that
Based on the costs of implementation we can decide if we can skip the step or not
In // we can start to investigate the following steps
Peter Haas: If we have a migration project, first question is if we have a big schema mismatch.
Align implementation strategy based on the best implementation choice/approach (FHD)
Is there documentation of the services? (Healthterm) - Giorgio Cangioliwill get in touch with Peter to highlight those definitions.
Peter Haas: Over 40 service methods...H2 retrieve an concept and translation
We need to investigate: they changed the synchro services a bit to allow an incremental synchronization, using solution which is a bit complex. Allow the NCP to make the complete resync. Might be more complex if we try to download more than one language...Code system is in leading language (ENg) in the service call you can ask specific translation. Then get the translation and original language...
Need to investigate if we can obtain the information through the value-set content or other
Giorgio Cangioli: proposes to retrieve original TSAM Sync, then see how to map with existing services, then in // with OMG services that we want to use.
Marco Bernardini has also started the GAP analysis of the datamodel.
How to phase the management of the different code systems and H2 approach them?
e.g. EDQM have different properties, assets to be considered... How 2 represent terms, H2 keep in touch with the people working...frequent updates of the terms...
Procedural aspects to be handled, technical aspects, relationship...=> We should start to list those aspects. Orga aspects, administration of semantic can be discussed in //. Giorgio Cangioli proposes to create a page listing the diffrent topics to be handled and start with that in //.
Management of the different code systems, organizational and technical aspects => Giorgio Cangioli will start the page, Marta Terron Cuadrado participation
start a meeting as soon as we are a bit more mature on the topic
Working space OpenNCP task force Terminology server can be used (need to be logged in to see the page: /wiki/spaces/ncp/pages/72417309
Next meeting: Terminology task force meeting on 1pm CET