AI and health | Just be patient

Next week, I will be attending a seminar entitled “AI and Health | Just be Patient”, looking at a number of challenges associated with applying artificial intelligence to healthcare.

One of the sessions that caught my eye is called “Give an AI some data and you feed it for a day; teach the AI to get its own data and you feed it for a lifetime”. The session will look at regulating the medical device internet of things (MDIoT) that feed the AI. Other panels will look at the promise of epidemiological research made possible through AI.

The internet of things is connecting billions of objects, enabling real time monitoring with the potential of driving massive improvements in efficiencies in virtually every aspect of our lives. From temperature controls in restaurants, to security systems, to traffic flows, inventory tracking and health care, the opportunities are limitless.

What kind of changes will this require from our communications networks? How do we build the systems to acknowledge and respect privacy rights? As technology companies come under increased scrutiny, are citizens able to trust them with the flood of data from the generic internet of things, let alone the personal medical data from an MDIoT?

When we teach artificial intelligence engines to get data, what ethical principles need to be established to guide the systems development?

The 2019 Canadian Telecom Summit (June 3-5 | Toronto) will explore these issues with panels on:

  • Artificial Intelligence: debating human autonomy vs. human innovation
  • Cyber Security: Protection, Pre-emption & Privacy in the Age of Bad Actors
  • Network Innovation: Transforming networks for nextgen services – SDN, Network Virtualization and more

Early bird savings are available for registrations through February 28. Have you registered yet?

1 thought on “AI and health | Just be patient”

  1. I watch this with interest and trepidation. AI and iOT offer so much promise, but the old school engineer in me is still very skeptical and leery. What happens if…. ? I think, especially from a disaster recovery perspective or when something goes wrong. I was reminded of the days back in the early ’90s when I was a young SE at Bell… only two companies got their phone services over T1 ; Nortel and BMO. As an SE I helped roll out the next 20 customers, including to some downtown hospitals. We always had to ensure that there remained multiple phone sets still attached to copper pairs throughout the hospital, just in case of major power outages etc What are the unknown unknowns in some of the use cases being contemplated ?

Comments are closed.

Scroll to Top