Image processing method, device, medium and program product

CN122800145APending Publication Date: 2026-09-22GUANGZHOU HUAYIN HEALTH MEDICAL GRP CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610939498.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-06-26
Publication Date
2026-09-22

AI Technical Summary

Technical Problem

[0004]本发明提供了一种图像处理方法、设备、介质及程序产品,以解决现有病理图像展示方法存在用户体验差的问题

Benefits of technology

[0010]本发明实施例提供的技术方案,由于预览地址基于病理标识以及病理标识对应设备标识确定,因此预览地址可使上层业务忽略不同设备标识对应设备所生成图像之间的底层存储协议、图像格式、传输机制,只需通过统一的预览地址即可展示相应切片图像;截图回传函数可将用户在浏览结果上的截图坐标转换为实际截取坐标,流式地址用于访问相应切片图像;这样处理器即可通过流式地址访问相应切片图像,然后基于实际截图坐标对相应切片图像执行截图处理,得到目标截图结果,实现了无需关注云端的底层图像存储机制,即可通过预览结果展示切片图像,以及无需展示实际切片图像即可完成实际切片图像的截图操作,使得用户无需频繁切换与每个设备标识对应的图像软件,显著提高了用户的体验水平。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122800145A_ABST
    Figure CN122800145A_ABST
Patent Text Reader

Abstract

Embodiments of the present application disclose an image processing method, device, medium and program product, and belong to the field of medical image processing. The method comprises: determining a pathology identifier in response to a viewing request, and displaying a preview result combination corresponding to the pathology identifier in the cloud; the preview result is determined based on a preview address under a slice image identifier corresponding to a corresponding slice image; the preview address is determined based on the pathology identifier and a device identifier corresponding to the pathology identifier; in response to a screenshot request, obtaining a screenshot coordinate for the current preview result, determining actual screenshot coordinates corresponding to the screenshot coordinate based on a screenshot return function under a target slice image identifier, the target slice image identifier being a slice image identifier corresponding to the current preview result in the cloud; and performing screenshot processing on a slice image corresponding to the target slice image identifier based on the actual screenshot coordinates and a streaming address under the target slice image identifier, to obtain a target screenshot result. The embodiments of the present application can improve the viewing experience of users.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of computer technology, and in particular to an image processing method, device, medium and program product. Background Technology

[0002] Full-field digital slide (WSI) technology digitizes glass slides using a high-precision scanner, generating ultra-large-capacity (typically several gigabytes to tens of gigabytes) medical image files, i.e., slide images. In modern digital pathology departments, hospitals typically purchase digital slide scanners from multiple vendors, and these devices store massive amounts of slide images in their own independent cloud slide libraries or dedicated image servers.

[0003] The slide images produced by scanners from different manufacturers have different formats and calling protocols. Hospital pathology information systems (PIS / LIS) often only save the local associated identifier of "digital pathology number", and cannot directly and uniformly preview the slide files scattered in the cloud of various manufacturers. Doctors need to switch frequently between different dedicated software when reading the slides, resulting in a poor experience. Summary of the Invention

[0004] This invention provides an image processing method, device, medium, and program product to solve the problem of poor user experience in existing pathological image display methods.

[0005] According to one aspect of the present invention, an image processing method is provided, the method comprising: In response to an image viewing request, a pathological identifier is determined, and a combination of preview results corresponding to the pathological identifier is displayed in the cloud. The combination of preview results includes preview results of one or more slide images corresponding to the pathological identifier. The preview results are determined based on the preview address under the slide image identifier corresponding to the slide image. The preview address is determined based on the pathological identifier and the device identifier corresponding to the pathological identifier. In response to a screenshot request, the screenshot coordinates for the current preview result are obtained, and the actual cropping coordinates corresponding to the screenshot coordinates are determined based on the screenshot return function under the target slice image identifier. The target slice image identifier is the slice image identifier in the cloud that corresponds to the current preview result. Based on the actual capture coordinates and the streaming address under the target slice image identifier, the slice image corresponding to the target slice image identifier is captured to obtain the target screenshot result.

[0006] According to another aspect of the present invention, an image processing apparatus is provided, the apparatus comprising: The display module is used to respond to an image viewing request to determine a pathological identifier and display a combination of preview results in the cloud corresponding to the pathological identifier. The combination of preview results includes preview results of one or more slide images corresponding to the pathological identifier. The preview results are determined based on the preview address under the slide image identifier corresponding to the corresponding slide image. The preview address is determined based on the pathological identifier and the device identifier corresponding to the pathological identifier. The coordinate determination module is used to respond to the screenshot request, obtain the screenshot coordinates for the current preview result, and determine the actual cropping coordinates corresponding to the screenshot coordinates based on the screenshot return function under the target slice image identifier. The target slice image identifier is the slice image identifier in the cloud that corresponds to the current preview result. The screenshot module is used to perform screenshot processing on the slice image corresponding to the target slice image identifier based on the actual capture coordinates and the streaming address under the target slice image identifier, so as to obtain the target screenshot result.

[0007] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising: One or more processors; Storage device for storing one or more programs. When one or more programs are executed by one or more processors, the one or more processors implement the image processing method as described in any embodiment of the present invention.

[0008] According to another aspect of the present invention, a computer-readable storage medium is provided, which stores computer instructions for causing a processor to execute and implement the image processing method described in any embodiment of the present invention.

[0009] According to another aspect of the present invention, a computer program product is provided, which, when executed by a processor, implements the image processing method as described in any embodiment of the present invention.

[0010] The technical solution provided by this invention allows upper-layer services to ignore the underlying storage protocols, image formats, and transmission mechanisms between images generated by devices corresponding to different device identifiers, since the preview address is determined based on the pathology identifier and the corresponding device identifier. The upper-layer address allows the display of the corresponding slice image simply through a unified preview address. The screenshot return function converts the screenshot coordinates on the browsing results into actual capture coordinates, and the streaming address is used to access the corresponding slice image. In this way, the processor can access the corresponding slice image through the streaming address and then perform screenshot processing on the corresponding slice image based on the actual screenshot coordinates to obtain the target screenshot result. This achieves the ability to display slice images through preview results without needing to pay attention to the underlying image storage mechanism in the cloud, and to complete the screenshot operation of the actual slice image without displaying the actual slice image. This significantly improves the user experience by eliminating the need for users to frequently switch between image software corresponding to each device identifier.

[0011] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1 A schematic flowchart of the image processing method provided in an embodiment of the present invention; Figure 2 This is another schematic flowchart of the image processing method provided in an embodiment of the present invention; Figure 3A This is a schematic diagram of the structure of an image processing apparatus provided in an embodiment of the present invention; Figure 3B This is another schematic diagram of the image processing apparatus provided in an embodiment of the present invention; Figure 3C This is another schematic diagram of the image processing apparatus provided in an embodiment of the present invention; Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0014] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0015] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0016] Figure 1 This is a flowchart illustrating the image processing method provided in an embodiment of the present invention. This embodiment is applicable to situations where the screenshot experience of pathological images generated by different devices is improved by using a combination of preview address, streaming address, and screenshot return function. This method can be executed by an image processing device, which can be implemented in hardware and / or software and can be configured in electronic devices such as computers or servers. Figure 1 As shown, the method in this embodiment includes: S110. In response to the image viewing request, determine the pathology identifier and display the preview result combination corresponding to the pathology identifier in the cloud. The preview result combination includes the preview results of one or more slide images corresponding to the pathology identifier. The preview result is determined based on the preview address under the slide image identifier corresponding to the corresponding slide image. The preview address is determined based on the pathology identifier and the device identifier corresponding to the pathology identifier.

[0017] A view request is a request to review a slice of an image. It is generated based on a user's corresponding triggering action, such as clicking or touching a corresponding control.

[0018] A pathology identifier is a unique number assigned by a hospital to a patient for a single pathological examination or biopsy, used to identify a complete pathological diagnostic event.

[0019] During a single pathological examination, a patient may have multiple samples taken, each used for different pathological tests. Furthermore, during the examination, a single sample is prepared into multiple slides, and each slide is electronically backed up as a slide image. Therefore, one pathological identifier corresponds to one or more sample identifiers, one sample identifier corresponds to one or more slide image identifiers, and one slide image identifier corresponds to one slide image.

[0020] Moreover, the pathological examination equipment used for the above-mentioned samples in different pathological examination processes is usually different, and the pathological examination equipment used may even come from different manufacturers. Therefore, the storage format, streaming address and retrieval method of the slide images generated by these devices will be significantly different.

[0021] In one embodiment, when a slice image is detected to be generated, a preview address, a streaming address, and a screenshot return function are determined based on the pathological identifier and device identifier corresponding to the slice image, and the preview address, streaming address, and screenshot return function are all bound to the slice image identifier of the slice image.

[0022] In one embodiment, a first cloud image identifier combination corresponding to a target identifier combination is determined, the target identifier combination including pathology identifiers and device identifiers; the preview address, the streaming address, and the screenshot return function are attached to each slice image identifier in the first cloud image identifier combination.

[0023] Specifically, a factory pattern is used to dynamically attach a standardized preview address, streaming address, and closure-encapsulated screenshot return function to each slice image identifier. This shields the underlying differences between multiple vendors on a unified web interface, enabling efficient integrated viewing of ultra-large medical slices. This embodiment dynamically converts the large underlying files in the cloud into streaming addresses (sectionUrl) and dedicated web preview addresses (sectionPreviewUrl) suitable for web-based streaming, based on the proprietary protocols of different vendors. Since different pathology testing devices have different coordinate systems and screenshot APIs, this embodiment dynamically injects a closure-encapsulated screenshot return function (getShotFn) into each slice image identifier. This screenshot return function is used to directly request the corresponding cloud device via coordinate indexing when dragging and zooming of the slice image on the web interface is detected and a lesion feature field is identified. The function can then capture and return a high-resolution slice of that feature field in real time.

[0024] Regarding the first cloud-based image identifier combination: Based on the target identifier and device identifier, the slice image identifiers in the cloud are searched, and all the found slice image identifiers are used as the first cloud-based image identifier combination. Alternatively, the examination device is configured such that the generated slice images are stored in a file containing its own identifier and a pathological identifier, and all slice image identifiers in that file are used as the first cloud-based image identifier combination.

[0025] After the first cloud image identifier combination is determined, the corresponding preview address, streaming address and screenshot return function are attached to each image combination in the first cloud image identifier combination.

[0026] The streaming address is used to access the corresponding slice image in the cloud.

[0027] The preview address is used to obtain a preview of the corresponding slice image in the cloud.

[0028] The screenshot return function is used to determine the actual cropping coordinates for the corresponding slice image based on the cropping range shown in the preview result.

[0029] Specifically, a custom `groupBy` utility function is invoked, using the combination of the slide's "pathology identifier (wsiNo)" and "device identifier (wsiZoomerName)" as a joint key to categorize and group the locally disorganized slide image identifiers. This ensures that cloud-based slide library resources can be accurately located by batch and by device in subsequent iterations. The grouping strategy of "pathology identifier + device identifier" and the combination URL (combinationUrl) routing mechanism can standardize the private protocols of multiple large-scale pathology testing equipment from different manufacturers. This allows the PIS system to seamlessly integrate and view multi-source slide images without needing to concern itself with the underlying image parsing logic, underlying storage protocols, image formats, or transmission mechanisms. It only needs to call the uniformly mounted preview address.

[0030] S120. In response to the screenshot request, obtain the screenshot coordinates for the current preview result, and determine the actual cropping coordinates corresponding to the screenshot coordinates based on the screenshot return function under the target slice image identifier. The target slice image identifier is the slice image identifier in the cloud that corresponds to the current preview result.

[0031] If a user wants to take a screenshot while viewing the preview results of each slice image, a screenshot operation is triggered, generating a screenshot request. The processor responds to this screenshot request by obtaining the screenshot coordinates selected by the user in the current preview result. Then, based on the screenshot postback function under the image identifier corresponding to the current preview result, it determines the actual cropping coordinates corresponding to these coordinates. The actual cropping coordinates are the coordinates applied to the corresponding slice image.

[0032] S130. Based on the actual capture coordinates and the streaming address under the target slice image identifier, perform screenshot processing on the slice image corresponding to the target slice image identifier to obtain the target screenshot result.

[0033] The system identifies the image identifier of the slice corresponding to the currently viewed result in the cloud, as well as the streaming address under that image identifier. Based on the streaming address, it accesses the slice image corresponding to that image identifier and uses the actual cropping coordinates to perform a screenshot process on the slice image to obtain the target screenshot result. This achieves the screenshot operation of a slice image without displaying the actual slice image.

[0034] The technical solution provided by this invention, since the preview address is determined based on the pathology identifier and the corresponding device identifier, allows upper-layer services to ignore the underlying storage protocols, image formats, and transmission mechanisms between images generated by devices corresponding to different device identifiers. The corresponding slice image can be displayed simply through a unified preview address. The screenshot return function converts the screenshot coordinates on the browsing results into actual capture coordinates, and the streaming address is used to access the corresponding slice image. In this way, the processor can access the corresponding slice image through the streaming address and then perform screenshot processing on the corresponding slice image based on the actual screenshot coordinates to obtain the target screenshot result. This achieves the ability to display slice images through preview results without needing to pay attention to the underlying image storage mechanism in the cloud. It enables efficient integrated image reading of ultra-large medical slices and allows screenshot operations of actual slice images to be completed without displaying the actual slice image. This significantly improves the user experience by eliminating the need for users to frequently switch image software corresponding to each device identifier.

[0035] Based on the foregoing embodiments, the method further includes: in response to a predetermined add operation, adding the target screenshot result to the current pathology report.

[0036] The current pathology report can be a pathology report for a specific sample under the current pathology identifier, or it can be a pathology report for the current pathology identifier.

[0037] Taking a pathology report for a specific sample under a current pathology identifier as an example, the pathology report needs to include at least two screenshots, which must come from different slide images. Therefore, after the target screenshot is determined, the user can add it to the current pathology report by dragging and dropping it; alternatively, they can add it through other move or copy trigger operations.

[0038] Figure 2This is another schematic flowchart of the image processing method provided in this embodiment of the invention. The technical solution of this embodiment can be combined with other embodiments; for the same or related parts, they can be described in conjunction with the descriptions of other embodiments, and will not be repeated here. Figure 2 As shown, the method includes: S2101. In response to the image viewing request, determine the pathology identifier, and determine the second cloud image identifier combination and the first local image identifier combination corresponding to the pathology identifier.

[0039] The second cloud-based image identifier group includes one or more slice image identifiers, and all of the one or more slice image identifiers are located in the cloud.

[0040] The first local image identifier group includes one or more slice image identifiers, and all of the one or more slice image identifiers are local.

[0041] S2102. Determine a second local image identifier combination that is the same as the second cloud image identifier combination based on the first local image identifier combination.

[0042] When a slice image in the cloud is deleted, its corresponding slice image identifier in the cloud also disappears, while its corresponding slice image identifier in the local memory is usually unaffected. Therefore, the second cloud image identifier combination is a subset of the first local image identifier combination.

[0043] Therefore, in one embodiment, the intersection of the first local image identifier combination and the second cloud image identifier combination is determined, and this intersection is taken as the second local image identifier combination. At this time, the second local image identifier combination is the same as the second cloud image identifier combination.

[0044] In another embodiment, for each slice image identifier in the first local image identifier group, if the slice image identifier exists in the second cloud image identifier group, then the slice image identifier is placed into the second local image identifier group.

[0045] It should be noted that if a slice image identifier exists locally but not in the cloud, it is an invalid slice image identifier. When an invalid slice image identifier is triggered to display the corresponding slice image or preview the result, a dead link problem will occur because the corresponding slice image does not exist in the cloud.

[0046] S2103. Display the preview results of the slice images corresponding to each slice image identifier in the cloud and the second local image identifier combination. The preview results are determined based on the preview address under the slice image identifier corresponding to the corresponding slice image. The preview address is determined based on the pathology identifier and the device identifier corresponding to the pathology identifier.

[0047] It is understandable that the cloud includes the slice image identifiers of each slice in the second local image identifier combination. Therefore, displaying the preview results of the slice images in the cloud that correspond to the slice image identifiers in the second local image identifier combination can avoid system errors caused by invalid local slice image identifiers, greatly improving the robustness of the system. An invalid slice image identifier is a slice image identifier that does not exist simultaneously in both the local and cloud environments.

[0048] S220. In response to the screenshot request, obtain the screenshot coordinates for the current preview result, and determine the actual cropping coordinates corresponding to the screenshot coordinates based on the screenshot return function under the target slice image identifier. The target slice image identifier is the slice image identifier in the cloud that corresponds to the current preview result.

[0049] S230. Based on the actual capture coordinates and the streaming address under the target slice image identifier, perform screenshot processing on the slice image corresponding to the target slice image identifier to obtain the target screenshot result.

[0050] The technical solution provided by this invention determines a second cloud image identifier combination and a first local image identifier combination corresponding to pathological identifiers; determines a second local image identifier combination that is the same as the second cloud image identifier combination based on the first local image identifier combination; displays preview results of slice images in the cloud corresponding to each slice image identifier in the second local image identifier combination; implements concurrent scheduling of cloud interfaces of various vendors to pull the latest cloud slice directory, i.e., the second cloud image identifier combination; by comparing the slice image identifiers of the first local image identifier combination and the second cloud image identifier combination, it achieves error prevention through intelligent sorting of slice image identifiers and automatic marking of "deleted" status, achieving the effect of two-way status alignment error prevention. In this way, by intelligently identifying slice image identifiers that have been cleaned or lost in the cloud and then intercepting the corresponding dead link access in advance, it effectively ensures the continuity of the medical diagnosis process and the stability of the software.

[0051] Based on the aforementioned embodiments, after determining the second local image identifier combination that is the same as the second cloud image identifier combination based on the first local image identifier combination, S2102 further includes: if the slice image identifier does not exist in the second cloud image identifier combination, then the slice image identifier is placed in the third local image identifier combination; correspondingly, while displaying the preview results of the slice images in the cloud that correspond to each slice image identifier in the second local image identifier combination, S2103 further includes: displaying each slice image identifier in the third local image identifier combination and the empty preview result identifier corresponding to each slice image identifier.

[0052] Specifically, if the slice image identifier is not present in the second cloud image identifier combination, it means that the slice image identifier does not exist in the cloud, that is, the slice image identifier has been deleted from the cloud. This means that the slice image identifier is an invalid slice image identifier, and therefore it will be added to the third local image identifier combination.

[0053] To better display the slice images corresponding to each slice image identifier to the user, this embodiment, while showing the preview results of the slice images corresponding to each slice image identifier in the cloud and the second local image identifier combination, also displays each slice image identifier in the third local image identifier combination and the empty preview result identifier corresponding to each slice image identifier. The empty preview result identifier can be the same predetermined image identifier, such as a gray pattern, or a corresponding deletion prompt message.

[0054] Based on the aforementioned embodiments, after the second local image identifier combination and the third local image identifier combination are determined, the second local image identifier combination and the third local image identifier combination are spliced ​​together to obtain a fourth local image identifier combination, and the slice image identifiers belonging to the third local image identifier combination in the fourth local image identifier combination carry an anomaly identifier; accordingly, during display, the preview results corresponding to each valid slice image identifier in the fourth local image identifier combination and the empty preview result identifiers corresponding to each invalid slice image identifier are displayed in the cloud, wherein the valid slice image identifier is a slice image identifier that does not carry the anomaly identifier, and the invalid slice image identifier is a slice image identifier that carries the anomaly identifier.

[0055] Specifically, the fourth local image identifier combination includes all elements from the second local image identifier combination and all elements from the third local image identifier combination, and the slice image identifiers belonging to the third local image identifier combination carry an anomaly identifier, such as "isDel". Thus, the fourth local image identifier combination includes all local slice image identifiers, and the presence or absence of anomaly identifiers can determine whether each local slice image identifier is invalid. Therefore, the display of preview results can be directly controlled based on the fourth local image identifier, for example, displaying preview results in the cloud corresponding to each valid slice image identifier in the fourth local image identifier combination, and empty preview results corresponding to each invalid slice image identifier.

[0056] Optionally, in the fourth local image identifier combination, each element of the third local image identifier combination is located after all elements of the second local image identifier combination.

[0057] This embodiment achieves the simultaneous display of preview results for all valid slide image identifiers corresponding to pathological identifiers, and empty preview results for all invalid slide image identifiers, making it easy for users to intuitively obtain the preview results of each slide image identifier.

[0058] Figure 3A This is a schematic diagram of the structure of an image processing apparatus provided in an embodiment of the present invention. Figure 3A As shown, the image processing apparatus includes: The display module 310 is used to respond to an image viewing request to determine a pathological identifier and display a combination of preview results corresponding to the pathological identifier in the cloud. The combination of preview results includes preview results of one or more slide images corresponding to the pathological identifier. The preview results are determined based on the preview address under the slide image identifier corresponding to the corresponding slide image. The preview address is determined based on the pathological identifier and the device identifier corresponding to the pathological identifier. The coordinate determination module 320 is used to respond to the screenshot request, obtain the screenshot coordinates for the current preview result, and determine the actual cropping coordinates corresponding to the screenshot coordinates based on the screenshot return function under the target slice image identifier. The target slice image identifier is the slice image identifier in the cloud that corresponds to the current preview result. The screenshot module 330 can be used to perform screenshot processing on the slice image corresponding to the target slice image identifier based on the actual capture coordinates and the streaming address under the target slice image identifier, so as to obtain the target screenshot result.

[0059] The technical solution provided by this invention allows upper-layer services to ignore the underlying storage protocols, image formats, and transmission mechanisms between images generated by devices corresponding to different device identifiers, since the preview address is determined based on the pathology identifier and the corresponding device identifier. The upper-layer address allows the display of the corresponding slice image simply through a unified preview address. The screenshot return function converts the screenshot coordinates on the browsing results into actual capture coordinates, and the streaming address is used to access the corresponding slice image. In this way, the processor can access the corresponding slice image through the streaming address and then perform screenshot processing on the corresponding slice image based on the actual screenshot coordinates to obtain the target screenshot result. This achieves the ability to display slice images through preview results without needing to pay attention to the underlying image storage mechanism in the cloud, and to complete the screenshot operation of the actual slice image without displaying the actual slice image. This significantly improves the user experience by eliminating the need for users to frequently switch between image software corresponding to each device identifier.

[0060] In one embodiment, such as Figure 3B As shown, the device also includes a mounting module 300, which is used for: Determine a first cloud image identifier combination corresponding to the target identifier combination, wherein the target identifier combination includes pathology identifiers and device identifiers; The preview address, the streaming address, and the screenshot return function are attached to each slice image identifier in the first cloud image identifier combination.

[0061] In one embodiment, the display module 310 includes: The first identifier combination determination unit is used to determine the second cloud image identifier combination and the first local image identifier combination corresponding to the pathology identifier; The second identifier combination determination unit is used to determine a second local image identifier combination that is the same as the second cloud image identifier combination based on the first local image identifier combination; The display unit is used to display the preview results of the slice images corresponding to each slice image identifier in the second local image identifier combination in the cloud.

[0062] In one embodiment, the second identifier combination determination unit For each slice image identifier in the first local image identifier group, if the slice image identifier exists in the second cloud image identifier group, then the slice image identifier is placed into the second local image identifier group.

[0063] In one embodiment, the second identifier combination determining unit is further configured to: If the slice image identifier is not present in the second cloud image identifier group, then the slice image identifier is placed in the third local image identifier group; Accordingly, the display unit is also used for: Display each slice image identifier in the third local image identifier combination and the empty preview result identifier corresponding to each slice image identifier.

[0064] In one embodiment, the second identifier combination determining unit is further configured to: The second local image identifier combination and the third local image identifier combination are spliced ​​together to obtain a fourth local image identifier combination, and the slice image identifiers belonging to the third local image identifier combination in the fourth local image identifier combination carry an anomaly identifier. Accordingly, the display unit is also used for: The preview results corresponding to each valid slice image identifier in the fourth local image identifier combination are displayed in the cloud, along with empty preview result identifiers corresponding to each invalid slice image identifier. The valid slice image identifier is a slice image identifier that does not carry the abnormal identifier, and the invalid slice image identifier is a slice image identifier that carries the abnormal identifier.

[0065] In one embodiment, such as Figure 3C As shown, the device also includes an adding module 340, which is used for: In response to a predetermined trigger operation, the target screenshot result is added to the current pathology report.

[0066] The image processing apparatus provided in the embodiments of the present invention can execute the image processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of executing the method.

[0067] It is worth noting that the various units and modules included in the above-mentioned image processing device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy distinction between each other and are not used to limit the protection scope of the embodiments of the present invention.

[0068] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. The electronic device 10 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (such as helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0069] like Figure 4 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0070] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0071] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as image processing methods.

[0072] In some embodiments, the image processing method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or mounted on electronic device 10 via read-only memory (ROM) 12 and / or communication unit 19. When the computer program is loaded into random access memory (RAM) 13 and executed by processor 11, one or more steps of the image processing method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the image processing method by any other suitable means (e.g., by means of firmware).

[0073] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0074] Computer programs for implementing the image processing methods of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The computer programs can be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0075] This invention provides a computer-readable storage medium storing computer instructions for causing a processor to execute an image processing method, including: In response to an image viewing request, a pathological identifier is determined, and a combination of preview results corresponding to the pathological identifier is displayed in the cloud. The combination of preview results includes preview results of one or more slide images corresponding to the pathological identifier. The preview results are determined based on the preview address under the slide image identifier corresponding to the slide image. The preview address is determined based on the pathological identifier and the device identifier corresponding to the pathological identifier. In response to a screenshot request, the screenshot coordinates for the current preview result are obtained, and the actual cropping coordinates corresponding to the screenshot coordinates are determined based on the screenshot return function under the target slice image identifier. The target slice image identifier is the slice image identifier in the cloud that corresponds to the current preview result. Based on the actual capture coordinates and the streaming address under the target slice image identifier, the slice image corresponding to the target slice image identifier is captured to obtain the target screenshot result.

[0076] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0077] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0078] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0079] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0080] In particular, according to embodiments of the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication unit 19, or installed from storage unit 18, or installed from ROM 12. When the computer program is executed by processor 11, it performs the functions defined in the methods described in the embodiments of the present invention.

[0081] This invention also provides a computer program product, including a computer program that, when executed by a processor, implements the image processing method according to any embodiment of the invention.

[0082] In implementing the computer program product, computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0083] It should be understood that the various forms of processes shown above can be used to reorder, add, or delete steps. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution provided by this invention can be achieved, and this is not limited herein.

[0084] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. An image processing method, characterized in that, The method includes: In response to an image viewing request, a pathological identifier is determined, and a combination of preview results corresponding to the pathological identifier is displayed in the cloud. The combination of preview results includes preview results of one or more slide images corresponding to the pathological identifier. The preview results are determined based on the preview address under the slide image identifier corresponding to the slide image. The preview address is determined based on the pathological identifier and the device identifier corresponding to the pathological identifier. In response to a screenshot request, the screenshot coordinates for the current preview result are obtained, and the actual cropping coordinates corresponding to the screenshot coordinates are determined based on the screenshot return function under the target slice image identifier. The target slice image identifier is the slice image identifier in the cloud that corresponds to the current preview result. Based on the actual cropping coordinates and the streaming address under the target slice image identifier, the slice image corresponding to the target slice image identifier is cropped to obtain the target cropping result.

2. The method according to claim 1, characterized in that, The response prior to the image viewing request also includes: Determine a first cloud image identifier combination corresponding to the target identifier combination, wherein the target identifier combination includes pathology identifiers and device identifiers; The preview address, the streaming address, and the screenshot return function are attached to each slice image identifier in the first cloud image identifier combination.

3. The method according to claim 1, characterized in that, The preview results of the slide images corresponding to the pathological markers displayed in the cloud include: Determine the second cloud image identifier combination and the first local image identifier combination corresponding to the pathological identifier; Based on the first local image identifier combination, a second local image identifier combination that is the same as the second cloud image identifier combination is determined; Display the preview results of the slice images corresponding to each slice image identifier in the cloud and the second local image identifier combination.

4. The method according to claim 3, characterized in that, The step of determining a second local image identifier combination that is the same as the second cloud image identifier combination based on the first local image identifier combination includes: For each slice image identifier in the first local image identifier group, if the slice image identifier exists in the second cloud image identifier group, then the slice image identifier is placed into the second local image identifier group.

5. The method according to claim 3, characterized in that, After determining the second local image identifier combination that is the same as the second cloud image identifier combination based on the first local image identifier combination, the method further includes: If the slice image identifier is not present in the second cloud image identifier group, then the slice image identifier is placed in the third local image identifier group; The preview results of the slice images corresponding to each slice image identifier in the second local image identifier combination, displayed in the cloud, also include: Display each slice image identifier in the third local image identifier combination and the empty preview result identifier corresponding to each slice image identifier.

6. The method according to claim 5, characterized in that, The step of placing the slice image identifier after the third local image identifier combination if the slice image identifier does not exist in the first local image identifier combination further includes: The second local image identifier combination and the third local image identifier combination are spliced ​​together to obtain a fourth local image identifier combination, and the slice image identifiers belonging to the third local image identifier combination in the fourth local image identifier combination carry an anomaly identifier. The preview results of the slice images corresponding to each slice image identifier in the second local image identifier combination displayed in the cloud include: The preview results corresponding to each valid slice image identifier in the fourth local image identifier combination are displayed in the cloud, along with empty preview result identifiers corresponding to each invalid slice image identifier. The valid slice image identifier is a slice image identifier that does not carry the abnormal identifier, and the invalid slice image identifier is a slice image identifier that carries the abnormal identifier.

7. The method according to claim 3, characterized in that, Also includes: In response to a predetermined trigger operation, the target screenshot result is added to the current pathology report.

8. An electronic device, characterized in that, The electronic device includes: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the image processing method as described in any one of claims 1-7.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the image processing method according to any one of claims 1-7.

10. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the image processing method according to any one of claims 1-7.