Application Software

Abstract

To facilitate the expansion of the functionality of the sample measurement system. [Solution] The application software (6) is used in a system (1) which includes first control software (3) for controlling a measurement unit (2) for measuring a sample, first data management software (4) for managing first data related to the measurement unit, second control software (3) for controlling an imaging unit (2000) for imaging blood cells in a sample, and second data management software (4) for managing second data related to the imaging unit. The application software (6) includes a request unit (62) that requests the interface (5) to use first and second data, which include blood cell images and metadata indicating the classification of blood cell types, a response receiving unit (63) that receives a response corresponding to the request, and a function providing unit (61) as an extended function of the system (1) that provides a function to display a plurality of classification candidates based on the metadata, which includes a plurality of classification candidates for blood cells, based on the use of the first and second data.

Description

Technical Field

[0001] The present invention relates to application software.

Background Art

[0002] Patent Document 1 discloses a graphical user interface for displaying cell images in a smear specimen of the same subject and auxiliary information related to the classification results of the cell images in a system for measuring and analyzing a specimen.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the system described in Patent Document 1, a graphical user interface for displaying cell images in a smear specimen of the same subject and auxiliary information related to the classification results of the cell images is disclosed. When adding such a new function to expand the functions, software modification may be required. However, when the software has been certified by a certification body as a component of a medical device, it may be necessary to obtain certification again according to the software modification. Due to these circumstances, it has sometimes been impossible to easily expand the functions in the conventional specimen measurement system.

[0005] An object of the present invention is to provide a system that can easily expand the function of displaying a plurality of classification candidates of blood cells in a blood cell image of a specimen.

Means for Solving the Problems

[0006] Application software (6) according to one aspect of the present invention includes a measurement unit (2) for measuring a sample, first control software (3) for controlling the measurement unit (2), first data management software (4) for managing first data relating to the measurement unit (2) which operates based on the control by the first control software (3), an imaging unit (2000) for imaging blood cells in a sample, second control software (3) for controlling the imaging unit (2000), and second data management software for managing second data relating to the imaging unit (2000) which operates based on the control by the second control software (3). Application software (6) used in a system (1) including software (4), comprising: a request unit (62) that requests the interface (5) to use first data and second data including a blood cell image of blood cells captured in a sample and metadata indicating the classification of the cell types of blood cells; a response receiving unit (63) that receives a response corresponding to the request; and a function providing unit (61) that, as a function to extend the system (1), provides a function to display a plurality of classification candidates based on the metadata including a plurality of classification candidates for blood cells, based on the use of the first data and the second data. [Effects of the Invention]

[0007] According to the present invention, it is possible to provide a system that can easily extend the function of displaying multiple classification candidates for blood cells in a blood cell image of a specimen. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows the components of the sample measurement system according to this embodiment. [Figure 2] This is a diagram showing an example of a computer configuration. [Figure 3] This figure shows an example configuration 1 of the sample measurement system according to this embodiment. [Figure 4] This figure shows an example configuration 1 of the sample measurement system according to this embodiment. [Figure 5] This figure shows an example configuration 2 of the sample measurement system according to this embodiment. [Figure 6] This figure shows an example configuration 3 of the sample measurement system according to this embodiment. [Figure 7] This figure shows an example configuration 4 of the sample measurement system according to this embodiment. [Figure 8] This figure shows an example configuration 4 of the sample measurement system according to this embodiment. [Figure 9] This figure shows an example configuration 5 of the sample measurement system according to this embodiment. [Figure 10] This figure shows an example configuration 5 of the sample measurement system according to this embodiment. [Figure 11] This figure shows an example configuration 6 of the sample measurement system according to this embodiment. [Figure 12] This figure shows an example configuration 7 of the sample measurement system according to this embodiment. [Figure 13] This figure shows an example configuration of a sample measuring device and an imaging device. [Figure 14] This figure shows an example of the hardware configuration of a control unit. [Figure 15] This figure shows an example configuration of control software and data management software. [Figure 16] This figure shows a modified example of the control unit configuration. [Figure 17] This figure shows an example of the configuration of a measurement unit. [Figure 18] This figure shows an example configuration when the measurement unit is a blood cell analyzer. [Figure 19] This is a schematic diagram illustrating the sample aspiration unit and sample preparation unit when supplying a measurement sample to the FCM detection unit. [Figure 20] This is a schematic diagram illustrating the sample aspiration and sample preparation sections when supplying a measurement sample to the RBC / PLT detection unit. [Figure 21] This is a schematic diagram illustrating the sample aspiration unit and sample preparation unit when supplying a measurement sample to the HGB detection unit. [Figure 22] This figure shows an example of the configuration of an imaging unit. [Figure 23] This is a diagram showing an example of an interface configuration. [Figure 24] It is a flowchart showing an example of the processing flow (cooperation method) by the interface of the specimen measurement device. [Figure 25] It is a diagram showing a configuration example of the interface of the data management system. [Figure 26] It is a diagram showing an example of the data structure of the HTTP request body when updating the lot information for accuracy management. [Figure 27] It is a diagram showing an example of a request / response to a request for information regarding the specimen measurement device. [Figure 28] It is a diagram showing an example of a request / response to a request for information regarding specimen measurement. [Figure 29] It is a diagram showing an example of a request / response to a request for information regarding the maintenance of the specimen measurement device. [Figure 30] It is a diagram showing an example of a request regarding the operation of the specimen measurement device. [Figure 31] It is a diagram showing an example of a request / response to a request for information regarding the imaging device. [Figure 32] It is a diagram showing an example of a request / response to a request for information regarding imaging. [Figure 33] It is a diagram showing an example of a request / response to a request for information regarding the maintenance of the imaging device. [Figure 34] It is a diagram showing an example of a request regarding the operation of the imaging device. [Figure 35] It is a diagram showing a configuration example of a PUSH notification from the specimen measurement device to the data management system. [Figure 36] It is a diagram showing an example of an event and an example of information corresponding to the event (information to be the target of the PUSH notification). [Figure 37] It is a diagram showing a configuration example of the application. [[ID=…]] [Figure 38] It is a diagram showing a configuration example of providing the functions of the application as a web service. [Figure 39] It is a diagram showing another configuration example of providing the functions of the application as a web service. [Figure 40]This figure shows another configuration example where the functionality of an application is provided as a web service. [Figure 41] This diagram shows an example configuration of an application server that provides applications. [Figure 42] This figure shows an example configuration for providing an application in a secure communication environment. [Figure 43] This figure shows an example configuration for providing applications using MDM or MAM. [Figure 44] This diagram shows an example of a data structure when the database of an MDM / MAM system is a relational database. [Figure 45] This figure shows the results of imaging blood cells using a GUI and an example 1 of providing multiple classification candidates for blood cells. [Figure 46] This figure shows the results of imaging blood cells using a GUI and an example 2 of providing multiple classification candidates for blood cells. [Figure 47] This figure shows an example of a data structure within the data storage according to this embodiment. [Figure 48] This flowchart shows the processing flow by the software according to this embodiment. [Figure 49] This flowchart shows the detailed processing flow by the software according to this embodiment. [Figure 50] This flowchart shows a modified example of the processing flow by the software according to this embodiment. [Figure 51] This figure shows example 3 of the results of imaging blood cells using a GUI and the provision of multiple classification candidates for blood cells. [Figure 52] This figure shows example 3 of the results of imaging blood cells using a GUI and the provision of multiple classification candidates for blood cells. [Figure 53] This figure shows an example 4 of the results of imaging blood cells using a GUI and the provision of multiple classification candidates for blood cells. [Figure 54] This figure shows an example 4 of the results of imaging blood cells using a GUI and the provision of multiple classification candidates for blood cells. [Figure 55]This figure shows an example (5) of the results of imaging blood cells using a GUI and the provision of multiple classification candidates for blood cells. [Figure 56] This figure shows an example 6 of the results of imaging blood cells using a GUI and the provision of multiple classification candidates for blood cells. [Modes for carrying out the invention]

[0009] [Components of the sample measurement system] As shown in Figure 1, the sample measurement system 1 according to this embodiment includes, for example, a measurement unit 2, control software 3, data management software 4, and an interface 5 as its components. The measurement unit 2 measures a sample and acquires measurement data. The control software 3 and data management software 4 may be configured as a single unit. The sample measurement system 1 is, for example, a sample measurement device including the measurement unit 2, control software 3, data management software 4, and interface 5. In addition to the sample measurement device, the sample measurement system 1 may also include, for example, an imaging device 12 including an imaging unit 2000, control software 3, data management software 4, and interface 5, as shown in Figure 4. The imaging unit 2000 images, for example, a smear specimen in which a sample has been smeared on a glass slide. The sample measurement system 1 is, for example, a system including a sample measurement device including the measurement unit 2, control software 3, data management software 4, and interface 5, and other devices and other software. The sample measuring device is, for example, a blood cell analyzer, which obtains hematology test results by classifying and counting the blood cell components contained in the blood sample. The imaging device 12 is, for example, a blood cell imaging device, which obtains results by imaging a smear specimen obtained by spreading the blood sample on a glass slide.

[0010] Measurement unit 2 measures the sample placed in measurement unit 2 and acquires data corresponding to the measurement result. An example of measurement unit 2 is a unit that performs measurements for blood cell analysis. Measurement unit 2 operates based on control by control software 3. Measurement unit 2 provides the acquired data to data management software 4 via control software 3. Imaging unit 2000 images the smear specimen placed in imaging unit 2000 and acquires data corresponding to the imaging result. An example of imaging unit 2000 is a unit that performs imaging for blood cell analysis. Imaging unit 2000 operates based on control by control software 3. Imaging unit 2000 provides the acquired data to data management software 4 via control software 3.

[0011] The control software 3 works in conjunction with the data management software 4 to control the operation of the measurement unit 2. The control software 3 instructs the measurement unit 2 to perform measurement operations corresponding to measurement orders for the specimens placed in the measurement unit 2. The control software 3 analyzes the data acquired by the measurement unit 2 and obtains measurement data, which is the measurement result. The control software 3 also works in conjunction with the data management software 4 to control the operation of the imaging unit 2000. The control software 3 instructs the imaging unit 2000 to perform imaging operations corresponding to imaging orders for the smear specimens placed in the imaging unit 2000. The control software 3 analyzes the data acquired by the imaging unit 2000 and obtains imaging data, which is the imaging result.

[0012] The data management software 4 manages data related to the measurement unit 2. The data management software 4 has a function (e.g., UI: User interface) to provide the operator with the measurement results acquired by the control software 3. The data management software 4 has functions related to device operation, such as registering and acquiring measurement orders, and functions to provide the control software 3 with information related to measurement orders. The data management software 4 may manage the data based on a classification according to the type of data related to the measurement unit 2. For example, the data management software 4 may classify and manage the data according to the type of measurement unit 2 it is cooperating with. The type of measurement unit 2 is, for example, a unit that performs measurements for blood cell analysis. The control software 3 and the data management software 4 may be independent software. Software having equivalent functions to the control software 3 and equivalent functions to the data management software 4 may perform the control of the measurement unit 2 and the management of data related to the measurement unit 2. In addition, the data management software 4 manages data related to the imaging unit 2000. The data management software 4 has a function (e.g., UI: User interface) to provide the operator with the imaging results acquired by the control software 3. The data management software 4 has functions related to device operation, such as registering and acquiring imaging orders, and functions to provide information related to imaging orders to the control software 3. The data management software 4 may manage the data based on classification according to the type of data related to the imaging unit 2000. For example, the data management software 4 may classify and manage the data according to the type of imaging unit 2000 with which it is linked. The type of imaging unit 2000 is, for example, a unit that performs imaging for blood cell analysis. The control software 3 and the data management software 4 may be independent software. Software having equivalent functions to the control software 3 and equivalent functions to the data management software 4 may perform control of the imaging unit 2000 and management of data related to the imaging unit 2000.

[0013] The measurement unit 2 or imaging unit 2000, control software 3, and data management software 4 described above may require certification by a certification body as a medical device. Medical devices requiring certification include, for example, in vitro diagnostic medical devices. In this case, the measurement unit 2, control software 3, and data management software 4 provide functions corresponding to the intended use of the certified medical device. The intended use of the medical device is, for example, to measure a sample and provide the measurement results. If the medical device is a blood cell analyzer, for example, to measure a blood sample and provide measurement results related to blood cells (e.g., red blood cell count, white blood cell count, white blood cell classification, etc.).

[0014] The application software (hereinafter simply referred to as "application") 6 is software independent of the control software 3 and the data management software 4. Application 6 has functions that were incorporated into, for example, prior art software relating to a device for measuring a sample. Application 6 has functions that were incorporated into, for example, prior art software relating to a device for imaging a smear. That is, Application 6 has functions that are separated from the prior art software relating to a device for measuring a sample or a device for imaging a smear. Application 6 may have new functions that were not incorporated into, for example, prior art software relating to a device for measuring a sample. Application 6 may have new functions that were not incorporated into, for example, prior art software relating to a device for imaging a smear. The sample measurement system 1 according to this embodiment displays multiple classification candidates for blood cells based on metadata that includes information indicating the cell type of the blood cell image of the sample. The sample measurement system 1 may, for example, obtain information on multiple classification candidates for blood cells in the blood cell image from metadata and display the multiple classification candidates in relation to the classification probability of each of the multiple classification candidates, or display them in relation to their respective classification probabilities in descending order of classification probability. The display of multiple classification candidates for blood cells is performed by application software 6, which can be added to the sample measurement system 1. The sample measurement system 1 displays multiple classification candidates for blood cells in the blood cell image, based on the metadata described above. The display of multiple classification candidates for blood cells is performed by application software 6, which can be added to the sample measurement system 1. As described above, the sample measurement system 1 is capable of displaying multiple classification candidates for blood cells in the blood cell image while simultaneously displaying multiple classification candidates for blood cells in the blood cell image. The sample measurement system 1 can provide a function that allows for a multifaceted evaluation of the analysis results of the blood cell image by displaying not only the blood cell image in which blood cells were captured in the sample, but also multiple classification candidates for blood cells in the blood cell image.In the specimen measurement system 1 according to this embodiment, application software can be added to the system that has the function of providing, for example, the hematology test results of the specimen and the results of imaging of blood cells in the specimen (results of imaging of a specimen smear). For example, in this specimen measurement system 1, the hematology test results of the specimen acquired by the specimen measurement device 11 and the results of imaging of blood cells in the specimen acquired by the imaging device 12 (results of imaging of a specimen smear) can be displayed, so that the user can check the hematology test results and the results of imaging of blood cells (results of imaging of a specimen smear) while comparing them. By checking the hematology test results and the results of imaging of blood cells (results of imaging of a specimen smear) while comparing them, the user can, for example, evaluate the validity of the results of imaging of blood cells (results of imaging of a specimen smear) while referring to the hematology test results, or evaluate the validity of the hematology test results while referring to the results of imaging of blood cells (results of imaging of a specimen smear). Application 6 provides a function different from, for example, the function corresponding to “Intended Use” of a medical device. Examples of Application 6 include software for non-medical healthcare purposes (hereinafter referred to as "non-medical device software") and software not for healthcare purposes (hereinafter referred to as "non-health software"). Non-medical device software and non-health software are software that does not require or requires limited certification as a medical device. However, Application 6 may be an application that requires certification as a medical device.

[0015] Application 6 can be added to the sample measurement system 1. In other words, Application 6 can be added on to the sample measurement system 1. Once added to the sample measurement system 1, Application 6 becomes a component of the sample measurement system 1. Application 6 added to the sample measurement system 1 provides, for example, functions that utilize information managed by the data management software 4 (e.g., data related to the measurement unit 2, data related to the imaging unit 2000), and functions that utilize the functions of the data management software 4. The functions provided by Application 6 are, for example, functions that the data management software 4 does not have, and functions that extend the functions that the data management software 4 has. The functions provided by Application 6 are, for example, new functions that differ from the functions corresponding to the intended use as a medical device ("Intended Use"). Thus, Application 6 added to the sample measurement system 1 provides functions to extend the sample measurement system 1. In other words, it can be said that Application 6 added to the sample measurement system 1 provides functions that complement the data management software 4.

[0016] Since Application 6 is separate from the data management software 4 and the control software 3, Application 6 can be easily added to the sample measurement system 1 without modifying the data management software 4 or the control software 3. Moreover, if, for example, Application 6 is non-medical device software or non-health software that does not require certification as a medical device, there is no need to obtain certification from a certification body when adding Application 6. Similarly, there is no need to modify the data management software 4 or the control software 3 when removing Application 6 from the sample measurement system 1.

[0017] Application 6, which is separate from the data management software 4, can interact with the data management software 4 via interface 5. Interface 5 is, for example, a software interface. Interface 5 is, for example, an API (Application Programming Interface). Interface 5 allows application 6 to use information managed by the data management software 4 (for example, data related to the measurement unit 2 and imaging unit 2000, such as measurement data and imaging data), and the functions of the data management software 4. Specifically, interface 5 receives requests from application 6 and provides a response to application 6 corresponding to those requests, thereby allowing application 6 to use, for example, the data corresponding to the request or the function corresponding to the request. Requests from application 6 include, for example, requests to use data managed by the data management software 4, and requests to use the functions of the data management software 4. Responses to application 6 include, for example, the provision of data corresponding to the request and the provision of functions corresponding to the request.

[0018] Application 6 interacts with Interface 5 according to predetermined rules (hereinafter referred to as "Rule R"). Based on Rule R, Interface 5 allows Application 6 to use information and functions related to the data management software 4. If Interface 5 is configured as a Web API, for example, Rule R is defined as a combination of a URI (Uniform Resource Identifier) ​​for specifying the processing target in a predetermined syntax and a predetermined HTTP (Hyper Text Transfer Protocol) method indicating an operation on the processing target. Based on Rule R, Application 6 creates a combination of a URI and an HTTP method that specifically identifies the processing target and the operation on the processing target as a request to Interface 5. Hereinafter, this request will also be referred to as "Command C". Application 6 sends Command C, created based on Rule R, to Interface 5. Interface 5 provides Application 6 with a response corresponding to Command C sent from Application 6. For example, based on a command C sent from application 6, interface 5 allows application 6 to use at least one of the following: data related to the measurement unit 2, data related to the measurement operation of the measurement unit 2, data related to the maintenance of the measurement unit 2, and data related to the operation of the measurement unit 2. For example, based on a command C sent from application 6, interface 5 allows application 6 to use data related to the imaging unit 2000, data related to the operation of the imaging unit 2000, etc. Also, for example, based on a command C sent from application 6, interface 5 causes application 6 to perform at least one of the following: acquisition of data related to the measurement unit 2, registration of said data, updating said data, or deletion of said data. For example, there may be multiple types of rules R depending on the type of sample measuring device 11. For example, the information management format of the data management software 4 and the data management system 15 may differ depending on the type of sample measuring device 11.In such a case, for example, by having interface 5 / 5A and application 6 cooperate based on multiple types of rules R corresponding to the information management format, application 6 can utilize multiple types of information, each with a different information management format. Interface 5 causes application 6 to perform at least one of the following actions based on command C sent from application 6: acquiring data related to the imaging unit 2000, registering the data, updating the data, or deleting the data.

[0019] Interface 5 may allow multiple types of applications 6 to utilize data related to the measurement unit 2 based on rules R commonly defined for multiple types of applications 6 that provide different functions from each other. Interface 5 may allow multiple types of applications 6 to utilize data related to the measurement unit 2 based on rules R commonly defined for multiple types of applications 6 that have been created for multiple types of operating systems.

[0020] Interface 5 may be incorporated into the data management software 4, or it may be incorporated into a separate software program. Interface 5 may be software independent of the data management software 4, the control software 3, and other software programs. Furthermore, the data management software 4 may consist of one software (e.g., one executable file) or multiple software (e.g., multiple executable files). For example, the software responsible for interface 5 and the software responsible for the data management software 4 may consist of multiple different executable files.

[0021] [Examples of software operating environments] The control software 3, data management software 4, interface 5, and application 6 are executed on, for example, one or more computers 900. Computers 900 are, for example, smartphones (iPhone, Android devices), tablets (iPad, Android tablets, Windows tablets), Windows PCs with Windows OS installed, and Macs with Mac OS installed (iPhone, iPad, Android, Windows, and Mac OS are registered trademarks). Furthermore, application 6 may be created for multiple types of operating systems. For example, a single application 6 may have separate versions for Windows OS and iOS.

[0022] Figure 2 shows an example configuration of computer 900. Computer 900, as an example, includes a processor 71, memory 72, bus 73, storage unit 74, display unit 75, interface 751, operation unit 76, interface 761, and communication unit 78. The terminal device 101 and control unit 7, described later, have a similar configuration to computer 900 shown in Figure 2.

[0023] The storage unit 74 is a non-volatile memory such as an SSD (Solid State Drive), flash memory, HDD (Hard Disk Drive), or a combination thereof. The storage unit 74 stores various programs, including control software 3, data management software 4, interface 5, and application 6, as well as various data.

[0024] The processor 71 may be, for example, an IPU (Infrastructure Processing Unit), a CPU (Central Processing Unit), a GPU (Graphic Processing Unit), a DSP (Digital Signal Processor), an MPU (Micro Processing Unit), or a combination thereof. The processor 71 may also be implemented by, for example, a logic circuit. The processor 71 reads various programs from the storage unit 74, loads them into memory 72, and executes them. Memory 72 may be volatile memory such as RAM (Random Access Memory) or DRAM (Dynamic Random Access Memory).

[0025] Interface 751 connects bus 73 to display unit 75, such as a display. Interface 761 connects bus 73 to control unit 76, such as a keyboard or mouse. Communication unit 78 is responsible for communication with external devices.

[0026] In the following sections, in order to simplify the explanation of the operation of the control software 3, data management software 4, interface 5, or application 6, components corresponding to the processor 71, storage unit 74, and memory 72 for executing these may be omitted.

[0027] Furthermore, the computer 900 may be further equipped with communication interfaces for communicating with other devices. The computer 900 may also be further equipped with input / output interfaces for connecting input / output devices such as keyboards, mice, displays, and printers.

[0028] [Example of a sample measurement system configuration] [Configuration Example 1] Figure 3 shows an example configuration of the sample measurement system 1. In the example configuration shown in the figure, the sample measurement system 1 is configured as a sample measurement device 11 that includes a measurement unit 2, control software 3, data management software 4, interface 5, and a control unit 7 that executes application 6. In this example configuration, application 6 is executed on the sample measurement device 11 and utilizes the information and functions of the data management software 4 managed by the data management software 4 via interface 5. The sample measurement system 1 may also include, for example, an imaging device 12 as shown in Figure 4, in addition to the sample measurement device 11. The imaging device 12 includes, for example, an imaging unit 2000, control software 3, data management software 4, interface 5, and a control unit 7 that executes application 6.

[0029] [Configuration Example 2] Application 6 may be mounted on a device different from the sample measuring device 11 and the imaging device 12. In the example configuration shown in Figure 5, the sample measuring system 1 includes a sample measuring device 11 installed in the laboratory, an imaging device 12 installed in the laboratory, and a terminal device 101 connected to the sample measuring device 11 and the imaging device 12 via a communication network 201. The terminal device 101 is used, for example, in the laboratory. The communication network 201 is, for example, an intranet.

[0030] The sample measurement device 11 includes a measurement unit 2 and a control unit 7 that executes control software 3, data management software 4, and interface 5. The imaging device 12 includes an imaging unit 2000, control software 3, data management software 4, and a control unit 7 that executes interface 5. The terminal device 101 is a computer used by users of the sample measurement system 1, and is, for example, a PC, smartphone, or tablet. The terminal device 101 is equipped with and executes application 6.

[0031] In this configuration example, the application 6 executed on the terminal device 101 accesses the interface 5 of the sample measurement device 11 and the imaging device 12 via the communication network 201. Interface 5, via the communication network 201, allows the application 6 on the terminal device 101 to use the information managed by the data management software 4 and the functions of the data management software 4.

[0032] [Configuration Example 3] The terminal device 101, which is equipped with application 6, may be used in a location different from the facility where the sample measuring device 11 and imaging device 12 are installed (for example, outside the laboratory, or in a different room within the same facility as the laboratory). In the configuration example shown in Figure 6, the sample measuring system 1 includes a sample measuring device 11 and imaging device 12 installed in the laboratory, and a terminal device 101 used in a facility different from the laboratory and connected to the sample measuring device 11 and imaging device 12 via a communication network 202. The communication network 202 is, for example, the Internet or an intranet. The sample measuring device 11 includes a measuring unit 2, control software 3, data management software 4, and a control unit 7 that executes interface 5. The imaging device 12 includes an imaging unit 2000, control software 3, data management software 4, and a control unit 7 that executes interface 5. The terminal device 101 is equipped with application 6 and executes application 6.

[0033] In this configuration example, application 6, executed on terminal device 101, accesses interface 5 of sample measurement device 11 via communication network 202. Interface 5, via communication network 202, allows application 6 on terminal device 101 to utilize the information and functions of data management software 4. Furthermore, application 6, executed on terminal device 101, accesses interface 5 of imaging device 12 via communication network 202. Interface 5, via communication network 202, allows application 6 on terminal device 101 to utilize the information and functions of data management software 4.

[0034] [Configuration Example 4] When the sample measuring device 11 is equipped with application 6, the application 6 equipped on the sample measuring device 11 may access other sample measuring devices 11 and utilize the information managed by the data management software 4 of the other sample measuring device 11 and the functions of the data management software 4. In the example configuration shown in Figure 7, the sample measuring system 1 is configured such that sample measuring devices 11, each comprising a measurement unit 2, control software 3, data management software 4, interface 5, and a control unit 7 that executes application 6, are connected to each other via a communication network 203. The communication network 203 is, for example, an intranet or the internet. In the example configuration shown in Figure 8, the sample measuring system 1 is configured such that a sample measuring device 11 comprising a measurement unit 2, control software 3, data management software 4, interface 5, and a control unit 7 that executes application 6, and an imaging device 12 comprising an imaging unit 2000, control software 3, data management software 4, interface 5, and a control unit 7 that executes application 6, are connected to each other via a communication network 203. The communication network 203 is, for example, an intranet or the internet.

[0035] In the configuration example shown in Figure 7, an application 6 running on a sample measuring device 11 can utilize the information and functions of the data management software 4 of the sample measuring device 11 via the interface 5 of the sample measuring device 11, and can also access the interface 5 of other sample measuring devices 11 connected via the communication network 203 and utilize the information and functions of the data management software 4 of those sample measuring devices 11. Furthermore, in the configuration example shown in Figure 8, for example, an application 6 running on an imaging device 12 can utilize the information and functions of the data management software 4 of the imaging device 12 via the interface 5 of the imaging device 12, and can also access the interface 5 of a sample measuring device 11 connected via the communication network 203 and utilize the information and functions of the data management software 4 of that sample measuring device 11.

[0036] [Configuration Example 5] The information managed by the data management software 4 (e.g., measurement data) may be managed by a device different from the sample measurement device 11. In the configuration example shown in Figure 9, the sample measurement system 1 includes a sample measurement device 11 and a data management system 15 connected to the sample measurement device 11 via a communication network 204. The communication network 204 is, for example, an intranet or the internet. The information managed by the data management software 4 (e.g., measurement data) may be managed by both the sample measurement device 11 and the data management system 15. For example, a copy of all or part of the information managed by the data management software 4 of the sample measurement device 11 may be managed by the data management system 15. In the configuration example shown in Figure 10, the sample measurement system 1 includes an imaging device 12 and a data management system 15 connected to the imaging device 12 via a communication network 204. The communication network 204 is, for example, an intranet or the internet. The information managed by the data management software 4 (e.g., imaging data) may be managed by both the imaging device 12 and the data management system 15. For example, copies of all or part of the information managed by the data management software 4 of the imaging device 12 may be managed by the data management system 15.

[0037] As shown in Figure 9, the sample measurement device 11 includes a measurement unit 2, control software 3, data management software 4, interface 5, and a control unit 7 that executes application 6. The sample measurement device 11 has a function for providing information managed by the data management software 4 to the data management system 15. As will be described in detail later, as an example of this function, interface 5 may, in response to a predetermined event, provide information corresponding to that event (such as measurement data) to the data management system 15 via push notification through the communication network 204. Push notifications may also be executed by something other than interface 5 (for example, data management software 4, or other software installed on the control unit 7). Instead of push notifications, the sample measurement device 11 may provide information managed by the data management software 4 to the data management system 15 as a response to an inquiry from the data management system 15. The provision of information to the data management system 15 is the same as in configuration examples 6 and 7 described later. Also, as shown in Figure 10, the imaging device 12 includes an imaging unit 2000, control software 3, data management software 4, interface 5, and a control unit 7 that executes application 6. The imaging device 12 has a function for providing information managed by the data management software 4 to the data management system 15. As will be described in detail later, as an example of this function, the interface 5 may, in response to a predetermined event, provide information corresponding to that event (such as measurement data) to the data management system 15 via push notification through the communication network 204. Push notifications may also be executed by something other than the interface 5 (for example, the data management software 4, or other software installed on the control unit 7). Similar to the sample measurement device 11, the imaging device 12 may, instead of push notifications, provide information managed by the data management software 4 to the data management system 15 as a response to an inquiry from the data management system 15.

[0038] As shown in Figure 9, the data management system 15 includes, for example, data management software 4A, interface 5A, and a control unit 17 that executes the communication control unit 16. The control unit 17 is equivalent to the processor 902 shown in Figure 2. The data management system 15 includes a data storage device 18, which is a memory device. The data management software 4A stores and manages information pushed from the sample measuring device 11 in the data storage device 18. The communication control unit 16 has the function of controlling communication related to push notifications from the sample measuring device 11. Alternatively, as shown in Figure 10, the data management software 4A may also store and manage information pushed from the imaging device 12 in the data storage device 18. The communication control unit 16 has the function of controlling communication related to push notifications from the imaging device 12.

[0039] As shown in Figure 9, application 6 can communicate with data management software 4A via interface 5A. Data management software 4A retrieves data from data storage 18 corresponding to requests from application 6 received by interface 5A and provides it to the requesting application 6. Interface 5A has the function of allowing application 6, which is executed on the sample measurement device 11, to use information managed by data storage 18 via data management software 4A. Interface 5A is equivalent to interface 5, for example, a software interface, and a typical example is an API. Interface 5A allows application 6 to use information managed by data management software 4A. Application 6 communicates with interface 5A based on rule R, and interface 5A allows application 6 to use information and functions related to data management software 4A based on rule R. Also, as shown in Figure 10, interface 5A has the function of allowing application 6, which is executed on the imaging device 12, to use information managed by data storage 18 via data management software 4A. Interface 5A is equivalent to interface 5, for example, a software interface, and a typical example is an API. Interface 5A allows Application 6 to use information managed by data management software 4A. Application 6 interacts with Interface 5A based on Rule R, and Interface 5A, based on Rule R, allows Application 6 to use information and functions related to data management software 4A.

[0040] In this configuration example, as shown in Figure 9, the application 6 executed on the sample measuring device 11 accesses the interface 5A of the data management system 15 via the communication network 204 and requests the use of information stored in the data storage 18 of the data management system 15. The data management system 15 may be installed in a laboratory or medical facility, in which case the application 6 of the sample measuring device 11 accesses the interface 5A via the communication network 204, for example, as an intranet. Also, as shown in Figure 10, the application 6 executed on the imaging device 12 accesses the interface 5A of the data management system 15 via the communication network 204 and requests the use of information stored in the data storage 18 of the data management system 15. The data management system 15 may be installed in a laboratory or medical facility, in which case the application 6 of the imaging device 12 accesses the interface 5A via the communication network 204, for example, as an intranet.

[0041] [Configuration Example 6] The information stored in the data storage 18 of the data management system 15 may be used by the application 6 executed on the terminal device 101. In the example configuration shown in Figure 11, the sample measurement system 1 consists of a sample measurement device 11, an imaging device 12, a data management system 15, and a terminal device 101, all connected via a communication network 204.

[0042] In this configuration example, application 6, which runs on terminal device 101, accesses interface 5A of data management system 15 via communication network 204 and requests the use of information stored in data storage 18 of data management system 15. Application 6, which runs on terminal device 101, interacts with interface 5A based on rule R.

[0043] [Configuration Example 7] As a variation of Configuration Example 6, the sample measuring device 11 and the imaging device 12 do not need to be equipped with data management software 4 and interface 5. The configuration example shown in Figure 12 is the same as Configuration Example 6, except that the sample measuring device 11 and the imaging device 12 do not have data management software 4 and interface 5.

[0044] In this configuration example, information such as measurement data acquired by the control software 3 controlling the measurement unit 2 is transmitted to the data management system 15 via the communication network 204, and is stored in the data storage 18 via the data management software 4A of the data management system 15. Similarly, information such as imaging data acquired by the control software 3 controlling the imaging unit 2000 is transmitted to the data management system 15 via the communication network 204, and is stored in the data storage 18 via the data management software 4A of the data management system 15. The application 6 executed on the terminal device 101 accesses the interface 5A of the data management system 15 via the communication network 204, similar to configuration example 6, and requests the use of information stored in the data storage 18 of the data management system 15.

[0045] [Example configuration of sample measuring device and imaging device] As described above, the sample measuring device 11 includes, for example, a control unit 7 and a measuring unit 2, as shown in Figure 13. The imaging device 12 also includes, for example, a control unit 7 and an imaging unit 2000, as shown in Figure 13.

[0046] [Control Unit] The control unit 7 for the sample measuring device 11 and the imaging device 12 is, for example, a computer. An example of the hardware configuration of the control unit 7 is shown in Figure 14. The control unit 7 includes, as an example, a processor 71, memory 72, bus 73, storage unit 74, display unit 75, interface 751, operation unit 76, interface 761, interface 77, and communication unit 78. In Figure 14, an example is shown in which the measuring unit 2 and the control unit 7 are connected via interface 77, but the imaging unit 2000 and the control unit 7 may also be connected via interface 77.

[0047] The processor 71 is a control unit that comprehensively controls the functions of the control unit 7. The processor 71 is equivalent to the processor 71 shown in Figure 2. The processor 71 reads, for example, the control software 3 and the data management software 4 from the storage unit 74, loads them into the memory 72, and executes them. The storage unit 74 is equivalent to the storage unit 74 shown in Figure 2. The memory 72 is equivalent to the memory 72 shown in Figure 2.

[0048] Interface 751 connects bus 73 to display unit 75, such as a display. Interface 761 connects bus 73 to operation unit 76, such as a keyboard or mouse. Interface 77 connects bus 73 to measurement unit 2. Communication unit 78 is responsible for communication with external devices.

[0049] [Example configuration of control software and data management software] Figure 15 shows an example configuration of the control software 3 and data management software 4 executed in the control unit 7. The control software 3 includes, for example, a unit control unit 31 and an analysis unit 32. The unit control unit 31 of the control unit 7 connected to the measurement unit 2 commands the measurement unit 2 to perform an action corresponding to the measurement order of the sample to be measured. The unit control unit 31 of the control unit 7 connected to the imaging unit 2000 commands the imaging unit 2000 to perform an action corresponding to the imaging order of the sample to be imaged. The analysis unit 32 of the control unit 7 connected to the measurement unit 2 analyzes the data acquired by the measurement unit 2, which has operated according to the commands of the unit control unit 31, generates measurement data as a measurement result, and stores the generated measurement data in the storage unit 74. The analysis unit 32 of the control unit 7 connected to the imaging unit 2000 analyzes the imaging data captured by the imaging unit 2000, generates a classification result of the cells contained in the imaging data, and stores the classification result and imaging data in the storage unit 74. Furthermore, the control software 3 of the control unit 7 connected to the imaging unit 2000 does not necessarily have to include an analysis unit 32. In this case, the control software 3 acquires imaging data captured by the imaging unit 2000 from the imaging unit 2000 and stores the acquired imaging data in the storage unit 74.

[0050] The data management software 4 includes, for example, a results provision unit 41 and an operation unit 42. The results provision unit 41 has the function of acquiring measurement data generated by the analysis unit 32 from the storage unit 74 and providing the acquired measurement data to the operator (e.g., GUI: Graphical User Interface). The operation unit 42 has operational functions such as a function (UI) for the operator to register measurement orders / sample information, a function to acquire measurement orders and sample information from a clinical laboratory information system (LIS) and / or a hospital information system (HIS), a function to register measurement instructions based on measurement orders, various setting functions for the device and system, and registration of reagent information and consumable information. The information set and registered by the operation unit 42 is stored in the storage unit 74. The operational functions provided by the data management software 4 are, for example, the functions required for the intended use of the sample measuring device 11 approved as a medical device (e.g., the minimum functions required to measure a sample and provide measurement results specified for the intended use). The operational functions of the data management software 4 include, for example, the functions required for the intended use of the specimen measuring device 11 approved as a medical device, and additional functions to enhance user convenience. The operational functions of the data management software 4 can be expanded, for example, by adding applications 6. The operational functions of the data management software 4 may also include, for example, the functions required for the intended use of the imaging device 12 approved as a medical device (e.g., the minimum functions required to image smear specimens and provide imaging results specified for the intended use), and additional functions to enhance user convenience. The operational functions of the data management software 4 can be expanded, for example, by adding applications 6.

[0051] As a variation, as shown in Figure 16, the control unit 7 of the sample measuring device 11 does not need to include data management software 4. The control unit 7 illustrated in Figure 16 is used, for example, in the system illustrated in Figure 12. In this example, the unit control unit 31 instructs the measurement unit 2 to perform an operation corresponding to a measurement order obtained from the LIS / HIS. The analysis unit 32 analyzes the data acquired by the measurement unit 2, which operated according to the instructions of the unit control unit 31, generates measurement data as a measurement result, and transmits the generated measurement data to the data management system 15, for example via the communication unit 78. The control unit 7 of the imaging device 12 does not need to include data management software 4. In this case, the unit control unit 31 instructs the imaging unit 2000 to perform an operation corresponding to an imaging order obtained from the LIS / HIS. The analysis unit 32 may analyze the data acquired by the imaging unit 2000, which operated according to the instructions of the unit control unit 31, generate imaging data as an imaging result, and transmit the generated imaging data to the data management system 15.

[0052] The sample measuring device 11 according to this embodiment measures the sample that is introduced and acquires data corresponding to the measurement result. The sample measuring device 11 is, for example, a device that performs measurements for blood cell analysis (e.g., CBC: Complete Blood Count). The sample measuring device 11 may be configured as an integrated unit of multiple types of devices, for example, an automated analyzer in which a device that performs measurements for blood cell analysis and a device that performs measurements for C-reactive protein (CRP) analysis are configured as an integrated unit.

[0053] The imaging device 12 according to this embodiment images a smear of a sample that has been introduced and acquires data corresponding to the imaging results. The imaging device 12 is, for example, a device that images blood cells on a smear. The imaging device 12 may be composed of multiple types of devices integrated together, for example, a device in which a smear preparation device that prepares a smear by spreading a blood sample on a glass slide and the imaging device are integrated together.

[0054] The specimen measuring device 11 and imaging device 12 described above may, for example, require certification by a certification body as medical devices. Medical devices requiring certification include, for example, in vitro diagnostic medical devices. The specimen measuring device 11 provides functions corresponding to the intended use of a certified medical device. The intended use of a medical device is, for example, to measure a specimen and provide the measurement results. If the medical device is a blood cell analyzer, for example, to measure a subject's specimen and provide measurement data related to blood cells (e.g., red blood cell count, white blood cell count, white blood cell classification, etc.). The imaging device 12 provides functions corresponding to the intended use of a certified medical device. The intended use of a medical device is, for example, to image a smear specimen and provide the imaging results. If the medical device is a blood cell imaging device, for example, it would image a blood smear and provide morphological data about the blood cells (e.g., classification of band neutrophils, segmented neutrophils, eosinophils, basophils, etc.).

[0055] A system for displaying the hematology test results of a specimen and the results of imaging blood cells in the specimen (results of imaging a specimen smear) may, for example, associate each of the hematology test results and the blood cell imaging results with identification information related to the specimen (e.g., specimen ID). In this case, the hematology test results and blood cell imaging results associated with the same identification information related to the specimen can be displayed.

[0056] Blood tests measure red blood cell count, white blood cell count, platelet count, hemoglobin concentration, and hematocrit value. These tests are called hematology tests (blood cell count tests) and are used to diagnose health conditions and as screening tests to check the state of disease recovery. Furthermore, hematology tests often use automated blood cell analyzers, which employ the flow cytometry method described later. By obtaining information optically, it is possible to classify and count each cellular component contained in the blood sample.

[0057] If a blood disorder is suspected based on the results of a hematology test, in addition to the hematology test, it is necessary to prepare a blood smear from a blood sample taken from the subject and observe the morphology of blood cells to check for morphological abnormalities in the blood cells. The blood smear can be imaged using a blood cell imaging device such as imaging device 12, and each of the multiple blood cell images captured can be classified according to the attributes of the blood cells (e.g., cell type) to identify abnormal cells.

[0058] In this embodiment, the system includes a sample measuring device 11 and an imaging device 12, but it is sufficient to obtain at least the result of imaging a smear specimen from the imaging device 12, and the sample measuring device 11 does not necessarily have to be included in the system.

[0059] [Example of GUI configuration] In the configuration shown in Figure 11, the application software of the terminal device 101 displays the data collected by the data management software of the data management system 15 on a display unit provided on the terminal device 101. Figure 45 shows an example of a GUI (Graphical User Interface) that displays data associated with the identification information (sample ID) A4 related to the sample for each of the blood cell image A1 and the multiple classification candidates A111 of blood cells in a specific blood cell image A11. In Figure 45, display areas are provided for multiple blood cell images A1 and multiple classification candidates A111 of blood cells in a specific blood cell image A11. The multiple classification candidates A111 of blood cells, for example, the multiple classification candidates A111 of blood cells in a specific blood cell image A11 (e.g., BL (blast cell), BA (basophil), VLY (reactive lymphocyte)) are displayed on the GUI. As shown in Figure 45, by displaying multiple blood cell images A1 and explicitly showing multiple classification candidates A111 for blood cells in a specific blood cell image A11, it is possible to prevent oversights compared to when only a single classification candidate is displayed, and to evaluate the analysis results of blood cell images from multiple perspectives. In this GUI, multiple classification candidates A111 may also be displayed in association with the classification probability of each of the multiple classification candidates A111 (e.g., BL: 97.8%, BA: 89.8%, VLY: 84.3%), and various display formats can be applied from the standpoint of visibility. Furthermore, in this GUI, multiple classification candidates A111 for blood cells in each of the multiple blood cell images A1 may also be displayed. For example, multiple blood cell images A1 classified by specific cell types (e.g., BL (blast cells), BA (basophils), VLY (reactive lymphocytes) in Figure 45) may each be displayed as an enlarged image similar to the specific blood cell image A11, and multiple classification candidates may be displayed. In this case, various display formats can also be applied from the standpoint of visibility. In Figure 45, multiple blood cell images A1 are displayed, classified by attribute (for example, BL (blast cells), MY (myelocytes)). A number of blood cell images, ranging from a few to several hundred, may be displayed. The displayed blood cell images may be individual images of captured blood cells, or images generated by stitching together multiple blood cell images.

[0060] [Measurement Unit] Figure 17 shows an example of the configuration of the measurement unit 2. The measurement unit 2 includes, as an example, a sample processing unit 21 and a detection unit 22. The sample processing unit 21 prepares a measurement sample based on the sample and reagent. The detection unit 22 measures the measurement sample prepared by the sample processing unit 21. The unit control unit 31 of the control software 3 controls the operation of the sample processing unit 21 and the detection unit 22 in cooperation with the operation unit 42 of the data management software 4 (according to instructions from the operation unit 42). The unit control unit 31 controls the operation of the mechanisms and fluid circuits that constitute the sample processing unit 21 and the detection unit 22, for example. This operation control may include, for example, control of the aspiration operation of a liquid containing at least one of the sample and reagent, control of mixing the sample and reagent to prepare a measurement sample, control of causing the detection unit 22 to detect the measurement sample, and control of detecting at least one of optical information and electrical signals related to the measurement sample by the detection unit 22 and analyzing the measurement result based on the detected detection result.

[0061] [Hematology analyzer] Figure 18 shows an example configuration when the measurement unit 2 is a blood cell analyzer. In this case, the sample processing unit 21 includes, for example, a sample aspiration unit 211 and a sample preparation unit 212, and the detection unit 22 includes, for example, an FCM detection unit 221, an RBC / PLT detection unit 222, and an HGB detection unit 223.

[0062] Figure 19 is a schematic diagram illustrating the sample aspiration unit 211 and sample preparation unit 212 when supplying a measurement sample to the FCM detection unit 221. The sample aspiration unit 211 includes a nozzle 2111 for aspirating a blood sample (whole blood) from a blood collection tube T, and a pump 2112 for applying negative / positive pressure to the nozzle. The nozzle 2111 is inserted into the blood collection tube T by being moved up and down by a device mechanism (not shown). When the pump 2112 applies negative pressure with the nozzle 2111 inserted into the blood collection tube T, the blood sample is aspirated through the nozzle 2111. The device mechanism may also include a hand member for inverting and agitating the blood collection tube T before aspirating blood from the blood collection tube T.

[0063] The sample preparation unit 212 is equipped with five reaction chambers 212a to 212e. Each reaction chamber 212a to 212e is used in the DIFF, RET, WPC, PLT-F, and WNR measurement channels (also called measurement systems). Each reaction chamber is connected via a flow path to a hemolytic agent container containing a hemolytic agent, which is the reagent corresponding to the measurement channel, and a staining solution container containing a staining solution. A measurement channel is composed of one reaction chamber and the reagents (hemolytic agent and staining solution) connected to it. For example, the DIFF measurement channel corresponds to a measurement item that classifies leukocytes into multiple subgroups (5-part leukocyte classification), and is composed of DIFF hemolytic agent and DIFF staining solution, which are reagents for DIFF measurement, and a DIFF reaction chamber. The RET measurement channel corresponds to the measurement parameters related to reticulocytes, the WPC measurement channel corresponds to the measurement parameters related to abnormal white blood cells, the PLT-F measurement channel corresponds to the measurement parameters related to the optical measurement of platelets, and the WNR measurement channel corresponds to the measurement parameters related to white blood cells and nucleated red blood cells. These measurement channels are configured in the same way as the DIFF measurement channel.

[0064] The nozzle 2111, which has aspirated the blood sample, moves horizontally and vertically by the device mechanism to access from above the reaction chamber 212a to 212e corresponding to the measurement channel corresponding to the order, and discharges the aspirated blood sample. The sample preparation unit 212 supplies the corresponding hemolytic agent and staining solution to the reaction chamber from which the blood sample was discharged, and prepares the measurement sample by mixing the blood sample, hemolytic agent, and staining solution in the reaction chamber. The prepared measurement sample is supplied from the reaction chamber to the FCM detection unit 221 via the flow path, and cell measurement is performed by flow cytometry.

[0065] Figure 20 is a schematic diagram illustrating the sample aspiration unit 211 and sample preparation unit 212 when supplying a measurement sample to the RBC / PLT detection unit 222. The sample aspiration unit 211 is the same as the sample aspiration unit 211 shown in Figure 17. The sample preparation unit 212 includes a reaction chamber 212f. The reaction chamber 212f is connected via a flow path to a diluent container containing a diluent corresponding to RBC / PLT. The measurement sample is prepared by mixing the blood sample and the diluent in the reaction chamber 212f. The prepared measurement sample is supplied from the reaction chamber to the RBC / PLT detection unit 222 via the flow path.

[0066] Figure 21 is a schematic diagram illustrating the sample aspiration unit 211 and sample preparation unit 212 when supplying a measurement sample to the HGB detection unit 223. The sample aspiration unit 211 is the same as the sample aspiration unit 211 shown in Figure 17. The sample preparation unit 212 includes a reaction chamber 212g. The reaction chamber 212g is connected via a flow path to a hemolytic agent container containing a hemolytic agent, which is a reagent corresponding to HGB. The measurement sample is prepared by mixing the blood sample and the hemolytic agent in the reaction chamber 212g. The prepared measurement sample is supplied from the reaction chamber to the HGB detection unit 223 via the flow path.

[0067] [Imaging device] Figure 22 shows an example configuration of the imaging unit 2000 of the imaging device 12 shown in Figure 13. As shown in Figure 22, the imaging unit 2000 includes, for example, an imaging unit 121, a transfer unit 122, a transport unit 123, and an oil application unit 124. The imaging unit 2000 supplies immersion oil to the smear surface of the smear specimen 120 transported from the transport unit 123, and images the smear specimen 120 using an objective lens provided in the imaging unit 121. The imaging unit 2000, for example, detects the position of each of the multiple cells in the smear specimen 120, adds immersion oil to the smear specimen 120, and acquires a blood cell image of the smear specimen 120 by magnifying and imaging each of the multiple cells contained in the smear specimen. The imaging unit 2000 may also acquire a wide-area image of the smear specimen by imaging an image of a predetermined area. The imaging unit 2000 may, for example, acquire metadata from the blood cell image and classify the cells contained in the blood cell image based on the metadata. Metadata includes, for example, flag information suggesting that cells in the blood cell image are abnormal cells, and information indicating the attributes of the cells in the blood cell image (e.g., cell classification type). Classification of blood cell images may be performed automatically by the imaging device 12 shown in Figure 13, or it may be performed automatically or manually by an application. The imaging device 12 is equipped with a control unit 7, which may, for example, acquire data and communicate with a data management system. The imaging device 12 may also be connected to a smear preparation device and may perform the process from preparing a smear to classifying multiple blood cell images automatically.

[0068] A blood smear is a specimen that has been stained with bright-field staining, such as May-Giemsa staining. The specimen is not restricted as long as the morphology of each of the multiple blood cells can be observed, for example, a blood smear prepared from peripheral blood.

[0069] [Example of interface configuration] Interface 5 receives requests from application 6, cooperates with data management software 4 (results provision unit 41 and operation unit 42), and provides a response to application 6 corresponding to the request. Figure 23 shows an example configuration of interface 5. Interface 5 includes, as an example, a request receiving unit 51, a cooperation unit 52, and a response unit 53. The request receiving unit 51 receives requests from application 6. The request receiving unit 51 analyzes the content of the request based on rule R, and based on the analyzed request, instructs the cooperation unit 52 to cooperate with data management software 4 to obtain a response to the request. The cooperation unit 52 cooperates with data management software 4 according to the instruction and obtains a response corresponding to the request. The response unit 53 provides the response obtained by the cooperation unit 52 to application 6.

[0070] Figure 24 is a flowchart illustrating an example of the processing flow (cooperation method) by the interface 5 of the sample measuring device 11. First, the interface 5 awaits a request from the application 6 (S1). Upon receiving a request from the application 6 (Yes in S1), the interface 5 analyzes the content of the request based on rule R (S2). The interface 5 instructs the data management software 4 to perform the processing corresponding to the analyzed request (S3). The data management software 4 executes the processing according to the instruction. For example, if the result provision unit 41 of the data management software 4 receives a request from the application 6 for information regarding measurement results (e.g., measurement data measured by the measurement unit 2 of a specific sample measuring device 11, measurement results of quality control substances for a period specified in the request (e.g., daily, weekly, or monthly periods)), it identifies the data corresponding to the request and provides that information to the application 6 via the interface 5. The operation unit 42 of the data management software 4, for example, registers a measurement order in response to a request from the application 6 to register a measurement order and provides the application 6 with a response via the interface 5 indicating that the registration is complete. Interface 5 returns a response to application 6 (S4) in response to the processing performed by data management software 4. This allows application 6 to utilize the data and functions corresponding to the request.

[0071] Figure 25 shows an example configuration of interface 5A of the data management system 15. Interface 5A includes, as an example, a request receiving unit 51A, a cooperation unit 52A, and a response unit 53A. The request receiving unit 51A receives requests from application 6 via the communication network 204. The request receiving unit 51A analyzes the content of the request and, based on the analyzed request, instructs the cooperation unit 52A to cooperate with the data management software 4A to obtain a response to the request. The cooperation unit 52A cooperates with the data management software 4A in accordance with the instruction and obtains a response corresponding to the request. The response unit 53A provides the response obtained by the cooperation unit 52A to application 6 via the communication network 204.

[0072] When interfaces 5 and 5A are configured as Web APIs, application 6 accesses interfaces 5 and 5A using the URI defined by rule R. An example of the syntax of the URI defined by rule R is shown in Equation 1.

[0073] http: / / [server address] / [interface ID] / [device ID]{ / [resource] / [query parameters]}...(Equation 1)

[0074] In Equation 1, the "server address" is the communication address corresponding to interfaces 5 and 5A. The server address is specified, for example, by an IP address and a port number.

[0075] Interfaces 5 and 5A may be configured, for example, according to the types of sample measuring device 11 and imaging device 12. In this case, the "interface ID" in Equation 1 is specified to identify interfaces 5 and 5A. The interface ID is, for example, an ID corresponding to the types of sample measuring device 11 and imaging device 12. Specifying the "interface ID" in Equation 1 is not mandatory; if it is not specified, a wildcard (space, *, etc.) may be used. The interface ID corresponds, for example, to the type of rule R. For example, there are multiple types of rule R depending on the types of sample measuring device 11 and imaging device. In other words, the interface ID corresponds, for example, to the type of sample measuring device 11 and the type of imaging device, respectively. For example, the information management style of the data management software 4 and the data management system 15 may differ depending on the type of sample measuring device 11. In such a case, for example, by having interface 5 / 5A and application 6 cooperate based on multiple types of rule R corresponding to the information management style, application 6 can utilize multiple types of information, each with a different information management style.

[0076] In Equation 1, "Device ID" is the ID of the sample measuring device 11 and imaging device 12 that will be used for the information and functions. The Device ID is, for example, the serial number of the sample measuring device 11. Specifying the "Device ID" in Equation 1 is not mandatory; if it is not specified, a wildcard (space, *, etc.) may be used.

[0077] In Equation 1, "resource" refers to the resource of the API endpoint. This resource is, for example, a directory in the database corresponding to the information to be used.

[0078] In Equation 1, the "query parameter" is a query used to uniquely identify data and control objects when multiple data and control objects exist on a resource. For example, it is used to identify measurement data from among multiple measurement data that meet the conditions specified by the query parameter (specific period, specific sample, measurement data where a measurement anomaly occurred). Specifying the "resource" in Equation 1 is not mandatory; if it is not specified, a wildcard (blank, *, etc.) can be used. The format for specifying the "resource" and "query parameter" may differ depending on the type of sample measuring device 11. For example, when acquiring "measurement data," the format for specifying the "resource" and / or "query parameter" for acquiring "measurement data" from a blood cell analyzer may differ from the format for specifying the "resource" and / or "query parameter" for acquiring "measurement data" from an immunoassay analyzer. Even for the same type of information, such as "measurement data," the resource as an API endpoint may differ depending on the type of sample measuring device 11, or specific query parameters may be required for each type of sample measuring device 11. In such cases, the format for specifying "resources" and "query parameters" may differ, for example, depending on the type of sample measuring device 11 and the type of imaging device 12. Since the format for specifying "resources" and "query parameters" is part of Rule R, in other words, "resources" and / or "query parameters" may be set based on multiple types of Rule R depending on the type of sample measuring device 11.

[0079] Operations on a resource specified by a URI are identified, for example, by an HTTP method. Examples of HTTP methods include "GET," "PUT," "DELETE," and "POST." Using "GET" retrieves the information specified by the "resource" and "query parameters" in the URI.

[0080] The "PUT" operation updates or edits the information specified by the "resource" and "query parameters" in the URI. In this case, the HTTP request body includes the new data (the content of the resource to be updated or edited). Figure 26 shows an example of the data structure of the HTTP request body when updating lot information for quality control. This example is written in JSON (JavaScript Object Notation) format (JavaScript is a registered trademark). For example, the URI = "http: / / 127.0.0.1:8080 / qcdata / qcLotsInfo?lotNumber=QC22421101" specifies the "server address" = "127.0.0.1" of the control unit 7 that is the target of the "PUT" operation (update). The QC (Quality Control) data held by the control unit 7 at "server address" = "127.0.0.1" is specified by "resource" = "qcdata". A "PUT" operation (update) is specified for the QC lot information with the "query parameter" = "QC22421101" (QC lot number) among the QC data held by control unit 7 with "server address" = "127.0.0.1". The HTTP request body = "{"Limits":[{"parameter":"WBC","lowerLimit":10.0,"upperLimit":100.0},{"parameter":"RBC","lowerLimit":20.0,"upperLimit":200.0},{"parameter":"HGB","lowerLimit":30.0,"upperLimit":300.0},]}" specifies the target and content of the "PUT" operation (update) for the specified QC lot information. This combination of URI and HTTP request body updates the specified QC lot information to: WBC (white blood cell count) lower limit = 10.0 / upper limit = 100.0, RBC (red blood cell count) lower limit = 20.0 / upper limit = 200.0, and HGB (hemoglobin concentration) lower limit = 30.0 / upper limit = 300.0.Here, by updating the lower and upper limits for WBC (white blood cell count), RBC (red blood cell count), and HGB (hemoglobin concentration), quality control (QC) can be performed using the updated lower and upper limits. These lower and upper limits are also called control values ​​and are set to guarantee the accuracy of the measurement results and to prove the validity of the measurement method and its control method from the record of the measurement results. Furthermore, if the measurement result falls outside the lower or upper limit, it is also used as an indicator that the measurement result is abnormal or that the measurement was not performed correctly.

[0081] Using "DELETE" deletes the information specified in the "resource" and "query parameters" of the URI.

[0082] When registering or creating new information, use "POST" without specifying "Resource" and "Query Parameters." In this case, include the new data (the content of the resource to be registered or created) in the HTTP request body.

[0083] The request receiving unit 51 of interface 5 receives, for example, a URI and HTTP method from application 6. The cooperation unit 52 of interface 5 cooperates with the data management software 4 based on, for example, the URI and HTTP method received by the request receiving unit 51. For example, the cooperation unit 52 cooperates with the result provision unit 41 to obtain the corresponding measurement result in response to a request to acquire measurement results from the sample measuring device 11 specified by the "device ID" in the URI (HTTP method "GET"). The response unit 53 of interface 5 sends a response to application 6 corresponding to the received URI and HTTP method.

[0084] Similarly, the request receiving unit 51A of interface 5A receives, for example, a URI and HTTP method from application 6. The coordination unit 52A of interface 5A coordinates with the data management software 4A based, for example, the URI and HTTP method received by the request receiving unit 51A. For example, the coordination unit 52A coordinates with the data management software 4A in response to a request to acquire measurement results from the sample measuring device 11 specified by the "device ID" in the URI (HTTP method "GET") and acquires the corresponding measurement results. The response unit 53A of interface 5A sends a response to application 6 corresponding to the received URI and HTTP method.

[0085] Examples of requests and responses to interfaces 5 and 5A of the sample measuring device 11 are shown in Figures 27 to 30. Figure 27 shows an example of a request / response regarding information about the sample measuring device 11. Figure 27 shows examples of (1) requests and responses to information specific to the sample measuring device 11 or the system including the sample measuring device 11, (2) requests and responses regarding information about the status of the sample measuring device 11, and (3) requests and responses regarding information about the operation of the sample measuring device 11. Examples of various types of information corresponding to requests and responses are shown in the table in Figure 27, but the types of information corresponding to requests and responses are not limited to those shown in the table. Interface 5 can provide information about multiple sample measuring devices 11 (e.g., serial numbers of multiple sample measuring devices 11 installed in a laboratory, error status of multiple sample measuring devices 11 installed in a laboratory, etc.) to application 6 all at once. Figure 28 shows an example of a request / response regarding information about sample measurement. Figure 28 shows examples of (1) requests and responses regarding information on measurement results, (2) requests and responses regarding quality control measurements, and (3) requests and responses regarding measurement orders. Examples of various types of information corresponding to requests and responses are shown in the table in Figure 28, but the types of information corresponding to requests and responses are not limited to those shown in the table. Interface 5 can provide application 6 with information on multiple sample measuring devices 11 (for example, the results of multiple sample measuring devices 11 installed in a laboratory measuring samples over a predetermined period, the results of multiple sample measuring devices 11 installed in a laboratory measuring quality control samples over a predetermined period, etc.) all at once. Figure 29 shows examples of requests and responses regarding information on the maintenance of the sample measuring device 11. Figure 29 shows examples of (1) requests and responses regarding information on reagents, and (2) requests and responses regarding maintenance. Examples of various types of information corresponding to requests and responses are shown in the table in Figure 29, but the types of information corresponding to requests and responses are not limited to those shown in the table. The "consumables" listed in Figure 29 include, for example, cuvettes used for measurement, cleaning solutions for cleaning the flow paths within the device, pipette tips, etc.Interface 5 can provide application 6 with a collection of information regarding multiple sample measuring devices 11 (for example, reagent remaining amount information for multiple sample measuring devices 11 installed in a laboratory, maintenance schedule information for multiple sample measuring devices 11 installed in a laboratory, etc.). Figure 30 shows an example of a request regarding the operation of a sample measuring device 11. Figure 30 shows examples of (1) requests and responses for operations related to sample measurement, (2) requests and responses for operations related to maintenance, and (3) requests and responses for operations related to the operation of a sample measuring device 11. Examples of various types of information corresponding to requests and responses are shown in the table in Figure 30, but the various types of information corresponding to requests and responses are not limited to the examples shown in the table. Interface 5 can, for example, cause application 6 to execute a collection of operations for multiple sample measuring devices 11 (for example, registration of Rerun / Reflex rules for multiple sample measuring devices 11 installed in a laboratory, start / stop requests for multiple sample measuring devices 11 installed in a laboratory, etc.). In the example in Figure 30, the response to an operation request includes, for example, information indicating whether the operation has been completed or not (e.g., an ACK corresponding to a completed operation and a NACK corresponding to an incomplete operation (e.g., an error)).

[0086] Examples of requests and responses to interfaces 5 and 5A of the imaging device 12 are shown in Figures 31 to 34. Figure 31 shows an example of a request / response regarding information about the imaging device 12. For example, Figure 31 shows examples of (1) requests and responses to information specific to the imaging device 12 or the system including the imaging device 12, (2) requests and responses to information regarding the status of the imaging device 12, and (3) requests and responses to information regarding the operation of the imaging device 12. Examples of various types of information corresponding to requests and responses are shown in the table in Figure 31, but the types of information corresponding to requests and responses are not limited to those shown in the table. Interface 5 can, for example, provide information about multiple imaging devices 12 (e.g., serial numbers of multiple imaging devices 12 installed in an examination room, error status of multiple imaging devices 12 installed in an examination room, etc.) to application 6 all at once. Figure 32 shows an example of a request / response regarding information about imaging. For example, Figure 32 shows examples of (1) requests and responses regarding information about imaging results, (2) requests and responses regarding quality control, and (3) requests and responses regarding imaging orders. Examples of various types of information corresponding to requests and responses are shown in the table in Figure 32, but the types of information corresponding to requests and responses are not limited to those shown in the table. Interface 5 can, for example, provide Application 6 with information regarding imaging results (e.g., blood cell images, metadata associated with blood cell images, etc.). Information regarding imaging results is associated with, for example, identification information about the sample (e.g., sample ID). For example, it is possible to request information regarding imaging results from Interface 5 based on identification information about the sample, and provide Application 6 with information regarding imaging results, including blood cell images and metadata. The metadata also includes, for example, flag information that suggests that cells included in the blood cell image are abnormal cells, and information indicating the attributes of the cells included in the blood cell image (e.g., cell classification type). For example, Application 6 can use the metadata to generate classification results (statistical information) for each sample, classifying multiple blood cell images by cell attributes.Interface 5 can provide application 6 with information related to imaging orders (e.g., a list of imaging orders, whether or not there are imaging orders, a list of specimen IDs associated with imaging orders, etc.). For example, based on the information related to imaging orders, interface 5 can extract identification information for specimens for which imaging orders exist, and provide application 6 with information related to imaging data associated with the extracted identification information for the specimens. Interface 5 can also provide application 6 with information related to multiple imaging devices 12 (e.g., the results of imaging specimens by multiple imaging devices 12 installed in the laboratory over a predetermined period, the results of quality control performed by multiple imaging devices 12 installed in the laboratory over a predetermined period, etc.). Here, quality control in imaging devices 12 is performed to confirm whether imaging devices 12 can correctly detect cells in smears. For example, imaging devices 12 can take a predetermined number of images using smears of blood specimens smeared on glass slides, and the accuracy of the detection of cells in the smears can be used as an indicator for quality control. Figure 33 shows an example of a request for / response to information regarding the maintenance of imaging devices 12. Figure 33 shows examples of (1) requests and responses regarding oil information, and (2) requests and responses regarding maintenance information. Examples of various types of information corresponding to requests and responses are shown in the table in Figure 33, but the types of information corresponding to requests and responses are not limited to those shown in the table. Interface 5 can provide information on multiple imaging devices 12 (for example, oil level information for multiple imaging devices 12 installed in the examination room, maintenance schedule information for multiple imaging devices 12 installed in the examination room, etc.) to Application 6 all at once. Figure 34 shows examples of requests regarding the operation of the imaging device 12. Figure 34 shows examples of (1) requests and responses regarding imaging operations, (2) requests and responses regarding maintenance operations, and (3) requests and responses regarding the operation of the imaging device 12. Examples of various types of information corresponding to requests and responses are shown in the table in Figure 34, but the types of information corresponding to requests and responses are not limited to those shown in the table.Interface 5 allows application 6 to execute a series of operations on multiple imaging devices 12 (for example, requests to start / stop multiple imaging devices 12 installed in an examination room). In the example in Figure 34, the response to an operation request includes information indicating whether the operation has been completed or not (for example, an ACK corresponding to completion of the operation and a NACK corresponding to incomplete operation (e.g., an error)).

[0087] [PUSH notification] Figure 35 shows an example of the configuration for push notifications from the data management software 4 of the sample measuring device 11 and the imaging device 12 to the data management system 15. Interface 5 may include a notification unit 54 that has the function of making push notifications. The notification unit 54 provides information corresponding to a predetermined event to the data management system 15 via the communication network 204 by push notification when a predetermined event occurs. Figure 36 shows an example of an event and an example of information corresponding to the event (information that is the subject of push notification). For example, the notification unit 54 provides the data management system 15 with the measurement result when the sample measuring device 11 has acquired the measurement result of the sample. For example, the notification unit 54 provides the data management system 15 with information related to a predetermined operation (e.g., reagent replacement, maintenance, information setting, etc.) performed on the sample measuring device 11. For example, the notification unit 54 provides the data management system 15 with information related to a change in the state of the sample measuring device 11 (e.g., error occurrence, error clearing, etc.) when the state of the sample measuring device 11 changes. As another example, the notification unit 54 provides the data management system 15 with the imaging results obtained when the imaging device 12 has imaged blood cells in a sample. For example, the notification unit 54 provides the data management system 15 with information related to an operation performed on the imaging device 12 (e.g., oil change, maintenance, information setting, etc.). For example, the notification unit 54 provides the data management system 15 with information related to a change in the state of the imaging device 12 (e.g., error occurrence, error clearing, etc.) (e.g., error information, operation history related to the error, etc.).

[0088] The notification unit 54 may be provided in the data management software 4 instead of the interface 5. Alternatively, the notification unit 54 may be provided in the control unit 7 as software independent of the interface 5 and the data management software 4.

[0089] 〔application〕 Figure 37 shows an example configuration of Application 6. Application 6 includes, for example, a function provisioning unit 61, a requesting unit 62, and a response receiving unit 63.

[0090] The function provision unit 61 provides functions to extend the sample measurement system 1. The function provision unit 61 provides functions according to the type of application 6. For example, depending on the type of application 6, the function provision unit 61 provides functions such as providing QC results (QC charts, etc.), managing reagents installed in the sample measurement device 11, managing errors that occur in the sample measurement device 11, maintenance of the sample measurement device 11, and operation management of the sample measurement device 11. For example, depending on the type of application 6, the function provision unit 61 provides functions such as displaying blood cell images, displaying multiple classification candidates for blood cells, and displaying measurement results from the sample measurement device 11.

[0091] The function provisioning unit 61 may have a function to allow the user to log in with the service provider's account for the services provided by application 6. In this case, application 6 will only provide the services provided by the function provisioning unit 61 when the user is logged in with the service provider's account.

[0092] For example, if information regarding the sample measuring device 11 and the imaging device 12 is required, the function providing unit 61 requests the requesting unit 62 to acquire such information. The requesting unit 62 requests information from interfaces 5 and 5A in response to the request from the function providing unit 61. The requesting unit 62 requests information using command C, which is defined as a combination of URI and HTTP method, as described above. Furthermore, if control of the sample measuring device 11 (e.g., registration and modification of setting information for the sample measuring device 11, etc.) is required depending on the operation of the function providing unit 61, the function providing unit 61 makes a request to the requesting unit 62 regarding such control (e.g., a request for registration and modification of setting information, etc.). Furthermore, if control of the imaging device 12 (e.g., registration and modification of setting information for the imaging device 12, etc.) is required depending on the operation of the function providing unit 61, the function providing unit 61 makes a request to the requesting unit 62 regarding such control (e.g., a request for registration and modification of setting information, etc.). The requesting unit 62 makes a request to interfaces 5 and 5A regarding such control. The request unit 62 makes a request for the control by a command C defined by a combination of a URI and an HTTP method, as described above. The request unit 62 generates a command C including a URI based on information provided by the function provision unit 61, for example, and sends the request to the interface 5 / 5A. For example, when requesting information about the sample measuring device 11, the function provision unit 61 notifies the request unit 62 of instructions regarding the requested information (for example, the results measured by the sample measuring device 11 with a specific ID over a predetermined period). For example, when requesting information about the imaging device 12, the function provision unit 61 notifies the request unit 62 of instructions regarding the requested information (for example, the results of imaging by the imaging device 12 with a specific ID over a predetermined period). The request unit 62 generates a command C based on the notified instructions. Instructions from the function provision unit 61 to the request unit 62 are notified based on operations by the user of application 6, for example. For example, if a user requests measurement results obtained on a specific day by a sample measuring device 11 with a specific ID, the function providing unit 61 notifies the requesting unit 62 of instructions corresponding to that request. For example, if a user requests imaging results obtained on a specific day by an imaging device 12 with a specific ID, the function providing unit 61 notifies the requesting unit 62 of instructions corresponding to that request.When generating command C, the request unit 62 refers to configuration information related to the creation of a URI (for example, the IP address of the server to be requested) and generates command C. The configuration information may be the IP address of the server to be requested itself, or the server's URL (Uniform Resource Locator) may be set. The IP address of the server to be requested is, for example, the IP address of the control unit 7 of the sample measuring device 11 and imaging device 12 set up in the laboratory, and the IP address of the data management system 15. If the address of the server to be requested is set by a URL, the request unit 62 queries the DNS (Domain Name System) for the IP address based on the domain name included in the URL, for example. The request unit 62 generates a URI based on the IP address notified by the DNS. The IP address or URL may be entered by the user via the GUI of application 6. The generation of URIs and command C by the request unit 62 is the same in the application example described later.

[0093] The response receiving unit 63 receives responses corresponding to requests from the requesting unit 62 from interfaces 5 and 5A, and passes the response content to the function providing unit 61.

[0094] [Example of a classification candidate display application] The following describes a case where Application 6 is a classification candidate display application that displays a blood cell image and multiple classification candidates for the blood cells. The classification candidate display application collects, for example, a blood cell image of a sample and metadata including information indicating the cell type of the blood cells in the blood cell image from the imaging device 12, and provides a function to display multiple classification candidates for the blood cells based on the metadata. The classification candidate display application provides a function to display, for example, a specific blood cell image A11 and multiple classification candidates A111 for the blood cells in the specific blood cell image A11, as shown in Figure 45.

[0095] Referring again to Figure 37, the parts of the classification candidate display application will be explained. The function provision unit 61 requests the request unit 62 to acquire information about the imaging device 12, which is the data subject for displaying blood cell images and multiple classification candidates for blood cells in the blood cell images. For example, the function provision unit 61 requests the request unit 62 to acquire metadata including information indicating the cell type of the blood cell images of the sample acquired by the imaging device 12, information about multiple classification candidates for blood cells based on the metadata, attribute information about the blood cell images of the sample and the subject, etc. If there are multiple imaging devices 12, for example, the request unit 62 may be requested to acquire the device IDs and names of the multiple imaging devices 12.

[0096] The request unit 62 generates a URI based on the request from the function provision unit 61, for example, and requests information acquisition from interfaces 5 and 5A using a command C generated by combining the generated URI with the HTTP method "GET". The URI generated by the request unit 62 when acquiring information about the imaging device 12 is, for example, "http: / / 128.0.0.1:8080 / DI / / YYYY". In this example URI, the "server address" is specified as "128.0.0.1:8080", the "interface ID" is specified as "DI", the "device ID" is not specified, the "resource" is specified as "YYYY", and the "query parameters" are not specified. "YYYY" is an API endpoint corresponding to information about the imaging device 12 (for example, information about the type of imaging device 12, patient imaging data acquired by the imaging device 12, etc.). The "server address," "128.0.0.1:8080," is, for example, the address corresponding to the interface of the data management system that manages information about the imaging device 12. If there are multiple "server addresses," multiple URIs (each URI corresponding to multiple addresses) may be generated. The "interface ID," "DI," is set, for example, according to the type of imaging device 12 from which information is to be acquired. Multiple URIs may be generated depending on the type of information requested. The response receiving unit 63 receives a response corresponding to the request from the requesting unit 62 and transmits the received information to the function providing unit 61. For example, the requesting unit 62 generates a URI in response to a request and uses a command C generated by combining the generated URI with the HTTP method "GET" to request information acquisition from interfaces 5, 5A and the interface of the data management software that manages information about the imaging device 12. If the imaging device 12 does not have an interface, data is transmitted from the imaging device 12 without an interface to the data storage 18 of the data management system 15 via interface 5 of the data management system 15. For example, data is transmitted from the imaging device 12 to the data storage 18 of the data management system 15 via the interface 5 of the data management system 15.In this case, an application for data transmission is added to the imaging device 12, a URI is generated by the data transmission application, and data is sent to the interface 5 of the data management system 15 by command C, which is generated by combining the generated URI with the HTTP methods "POST" and "PUT". The data sent to the data management system 15 can be retrieved by the abnormal flag display application. For this reason, the request unit 62 generates a URI based on the request content from the function provision unit 61, and requests the transmission of data to the interface 5 of the data management system 15 by command C, which is generated by combining the generated URI with the HTTP method "GET".

[0097] The function provider 61, for example, compares rules regarding multiple classification candidates for blood cells in a blood cell image with metadata to determine whether or not to generate multiple classification candidates for blood cells. The function provider 61 generates multiple classification candidates for blood cells if, for example, it determines that the metadata satisfies the rules regarding multiple classification candidates for blood cells. The metadata includes information indicating the cell type of blood cells in the blood cell image of the sample. The function provider 61 determines that the rules regarding multiple classification candidates for blood cells are satisfied if, for example, metadata exists that includes information indicating that there are multiple classification candidates for blood cells in the blood cell image of the sample (e.g., BL (blast cell), BA (basophil), VLY (reactive lymphocyte)). The metadata that includes information indicating that there are multiple classification candidates for blood cells may be statistical information such as classification results or classification probabilities classified by image analysis of blood cell images, or it may be information calculated from predetermined classification criteria based on past image data classified by image analysis of blood cell images. Furthermore, metadata including information indicating that there are multiple classification candidates for the blood cell may be, for example, information generated by processing the blood cell image using an artificial intelligence algorithm. The function provider 61 displays the blood cell image and the multiple classification candidates for the blood cell according to the determination result.

[0098] Application 6 extends the functionality to display blood cell images and multiple classification candidates for blood cells in the blood cell images. In Application 6, in order to distinguish and utilize data for each sample, for example, metadata may be associated with identification information about the sample (e.g., sample ID).

[0099] Figure 45 shows an example 1 of a GUI provided by the function provider 61 that displays blood cell images and multiple classification candidates for blood cells in the blood cell images. The function provider 61, for example, acquires multiple blood cell images associated with the sample identification information A4. The function provider 61, for example, displays a list A1 of blood cell images associated with the sample identification information A4. The function provider 61 groups and displays the blood cell images according to the classification type of cells in the blood cell images (BL (blast), MY (myelocyte), MMY (metamyelocyte)). The function provider 61, for example, recognizes the classification type based on the metadata of each blood cell image and groups the blood cell images. The function provider 61, for example, displays multiple classification candidates A111 for blood cells based on the metadata corresponding to a specific blood cell image associated with the sample identification information A4.

[0100] [Example of a classification candidate display application] The modified version of Application 6 is a classification candidate display application that further displays statistical information about blood cell images based on metadata including information indicating the cell type of the blood cell images of the sample, an abnormality flag for the sample based on metadata, and hematology test results. The classification candidate display application of this modified version provides the function of further displaying statistical information A2, an abnormality flag B3, and hematology test results A3 of the sample measuring device 11, in addition to blood cell images A1, A11, and multiple classification candidates A111 for blood cells in the blood cell images, as shown in Figure 46.

[0101] Referring again to Figure 37, we will describe the parts of the classification candidate display application that further displays statistical information about blood cell images based on metadata including information indicating the cell type of the blood cell images of the sample, abnormal flags about the sample based on metadata, and hematology test results. The function providing unit 61 requests the requesting unit 62 to acquire information about each of the sample measuring device 11 and imaging device 12 that are subject to management of the data to be displayed in an integrated manner. For example, the function providing unit 61 requests the requesting unit 62 to acquire hematology test results acquired by the sample measuring device 11, results of imaging blood cells acquired by the imaging device 12 (e.g., multiple blood cell images, metadata which is additional information related to each of the multiple blood cell images), and attribute information about the subject. If there are multiple sample measuring devices 11 and imaging devices 12, for example, the requesting unit 62 may be requested to acquire the device IDs of each of the multiple sample measuring devices 11 and multiple imaging devices 12, and the names of each of the multiple sample measuring devices 11 and multiple imaging devices 12.

[0102] The request unit 62 generates a URI based on the request from the function provision unit 61, for example, and requests information acquisition from interfaces 5 and 5A using a command C generated by combining the generated URI with the HTTP method "GET". The URI generated by the request unit 62 when acquiring information about the specimen measurement device 11 is, for example, "http: / / 127.0.0.1:8080 / XR / / XXXX". In this example URI, the "server address" is specified as "127.0.0.1:8080", the "interface ID" is specified as "XR", the "device ID" is not specified, the "resource" is specified as "XXXX", and the "query parameters" are not specified. "XXXX" is an API endpoint corresponding to information about the specimen measurement device 11 (for example, information about the type of specimen measurement device 11, patient measurement data acquired by the specimen measurement device 11, etc.). The "server address," "127.0.0.1:8080," is, for example, the address corresponding to interface 5A of the data management system 15 that manages information about the sample measuring device 11. If there are multiple "server addresses," multiple URIs (each URI corresponding to multiple addresses) may be generated. The "interface ID," "XR," is set, for example, according to the type of sample measuring device 11 from which information is to be acquired. Multiple URIs may be generated depending on the type of information requested. Similarly, the URI generated by the request unit 62 when acquiring information about the imaging device 12 is, for example, "http: / / 128.0.0.1:8080 / DI / / YYYY." In this example URI, the "server address" is specified as "128.0.0.1:8080," the "interface ID" is specified as "DI," the "device ID" is not specified, the "resource" is specified as "YYYY," and the "query parameters" are not specified. "YYYY" is an API endpoint corresponding to information about the imaging device 12 (for example, information about the type of imaging device 12, patient imaging data acquired by the imaging device 12, etc.). The "server address" "128.0.0.1:8080" is, for example, an address corresponding to the interface of a data management system that manages information about the imaging device 12.If there are multiple "server addresses", multiple URIs (each URI corresponding to one of the multiple addresses) may be generated. The "interface ID", "DI", is set, for example, according to the type of imaging device 12 that is the target of information acquisition. Multiple URIs may be generated depending on the type of information requested. The response receiving unit 63 receives a response corresponding to the request from the requesting unit 62 and passes the received information to the function providing unit 61. For example, the requesting unit 62 generates a URI in response to the request and uses a command C generated by combining the generated URI with the HTTP method "GET" to request information acquisition from interface 5 and / or 5A.

[0103] The function provider unit 61 further provides functions to display blood cell images, multiple classification candidates for blood cells in the blood cell images, statistical information, abnormality flags, and hematology test results.

[0104] Figure 46 shows Example 2 of GUI provision by the function provider 61. GUI provision Example 2 is an example of integrated display of statistical information, abnormality flags, and hematology test results. The function provider 61, for example, acquires multiple blood cell images associated with the sample identification information A4. The function provider 61, for example, displays a list A1 of blood cell images associated with the sample identification information A4. The function provider 61 groups and displays the blood cell images according to the classification type of cells in the blood cell images (BL (blast), MY (myelocyte), MMY (metamyelocyte)). The function provider 61, for example, recognizes the classification type based on the metadata of each blood cell image and groups the blood cell images. The function provider 61, for example, displays statistical information A2 based on the metadata corresponding to each of the multiple blood cell images associated with the sample identification information A4. The function provider 61, for example, displays the number and percentage of blood cell images classified into each of the multiple classification types as statistical information A2, based on the classification types included in the metadata. The function provider 61 displays an abnormality flag B3 in addition to the statistical information A2. The function provider 61, for example, obtains the hematology test result A3 associated with the specimen identification information A4, and displays the hematology test result A3, the list of blood cell images A1, the statistical information A2, and the abnormality flag B3 in an integrated manner. The hematology test result A3 includes, for example, the result of CBC (Complete Blood Count) and the result regarding the white blood cell classification.

[0105] By adding Application 6 to the system, the functionality to display the GUI exemplified in Figure 46 can be extended. To use data in this system, it is necessary to distinguish and use data for each sample. For example, metadata for blood cell images and hematology test results may each be associated with identification information about the sample (e.g., sample ID). In this case, it is possible to display blood cell images associated with the identification information for the same sample, multiple classification candidates for blood cells in the blood cell images, statistical information, abnormality flags, and hematology test results.

[0106] [Example of data structure within data storage] Figure 47 shows an example of a data structure when the data storage 18 or storage unit 74 is a relational database. As shown in the figure, the information managed by the data storage 18 or storage unit 74 includes, for example, data associated with "identification information about the sample" for each of the "hematology test results" acquired by the sample measuring device 11 and the "blood cell images" acquired by the imaging device 12. The "blood cell images" are associated with, for example, an "image ID" for identifying the "blood cell images" and "meta-information". The "meta-information" includes, for example, the classification type of cells contained in the blood cell image, a flag related to the cells (for example, a flag indicating that the cells are abnormal cells), a comment from the laboratory technician who classified the cells, the date and time the blood cell image was taken, and information about the scale size of the cells contained in the blood cell image (for example, a scale size pre-set according to the classification type). Interfaces 5 and 5A specify the blood cell images and meta-information to be used, for example, based on the identification information of the sample and / or the image ID. Application 6 generates statistical information, for example, based on the meta-information associated with the sample. Statistical information may be stored in the data storage 18 or storage unit 74, as shown in the example in Figure 47. For example, the data management software 4 of the imaging device 12 may generate statistical information based on the blood cell images and metadata acquired for the sample and store it in the data storage 18 or storage unit 74. In this case, application 6 may retrieve the statistical information stored in the data storage 18 or storage unit 74 and display the retrieved statistical information. Application 6 may also provide a function for modifying the metadata of the blood cell images. For example, application 6 may provide a function to change the classification type of cells included in the blood cell images using a GUI as shown in the example in Figure 46. In response to the change in the classification type of cells via the GUI, application 6 updates the metadata in the data storage 18 and / or storage unit 74, for example, via interface 5 or 5A. Application 6 can also provide a function to display the blood cell images acquired via interface 5 or 5A together with a reference image.Application 6, for example, refers to metadata corresponding to each of the acquired blood cell images and groups and displays the blood cell images according to the cell classification type. Application 6, for example, displays a reference image corresponding to the classification type of the group in the group's display area. Application 6, for example, has reference images corresponding to the classification type. The reference image is, for example, a reference image of a cell corresponding to the classification type (for example, if the classification type is "Neutrophil", the reference image is a blood cell image in which a typical neutrophil is captured). Application 6 may, for example, display a ruler that serves as an indicator of the size of the cells contained in the blood cell image. Application 6 displays the ruler by referring to metadata, for example. The metadata may include, for example, information indicating a pre-set scale size according to the classification type of cells in the blood cell image. Application 6 displays the ruler based on the scale size information included in the metadata, for example. Application 6 may, for example, provide a function for the operator to register information indicating that the displayed hematology test results and / or blood cell images have been verified in the GUI illustrated in Figure 46. Hematology test results include, for example, the number and percentage of blood cells (e.g., the number and percentage of white blood cells), the classification of blood cells and the number and percentage of each classification, histograms, and scattergrams.

[0107] Identifying information about a specimen may be associated with "subject attribute information." "Subject attribute information" may include, for example, the subject's gender, age, medical department, diagnosis, and medical record information regarding their medical history.

[0108] The data storage 18 or storage unit 74 may store metadata associated with a unique "metadata ID". For example, when application 6 obtains metadata for a blood cell image, it may request the interface 5 and / or 5A to obtain the desired metadata based on the metadata ID. By making a request based on the metadata ID, application 6 can, for example, specify and request any metadata from among multiple metadata related to the identification information of the specimen.

[0109] Hematology test results may include, for example, values ​​relating to the number of each cell type selected from erythrocytes, nucleated erythrocytes, miniature erythrocytes, platelets, hemoglobin, reticulocytes, immature granulocytes, neutrophils, eosinophils, basophils, lymphocytes, and monocytes; values ​​relating to the ratio of each cell type selected from erythrocytes, nucleated erythrocytes, miniature erythrocytes, platelets, hemoglobin, reticulocytes, immature granulocytes, neutrophils, eosinophils, basophils, lymphocytes, and monocytes; and values ​​relating to at least one selected from hematocrit, mean corpuscular volume (MCV), mean corpuscular hemoglobin (MCH), mean corpuscular hemoglobin concentration (MCHC), and mean platelet volume (MPV). Hematology test results may also include scattergrams and histograms (e.g., frequency distribution charts for erythrocytes, frequency scatter plots for leukocytes, etc.).

[0110] The results of imaging blood cells include flags that indicate the possibility of abnormal cells being present among the cells contained in each blood cell image. Flags indicating abnormal cells may include values ​​associated with at least one selected from nuclear morphological abnormalities, granular abnormalities, cell size abnormalities, cell malformations, cell disruption, vacuoles, immature cells, presence of inclusion bodies, Döhle bodies, satellite phenomena, chromatin abnormalities, petal-like nuclei, high N / C ratio, bleb-like morphology, smudge, and hairy cell-like morphology. Nuclear morphological abnormalities may include at least one selected from hyperlobulation, hypolobulation, pseudopelger nucleus abnormalities, annular nuclei, spheroid nuclei, elliptic nuclei, apoptosis, polynucleation, nuclear disintegration, enucleation, naked nuclei, irregular nuclear margins, nuclear fragmentation, internuclear bridges, multiple nuclei, notched nuclei, mitosis, and nucleolar abnormalities. Granule abnormalities may include at least one selected from degranulation, granule distribution abnormalities, toxic granules, Auer bodies, Fagott cells, and pseudo-Chediak-Higashi granule-like granules. Furthermore, a flag indicating that each cell in the blood cell image is an abnormal cell may be added as additional metadata associated with the blood cell image.

[0111] The classification results obtained by classifying multiple blood cell images included in the imaging of blood cells according to the attributes of each cell may be a classification result based on cell type or a morphological classification result. Regarding the morphological classification of cells, the classification may include values ​​related to the number of each cell type selected from at least one cell type selected from neutrophils, eosinophils, platelets, lymphocytes, monocytes, basophils, metamyelocytes, myelocytes, promyelocytes, blasts, plasma cells, atypical lymphocytes, immature eosinophils, immature basophils, erythroblasts, and megakaryocytes, and values ​​related to at least one ratio of each cell type selected from at least one cell type selected from neutrophils, eosinophils, platelets, lymphocytes, monocytes, basophils, metamyelocytes, myelocytes, promyelocytes, blasts, plasma cells, atypical lymphocytes, immature eosinophils, immature basophils, erythroblasts, and megakaryocytes. The classification of each of the multiple blood cell images may be performed by an operator on the application, or it may be performed automatically using machine classification and artificial intelligence algorithms. Alternatively, the operator may reclassify the results initially classified by the imaging device 12 on the application.

[0112] The classification results (statistical information) may be modified, for example, in response to manual or automated corrections of the metadata.

[0113] [Processing flow by application software] Let's explain using Configuration Example 1 (see Figure 4) as an example. First, the data management software of the data management system 15 collects data including imaging results from the imaging device 12. For example, the data management software of the data management system 15 collects data from the imaging device 12 in which the results of imaging blood cells are associated with identification information about the specimen. It may also collect data in which blood cell images and multiple classification candidates for blood cells in the blood cell images are associated with identification information about the specimen. Furthermore, the data management software of the data management system 15 may collect data in which statistical information and abnormality flags are associated with identification information about the specimen, and may also collect data including hematology test results from the specimen measuring device 11. For example, the data management software of the data management system 15 may collect data in which hematology test results are associated with identification information about the specimen from the specimen measuring device 11.

[0114] Next, the application software 6 of the terminal device 101 displays the data collected by the data management software of the data management system 15 on a display unit provided on the terminal device 101. The data displayed on the display unit provided on the terminal device 101 is, for example, the imaging results associated with identification information related to the specimen. Figure 45 shows an example of a GUI (Graphical User Interface) that displays data associated with identification information (specimen ID) related to the specimen for each of the blood cell images and multiple classification candidates for blood cells in the blood cell images. In Figure 45, the blood cell images are grouped and displayed by classification type (for example, BL (blast cell), MY (myelocyte), MMY (metamyelocyte)), and for a specific blood cell image, multiple classification candidates for blood cells (for example, BL (blast cell), BA (basophil), VLY (reactive lymphocyte)) are displayed. Several to several hundred blood cell images are displayed, and they may be individual blood cell images that were captured, or a single blood cell image generated by stitching together multiple blood cell images.

[0115] Figure 48 is a flowchart illustrating an example of the processing flow by the application software 6 of the terminal device 101. In Figure 48, the application software 6 of the terminal device 101 collects data including the results of imaging a smear specimen by the imaging device 12 (S11). The collected data may also include hematology test results. The application software 6 collects data from, for example, the data management system 15. Based on the collected data, the application software 6 generates multiple classification candidates for blood cells in a specific blood cell image (S222). The application software 6 may also collect multiple classification candidates for blood cells in a specific blood cell image generated by, for example, the data management system 15. The application software 6 of the terminal device 101 displays multiple classification candidates for blood cells in the blood cell image and the specific blood cell image for each specimen ID (S333). The application software 6 may also display statistical information, abnormality flags, and hematology test results. The application software 6 may also display multiple classification candidates for blood cells in the blood cell image and the specific blood cell image, as illustrated in Figure 45. Furthermore, the application software 6 may display blood cell images, multiple classification candidates for blood cells in a specific blood cell image, statistical information, abnormality flags, and hematology test results, as illustrated in Figure 46.

[0116] Figure 49 is a flowchart detailing the processing flow shown in Figure 48. The application software 6 of the terminal device 101 collects data including imaging results of smear specimens (S111). The collected data may also include hematology test results. The application software 6 collects data from, for example, the data management system 15. The application software 6 compares the metadata contained in the collected data with rules regarding multiple classification candidates for blood cells in a specific blood cell image (S1001). The rules regarding multiple classification candidates for blood cells in a specific blood cell image may be, for example, multiple rules set in advance in the application software 6 based on statistical information such as classification results and classification probabilities based on past image data classified by image analysis of blood cell images, or rules set by predetermined classification criteria based on past image data classified by image analysis of blood cell images. Furthermore, the rules regarding multiple classification candidates for blood cells in a specific blood cell image may be, for example, rules using an artificial intelligence algorithm set in advance in the application software 6. The rules regarding multiple classification candidates for blood cells in a specific blood cell image may be arbitrarily set by the user of the application software 6 based on past data regarding microscopic examination of smear specimens. Based on the determination by the rules, the application software 6 of the terminal device 101 generates multiple classification candidates for blood cells in a specific blood cell image (S222), and displays the blood cell image and the multiple classification candidates for blood cells in the specific blood cell image for each sample ID (S333). The blood cell image and the multiple classification candidates for blood cells in the specific blood cell image are displayed, for example, as shown in Figure 45 above. Note that in S1001, the rules regarding multiple classification candidates and metadata are compared, and if it is determined that the rules regarding multiple classification candidates for blood cells in a specific blood cell image are not met, multiple classification candidates are not generated, and for example, only the blood cell image classified into a single cell type is displayed in the GUI.

[0117] Figure 50 is a flowchart showing a modified version of Figure 48. In the example of Figure 50, the application software 6 can change the displayed content in response to GUI operations. In Figure 50, after S333, the application software 6 displays an additional screen related to the attribute selection (S5555) in response to the attribute selection (S4444). The attributes of the blood cell image are, for example, the classification type of the cells. The application software 6 can, for example, display multiple classification candidates for blood cells in the relevant blood cell image and hematology test results as additional screens, depending on the selected classification type. Figures 51 and 52 are examples 3 of GUI provision corresponding to the flowchart in Figure 50. In the screen shown in Figure 51, where statistical information A2, abnormality flag B3, and hematology test result A3 are displayed, when the selection of an attribute included in statistical information A2 (classification type shown in a thick frame: BL (blast cell)) is accepted (S4444), as shown in Figure 52, a specific blood cell image A11 related to the selection of the attribute (BL (blast cell)) and multiple classification candidates A111 of the blood cells in the specific blood cell image A11 are displayed in area B2 as an additional screen (S5555). The application software 6 may, for example, highlight the displayed content of the selected attribute (e.g., cell classification type) compared to the displayed content of the unselected attribute. Examples of highlighting include, for example, displaying the selected classification type in a frame such as a square, or displaying it in a color that can be distinguished from the displayed content of the unselected classification type. The operation of selecting an attribute includes at least one of mouse operation, touch panel operation, and voice operation. Figures 53 and 54 are GUI provision example 4. As shown in Figures 53 and 54, statistical information may be displayed for each attribute (for example, for each classification type), an area B1 for displaying the abnormality flag B3 may be displayed, and depending on the selection of an attribute (the part shown in the thick border), a specific blood cell image A11 related to the attribute selection, multiple classification candidates A111 for the blood cells in the specific blood cell image A11, and hematology test results A3 may be displayed as additional screens. Figure 55 is GUI example 5.As shown in Figure 55, for example, a first area B1 displaying statistical information A2 and an abnormality flag B3, and a second area B2 displaying a blood cell image A1 may be displayed. Depending on the selection of an attribute (e.g., classification type shown in a thick border: BL (blast cell)), a specific blood cell image A11 related to the attribute selection, multiple classification candidates A111 for blood cells in the specific blood cell image A11, and a scattergram included in the hematology test result A3 (e.g., a scattergram showing a population of cells indicating Blasts (blast cells)) may also be displayed. Figure 56 is an example GUI 6. In the GUI of example 6, a blood cell image A1 in which platelet aggregation is observed, an abnormality flag B3 (e.g., "Platelet aggregation has been detected"), and statistical information A2 are displayed. In the GUI of example 6, a digital slide simulating the position where the blood cell image was captured on the smear specimen 120 by the imaging device 12 may be displayed along with the blood cell image. The digital slide shown in Figure 56 indicates platelet aggregates (e.g., aggregates of 5 or more platelets) in the blood cell image detected by the imaging device 12 with white dots. By checking the digital slide, the operator can determine, for example, whether the platelet aggregates in the blood cell image are located on the top / bottom or left / right sides of the smear specimen 120.

[0118] Conventionally, in the imaging device 12, the operator verifies whether or not the obtained results should be output for use in diagnosis. A flag indicating whether or not the operator has verified the results of imaging the obtained blood cells can be displayed, which can be used as reference information when checking the results in the application.

[0119] [Example configuration for providing application functionality as a web service] The functionality of application 6 is not limited to being provided as standalone software executed on terminal device 101 and sample measuring device 11, but may also be provided as a web service.

[0120] Figure 38 shows an example configuration in which the functions of application 6 are provided as a web service. In the example configuration shown in the figure, the sample measurement system 1 includes a sample measurement device 11 equipped with a web browser 8, and a web service system 301 connected to the sample measurement device 11 via a communication network 205. The communication network 205 is, for example, the internet. The sample measurement device 11 includes a measurement unit 2 and a control unit 7 having control software 3, data management software 4, an interface 5, and a processor 71 that runs the web browser 8.

[0121] The Web service system 301 includes a control unit 302 having a processor that executes a service function provision unit 6A that functions as a Web service. The service function provision unit 6A has functions equivalent to those of application 6. The service function provision unit 6A includes, for example, a function provision unit 61A, a request unit 62A, and a response receiving unit 63A. The function provision unit 61A, the request unit 62A, and the response receiving unit 63A have functions equivalent to those of function provision unit 61, the request unit 62, and the response receiving unit 63, respectively.

[0122] In this configuration example, by accessing the service function provision unit 6A, which functions as a web service, via the web browser 8 of the sample measurement device 11, information and functions can be used through the interface 5 of the sample measurement device 11.

[0123] Figure 39 shows another configuration example in which the functions of application 6 are provided as a web service. In the configuration example shown in the figure, the sample measurement system 1 consists of a sample measurement device 11, a web service system 301, a data management system 15, and a terminal device 101 equipped with a web browser 8, all connected via a communication network 205.

[0124] In this configuration example, by accessing the service function provision unit 6A, which functions as a web service, using the web browser 8 of the terminal device 101, information managed by the data storage 18 can be used via the interface 5A of the data management system 15.

[0125] Figure 40 shows another configuration example in which the functions of application 6 are provided as a web service. In the configuration example shown in this figure, the sample measurement system 1 consists of a sample measurement device 11, a web service system 301, and a terminal device 101 equipped with a web browser 8, all connected via a communication network 205.

[0126] In this configuration example, by accessing the service function provision unit 6A, which functions as a web service, via the Web browser 8 of the terminal device 101, information and functions can be used through the interface 5 of the sample measurement device 11.

[0127] [Application delivery method] The delivery method for application 6 will now be described. Figure 41 shows an example configuration of an application delivery server 401 that provides application 6. The application delivery server 401 is located, for example, on the cloud and is connected to terminal devices 101 and control units 7 via a communication network. Terminal devices 101 and control units 7 are, for example, smartphones (iPhone, Android devices), tablets (iPad, Android tablets, Windows tablets), Windows PCs with Windows OS installed, and Macs with Mac OS installed. The application delivery server 401 includes a control unit 402 having a processor that executes a download request receiving unit 403 and an application delivery unit 404, and an application storage 405 that stores application 6.

[0128] The operators of the terminal device 101 and the control unit 7 log in to a designated download application (e.g., App Store, Google Play Store, Windows Store) using an account ID managed by an application provider (e.g., Apple ID, Google account, Microsoft account, etc.), and request the application provider server 401 to download the desired application 6 through that download application.

[0129] The download request receiving unit 403 notifies the application providing unit 404 of information regarding the requested application 6. The application providing unit 404 retrieves the notified application 6 from the application storage 405 and sends it to the requesting party (terminal device 101 or control unit 7). The application providing unit 404 may also send, for example, an installer for application 6 to the requesting party (terminal device 101 or control unit 7). The terminal device 101 or control unit 7, upon receiving the installer, installs application 6 based on the installer.

[0130] The application delivery server 401 may be multi-platform compatible (e.g., Windows, MacOS, iOS, Android). Furthermore, there may be multiple application delivery servers 401 depending on the platform. For example, there may be an application delivery server 401 providing applications 6 for iOS (e.g., the App Store), an application delivery server 401 providing applications 6 for Android (e.g., Google Play), and an application delivery server 401 providing applications 6 for Windows (e.g., the Microsoft Store). In this case, the terminal device 101 and the control unit 7 request the provision of applications 6 in a manner appropriate to the platform.

[0131] A terminal device 101 and control unit 7 equipped with iOS can request, for example, an application provision server 401 that provides iOS applications 6 to download a desired application 6 found using a predetermined download application (e.g., the App Store). Similarly, a terminal device 101 and control unit 7 equipped with Android OS can request, for example, an application provision server 401 that provides Android applications 6 to download a desired application 6 found using a predetermined download application (e.g., the Google Play Store). Similarly, a terminal device 101 and control unit 7 equipped with Windows OS can request, for example, an application provision server 401 that provides Windows applications 6 to download a desired application 6 found using a predetermined download application (e.g., the Microsoft Store).

[0132] In some medical facilities, such as laboratories, the terminal device 101 and control unit 7 may not be connected to the internet. In such cases, for example, a maintenance worker may copy the installer for application 6 from a medium containing the installer (e.g., CD / DVD / USB memory / external HDD / SSDD) to the terminal device 101 and control unit 7, and then install application 6 to the terminal device 101 and control unit 7.

[0133] In some medical facilities and laboratories, the terminal device 101 and control unit 7 may only be allowed to communicate with the outside world via a secure communication network (e.g., VPN: Virtual Private Network). In this case, for example, application 6 may be distributed from a server that can be configured to connect to the terminal device 101 and control unit 7 via a secure communication network. Figure 42 shows an example configuration for providing application 6 in a secure communication environment. Note that a secure communication environment includes an environment in which the file distribution server 501 is installed within the facility's intranet and accessible from the terminal device 101 and control unit 7 via the intranet.

[0134] The file distribution server 501 includes a processor that runs the communication unit 502 and the information provision unit 503, and storage 504 that stores data necessary for the installation of application 6 (e.g., installer and application 6 configuration files). The communication unit 502 has, for example, VPN server functionality. The information provision unit 503 has, for example, Web server functionality.

[0135] The terminal device 101 and the control unit 7 have processors that execute a communication client unit 91 and an information acquisition unit 92. The communication client unit 91 has, for example, a VPN client function and establishes a secure communication network 206 with the communication unit 502. The information acquisition unit 92 is, for example, a web browser.

[0136] The terminal device 101 and the information acquisition unit 92 of the control unit 7 access the information provision unit 503 of the file distribution server 501 via the secure communication network 206. The information provision unit 503 provides the information acquisition unit 92 with data that the terminal device 101 and the control unit 7 can download, for example. The information acquisition unit 92 presents this data on a web page. When the operators of the terminal device 101 and the control unit 7 select the data they wish to download from the web page, the information provision unit 503 retrieves the corresponding data from the storage 504 and transmits it to the information acquisition unit 92. The information acquisition unit 92 then installs the application 6 based on the retrieved data.

[0137] The terminal device 101 and the control unit 7 may download the installer for application 6 via the internet and install application 6 using the installer.

[0138] [Web clip] The functionality of application 6 may be provided to terminal device 101 and control unit 7 as a web clip (shortcut to a website). The service provider notifies terminal device 101 and control unit 7, for example, of the URL (Uniform Resource Locator) to which the web clip will be accessed. The operator of terminal device 101 and control unit 7 can, for example, bookmark the notified URL as a web clip on the home screen or desktop of terminal device 101 and control unit 7. The operator of terminal device 101 and control unit 7 can, for example, access the service provider's website using the web browser installed in terminal device 101 and control unit 7, access the menu that provides the desired service from that website, and bookmark the site of that menu as a web clip.

[0139] The system configuration examples for using the functions of application 6 with Web Clip are the same as those shown in Figures 38-40. In the configuration example shown in Figure 38, information and functions can be used via the interface 5 of the sample measuring device 11 by accessing the service function provider unit 6A, which functions as a Web service at the URL specified by Web Clip, using the Web browser 8 of the control unit 7. Similarly, in the configuration example shown in Figure 39, information managed by the data storage 18 via the interface 5A of the data management system 15 can be used by accessing the service function provider unit 6A, which functions as a Web service at the URL specified by Web Clip, using the Web browser 8 of the terminal device 101. Similarly, in the configuration example shown in Figure 40, information and functions can be used via the interface 5 of the sample measuring device 11 by accessing the service function provider unit 6A, which functions as a Web service at the URL specified by Web Clip, using the Web browser 8 of the terminal device 101.

[0140] [Providing applications via MDM / MAM] Application 6 may be provided without going through a designated application provider (e.g., Apple Store, Google Play Store, Microsoft Store). For example, Application 6 may be provided to the terminal device 101 and the control unit 7 without going through a designated application provider by utilizing an MDM (Mobile Device Management) or MAM (Mobile Application Management) mechanism.

[0141] Figure 43 shows an example configuration for providing application 6 using MDM or MAM. The terminal device 101 and control unit 7 are connected to the MDM / MAM system 601 via a communication network 207. The terminal device 101 and control unit 7 are registered with the MDM / MAM system 601 and managed by the MDM / MAM system 601 according to a management policy. To manage the terminal device 101 and control unit 7 with the MDM / MAM system 601, for example, a management profile is installed on the terminal device 101 and control unit 7. For example, information for installing the management profile (e.g., a URL to download the installer) is notified to the terminal device 101 and control unit 7 (e.g., by email).

[0142] Once the management profile is installed on the terminal device 101 and the control unit 7, the terminal device 101 and the control unit 7 are registered with the MDM / MAM system 601, and information about the terminal device 101 and the control unit 7 is registered in the database 604 of the MDM / MAM system 601.

[0143] The MDM / MAM execution unit 603 acquires information about the application 6 installed on the terminal device 101 and the control unit 7, and registers it in the application list of the database 604. The MDM / MAM execution unit 603 can then distribute the application 6 to the terminal device 101 and the control unit 7. The terminal device 101 and the control unit 7 install the distributed application 6. This allows the application 6 to be provided without going through a predetermined application provider (such as the App Store).

[0144] The management function provision unit 602 provides the MDM / MAM management terminal 701 with management functions for the terminal device 101 and the control unit 7. For example, the management function provision unit 602 provides the MDM / MAM management terminal 701 with a website for managing the terminal device 101 and the control unit 7. Through this website, the operator of the MDM / MAM management terminal 701 can perform tasks such as registering and modifying management policies for the terminal device 101 and the control unit 7, distributing applications 6 to the terminal device 101 and the control unit 7, and managing applications 6 installed on the terminal device 101 and the control unit 7.

[0145] Figure 44 shows an example of the data structure of database 604 when it is a relational database. As shown in the figure, the information managed in database 604 includes, for example, user identification information, affiliated organization, device type, device identification information, policies, and application lists.

[0146] User identification information is information used to identify users of terminal device 101 and control unit 7. For example, it may include an ID assigned to the user by the MDM / MAM system 601, the user's name, or a combination of these.

[0147] The affiliated organization is the identification information of the organization to which the terminal device 101 and the control unit 7 belong. For example, this includes the ID assigned to the organization by the MDM / MAM system 601, the organization name, or a combination thereof.

[0148] The device type is information used to identify the platform of the device. For example, iOS, Android, Windows, Mac, etc.

[0149] Device identification information is unique to the terminal devices 101 and control unit 7 managed by the MDM / MAM system 601. Examples include IMEI (International Mobile Equipment Identifier), serial number, SIM (Subscriber Identity Module) card number, telephone number, MAC (Media Access Control) address, or combinations thereof.

[0150] The policy is a management policy provided by the MDM / MAM system 601. For example, it is the configuration information for the management policy.

[0151] The application list contains information about applications 6 installed on terminal device 101 and control unit 7, corresponding to user identification information. For example, it is a list describing the identification information of application 6 (application name, application ID) and the application version.

[0152] The present invention is not limited to the embodiments described above, and various modifications are possible within the scope of the claims. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention.

[0153] (Note) From the above embodiments, the inventions claimed below can be extracted.

[0154] (Claim 1) A system comprising a measuring unit for measuring a sample and an imaging unit for imaging blood cells in the sample, First control software for controlling the measurement unit, A first data management software that manages first data relating to the measurement unit, Second control software for controlling the imaging unit, Second data management software manages blood cell images of blood cells in a sample captured by the imaging unit and second data including metadata of the blood cell images, The system includes an interface for allowing application software that can be added to the system to utilize the first data and the second data, The interface allows the application software to utilize the second data, which includes the metadata indicating the classification of the cell types of the blood cells. The application software added to the system extends the system's functionality to include the ability to display multiple classification candidates based on the metadata, which includes multiple classification candidates for the blood cells. system.

[0155] (Claim 2) The interface allows the application software to utilize the second data, which includes metadata indicating the plurality of classification candidates classified by image analysis of the blood cell image. The system according to claim 1.

[0156] (Claim 3) The interface allows the application software to use the second data, which includes the metadata. The application software extends the functionality of the system by displaying the multiple classification candidates in relation to the classification probability of each of the multiple classification candidates, based on the metadata. The system according to claim 1.

[0157] (Claim 4) The interface allows the application software to use the second data associated with the identification information of the sample, where the plurality of metadata are used. The system according to claim 1.

[0158] (Claim 5) The interface allows the application software to utilize second data, each of the plurality of metadata and plurality of blood cell images, which is associated with identification information about the sample. The system according to claim 1.

[0159] (Claim 6) The interface allows the application software to utilize second data, each of which is associated with identification information about the sample, including a plurality of metadata, a plurality of blood cell images, and a plurality of image IDs that distinguish each of the plurality of blood cell images. The system according to claim 1.

[0160] (Claim 7) The interface allows the application software to utilize the first data and second data associated with the identification information of the sample, each of the multiple metadata, multiple blood cell images, and hematology test results of the sample. The system according to claim 1.

[0161] (Claim 8) The interface allows the application software to utilize the first and second data, each of which is associated with identification information about the sample, and which is associated with a plurality of metadata, a plurality of blood cell images, the hematology test results of the sample, and information about the subject's attributes. The system according to claim 1.

[0162] (Claim 9) The interface allows the application software to utilize the first data and second data associated with the identification information of the sample, each of the multiple metadata, multiple blood cell images, and information about platelets based on the metadata. The system according to claim 1.

[0163] (Claim 10) The interface allows the application software to utilize the second data, each of which the metadata and the blood cell image are associated with the identification information relating to the sample. The application software extends the functionality of the system to include the ability to display the multiple classification candidates associated with the blood cell image. The system according to claim 1.

[0164] (Claim 11) The interface allows the application software to utilize the second data, each of which the metadata and the blood cell image are associated with the identification information relating to the sample. The application software extends the functionality of the system to include the ability to enlarge and display the blood cell images associated with the multiple classification candidates. The system according to claim 1.

[0165] (Claim 12) The interface allows the application software to utilize the second data, each of which the metadata and the blood cell image are associated with the identification information relating to the sample. The application software extends the functionality of the system by displaying the multiple classification candidates based on the results of comparing a pre-set rule with the metadata. The system according to claim 1.

[0166] (Claim 13) The interface allows the application software to utilize the second data, each of which the metadata and the blood cell image are associated with the identification information relating to the sample. The application software extends the functionality of the system by displaying the multiple classification candidates based on the metadata compared with a plurality of pre-set rules. The system according to claim 1.

[0167] (Claim 14) The interface allows the application software to utilize the second data, each of which the metadata and the blood cell image are associated with the identification information relating to the sample. The application software extends the functionality of the system to include the ability to accept the setting of rules for the multiple classification candidates. The system according to claim 1.

[0168] (Claim 15) The interface allows the application software to utilize the second data, each of which the metadata and the blood cell image are associated with the identification information relating to the sample. The aforementioned application software extends the functionality of the system to include the ability to display a reference image for comparison of cells included in the blood cell image. The system according to claim 1.

[0169] (Claim 16) The interface allows the application software to utilize the second data, each of which the metadata and the blood cell image are associated with the identification information relating to the sample. The aforementioned application software extends the functionality of the system to include the display of a ruler indicating an indicator of the size of cells included in the blood cell image. The system according to claim 1.

[0170] (Claim 17) The interface allows the application software to utilize the second data, each of which the metadata and the blood cell image are associated with the identification information relating to the sample. The application software extends the functionality of the system to include the ability to display the multiple classification candidates based on predetermined classification criteria. The system according to claim 1.

[0171] (Claim 18) The interface allows the application software to use the second data, which includes an image ID that distinguishes each of the multiple blood cell images and the multiple blood cell images associated with the image ID. The application software extends the functionality of the system to include the ability to specify each of the multiple pieces of metadata used via the interface based on the image ID. The system according to claim 1.

[0172] (Claim 19) The interface allows the application software to utilize the second data, which includes metadata for each of the multiple blood cell images. The application software extends the functionality of the system by displaying statistical information about the cells contained in each of the multiple blood cell images for each attribute of the cell, and by modifying the statistical information in accordance with the modification of the metadata. The system according to claim 1.

[0173] (Claim 20) The interface causes the application software to use the data based on predetermined rules. The system according to claim 1.

[0174] (Claim 21) The interface allows the multiple types of application software to utilize the data based on predetermined rules common to the multiple types of application software that provide different functions. The system according to claim 1.

[0175] (Claim 22) The interface provides the application software with a response corresponding to the request in response to a request from the application software. The system according to claim 1.

[0176] (Claim 23) The interface causes the application software to use the data based on a command created by the application software in accordance with predetermined rules. The system according to claim 1.

[0177] (Claim 24) The interface causes the application software to utilize at least one of the following based on a command created by the application software in accordance with predetermined rules: the data relating to the measurement unit, the data relating to the measurement operation by the measurement unit, the data relating to the maintenance of the measurement unit, and the data relating to the operation of the measurement unit. The system according to claim 1.

[0178] (Claim 25) The interface causes the application software to perform at least one of the following actions based on a command created by the application software in accordance with predetermined rules: acquiring the data, registering the data, updating the data, or deleting the data. The system according to claim 1.

[0179] (Claim 26) The interface allows the multiple types of application software to use the data based on predetermined rules common to the multiple types of application software that run on each of the multiple types of operating systems. The system according to claim 1.

[0180] (Claim 27) The data management software manages the data based on classification according to the type of data. The system according to claim 1.

[0181] (Claim 28) The interface causes the application software to use the data based on predetermined rules. The data management software manages the data based on the classification corresponding to the predetermined rules. The system according to claim 1.

[0182] (Claim 29) The system comprises a sample measuring device including the measurement unit, the control software, and the data management software. The interface causes the application software to utilize the data based on a plurality of predetermined rules corresponding to each type of sample measuring device. The system according to claim 1.

[0183] (Claim 30) The system comprises a sample measuring device including the measurement unit, the control software, and the data management software. The aforementioned specimen measuring device is certified as a medical device. The system according to claim 1.

[0184] (Claim 31) The interface allows the application software, which is a non-medical device, to utilize the data. The system according to claim 1.

[0185] (Claim 32) The control software and the data management software are software independent of the application software. The system according to claim 1.

[0186] (Claim 33) The measurement unit includes a sample processing unit for preparing a measurement sample based on the sample and reagent, and a detection unit for measuring the prepared measurement sample. The control software, in cooperation with the data management software, controls the operation of the sample processing unit and the detection unit. The data management software manages the data, including the measurement results obtained by the operation of the sample processing unit and the detection unit. The system according to claim 1.

[0187] (Claim 34) The measurement unit includes a sample processing unit for preparing a measurement sample based on the sample and reagent, and a detection unit for measuring the prepared measurement sample. The control software, in cooperation with the data management software, controls the operation of the sample processing unit and the detection unit. The data management software manages the data, including the measurement results obtained by the operation of the sample processing unit and the detection unit. The control software and the data management software are software independent of the application software. The system according to claim 1.

[0188] (Claim 35) The measurement unit includes a sample processing unit for preparing a measurement sample based on the sample and reagent, and a detection unit for measuring the prepared measurement sample. The control software, in cooperation with the data management software, controls the operation of the sample processing unit and the detection unit. The data management software manages the data, including the measurement results obtained by the operation of the sample processing unit and the detection unit. The control software and the data management software are software independent of the application software. The data management software can cooperate with the application software via the interface. The system according to claim 1.

[0189] (Claim 36) The system comprises a sample measuring device including the measurement unit, the control software, and the data management software. The measurement unit includes a sample processing unit for preparing a measurement sample based on the sample and reagent, and a detection unit for measuring the prepared measurement sample. The control software, in cooperation with the data management software, controls the operation of the sample processing unit and the detection unit. The data management software manages the data, including the measurement results obtained by the operation of the sample processing unit and the detection unit. The data management software can cooperate with the application software via the interface, The measurement unit, the control software, and the data management software are components of a certified medical device. The control software and the data management software are software independent of the application software. The system according to claim 1.

[0190] (Claim 37) The system comprises a sample measuring device including the measurement unit, the control software, and the data management software. The measurement unit includes a sample processing unit for preparing a measurement sample based on the sample and reagent, and a detection unit for measuring the prepared measurement sample. The control software, in cooperation with the data management software, controls the operation of the sample processing unit and the detection unit. The data management software manages the data, including the measurement results obtained by the operation of the sample processing unit and the detection unit. The data management software can cooperate with the application software via the interface, The measurement unit, the control software, and at least a portion of the data management software provide functions corresponding to the intended use of the specimen measuring device certified as a medical device. The functionality of the system is extended by application software capable of providing functions different from those corresponding to the intended use. The system according to claim 1. The measurement unit includes a sample processing unit for preparing a measurement sample based on the sample and reagents. It includes a unit and a detection unit for measuring the prepared measurement sample, The control software, in cooperation with the data management software, controls the operation of the sample processing unit and the detection unit. The data management software manages the data, including the measurement results obtained by the operation of the sample processing unit and the detection unit. The system according to claim 1.

[0191] (Claim 38) The control software controls the operation of the sample processing unit and the detection unit, Control of the aspiration operation of a liquid containing at least one of the aforementioned sample and reagent, A control system that mixes the aforementioned sample and the aforementioned reagent to prepare a measurement sample. Control to cause the measurement sample to be detected by the detection unit, and The detection unit detects at least one of the optical information and electrical signals related to the measurement sample, and the control unit analyzes the measurement result based on the detected result. including at least one of the following: The system according to any one of claims 35 to 39.

[0192] (Claim 39) A measurement unit for measuring a sample; first control software for controlling the measurement unit; first data management software for managing first data relating to the measurement unit that operates based on the control software; an imaging unit for imaging blood cells in the sample; second control software for controlling the imaging unit; and second data management software for managing second data relating to the imaging unit that operates based on the control software. Application software used in a system that includes, A request unit requests the interface to use the first data and the second data, which include a blood cell image of blood cells captured in the sample and metadata indicating the classification of the cell types of the blood cells. A response receiving unit that receives a response corresponding to the aforementioned request, Application software including, as a function for extending the system, a function providing unit that provides a function to display the plurality of classification candidates based on the metadata, which includes the plurality of classification candidates of the blood cells, based on the use of the first data and the second data.

[0193] (Claim 40) The requesting unit requests the interface to use the second data, which includes the metadata indicating the plurality of classification candidates classified by image analysis of the blood cell image. The application software according to claim 39.

[0194] (Claim 41) The requesting unit requests the interface to use the second data, which includes the metadata. The function-providing unit provides a function to display the plurality of classification candidates in relation to the classification probability of each of the plurality of classification candidates. The application software according to claim 39.

[0195] (Claim 42) The request unit requests the interface to use the second data in which a plurality of the meta-informations are associated with the identification information regarding the specimen. The application software according to claim 39.

[0196] (Claim 43) The request unit requests the interface to use the second data in which each of the plurality of the meta-informations and each of the plurality of the blood cell images are associated with the identification information regarding the specimen. The application software according to claim 39.

[0197] (Claim 44) The request unit requests the interface to use the second data including each of the plurality of the meta-informations, each of the plurality of the blood cell images, and each of the plurality of the image IDs for distinguishing each of the plurality of the blood cell images, where each is associated with the identification information regarding the specimen. The application software according to claim 39.

[0198] (Claim 45) The request unit requests the interface to use the first data and the second data in which each of the plurality of the meta-informations, each of the plurality of the blood cell images, and the hematology test result of the specimen are associated with the identification information regarding the specimen. The application software according to claim 39.

[0199] (Claim 46) The request unit requests the interface to use the first data and the second data in which each of the plurality of the meta-informations, each of the plurality of the blood cell images, the hematology test result of the specimen, and the information regarding the attributes of the subject are associated with the identification information regarding the specimen. The application software according to claim 39.

[0200] (Claim 47) The requesting unit requests the interface to use the first data and the second data associated with the identification information of the sample, each of the plurality of metadata, the plurality of blood cell images, and the platelet information based on the metadata. The application software according to claim 39.

[0201] (Claim 48) The requesting unit requests the interface to use the second data, each of which is associated with the identification information relating to the sample, the metadata and the blood cell image. The function-providing unit provides a function to display the plurality of classification candidates associated with the blood cell image. The application software according to claim 39.

[0202] (Claim 49) The requesting unit requests the interface to use the second data, each of which is associated with the identification information relating to the sample, the metadata and the blood cell image. The function-providing unit provides a function to enlarge and display the blood cell images associated with the plurality of classification candidates. The application software according to claim 39.

[0203] (Claim 50) The requesting unit requests the interface to use the second data, each of which is associated with the identification information relating to the sample, the metadata and the blood cell image. The function providing unit provides a function to display the multiple classification candidates based on the result of comparing a pre-set rule with the metadata. The application software according to claim 39.

[0204] (Claim 51) The requesting unit requests the interface to use the second data, each of which is associated with the identification information relating to the sample, the metadata and the blood cell image. The function providing unit provides a function to display the multiple classification candidates based on the metadata compared with a plurality of pre-set rules. The application software according to claim 39.

[0205] (Claim 52) The requesting unit requests the interface to use the second data, each of which is associated with the identification information relating to the sample, the metadata and the blood cell image. The function providing unit provides a function to accept the setting of rules regarding the plurality of classification candidates. The application software according to claim 39.

[0206] (Claim 53) The requesting unit requests the interface to use the second data, each of which is associated with the identification information relating to the sample, the metadata and the blood cell image. The aforementioned function-providing unit provides a function to display a reference image for comparison of cells included in the blood cell image. The application software according to claim 39.

[0207] (Claim 54) The requesting unit requests the interface to use the second data, each of which is associated with the identification information relating to the sample, the metadata and the blood cell image. The function-providing unit provides a function to display a ruler that indicates an indicator of the size of cells included in the blood cell image. The application software according to claim 39.

[0208] (Claim 55) The requesting unit requests the interface to use the second data, each of which is associated with the identification information relating to the sample, the metadata and the blood cell image. The function-providing unit provides a function to display the multiple classification candidates based on predetermined classification criteria. The application software according to claim 39.

[0209] (Claim 56) The request unit requests the interface to use the second data in which each of the meta information and the blood cell image is associated with the identification information regarding the specimen. The function providing unit provides a function of designating each of a plurality of the meta information to be used via the interface based on the image ID. The application software according to claim 39.

[0210] (Claim 57) The request unit requests the interface to use the second data including the meta information of each of a plurality of the blood cell images. The function providing unit provides a function of displaying statistical information regarding cells included in each of the plurality of blood cell images for each attribute of the cells and correcting the statistical information according to the correction of the meta information. The application software according to claim 39.

[0211] [Supplementary Note] The present invention also includes the following aspects.

[0212] [Aspect 1] A system including a measurement unit for measuring a specimen and an imaging unit for imaging blood cells in the specimen, first control software for controlling the measurement unit, first data management software for managing first data regarding the measurement unit, second control software for controlling the imaging unit, second data management software for managing second data including a blood cell image obtained by imaging blood cells in a specimen by the imaging unit and meta information of the blood cell image, and an interface for causing application software addable to the system to use the first data and the second data. The interface allows the application software to utilize the second data, which includes the metadata indicating the classification of the cell types of the blood cells. The application software added to the system extends the system's functionality to include the ability to display multiple classification candidates based on the metadata, which includes multiple classification candidates for the blood cells. system.

[0213] [Aspect 2] The interface allows the application software to utilize the second data, which includes metadata indicating the plurality of classification candidates classified by image analysis of the blood cell image. The system described in Embodiment 1.

[0214] [Aspect 3] The interface allows the application software to use the second data, which includes the metadata. The application software extends the functionality of the system by displaying the multiple classification candidates in relation to the classification probability of each of the multiple classification candidates, based on the metadata. The system described in Embodiment 1.

[0215] [Aspect 4] The interface allows the application software to use the second data associated with the identification information of the sample, where the plurality of metadata are used. The system described in Embodiment 1.

[0216] [Aspect 5] The interface allows the application software to utilize second data, each of the plurality of metadata and plurality of blood cell images, which is associated with identification information about the sample. The system described in Embodiment 1.

[0217] [Aspect 6] The interface allows the application software to utilize second data, each of which is associated with identification information about the sample, including a plurality of metadata, a plurality of blood cell images, and a plurality of image IDs that distinguish each of the plurality of blood cell images. The system described in Embodiment 1.

[0218] [Aspect 7] The interface allows the application software to utilize the first data and second data associated with the identification information of the sample, each of the multiple metadata, multiple blood cell images, and hematology test results of the sample. The system described in Embodiment 1.

[0219] [Aspect 8] The interface allows the application software to utilize the first and second data, each of which is associated with identification information about the sample, and which is associated with a plurality of metadata, a plurality of blood cell images, the hematology test results of the sample, and information about the subject's attributes. The system described in Embodiment 1.

[0220] [Aspect 9] The interface allows the application software to utilize the first data and second data associated with the identification information of the sample, each of the multiple metadata, multiple blood cell images, and information about platelets based on the metadata. The system described in Embodiment 1.

[0221] [Aspect 10] The interface allows the application software to utilize the second data, each of which the metadata and the blood cell image are associated with the identification information relating to the sample. The application software extends the functionality of the system to include the ability to display the multiple classification candidates associated with the blood cell image. The system described in Embodiment 1.

[0222] [Aspect 11] The interface allows the application software to utilize the second data, each of which the metadata and the blood cell image are associated with the identification information relating to the sample. The application software extends the functionality of the system to include the ability to enlarge and display the blood cell images associated with the multiple classification candidates. The system described in Embodiment 1.

[0223] [Aspect 12] The interface allows the application software to utilize the second data, each of which the metadata and the blood cell image are associated with the identification information relating to the sample. The application software extends the functionality of the system by displaying the multiple classification candidates based on the results of comparing a pre-set rule with the metadata. The system described in Embodiment 1.

[0224] [Aspect 13] The interface allows the application software to utilize the second data, each of which the metadata and the blood cell image are associated with the identification information relating to the sample. The application software extends the functionality of the system by displaying the multiple classification candidates based on the metadata compared with a plurality of pre-set rules. The system described in Embodiment 1.

[0225] [Aspect 14] The interface allows the application software to utilize the second data, each of which the metadata and the blood cell image are associated with the identification information relating to the sample. The application software extends the functionality of the system to include the ability to accept the setting of rules for the multiple classification candidates. The system described in Embodiment 1.

[0226] [Aspect 15] The interface allows the application software to utilize the second data, each of which the metadata and the blood cell image are associated with the identification information relating to the sample. The aforementioned application software extends the functionality of the system to include the ability to display a reference image for comparison of cells included in the blood cell image. The system described in Embodiment 1.

[0227] [Aspect 16] The interface allows the application software to utilize the second data, each of which the metadata and the blood cell image are associated with the identification information relating to the sample. The aforementioned application software extends the functionality of the system to include the display of a ruler indicating an indicator of the size of cells included in the blood cell image. The system described in Embodiment 1.

[0228] [Aspect 17] The interface allows the application software to utilize the second data, each of which the metadata and the blood cell image are associated with the identification information relating to the sample. The application software extends the functionality of the system to include the ability to display the multiple classification candidates based on predetermined classification criteria. The system described in Embodiment 1.

[0229] [Aspect 18] The interface allows the application software to use the second data, which includes an image ID that distinguishes each of the multiple blood cell images and the multiple blood cell images associated with the image ID. The application software extends the functionality of the system to include the ability to specify each of the multiple pieces of metadata used via the interface based on the image ID. The system described in Embodiment 1.

[0230] [Aspect 19] The interface allows the application software to utilize the second data, which includes metadata for each of the multiple blood cell images. The application software extends the functionality of the system by displaying statistical information about the cells contained in each of the multiple blood cell images for each attribute of the cell, and by modifying the statistical information in accordance with the modification of the metadata. The system described in Embodiment 1. [Explanation of Symbols]

[0231] 1 Sample measurement system 2 Measurement unit 3 Control software 4, 4A Data management software 5, 5A Interface 6 Application software 11 Sample measurement device 12 Imaging device 21 Sample processing unit 22 Detection unit 61 Function provision unit 62 Request unit 63 Response reception unit 2000 Imaging unit C Command R Predefined rules

Claims

1. Application software used in a system including: a measurement unit for measuring a sample; first control software for controlling the measurement unit; first data management software for managing first data relating to the measurement unit that operates based on the control by the first control software; an imaging unit for imaging blood cells in the sample; second control software for controlling the imaging unit; and second data management software for managing second data relating to the imaging unit that operates based on the control by the second control software. A request unit requests the interface to use the first data and the second data, which include a blood cell image of the blood cells in the sample and metadata indicating the classification of the cell types of the blood cells. A response receiving unit that receives a response corresponding to the aforementioned request, As a function to extend the system, the system includes a function providing a function that displays the plurality of classification candidates based on the metadata, which includes the plurality of classification candidates of the blood cells, based on the use of the first data and the second data, Application software.

2. The requesting unit requests the interface to use the second data, which includes the metadata indicating the plurality of classification candidates classified by image analysis of the blood cell image. The application software according to claim 1.

3. The requesting unit requests the interface to use the second data, which includes the metadata. The function-providing unit provides a function to display the plurality of classification candidates in relation to the classification probability of each of the plurality of classification candidates. The application software according to claim 1.

4. The requesting unit requests the interface to use the second data associated with the identification information relating to the sample, based on the plurality of metadata. The application software according to claim 1.

5. The requesting unit requests the interface to use the second data associated with the identification information relating to the sample, each of the plurality of metadata and the plurality of blood cell images. The application software according to claim 1.

6. The requesting unit requests the interface to use the second data, which includes a plurality of metadata, a plurality of blood cell images, and a plurality of image IDs that distinguish each of the plurality of blood cell images, each of which is associated with identification information relating to the sample. The application software according to claim 1.

7. The requesting unit requests the interface to use the first data and the second data, each of which is associated with identification information relating to the sample, based on the plurality of metadata, the plurality of blood cell images, and the hematology test results of the sample. The application software according to claim 1.

8. The requesting unit requests the interface to use the first data and the second data associated with the identification information of the sample, each of the plurality of metadata, plurality of blood cell images, hematology test results of the sample, and information on the attributes of the subject. The application software according to claim 1.

9. The requesting unit requests the interface to use the first data and the second data associated with the identification information of the sample, each of the plurality of metadata, the plurality of blood cell images, and the platelet information based on the metadata. The application software according to claim 1.

10. The requesting unit requests the interface to use the second data, each of which is associated with the identification information relating to the sample, the metadata and the blood cell image. The function-providing unit provides a function to display the plurality of classification candidates associated with the blood cell image. The application software according to claim 1.

11. The requesting unit requests the interface to use the second data, each of which is associated with the identification information relating to the sample, the metadata and the blood cell image. The function-providing unit provides a function to enlarge and display the blood cell images associated with the plurality of classification candidates. The application software according to claim 1.

12. The requesting unit requests the interface to use the second data, each of which is associated with the identification information relating to the sample, the metadata and the blood cell image. The function providing unit provides a function to display the multiple classification candidates based on the result of comparing a pre-set rule with the metadata. The application software according to claim 1.

13. The requesting unit requests the interface to use the second data, each of which is associated with the identification information relating to the sample, the metadata and the blood cell image. The function providing unit provides a function to display the multiple classification candidates based on the metadata compared with a plurality of pre-set rules. The application software according to claim 1.

14. The requesting unit requests the interface to use the second data, each of which is associated with the identification information relating to the sample, the metadata and the blood cell image. The application software according to claim 1, wherein the function providing unit provides a function for receiving the setting of rules relating to the plurality of classification candidates.

15. The requesting unit requests the interface to use the second data, each of which is associated with the identification information relating to the sample, the metadata and the blood cell image. The aforementioned function-providing unit provides a function to display a reference image for comparison of cells included in the blood cell image. The application software according to claim 1.

16. The requesting unit requests the interface to use the second data, each of which is associated with the identification information relating to the sample, the metadata and the blood cell image. The function-providing unit provides a function to display a ruler that indicates an indicator of the size of cells included in the blood cell image. The application software according to claim 1.

17. The requesting unit requests the interface to use the second data, each of which is associated with the identification information relating to the sample, the metadata and the blood cell image. The function-providing unit provides a function to display the multiple classification candidates based on predetermined classification criteria. The application software according to claim 1.

18. The requesting unit requests the interface to use the second data, each of which is associated with the identification information relating to the sample, the metadata and the blood cell image. The function providing unit provides a function to specify each of the multiple pieces of metadata used via the interface based on the image ID. The application software according to claim 1.

19. The requesting unit requests the interface to use the second data, which includes metadata for each of the multiple blood cell images. The function-providing unit provides a function to display statistical information about cells included in each of the plurality of blood cell images for each attribute of the cell, and to modify the statistical information in accordance with the modification of the metadata. The application software according to claim 1.

Images