OHDSI Home | Forums | Wiki | Github

UMLS deprecated password authentication


(Andrey Ilatovskiy) #1

I got the following email from UMLS. I wonder if this affects the CPT4 utility to resolve the concept names.

@Dymshyts @maria.pozhidaeva @Yaroslav @Alexdavv

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.

(Konstantin Yaroshovets) #2

Thank you for pointing it. We got this email too.

There is ticket created in Athena repo to update cpt4 tool

(Andrey Ilatovskiy) #3

@Dymshyts @Konstantin_Yaroshove @acumarav

Any updates on the cpt4 tool?

(Konstantin Yaroshovets) #4

@andrey We plan to release cpt4 tool with API KEY support by beginning of December. That’s why my recommendation will be not to migrate UMLS account till that time.

(Andrey Ilatovskiy) #5

@Konstantin_Yaroshove Thank you for the info. This was exactly the reason I asked.

How to run cpt4.jar on Athena download: using new UMLS login