Loading...
Help
Login
Busy
Search
eHDSI - Issues
 
Select object
 
Results (1 / 1)
Id Issue Status Priority Type Date Assigned To Label
297Add schematron rule to avoid the schemaLocation attribute to being usedClosedNormalChange Request2020-04-30 07:43:34Mathias Ghys
 
Change RequestAdd schematron rule to avoid the schemaLocation attribute to being used
Idepsos-issue-297
StatusClosed
PriorityNormal
Last Tracking2020-04-30 07:43:34  by  Mathias Ghys
Current AssigneeMathias Ghys
    
Concerns
Template
epSOS-Patient Summary (epSOS Patient Summary)
/
/
Template1.3.6.1.4.1.12559.11.10.1.3.1.1.3 (2018-11-14 10:53:50) epSOS-Patient Summary
StatusRetired
/
-
/
-
Events
TrackingClosed2020-04-30 07:43:34: Tracking by Mathias Ghys
Description
Schematron rule added for every document level template and verified.
Fix already implemented since v3.0.0. RC1
Assignment2019-02-25 09:50:49: Assigned To Mathias Ghys by Mathias Ghys
TrackingOpen2019-02-25 09:50:48: Tracking by Mathias Ghys
Description
Finding:

- From the CDA book:

Do Not Use the schemaLocation Attribute


While the XML Schema Language allows a schema location to be associated with an XML

document by including a schemaLocation attribute associated with the http://www.

w3.org/2001/XMLSchema-instance namespace, this is explicitly PROHIBITED

by [ITS§1.4], and thus by the CDA standard.

Systems validating a CDA document are expected to provide their own schemas to use

during validation. This rule is sometimes broken by CDA implementers. Applications

receiving CDA documents should at the very least REMOVE the schemaLocation

attribute

from the document before processing it, if not rejecting documents containing

them completely. Downloading schema resources from arbitrary URLs or file locations for

validation can at the very least slow down your system, and could crash it or even worse,

cause a security breach. I have seen a number of different systems crash at testing events

upon seeing an otherwise valid CDA document containing a schemaLocation attribute

pointing to a file that does not exist.

Suggestion:

- Add a schematron rule to avoid the use of the schemaLocation attribute. Has to be added to every CDA Document Level Template.
JIRA issue has been created for this: https://ec.europa.eu/cefdigital/tracker/browse/EHSEMANTIC-385

Further explanation:

-

    
Labels
PreviewCodeHTML colorDisplay NameDescription
 
 TBA 
TBATBATo be approved
To be discussed and approved
 
 M1 
M1M1Milestone 1
Milestone 1 – before the EXPAND-athon 9-12 December 2015 Lisbon
 
 M2 
M2M2Milestone 2
Milestone 2 – final results to be delived at the end of EXPAND
 
 M3 
M3M3Milestone 3
Milestone 3 – end of the HL7 International Project
 
 M4 
M4M4Milestone 4
Milestone 4 – for consideration in the future / desiderata
 
 WJ 
WJWJChanges Word/JIRA
Changes in the Word Specification/Open a JIRA issue
 
 TID 
TIDTIDTemplate ID
Template-ID changes throughout the specification