Generate extension classes from IG

[bschaffh]

I am currently using the fhir-codegen to generate the vallue sets frome the FrCore Project.

I would like to know if it would be possible to generate the classes that represents the extension. From what i've read, i've understood that for the moment it is not possible to generate classes for the profiles according to their structure definition, but what about the extensions and the slices (for example the Identifiers for Patient ) ? It would make me avoid to write the extensions classes manually and generate them from the tool..

Thank's for reading and for your attention !

[GinoCanessa]

Hi @bschaffh! This looks like a duplicate of #145 , but to be sure - are you asking for those classes in C#, or another language (e.g., one you are exporting yourself)?

The core software already supports loading everything we should need for the extensions, so it is mostly a function of what we want the exports to look like. I have a pretty good handle on the 'first cut' planned for interop with the Firely Net SDK, but if this is for another language I am happy to work through what it would look like with you.

Cheers!

[bschaffh]

Hi ! Thank you for you answer.

I want to generate the classes in C# as you said, but I didn't find a way to generate the extensions and slices in a way that I wouldn't have to populate a Extension object in C# with the fields that are fixed in the IG.

For example, in the FrCorePatient profile, some values are defined and fixed for the slices of the Identifier (URL, Use, etc). These values are defined in the StructureDefinition.json, so I was expecting the tool to generate a class (for example Identifier INS-C, wich is a slice of Identifier) where the fixed fields values are already set, that would avoid me to fill the fields manually.

For the moment, I can only use the valueSets classes coming from the FrCore project, but I would like to use the values defined in Profiles, Extensions and slices too.

[preston]

Just checking in if there's been movement on this? I'm only interested in TypeScript types, though.

[GinoCanessa]

It is on my list for after the cross-version work is finished (which has been more of a slog than I hoped). No specific ETA, but happy to accept contributions in the meantime :-).

[wiegell]

@GinoCanessa - are there any current/upcoming features that are blocking for the start of this work?
If not - could you point to some of the related files and would you be able to guide me and a colleague if we were to try and tackle this?
@bakgaard tagging you FYI