Agenda:

What is the status about CDA?
1. What is the problematic and the urgency?
  1. Distinguish the different problems, if relevant
2. What is the status?
  1. What has been done already?
  2. What still needs to be done?
What are the reference/background documents?
Next steps
1. Who
2. What
3. When

Location

AdobeConnect:

http://ec-wacs.adobeconnect.com/openncp/

Room Passcode: markus.kalliola or Licinio Kustra Mano

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

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

Participants

Meeting Notes

What is the status about CDA?
1. What is the problematic? There are different topics that need to be handled with regards to the CDA (today they are a bit mixed/not clear):
  1. The CDA is the last ring of the chain. We can forecast what CDA display tool should do but this is a process of managing data and we need to take into consideration the modification of the xml file
  2. 1. Changes have to be done in the transformation manager and in the CDA display tool to generate the new epSOS friendly document because the way to retrieve ingredient and ATC code has changed.
  3. CDA specifications need to be continuously maintained:
  4. 1. Problematic raised by Kostas Karkaletsis during the Connectathon in Bochum: We were missing the specifications of the PS scanned document => we have decided that we have to include it in the next version of the specifications => Part of the maintainence process
    2. Marcello Melgara: the eHMSEG semantic subgroup is working on the maintenance process of the specifications.
      1. Everyone agree that we need a specification maintenance process in place.
  5. Fail during the Connectathon CDA display tool: missing quantities/dosage in "substance administration class code"
    1. Reference in Gazelle: https://gazelle.ihe.net/EU-CAT/testing/test/test/TestInstance.seam?id=47458&cid=39351
    2. michele.foucart will attach the xml files where there was the problem
    3. JIRA issue: TM-62
What is the urgency?
1. In the current situation: We are fully coherent with the past. We have the old epsos document with the "old" MVC 1.8, displayed according to the old epsos approach.In order to be compliant with the new specifications, we need to update the transformation manager to be able to generate the new epSOS friendly document
2. This should be done by the end of the year 2016, in order to be able to validate it during the next Connectathon in 2017, which is preceeding the go live in 2018
3. What about the adoption of MVC 2.0? Is there a depedency?
  1. Not sure MVC 2.0 can be adopted, question mark related to the SNOMED CT part. There is also a link between MVC 2.0 and the current licence with iHSDO.
  2. Other elements can be updated independently from this task because there is no change of any data set. Only the number of terms has changed.
Proposed approach
Marcello Melgara suggests that we concentrate on technical aspects.
1. Activity 1: Identify the changes that need to be applied - Check the coherence of the xml file with the current specifications
  1. A full check, not only on the new elements. Because it happened in the history of the implementation of the OpenNCP that some changes were lost. We have to make sure it is 100% compliant to the LAST version of the specifications.
2. Activity 2: Generate a reference document that pass all the scrutiny tests from Gazelle
  1. Generate 1 eP and 1 PS to test if it passes Gazelle tests - which will validate that the epsos friendly document is correctly displayed by the CDA display tool
  2. Attention point: We realized during the last Connectathon that Gazelle tests tools were not aligned to the specifications. The functional validator of Gazelle is built on Artdecor which is not aligned to the last version of the specifications.
    1. We need to verify the Gazelle scrutiny tests and ensure they are 100% aligned to the current version of the specifications
      1. Giorgio Cangioli: The testing script used was not based on Artdecor but on the word document...?
      2. The test scripts will be used to approve, so it is essential that they are aligned with the current version of the specifications.
  3. Test data: we should find some examples (allowing to test the changes) to test the full chain
3. Activity 3: Align the CDA display tool to the last specifications
  1. Jira issue: TM-63
4. Activity 4: Ensure that the code formal description (in Artdecor) is aligned with the last version of the approved paper specifications of the CDA (appendix B1, B2)
  1. Artdecor includes and summarize the content of the CDA display tool appendix B1, B2... It represents the master specifications to be maintained and updated. It also includes the issues identified in the specifications.
  2. 1. At the end of process, the only master = Artdecor for the content of CDA - In principle Gazelle can automatically get the specs from Artdecor
  3. For completing that alignment, the process for maintaining the specifications should be in place => link with semantic-subgroup (Marcello Melgara)
    1. Who is responsible to maintain Artdecor specifications (the tool and the specs)? Will be discussed in the semantic task force.
    2. Who has access to Art decor?
      1. https://art-decor.org/art-decor/decor-templates--epsos-
      2. Everyone has access in consultation (not in editing)
      3. who is the OpenNCP admin - Artdecor was maintained by IHE Europe during the project EXPAND
        Edit rights were given to the people involved in the core team of epSOS specs at the time of Expand: Giorgio, Kay, Christophe from Gematik...
      4. We need to assign the role of maintaining Artdecor specs, forgetting the role of past projects
        who is in charge of maintining the tool
        who is in charge of maintaining the specs
What are the reference documents?

Giorgio Cangioli: The reference document to be used is the Word document including the changes agreed in EXPAND:
1. ePrescription pivot extension needs; Change request; WP5, T5.2, Semantic Maintenance; 30 Mar 2015 ; version 0.2
2. There is also supporting documents on what has been changed according to specifications.
Changes have to be done in the transformation manager and in the CDA display tool because the way to retrieve ingredient and ATC code has changed. CDA specifications have been updated to include those changes. Updated version of the CDA specifications including those changes:
1. Requirements specification for an epSOS CDA display; Appendix A3; D 3.10.1
Giorgio Cangioli will attach to the minutes the documents, as a trace of what has to be done

https://art-decor.org/art-decor/decor-templates--epsos-
"epSOS Patient Summary, ePrescription, eDispensation and Common Modules HL7 CDA R2 Implementation Guide" ( WP3A_epSOS_EED_PSePeD_CM_CDAIG_1_1.pdf)
Note: there are known editorial changes that have to be applied to this version: e.g. R/R/RNFA shall be read as RNFA/RNFA/RNFA ; update the table in § 10.1 in order to make clear that changes on medicines description applies not only in eP but also to the PS (e.g. how ATC or multi-ingredients are represented); etc...
HL7 implementation guide for CDA release 2 - draft standard for trial use, release 1, levels 1, 2 and 3

Next steps
1. Who?
  1. New resource in EC working also on the terminology server?
2. EC will create issues in JIRA, with the documents attached, for follow-up
  1. TM-62 - Bug from the Connectathon
  2. TM-63 - Alignment with the updated specs
3. EC will create a dedicated space in Confluence
4. EC will organize ad hoc meetings when needed