Stream: IG creation
Topic: v1.1.40 Good news and Bad News
Saul Kravitz (Nov 11 2020 at 18:11):
Good news: Carin-BB IG builds without fatal errors.
Bad news: There are a bunch of new errors reported https://build.fhir.org/ig/HL7/carin-bb/branches/v0.1.10/qa.html
These are of several types, but I suspect there is one root cause.
1) internal: https://build.fhir.org/ig/HL7/carin-bb/branches/v0.1.10/qa.html#internal
- e.g.: The link 'StructureDefinition-C4BB-ExplanationOfBenefit-Inpatient-Institutional-definitions.html#ExplanationOfBenefit.adjudication.category' for "category" cannot be resolved (valid targets: 493 targets) .
- this is the first build of the IG publisher that has this error.
2) problems in the referenced profile relating to the differential view:
-e.g.: StructureDefinition profile http://hl7.org/fhir/us/carin-bb/StructureDefinition/C4BB-ExplanationOfBenefit-Inpatient-Institutional: Differential contains path ExplanationOfBenefit.ttp://hl7.org/fhir/StructureDefinition/ExplanationOfBenefit#ExplanationOfBenefit.item.adjudication.amount which is not found in the in base profile http://hl7.org/fhir/us/carin-bb/StructureDefinition/C4BB-ExplanationOfBenefit-Inpatient-Institutional
3) problems in the referenced profile relating to the snapshot:
- e.g.: No match found in the generated snapshot: check that the path and definitions are legal in the differential (including order)
4) Errors relating to slicing:
- e.g.: The profile http://hl7.org/fhir/us/carin-bb/StructureDefinition/C4BB-ExplanationOfBenefit-Inpatient-Institutional has 5 elements in the differential (id: ExplanationOfBenefit.adjudication.category, id: ExplanationOfBenefit.adjudication:adjudicationamounttype.category, id: ExplanationOfBenefit.adjudication:adjudicationamounttype.amount, id: ExplanationOfBenefit.adjudication:denialreason.category, id: ExplanationOfBenefit.adjudication:denialreason.reason) that don't have a matching element in the snapshot: check that the path and definitions are legal in the differential (including order)
@Pat Taylor @Mark Roberts @Ryan Howells @Grahame Grieve
Grahame Grieve (Nov 12 2020 at 06:39):
well, it's certainly challenging how fixing a bug in one place makes a cascade of bugs appear elsewhere in apparently well tested code. Which turns out not to have any formal tests. (it does now)
This will be fixed next release. I'm just waiting on review of the other snapshot issue for doing another release
Last updated: Apr 12 2022 at 19:14 UTC
