Here is another similar, but different version of the letter: On Fri, Sep 18, 2020 at 12:34 PM Peter Abramowitsch <pabramowit...@gmail.com> wrote:
> Ok. Here you go. > It seems only for users that are also registered content providers, so > perhaps that's why some (all?) of you may not have received it. > > > ------------------------------------------------------------------------------------------------------------------------------ > > Patrick McLaughlin > > Head, Terminology QA & User Services > > National Library of Medicine > > 8600 Rockville Pike, MSC 3831, Bethesda, MD 20894 > > patrick.mclaugh...@nih.gov > > > > *From:* McLaughlin, Patrick (NIH/NLM) [E] <patrick.mclaugh...@nih.gov> > *Sent:* Tuesday, August 11, 2020 2:23 PM > *To:* > *Subject:* Changes to UTS Authentication for Authorized Content > Distributors > > > > Dear UMLS Licensee, > > > > I’m contacting you from the U.S. National Library of Medicine because you > are an Authorized Content Distributor of UMLS Terminology Services (UTS) > content (https://uts.nlm.nih.gov/help/license/validateumlsuserhelp.html > < > https://urldefense.proofpoint.com/v2/url?u=https-3A__uts.nlm.nih.gov_help_license_validateumlsuserhelp.html&d=DwMFAg&c=iORugZls2LlYyCAZRB3XLg&r=h6N9s_G3H8x-GI2njqb2gWIIswfJoO1u2HuLnROxE5w&m=E1w0zYv65lQLcrqZbvvOJ3pqqiFoyZdSWLEKe3pnwFc&s=dq3l2rGNrzzcVbYe4rFdUCwyVxe3jY_M39tSNltNJoc&e= > >). > We are contacting you because we are making changes to the way in which UTS > users authenticate starting this November. > > > > *What is changing?* > > > > UTS users will no longer authenticate using a username and password. > Instead, users will sign in using external authentication services like > Login.gov, Google, Facebook, Microsoft, or one of several research > organizations. We anticipate that users will begin migrating to external > authentication services on November 9, 2020. Users who migrate to these > services will no longer authenticate with a username and password. We also > anticipate that passwords will be removed from UTS accounts on January 1, > 2021. After that point, it will no longer be possible for Authorized > Content Distributors to authenticate users with a username and password via > https://uts.nlm.nih.gov/help/license/validateumlsuserhelp.html > < > https://urldefense.proofpoint.com/v2/url?u=https-3A__uts.nlm.nih.gov_help_license_validateumlsuserhelp.html&d=DwMFAg&c=iORugZls2LlYyCAZRB3XLg&r=h6N9s_G3H8x-GI2njqb2gWIIswfJoO1u2HuLnROxE5w&m=E1w0zYv65lQLcrqZbvvOJ3pqqiFoyZdSWLEKe3pnwFc&s=dq3l2rGNrzzcVbYe4rFdUCwyVxe3jY_M39tSNltNJoc&e= > >. > > > > > *What does this mean for Authorized Content Distributors?* > > > > If you wish to continue to authenticate UTS users, *you will need to > implement a web-based authentication service*. To do this, you will need to > provide your users with a web interface that links to our authentication > service. The user will navigate to your web interface using their web > browser and click a link to our authentication service. Our service will > then authenticate the user via an external authentication service (for > example, Google or Facebook) and redirect the user back to your web > interface. We will return true / false to you to let you know whether the > user has an active UTS account. We are working on a test environment for > you to test your implementation, and we anticipate that will be ready on > August 15, 2020. This will allow you to test your implementation ahead of > our November 9 release date. > > > > *We need some information from you.* > > > > In order for you to test your implementation, we need two things: > > > > 1. A domain name from which you will link your users to our > authentication service - We will need to whitelist your domain name for > use > in our test system. Example: www.yourwebsite.org > < > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.yourwebsite.org&d=DwMFAg&c=iORugZls2LlYyCAZRB3XLg&r=h6N9s_G3H8x-GI2njqb2gWIIswfJoO1u2HuLnROxE5w&m=E1w0zYv65lQLcrqZbvvOJ3pqqiFoyZdSWLEKe3pnwFc&s=BysYBsS0Lt-dnrlhQ2wiL_vATaL54f-2dFOOAQkWGvg&e= > >. > > 2. An email address - We will need to configure a test account for you > so that you can test user authentication. > > > > If you have questions or concerns, please respond to this email. We > appreciate your patience as we make improvements to UTS. > > > > Regards, > > Patrick McLaughlin > > Head, Terminology QA & User Services > > National Library of Medicine > > 8600 Rockville Pike, MSC 3831, Bethesda, MD 20894 > > Phone: 301-827-5063 > > patrick.mclaugh...@nih.gov > > On Fri, Sep 18, 2020 at 10:52 AM Savova, Guergana < > guergana.sav...@childrens.harvard.edu> wrote: > > > I have not received that email either. Could you share it with us? > > --Guergana > > > > Guergana Savova, PhD, FACMI > > Associate Professor > > PI Natural Language Processing Lab > > Computational Health Informatics Program (CHIP) > > Boston Children's Hospital and Harvard Medical School > > 401 Park, 5th floor East, 5523.3 > > Boston, MA 02215 > > > > > > -----Original Message----- > > From: Greg Silverman [mailto:g...@umn.edu.INVALID] > > Sent: Friday, September 18, 2020 1:46 PM > > To: dev@ctakes.apache.org > > Subject: Re: Current thinking on new UMLS authentication [EXTERNAL] > > > > * External Email - Caution * > > > > > > I never received the email you mentioned. > > > > I assume this will affect the API call to NLM for UMLS validation? If it > > does, why not take the NLM's model for UMLS and only require UMLS > > credentials at the time of download? > > > > Greg-- > > > > > > > > On Fri, Sep 18, 2020 at 12:33 PM Peter Abramowitsch < > > pabramowit...@gmail.com> > > wrote: > > > > > Hi All > > > > > > Probably all of you have received an email from Patrick McLaughlin at > > > the NLM regarding upcoming changes to the UMLS authentication they are > > going to > > > support and to retire. This will have implications for all cTakes > users > > > in different ways depending on how cTakes is implemented in your > > > community. To me, there were some ambiguities in his email regarding > > > usage situations as a registered content provider that needed to be > > > spelled out. > > > > > > I was wondering if any of you have had further conversations with him > > > which might clarify whether, for instance, users within a registered > > > content provider installation would still need to be individually > > authenticated. > > > Or on any other authentication scenario. > > > > > > I'm trying to contact him or his team at the moment to ask about our > > > particular architecture. > > > > > > Regards, Peter > > > > > > > > > -- > > Greg M. Silverman > > Senior Systems Developer > > NLP/IE < > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__healthinformatics.umn.edu_research_nlpie-2Dgroup&d=DwIBaQ&c=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU&r=SeLHlpmrGNnJ9mI2WCgf_wwQk9zL4aIrVmfBoSi-j0kfEcrO4yRGmRCJNAr-rCmP&m=OoVx9YhA_zrGwya4OQ29snp1lWjOvt3EuMAspsP5CbA&s=4lOuRwaYmEQD_5BlWeR8Q2qXY9olJvV1k3W2LLnVwvo&e= > > > Department of Surgery University of Minnesota g...@umn.edu > > >
