Snowstorm

Join In

Please join in the discussions and feel free to suggest any specific categories that you would like added to this forum. You will need a SNOMED International Confluence Account and if you do not already have one, please apply for a user account if you would like to take part in these discussions.

Add discussion

Status: All

New
In discussion
Resolved
No corresponding status

Creators: All

Current user

No specific user

Creation period

Choose creation period

ideation.btn.close

Today Last week Last month Reset

Categories: All

Snowstorm
General development
Netherlands
No corresponding category

Restarting / refreshing a snowstorm installation

Added by Anibal Jodorcovsky on Nov 26, 2021

I'd like to refresh / start a new with my snowstorm installation. How do I do that?

Status: In discussion 1339 View 1 Comment Comments enabled In the category: Snowstorm

Comment Last contribution, Nov 30, 2021. All contributions

Kai Kewley

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!

Best practices for Snowstorm and branches

Added by Rory Davidson on Nov 3, 2019

(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

Status: In discussion 3218 View 3 Comment Comments enabled In the category: Snowstorm

Comment Last contribution, Nov 6, 2019. All contributions

Kai Kewley

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

Welcome to the Snowstorm discussion category

Added by Rory Davidson on Aug 19, 2019

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

Status: New 1404 View 0 Comment Comments disabled In the category: Snowstorm

	Topic	Status	Author	Like	View	Replies	Creation date	Last Reply	Contributors	Category
Question	Restarting / refreshing a snowstorm installation	In discussion	Anibal Jodorcovsky	0	View 1339	Comment 1	$discPage.getCreationDate().getTime() Nov 26, 2021 04:11	Nov 30, 2021 16:47	1	Snowstorm
Question	Best practices for Snowstorm and branches	In discussion	Rory Davidson	1	View 3218	Comment 3	$discPage.getCreationDate().getTime() Nov 3, 2019 22:58	Nov 6, 2019 13:48	3	Snowstorm
Discussion	Welcome to the Snowstorm discussion category	New	Rory Davidson	3	View 1404	Comment 0	$discPage.getCreationDate().getTime() Aug 19, 2019 08:25	0 -	0 -	Snowstorm

Page tree

Snowstorm

Kai Kewley

Kai Kewley