UK +44 (0)1865 849841
Malaysia +603 2731 9335

Tag: pathology

Presentation slides from the 5th Digital Pathology & AI Congress: USA

Following the 5th Digital Pathology & AI Congress: USA, we have made the following presentation slides available from Iman Hajirasouliha, Kim Solez and Mrinal Mandal.

Read More

PathLAKE: Benefitting Pathologists with exemplary projects

David Snead is Consultant Histopathologist and Clinical lead for Coventry and Warwickshire Pathology Services (CWPS), a network of labs hosted by University Hospitals of Coventry and Warwickshire NHS Trust. As head of the UHCW Digital Pathology Centre of Excellence, he is now heavily involved in the Pathology image data Lake for Analytics, Knowledge, and Education (PathLAKE).

Read More

How Can we Develop Collaborative Standards for AI in Digital Pathology?

As laboratories transform their workflows into the digital environment, a tremendous opportunity presents itself: to transition the field of pathology from a qualitative to quantitative discipline. Quantitation brings measures of accuracy, reproducibility, and statistical stringency that allow computational algorithms (including AI) to perform complex tasks and measure their success. The evolution of Pathology will not be dictated by any single organization but rather will take an entire community of experts.

Read More

Developing a pathology LIS for the digital age

For over a decade, Memorial Sloan Kettering has implemented digital pathology enterprise system for clinical scanning. Over the years that has evolved significantly. Currently, a lot of our efforts are spent on archive scanning to be available for prospective clinical cases.

Efforts to enable pathologists the ability for primary diagnosis are being explored, and we’re currently validating available systems. There’s always a certain flux in terms of vendor communication and networking, meaning that we’re validating systems for our internal use whether that’s for clinical, education, or research.

Read More

What does the future hold for AI in Digital Pathology?

This is the second of a two-part blog post. In his first post, Liron wrote on embedding AI in Digital Pathology workflows.

Digital Pathology AI apps are certainly feasible, but exactly when they will be ready for clinical use is less clear.

There are potentially hundreds or thousands of algorithms that will need to be developed. Currently, there are only a handful of algorithms that are approved by regulatory bodies for clinical practice, so we’ve got a long way to go.

Read More

How do we embed AI into Digital Pathology workflows?

This is an exciting time in pathology: now that digital pathology is mature, we have noticed an uptake in a lot of AI start-up companies. Most of the algorithms have been developed on a research basis or in a test environment, and only recently applied. What follows is a summary of the work we are doing at the University of Pittsburgh Medical Center testing these AI apps, and some of the questions arising therefrom.

Read More

AI in digital pathology; increasing workflow efficiency and patient safety

In the fifth of this six-part series, the experts considered the potential cross-border solutions and challenges for Digital Pathology, as well as the evidence for improved efficiency. In this final installment, they discuss the impact of AI on industry and medical practice.

If you weren’t able to make the panel discussion, you can watch the recording here.

Read More

The benefits and challenges of offsite working in Digital Pathology

In the fourth of this six-part series, the experts discussed the biggest drivers in the transition to going 100% digital. Here, the panel contemplated the potential cross-border solutions and challenges to the field, as well as the evidence for improved efficiency in digital pathology.

If you weren’t able to make the panel discussion, you can watch the recording here.

Read More

Subscribe to Our Newsletter

Get free reports and resources from our world class speakers.
  • This field is for validation purposes and should be left unchanged.

Archive