Stream: IG creation
Topic: IG publisher snapshot error
Brian Reinhold (Oct 07 2018 at 00:29):
I get the following error building the IG using Lloyd's framework approach. It does not seem to effect the build but something must be wrong. The error is
Error in snapshot generation: valueQuantity has an element that is not marked with a snapshot match
Does anyone understand what this error means and how to fi it?
Lloyd McKenzie (Oct 07 2018 at 01:17):
It means that your hierarchy isn't complete in the differential. Every element in the differential needs to have all ancestors present - though you don't have to say anything about them.
Brian Reinhold (Oct 07 2018 at 21:49):
It means that your hierarchy isn't complete in the differential. Every element in the differential needs to have all ancestors present - though you don't have to say anything about them.
@Lloyd McKenzie
I do have the Device as the baseDefinition (its only the property giving me trouble)
My first element for the property differential is
<!-- PROPERTY: This element is going to be sliced for time capabilities, clock resolution, time synchronization,
synchronization accuracy, PAN certification lists, and regulations status. There can be many property elements
for PHDs. -->
<element id="Device.property">
<path value="Device.property" />
<slicing>
<!-- The type.system and the type of value (code or quantity) are needed to distinguish entrants. The BITs properties
(time capabilities and regulation status) will have a fixed system ASN1-url with a coded value. The remaining entrants
will have the same fixed 10101-url with either a single-coded, multiple-coded, or quantity entry. -->
<discriminator>
<type value="value" />
<path value="type.coding.system" />
</discriminator>
<discriminator>
<type value="type" />
<path value="$this" />
</discriminator>
<rules value="open" />
</slicing>
<!-- There will, at minimum be a MDC_TIME_SYNC_PROTOCOL entry -->
<min value="1" />
</element>
which seems okay. The slices are defined after.
Brian Reinhold (Oct 08 2018 at 11:53):
It means that your hierarchy isn't complete in the differential. Every element in the differential needs to have all ancestors present - though you don't have to say anything about them.
I have the answer. There is a typo in the spec on the Device.property.valueQuanity. I was spelling it correctly Device.property.valueQuantity. Note the missing 't'. I ran into the same problem in HAPI FHIR which took me hours to solve! I have already submitted a change request for it during the HL7 meeting last week.
Last updated: Apr 12 2022 at 19:14 UTC
