Stream: IG creation
Topic: QA build errors from the generated text entry
Brian Reinhold (Dec 09 2021 at 14:43):
I got this error once before and for some reason it went away. I think I was getting it from doing the continuous versus the one-time build. But now its back. I am getting 24 errors and they are all due to the generated 'text' entry in each of my example resources. Something about a bad link. Why is the validator even looking at this entry? My example resources do not have one.
Lloyd McKenzie (Dec 09 2021 at 16:06):
Narrative gets generated for all resources as part of publication. Typically if the generated narrative has bad links, we won't stop you from publishing.
Grahame Grieve (Dec 09 2021 at 19:19):
why is it broken?
Stefan Karl (Dec 13 2021 at 15:54):
@Brian Reinhold, do you mean the broken links in the QA report of your CI build? I got similar errors when rebuilding the PoCD IG a few weeks ago (which haven't been reported in the September ballot version). The errors are about links from the profile's differential view to detailed descriptions for slices on data type choices. I got them fixed by replacing the specific type (e.g., valueQuantity) by generic type (e.g., value[x]) in the element.path expression.
Brian Reinhold (Dec 15 2021 at 14:44):
@Stefan Karl I checked the errors and they were only on one value[x] case and that was in the Observation.component. I have similar value[x] slices all over the place and they do not create the errors. However, when I do as you say on JUST the accuracy component in the Numeric, those errors do, indeed, go away. There are two more components that have such errors. The accuracy in the compound and the threshold and alert-op text strings in the Numeric.
Why not all the other sliced value[x]s where I DON'T have a value[x] in the path?
This
<element id="Observation.value[x]:valueQuantity.system">
<path value="Observation.valueQuantity.system" />
<min value="1" />
<fixedUri value="http://unitsofmeasure.org" />
</element>
causes no error.
Stefan Karl (Dec 15 2021 at 15:55):
I don't know. I got the errors in all slices and fixed them as described above.
Brian Reinhold (Dec 22 2021 at 22:16):
@Stefan Karl I went ahead and did it for all of the cases too, and all the errors did go away. I did not check which ones I could 'get away' with. Not sure I understand this. But I do recall (a couple of years ago) going around and entering all the value-specific text strings in the path in order to get it to work. It was so long ago I don't recall the reason.
Last updated: Apr 12 2022 at 19:14 UTC
