System and method for controlling interface of medical imaging device
By setting preset rules in the interface of the medical imaging device, the problem of insufficient space and mismatch in operation is solved, flexible interface layout and efficient operation processes are realized, and the efficiency of medical imaging devices is improved.
Patent Information
- Application Number
- CN202510610078.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2021-08-30
- Publication Date
- 2025-08-15
AI Technical Summary
The existing medical imaging device user interface lacks space when expanding functions and cannot be adjusted according to the user's operating habits, resulting in mismatch and inefficiency.
Adjust user interface components by setting preset rules, including applications, application widgets and program docking, optimize interface layout according to user operation data and system policies, supports interactive operations such as clicks, swipes, and long presses to achieve flexible interface component adjustments.
It improves the utilization rate of interface space, simplifies the operation process, enhances the scalability and adaptability of interfaces, and improves the efficiency of medical imaging work.
Smart Images

Figure CN120496788A_ABST
Abstract
Description
Description of the case
[0001] This application is a divisional application filed for the Chinese application with the application date of August 30, 2021, application number 202111004268.9, and invention name “A system and method for controlling an interface of medical imaging equipment”. Technical Field
[0002] This specification relates to the field of medical imaging, and in particular to a system and method for controlling an interface of a medical imaging device. Background Art
[0003] With the advancement of medical imaging technology, medical imaging equipment has also experienced rapid development. Medical imaging device users operate these devices through user interfaces, where the position and order of functional controls are typically fixed. Under these settings, the main interface may lack sufficient space when expansion is needed; sometimes, functional controls may not align with the user's current operations; and they cannot be adjusted to suit the user's operating habits.
[0004] Therefore, it is necessary to provide a system and method for controlling an interface of a medical imaging device. Summary of the Invention
[0005] One of the embodiments of the present specification provides a system for controlling an interface of a medical imaging device, the system comprising: a processor; a display device, the display device being used to display a user interface comprising interface components, wherein the interface components are configured to correspond to functions of the medical imaging device and operations on the medical imaging device, and the processor controls the medical imaging device through operations on the interface components, and the types of the interface components include applications, application widgets, and program docks.
[0006] In some embodiments, the interface component is formed by setting the initial layout of the user interface according to preset rules.
[0007] In some embodiments, setting the initial layout of the user interface according to preset rules includes: determining the target interface components displayed in the initial layout based on the preset rules; and determining the layout of the target interface components on the user interface based on the preset rules.
[0008] In some embodiments, the preset rules include at least one of user-defined, based on user operation data, and based on system policy.
[0009] In some embodiments, the interface component corresponds to multiple interactive operations, and the multiple interactive operations include at least one of clicking, sliding, long pressing and double-clicking.
[0010] In some embodiments, the application corresponds to at least one function of the medical imaging device; the application widget corresponds to at least one of the information related to the application and the operations related to the application; the program dock includes one or more of the applications and the application widgets, and the program dock is configured to be displayed on the interface corresponding to the application.
[0011] In some embodiments, the application widget includes multiple types, one of the multiple types corresponds to a function sequence of functions of the medical imaging device that are executed in sequence, and each function in the function sequence corresponds to a function of the medical imaging device.
[0012] In some embodiments, the various interface components are configured to adjust based on user actions.
[0013] In some embodiments, the adjustment is made actively by the user, or automatically based on user operation data.
[0014] Another embodiment of the present specification provides a method for controlling an interface of a medical imaging device, the method comprising: displaying a user interface including interface components through a display device, wherein the interface components are set to correspond to functions of the medical imaging device and operations on the medical imaging device according to preset rules, and types of the interface components include applications, application widgets, and program docks; receiving operations on the interface components through one or more processors to control the medical imaging device.
[0015] Some embodiments of the present specification provide systems and methods for controlling the interface of medical imaging equipment. Users can layout the user interface of the medical imaging equipment as needed. By using a variety of interface components, operations and function calls of the medical imaging equipment can be flexibly and quickly implemented, thereby improving the utilization of the interface space, improving the scalability of the interface, reducing unnecessary steps, simplifying the operating process, facilitating user operations, and improving the efficiency of medical imaging-related work. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] This specification will be further described in the form of exemplary embodiments, which will be described in detail with reference to the accompanying drawings. These embodiments are not limiting, and in these embodiments, like numbers represent like structures, wherein:
[0017] Figure 1 is a schematic diagram of an application scenario of a system for controlling an interface of a medical imaging device according to some embodiments of this specification;
[0018] Figure 2is a schematic diagram of a system for controlling an interface of a medical imaging device according to some embodiments of this specification;
[0019] Figure 3 is a flowchart of configuring a user interface according to some embodiments of this specification;
[0020] Figure 4 is a schematic diagram of interface components according to some embodiments of this specification;
[0021] Figure 5 is a schematic diagram of an APP according to some embodiments of this specification;
[0022] Figure 6 is a schematic diagram of an application widget according to some embodiments of this specification;
[0023] Figure 7 is a schematic diagram of stacking application widgets according to some embodiments of this specification;
[0024] Figure 8 is a schematic diagram of interface components according to some embodiments of this specification;
[0025] Figure 9 is a schematic diagram of a program dock according to some embodiments of this specification;
[0026] Figure 10a Schematic diagram of a mobile APP according to some embodiments of this specification;
[0027] Figure 10b is a schematic diagram of a combined APP according to some embodiments of this specification;
[0028] Figure 11 is an exemplary flow chart of a method for controlling an interface of a medical imaging device according to some embodiments of this specification. DETAILED DESCRIPTION
[0029] To more clearly illustrate the technical solutions of the embodiments of this specification, the following briefly describes the drawings required for describing the embodiments. Obviously, the drawings described below are merely examples or embodiments of this specification. Those skilled in the art can apply this specification to other similar scenarios based on these drawings without inventive effort. Unless otherwise apparent from the context or otherwise noted, the same reference numerals in the figures represent the same structure or operation.
[0030] It should be understood that the terms "system," "device," "unit," and / or "module" used herein are a method for distinguishing different components, elements, parts, portions, or assemblies at different levels. However, if other terms can achieve the same purpose, the terms may be replaced by other expressions.
[0031] As used in this specification and claims, unless the context clearly indicates otherwise, the words "a," "an," "an," and / or "the" do not refer to the singular but also include the plural. Generally speaking, the terms "comprises" and "include" only indicate the inclusion of the steps and elements specifically identified, and these steps and elements do not constitute an exclusive list. A method or apparatus may also include other steps or elements.
[0032] Flowcharts are used throughout this specification to illustrate the operations performed by systems according to embodiments of this specification. It should be understood that preceding or following operations do not necessarily need to be performed in exact order. Instead, the steps may be processed in reverse order or simultaneously. Furthermore, other operations may be added to these processes, or one or more operations may be removed from these processes.
[0033] Figure 1 This is a schematic diagram of an application scenario of a system for controlling an interface of a medical imaging device according to some embodiments of this specification.
[0034] In some application scenarios, an interface system for controlling medical imaging equipment may include a processing device and a display device, wherein the display device may be used to display a user interface including multiple interface components. The interface system for controlling medical imaging equipment may be implemented by implementing the methods and / or processes disclosed in this application to obtain different interface systems to meet the different needs of users and improve user efficiency.
[0035] like Figure 1 As shown, in some embodiments, the system 100 may include a processing device 110 , a display device 120 , an input device 130 , a medical imaging device 140 , a network 150 , and a storage device 160 .
[0036] In some embodiments, the processing device 110 can process data and / or information obtained from other devices or system components and execute program instructions based on this data, information, and / or processing results to perform one or more functions described in this application. For example, the processing device 110 can execute an operation instruction based on an operation input by the input device 130. For another example, the processing device 110 can receive a control instruction to control the medical imaging device 140 to perform relevant tests. In some embodiments, the data or images processed by the processing device 110 can be displayed by the display device 120.
[0037] In some embodiments, the processing device 110 may include one or more sub-processing devices (e.g., a single-core processing device or a multi-core multi-core processing device). By way of example only, the processing device 110 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), an application-specific instruction set processor (ASIP), a graphics processing unit (GPU), a physical processing unit (PPU), a digital signal processor (DSP), a field-programmable gate array (FPGA), a programmable logic device (PLD), a controller, a microcontroller unit, a reduced instruction set computer (RISC), a microprocessor, or any combination thereof.
[0038] Display device 120 refers to a device for displaying a user interface including a variety of interface components. In some embodiments, the display device can be touch-sensitive, non-touch-sensitive, or any combination thereof. In some embodiments, display device 120 can display data or images processed by processing device 110. In some embodiments, display device 120 can include one or more screens.
[0039] The input device 130 refers to a device that a user can use to input commands, such as a mouse 130 - 1 , a trackball 130 - 2 , a touchpad, a keyboard, a slide bar, and the like.
[0040] In some embodiments, instructions are input to the processing device 110 via the input device 130. The processing device 110 can control the medical imaging device 140 via the network 150. The medical imaging device 140 performs corresponding processing according to the instructions and displays the processing results on the display device 120. In some embodiments, the display device 120 and the input device 130 can be integrated. For example, a touch-sensitive display device can be used to input instructions directly through the display device. In some embodiments, the display device 120, input device 130, and processing device 110 can be integrated, such as an all-in-one computer with a touch screen or a laptop computer.
[0041] Medical imaging equipment 140 can refer to medical devices that utilize various media to reproduce internal human structures as images. Examples include medical X-ray machines 140-1 and ultrasound imaging equipment 140-2. Another example includes digital imaging equipment, computed tomography (CT) equipment, magnetic resonance imaging (MRI) equipment, nuclear medicine imaging equipment, and any combination thereof. The above list of medical imaging equipment 140 is provided for illustrative purposes only and is not intended to limit its scope.
[0042] Network 150 can connect the various components of the system and / or connect the system to external resources. Network 150 enables communication between the various components and with other components outside the system, facilitating the exchange of data and / or information. In some embodiments, one or more components in interface system 100 (e.g., processing device 110, medical imaging device 140, storage device 160) can send data and / or information to other components via network 150. In some embodiments, network 150 can be any one or more of a wired network and a wireless network. In some embodiments, processing device 110 and medical imaging device 140 can be connected via a cable.
[0043] Storage device 160 can store data or information generated by other devices. In some embodiments, storage device 160 can store data and images processed by processing device 110. In some embodiments, storage device 160 can store medical images and other data acquired by medical imaging device 140. Storage device 160 includes one or more storage components, each of which can be a standalone device or part of another device.
[0044] It should be understood that Figure 1 The system and its modules shown can be implemented in various ways. For example, in some embodiments, the system and its modules can be implemented by hardware, software, or a combination of software and hardware.
[0045] It should be noted that the above description of system 100 is for convenience only and does not limit this specification to the scope of the illustrated embodiments. It is understood that those skilled in the art, after understanding the principles of the system, may arbitrarily combine the modules or form subsystems connected to other modules without departing from these principles. For example, processing device 110 and medical imaging device 140 may be directly connected without passing through network 150. For another example, the modules may share a storage module, or each module may have its own storage module. Variations such as these are within the scope of this specification.
[0046] Figure 2 is a schematic diagram of a system for controlling an interface of a medical imaging device according to some embodiments of this specification.
[0047] like Figure 2 As shown, in some embodiments, a system 200 for controlling an interface of a medical imaging device may include a processor 210 , a display device 220 , and a user 230 .
[0048] In some embodiments, the processor 210 may be used to control the medical imaging device to perform operations. In some embodiments, the processor 210 may correspond to the processing device 110.
[0049] In some embodiments, the processor 210 may include modules. In some embodiments, the modules may include a processing module 2101 and a display output module 2102. In some embodiments, the display output module 2102 may include a setting module 21021 and an adjustment module 21022.
[0050] The processing module 2101 can be used to control the medical imaging device. In some embodiments, the processing module 2101 can receive user operations on the interface components. In some embodiments, the processing module 2101 can control the medical imaging device based on the received operations.
[0051] The display output module 2102 can be used to display a user interface including a plurality of interface components through a display device, wherein the interface components are configured to correspond to the functions of the medical imaging device and the user's operations on the medical imaging device.
[0052] The functions of a medical imaging device refer to the operations that the device itself can perform, such as scanning a human body and capturing medical images of a human body. Operations on a medical imaging device refer to operations performed by a user on the device, such as setting scanning parameters and aligning the scanning position with the position of the medical imaging device. In some embodiments, user operations on interface components can invoke corresponding medical imaging device functions or perform corresponding operations on the device.
[0053] In some embodiments, the setting module 21021 can be used to determine the target interface components displayed in the initial layout based on preset rules. In some embodiments, the setting module 21021 can be used to determine the layout of the target interface components on the user interface based on preset rules.
[0054] In some embodiments, the adjustment module 21022 can be used to adjust the interface components on the user interface, for example, the position, size, etc.
[0055] The display device 220 is used to display a user interface including multiple interface components. In some embodiments, the display device 220 is a part of the display device 120. In some embodiments, the user interface can span multiple display screens and be composed of interfaces on multiple display screens.
[0056] In some embodiments, the display device 220 may include an input device, such as the input device 130 .
[0057] In some embodiments, the display device 220 may receive operations on the interface components by the user 230 . In some embodiments, the display device may send the operations on the interface components by the user 230 to the processor 210 .
[0058] In some embodiments, the display device 220 may display a user interface including a variety of interface components by receiving user interface data from the display output module 2102 .
[0059] An interface component is a component used to form a user interface and to perform corresponding functions. In some embodiments, the interface component may include one or more of an application 220-1, an application widget 220-2, a program dock 220-3, and the like.
[0060] Application 220-1 may correspond to an application program. For example, different functions in a medical imaging device correspond to different APPs. Application 220-1 may include a variety of different applications. For example, application a, application b, application c, application f, application g, application h, etc. For example, application a may be a probe APP, application c may be a scanning APP, application g may be a measurement APP, application h may be a reporting APP, etc. In some embodiments, an application may also refer to an APP for one or more key functions of a medical imaging device. For example, a convex array probe APP, an automatic cardiac measurement APP, etc. The application may also be other, the above is only an example, not a limitation. For more information about application 220-1, please see Figure 4 、 Figure 5 The relevant description will not be repeated here.
[0061] In some embodiments, the application widget 220-2 refers to a component composed of one or more APPs. The application widget 220-2 may include a variety of different application combinations. For example, the application widget 220-2 may include 2 applications (I, II). For another example, the application widget 220-2 may include 4 applications (1, 2, 3, 4). Exemplarily, application I may be a patient APP, application II may be a linear array probe APP, and so on. In some embodiments, the application widget 220-2 may refer to a widget with one of the functions. For example, a phased probe widget, an automatic cardiac measurement widget. The phased probe widget may include multiple preset probes. The automatic cardiac measurement widget may include multiple different measurement items, and so on. The number of applications contained in the application widget can be set according to demand. For more information about the application widget 220-2, please see Figure 4 、 Figure 6 、 Figure 7 and Figure 8 Related description.
[0062] In some embodiments, the interface component can be in the form of a program dock 220-3. The program dock 220-3 can include a variety of different application combinations. For example, the program dock 220-3 can include 4 applications (A, B, C, D) and 2 application widgets (I, W) and (X, Y). The above applications in different expressions (uppercase and lowercase letters or numbers) are only examples and can represent the same or different applications, but are not limited. For more information about the program dock 220-3, please see Figure 9 Related description.
[0063] In some embodiments, the interface components are set to correspond to the functions of the medical imaging device and the user's operations on the medical imaging device, so that the functions of the medical imaging device can be quickly called, and convenient operation of the medical imaging device can be achieved, reducing unnecessary steps and operations, facilitating the user, and improving the efficiency of medical examinations and other work; at the same time, it expands the user's operating space and improves the utilization of the screen space; different interface components that are interconnected can adapt to the different needs of users, enhance the flexibility of the user interface, and improve adaptability.
[0064] In some embodiments, the user 230 may be a user of a medical imaging device, such as a system administrator 230 - 1 , a doctor 230 - 2 , and the like.
[0065] Figure 3 This is a schematic diagram of a configuration user interface according to some embodiments of this specification.
[0066] In some embodiments, the interface component may be formed by setting the initial layout of the user interface according to preset rules.
[0067] In some embodiments, when configuring a user interface, the initial layout 310 of the user interface is first obtained, then preset rules are obtained, and finally the user interface is set according to the obtained preset rules to obtain the set user interface 340.
[0068] The initial layout of a user interface refers to the initial state of the user interface. In some embodiments, the initial layout of a user interface may be a default layout of the user interface. For example, the factory default settings, where the positions of different apps or functional controls are pre-set by the manufacturer.
[0069] Preset rules refer to the rules based on which the user interface is laid out. In some embodiments, the preset rules may include at least one of user-defined 320-1, based on user operation data 320-2, and based on system policy 320-3. In some embodiments, the preset rules may also include other types.
[0070] User customization refers to adjustments made by users based on their needs, such as adjustments to the location and order of apps.
[0071] In some embodiments, when the preset rule is user customization 320 - 1 , the layout of the user interface can be set based on the user customization 320 - 1 through step 330 - 1 . In some embodiments, step 330 - 1 can be performed by the setting module 21021 .
[0072] In some embodiments, the edit state of the user interface can be activated by the user, and the APP can be moved to the target location according to the set action. The setting module 21021 can store the location information of the APP in real time. In some embodiments, the set action can be dragging the APP icon, etc.
[0073] Based on user operation data refers to adjusting based on the user's operation data, such as user role, operation history data, etc. In some embodiments, the APP can be automatically adjusted according to the user's role, the scanned area, etc.
[0074] In some embodiments, when the preset rule is based on the user operation data 320 - 2 , the layout of the user interface can be set based on the user operation data 320 - 2 through step 330 - 2 . In some embodiments, step 330 - 2 can be performed by the setting module 21021 .
[0075] In some embodiments, the user's role can be set. For example, it can be set by the system administrator, which can include service engineers, department heads, etc. In another example, it can be set by the user. It can be set when the user registers an account. In some embodiments, the user's role can be divided according to different requirements. For example, based on the doctor's position, the user's role can be divided into chief physician, attending physician, intern, etc.; for another example, based on the specialty, the user's role can be divided into cardiologist, obstetrics specialist, etc.
[0076] In some embodiments, the settings module 21021 can automatically adjust apps based on the user's role. For example, if the user's role is a cardiologist, the settings module 21021 can determine the user's role and place the phased array probe application used by cardiologists in the first app's location. In some embodiments, the user can determine whether to perform adjustments based on user operation data 320-2 as needed.
[0077] In some embodiments, the settings module 21021 can automatically adjust the app based on the scanned area. For example, if the scanned area is abdominal organs, doctors generally use a convex array probe for abdominal organ scans. The settings module 21021 can prompt the user to select the convex array probe for scanning by flashing a small icon on the convex array probe.
[0078] System policy-based means that the system automatically adjusts the APP according to the product operation strategy, for example, the update strategy after the system upgrade.
[0079] In some embodiments, when the preset rule is based on the system policy 320 - 3 , the layout of the user interface can be set based on the system policy 320 - 3 through step 330 - 3 . In some embodiments, step 330 - 3 can be performed by the setting module 21021 .
[0080] In some embodiments, the product's operational policy can be synchronized to the system online or offline. Online methods include OTA, and offline methods include importing it into the system via external media (such as a USB flash drive). The operational policy may include at least one of the following information: the target app to be adjusted, the target location, the effective time, the expiration time, etc. In some embodiments, the system administrator or user can set whether to make adjustments based on the system policy 320-3 according to needs.
[0081] In some embodiments of this specification, setting the initial layout of the user interface according to preset rules can improve the user's measurement efficiency. For example, a system upgrade that upgrades the functionality of the automatic heart measurement application can effectively improve the user's measurement efficiency. The automatic heart measurement application can be automatically placed in the first app position by adjusting the system policy.
[0082] Figure 4 is a schematic diagram of interface components according to some embodiments of this specification.
[0083] Interface components may include multiple types, for example, applications (APPs), application widgets, program docks, etc. In some embodiments, the interface components on the user interface may include one or more of applications (APPs) 410 , application widgets 420 , and program docks 430 .
[0084] The home screen of the user interface refers to the screen displayed by default, such as Home, Homepage, etc. In some embodiments, the home screen of the user interface can include at least one APP and application widget.
[0085] The application screen of the user interface refers to the application interface displayed when using the application. In some embodiments, the application screen of the user interface can include a program dock. In some embodiments, the program dock can be included in the main screen of the user interface.
[0086] In some embodiments, the APP may correspond to at least one medical imaging-related function to complete operations related to medical imaging devices and / or medical imaging. In some embodiments, the APP may correspond to certain main functions in the medical imaging device, such as patients, probes, scans, measurements, annotations, reports, etc. In some embodiments, the application component may also correspond to a key function or a set of key functions in the main functions, such as a convex array probe application or an automatic cardiac measurement application. In some embodiments, the application may also correspond to a set of other functions, such as notifications and configurations. In some embodiments, the application may correspond to the processing of medical images, for example, generating three-dimensional models, image annotation, etc.
[0087] In some embodiments, an application widget may correspond to an app to implement extended functionality related to the app, such as displaying app information, calling in-app functions, etc. In some embodiments, an application widget may correspond to at least one of app-related information and app-related operations. In some embodiments, an application widget may contain one or more internal elements, each of which may correspond to application information or application functions, which may be from one or more apps.
[0088] In some embodiments, the dock can include one or more apps and / or app widgets to implement app-related functions. In some embodiments, the dock can be displayed on the interface corresponding to the app by calling it, and specific operations can be implemented by calling the app or app widget in the dock.
[0089] Interface components can execute calls or implement related functions through interactive operations. In some embodiments, interface components can be represented as icons, etc., corresponding to one or more interactive operations, such as clicking, sliding, long pressing, double-clicking, etc. In some embodiments, different interactive operations can correspond to different functions, for example, clicking corresponds to selection, long pressing brings up a shortcut menu, etc. In some embodiments, the same interactive operation can correspond to different functions for different interface components. For example, clicking on the APP can open the corresponding function interface, and clicking on the application widget can display the widget content. In some embodiments, the user can define the function corresponding to the interactive operation. For example, the user can define clicking on the APP as selection, and double-clicking on the APP as opening.
[0090] Each type of interface component can be further classified according to specific standards. The classification standards can be determined according to the specific type of the interface component, for example, classification based on whether it is executable, classification based on the number of elements contained, etc.
[0091] The interface components can be adjusted, for example, in terms of size, position, color, content, corresponding functions, etc. In some embodiments, the interface components of the user interface are configured to be adjustable based on user operations to suit the needs of the user. In some embodiments, the user can adjust the interface components by interacting with the interface components, for example, by dragging the interface components to adjust the position and / or order of the interface components. In some embodiments, the interface components can also be adjusted in a variety of other ways, for example, by eye movement control, by brain control, by gesture control, by voice control, etc.
[0092] In some embodiments, adjustments to interface components may include adjustments to their appearance, position, corresponding functionality, and the like. Different interface components may contain different adjustable content. For example, an app may not include size adjustments. In some embodiments, adjustments to interface components may span multiple screens, for example, dragging an interface component from screen A to screen B.
[0093] In some embodiments, adjustments to interface components can be made by the user. For example, the user can place the interface components they use most often in an easily accessible location. For another example, the user can add or remove content from the interface components as needed.
[0094] In some embodiments, the adjustment of interface components can be automatically performed based on user operation data. For example, based on the user's historical operation data, the interface components that users use most often can be placed in the position where they are most easily seen and operated (for example, in the middle of the interface). For another example, based on the user's historical operation data, the interface components that users use less frequently can be placed in a relatively inconspicuous position (for example, near the edge of the interface), or even the interface components that users use least frequently can be folded to reduce occupancy. For another example, when the frequency of calling a certain interface component reaches a threshold, its arrangement order is moved forward one position.
[0095] In some embodiments, the interface components may be adjusted in other ways, such as self-adaptation.
[0096] like Figure 4As shown, in some embodiments, applications 410 can be categorized into different types, such as functions and function sets, based on the amount of content they correspond to. For example, an app can correspond to a specific function in a medical imaging device, such as probe, scan, or measurement. Another example is an app that corresponds to a collection of multiple functions of a medical imaging device, such as convex array probe application and configuration.
[0097] Figure 5 It is a schematic diagram of an APP according to some embodiments of this specification.
[0098] like Figure 5 As shown, in some embodiments, the APP may correspond to the main functions in the medical imaging device, for example, the patient APP 510 and the scanning APP 520; or may correspond to a key function or a set of key functions in the main functions, for example, the linear array probe APP 540.
[0099] In some embodiments, the APP may be a combination of multiple APPs represented in a folder form, for example, the APP combination 530 .
[0100] like Figure 4 As shown, in some embodiments, the interactive operation corresponding to the application 410 may include clicking, sliding, long pressing, double clicking, etc. In some embodiments, clicking the APP icon can enter the APP corresponding function interface, and long pressing the APP icon can display the APP shortcut menu and the home screen shortcut menu.
[0101] In some embodiments, the interactive operations with the APP may also include other forms, such as eye movement control, brain control, gesture control, voice control, etc.
[0102] A shortcut menu is used to quickly access functions. An app's shortcut menu can be used to quickly access app functions. The home screen's shortcut menu can be used to quickly access system functions. In some embodiments, different types of shortcut menus can be distinguished, such as with a dividing line or icon, to help users better distinguish between app and home screen shortcut menus.
[0103] like Figure 4 As shown, in some embodiments, the adjustable content of application 410 may include: position, arrangement order, status, shortcut menu, etc. The position of the app is the position of the app icon on the screen. The arrangement order of the app is the spatial arrangement order of the app icons on the screen, that is, the relative positions of the app icons, such as left and right, up and down, etc.
[0104] In some embodiments, the adjustable content of an APP may also include splitting and reorganizing. Specifically, if an APP corresponds to more than one function, the APP can be split according to the function or function combination. The split functions and function combinations can each correspond to a new APP, and the new APP can be combined with other APPs.
[0105] In some embodiments, the decision to split an app can be made based on the frequency of use of the app. In some embodiments, if the frequency of use of a function exceeds a certain threshold, the system can ask the user whether to split the app, or the system can automatically split the app and notify the user.
[0106] The app status is used to prompt the user to operate or explain the app's status. In some embodiments, the measurement app can use a small icon to indicate the number of measurements the user has taken. In some embodiments, the probe app can use a flashing small icon or color change to prompt the user to select the probe.
[0107] In some embodiments, the items included in the shortcut menu of the APP can be adjusted, for example, the order can be adjusted, items can be added or removed, etc.
[0108] In some embodiments, at least one of the position, arrangement order, status, shortcut menu, etc. of the APP can be adjusted manually by the user or automatically by the system to meet the user's needs.
[0109] Figure 10a It is a schematic diagram of a mobile APP according to some embodiments of this specification.
[0110] In some embodiments, as Figure 10a As shown, the user interface includes APP1010, APP1020, and APP1030. The position of APP1010 can be moved. Before moving, the position of APP1010 is in the upper left corner of the screen. The position can be moved by various methods such as dragging the APP1010 icon. After moving, the position of the APP1010 icon is in the lower right corner of the screen.
[0111] Figure 10b It is a schematic diagram of a combined APP according to some embodiments of this specification.
[0112] In some embodiments, as Figure 10b As shown, before combination, there are 4 independent APPs on the screen: APP1050, APP1060, APP1070, and APP1080. Multiple APPs can be combined into an APP folder. After combination, the screen contains a combined folder 1090 containing APP1050, APP1060, APP1070, and APP1080.
[0113] like Figure 4 As shown, in some embodiments, the application widgets 420 can be divided into different types such as information display and application operation according to their corresponding functions.
[0114] In some embodiments, application widgets can be used to display application-related information. For example, a measurement APP can define a widget for measurement results to provide the function of viewing measurement results; a trackball APP can define a widget for trackball operation instructions to prompt users of the current functions of the trackball and its buttons.
[0115] In some embodiments, the application widget 420 can be used to directly call APP-related functions. For example, the "distance measurement" in the measurement widget can activate the distance measurement tool.
[0116] In some embodiments, the application widget can be used to open the interface of the corresponding application. For example, the "Enter General Measurement" button of the measurement widget can enter the measurement APP and locate the application interface of the general measurement.
[0117] Figure 6 is a schematic diagram of an application widget according to some embodiments of this specification.
[0118] like Figure 6 As shown, in some embodiments, the application widget can be one that displays application information, for example, the information display widget 610; can be one that directly executes application-related operations, for example, the common function widget 620; can be an entrance to an interface corresponding to a certain function, for example, the function entrance widget 630; or can be a combination of multiple types of the above, for example, the function widget 640.
[0119] Figure 8 is a schematic diagram of interface components according to some embodiments of this specification.
[0120] like Figure 8 The user interface shown includes multiple types of interface components, among which APP includes report APP 810, review APP 820, other APP 830, APP combination 840, etc., and interface widgets include current scanning part widget 850, commonly used measurement widget 860, measurement entry widget 870, scanning widget 880, shortcut widget 890, etc.
[0121] In some embodiments, the application widget can cross APPs, that is, the functions of multiple APPs can be freely combined into one widget, for example, Figure 8 Shortcut widget 890 is shown.
[0122] In some embodiments, the interface components may correspond to a functional sequence composed of multiple functions in order, and these interface components may include APPs, application widgets, etc.
[0123] In some embodiments, one of the multiple types of application widgets can correspond to a sequence of medical imaging-related functions that are executed sequentially, with each function in the sequence corresponding to a medical imaging-related function. In some embodiments, multiple functions can be added to a single application widget. These functions can be from the same application or from different applications. The execution order of these functions is then determined, and the functions can also be executed in the order in which they were added. For example, a common operation process for monitoring cardiac blood flow during a heart scan can be added to a single application widget. The application widget can include the following operations in sequence: 1. Open B-mode; 2. Open C-mode; 3. Adjust the position and size of the sampling box (ROI) in C-mode; 4. Open PW mode; 5. Freeze the image; 6. Measure the PW envelope (or other parameters); 7. Unfreeze the image. B, C, PW, sampling box adjustment, freeze / unfreeze, etc. can belong to the scanning app, while envelope measurement can belong to the measurement app. This series of operations can be automatically executed sequentially through a single call of the application widget, eliminating the need for the user to manually switch apps.
[0124] In some embodiments, users can implement a fixed, frequently used sequence of operations using widgets. This can significantly save time, reduce repetitive operations, reduce operational complexity, and alleviate user burden. In some embodiments, experienced users can define a complex sequence of operations as a widget. Other users can then use the widget to achieve the desired results without having to worry about the specific operational procedures. This saves training resources, reduces learning difficulty, and improves user-friendly interaction.
[0125] like Figure 4 As shown, in some embodiments, the interactive operations corresponding to the application widget 420 may include clicking, sliding, long pressing, double-clicking, etc. In some embodiments, the same interactive operation may correspond to different functions for different types of application widgets. For example, clicking the measurement result widget displays the measurement result; clicking "Distance Measurement" in the measurement widget activates or deactivates the distance measurement tool; and clicking "Enter General Measurement" in the measurement widget enters the application interface of the measurement app.
[0126] In some embodiments, long pressing an application widget activates a shortcut menu. The shortcut menu of an application widget is similar to the shortcut menu of an app. Please refer to the relevant description of the shortcut menu of the app above and will not be repeated here.
[0127] like Figure 4 As shown, in some embodiments, the adjustable content of the application widget 420 may include: position, arrangement order, status, shortcut menu, size, stacking, etc. The position, arrangement order, status, shortcut menu and their adjustment of the application widget are similar to the corresponding content of the APP. Please refer to the relevant description of the APP above and will not be repeated here.
[0128] The size of an app widget refers to the amount of space it occupies on the screen. In some embodiments, the system can provide app widgets of different sizes to include or simultaneously display different amounts of app functionality and information. In some embodiments, the user can modify the app widget to a larger or smaller size based on the space or arrangement of the home screen.
[0129] In some embodiments, the size of an app widget can be defined as a multiple of the app icon, for example, n*m icon sizes, where n and m can be positive integers determined based on the screen size. As an example only, the size of an app widget can be 1*1 app icon, 2*1 app icons, 2*2 app icons, 3*3 app icons, 4*4 app icons, etc. This ensures an orderly arrangement of the home screen and fully utilizes the home screen space.
[0130] Stacking refers to placing multiple interface components overlapping in the same space on the screen, and switching to display different interface components. In some embodiments, multiple application widgets can be stacked, that is, several application widgets are stacked in the same space, and the application widgets can be switched by swiping up / down / left / right. In some embodiments, the number of application widgets currently stacked and the application widget displayed on the top can be indicated by an icon. In some embodiments, application widgets can be stacked in various ways, such as through user operation or automatic adjustment by the system.
[0131] Figure 7 This is a schematic diagram of stacking application widgets according to some embodiments of this specification.
[0132] like Figure 7 As shown, the stacked application widget includes 3 pages, which are represented by the circular icon at the bottom of the application widget. The black circle represents the currently displayed page, the white circle represents the undisplayed page, and the number of circles represents the number of pages. In some embodiments, different pages can be switched by sliding left and right, such as Figure 7 As shown, before switching, the displayed page is the stack widget page 1, that is, the phased array probe widget 710. By sliding to the right, you can switch to the stack widget page 2, that is, the automatic heart measurement widget 720.
[0133] like Figure 4As shown, in some embodiments, the application dock 430 can be a collection of functions and can include at least one app and application widget. In some embodiments, the interactive operations and adjustable content corresponding to the application dock 430 are similar to those of the application 410 and application widget 420. Please refer to the relevant description above and will not be repeated here.
[0134] In some embodiments, the dock can be activated within the display interface of the application, that is, displayed within the display interface of the application. In some embodiments, the dock can be activated / closed by interactive operations, for example, swiping up from the bottom of the screen to open it, swiping down to close it, etc.
[0135] Figure 9 is a schematic diagram of a program dock according to some embodiments of this specification.
[0136] In some embodiments, as Figure 9 As shown, after opening the application corresponding to the APP, the current display area of the screen is occupied by the APP content area 910. The application dock 930 can be activated through some interactive operation. After activation, the application dock 930 is displayed in the lower half of the screen and covers the original display area of the APP content area 910. In some embodiments, the user can use the corresponding functions of each interface component of the application dock through interactive operations.
[0137] Figure 11 is an exemplary flow chart of a method for controlling an interface of a medical imaging device according to some embodiments of this specification. Figure 11 As shown, process 1100 includes the following steps:
[0138] Step 1110 : Displaying a user interface including multiple interface components via a display device. In some embodiments, step 1110 may be performed by the display output module 2102 .
[0139] In some embodiments, interface components on the user interface can be configured to correspond to functions of the medical imaging device and user operations on the medical imaging device. Functions of the medical imaging device refer to operations that the medical imaging device can perform on medical examination objects, such as scanning and measurement. User operations on the medical imaging device refer to operations performed on the medical device itself, such as moving the probe.
[0140] In some embodiments, the display output module 2102 can set interface components according to the functions of the medical imaging device, such as a scanning mode component, a measurement component, an automatic heart measurement component, etc.
[0141] The user's operation on the medical imaging device may include various operations. In some embodiments, the display output module 2102 can set interface components based on the user's operation on the medical imaging device, such as commonly used measurement components.
[0142] In some embodiments, the interface component includes one or more of an application, an application widget, and a dock. For more information about interface components, see Figure 5-Figure 11 The relevant description will not be repeated here.
[0143] Step 1120 : Receive user operations on the interface components via one or more processors 210 . In some embodiments, step 1120 may be performed by the processing module 2101 .
[0144] User operations on an interface component refer to user operations on the interface component through interactive actions such as clicking and sliding. In some embodiments, user operations on an interface component may correspond to user-issued instructions, such as distance measurement instructions and automatic heart rate measurement instructions.
[0145] Step 1130 : Based on the received operation, control the medical imaging device. In some embodiments, step 1130 may be performed by the processing module 2101 .
[0146] In some embodiments, the processing module 2101 may control the medical imaging device to perform corresponding measurements based on the received operation. For example, upon receiving an instruction for automatic heart measurement, the medical imaging device may measure the patient's heart.
[0147] In some embodiments of this specification, the user interface is set and adjusted through multiple interface components, which improves the flexibility of the user interface layout of the medical imaging equipment, increases the scalability of the application, reduces redundant information, simplifies the operation steps, improves the operation efficiency, facilitates the user's operation, and improves the user's usage efficiency.
[0148] It should be noted that the above description of process 1100 is for illustrative purposes only and does not limit the scope of this specification. Those skilled in the art will be able to make various modifications and alterations to process 1100 under the guidance of this specification. However, such modifications and alterations remain within the scope of this specification. For example, in process 1100, a medical imaging device can be controlled while receiving user operations on interface components.
[0149] This specification also uses specific terms to describe the embodiments of this specification. For example, "one embodiment," "an embodiment," and / or "some embodiments" refer to a feature, structure, or characteristic associated with at least one embodiment of this specification. Therefore, it should be emphasized and noted that references to "one embodiment," "an embodiment," or "an alternative embodiment" two or more times in different locations in this specification do not necessarily refer to the same embodiment. Furthermore, certain features, structures, or characteristics of one or more embodiments of this specification may be appropriately combined.
[0150] In addition, unless expressly stated in the claims, the order of the processing elements and sequences, the use of alphanumeric characters, or the use of other names described in this specification are not intended to limit the order of the processes and methods of this specification. Although the above disclosure discusses some of the invention embodiments currently considered useful through various examples, it should be understood that such details are for illustrative purposes only, and the appended claims are not limited to the disclosed embodiments. On the contrary, the claims are intended to cover all modifications and equivalent combinations that are consistent with the spirit and scope of the embodiments of this specification. For example, although the system components described above can be implemented by hardware devices, they can also be implemented only by software solutions, such as installing the described system on an existing server or mobile device.
[0151] Similarly, it should be noted that, in order to simplify the presentation of this specification and thus facilitate understanding of one or more embodiments of the invention, the foregoing descriptions of the embodiments of this specification sometimes combine multiple features into a single embodiment, figure, or description thereof. However, this disclosure method does not imply that the subject matter of this specification requires more features than those recited in the claims. In fact, an embodiment may have fewer features than all of the features of a single disclosed embodiment.
[0152] In some embodiments, numbers are used to describe the quantity of components and attributes. It should be understood that such numbers used in the description of the embodiments are modified by the modifiers "about", "approximately" or "substantially" in some examples. Unless otherwise stated, "about", "approximately" or "substantially" indicate that the numbers are allowed to vary by ±20%. Accordingly, in some embodiments, the numerical parameters used in the description and claims are approximate values, which may change according to the required characteristics of individual embodiments. In some embodiments, the numerical parameters should take into account the specified significant digits and adopt the general method of retaining digits. Although the numerical domains and parameters used to confirm the breadth of their range in some embodiments of this specification are approximate values, in specific embodiments, the settings of such numerical values are as accurate as possible within the feasible range.
[0153] Each patent, patent application, patent application publication, and other materials, such as articles, books, specifications, publications, and documents, cited in this specification is hereby incorporated by reference in its entirety. This includes application history documents that are inconsistent with or conflict with the content of this specification, as well as documents (currently or subsequently attached to this specification) that limit the broadest scope of the claims of this specification. It should be noted that if the descriptions, definitions, and / or terminology used in the accompanying materials are inconsistent or conflicting with the content of this specification, the descriptions, definitions, and / or terminology used in this specification will control.
[0154] Finally, it should be understood that the embodiments described in this specification are intended only to illustrate the principles of the embodiments of this specification. Other variations may also fall within the scope of this specification. Therefore, by way of example and not limitation, alternative configurations of the embodiments of this specification may be considered consistent with the teachings of this specification. Accordingly, the embodiments of this specification are not limited to the embodiments explicitly described and illustrated in this specification.
Claims
1. A system for controlling an interface of a medical imaging device, comprising: processor; a display device, the display device being used to display a user interface including an interface component, The interface components are configured to correspond to the functions of the medical imaging device and the operations on the medical imaging device. By operating the interface components, the processor controls the medical imaging device. The types of interface components include applications and application widgets.
2. The system of claim 1, wherein: The interface components are formed by setting the initial layout of the user interface according to preset rules.
3. The system of claim 2, wherein setting the initial layout of the user interface according to a preset rule comprises: Determining a target interface component to be displayed in the initial layout based on the preset rule; The layout of the target interface components on the user interface is determined based on the preset rules.
4. In the system as described in claim 2, the preset rules include at least one of user customization, user operation data-based and system policy-based, the user operation data includes user role, operation history data and scanned area, and the system policy includes product operation strategy.
5. The system of claim 1, wherein the interface component corresponds to multiple interactive operations, and the multiple interactive operations include at least one of clicking, sliding, long pressing and double-clicking.
6. The system of claim 1, comprising: The application corresponds to at least one function of the medical imaging device; The application widget corresponds to at least one of information related to the application and operations related to the application; The application includes at least one application program (App), and the application widget includes functions related to the at least one application program.
7. In the system as described in claim 6, the application widget includes multiple types, one of the multiple types corresponds to a function sequence of the functions of the medical imaging device executed in sequence, and each function in the function sequence corresponds to a function of the medical imaging device.
8. The system of claim 1, wherein: The interface components are configured to adjust based on user actions. 9 . The system according to claim 8 , wherein the adjustment is performed actively by the user or automatically based on user operation data.
10. A method for controlling an interface of a medical imaging device, comprising: Displaying a user interface including an interface component via a display device, The interface components are configured to correspond to the functions of the medical imaging device and the operations on the medical imaging device. The types of interface components include applications and application widgets; The medical imaging device is controlled by receiving operations on the interface components through one or more processors.