FHIR Chat · Logical Models - BackboneElement, ElementDefintion or both · implementers

Stream: implementers

Topic: Logical Models - BackboneElement, ElementDefintion or both


view this post on Zulip Richard Kavanagh (Feb 22 2016 at 20:45):

I'm creating a tool for creating FHIR Logical Models. As such I need to cater for "BackboneElements" or "ElementDefintions" when the models are being created. As I don't think there is any firm decision as yet on which class should be used within a Logical Model, I'll cater for either. My question is would a model ever use a mixture of the two or would it be sensible to expect consistency within a single model?

view this post on Zulip Grahame Grieve (Feb 22 2016 at 20:47):

firstly, it's Element vs BackboneElement (not ElementDefinition)

view this post on Zulip Richard Kavanagh (Feb 22 2016 at 20:47):

Yep, my mistake

view this post on Zulip Grahame Grieve (Feb 22 2016 at 21:01):

I think that in general, a logical model wouldn't make use of extensibility, and especially modifier extensibility

view this post on Zulip Grahame Grieve (Feb 22 2016 at 21:01):

but I can also cases where the same logic as in the base specification applies

view this post on Zulip Grahame Grieve (Feb 22 2016 at 21:02):

but the principle we've defined as part of the spec would also be applicable: we limit the places where modifier extensions can be found

view this post on Zulip Grahame Grieve (Feb 22 2016 at 21:02):

given that, it would seem reasonable for a logical model to decide for itelf where it wants to use element or backbone element


Last updated: Apr 12 2022 at 19:14 UTC