Stream: terminology
Topic: Persisting Large Concept Maps
Brian Wright (Aug 04 2021 at 17:45):
Are there any recommended patterns for persisting a large concept map in a FHIR store if the size of the concept map exceeds the supported resource size? For example, ways to partition the concept map, etc.? One of our specific examples is mapping from local lab result codes to LOINC. Thank you.
Lloyd McKenzie (Aug 04 2021 at 21:50):
You could manipulate using PATCH, and could theoretically POST a small one and then PATCH to make it larger. However on a read or search, you'd still get the whole thing. You could possibly use an operation to retrieve subsets - where you'd generate a temporary concept map from the 'big' one in response to a set of parameters.
Lloyd McKenzie (Aug 04 2021 at 21:51):
No standard operation for that at the moment though.
Michael Lawley (Aug 04 2021 at 21:53):
Unmapped should work to partition the map?
Brian Wright (Aug 05 2021 at 13:58):
Thank you for the input. The main issue we are dealing with is the FHIR server has size limit on its storage which limits the size of the resources that can be persisted, so, I don't think that patching to a larger size would work. Not sure how the "unmapped" work work in this case. I think we will have to partition into subsets and work with those. Thanks again.
Michael Lawley (Aug 06 2021 at 02:28):
If you partition your map into multiple ConceptMaps, then unmapped with mode=other-map _should_ allow you to aggregate the partitions under a single umbrella ConceptMap
Last updated: Apr 12 2022 at 19:14 UTC
