This September 2016 US Edition of SNOMED CT marks the last RF1 release. Going forward the International Health Terminology Standards Development Organisation (IHTSDO) and NLM will only produce the RF2 release files for SNOMED CT. This includes the International and US Editions of SNOMED CT. At this time our External Database Import Utility does not support Snomed RF2.
The solution to this issue is to add a new functionality that will implement the database load processing of Snomed_RF2 files into OpenEmr
I’ll be working in this endeavor, If someone wish to get involved or provide input is very welcome.
I will begin with SnomedCT_RF2_INT new install
Sounds like a good plan.
The SnomedCT_RF2 has the data files in two locations : Full/Terminology and Snapshot/Terminology. Which location should be load in to openemr ?
Note the Full includes all revisions of codes, while the Snapshot contains only the current revision of codes.
I'd go with the Full for now.
my External Database Import Utility created and loaded tables: sct2_concept, sct2_description, sct2_identifier, sct2_relationship, sct2_statedrelationship, sct2_textdefinition. the tables are BIG, sct2_relationship has 2455945 rows.
I'm not sure if the Notice about the checksum below needs to be fix ?
Release Date: 2015-01-31
Notice: Undefined index: checksum in /var/www/html/openemrRF2/interface/code_systems/list_staged.php on line 333
The installed version and the staged files are the same.
Follow these instructions for installing or upgrading the following database: SNOMED?
Wouldn't worry about how much space it takes up at this point; once it's all up and running well, can then minimize it and clean things up, if needed (note rf1 produces sct_relationship with about 1.4 millions rows, so not too big of a difference). Regarding php Notice, ensure you have your php errors logged to file instead of screen, then they won't bother you :)
Does OpenEMR will continue giving support to RF1?
If this is true I will add SNOMEDRF2, SNOMEDRF2-CT and SNOMEDRF2-PR to tb code_types
I wouldn't add new code_types. But will need to add new options for the selector at far right column when look at Administration->Lists->Code Types (I think it is External Tables or something like that). This is what is used to identify the external tables used, and the new options can be added here:
(will basically add 3 more entries add the end with RF2 in them rather than RF1)(and then the 10,11,12 are used to create the connectors to the new RF2 tables)
Here's how the connectors are done for RF1:
(will keep this code and then add additional code to support 10,11,12 for RF2)
This will then allow the user to use either RF1 or RF2 by selecting it on the far right column in the Code Type list.
This is a working RF2 prototype
Hi @robertogagliotta ,
Looks like you are beginning to crack the "define_external_table" code :)
Is your code posted on github?