- Home
- Member Resources
- Clinical Informatics Resources
- Clinical Informatics Case-Based Education
The Informatics Committee developed these cases with the goal to help pathologists learn about important informatics topics within the context of realistic scenarios that reflect situations they can encounter in their day-to-day practice.
About the Cases
- Each case may take between 15 to 30 minutes to complete.
- The cases are presented in parts and include questions to support your learning in between each part of the scenario. We also provide a case summary, key points, multiple choice questions with answers, and a list of references.
- The cases are free and do not offer CME credit.
Summary of Each Case
Case #1: The Simple Definitions, Dos, and Don’ts of Installing Middleware
There are simple definitions, dos, and don’ts that all laboratory directors should know (some may surprise you!). For example, what is middleware? How can middleware help my laboratory? How do we avoid pitfalls to installing and maintaining middleware? These and other questions will be answered in a case-based format derived from real clinical laboratory situations.
Case #2: Don’t Forget Your Rules When Harmonizing Laboratory Testing Across Multiple Sites
Many healthcare systems are seeking to harmonize laboratory testing across multiple sites, improving patient care and reducing cost. How can I ensure patient samples are treated uniformly across locations while reducing unnecessary or inappropriate testing? How can LIS/middleware rules help to streamline testing? Review this case and get the answers to these plus other important questions.
Case #3: How to Validate AI Algorithms in Anatomic Pathology
Your laboratory has decided to implement an artificial intelligence / machine learning algorithm to assist with the diagnosis of cervical cytology specimens. You are asked to take the lead on this project and assure that it is implemented appropriately and in accordance with any pertinent regulatory guidelines. This case helps you through that process.