andrey
(Andrey Ilatovskiy)
August 13, 2020, 5:15pm
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 (User Authentication ). 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: VSAC API Resources
FHIR® Terminology Service for VSAC Resources: https://cts.nlm.nih.gov/fhir/
RxNorm Proprietary Information API: RxNorm API - APIs
AccessGUDID SNOMED Device and Implantable List APIs: AccessGUDID - 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.
Thank you for pointing it. We got this email too.
There is ticket created in Athena repo to update cpt4 tool
opened 09:50AM - 14 Aug 20 UTC
closed 07:35AM - 01 Dec 20 UTC
Here are detailes from email
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
1 Like
andrey
(Andrey Ilatovskiy)
November 18, 2020, 5:24pm
3
@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.
1 Like
andrey
(Andrey Ilatovskiy)
November 18, 2020, 8:39pm
5
@Konstantin_Yaroshove Thank you for the info. This was exactly the reason I asked.