Stream: IG creation
Topic: history of changes
John Moehrke (Jul 07 2020 at 15:13):
I now have a history of changes on the IHE FormatCode vocabulary. But only one of two history entries is showing up.
See http://build.fhir.org/ig/IHE/FormatCode/branches/master/CodeSystem-formatcode.html
Jose Costa Teixeira (Jul 07 2020 at 16:51):
your bundle has only one entry
Jose Costa Teixeira (Jul 07 2020 at 18:13):
add this to your provenance bundle, between line 55 and 56:
</resource>
</entry>
<entry xmlns="http://hl7.org/fhir">
<fullUrl value="http://ihe.net/fhir/ihe.formatcode.fhir/Provenance/20200703-1"/>
<resource>
Jose Costa Teixeira (Jul 07 2020 at 18:13):
that will render
John Moehrke (Jul 07 2020 at 18:22):
thanks... oops
John Moehrke (Jul 07 2020 at 18:41):
Yeah, that did solve it. Thanks @Jose Costa Teixeira
John Moehrke (Jul 07 2020 at 18:41):
Now, How do I resolve the error it is throwing on the history
Error: Unable to find ImplementationGuide.definition.resource.name for the resource Bundle/history-IHE-formatcode.codesystem. Name is mandatory if it cannot be inferred from the resource to allow proper population of the artifact list.
Jose Costa Teixeira (Jul 07 2020 at 18:47):
I don't like the implications of that one - @Lloyd McKenzie what do we do with resources that do not have a name?
Lloyd McKenzie (Jul 07 2020 at 18:57):
You have to list the resource in the IG and declare one
Lloyd McKenzie (Jul 07 2020 at 18:57):
E.g. for examples
John Moehrke (Jul 07 2020 at 19:00):
it is an ever increasing set of Provenance resources
Jose Costa Teixeira (Jul 07 2020 at 19:13):
you list the bundle, not the provenances individually
John Moehrke (Jul 07 2020 at 19:13):
the sample-ig throws the same error
Lloyd McKenzie (Jul 07 2020 at 19:13):
If that's for history, those shouldn't be listed in the ToC at all...
John Moehrke (Jul 07 2020 at 19:14):
I was not expecting history to show up in the TOC... just wondering what to do about this error
Jose Costa Teixeira (Jul 07 2020 at 19:14):
sorry, i was misleading then. question should be - how to avoid the error when we are not interested in the resource's name?
John Moehrke (Jul 07 2020 at 19:15):
it is an error and a warning
Lloyd McKenzie (Jul 07 2020 at 19:46):
The bundle shouldn't be showing up in the list of IG artifacts - or at least needs to be excluded when generating the table of contents
John Moehrke (Jul 07 2020 at 19:48):
so, how do I do either of those?
Lloyd McKenzie (Jul 07 2020 at 19:48):
You don't - it's a template issue
Jose Costa Teixeira (Jul 07 2020 at 19:48):
we have to work on that on the template, right? now that history is a resource folder..
John Moehrke (Jul 07 2020 at 19:48):
it shows up in the TOC as an empty header
John Moehrke (Jul 07 2020 at 19:49):
seems history would not be TOC worthy. unless it was history of the IG itself.
John Moehrke (Jul 07 2020 at 19:50):
Jose Costa Teixeira said:
we have to work on that on the template, right? now that history is a resource folder..
im not convinced it should be a folder.
Jose Costa Teixeira (Jul 07 2020 at 19:50):
@Lloyd McKenzie what do we exclude? not all bundles. Only bundles in "history" (not really elegant)? How do we do if the IG wants to actually publish a bundle of provenances?
Jose Costa Teixeira (Jul 07 2020 at 19:51):
perhaps we need a special indicator (blacklist or extension) to exclude some artifacts from the IG ToC
Lloyd McKenzie (Jul 07 2020 at 20:35):
@Grahame Grieve Is the publisher able to expose when a resource is being used to convey history?
Grahame Grieve (Jul 07 2020 at 22:13):
that's not really something that has a clearly defined meaning observationally. If a bundle has only provenance resources, how I do know that it's being used to convey history?
Last updated: Apr 12 2022 at 19:14 UTC
