Stream: IG creation
Topic: IGPub Warning: Models - type value provided not in value set
Chris Moesel (Mar 25 2018 at 23:13):
Another issue w/ using logical model URLs in type.code fields, it causes warnings like the following:
Path: StructureDefinition/oncology-BreastCancerNCategory-model: StructureDefinition.snapshot.element[6].type.code
Severity: warning
Message: The value provided ('http://hl7.org/fhir/us/breastcancer/StructureDefinition/oncology-StageSuffix-model') is not in the value set http://hl7.org/fhir/ValueSet/defined-types (http://hl7.org/fhir/ValueSet/defined-types, and a code should come from this value set unless it has no suitable code) (error message = Unknown Code http://hl7.org/fhir/us/breastcancer/StructureDefinition/oncology-StageSuffix-model in http://hl7.org/fhir/ValueSet/defined-types)
I believe this is an appropriate and expected use case, as according to the documentation of type.code:
Absolute URLs are only allowed in logical models.
If I'm doing something wrong, please let me know. Otherwise, it would be nice if the publisher didn't flag this when the structure definition's kind is logical.
Grahame Grieve (Mar 26 2018 at 03:32):
so this is a generic warning triggered by extensible bindings.
Chris Moesel (Mar 26 2018 at 12:46):
Yep. I'm just wondering if in the case of logical models, it should be suppressed -- because I think it's a normal use case if you have compositional models. Not high priority -- just something to consider. Otherwise our IG will always have hundreds of warnings even though we're not doing anything that is actually suspicious.
Grahame Grieve (Mar 26 2018 at 18:59):
well, that's a general issue with that warning...
Last updated: Apr 12 2022 at 19:14 UTC
