Partner integration for digital image generation and processing

Abstract

A data manager is directly communicatively connected to multiple components of a digital image generation system for medical samples. The data manager provides a single integration point for a platform provider that provides a viewer for the user to visualize the digital image data. The data manager provides communications between the platform provider and local components that can generate and / or store sensitive health information, such as the digital image data.

Description

[0001] PARTNER INTEGRATION FOR DIGITAL IMAGE GENERATION AND PROCESSING CROSS-REFERENCE TO RELATED APPLICATION(S) This application claims the benefit of U.S. Provisional Application No.

[0002] 63 / 711,346 filed October 24, 2024 and entitled “PARTNER INTEGRATION FOR DIGITAL IMAGE GENERATION AND PROCESSING,” the disclosure of which is hereby incorporated by reference in its entirety.

[0003] BACKGROUND

[0004] This disclosure relates generally to medical image processing. More specifically, this disclosure relates to integration of partners for computational pathology.

[0005] Medical scanners generate data regarding medical samples. The scanners generate image data that is analyzed by a medical professional (e.g., pathologist) to make a diagnosis regarding the specimen, such as whether or not cancer is present. Artificial intelligence algorithms can be utilized to provide supplemental information regarding the medical sample, such as by highlighting areas of interest, providing written reports, annotating images, etc.

[0006] SUMMARY

[0007] According to an aspect of the disclosure, a system for generating and processing digital images regarding medical samples includes a scanner system configured to generate digital image data corresponding to a medical sample associated with a patient; a data manager communicatively connected to the scanner system, the data manager configured to receive the digital image data from the scanner system; and a platform partner communicatively connected to the data manager, the platfomr partner configured to display at least one digital image based on the digital image data, wherein the platform partner includes at least one viewer configured to display the at least one digital image. The data manager is communicatively connected to one or more artificial intelligence partners deployed in at least one cloud platform, each of the one or more artificial intelligence partners being configured to generate supplemental data, the data manger is directly communicatively connected to a laboratory information system (LIS / LIMS), and the data manager is directly communicatively connected to the platform partner. The data manager is configured to: associate the digital image data with patient health information for the patient recalled from the LIS / LIMS to generate associated digital image data; provide the associated digital image data to the viewer for displaying of the digital image by the viewer; and receive a first supplemental output regarding the medical sample generated by the first artificial intelligence partner, the first supplemental output generated based on request information that is at least partially formed by at least a portion of the digital image data, provide the first supplemental output to the platform partner for displaying by the viewer.

[0008] According to an additional or alternative aspect of the disclosure, a system for generating and processing digital images regarding medical samples, the system including a data manager configured to communicatively connect to a scanner system configured to generate digital image data corresponding to a medical sample associated with a patient, the data manager configured to receive the digital image data from the scanner system and configured to associate the digital image data with patient health information for the patient to generate associated digital image data, the patient health information recalled from a laboratory information database (LIS / LIMS) by the data manager; and a platform provider directly communicatively connected to the data manager, the platform provider configured to generate and display at least one digital image based on the digital image data, wherein the platform provider includes at least one viewer configured to display the at least one digital image. The data manager includes a transfer management module disposed on a local server; and a data distribution module. The data manager is configured to provide the associated digital image data to the platform provider. The platform provider is directly communicatively connected to one or more artificial intelligence partners deployed in at least one Al cloud platform, the one or more artificial intelligence partners being configured to generate supplemental data based on request data and to output the supplemental data, wherein the request data at least partially includes at least a portion of the digital image data. The data distribution module is further configured to: receive the first supplemental data generated by the first artificial intelligence partner; and transmit the first supplemental data to the transfer management module; and wherein the transfer management module is configured to write the first supplemental data to the LIS / LIMS.

[0009] According to another additional or alternative aspect of the disclosure, a method of processing digital images regarding medical samples, the method including receiving, by a data manager, digital image data generated by a scanner system, the scanner system configured to generate the digital image data based on a scan of a medial sample associated with a patient; recalling, by the data manager, patient health information for the patient from a laboratory information database (LIS / LIMS) and associating, by the data manager, the patient health information with the digital image data to generate associated digital image data; receiving, by the data manager, a supplemental request from a viewer of a platform partner directly communicatively connected to the data manager; generating, by the data manager, request data based on the supplemental request, the request data including at least a portion of the digital image data; providing the request data to at least one artificial intelligence partner deployed in a cloud platform to cause the at least one artificial intelligence partner to generate supplemental data; receiving, by the data manager, the supplemental data; and providing, by the data manager, the supplemental data to the viewer for displaying the supplemental data.

[0010] According to yet another additional or alternative aspect of the disclosure, a system for generating and processing digital images regarding medical samples includes a scanner system configured to generate digital image data corresponding to a medical sample associated with a patient; a data manager communicatively connected to the scanner system, the data manager configured to receive the digital image data from the scanner system; and a platform partner communicatively connected to the data manager, the platform partner configured to display at least one digital image based on the digital image data, wherein the platform partner includes at least one viewer configured to display the at least one digital image; wherein the data manager is directly communicatively connected to one or more artificial intelligence partners deployed in at least one cloud platform, each of the one or more artificial intelligence partners being configured to generate supplemental data, the data manger is directly communicatively connected to a laboratory information system (LIS / LIMS), and the data manager is directly communicatively connected to the platform partner; and wherein the data manager is configured to: associate the digital image data with patient health information for the patient recalled from the LIS / LIMS to generate associated digital image data; provide the associated digital image data to the viewer for displaying of the digital image by the viewer; generate and provide request information to a first artificial intelligence partner of the one or more artificial intelligence partners to cause the first artificial intelligence partner to generate a first supplemental output regarding the medical sample, wherein the request information at least partially includes at least a portion of the digital image data; and receive the first supplemental output from the first artificial intelligence partner and provide the first supplemental output to the platform partner for displaying by the viewer.

[0011] According to yet another additional or alternative aspect of the disclosure, a system for generating and processing digital images regarding medical samples includes a data manager communicatively connected to a scanner system configured to generate digital image data corresponding to a medical sample associated with a patient to receive the digital image data from the scanner system and configured to associate the digital image data with patient health information for the patient to generate associated digital image data, the patient health information recalled from a laboratory information database (LIS / LIMS) by the data manager; and a platform provider communicatively connected to the data manager, the platform provider configured to generate and display at least one digital image based on the digital image data, wherein the platform provider includes at least one viewer configured to display the at least one digital image. The data manager includes a transfer management module disposed on a local server; and a data distribution module disposed on a manager portal within a first cloud platform. The data manager is configured to provide the associated digital image data to the platform provider. The data distribution module is directly communicatively connected to one or more artificial intelligence partners deployed in at least one Al cloud platform, the one or more artificial intelligence partners being configured to generate supplemental data based on request data and to output the supplemental data, wherein the request data at least partially includes at least a portion of the digital image data. The data distribution module is further configured to: provide the request data to a first artificial intelligence partner of the one or more artificial intelligence partners to cause the first artificial intelligence partner to generate first supplemental data; receive the first supplemental data from the first artificial intelligence partner; and transmit the first supplemental data to the transfer management module. The transfer management module is configured to provide the first supplemental data to the platform provider for display by the viewer.

[0012] BRIEF DESCRIPTION OF THE DRAWINGS FIG. l is a block diagram showing a digital image generation and processing system.

[0013] FIG. 2 is a schematic diagram showing an example of an image processing system.

[0014] FIG. 3 is a schematic diagram showing an example of an image processing system.

[0015] FIG. 4 is a schematic diagram showing an example of an image processing system.

[0016] FIG. 5 is a schematic diagram showing an example of an image processing system. DETAILED DESCRIPTION

[0017] The present disclosure is directed to systems and methods for generating and processing slide image data generated by one or more scanners. As explained in more detail herein, systems and methods of the present disclosure provide for integrated workflow between platform providers, such as an image display system providing a viewer for the user, and artificial intelligence (Al) programs. A data manager is configured to receive image data from a scanner. The data manager can recall patient health information from a laboratory information system / laboratory information management system (LIS / LIMS) and associate that information with the image data to generate associated image data. A platform partner, which provides components (e.g., software and / or hardware) of the viewer, has a single integration with the data manager. The platform partner can be hosted locally or on a cloud platform. The data manager is configured to generate and provide the associated image data for viewing on the viewer. For example, integration can refer to the ability of components within the system to communicate with one another according to a common protocol and / or in a common format, such that the receiving component is able to understand and work with the data provided by the transmitting component.

[0018] Al partners provide Al algorithms that are available in a cloud computing environment. The Al partners host algorithm infrastructure on a cloud platform. The Al partners are configured to generate supplemental data regarding the image data for a medial sample. The image data can be provided to the Al algorithm and the Al algorithm provides a supplemental output. The supplemental data can be in the form of diagnostic data (e.g., annotated image, highlighted image, written report, etc.), image quality information (e.g., identifying blurry images or other defects), report data, comments, notes, analytics, among other options.

[0019] According to some aspects of the disclosure, the data manager is configured to control data transfer to and from the Al partners. The data manager can be configured to provide single point integration for the Al partners. In such a configuration, the Al partners are integrated with the data manager and the data manager is configured to control data transfer to and from the Al partners and to and from the platform partner.

[0020] The data manager according to aspects of the disclosure provides single point integration for platform partners and Al partners. The platform partners are integrated with the data manager to facilitate data communication to and from the platform partner. The data manger provides a communication link between the viewer provided by the platform partner and the scanner. The data manager can further provide a communication link between the LIS / LIMS and the platform partner. The data manager provides a single integration point for the platform partner such that migration to a new platform partner requires integration with only the data manager to provide data to or receive data from the scanner and LIS / LIMS.

[0021] The Al partners are integrated with the data manager to facilitate data communication to and from the Al partners. The data manager can, in some examples, control all data communications between the Al partners and the platform partner. The data manager can, in some examples, provide a bridge between local components (e.g., scanner, LIS / LIMS) and the platform provider as well as between such local components and Al partners. The data manager can, in some additional or alternative examples, provide a bridge between the Al partners and the platform partner. The data manager providing the integration with the Al partners allows for quick and easy addition or removal of Al partners. In some examples, the platform partner is not required to directly integrate with the Al partners such that a migration to a new platform partner does not require reintegration with all Al partners. Instead, the relationship between Al partners and the data manager is maintained and the new platform partner needs to only be integrated with the data manager to facilitate data communications with the Al partners.

[0022] Systems, devices, and methods disclosed herein provide a platform for more efficient and cost effective analysis of medical samples and diagnosis of disease. The systems, devices, and methods can provide single point integration for multiple partners with a data manager that facilitates and can provide communication between the partners. The individual partners are not required to have multiple integrations with each other according to aspects of the disclosure. Instead, the single point integration with the data manager maintains the partner relationships and can facilitate quick and easy transfer between cloud platforms as required by an end user.

[0023] FIG. 1 is a block diagram of digital image processing system 10. System 10 includes scanner system 12, laboratory information database 14 (LIS / LIMS 14), data manager 16, image association module 18, image repository 20, cloud platform 22ai, cloud platform 22dm, Al partners 24a-24n (collectively herein “Al partner 24” or “Al partners 24”), and platform partner 26. Scanner system 12 includes scanner 28 and scanner administrator 30. Data manager 16 includes monitoring module 32, prioritization module 34, transfer manager 36, and data distribution module 38. Transfer management module 40 and data association module 42 of transfer manager 36 are shown. Platform partner 26 includes viewer 44.

[0024] System 10 can be configured to generate information regarding digital images and control transmission of information regarding such images. System 10 can be configured to generate, process, and control transmission and communication of digital image data. The digital image data can include a digital image itself and / or image metadata. In some examples, system 10 can be configured to generate information regarding the whole slide images (WSI) for diagnostic purposes. A whole slide image can include data regarding the image itself (i.e., the digital image) and image metadata. The WSI can be considered to form digital image data in at least some examples. It is understood, however, that the digital image data can include the digital image without image metadata or image metadata without the digital image, among other options.

[0025] Scanner system 12 is configured to generate digital image data and provide that digital image data to data manager 16. Scanner system 12 is a local system that is disposed on premises at a location, which local location can be referred to as a “local facility.” Scanner system 12 includes one or multiple individual scanners 28 that are configured to generate initial image data regarding a medical sample associated with a patient. The scanner administrator 30 can be communicatively connected to one or more, up to all, of the scanners 28 disposed at the local facility. The initial image data is provided to the scanner administrator 30. In some examples, the scanner 28 is configured for unidirectional communications. For example, the scanner 28 can be configured to output information (e.g., initial image data) to scanner administrator 30 but is not configured to receive information from scanner administrator 30.

[0026] Scanner administrator 30 can be configured as one or more servers. Scanner administrator 30 is communicatively connected to one or more scanners 28 to receive the initial image data from the scanners 28. The scanner administrator 30 is configured to output digital image data. In some examples, the scanner administrator 30 is configured to convert one or more portions of the initial image data into a different file format to generate the digital image data. For example, the scanner 28 can be configured to provide the initial image data in a primary file format. The primary file format can, in some examples, include image metadata, such as additional information such as information regarding the patient. The primary file format can include the digital image and image metadata. For example, the primary file format can include identifying information regarding the patient, such as a barcode that identifies the patient in LIS / LIMS 14, among other information options. The primary file format can be referred to as an “aware file format” in that the primary file format includes identifying information regarding the patient. In some examples, the primary file format can be in the Digital Imaging and Communications in Medicine (DICOM) standard (ISO 12052), among other options. In some examples, the scanner administrator 30 is configured to treat the initial image data in the primary file format as the digital image data. In such an example, the scanner administrator 30 can collect initial image data and pass such initial image data along as all or a portion of the digital image data, such as by transmitting to the image repository 20.

[0027] In some examples, scanner system 12 is configured to output the digital image data in multiple file formats. For example, the scanner system 12 can be configured to generate the digital image data in a secondary file format in addition to the primary file format. The secondary file format can include image data without identifying information regarding the patient. The secondary file format can include the digital image without image metadata. As such, the digital image data in the secondary file format can be utilized to display the digital image but does not include the image metadata. The secondary file format can be referred to as an “unaware file format” in that the secondary file format does not include identifying information regarding the patient. In some examples, the scanner administrator 30 can be configured to generate the digital image data in the secondary file format based on the image data in the first file format. For example, the scanner administrator 30 can be configured to generate the digital image data in the secondary file format is a tiled image. In some examples, the second file format can be an SVS file, or a TIFF file, among other options.

[0028] The scanner administrator 30 is configured to transmit the digital image data to image repository 20. The digital image data can include image data in multiple formats, though it is understood that not all examples are so limited. For example, the digital image data can include data in the primary file format and can include data in the secondary file format.

[0029] The scanner administrator 30 is configured to send the digital image data to image repository 20. Image repository 20 can, in some examples, be a local database disposed at the local facility with scanner system 12. In some examples, image repository 20 can be distributed across multiple component devices. Image repository 20 can be configured as a file share, such as disposed on a local area network, among other options.

[0030] Platform partner 26 provides software and hardware components for viewing digital images of slides. Platform partner 26 includes viewer 44 that can display digital scans of slide images. Viewer 44 can, in some examples, include an interactive user interface which can display digital images, provide information to the user (e.g., pathologist, administrator, etc.), display information received from Al partners 24, among other options. Viewer 44 can be configured to display whole slide images, among other options. In some examples, platform partner 26 is disposed locally at the local facility, though it is understood that not all examples are so limited. For example, platform partner 26 can be deployed on a cloud platform (e.g., cloud platform 22ai, or cloud platform 22dm, among other options).

[0031] Al partners 24 are disposed in cloud platform 22ai. It is understood that each of Al partners 24 can be disposed in a single, common cloud platform 22ai or disposed across various discrete cloud platforms 22ai. Each Al partner 24 provides one or more Al algorithms that are configured to output supplemental data regarding the slide images. For example, an Al partner 24 can be configured to provide an annotated image, highlighted image, written report, etc. In some examples, an Al partner 24 can include an Al slide viewer that facilitates viewing of the supplemental data generated by the Al partner 24, though it is understood that not all examples are so limited.

[0032] Data manager 16 is configured to receive the digital image data from scanner system 12. In some examples, the scanner system 12 can be configured to transmit the digital image data directly to data manager 16. In some examples, the scanner system 12 is configured to output the digital image data to image repository 20 and the data manager 16 is configured to retrieve the digital image data from image repository 20. In some such examples, the data manager 16 is configured to monitor the image repository 20 and to pull digital image data from image repository 20 based on the digital image data being received in the image repository 20.

[0033] Data manager 16 is configured to provide single integration for the platform partner 26 to communicate with other components of system 10. Data manager 16 is configured to provide associated digital image data regarding medical samples and can provide responsive outputs to user requests. Data manager 16 is configured to store software, implement functionality, and / or process instructions. Data manager 16 can be of any suitable configuration for gathering data, processing data, etc. Data manager 16 can receive inputs, provide outputs, generate responsive information, and / or output information regarding medical samples. Data manager 16 can include hardware, firmware, and / or stored software. Data manager 16 can be entirely or partially mounted on one or more circuit boards. It is understood that the functionality attributed to the data manager 16 herein can be distributed across one or more physical and / or virtual machines.

[0034] Data manager 16 can be a discrete assembly or can be formed by one or more devices capable of individually or collectively implementing functionalities and generating and outputting data as discussed herein. Data manager 16 can, in some examples, be considered to form a single computing device even when distributed across multiple component devices. Data manager 16 is configured to perform any of the functions attributed herein to data manager 16, including receiving an output from any source referenced herein, detecting any condition or event referenced herein, and generating and providing data and information as referenced herein. Data manager 16 can be of any type suitable for operating in accordance with the techniques described herein. In some examples, data manager 16 can be implemented as a plurality of discrete circuitry subassemblies.

[0035] Data manager 16 can include control circuitry 46, memory 48, and user interface 50. Control circuitry 46, in one example, is configured to implement functionality and / or process instructions. Examples of control circuitry 46 can include one or more of a processor, a microprocessor, a controller, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a graphics processing unit (GPU), a system-on-module (SOM), or other equivalent discrete or integrated logic circuitry. Control circuitry 46 is configured to execute the software or other code stored by memory 48 to perform various functions referenced herein. Control circuitry 46 can be entirely or partially mounted on one or more circuit boards.

[0036] Memory 48 can be configured to store data and information before, during, and / or after operation. Memory 48, in some examples, is described as computer-readable storage media. In some examples, a computer-readable storage medium can include a non-transitory medium. The term “non-transitory” can indicate that the storage medium is not embodied in a earner wave or a propagated signal. In certain examples, a non-transitory storage medium can store data that can, over time, change (e.g., in RAM or cache). In some examples, memory 48 is a temporary memory, meaning that a primary purpose of the memory is not long-term storage. The memory 48, in some examples, is described as volatile memory, meaning that memory 48 does not maintain stored contents when power to data manager 16 is turned off. Examples of volatile memories can include random access memories (RAM), dynamic random access memories (DRAM), static random access memories (SRAM), and other forms of volatile memories. In some examples, memory 48 is used to store program instructions for execution by control circuitry 46. Memory 48, in one example, is used by software or applications running on data manager 16 to temporarily store information during program execution.

[0037] Memory 48, in some examples, also includes one or more computer-readable storage media. Memory 48 can be configured to store larger amounts of information than volatile memory. Memory 48 can further be configured for long-term storage of information. In some examples, memory 48 includes non-volatile storage elements. Examples of such non-volatile storage elements can include magnetic hard discs, optical discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.

[0038] As illustrated in FIG. 1 , memory 48 can be configured to include monitoring module 32, transfer management module 40, data distribution module 38, data association module 42, and prioritization module 34. Modules 32, 34, 38, 40, 42 can take the form of computer-readable instructions that, when executed by control circuitry 46, cause data manager 16 to implement functionality attributed herein to modules 32, 34, 38, 40, 42. Though the example of FIG. 1 is described with respect to separate modules 32, 34, 38, 40, 42, it is understood that the techniques described herein with respect to such modules 32, 34, 38, 40, 42, can be implemented in a single module or multiple modules (e.g., two, three, four, etc.) that distribute functionality attributed herein to modules 32, 34, 38, 40, 42 among the multiple modules. In general, memory 48 can store computer-readable instructions that, when executed by control circuitry 46, cause data manager 16 to operate in accordance with techniques described herein.

[0039] User interface 50 is an input and / or output device and / or software interface that enables an operator, such as a user, to control operation of and / or interact with software elements of data manager 16. For example, user interface 50 can be configured to receive inputs from the user and / or provide outputs to the user. In one example, user interface 50 can be configured to receive inputs from a user, such as requests for additional information, and / or can provide information responsive to a request from a user, among other information. Examples of user interface 50 can include one or more of a sound card, a video graphics card, a graphical user interface (GUI), a speaker, a display device (such as a liquid crystal display (LCD), a light emitting diode (LED) display, an organic light emitting diode (OLED) display, etc.), a touchscreen, a keyboard, a mouse, a joystick, or other type of device for facilitating input and / or output of information in a form understandable to users and / or machines. Data manager 16 is a network-connected device that is connected to local and, in some examples, remote components. Data manager 16 can be disposed on premises with other local components, such as within the local facility. In some examples, such as shown in FIG. 1, the data manager 16 can be disposed across various locations, such as with a portion of data manager 16 disposed locally and another portion of data manager 16 deployed in cloud platform 22dm. Data manager 16 can include one or more hardware elements, devices, etc. for facilitating electronic communication with a wide area network (WAN) and / or local area network (LAN) and / or any other suitable device via one or more wired and / or wireless connections. It is understood that data manager 16 can be formed by any one or more suitable network-connectable computing device(s) for performing the functions of data manager 16 detailed herein.

[0040] In the example shown, data manager 16 is configured to receive the digital image data output by scanner administrator 30. In some examples, scanner administrator 30 is configured to output the digital image data in multiple file formats as discussed above. Data manager 16 can be configured to receive the digital image data in one or multiple of the image file formats. In some examples, the data manager 16 is configured to receive the digital image data in a single file format.

[0041] Data manager 16 includes monitoring module 32 in some examples. Monitoring module 32 is configured to monitor incoming transmissions to image repository 20 and pull the digital image data into data manager 16. In some examples, monitoring module 32 is configured to pull information from image repository 20 based on the file type provided to image repository 20. For example, monitoring module 32 can be configured to pull the digital image data in the primary file format and / or the secondary file format, among other options. The digital image data in the secondary file format does not include patient identifying information. Instead, the digital image data in the secondary file format includes the image data that is needed to generate and display an electronic image on viewer 44.

[0042] Monitoring module 32 can provide the retrieved digital image data to prioritization module 34. Prioritization module 34 can, in some examples, store digital image data for processing by data manager 16. In some examples, prioritization module 34 can place the digital image data in various positions within a queue for further processing by data manager 16, such as depending on the priority of the case associated with that digital image data. For example, prioritization module 34 can be configured such that higher priority cases are placed closer to the front of a line for further processing while lower priority cases can be placed further back in the line for further processing by data manager 16.

[0043] Data manager 16 includes transfer manager 36 that facilitates communication between data manager 16 and various other components of system 10. In the example shown, transfer manager 36 is distributed both locally and in a cloud computing environment, though it is understood that not all examples are so limited. For example, transfer manager 36 can be disposed locally and not partially in a cloud computing environment in various examples. Transfer manager 36 is communicatively connected to platform partner 26 and is configured to provide data communications to and receive data communications from platform partner 26. Transfer manager 36 can, in some examples, be communicatively connected to Al partners 24 to provide data communications to and receive data communications from Al partners 24.

[0044] Transfer manager 36 provides a single communication integration point for platform partner 26. Platform partner 26 can provide requests for information to transfer manager 36 and can receive information from transfer manager 36. In the example shown, platform partner 26 is not directly communicatively connected to L1S / L1MS 14. Instead, data manager 16 is configured to provide all data communications between LIS / LIMS 14 and platform partner 26. Such a configuration with a single integration point for platform partner 26 facilitates quick, easy, and secure data communications between LIS / LIMS 14 and platform partner 26. In such a configuration, the end user can migrate from one platform partner 26 to another platform partner 26 and such a change requires only a single integration with data manager 16 without requiring the formation of new partnerships and integrations with scanner system 12, LIS / LIMS 14, and other local components.

[0045] In some examples, transfer manager 36 provides a single communication integration point for Al partners 24. Al partners 24 can receive information from and provide information to transfer manager 36. Transfer manager 36 can, in some examples, provide all communications between Al partners 24 and other components of system 10. Each of the Al partners 24 can have its own integration with data manager 16. The single integration point for each of Al partners 24 and transfer manager 36 facilitates quick, easy, and secure data communications between Al partners 24 and other components of system 10, such as platform partner 26, scanner system 12, LIS / LIMS 14, etc.

[0046] It is understood, however, that in alternative examples platform partner 26 can be directly communicatively connected to one or more Al partners 24. Such a communication link is illustrated with the dashed line link between Al partners 24 and platform partner 26 shown in FIG. 1. In such an example, transfer manager 36 provides a single integration point for platform partner 26 and insulates information from scanner system 12 and within LIS / LIMS 14 from direct communication with either Al partners 24 or platform partner 26. Transfer manager 36 can receive requests for information from and provide information to platform partner 26. In such an example, Al partners 24 are directly integrated with platform partner 26 to provide direct communications between Al partners 24 and platform partner 26. In such an example, transfer manager 36 may not include any cloud-based components (as discussed with regard to FIGS. 4 and 5 below) and may instead be disposed fully locally.

[0047] In the example shown in FIG. 1 , transfer manager 36 can be deployed across multiple platforms. In the example shown, transfer manager 36 includes transfer management module 40 that is disposed locally and includes data distribution module 38 that is deployed in cloud platform 22dm. It is understood, however, that in various other examples transfer manager 36 can be deployed locally without components disposed on cloud platform 22dm.

[0048] Cloud platform 22dm can, in some examples, be the same cloud platform as cloud platform 22ai such that data distribution module 38 and one or more Al partners 24 are deployed in the same cloud platform. In other examples, cloud platform 22dm can be different from cloud platform 22ai. For example, the data distribution module 38 can be deployed in cloud platform 22dm that is distinct from cloud platform 22ai. It is further understood that while a single cloud platform 22ai is shown, Al partners 24 can, in some examples, be deployed across various cloud platforms 22ai. For example, a first Al partner 24 can be deployed in a first cloud platform 22ai and a second Al partner 24 can be deployed in a second cloud platform 22ai distinct from the first cloud platform 22ai.

[0049] Transfer manager 36 is configured to control communication of data into and out of data manager 16. Transfer manager 36 is communicatively connected with platform partner 26 and is configured to provide data communications to platform partner 26 and to receive data communications from platform partner 26. All or portions of transfer manager 36 can be disposed in the same environment as platform partner 26. In some examples, transfer manager 36 and platform partner 26 can both be disposed locally. In such an example, transfer manager 36 and platform partner 26 can communicate via a local area network (LAN), among other options. In some examples, transfer manager 36 can be partially deployed in a cloud computing environment (e.g., cloud platform 22dm) and platform partner 26 can also be deployed in the same or another cloud computing environment.

[0050] In the various examples, transfer manager 36 is deployed, at least partially, locally. Such local deployment of transfer manager 36 protects the image data and personal health information as such data does not need to leave the local facility (e.g., the local network, among other options) for transfer between local components. Transfer manager 36 further facilitates communications with components not disposed locally, such as with Al partners 24 and with platform partner 26 in examples in which platform partner 26 is not deployed locally. Such a configuration provides controlled data communications that provides improved security and connectivity between the various components of system 10.

[0051] In some examples, data manager 16 can generate associated digital image data based on the digital image data received from scanner system 12 and information from LIS / LIMS 14. Data manager 16 can have bi-dircction communications with LIS / LIMS 14. The data manager 16 can receive information from LIS / LIMS 14 and data manager 16 can write information to LIS / LIMS 14.

[0052] Data association module 42 can receive digital image data, such as the labeled digital image, from transfer manager 36. Data association module 42 is disposed locally. In the example shown, transfer management module 40 can provide a request to data association module 42, such as a request for information or can a request to write information to LIS / LIMS 14, among other options.

[0053] Data manager 16 is communicatively connected to LIS / LIMS 14. In the example shown, data association module 42 is configured to control communications with LIS / LIMS 14. Data association module 42 can, in some examples, be configured to recall information from and / or write information to LIS / LIMS 14. In one example, data association module 42 can be configured to write supplemental data from an Al partner 24 to LIS / LIMS 14. For example, data association module 42 can provide a URL to LIS / LIMS 14 that allows the user to access a viewer provided by Al partner 24 (e.g., via viewer 44 of platform partner 26), or can provide the supplemental information to LIS / LIMS 14 in any other desired manner.

[0054] The Al partners 24 can be caused to generate a link (e.g., a URL) based on information from data manager 16 and the Al partners 24 can provide the URL to the data manager 16 which can write the URL information to LIS / LIMS 14. A user can utilize the URL to access the information generated by the Al partner 24. The URL can open a platform viewer 44 in a browser to access the information.

[0055] In some examples, the user to take notes and / or make comments regarding the image data, such as via viewer 44 among other options. Such information can be compiled into a report that the data manager 16 can transmit to the LIS / LIMS 14 for storage and later access if needed.

[0056] In some examples, data manager 16 is configured to generate associated digital image data. The associated digital image data includes the digital image data and selected patient health information regarding the patient associated with the medical sample from which the digital image data was generated. Such additional information that is associated with the digital image data can take the form of metadata. For example, the associated digital image data can include image data along with other information from LIS / LIMS 14, such as demographic information (e.g., age, gender, etc.), health history information, or other options. The associated digital image data can be provided to the user, such as via platform partner 26. The associated digital image data can, additionally or alternatively, be provided to an Al partner 24 to facilitate the Al partner 24 generating an Al supplemental output.

[0057] Image association module 18 is configured to monitor data transmissions coming from scanner system 12. For example, image association module 18 can monitor transmissions being provided to image repository 20, among other options. Image association module 18 is configured to provide identifying information to data manager 16 regarding the medical sample for which the digital image data was generated. As previously discussed, the digital image data can be received by data manager 16 in a secondary image format that does not include identifying patient information. Image association module 18 can be configured to determine a unique identifier associated with the medical sample / patient and image association module 18 can provide that unique identifier to data manager 16. In the example shown, image association module 18 is configured to provide the unique identifier to transfer management module 40.

[0058] In some examples, scanner system 12 can output the digital image data in multiple file formats (e.g., the primary file format, the secondary file format, or other options). That digital image data can be provided to image association module 18 and / or passed through image association module 18. Image association module 18 is configured to copy information from the digital image data to generate identification data that includes the unique identifier. For example, image association module 18 can copy the unique identifier that is present in the primary file format (e.g., present in the image metadata) and copy a file identifier (e.g., file name or other identifying information) present in the secondary file format that identifies the data in the secondary file format.

[0059] Image association module 18 can package the unique identifier and the file identifier together to generate the identification data. Image association module 18 is configured to provide the packaged identification data to data manager 16. Image association module 18 is configured to copy the relevant information from the data being transmitted from scanner system 12 and does not modify the digital image data being output by scanner system 12. In this way, image association module 18 can generate the identification data without affecting the integrity of the digital image data, thereby preserving the digital image data as output by scanner system 12.

[0060] The packaged identification data is provided to data manager 16. For example, the packaged identification data can be provided directly to transfer management module 40. Transfer management module 40 can, in some examples, utilize the identification data to generate an image label. The image label is associated with the digital image data to facilitate communication between data manager 16 and L1S / LIMS 14. For example, data manager 16 can receive the digital image data in the secondary file format. The secondary file format includes information regarding the electronic image (e.g., includes the digital image) but does not include identifying information regarding the medical sample or patient. Data manager 16 can identify the patient associated with the digital image data based on the identifying information provided by image association module 18. Data manager 16 can associate the digital image data with the patient based on the file identifier from the identifying information matching with the file identifier of the digital image data in the secondary file format.

[0061] Data manager 16 generates the image label based on the unique identifier in the identifying information and the image label is associated with the digital image data, thereby generating labeled digital image data. The labeled digital image data includes patient identifying information sufficient to facilitate communications with LIS / LIMS 14. For example, data manager 16 can be configured to label the image data received in an unaware file format with the image label such that the information in the unaware file format is now associated with a particular patient in the LIS / LIMS 14, facilitating data communications between data manager 16 and LIS / LIMS 14.

[0062] Data manager 16 provides single point integration for platform partner 26. Platform partner 26, which provides viewer 44, is directly integrated with data manager 16 such that data manager 16 controls data transmission from locally disposed components to and from platform partner 26. Data manager 16 isolates platform partner 26 from data transmissions from scanner system 12 such that the digital image data is communicated to platform partner 26 by data manager 16 and not directly from scanner system 12. Data manager 16 also isolates platform partner 26 from LIS / LIMS 14 such that data transmissions to or from LIS / LIMS 14 are handled by data manager 16 and are not communicated directly between platform partner 26 and LIS / LIMS 14. As such, platform partner 26 is indirectly integrated with the scanner system 12 and LIS / LIMS 14 via the direct integration of platform partner 26 with data manager 16. Data manager 16 can provide a single integration point for each of Al partners 24. In such an example, platform partner 26 is not directly communicatively connected to Al partners 24. Platform partner 26 is instead communicatively connected to Al partners 24 via data manager 16.

[0063] According to one example, scanner system 12 generates the digital image data regarding a slide containing a medical sample. For example, scanner 28 can generate initial image data and provide that initial image data to scanner administrator 30. Scanner administrator 30 is configured to output digital image data to image repository 20. In some examples, scanner system 12 can provide digital image data to image repository 20 in multiple file formats. For example, scanner system 12 can output the digital image data to image repository 20 in a primary file format, such an aware file format, and in a secondary file format, such as an unaware file format.

[0064] Monitoring module 32 is configured to monitor data transmissions to image repository 20. Monitoring module 32 intakes the digital image data to data manager 16. In some examples, monitoring module 32 is configured to intake the digital image data in multiple formats, such as in the primary file format and the secondary file format. Monitoring module 32 is configured to transmit the digital image data to transfer manager 36. In some examples, monitoring module 32 provides the digital image data to prioritization module 34 from which the digital image data is provided to transfer manager 36.

[0065] Image association module 18 monitors the data transmissions output by scanner system 12. Image association module 18 is configured to generate and output identifying information regarding data in the secondary file format and provides such identifying information to data manager 16. For example, image association module 18 can be configured to provide such identifying information directly to transfer manager 36. Data manager 16 is configured to assign a unique identifier to the digital image data in the secondary file format based on the identifying information received from image association module 18. For example, data manager 16 can compare a file identifier in the identifying information from image association module 18 with the file identifier of one or more packets of digital image data in the secondary file format. Data manager 16 can associate the unique identifier with the image data in the secondary file format that has a file identifier that matches with the file identifier from the identifying information. Such an association tags the image data in the secondary file format with the unique identifier such that the image data in the secondary file format is associated with the patient in LIS / LIMS 14 to facilitate retrieval of information from or transfer of information to LIS / LIMS 14.

[0066] Transfer manager 36 receives the digital image data from prioritization module 34, in examples including prioritization module 34, and can transmit the digital image data to viewer 44 such that the user can interact with the digital image data and view the electronic images. For example, transfer manager 36 can provide a WSI to viewer 44 to be displayed by viewer 44. In the example shown, transfer management module 40, which is disposed locally, provides communications between data manager 16 and platform partner 26.

[0067] Data manager 16 is further configured to provide information to and receive information from LIS / LIMS 14. Data manager 16 is configured to recall information from LIS / LIMS 14 and provide such information to the user via viewer 44. In the example shown, data association module 42 is configured to communicate with LIS / LIMS 14. Data association module 42 can recall relevant patient health information for a patient associated with the digital image data and provide that patient health information to transfer manager 36. Transfer manager 36 can package the digital image data and the patient health information together as associated image data. Transfer manager 36 can provide the associated image data to platform partner 26 for viewing by the user on viewer 44.

[0068] In some additional or alternative examples, data manager 16 is configured to receive data requests from the user, via platform partner 26, and is configured to provide information responsive to such requests. For example, the user may want some additional information regarding the patient. The user can input such a request at viewer 44 and the request is transmitted to data manager 16. Data manager 16 retrieves the requested information from LIS / LIMS 14, such as via data association module 42, and can communicate the retrieved information back to the user via platform partner 26. Al partners 24 generate Al supplemental information to assist the user in analyzing the medical sample. A request for Al supplemental information can be provided by the user to data manager 16 and / or data manager 16 can be configured to cause an Al partner 24 to generate supplemental information based on data manager 16 receiving the digital image data. Data manager 16 can be configured to cause certain Al partners 24 to provide Al supplemental information based on information regarding the digital image data. For example, data manager 16 can cause certain Al partners 24 to generate Al supplemental information based on the information provided to data manager 16 from the digital image data in the primary file format. Data manager 16 can, in additional or alternative examples, cause certain Al partners 24 to generate Al supplemental information based on information received from LIS / LIMS 14 regarding the digital image data. It is thus understood that in various examples data manager 16 can be configured to automatically cause one or more of Al partners 24 to generate the Al supplemental information based on characteristics of the medical sample (c.g., based on the specimen type, based on a priority of the specimen, based on historical infomiation regarding the patient, or other options). As such, data manager 16 can be configured to cause generation of and include the Al supplemental information in the data provided to platform partner 26 for viewing on viewer 44.

[0069] Transfer manager 36 is configured to communicate with Al partners 24 as well as platform partner 26. Transfer manager 36 is directly integrated with Al partners 24 to provide the direct communication integration between system 10 and Al partners 24, in this example. In the example shown, transfer management module 40 is configured to provide information, such as requests for Al supplemental information, to data distribution module 38. Data distribution module 38 is deployed in cloud platform 22dm. Data distribution module 38 is communicatively integrated with one or more Al partners 24. For example, each Al partner 24 can be integrated with data distribution module 38 at an application programming interface (API) of data distribution module 38, facilitating communication with Al partner 24 to provide the single integration point for each Al partner 24. Data distribution module 38 can include multiple APIs for facilitating communication with multiple Al partners 24.

[0070] Data distribution module 38 can send a request for Al supplemental information to Al partner 24 and / or receive Al supplemental information as a responsive output from Al partner 24. Data distribution module 38 can communicate the responsive Al supplemental information to transfer management module 40 and transfer management module 40 can provide such responsive Al supplemental information to platform partner 26. In some examples, data manager 16 is configured to receive the Al supplemental information and can write such Al supplemental information to LIS / LIMS 14.

[0071] While transfer manager 36 is shown as including transfer management module 40 that is deployed locally and data distribution module 38 deployed in cloud platform 22dm, it is understood that not all examples are so limited. In some examples, transfer manager 36 includes transfer management module 40 and data distribution module 38 both deployed locally (see FIGS. 4 and 5). During the Al supplemental data generation process, data manager 16 can generate and provide filtered request data to Al partners 24. In some examples, each Al partner 24 can require baseline information to generate the Al supplemental information. The baseline information can include image data as well as, in some examples, additional information (e.g., certain patient health information). The integration between Al partner 24 and data manager 16 provides the baseline information requirements for Al partner 24 to data manager 16 such that data manager 16 is aware of what baseline information is required for each Al partner 24 integrated with data manager 16.

[0072] Data manager 16 can generate the filtered request data based on the baseline information required by Al partner 24. The filtered request data can be a subset or otherwise different from the digital image data provided to viewer 44. For example, data manager 16 can provide the digital image data to viewer 44 in the primary file format that includes various patient health information associated with the patient. However, the personal information regarding the patient that is provided to viewer 44 may not be required by Al partner 24 to generate the Al supplemental information. Data manager 16 is configured to limit the data transmitted to Al partner 24 to the baseline information that is required by Al partner 24. For example, the baseline information can be the electronic image and demographic information regarding the patient. Data manager 16 can generate the filtered request data including the electronic image and the demographic information, such as demographic information recalled from LIS / LIMS 14. For example, data manager 16 can provide the digital image data in the secondary file format, which does not inherently include patient health information, along with the required demographic information. As such, the data manager 16 can be configured to remove or limit the metadata provided to an Al partner 24 to just that information needed by the Al partner 24 to generate the supplemental data. In some examples, transfer manager 36 can include a request filter. For example, an API for Al partner 24 can include the request filter. The request filter can specify the data that is provided to Al partner 24 for generating the Al supplemental data. The request filter can, in some examples, limit the data that can be transmitted to Al partner 24 to the baseline information. For example, the request filter can specify that only information required to satisfy the baseline information is transmitted to Al partner 24 (e.g., digital image data with demographic information).

[0073] In some examples, data manager 16 can provide partner options to the user via viewer 44. A partner option can provide the identity of one or more Al partners 24 that can provide Al diagnostic information regarding the digital image data being analyzed. For example, data manager 16 can cause viewer 44 to display a menu allowing the user to select from between one or more partner options. Data manager 16 can select an Al partner 24 and cause Al partner 24 to generate the diagnostic output based on a response received from the user regarding the partner option. For example, data manager 16 can identify two Al partners 24 as being relevant to particular digital image data. Data manager 16 can present the two Al partners 24 to the user and the user can select one, or both, of Al partners 24 as a response to data manager 16. Data manager 16 can then cause the selected Al partner 24 to generate a supplemental output and data manager 16 can provide that supplemental output to the user.

[0074] It is understood that, in some alternative examples, Al partners 24 can be directly communicatively connected to platform partner 26 such that Al partners 24 are integrated directly with platform partner 26. In such an example, data manager 16 provides all data communications to and from the local components (scanner system 12 and LIS / LIMS 14) and platform partner 26 and thus to Al partners 24. For example, Al partner 24 can require certain patient health information (e.g., demographic information among other options) in addition to the digital image data to generate and provide the Al supplemental information. Data manager 16 can recall such patient heath information from LIS / LIMS 14 and provide the requested health information to platform partner 26 for platform partner 26 to generate the Al supplemental request. In such an example, data manager 16 can be configured to implement a request filter to limit data transmissions to Al partner 24 to only the data required to generate the Al supplemental output. Data manager 16 can thereby limit data transmission out of the local components when not directly communicatively connected to Al partner 24. In one additional or alternative example, the data manager 16 provides single integration with the platform partner 26 and each of the Al partners 24. The platform partner 26 can support the software that allows the viewer 44 to function and display the electronic image and other relevant information. The platform partner 26 can be disposed locally, such as on a local server, network, etc., or can be hosted in a cloud platform. The user can access the viewer 44 via a computing device, such as a personal computer (PC) among other options, to view the electronic image data and other relevant information. The viewer 44 can be configured to be capable of

[0075] If the user wants to switch from a first platform partner 26 to a second platform partner 26, such as to utilize a different viewer 44. For example, the user may want to utilize a file format supported by the second viewer 44 but not supported by the first viewer 44. To make such a change, the new, second platform partner 26 is integrated with the data manager 16 such that the data manager can transmit information to and receive information from the second platform partner 26, and thus to and from the second viewer 44. The new platform partner 26 is not required to be integrated directly with LIS / LIMS 14, scanner system 12, or Al partners 24 (in various examples).

[0076] In examples in which the Al partners 24 are directly integrated with the data manager 16, the new platform partner 26 does not require direct integration with the Al partners 24. Instead, the data manager 16 maintains the integrations with the Al partners 24 such that integration of the second platform partner 26 with the data manager 16 provides the platform partner 26 with access to and communication with the Al partners 24.

[0077] Further, if an Al partner 24 is desired to be added or removed, such an integration can be formed or broken directly with the data manager 16. A new Al partner 24 can be integrated with the data manager 16 to provide data communications between the data manager 16 and the Al partner 24. An old Al partner 24 can be removed by breaking the communication link with that Al partner 24. The integrations of Al partners 24 into system 10 does not require communication with or manipulation of the platform partner 26. Instead, the Al partners 24 are directly integrated with data manager 16, facilitating easier and more efficient integration and removal of Al partners 24 without affecting operation of platform partner 26 and viewer 44.

[0078] Data manager 16 provides significant advantages. Data manager 16 is configured to receive digital image data generated by scanner system 12 and is configured to recall and / or write information to LIS / LIMS 14. Data manager 16 provides a bridge between the local components (e.g., scanner system 12 and LIS / LIMS 14) and platform partner 26, which can be deployed locally or in a cloud computing environment. Data manager 16 provides for secure and efficient communication of image data and patient health information to and from viewer 44.

[0079] Data manager 16 is the single integration point for platform partner 26 to communicate with the local components of system 10. Such a configuration allows for quick and easy deployment of any platform partner 26 desired by the end user. It is understood that the user can select from among a variety of platform partners 26 to provide a desired viewer 44. The user, such as a medical laboratory pathologist, technician, etc., may decide to switch platform partners 26. In the event such a change is made, the new platfomr partner 26 requires only a single integration with data manager 16 to provide communications with local components and Al partners 24. Platform partner 26 is singly integrated with data manager 16, which provides for a quick and easy migration between platform partners 26 for the user. A new platform partner 26 is not required to be individually integrated with scanner system 12, LIS / LIMS 14, Al partners 24, etc. Instead, the new platform partner 26 can be singly integrated with data manager 16 and data manager 16 provides communications between platform partner 26 and other components of system 10.

[0080] In examples in which platform partner 26 is individually integrated with Al partners 24, data manager 16 provides a single integration point for platform partner 26 to communicate with local components of system 10. The user can switch to a new platform partner 26 and data manager 16 provides a single integration point for that platform partner 26, facilitating quick and easy update and modification of platform partner 26. Data manager 16 can limit data communications to Al partners 24 to only that data required to generate the Al supplemental information. Such a configuration provides for secure communications that protects sensitive patient health information. Such a configuration can also reduce the volume of data communications, thereby providing cost savings while facilitating quicker and more efficient communications.

[0081] FIG. 2 is a schematic block diagram of system 10A. Scanner system 12, LIS / LIMS 14, data manager 16, platform partner 26, and Al partners 24 of system 10A are shown. System 10A is an example of system 10 and is substantially similar to system 10. Transfer management module 40 and data distribution module 38 of data manager 16 are also shown. The example of system 10A shown in FIG. 2 can be referred to as a hybrid controller system as data manager 16 controls communications between the locally deployed platform partner 26 and the cloud deployed Al partners 24.

[0082] Scanner system 12 is communicatively connected to data manager 16. Scanner 28 is configured to generate digital image data regarding medical samples. The digital image data is provided to data manager 16. Data manager 16 provides a bridge between scanner 28, LIS / LIMS 14, platform partner 26, and Al partners 24. Data manager 16 is configured to facilitate communication between platform partner 26 and Al partners 24 and provides data communication between platform partner 26 and Al partners 24.

[0083] Data manager 16 provides a single integration point for platform partner 26 and Al partners 24 to facilitate transmission and analysis of digital image data generated by scanner 28, such as for diagnostic purposes, image quality analysis, etc. In the example shown, scanner 28, LIS / LIMS 14, and platform partner 26 are disposed locally at the local facility. Al partners 24 are disposed in cloud platform 22ai. Data manager 16 is partially disposed locally and partially disposed in a cloud environment. In the example shown, transfer management module 40 is disposed locally and data distribution module 38 is deployed in a cloud computing environment. In the example shown, data distribution module 38 is disposed in cloud platform 22dm. As discussed above with regard to FIG. 1, cloud platform 22dm can be the same as or different from cloud platform 22ai. Further, Al partners 24 can be disposed in different cloud platforms 22ai (e.g., Amazon Web Services Cloud (AWS), Microsoft Azure Cloud, Google Cloud Platform (GCP), or other options).

[0084] Each Al partner 24 is directly integrated with data manager 16 to provide communications to and from other components of system 10A. Data manager 16 controls communications to and receives communications from Al partners 24. Al partners 24 are not directly integrated with platform partner 26 in this example. Instead, data manager 16 provides a bridge for data transfer and communications between platform partner 26 and Al partners 24.

[0085] Platform partner 26 provides viewer 44 for viewing the electronic images and other information associated with the electronic images. Platform partner 26 has a single integration with data manager 16 to facilitate communication between platform partner 26 and data manager 16. In the example shown, platform partner 26 is disposed locally at the local facility. Platform partner 26 is not directly communicatively connected to Al partners 24. Platform partner 26 is not directly communicatively connected to a cloud computing environment in the example shown. Data manager 16 is configured to provide data communications to and from platform partner 26. Data manager 16 provides the communication link between local platform partner 26 and cloud-based Al partners 24.

[0086] Transfer management module 40 is disposed locally in the example shown. Transfer management module 40 is communicatively connected to one or more scanners 28 to receive the digital image data generated by the one or more scanners 28. Transfer management module 40 is further communicatively connected to LIS / LIMS 14. The transfer management module 40 can provide information to LIS / LIMS 14 and can retrieve information from LIS / LIMS 14.

[0087] Data distribution module 38 is deployed in cloud platform 22dm in the example shown. Data distribution module 38 forms a remote portion of transfer manager 36. Data distribution module 38 is communicatively connected with the local portion of transfer manager 36 (i.e., transfer management module 40). Data distribution module 38 is communicatively connected to one or more Al partners 24 disposed in one or more cloud platforms 22ai.

[0088] Data manager 16 provides a single integration point for the various Al partners 24. Each Al partner 24 is integrated with data manager 16 for data communications. Data manager 16 isolates the local components that generate the digital image data (e.g., scanner system 12) and local components that store sensitive patient health information (e.g., LIS / LIMS 14) from Al partners 24.

[0089] During operation, digital image data is generated by scanner system 12 and provided to data manager 16. Data manager 16 can recall information from and / or write information to LIS / LIMS 14. Data manager 16 provides a communication link between platform partner 26 and the digital image data generated by scanner system 12 and provides a communication link between platform partner 26 and information stored in LIS / LIMS 14. Data manager 16 can provide the digital image data to the platform partner 26 for the user to view on viewer 44. Data manager 16 can further recall information from LIS / LIMS 14 and provide such information to the user at viewer 44.

[0090] Data manager 16 further provides a communication link between Al partners 24 and other components of system 10A. Data manager 16 can provide data requests to Al partners 24 and can receive Al supplemental information from Al partners 24. Data manager 16 controls data communications to and from Al partners 24.

[0091] Data manager 16 provides significant advantages. Data manager 16 provides a single integration point for platform partner 26. Platform partner 26 is not required to be directly integrated with LIS / LIMS 14, scanner system 12, or Al partners 24. Instead, platform partner 26 is integrated with data manager 16 and data manager 16 provides communications between platform partner 26 and other components of system 10A. If a change in platform partner 26 occurs, then the new platform partner 26 only needs to integrate with data manager 16, a single integration, rather than having multiple individual integrations with scanner system 12, LIS / LIMS 14, and each of Al partners 24. Such a configuration allows for quick and efficient migration from one platfonn partner 26 to another. Such a configuration can thereby reduce downtime and provide more efficient migration, which allows for quick and efficient processing of the digital image data.

[0092] Data manager 16 further provides a single integration point for Al partners 24. Al partners 24 are not directly integrated with LIS / LIMS 14, scanner system 12, or platform partner 26. Data manager 16 provides improved security for sensitive information by controlling all data communications to and from Al partners 24. Each Al partner 24 is directly integrated with data manager 16 such that data manager 16 can verify the identity of Al partners 24 prior to sending data out to Al partners 24 and when receiving data back from Al partners 24. Further, Al partners 24 being communicatively isolated from LIS / LIMS 14 and from scanner system 12 prevents undesired direct access of an Al partner 24 to such systems that include sensitive health information.

[0093] Data manager 16 can limit data transmissions to Al partners 24 based on the information required by each Al partner 24. As discussed above, data manager 16 can filter the data being output to Al partner 24 based on the baseline information required by Al partner 24 to generate the Al supplemental output. Data manager 16 can provide different information to each of Al partners 24 based on the baseline information requirements of each of the various Al partners 24. As such, data manager 16 can limit data transmissions to Al partners 24 to only that information required for to generate the Al supplemental information. Limiting data transmissions to Al partners 24 based on the data requirements of Al partners 24 protects sensitive information and reduces data volume, which can provide for cost savings and more efficient communications.

[0094] System 10A maintains sensitive patient health information on premises unless such patient health information is required by Al partner 24 to generate an Al supplemental output. The platform partner 26, scanner system 12, LIS / LIMS 14, and portions of data manager 16 directly communicating with such components (e.g., transfer management module 40, data association module 42) are all disposed locally. Data manager 16 can communicate with Al partners 24 that are disposed outside of the local facility (i.e., in cloud platform 22ai). Data manager 16 can limit the patient health data that is communicated outside of the local facility to only that information required by Al partner 24 to provide an Al supplemental output. Such a configuration protects sensitive data while providing quick and secure integration of Al partners 24 to provide Al supplemental data.

[0095] Al partners 24 each being singly integrated with data manager 16 allows for quick and easy migration between different Al partners 24. Al partners 24 can quickly and easily be added to system 10A, by integration with data manager 16, or removed from system 10A, by breaking the integration with data manager 16. The user can thereby migrate between and select from multiple Al partners 24 without requiring the time consuming individual integrations between platform partner 26 and the individual Al partners 24.

[0096] FIG. 3 is a schematic block diagram of system 10B. Scanner system 12, LIS / LIMS 14, data manager 16, platform partner 26, and Al partners 24 of system 10B are shown. Transfer management module 40 and data distribution module 38 of data manager 16 arc shown. The example of system 10B shown in FIG. 3 can be referred to as a cloud controller system as the data manager 16 controls communications between cloud based platform partner 26 and cloud based Al partners 24.

[0097] System 10B shown in FIG. 3 is substantively similar to system 10A shown in FIG. 2, except platform partner 26 is deployed in a cloud platform. In the example shown, platform partner 26 is deployed in cloud platform 22dm along with data distribution module 38. It is understood that platform partner 26 and data distribution module 38 can be deployed in the same cloud platform 22dm or different cloud platforms 22dm.

[0098] Data manager 16 provides a single integration point for platform partner 26 and Al partners 24 to facilitate transmission and analysis of digital image data generated by scanner 28, such as for diagnostic purposes, image quality analysis, etc.. In the example shown, scanner 28, LIS / LIMS 14, and portions of data manager 16 are deployed locally at the local facility. Al partners 24 and platform partner 26 are disposed in cloud computing environments. In the example shown, Al partners 24 are deployed in cloud platform 22ai and platform partner 26 is disposed in cloud platform 22dm.

[0099] Data manager 16 is partially disposed locally and partially disposed in a cloud environment. In the example shown, transfer management module 40 is disposed locally and data distribution module 38 is deployed in a cloud computing environment. In the example shown, data distribution module 38 is disposed in cloud platform 22dm. As discussed above, cloud platform 22dm can be the same as or different from cloud platform 22ai. Further, Al partners 24 can be disposed in multiple and different cloud platforms 22ai (e.g., Amazon Web Services Cloud (AWS), Microsoft Azure Cloud, Google Cloud Platform (GCP), or other options).

[0100] Platform partner 26 provides viewer 44 for viewing the electronic images and other information associated with the electronic images, which viewer 44 is deployed in cloud platform 22dm. Platform partner 26 has a single integration with data manager 16 to facilitate communication between platform partner 26 and data manager 16 and between platform partner 26 and Al partners 24. Platform partner 26 is not directly communicatively connected to Al partners 24. Data manager 16 is configured to provide data communications to and from platform partner 26.

[0101] Transfer management module 40 is disposed locally in the example shown. Transfer management module 40 is communicatively connected to one or more scanners 28 to receive the digital image data generated by the one or more scanners 28. Management module 40 is further communicatively connected to LIS / LIMS 14. Transfer management module 40 can provide information to LIS / LIMS 14 and can retrieve information from LIS / LIMS 14.

[0102] Data distribution module 38 is deployed in cloud platform 22dm in the example shown. Data distribution module 38 forms a remote portion of transfer manager 36. Data distribution module 38 is communicatively connected with the local portion of transfer manager 36 (i.e., transfer management module 40). Data distribution module 38 is communicatively connected to one or more Al partners 24 disposed in one or more cloud platforms 22ai. In some examples, data distribution module 38 can be directly communicatively connected to platform partner 26.

[0103] Data manager 16 provides a single integration point for the various Al partners 24. Each Al partner 24 is integrated with data manager 16 for data communications. Data manager 16 isolates the local components that generate the digital image data (e.g., scanner system 12) and local components that store sensitive patient health information (e.g., LIS / LIMS 14) from Al partners 24.

[0104] Data manager 16 provides a communication link between Al partners 24 and other components of system 10B. Data manager 16 can provide data request to Al partners 24 and can receive Al supplemental information from Al partners 24. Data manager 16 controls data communications to and from Al partners 24. Data manager 16 controls data communications to and from platform partner 26.

[0105] In the example shown, data manager 16 can provide digital image data and / or patient health information to platform partner 26 deployed in cloud platform 22dm. Data manager 16 controlling communications to and from Al partners 24 isolates the data communications to and from platfomr partner 26 from the communications to and from Al partners 24. Data manager 16 controls distribution of data to Al partners 24 and can filter the data provided to Al partners 24 to limit transmission of sensitive data. Platform partner 26 is isolated from Al partners 24 and does not directly communicate with Al partners 24. Instead, data manager 16 performs communications with Al partners 24 and performs communications with platform partner 26.

[0106] FIG. 4 is a schematic block diagram of system IOC. Scanner system 12, LIS / LIMS 14, data manager 16, platform partner 26, and Al partners 24 of system IOC are shown. The example of system IOC shown in FIG. 4 can be referred to as a hybrid delegate system as data manager 16 controls communications to and from the local data generating and storing components (e.g., scanner system 12 and LIS / LIMS 14) and the locally deployed platform partner 26 while platform partner 26 is directly communicatively connected with cloud based Al partners 24.

[0107] System IOC shown in FIG. 4 is substantially similar to system 10A shown in FIG. 2, except that data manager 16 does not control data transmission between platform partner 26 and Al partners 24. Both transfer management module 40 and data distribution module 38 are deployed locally in the example shown. Data manager 16 controls data communications between platform partner 26 and LIS / LIMS 14. Data manager 16 controls data communications between scanner system 12 and platform partner 26.

[0108] FIG. 5 is a schematic block diagram of system 10D. Scanner system 12, LIS / LIMS 14, data manager 16, platform partner 26, and Al partners 24 of system 10D are shown. The example of system 10D shown in FIG. 5 can be referred to as a cloud delegate system as data manager 16 controls communications to and from the local data generating and storing components (e.g., scanner system 12 and LIS / LIMS 14) and the cloud deployed platform partner 26 while platform partner 26 is directly communicatively connected with the cloud deployed Al partners 24. Al partners 24 are deployed in one or more cloud platforms 22ai. Platform partner 26 is deployed in cloud platform 22pp. It is understood that cloud platform 22pp and cloud platform 22ai can be different cloud platforms or can be the same cloud platform.

[0109] System 10D shown in FIG. 5 is substantially similar to system 10B shown in FIG. 3, except that data manager 16 does not control data transmission between platform partner 26 and Al partners 24. Both transfer management module 40 and data distribution module 38 are deployed locally in the example shown. Data manager 16 controls data communications between platform partner 26 and LIS / LIMS 14. Data manager 16 controls data communications between scanner system 12 and platform partner 26.

[0110] Discussion of Possible Embodiments

[0111] The following are non-exclusive descriptions of possible embodiments of the present invention.

[0112] A system for generating and processing digital images regarding medical samples includes a scanner system configured to generate digital image data corresponding to a medical sample associated with a patient; a data manager communicatively connected to the scanner system, the data manager configured to receive the digital image data from the scanner system; and a platform partner communicatively connected to the data manager, the platform partner configured to display at least one digital image based on the digital image data, wherein the platform partner includes at least one viewer configured to display the at least one digital image. The data manager is communicatively connected to one or more artificial intelligence partners deployed in at least one cloud platform, each of the one or more artificial intelligence partners being configured to generate supplemental data, the data manger is directly communicatively connected to a laboratory information system (TIS / LIMS), and the data manager is directly communicatively connected to the platform partner. The data manager is configured to: associate the digital image data with patient health information for the patient recalled from the TIS / LIMS to generate associated digital image data; provide the associated digital image data to the viewer for displaying of the digital image by the viewer; and receive a first supplemental output regarding the medical sample generated by the first artificial intelligence partner, the first supplemental output generated based on request information that is at least partially formed by at least a portion of the digital image data, provide the first supplemental output to the platform partner for displaying by the viewer.

[0113] The system of the preceding paragraph can optionally include, additionally and / or alternatively, any one or more of the following features, configurations and / or additional components:

[0114] The platform partner is deployed on a first cloud platform.

[0115] The data manager comprises: a transfer manager directly communicatively connected to the platform partner and directly communicatively connected to the one or more of artificial intelligence partners, wherein the transfer manager is partially deployed locally and partially deployed in a first cloud platform.

[0116] The at least one viewer is deployed in the first cloud platform. The transfer manager includes a transfer management module disposed locally and the transfer manager includes a data distribution module deployed in the first cloud platform; the transfer management module is communicatively connected to a scanner manager of the scanner system to receive the digital image data; the transfer management module is configured to cause generation of the associated digital image data and is configured to provide the associated digital image data to the data distribution module; the data distribution module is configured to generate the request information and provide the request information to the first artificial intelligence partner; and the data distribution module is configured to receive the first supplemental output from the first artificial intelligence partner and provide the first supplemental output to the platform provider.

[0117] The data distribution module is configured to generate the request data by filtering the associated digital image data to remove at least a portion of the patient health information.

[0118] The data manager comprises: a data monitoring module, the data monitoring module configured to receive the digital image data from the scanner system; a transfer management module configured to receive the digital image data from the data monitoring module and communicate the digital image data to a data processing module of the data manager; wherein the data processing module is directly communicatively connected to the LIS / LIMS to receive the patient health information from the LIS / LIMS; and wherein the data processing module is configured to provide the associated digital image data to the transfer management module.

[0119] The data manager is bi-directionally connected to the LIS / LIMS such that the data manager is configured to receive the patient health information from the LIS / LIMS and the data manager is configured to write information to the LIS / LIMS.

[0120] The first supplemental output is in the form of a URL and the data manager is configured to write the URL to the LIS / LIMS.

[0121] The scanner system is configured to output the digital image data in a primary file format and a secondary file format, wherein the primary file format includes the digital image data and patient data for the patient, and wherein the secondary file format includes the digital image data and does not include the patient data.

[0122] An image association module, the image association module configured to monitor outgoing communications from the scanner manager, generate a unique identifier based on the patient data from the primary file format and based on a file identifier of the secondary file format, and provide the unique identifier to the data manager.

[0123] The data manager is configured to receive the digital image data in the secondary file format, label the digital image data received in the secondary file format with a patient identifier provided by the unique identifier to generate labeled digital image data, and generate the associated digital image data based on the labeled digital image data.

[0124] The data manager is configured to receive the supplemental data from the first artificial intelligence partner, and the data manager is configured to provide the supplemental data to the LIS / LIMS for storage in the LIS / LIMS.

[0125] The data manager includes a one or more application programming interfaces, and wherein each application programming interface of the one or more application programming interfaces is associated with an artificial intelligence partner of one or more artificial intelligence partners.

[0126] The data manager is configured to directly communicate with first artificial intelligence partner and the data manager is configured to directly communicate with the platform partner such that the platform partner is communicatively coupled to the first artificial intelligence partner via the data manager.

[0127] The platform is configured to directly communicate with first artificial intelligence partner and the data manager is configured to directly communicate with the platform partner such that the data manager is communicatively coupled to the first artificial intelligence partner via the platform partner.

[0128] The LIS / LIMS, the scanner system, and a first portion of the data manager are disposed on a local network.

[0129] The platform provider is disposed on the local network.

[0130] A second portion of the data manager is deployed in a first cloud platform, and wherein the second portion of the data manager is directly communicatively connected to the one or more of artificial intelligence partners.

[0131] A system for generating and processing digital images regarding medical samples, the system including a data manager configured to communicatively connect to a scanner system configured to generate digital image data corresponding to a medical sample associated with a patient, the data manager configured to receive the digital image data from the scanner system and configured to associate the digital image data with patient health information for the patient to generate associated digital image data, the patient health information recalled from a laboratory information database (LIS / LIMS) by the data manager; and a platform provider directly communicatively connected to the data manager, the platform provider configured to generate and display at least one digital image based on the digital image data, wherein the platform provider includes at least one viewer configured to display the at least one digital image. The data manager includes a transfer management module disposed on a local server; and a data distribution module. The data manager is configured to provide the associated digital image data to the platform provider. The platform provider is directly communicatively connected to one or more artificial intelligence partners deployed in at least one Al cloud platform, the one or more artificial intelligence partners being configured to generate supplemental data based on request data and to output the supplemental data, wherein the request data at least partially includes at least a portion of the digital image data. The data distribution module is further configured to: receive the first supplemental data generated by the first artificial intelligence partner; and transmit the first supplemental data to the transfer management module; and wherein the transfer management module is configured to write the first supplemental data to the LIS / LIMS.

[0132] The system of the preceding paragraph can optionally include, additionally and / or alternatively, any one or more of the following features, configurations and / or additional components:

[0133] A plurality of scanners configured to generate raw image data; and a scanner manager communicatively connected to the plurality of scanners, the scanner manager configured to convert the raw image data into the digital image data; wherein the data manager is directly communicatively connected to the scanner manager.

[0134] The at least one viewer is deployed in a first cloud platform.

[0135] The at least one Al cloud platform includes a plurality of Al cloud platforms. The at least one Al cloud platform is different than the first cloud platform. A method of processing digital images regarding medical samples, the method including receiving, by a data manager, digital image data generated by a scanner system, the scanner system configured to generate the digital image data based on a scan of a medial sample associated with a patient; recalling, by the data manager, patient health information for the patient from a laboratory information database (LIS / LIMS) and associating, by the data manager, the patient health information with the digital image data to generate associated digital image data; receiving, by the data manager, a supplemental request from a viewer of a platform partner directly communicatively connected to the data manager; generating, by the data manager, request data based on the supplemental request, the request data including at least a portion of the digital image data; providing the request data to at least one artificial intelligence partner deployed in a cloud platform to cause the at least one artificial intelligence partner to generate supplemental data; receiving, by the data manager, the supplemental data; and providing, by the data manager, the supplemental data to the viewer for displaying the supplemental data.

[0136] A system for generating and processing digital images regarding medical samples includes a scanner system configured to generate digital image data corresponding to a medical sample associated with a patient; a data manager communicatively connected to the scanner system, the data manager configured to receive the digital image data from the scanner system; and a platform partner communicatively connected to the data manager, the platform partner configured to display at least one digital image based on the digital image data, wherein the platform partner includes at least one viewer configured to display the at least one digital image; wherein the data manager is directly communicatively connected to one or more artificial intelligence partners deployed in at least one cloud platform, each of the one or more artificial intelligence partners being configured to generate supplemental data, the data manger is directly communicatively connected to a laboratory information system (LIS / LIMS), and the data manager is directly communicatively connected to the platform partner; and wherein the data manager is configured to: associate the digital image data with patient health information for the patient recalled from the LIS / LIMS to generate associated digital image data; provide the associated digital image data to the viewer for displaying of the digital image by the viewer; generate and provide request information to a first artificial intelligence partner of the one or more artificial intelligence partners to cause the first artificial intelligence partner to generate a first supplemental output regarding the medical sample, wherein the request information at least partially includes at least a portion of the digital image data; and receive the first supplemental output from the first artificial intelligence partner and provide the first supplemental output to the platform partner for displaying by the viewer.

[0137] A system for generating and processing digital images regarding medical samples includes a data manager communicatively connected to a scanner system configured to generate digital image data corresponding to a medical sample associated with a patient to receive the digital image data from the scanner system and configured to associate the digital image data with patient health information for the patient to generate associated digital image data, the patient health information recalled from a laboratory information database (LIS / LIMS) by the data manager; and a platform provider communicatively connected to the data manager, the platform provider configured to generate and display at least one digital image based on the digital image data, wherein the platform provider includes at least one viewer configured to display the at least one digital image. The data manager includes a transfer management module disposed on a local server; and a data distribution module disposed on a manager portal within a first cloud platform. The data manager is configured to provide the associated digital image data to the platform provider. The data distribution module is directly communicatively connected to one or more artificial intelligence partners deployed in at least one Al cloud platform, the one or more artificial intelligence partners being configured to generate supplemental data based on request data and to output the supplemental data, wherein the request data at least partially includes at least a portion of the digital image data. The data distribution module is further configured to: provide the request data to a first artificial intelligence partner of the one or more artificial intelligence partners to cause the first artificial intelligence partner to generate first supplemental data; receive the first supplemental data from the first artificial intelligence partner; and transmit the first supplemental data to the transfer management module. The transfer management module is configured to provide the first supplemental data to the platform provider for display by the viewer.

[0138] While the invention has been described with reference to an exemplary embodiment(s), it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiment(s) disclosed, but that the invention will include all embodiments falling within the scope of the present disclosure.

Claims

CLAIMS:

1. A system for generating and processing digital images regarding medical samples, the system comprising:a scanner system configured to generate digital image data corresponding to a medical sample associated with a patient;a data manager communicatively connected to the scanner system, the data manager configured to receive the digital image data from the scanner system; anda platform partner communicatively connected to the data manager, the platform partner configured to display at least one digital image based on the digital image data, wherein the platform partner includes at least one viewer configured to display the at least one digital image;wherein the data manager is communicatively connected to one or more artificial intelligence partners deployed in at least one cloud platform, each of the one or more artificial intelligence partners being configured to generate supplemental data, the data manger is directly communicatively connected to a laboratory information system (LIS / LIMS), and the data manager is directly communicatively connected to the platform partner; and wherein the data manager is configured to:associate the digital image data with patient health information for the patient recalled from the LIS / LIMS to generate associated digital image data;provide the associated digital image data to the viewer for displaying of the digital image by the viewer; andreceive a first supplemental output regarding the medical sample generated by the first artificial intelligence partner, the first supplemental output generated based on request information that is at least partially formed by at least a portion of the digital image data, provide the first supplemental output to the platform partner for displaying by the viewer.

2. The system of claim 1, wherein the platform partner is deployed on a first cloud platform.

3. The system of claim 2, wherein the data manager comprises:a transfer manager directly communicatively connected to the platform partner and directly communicatively connected to the one or more of artificial intelligence partners, wherein the transfer manager is partially deployed locally and partially deployed in a first cloud platform.

4. The system of claim 3. wherein the at least one viewer is deployed in the first cloud platform.

5. The system of any one of claims 3 and 4, wherein:the transfer manager includes a transfer management module disposed locally and the transfer manager includes a data distribution module deployed in the first cloud platform;the transfer management module is communicatively connected to a scanner manager of the scanner system to receive the digital image data; the transfer management module is configured to cause generation of the associated digital image data and is configured to provide the associated digital image data to the data distribution module; the data distribution module is configured to generate the request information and provide the request information to the first artificial intelligence partner; andthe data distribution module is configured to receive the first supplemental output from the first artificial intelligence partner and provide the first supplemental output to the platform provider.

6. The system of claim 5, wherein:the data distribution module is configured to generate the request data by filtering the associated digital image data to remove at least a portion of the patient health information.

7. The system of any one of claims 1-4, wherein the data manager comprises:a data monitoring module, the data monitoring module configured to receive the digital image data from the scanner system;a transfer management module configured to receive the digital image data from the data monitoring module and communicate the digital image data to a data processing module of the data manager;wherein the data processing module is directly communicatively connected to the LIS / LIMS to receive the patient health information from the LIS / LIMS; andwherein the data processing module is configured to provide the associated digital image data to the transfer management module.

8. The system of any one of claims 1-7, wherein the data manager is bidirectionally connected to the LIS / LIMS such that the data manager is configured to receive the patient health information from the LIS / LIMS and the data manager is configured to write information to the LIS / LIMS.

9. The system of claim 8, wherein the first supplemental output is in the form of a URL and the data manager is configured to write the URL to the LIS / LIMS.

10. The system of any one of claims 1-9, wherein:the scanner system is configured to output the digital image data in a primary file format and a secondary file format, wherein the primary file format includes the digital image data and patient data for the patient, and wherein the secondary file format includes the digital image data and does not include the patient data.

11. The system of claim 10, further comprising:an image association module, the image association module configured to monitor outgoing communications from the scanner manager, generate a unique identifier based on the patient data from the primary file format and based on a file identifier of the secondary file format, and provide the unique identifier to the data manager.

12. The system of claim 11, wherein the data manager is configured to receive the digital image data in the secondary file format, label the digital image data received in the secondary file format with a patient identifier provided by the unique identifier to generate labeled digital image data, and generate the associated digital image data based on the labeled digital image data.

13. The system of any one of claims 1-12, wherein the data manager is configured to receive the supplemental data from the first artificial intelligence partner, and the data manager is configured to provide the supplemental data to the LIS / LIMS for storage in the LIS / LIMS.

14. The system of any one of claims 1-13, wherein the data manager includes a one or more application programming interfaces, and wherein each applicationprogramming interface of the one or more application programming interfaces is associated with an artificial intelligence partner of one or more artificial intelligence partners.

15. The system of any one of claims 1-14, wherein the data manager is configured to directly communicate with first artificial intelligence partner and the data manager is configured to directly communicate with the platform partner such that the platform partner is communicatively coupled to the first artificial intelligence partner via the data manager.

16. The system of any one of claims 1-14, wherein the platform is configured to directly communicate with first artificial intelligence partner and the data manager is configured to directly communicate with the platform partner such that the data manager is communicatively coupled to the first artificial intelligence partner via the platform partner.

17. The system of claim 1, wherein the LIS / LIMS, the scanner system, and a first portion of the data manager are disposed on a local network.

18. The system of claim 17, wherein the platform provider is disposed on the local network.

19. The system of any one of claims 17 and 18, wherein a second portion of the data manager is deployed in a first cloud platform, and wherein the second portion of the data manager is directly communicatively connected to the one or more of artificial intelligence partners.

20. A system for generating and processing digital images regarding medical samples, the system comprising:a data manager configured to communicatively connect to a scanner system configured to generate digital image data corresponding to a medical sample associated with a patient, the data manager configured to receive the digital image data from the scanner system and configured to associate the digital image data with patient health information for the patient to generate associated digital image data, the patient health information recalled from a laboratory information database (LIS / LIMS) by the data manager, wherein the data manager comprises:a transfer management module disposed on a local server; anda data distribution module; anda platform provider directly communicatively connected to the data manager, the platform provider configured to generate and display at least one digital image based on the digital image data, wherein the platform provider includes at least one viewer configured to display the at least one digital image;wherein the data manager is configured to provide the associated digital image data to the platform provider;wherein the platform provider is directly communicatively connected to one or more artificial intelligence partners deployed in at least one Al cloud platform, the one or more artificial intelligence partners being configured to generate supplemental data based on request data and to output the supplemental data, wherein the request data at least partially includes at least a portion of the digital image data; wherein the data distribution module is further configured to:receive the first supplemental data generated by the first artificial intelligence partner; andtransmit the first supplemental data to the transfer management module; andwherein the transfer management module is configured to write the first supplemental data to the LIS / LIMS.

21. The system of claim 20, further comprising:a plurality of scanners configured to generate raw image data; and a scanner manager communicatively connected to the plurality of scanners, the scanner manager configured to convert the raw image data into the digital image data;wherein the data manager is directly communicatively connected to the scanner manager.

22. The system of any one of claims 20 and 21, wherein the at least one viewer is deployed in a first cloud platform.

23. The system of any one of claims 20-22, wherein the at least one Al cloud platform includes a plurality of Al cloud platforms.

24. The system of any one of claims 20-23, wherein the at least one Al cloud platform is different than the first cloud platform.

25. A method of processing digital images regarding medical samples, the method comprising:receiving, by a data manager, digital image data generated by a scanner system, the scanner system configured to generate the digital image data based on a scan of a medial sample associated with a patient; recalling, by the data manager, patient health information for the patient from a laboratory information database (LIS / LIMS) and associating, by the data manager, the patient health information with the digital image data to generate associated digital image data; receiving, by the data manager, a supplemental request from a viewer of a platform partner directly communicatively connected to the data manager;generating, by the data manager, request data based on the supplemental request, the request data including at least a portion of the digital image data;providing the request data to at least one artificial intelligence partner deployed in a cloud platform to cause the at least one artificial intelligence partner to generate supplemental data;receiving, by the data manager, the supplemental data; and providing, by the data manager, the supplemental data to the viewer for displaying the supplemental data.

26. A system for generating and processing digital images regarding medical samples, the system comprising:a scanner system configured to generate digital image data corresponding to a medical sample associated with a patient;a data manager communicatively connected to the scanner system, the data manager configured to receive the digital image data from the scanner system; anda platform partner communicatively connected to the data manager, the platform partner configured to display at least one digital image based on the digital image data, wherein the platform partner includes at least one viewer configured to display the at least one digital image;wherein the data manager is directly communicatively connected to one or more artificial intelligence partners deployed in at least one cloud platform, each of the one or more artificial intelligence partners being configured to generate supplemental data, the data manger is directly communicatively connected to a laboratory information system (LIS / LIMS), and the data manager is directly communicatively connected to the platform partner; and wherein the data manager is configured to:associate the digital image data with patient health information for the patient recalled from the LIS / LIMS to generate associated digital image data;provide the associated digital image data to the viewer for displaying of the digital image by the viewer;generate and provide request information to a first artificial intelligence partner of the one or more artificial intelligence partners to cause the first artificial intelligence partner to generate a first supplemental output regarding the medical sample, wherein the request information at least partially includes at least a portion of the digital image data; and receive the first supplemental output from the first artificial intelligence partner and provide the first supplemental output to the platform partner for displaying by the viewer.

27. A system for generating and processing digital images regarding medical samples, the system comprising:a data manager communicatively connected to a scanner system configured to generate digital image data corresponding to a medical sample associated with a patient to receive the digital image data from the scanner system and configured to associate the digital image data with patient health information for the patient to generate associated digital image data, the patient health information recalled from a laboratory information database (LIS / LIMS) by the data manager, wherein the data manager comprises:a transfer management module disposed on a local server; anda data distribution module disposed on a manager portal within a first cloud platform; and a platform provider communicatively connected to the data manager, the platform provider configured to generate and display at least one digital image based on the digital image data, wherein the platform provider includes at least one viewer configured to display the at least one digital image;wherein the data manager is configured to provide the associated digital image data to the platform provider;wherein the data distribution module is directly communicatively connected to one or more artificial intelligence partners deployed in at least one Al cloud platform, the one or more artificial intelligence partners being configured to generate supplemental data based on request data and to output the supplemental data, wherein the request data at least partially includes at least a portion of the digital image data; wherein the data distribution module is further configured to:provide the request data to a first artificial intelligence partner of the one or more artificial intelligence partners to cause the first artificial intelligence partner to generate first supplemental data;receive the first supplemental data from the first artificial intelligence partner; andtransmit the first supplemental data to the transfer management module; andwherein the transfer management module is configured to provide the first supplemental data to the platform provider for display by the viewer.

Images