CDA-core-2.0 icon indicating copy to clipboard operation
CDA-core-2.0 copied to clipboard

Published 20 hours ago • verified publisher icon HL7

ST as type specialization instead of constraint

Open oliveregger opened this issue 6 years ago • 1 comments

to define ST just as a constraint from me was an error, it gives a validation error:

Type 'ST' is not an acceptable type for 'value' on property Observation.value

Defining ST as proper own type as the others and specialized from ED (instead constraint from ED) resolves the validation problem.

oliveregger avatar Nov 13 '19 22:11 oliveregger

I'm not sure about this - what's an example?

grahamegrieve avatar Jun 21 '21 05:06 grahamegrieve

@grahamegrieve I have no more validation problems when I switch back to the constraint version.

The IG Publisher shows however two times the ED type in Observation.value instead of one ED, one ST.

image

This is not happening if it is defined with the specialization.

image

Is this an issue I should note for the IG Publisher or related to the CDA-Core model?

During testing I had a validation problem due to missing matching paths as Observation.value is not defined as Observation.value[x], will submit a PR for the validation code.

oliveregger avatar Feb 07 '23 16:02 oliveregger

Quite interesting though, the links are resolving to the correct datatype:

image

gabriel0316 avatar Feb 08 '23 07:02 gabriel0316

ST is now its own type (not specialized from ED, at least right now while figuring out some xmlText things).

benjaminflessner avatar Oct 03 '23 17:10 benjaminflessner