Stream: IG creation
Topic: New IG publisher woes
Brian Reinhold (Jan 22 2021 at 13:26):
Previously I could point to a structure definition in my mark-down page file using
The structure definition for this profile is given [here](PhdBitsEnumerationObservation.html)
That no longer works. What changed?
John Moehrke (Jan 22 2021 at 13:34):
you need the filename prefix of StructureDefinition-
here](StructureDefinition-PhdBitsEnumerationObservation.html)
Brian Reinhold (Jan 22 2021 at 13:41):
John Moehrke THanks for that. I figured it out by looking at the local output file and saw that the 'StructureDefinition-' was prefixed before the html file. Now I am going to have to go through my entire guide and check all the links to see what else has changed. And there are hundreds of them! :frown:
New news! Looks like links to my other pages have NOT been changed! :grinning:
Lloyd McKenzie (Jan 22 2021 at 14:17):
If you look at the qa.html page, you'll get a list of all broken links (and any other validation issues with your IG)
Brian Reinhold (Jan 22 2021 at 16:45):
Lloyd McKenzie said:
If you look at the qa.html page, you'll get a list of all broken links (and any other validation issues with your IG)
Yes I noted that. I had about 60 links to fix. There were links in the Structure definitions I could not fix; I could not find where they were but I believe those links are broken because they reference coding systems that are part of this guide and the links are those that WILL exist when the guide gets published, but that has not yet happened. Just a guess.
Lloyd McKenzie (Jan 22 2021 at 17:21):
If they're links that will exist (and content is properly defined in the IG), the publisher shouldn't yell about those. It's possible there's a publisher bug, but it's also possible there's a problem with the links (e.g. character case)
Brian Reinhold (Jan 25 2021 at 10:18):
Lloyd McKenzie
I get broken links like this:
The link 'StructureDefinition-PhdBaseObservation-definitions.html#Observation.component:supplementalTypesComponent.valueCodeableConcept:valueCodeableConcept' for "valueCodeableConcept:valueCodeableConcept" cannot be resolved (valid targets: 303 targets)
I get 27 of them. All of the errors seem to be representing value sets with system values like this <system value="urn:iso:std:iso:11073:10101"/>. That is the IEEE 11073 10101 set of Nomenclature codes used by medical devices following the IEEE 11073 standards. I seem to have a lot of issues related to references to that system.
I posted as similar problem on Jan 22: IG Publisher: Does not resolve. It references a value set from an IG (Point of Care Devices) that is still a work in progress. But the value set also references <system value="urn:iso:std:iso:11073:10101"/>
Jose Costa Teixeira (Jan 25 2021 at 10:58):
@Brian Reinhold can we reproduce this?
Brian Reinhold (Jan 25 2021 at 11:41):
Jose Costa Teixeira
Would the project on git-hub be sufficient to do that?
https://build.fhir.org/ig/HL7/PHD/
I just pushed the latest version. If not, what would you need?
Lloyd McKenzie (Jan 25 2021 at 15:23):
The path in your StructureDefinition should be "value[x]", not "valueCodeableConcept".
Brian Reinhold (Jan 25 2021 at 16:25):
Lloyd McKenzie said:
The path in your StructureDefinition should be "value[x]", not "valueCodeableConcept".
Now I am confused ... how do I separate the various descrimators?
<element id="Observation.component:supplementalTypesComponent.value[x]:valueCodeableConcept">
<path value="Observation.component.valueCodeableConcept" />
<sliceName value="valueCodeableConcept" />
<definition value="The information determined as a result of making the observation, if the information is a code." />
<min value="1" />
<type>
<code value="CodeableConcept" />
</type>
</element>
<element id="Observation.component:supplementalTypesComponent.value[x]:valueCodeableConcept.coding">
<path value="Observation.component.valueCodeableConcept.coding" />
<slicing>
<discriminator>
<type value="value" />
<path value="system" />
</discriminator>
<rules value="open" />
</slicing>
<min value="1" />
</element>
<element id="Observation.component:supplementalTypesComponent.value[x]:valueCodeableConcept.coding:MDCType">
<path value="Observation.component.valueCodeableConcept.coding" />
<sliceName value="MDCType" />
<short value="Required MDC code entry." />
<min value="1" />
<max value="1" />
</element>
<element id="Observation.component:supplementalTypesComponent.value[x]:valueCodeableConcept.coding:MDCType.system">
<path value="Observation.component.valueCodeableConcept.coding.system" />
<min value="1" />
<fixedUri value="urn:iso:std:iso:11073:10101" />
</element>
<element id="Observation.component:supplementalTypesComponent.value[x]:valueCodeableConcept.coding:MDCType.code">
<path value="Observation.component.valueCodeableConcept.coding.code" />
<definition value="For the given Supplemental-Types entry the code here is given by: partition * 2**16 + term code" />
<min value="1" />
</element>
<element id="Observation.component:supplementalTypesComponent.dataAbsentReason">
<path value="Observation.component.dataAbsentReason" />
<max value="0" />
</element>
Is it just Observation.component.value[x] in every case?
Brian Reinhold (Jan 26 2021 at 09:48):
Lloyd McKenzie said:
The path in your StructureDefinition should be "value[x]", not "valueCodeableConcept".
Any modification of the 'path' elements above causes the build to fail. However, If it is just the first path element, that seems to work. I guess that is what you meant - not the path element in the slices???
Lloyd McKenzie (Jan 26 2021 at 14:35):
I would expect to see value[x] in both the path and the id everywhere...
Brian Reinhold (Jan 26 2021 at 21:02):
Lloyd McKenzie said:
I would expect to see value[x] in both the path and the id everywhere...
I had it in the id, placed it in all the paths of the slices (did not build) but then put it in only the first one and not the slices. All those errors went away.
3 left.
Last updated: Apr 12 2022 at 19:14 UTC
