Setting FindResourceInfoOptions.type to ['Type'] excludes StructureDefinitions having the same StructureDefinition.type value

[Paqrat76]

When setting the FindResourceInfoOptions.type filter to ['Type'], the returned StructureDefinitions exclude complex-type StructureDefinitions having the same StructureDefinition.type value. Specifically, the Quantity StructureDefinition IS returned but the MoneyQuantity and SimpleQuantity StructureDefinitions are NOT returned. All three of these StructureDefinitions have StructureDefinition.type = 'Quantity'.

Is this intentional?

How can I use the FindResourceInfoOptions to return all complex-types?

[cmoesel]

Hi @Paqrat76! Aren't you supposed to be retired?! ;-)

The FPL does not return MoneyQuantity or SimpleQuantity when you ask for Type because those are actually just profiles on the Quantity type. The code comment documentation on Type defines Type as:

a StructureDefinition w/ kind "primitive-type", "complex-type", or "datatype" & derivation "specialization"

If you look at the MoneyQuantity SD and SimpleQuantity SD, they both have "derivation": "constraint".

If you want to additionally find the profiles of types, you'd have to search by type profile and then filter the results based on kind (allowing for primitive-type, complex-type, and datatype).

[Paqrat76]

Hi @cmoesel,

Thanks for the clarification. I should have known that but I didn't look close enough.

Yes, I'm retired but, along with working on model cars, I'm working on a project that will generate TypeScript FHIR data models heavily inspired by the HAPI FHIR data models in Java. Between July 2024 and Feb 2025, I completed a proof-of-concept project for what I needed/wanted in these TypeScript FHIR data models. See typescript-hapi-models-poc. It contains utilities, primitive FHIR data types, etc. that will become a core library for generated data models.

I used this POC project to create a new mono-repo project (ts-fhir-datamodels) that will use a generator to consume StructureDefinitions and CodeSystems to generate FHIR data models for complex types and resources for each FHIR release. It is still early in development, but I'm making progress and having fun doing it.

I'm using FPL in the generator app. I really like what you and the team did with FPL 2, and I've seen the transition of Sushi and related tools to the FHIR Foundation on GitHub. Maybe after I finish my current project, I'll look into contributing to Sushi.

[cmoesel]

Ooooh. That's all very exciting and the TS stuff looks cool! Have fun!

As for FPL 2, I like it too. It's a lot more flexible and will allow us to support more complicated dependency workflows in the future. That said, if you think it really should support searching by kind, feel free to submit a PR!

[cmoesel]

Also, we'll gladly take your help on SUSHI. Our ability to contribute has been reduced by quite a bit, so we're really counting on the community stepping up!