Loading...
Help
Login
Busy
Search
eHDSI - Templates
 
Template locked

OK Not OK
Templates (External repositories)

Warning Ok
Warning
Filter
epSOS CDA Material
Issues (8)
Change Request Status = Feedback needed (epsos-issue-187): units in ingredient/quantity
TypeChange RequestStatusChange Request Status = Feedback needed PriorityNormal
Current Labels
 
 (TBA) To be approved 
Events
Assignment2017-07-18 23:19:06: Assigned To Christof Gessner by Christof Gessner
 
 TBA 
Tracking / Status = Feedback needed 2017-07-17 12:46:39: Tracking by Dr. Kai U. Heitmann
 
 TBA 
Description
I'm not sure without re-reading our manual but I think if the binding is CWE a warning is generated instead of an error.
Tracking / Status = Feedback needed 2017-07-17 11:15:29: Tracking by Christof Gessner
 
 TBA 
Description
How to tell the template to create schematron entries with a warning and not an error?
Tracking / Status = Open 2017-07-16 13:09:11: Tracking by Dr. Kai U. Heitmann
 
 TBA 
Description
Which would be easy: simply bind value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.16 epSOSUnits to it
Tracking / Status = Open 2017-07-15 18:41:32: Tracking by Christof Gessner
 
 TBA 
Description
Finding:

- units in numerator and denominator are not checked agains unit value set

Suggestion:

- add a warning if unit is not in value set

Further explanation:

-

Change Request Status = Closed (epsos-issue-207): Support for Multiple Active ingredient in ART-DECOR
TypeChange RequestStatusChange Request Status = Closed PriorityHigh
Current Labels
 
 (TBA) To be approved 
Events
Assignment2017-10-12 16:05:22: Assigned To Christof Gessner by Christof Gessner
 
 TBA 
Tracking / Status = Closed 2017-10-12 15:56:11: Tracking by Christof Gessner
 
 TBA 
Description
Yes, it looks like an error in the current IG version. In the original PDF spec under rule R4.3 we see that manufacturedMaterial/ingredient/[@classCode='ACTI']/ingredient/name is on the same lavel as manufacturedMaterial/ingredient/[@classCode='ACTI']/ingredient/code

Also, the levels of originalText and translation are strange. I believe they should be under manufacturedMaterial/ingredient/[@classCode='ACTI']/ingredient/code.

I changed the template, moving originalText and translation under code, and moving name to the same level as code.
Assignment2017-10-12 11:45:56: Assigned To Marta Terrón Cuadrado by Mathias Ghys
Tracking / Status = Open 2017-10-12 11:45:55: Tracking by Mathias Ghys
Description
Finding:

- We noticed that in ART-DECOR, there is an inconsistency for the Ingredient element definition. The Ingredient element can be found here: http://art-decor.org/art-decor/decor-templates--epsos-?id=2.16.840.1.113883.3.1937.777.11.10.143&effectiveDate=dynamic . There is stated that the name is under the epsos:ingredient top level element, but based on the schema of epSOS for CDA, the name element must be defined one level lower, together with the code element:


Suggestion:

- I suggest the ART-DECOR implementation guide to be adapted to correspond with the epSOS CDA schema

Further explanation:

-

Change Request Status = Closed (epsos-issue-208): Schema Error for draft element "hl7:desc"
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Current Labels
 
 (TBA) To be approved 
Events
Tracking / Status = Closed 2017-10-27 16:22:22: Tracking by Mathias Ghys
 
 TBA 
Description
Solved by changing the namespace prefix from hl7 to epsos
Tracking / Status = In Progress 2017-10-25 09:49:13: Tracking by Christof Gessner
 
 TBA 
Description
In the original PDF specs the element was introduced. And it was under the namespace for epSOS extensions (like formCode etc.). In that way it would not violate the CDA schema.

Tracking / Status = Closed 2017-10-25 09:02:49: Tracking by Giorgio Cangioli
Description
Could you explain to me this issue ?

the element 'desc' is not part of the CDA base schema, but is part of the epSOS CDA extensions...

as several other elements used in the epSOS CDAs...
Tracking / Status = Closed 2017-10-25 08:55:29: Tracking by Mathias Ghys
Description
I removed the newly added element.
The schema error will now be gone
Assignment2017-10-25 00:20:14: Assigned To Mathias Ghys by Christof Gessner
Tracking / Status = Open 2017-10-25 00:20:13: Tracking by Christof Gessner
Description
Finding:

- We get a schema Error for instances that use new draft element "hl7:desc" : 

In content of element <manufacturedMaterial>: The content model does not allow element <Q{urn:hl7-org:v3}desc> to appear immediately after element <Q{urn:hl7-org:v3}name>.

Suggestion:

- remove the newly added element
- specify the requirements that triggered the introduction
- find a conformant solution that fulfills the requirements

Further explanation:

-The element violates the CDA schema.

Change Request Status = Open (epsos-issue-248): hl7:name cardinality must be changed from 0 ... 1 to 1 ... 1
TypeChange RequestStatusChange Request Status = Open PriorityNormal
Current Labels
 
 (TBA) To be approved 
Events
Assignment2017-12-18 10:50:39: Assigned To Mathias Ghys by Mathias Ghys
 
 TBA 
Tracking / Status = Open 2017-12-18 10:50:38: Tracking by Mathias Ghys
 
 TBA 
Description
Finding:  

- outcome of gap analysis of Abderrazek: consumable/manufacturedProduct/manufacturedMaterial/name required. In Expand the Cardinality is for the element is: (eP/eD/PS: R/NA/NA).

Suggestion:

- Change the cardinality from 0 ... 1 to 1 ... 1

Further explanation:

-

Change Request Status = Closed (epsos-issue-259): No conformance set for ActiveIngredient substance name
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Current Labels
 
 (TBA) To be approved 
Events
Tracking / Status = Closed 2020-07-13 14:30:08: Tracking by Mathias Ghys
 
 TBA 
Description
No fix. CDA IGs are aligned with the EXPAND PDF Spec (this corresponds to 4.3). Since the datatype is ST, using nullFlavor is not an option.
Assignment2018-04-05 11:51:38: Assigned To Mathias Ghys by Mathias Ghys
 
 TBA 
Tracking / Status = Open 2018-01-31 18:20:32: Tracking by Christof Gessner
 
 TBA 
Description
In the EXPAND PDF Spec this corresponds to R4.3, saying that this element is optional. As the  datatype is ST, using nullFlavor is not an option. However, in the code element you also have the name.
Assignment2018-01-31 16:49:51: Assigned To Mathias Ghys by Mathias Ghys
 
 TBA 
Tracking / Status = Open 2018-01-31 16:49:50: Tracking by Mathias Ghys
 
 TBA 
Description
Finding:

- I noticed that no conformance is set for the name of the substance (under the ingredient element). This has to be at least 'REQUIRED' according to the guidelines.

Suggestion:

- Set the conformance to 'R'

Further explanation:

-

Change Request Status = Closed (epsos-issue-270): Adapt form code example to contain the new OID for the EDQM code system
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Events
Tracking / Status = Closed 2018-05-18 09:30:16: Tracking by Mathias Ghys
Description
modified the example and the erroneous namespace prefix was fixed by dr Kai Heitmann
Assignment2018-05-17 10:11:29: Assigned To Mathias Ghys by Mathias Ghys
Tracking / Status = Open 2018-05-17 10:11:28: Tracking by Mathias Ghys
Description
Finding:

- Example for the formCode is still using the old OID.

Suggestion:

- Adapt it to the new OID (0.4.0.127.0.16.1.1.2.1)

Further explanation:

-

Change Request Status = Open (epsos-issue-272): restrict formCode CONF to epSOSPackage value set for asContent part
TypeChange RequestStatusChange Request Status = Open PriorityNormal
Events
Assignment2018-05-25 11:52:02: Assigned To Mathias Ghys by Mathias Ghys
Tracking / Status = Open 2018-05-25 11:52:01: Tracking by Mathias Ghys
Description
Finding:

- In the asContent element we see the following description:
This structure describes the packaging of the medication. The element provides the code for the particular package.

But if we go into the formCode, we have the freedom to choose from the eHDSIDoseForm value set OR the eHDSIPackage value set. In my opinion, the Pharmaceutical dose form has to come into the formCode element under the manufacturedMaterial level and the formCode element under the /asContent/containerPackageMedicine can only contain values from the eHDSIPackage value set

Suggestion:

- Remove the possibility to have a value from the 2 value sets.

Further explanation:

-

Change Request Status = Closed (epsos-issue-284): Remove constraint that @unit value has to come from UCUM value set for capacityQuantity
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Events
Tracking / Status = Closed 2018-11-20 08:49:32: Tracking by Mathias Ghys
Description
Constraint removed after approval by the semantic group during the semantic F2F meeting in Brussels on the 12/13th of November 2018.
Added a textual constraint.
Assignment2018-08-17 08:33:57: Assigned To Mathias Ghys by Mathias Ghys
 
 TBA 
Tracking / Status = Open 2018-08-17 08:33:56: Tracking by Mathias Ghys
 
 TBA 
Description
Finding:

- Since CP-09, also UCUM annotations are supported, like {tablet}. These value are not part of our current epsosUnits resulting in a validation failure if they are present in the CDA document. There are two possibilities:
- Adding the UCUM annotations to the value set
- Removing the constraint from the ART-DECOR IG (maybe we can only keep a textual constraint)

Suggestion:

-

Further explanation:

-

 
 
Busy
Structure Definitions (External repositories)