OHDSI Home | Forums | Wiki | Github

Usagi Not Being Developed Anymore?


The last release was in May 2019 and that is just a pre-release.

It is supposed to help with the memory use which is very important when building the index. Also questions on the issues GitHub page have no answers for past 3 months.


Anybody? We need to start mapping with the new vocabularies soon so it would be very helpful if there is a full release of the memory fixes for Usagi.

(Maxim Moinat) #3

Hi @OHDSI_User, I just made the pre-release an official release.

Usagi is indeed currently not actively developed. This will change in the future. Please keep reporting any bugs or enhancements.


Thanks very much for your help. We are wondering that it is possible to have two extra functions in Usagi

  1. Search concept information by concept_code. The reason we want to have the function, because there is some source medical code in our existing database, but there is no description of the code. We hope that the tool can search by those medical codes, and provide the description of those codes if they are in the concept table

  2. To map lab results with LOINC codes, we have to match the source of samples and units of tests. Is it possible to provide LOINC codes sample source and unit information when the tool matches the record with LOINC code?


(Maxim Moinat) #5

A quick response to your questions. Let us know if these solutions would work for you.

  1. Searching for matching source codes can also be done with a simple sql query outside of Usagi. This, which will be faster in the end. Something in the lines of:
    SELECT * FROM concept JOIN source_concept ON concept.concept_code = source_concept.code
  2. With View->Concept Information (or alt-c), Usagi will show a pop-up with the relationships of this selected concept. Would that give you the required information? If not, could you give an example of what information you are looking for?

And have you tried adding additional LOINC information when building the index? I have to admit that I cannot find documentation on this feature. @schuemie would you know if and where the usage of this is explained?