Stream: implementers
Topic: Id fields
Patrik Sundberg (Sep 13 2018 at 18:06):
Out of curiosity, what do people use the "id" field on extensions for, in practice? And the "id" field on primitive types? And on non-top-level backbone elements inside resources? I'm trying to understand the use cases.
Lloyd McKenzie (Sep 13 2018 at 18:18):
Primary use is if you want to point to something in one place in the instance from another place in the instance - which would almost always have to be done with an extension. At one point we thought we'd point from narrative elements to discrete data this way too, but it turned out to be better to point from the narrative to the data.
Patrik Sundberg (Sep 13 2018 at 18:58):
could you point me to some examples? this makes sense in theory but i haven't come across any such use cases in practice.
Lloyd McKenzie (Sep 13 2018 at 19:01):
Nor have I. I'm not aware of a place where we're currently using it.
Grahame Grieve (Sep 15 2018 at 00:50):
there's some places where it's required in CDA, and so you end up with the same set up in FHIR. @Jean Duteau can describe them better
Michel Rutten (Sep 17 2018 at 09:27):
The id attribute also uniquely identifies named slices, e.g. in complex extensions and sliced backbone elements.
Last updated: Apr 12 2022 at 19:14 UTC
