FHIR Chat · Contained/local entity and references · questionnaire

Stream: questionnaire

Topic: Contained/local entity and references


view this post on Zulip Xiaocheng Luan (Jun 14 2019 at 15:32):

In Questionnaire (and perhaps for FHIR in general), for example, the same extension or Coding may be repeatedly used within the same resource and these things are quite verbose and can significantly inflate (easily double) the size of the data, making it cluttered and hard to read. I'm wondering whether it's possible to introduce (if not already exists) something like contained entities, where you define an "entity" or element, like a coding (with system, code, display, etc.) that can be referenced within the resource where the specific element/entity is used? Of course the resource def would need to be updated to allow such local references. Because the entities are defined within the resource, it should be pretty simple to manage/process, and should not impact readability if not making it easier to read. @Paul Lynch @Grahame Grieve

view this post on Zulip Lloyd McKenzie (Jun 14 2019 at 17:14):

That would reduce size but significantly increase complexity. And in the end, what you'd really be doing is a less effective version of what compression algorithms already do really well. The unit of re-use in FHIR is the resource. In a few places there are abilities to reference re-useable chunks inside a resource - but those are part of the design of that specific resource and are explicitly called out. There's no ability to "point" to a Coding already elsewhere in an instance and avoid repeating the system, code and display.

view this post on Zulip Xiaocheng Luan (Jun 17 2019 at 14:44):

Thanks for the response, I can see the point of simplicity and trade off, especially the unit of reuse argument, although repeating a structured data element value over and over again doesn't look very elegant.

view this post on Zulip Brian Postlethwaite (Jun 18 2019 at 00:15):

My experience with Fhir questionnaires doesnt feel like that's likely to occur.
If you're referring to repeating the same set of options for multiple questions, then you create a valueset with those concepts and share that. Which is then able to utilise http caches too during execution, even further reducing overall bandwidth used.

view this post on Zulip Lloyd McKenzie (Jun 18 2019 at 02:30):

If you've got 100 questions which are coded as "Strongly Agree", "Agree", ... then you will end up repeating the codings in the instance a whole lot. But in the grand scheme of things, that's not a typical occurrence.


Last updated: Apr 12 2022 at 19:14 UTC