Storing Large, Queryable Lookups
# support
m
Hello, Medplum Team! We are trying to model Lookup data in Medplum (e.g. ICD Codes, Drop-down list options). We've run into a few limitations that presenting some unforseen challenges: 1. Medplum Resources have a size limitation that seems to prohibit us from storing large tables in a single resource (like CodeSystem or Binary Bundles) 2. FHIR Search Parameters do not allow search on
CodeSystem.concept
items except for the Code value itself, and we often need to query off of other fields like names, ids, descriptions, and others. - Perhaps we can use
_filter
to work around this but I'm not sure how this works with heavily nested concepts like this one. 3. Many fields do not allow for substring search which limits the number of properties into which I can map queryable values like descriptions, names, ids - Particularly
identifier
doesn't seem to support substring search. 4. Some lookups are sufficiently large so we do not want to 100K+ items to the FrontEnd to parse through the options. Can you confirm if the above understanding of the limitations is correct? If so, do you have any recommended solutions for these problems? Please let me know if I can provide any additional context to help in answering these questions!
I did answer #3 with the docs that Medplum allows for
_filter
based on the Identifier value as below:
_filter: 'identifier co "abd"'
. Played around with the syntax and found that it also allows for the filtering to work on System as well:
_filter: 'identifier co "https://example.com|abd"'
. https://www.medplum.com/docs/search/filter-search-parameter#logical-expressions
183 Views