Ok, so this became more complex than I expected. So, the actual fix for the constraint is in the "Fixed Constraint" commit. Since I wanted to use FSH I transformed the existing StructureDefinition for the Extension using GoFSH (First commit). Then the validator complained about not finding the definitions for the extension and the TobaccoUse profile and I decided to blame it on SUSHI 1.X not working with the validator so everything was upgraded to SUSHI 2.X according to the instructions here: https://fshschool.org/docs/sushi/migration/ Additionally, I had to rename most FHIR resource files to fit the SUSHI output naming scheme because the Publisher does not find them otherwise. (Migrate to SUSHI 2.X commit)
In this process I also found an slicing error in the TobaccoUse profile and file name typo in the etlTalend page file which have their own seperate commits to fix them.
Then I realized the IG-URL in the sushi config file was wrong which might have been the cause of the validator not finding the files generated by SUSHI in the first place but since I already migrated everything and it is working now I decided to stick with the whole SUSHI 2.X migration anyway.
Ok, so this became more complex than I expected. So, the actual fix for the constraint is in the "Fixed Constraint" commit. Since I wanted to use FSH I transformed the existing StructureDefinition for the Extension using GoFSH (First commit). Then the validator complained about not finding the definitions for the extension and the TobaccoUse profile and I decided to blame it on SUSHI 1.X not working with the validator so everything was upgraded to SUSHI 2.X according to the instructions here: https://fshschool.org/docs/sushi/migration/ Additionally, I had to rename most FHIR resource files to fit the SUSHI output naming scheme because the Publisher does not find them otherwise. (Migrate to SUSHI 2.X commit) In this process I also found an slicing error in the TobaccoUse profile and file name typo in the etlTalend page file which have their own seperate commits to fix them. Then I realized the IG-URL in the sushi config file was wrong which might have been the cause of the validator not finding the files generated by SUSHI in the first place but since I already migrated everything and it is working now I decided to stick with the whole SUSHI 2.X migration anyway.