The simplest way to delete all the data in your installation is to start Snowstorm using this command line flag "--delete-indices".
For example:
java -Xms2g -Xmx4g -jar snowstorm.jar --delete-indices
From there you can load the SNOMED CT RF2 data again.
Don't forget to remove this flag when you restart next time!
(originally posted by eroenjum - copied from 96808101 )
We recently implemented a Proof of Concept for patient information as open data in Norway - with SNOMED CT as the metadata core. In this work we did an installation of Snowstorm, and used this as API against the front end GUI. The project was very successful.
We will now reset Snowstorm and build the terminology server in a more sustainable way. But we have not found good documentation on best practices on how to install different
Hi eroenjum, if you have extensions which are dependant on each other you can import them in a branch tree structure.
For example if you have a local extension SNOMEDCT-NO-NORD which depends on the Norway extension this could live at MAIN/SNOMEDCT-NO/SNOMEDCT-NO-NORD.
This way running a query on the Nord extension branch also queries the Norway extension. We have used the same technique to host the Argentinian extension in the public browser using branch MAIN/SNOMEDCT-ES/SNOMEDCT-AR.
The ICPC-2 content is not so straight forward.. if this content is common to all Norway content it could be loaded into the SNOMEDCT-NO code system along with the Norway extension? The downside to this would be that the ICPC-2 content could not be versioned independently of the Norway extension within Snowstorm but this may be an acceptable inconvenience.
Let us know if you try any of these ideas and how you get on.
Kind regards, Kai
This discussion category is to ask questions about using, deploying and developing with SNOMED International Snowstorm terminology server that are more general. Any bugs or issues should be posted on the GitHub repo issue page https://github.com/IHTSDO/snowstorm/issues
Kai Kewley