2020-08-12 Meeting notes

• Branch resolution can only be sped up so much
• Looking forward to users taking it for "long drive"
• Talked to Brian about all-in-one resolution but he thinks it will be too slow
• Almost all searching is going through ElasticSearch

• Looking at scope to finalize first release
• Waiting on time from Brian

Dear UMLS Licensee,

You are receiving this email from the U.S. National Library of Medicine because you have used a username and password to authenticate with an API that relies on UMLS Terminology Services (UTS) authentication (https://documentation.uts.nlm.nih.gov/rest/authentication.html). We are contacting you because effective immediately, we are deprecating username and password authentication for all APIs that rely on UTS authentication. Instead, we will require you to authenticate using an API key. APIs that rely on UTS authentication include:

• UMLS API: https://documentation.uts.nlm.nih.gov/
• VSAC SVS API: https://www.nlm.nih.gov/vsac/support/usingvsac/vsacsvsapiv2.html
• FHIR® Terminology Service for VSAC Resources: https://cts.nlm.nih.gov/fhir/
• RxNorm Proprietary Information API: https://rxnav.nlm.nih.gov/RxNormAPIs.html#uLink=RxNorm_REST_getProprietaryInformation
• AccessGUDID SNOMED Device and Implantable List APIs: https://accessgudid.nlm.nih.gov/resources/developers/generating_umls_tickets

We recommend that you switch to using an API key as soon as possible. We anticipate that these APIs will no longer accept username and password starting January 1, 2021.

You can find your API key by going to https://uts.nlm.nih.gov/, signing in to your UTS account, and clicking “My Profile.” If you do not already have an API key, you can generate one by clicking “Edit Profile” then checking the box that says “Generate new API Key” then clicking “Save Profile.”

Documentation for implementing API key authentication is available here: https://documentation.uts.nlm.nih.gov/rest/authentication.html

If you have questions or concerns, please direct them to UMLS Customer Service at: https://support.nlm.nih.gov/support/create-case/

Regards,

U.S. National Library of Medicine, NIH, HHS

Had meeting this morning with Doug Forbeck.  Systems is concerned with security of anonymous FTP. They want to look at options if security team shuts it down.  

Architecture:

• Upload server ncicbftp2
• Download server caftp1
• AWS image evs.nci.nih.gov/ftp1

Disjoint corrected NCIt loaded onto Dev without issue

New Meta received last week.  Will load once monthlies go to Stage (today?)

DataQA MySQL password expired - keep an eye out for this happening on other tiers

Working on build process to get EVS Exporter to work on Tomcat.

Would currently be manual install - copying of the file to tomcat instance.

Set up of instance in Kathy's court. Discussions whether it is part of AWS EVS project or should be under a new header.