Compatibility with international versions of SNOMED

Hi BestenIT,
Didn't realize this. Is there a link to your code?
thanks,
-brady

Hi bradymiller,

I'm preparing a patch file with the differences compared to version 4.1.1 - patch 8, I'll upload soon as I have.

BestenIT (www.bestenit.com) is a Spanish company specialized in eHealth, we are a group of professionals with extensive experience in IT solutions for the world of health.

We have a special interest in working with the OpenEMR project, we plan to provide our services in Spanish and Latin American market offering a SAAS model to our end customers.

To do this, we would like to join the project and appear as professional support OpenEMR official website, initially for Spain.

This first contribution comes from the need to use the Spanish version of SNOMED in OpenEMR, but I think it would be valid for any translation.

Regards.

Patch file for compatibility with international versions of SNOMED

Hi bradymiller,

After reviewing the code only applies to the Spanish version of SNOMED, since the search is performed to concepts that contain "trastorno", Spanish translation of "disorder".

Can be improved by creating a global variable containing the translation into the local language “disorder” and then it would be for any language.

Regards.

Hi BestenIT,

Couple things here:
1. Feel free to list yourself on the Professional Support page:
(1st link is the page to request a wiki account, which I'll gladly)
(2nd link is the requirements to post on the Support page)
(3rd link is the Support page)
http://www.open-emr.org/wiki/index.php/Special:RequestAccount
http://www.open-emr.org/wiki/index.php/Talk:OpenEMR_Professional_Support#Instructions_for_placing_your_entry_on_this_page
http://www.open-emr.org/wiki/index.php/OpenEMR_Professional_Support

2. Note we also have a Certified Developer status, which I am guessing your company will be heading towards:
http://www.open-emr.org/wiki/index.php/Talk:OpenEMR_Professional_Support#Certified_OpenEMR_Contributors

2. For code contributions, best way to contribute is via git/github and there is a tutorial here(please always feel free to ask for help while learning git; we are happy to spend our time helping you learn this since it makes contributing/testing new code very easy):
http://www.open-emr.org/wiki/index.php/Git_for_dummies

3. It's generally best to develop code form the master branch (rather then current 4.1.1 branch) and then if needed we can modify it a bit to get it into the 4.1.1 branch (usually mods are never needed) patch.

4. Regarding the "disorder" issue. A robust way to go about this would be to grab this from the entry in the standardized_tables_track (the version column contains international:eng (as I recall) for the english version). So, can store which language is there and then use this to use the proper disorder label in the query. It actually would not take much to support importing of the Spanish snomed version in the Administration->Other->External Data Loads (ie. make it really easy to install other translations of snomed codes). For example, see how I recently added support for allowing importing of the US extension snomed package:
http://github.com/openemr/openemr/commit/a6023b1b8c05ec570f40248687e8bcc3aee41f8d
(ignore the smoking stuff, just look at the snomed importing stuff)

thanks,
-brady

Hi bradymiller.

We will follow your instructions.
Thanks.

Hi,
Just checking if you've done any work here. I was going to start playing arund with the switch over to the sct_descriptions table for another reason (if you haven't done this). I am not doing this explicitly for internationalization, but because it will likely provide an easy way to search for the 'disorder' keyword and remove it in the output (by searching via DescriptionType = 3, but then using it where DescriptionType=1).
-brady

Hi,
Currently have this working (I also added support for importing the Spanish snomed dataset) and am in process of testing it. Guessing it will get committed to the official codebase within the month.
-brady

This feature was committed to the official developer codebase on sourceforge. It will be part of the future 4.1.2 release.