Stream: implementers
Topic: Type Changes in Resource Profile Types
Gino Canessa (Nov 05 2019 at 23:42):
Howdy, I just came across a change in the build output typing in the StructureDefinitions and was curious about it (e.g., boolean.profile.json). The change is the conversion from structuredefinition-<lang>-type to structuredefinition-fhir-type, which also included moving the field from type._code.extension to type.extension.
Overall the new method is much cleaner (yay!), but I was surprised by a bunch of odd behaviors in my tooling when it couldn't find the JSON types anymore.
My searching may not be up to scratch, but I can't find info on here or GForge, so figured I would ask. (Tagging @Grahame Grieve because this probably could've just been a PM to you : ).
Grahame Grieve (Nov 06 2019 at 00:55):
I’m not sure what you are asking here. yes, that changed. Yes, it’s cleaner
Gino Canessa (Nov 06 2019 at 01:00):
Was curious if there was notice/discussion somewhere I’m not looking (e.g, a different stream, etc). Hunting down what was happening took some time, and I would prefer to be proactive in the future.
Grahame Grieve (Nov 06 2019 at 01:01):
it was discussed at length in the #conformance stream. I’ll chase the discussion down
Gino Canessa (Nov 06 2019 at 01:11):
That was all I needed, wasn’t subscribed to that stream. Thanks!
Michel Rutten (Nov 06 2019 at 09:00):
The 4.0.1 release notes briefly mention this change:
http://hl7.org/fhir/R4B/history.html#v4.0.1
Fix up the definition of ElementDefinition.type.code for special elements (Element.id, Extension.url, [Primitive].value)
Last updated: Apr 12 2022 at 19:14 UTC
