2. 4. Allergy severity
The severity of an allergy is not displayed by the CDA Display Tool, and this is considered relevant to the HP. PT
MAJOR
The severity is subject to semantic processing, but in the end it's not displayed by the CDA Display Tool. The fix should is easy to implement.
EHNCP-1727 - Jira project doesn't exist or you don't have permission to view it. PS
CDA Display Tool
 To be approved in the semantic teleconference/F2F meeting.

3. 5. Display of codes
In some PS sections, the underlying codes are displayed together with the description, e.g., "Coxartrose, não especificada(M16.9)", while in others just the description is displayed. In the case where codes are displayed, it's more useful to display as well the associated code system (e.g., ICD-10). Ideally, the behavior should be the same in all sections (currently some sections display codes while others don't). PT
MINOR
For every coded value, CDA Display Tool should capture and display the codeSystem as well. PS
CDA Display Tool
To be approved in the semantic teleconference/F2F meeting.

4. 7. Brand name of immunization
The brand name of the immunizations is considered irrelevant by the HP PT
MINOR
Remove the brand name column from the immunizations section. PS
CDA Display Tool
To be discussed during the semantic teleconference/F2F meeting.
Solution Provider considers that displaying the brand name of the vaccines might be relevant in some cases: e.g. Country A cannot provide the expected coded information for the vaccine according to the concepts in the Value Set, due to different reasons → it is not coded at national level / was not coded in the past, or it is not possible to map

5. 9. Author information for assembled PS
When the PS document is created by a machine the CDA Display Tool presents this fact in the author part, but not the represented organization. Therefore, the name alone might not be informative enough for the HP in Country B
eHDSI Solution Provider
MINOR
Improve the display of the author of the document when the CDA document is created by a machine: display the name as well as the represented organization - as the name alone might not be useful for the HP.
This was noticed in a test data document, in which the original Country A PDF provided was more explicit and included the organization name along with the name of the creator of the document (just an acronym). PS
CDA Display Tool

6. 10. Showing a section is missing
The fact that there is no information about allergies is not clearly understood
eHDSI Solution Provider
MAJOR
Once CP-eHealthDSI-027 is fully implemented for Wave 3 and the Guidance finalised, the 'No Information' situation will be clearly represented. PS
MVC, CDA Implementation Guides, and CDA Display Tool
CP-eHealthDSI-027
Guidance (Wave 3) for communicating and representing the 'No Information' and 'Known Absence' situations

7. 11. Date range instead of onset time
In one of the PS test data documents, the entries for current problems contain dates for the low and high values of the effectiveTime element (very close dates, which makes not sense from a biological/clinical point of view)
eHDSI Solution Provider
MINOR
According to the eHN Guidelines and eHDSI Functional Requirements: the List of current problems/diagnosis is only expected to have a date, that of the onset time, while the data set for the List of resolved, closed, or inactive problems, includes two - onset and end date.
In practice, the eHDSI IGs re-use the same template (Problem Concern) for both Sections with the effectiveTime element defined as an IVL_TS (interval of time), but it is specified:
the <low> element shall be present
the <high> element shall be present for concerns in the completed or aborted state, and shall not be present otherwise PS
Implementation Guides

8. 12. Missing sections
It is indicated as no safely interpreted that there is 'No Information' about required Sections: e.g. Medication Summary, Surgical Procedures, and Medical Devices and Implants
eHDSI Solution Provider
MAJOR
Once CP-eHealthDSI-027 is fully implemented for Wave 3 and the Guidance finalised, the 'No Information' and 'Known Absence' situations will be clearly represented.
Additionally, this feedback is important for deploying countries regarding the necessary training of the future users of the service, about the Patient Summary service; explaining that it contains 5 required sections that may contain known absence, for example, given that a patient does not necessarily have to have information on past surgeries (he/she might have never had any procedure performed) or is not carrying any implant. PS
MVC, CDA Implementation Guides, and CDA Display Tool
CP-eHealthDSI-027
Guidance (Wave 3) for communicating and representing the 'No Information' and 'Known Absence' situations

9. 13. Date or date and time for prescribing
The ClinicalDocument/effectiveTime shall always be more precise than to the day, therefore including a timezone. For instance, for pharmacists it's not natural to see they're trying to dispense an eP issued in the future. Take the following example:
1) EE issues an eP at 00:02 EET (22:02 GMT), with effectiveTime= (already 18 March 2019 in EE)
2) 30 minutes later (00:32 EET, 22:32 GMT, still 17 March in PT), a pharmacist in PT fetches this eP and sees that this eP was issued "tomorrow". Without timezone, it's not possible to convert between timezones (EET to GMT in this case). PT
MINOR
Add a new constraint in the ClinicalDocument/effectiveTime to force the provision of a timestamp that is more precise than to the day and includes a timezone. In the CDA IGs, for this specific element, it should be:
"SHALL include a time zone and be more precise than to the day, and SHOULD be precise to the second."
instead of:
"SHALL be precise to the day, SHALL include a time zone if more precise than to the day, and SHOULD be precise to the second."
eP/eD/PS
CDA Implementation Guides

10. 16. Pregnancy section for non-pregnant women
Including a gynaecological/obstetric Section is important in the case of women in fertile age PT
MAJOR
The current Pregnancy Section is optional and only designed to present the expected date of delivery for pregnant women.
Possible solutions:
make the Section required - conditional to being a female patient- and indicate in the original narrative the pregnancy status in English.
introduce a coded element, Status and meaningful concepts to represent the value for that status: pregnant, non-pregnant, unknown.
update the Section to represent a Pregnancy Section in the sense of a more complete obstetric history - which would include gravity (the number of times a woman has been pregnant regardless of the outcome), parity, abortions, etc. - that will give  the attending physician valuable input information when providing healthcare → as suggested in the future clinical improvements of the IGs PS
CDA Implementation Guides
eHN Guideline on the electronic exchange of health data under Cross-Border Directive 2011/24/EU, Release 2
Pregnancy Section - eHDSI PS Implementation Guide