Help
Login
Search
eHDSI - Issues

 
Select object
 
false
Results (1 / 1)
Id Issue Status Priority Type Date Assigned To Label
366 Cardinality of asContent defined in the CDA IGs in conflict with the XSD schema definitions. Closed Normal Change Request 2021-04-29 12:51:39 Mathias Ghys
 
Change Request Cardinality of asContent defined in the CDA IGs in conflict with the XSD schema definitions.
Id epsos-issue-366
Status Closed
Priority Normal
Last Tracking 2021-04-29 12:51:39  by  Mathias Ghys
Current Assignee Mathias Ghys
    
Concerns
Template
false
eHDSI Material (epsos-template-143)
/
/
Template 2.16.840.1.113883.3.1937.777.11.10.143 (2020-09-09 14:15:31) eHDSI Material
Status Retired
/
-
/
-
Events
Tracking Closed 2021-04-29 12:51:39 : Tracking by Mathias Ghys
Description
Implementation done as part of CP-050
Assignment 2021-04-29 12:45:25 : Assigned To Mathias Ghys by Mathias Ghys
Tracking Open 2021-04-29 12:45:24 : Tracking by Mathias Ghys
Description
Finding:

- In the hl7:manufacturedMaterial template the property of type asContent has cardinality 0..* but the XSD files only contain a single value (XSD cardinality is 0..1):

<xs:element ref="epsos:asContent" minOccurs="0" maxOccurs="1"/>
In the IPS, where the pharmacy profile is used, it is also possible to provide multiple asContent elements:

<xs:element ref="epsos:asContent" minOccurs="0"/>
Suggestion:

- Proposed solution is to set the enclosing hl7:name element to mandatory.

Further explanation:

- Link to JIRA issue: https://ec.europa.eu/cefdigital/tracker/browse/EHSEMANTIC-645

    
Labels
Preview Code HTML color Display Name Description
 
 TBA 
TBA TBA To be approved
To be discussed and approved
 
 M1 
M1 M1 Milestone 1
Milestone 1 – before the EXPAND-athon 9-12 December 2015 Lisbon
 
 M2 
M2 M2 Milestone 2
Milestone 2 – final results to be delived at the end of EXPAND
 
 M3 
M3 M3 Milestone 3
Milestone 3 – end of the HL7 International Project
 
 M4 
M4 M4 Milestone 4
Milestone 4 – for consideration in the future / desiderata
 
 WJ 
WJ WJ Changes Word/JIRA
Changes in the Word Specification/Open a JIRA issue
 
 TID 
TID TID Template ID
Template-ID changes throughout the specification