In a way is kind of our own Athena, for these vocabularies that are only used in Finland.
I would like to add to this table some more columns with the standard code each of our local codes maps, including the standard code_name, and make it public.
However, I’m afraid that I may be breaking some licenses ??
Is it possible to do like in Athena or the public Atlas, where a banner appears, making the user to accept some license before this info is shown ?
Is it possible to do like in Athena or the public Atlas, where a banner appears, making the user to accept some license before this info is shown ?
In technical sense, that is completely dependent on your implementation. Most frontend frameworks should contain at least one method of displaying a blocking overlay; or better yet, backend should use dynamic routing to direct user to a different page where they can accept the license and get a cookie that would prevent such a redirect next time.
However, I’m afraid that I may be breaking some licenses ??
On high level, probably no, since Finland is a SNOMED CT member country. Conceptually it should mean that access to its content is expected to be free inside Finland.
That being said: according to this page, the organization licensing SNOMED use within Finland is “National Institute for Health and Welfare”, and nobody else can answer this side of your question with any certainty. The page I linked also contains names of persons responsible and contact information.
Showing a page with a couple concepts is no problem, period. The anxieties, and the need for compliance with licenses, comes in when we distribute them in bulk.
In case of SNOMED you are ok doing that if the purpose is OHDSI research using standardized tools. And, as @Eduard_Korchmar pointed out, if you are in a member country, which is pretty much every developed country.
(also thanks @Eduard_Korchmar for your presentation on Bouzyges yesterday on the AI WG group, I watch it off line. We were thinking to try something on these lines, and your presentation had such a good bases)
Pleased to hear this! I would gladly contribute if you want to build a practical use-case using Bouzyges. Please keep me updated through korchmar@ohdsi.org
