• Home
  • About Us
  • Contact Us
  • Privacy Policy
  • Special Offers
Business Intelligence Info
  • Business Intelligence
    • BI News and Info
    • Big Data
    • Mobile and Cloud
    • Self-Service BI
  • CRM
    • CRM News and Info
    • InfusionSoft
    • Microsoft Dynamics CRM
    • NetSuite
    • OnContact
    • Salesforce
    • Workbooks
  • Data Mining
    • Pentaho
    • Sisense
    • Tableau
    • TIBCO Spotfire
  • Data Warehousing
    • DWH News and Info
    • IBM DB2
    • Microsoft SQL Server
    • Oracle
    • Teradata
  • Predictive Analytics
    • FICO
    • KNIME
    • Mathematica
    • Matlab
    • Minitab
    • RapidMiner
    • Revolution
    • SAP
    • SAS/SPSS
  • Humor

AI Weekly: Coronavirus chatbots use inconsistent data sources and privacy practices

April 4, 2020   Big Data

It’s been widely reported that U.S. hospital systems — particularly in hotspots like New York City, Detroit, Chicago, and New Orleans — are overwhelmed by the influx of patients affected by COVID-19. There’s a nationwide ventilator shortage. Convention centers and public parks have been repurposed as ward overflows. And waiting times at some call and testing centers are averaging multiple hours.

Clearly, there’s a real and present need for triaging solutions that ensure people at risk receive treatment expeditiously. Chatbots have been offered as a solution — tech giants including IBM, Facebook, and Microsoft have championed them as effective informational tools. But problematically, there are disparities in the way these chatbots source and handle data, which could in the worst case lead to inconsistent health outcomes.

We asked six companies that provide COVID-19 chatbot solutions to governments, nonprofits, and health systems — Clearstep, IPsoft, Quiq, Drift, LifeLink, and Orbita — to reveal the sources of their chatbots’ COVID-19 information and their vetting processes, as well as whether they collect and how they handle personally identifiable information (PII).

Quality and sources of information

Unsurprisingly, but nonetheless concerningly, sourcing and vetting processes vary widely among chatbot providers. While some claimed to review data before serving it to their users, others demurred on the question, instead insisting that their chatbots are intended to be used for educational — not diagnostic — purposes.

Clearstep, Orbita, and LifeLink told VentureBeat that they run all of their chatbots’ information by medical professionals.

 AI Weekly: Coronavirus chatbots use inconsistent data sources and privacy practices

Clearstep says that it uses data from the Centers for Disease Control and Prevention (CDC) and protocols “trusted by over 90% of the nurse call centers across the country.” The company recruits chief medical and chief medical informatics officers from its customer institutions, as well as internal medicine and emergency medicine physicians in the field, to review content with their clinical review teams and provide actionable feedback.

Orbita also draws on CDC guidelines, and it has agreements in place to provide access to content from trusted partners such as the Mayo Clinic. Its in-house clinical team prioritizes the use of that content, which it claims is vetted by “leading institutions.”

LifeLink, too, aligns its questions, risk algorithms, and care recommendations with those of the CDC, supplemented with an optional question-and-answer module. But it also makes clear that it retains hospital clinical teams to sign off on all of its chatbots’ data.

By contrast, IPsoft says that while its chatbot sources from the CDC in addition to the World Health Organization (WHO), its content isn’t further reviewed by internal or external teams. (To be clear, IPsoft notes the chatbot isn’t intended to offer medical advice or diagnosis but rather to “help users evaluate their own situations using verifiable information from authorized sources.”)

Quiq similarly says that its bot “passively” gives out unvetted information, using undisclosed approved sources for COVID-19 and local health authority, CDC, and White House materials.

Drift’s chatbot uses CDC guidelines as a template, and it’s customizable based on organizations’ response plans, but it also carries a disclaimer that it isn’t to be used as a substitute for medical advice, diagnoses, or treatment.

Data privacy

The COVID-19 chatbots reviewed are as inconsistent about data handling and collection as they are with sources of information, we found. That said, none appear to be in violation of HIPAA, the U.S. law that establishes standards to protect individual medical records and other personal health information.

Clearstep says that its chatbot doesn’t collect information that would allow it to identify a particular person. Furthermore, all data the chatbot collects is anonymized, and health information is encrypted in transit and at rest and stored in the HIPAA-compliant app hosting platform Healthcare Blocks.

For LifeLink’s part, it says that all of its chatbot conversations occur in a HIPAA-compliant browser session. No PII is collected during screening; the only data retained is symptoms and travel/contact/special population risk. Moderate- and high-risk patients move into clinical intakes for appointments, during which the chatbot collects health information submitted directly to the hospital system via integration with their scheduling systems in preparation for the visit.

IPsoft is a bit vaguer about its data collection and storage practices, but it says that its chatbot doesn’t collect private health information or record conversations or data. Quiq also says that it doesn’t collect personal information or health data. And Drift says that it requires users to opt-in to a self-assessment and agree to clinical terms and conditions.

As for Orbita, it says that its premium chatbot platform — which is HIPAA-complaint — collects personal health information, but that its free chatbot does not.

Challenges ahead

The differences in the various COVID-19 chatbot products deployed publicly are problematic, to say the least. While we examined only a small sampling, our review revealed that few use the same sources of information, vetting processes, or data collection and storage policies. For the average user, who isn’t likely to read the fine print of every chatbot they use, this could result in confusion. A test Stat conducted of eight COVID-19 chatbots found that diagnoses of a common set of symptoms ranged from “low risk” to “start home isolation.”

While companies are normally loath to disclose their internal development processes for competitive reasons, greater transparency around COVID-19 chatbots’ development might help to achieve consistency in the bots’ responses. A collaborative approach, in tandem with disclaimers about the chatbots’ capabilities and limitations, seems the responsible way forward as tens of millions of people seek answers to critical health questions.

For AI coverage, send news tips to Khari Johnson and Kyle Wiggers and AI editor Seth Colaner — and be sure to subscribe to the AI Weekly newsletter and bookmark our AI Channel.

Thanks for reading,

Kyle Wiggers

AI Staff Writer

Let’s block ads! (Why?)

Big Data – VentureBeat

chatbot’s, coronavirus, data, Inconsistent, Practices, privacy, sources, Weekly
  • Recent Posts

    • C’mon hooman
    • Build and Release Pipelines for Azure Resources (Logic Apps and Azure Functions)
    • Database version control: Getting started with Flyway
    • Support CRM with New Dynamics 365 Field Service Mobile App
    • 6 Strategies for Achieving Your Business Goals in the New Year
  • Categories

  • Archives

    • January 2021
    • December 2020
    • November 2020
    • October 2020
    • September 2020
    • August 2020
    • July 2020
    • June 2020
    • May 2020
    • April 2020
    • March 2020
    • February 2020
    • January 2020
    • December 2019
    • November 2019
    • October 2019
    • September 2019
    • August 2019
    • July 2019
    • June 2019
    • May 2019
    • April 2019
    • March 2019
    • February 2019
    • January 2019
    • December 2018
    • November 2018
    • October 2018
    • September 2018
    • August 2018
    • July 2018
    • June 2018
    • May 2018
    • April 2018
    • March 2018
    • February 2018
    • January 2018
    • December 2017
    • November 2017
    • October 2017
    • September 2017
    • August 2017
    • July 2017
    • June 2017
    • May 2017
    • April 2017
    • March 2017
    • February 2017
    • January 2017
    • December 2016
    • November 2016
    • October 2016
    • September 2016
    • August 2016
    • July 2016
    • June 2016
    • May 2016
    • April 2016
    • March 2016
    • February 2016
    • January 2016
    • December 2015
    • November 2015
    • October 2015
    • September 2015
    • August 2015
    • July 2015
    • June 2015
    • May 2015
    • April 2015
    • March 2015
    • February 2015
    • January 2015
    • December 2014
    • November 2014
© 2021 Business Intelligence Info
Power BI Training | G Com Solutions Limited