Stream: terminology
Topic: Large Composes/Expansions
Bryn Rhodes (Mar 16 2021 at 00:14):
I'm looking for feedback on a few assumptions I'm making about how to handle large composes and expansions:
- From what I can see, the way to handle large composes would be by spreading the definition across multiple ValueSets and use a grouping ValueSet to bring them together. Some practical, implementation-defined limit on the number of concepts that could appear in a single ValueSet definition, but no need for the spec to say anything about that (and it doesn't, from what I can see).
- There is provision in the ValueSet expansion element for saying "this is a portion of the overall expansion, beginning at offset X", so in theory, you could have a "value set" with an expansion of 100,000 codes, and you would render that over the API with, say, 100 ValueSet instances, each with the same canonical, but different ids, each one with 1000 codes in it.
Bryn Rhodes (Mar 16 2021 at 00:15):
For systems that have implemented large value sets, is this how you've done it?
Bryn Rhodes (Mar 16 2021 at 00:15):
Or do you avoid persisting the expansion at all (i.e. the only way to get the expansion is through an invocation of the $expand operation?)
Lin Zhang (Mar 16 2021 at 08:19):
Sounds good
Lin Zhang (Mar 16 2021 at 08:24):
I mean it's disirable
Michael Lawley (Mar 16 2021 at 08:24):
We support arbitrary size expansions (from $expand) using count & offset parameters. In the expansion itself the offset is indicated as is the total, so you can determine that you've not got the whole thing and you can persist each expansion "page" separately.
Lin Zhang (Mar 16 2021 at 13:34):
(deleted)
Last updated: Apr 12 2022 at 19:14 UTC
