Suggestion: Move autogenerated FHIR types to a separate package

[devmotion]

The autogenerated FHIR types are not required for the core functionality of FHIRClient, and additionally the file with the autogenerated FHIR types is extremely large (which means unnecessary parsing and precompilation in case they are not used). I think we could maybe strip down the package and move the autogenerated types to a separate package - only the downstream users that do not define their own FHIR types have to depend on it and load it. Moreover, FHIR types for other FHIR versions could be defined in additional packages.

[DilumAluthge]

Yeah, this sounds like a good plan to me.

[DilumAluthge]

Maybe JuliaHealth/FHIRTypes.jl or something like that?

[devmotion]

Or maybe JuliaHealth/FHIRR4Types.jl or something similar to make it clear that they are for version R4 (but that is only useful if there are plans to support multiple versions at some point)?

[DilumAluthge]

I was thinking we'd have a single package named JuliaHealth/FHIRTypes.jl, and then within the package, we could support multiple FHIR versions as different submodules, so e.g. FHIRTypes.R4 versus FHIRTypes.R5 versus etc.