Stream: IG creation
Topic: Type constraint not respected in complex Extension
Joshua Kelly (Feb 15 2022 at 15:45):
When constraining a value type in a complex Extension, it seems that the Publisher does not correctly output the constraints on type and instead outputs a list of all possible types.
Here's an example of what I mean in an IG.
This Extension displays the following types:
http://hl7.org/fhir/us/insurance-card/2022Jan/StructureDefinition-C4DIC-Coverage-definitions.html#Coverage.extension:C4DIC-PlanBeneficiaries-extension
Screen-Shot-2022-02-15-at-10.43.04-AM.png
The FSH backing this extension looks like the following:
Extension: PlanBeneficiaries
Id: C4DIC-PlanBeneficiaries-extension
Title: "Plan Beneficiaries"
Description: "This extension allows for the representation of all of the members on the plan with corresponding Names and MemberIDs. This enables health plans to pass this information along with the Coverage resources to align with how this content is printed on physical insurance cards."
* ^context[0].type = #element
* ^context[0].expression = "Coverage"
* extension contains
memberId 1..1 MS and
name 1..1 MS
* extension[memberId] ^short = "Member Id"
* extension[memberId].value[x] 1..1
* extension[memberId].value[x] only string
* extension[name] ^short = "Member Name"
* extension[name].value[x] 1..1
* extension[name].value[x] only HumanName
* extension[name].valueHumanName.family 1..1 MS
* extension[name].valueHumanName.given 0..* MS
Is there a correct way to achieve the result of correctly showing the actual value type constraints for a complex Extension or is this a bug?
Grahame Grieve (Mar 01 2022 at 09:51):
no that rendering is definitely wrong.
Grahame Grieve (Mar 01 2022 at 10:16):
fixed next release
Grahame Grieve (Mar 01 2022 at 10:16):
Joshua Kelly (Mar 28 2022 at 15:02):
Thanks!
Confirmed that this is resolved and our builds work as expected now.
Screen-Shot-2022-03-28-at-9.59.09-AM.png
Cille Kissel Watkins (Mar 28 2022 at 15:16):
Thank you both! Is there a timeline for when this might be fixed in the auto-ig-publisher?
Jose Costa Teixeira (Mar 28 2022 at 15:55):
@Cille Kissel Watkins I don't know a timeline but (in case you don't know) you can check here:
https://chat.fhir.org/#narrow/stream/217600-tooling.2Freleases/topic/java.20IGPublisher
When there is a new notification, you should have the problem fixed
Grahame Grieve (Mar 28 2022 at 21:44):
Is there a timeline for when this might be fixed in the auto-ig-publisher?
That always runs the current version, so it should be fixed, but someone needs to re-trigger a build
Last updated: Apr 12 2022 at 19:14 UTC
