UMLS data generator utility #1214
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ |
|
Kudos, SonarCloud Quality Gate passed!
|
|
Related to #992 |
reshmakh
added
fhir-datastore
reshmakh
approved these changes
Dec 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checkpoint for a utility that generates bite sized files out of the 30 GB UMLS data set.
There is separate future work to ingest these files by the server. The terminologies are too big to be stored in the naive default "JSON string in a TEXT column" method.
Options for consideration:
"concept"properties - more semantically correct, allows for end users to submit their own large terminologiesReference: HAPI FHIR docs on importing terminologies: https://hapifhir.io/hapi-fhir/docs/tools/hapi_fhir_cli.html#upload-terminology