Display method and device of instrument software interface, and in-vitro diagnostic equipment

Abstract

The application discloses a kind of display method, device and in-vitro diagnostic equipment of instrument software interface.Therein, the method includes: obtaining shared display page, wherein, shared display page includes floating screen control and instrument software interface, the display layer corresponding to floating screen control is located on the display layer corresponding to instrument software interface, instrument software interface is used to display the operation page corresponding to a set of instrument at the same time, floating screen control includes dynamic identification area, dynamic identification area is used to display the target identification information of the instrument software interface of other instruments, and the target identification information displayed by dynamic identification area is dynamically determined according to switching record;Receive interface control operation to floating screen control;In response to interface control operation, the interface displayed by instrument software interface is executed corresponding control.The application solves the technical problems of high hardware cost, low operation efficiency and complex system maintenance caused by using one-machine-one-screen mode in multi-instrument connection scenario.

Description

Technical Field

[0001] This invention relates to the field of data processing, and more specifically, to a method and apparatus for displaying a multi-instrument software interface and an in vitro diagnostic device. Background Technology

[0002] In online production lines used in fields such as medical testing, chemical analysis, and automated manufacturing, multiple instruments with different functions typically work together to complete complex processes. For example, an in vitro diagnostics pipeline may include various devices such as sample pretreatment instruments, biochemical analyzers, and chemiluminescence immunoassay analyzers.

[0003] Currently, the industry generally adopts a one-machine-one-screen management model, where each instrument on the production line is equipped with a dedicated display screen to load and display its own control software interface. Operators must monitor and control the entire production line by observing and operating their respective screens. This traditional model has significant drawbacks.

[0004] Therefore, existing technologies suffer from technical problems such as high hardware costs and large space occupation, low operating efficiency and easy error, complex system maintenance and low resource utilization caused by the use of a one-machine-one-screen mode in multi-instrument online scenarios. No effective solution has been proposed yet. Summary of the Invention

[0005] This invention provides a method, apparatus, and in vitro diagnostic device for displaying an instrument software interface, to at least solve the technical problems of high hardware cost, low operating efficiency, and complex system maintenance caused by the use of a one-machine-one-screen mode in multi-instrument online scenarios.

[0006] According to one aspect of the present invention, a method for displaying an instrument software interface is provided, comprising: acquiring a shared display page, wherein the shared display page includes a floating screen control and an instrument software interface, the display layer corresponding to the floating screen control is located above the display layer corresponding to the instrument software interface, the instrument software interface is used to display an operation page corresponding to one instrument at the same time, the floating screen control includes a dynamic identification area, the dynamic identification area is used to display target identification information of the instrument software interface of other instruments, the target identification information displayed in the dynamic identification area is dynamically determined according to a switching record, the switching record is used to record the source instrument identification and target instrument identification of at least one interface switching; receiving an interface control operation on the floating screen control, wherein the interface control operation is used to control the interface displayed by the instrument software interface; and responding to the interface control operation, performing corresponding control on the interface displayed by the instrument software interface.

[0007] According to one aspect of the present invention, a display device for an instrument software interface is provided, comprising: an acquisition module, configured to acquire a shared display page, wherein the shared display page includes a floating screen control and an instrument software interface, the display layer corresponding to the floating screen control is located above the display layer corresponding to the instrument software interface, the instrument software interface is used to display the operation page corresponding to one instrument at the same time, the floating screen control includes a dynamic identification area, the dynamic identification area is used to display target identification information of the instrument software interface of other instruments, the target identification information displayed in the dynamic identification area is dynamically determined according to a switching record, the switching record is used to record the source instrument identification and target instrument identification of at least one interface switching; a receiving module, configured to receive an interface control operation on the floating screen control, wherein the interface control operation is used to control the interface displayed by the instrument software interface; and a control module, configured to respond to the interface control operation and perform corresponding control on the interface displayed by the instrument software interface.

[0008] According to another aspect of the present invention, an in vitro diagnostic device is also provided, comprising: multiple instruments, a central control terminal, and a floating screen control. The central control terminal includes a core control module and a shared display page. The core control module is used to execute the above-described method. The multiple instruments are respectively connected to the central control terminal via a communication bus, and are used to transmit their respective instrument software interface data to the central control terminal. The core control module is also used to instantiate and manage the software interfaces of each instrument, load the software interface of the currently active instrument in the shared display page, and, when a user operates the floating screen control to trigger a switching command, unload the current instrument software interface instance and load the target instrument software interface instance according to the switching command, while updating the display content of the dynamic identification area of ​​the floating screen control. The floating screen control, as an independent interaction layer of the central control terminal, communicates with the core control module through an internal message mechanism. The display layer corresponding to the floating screen control is located above the display layer corresponding to the instrument software interface. The floating screen control includes a dynamic identification area, which is used to display target identification information of the software interfaces of other instruments. The target identification information displayed in the dynamic identification area is dynamically determined based on the switching record.

[0009] According to one aspect of the present invention, an electronic device is provided, comprising: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to execute the instructions to implement the instrument software interface display method described in any of the preceding claims.

[0010] According to one aspect of the present invention, a computer-readable storage medium is provided, wherein when the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform the instrument software interface display method described in any of the preceding claims.

[0011] In this embodiment of the invention, a shared display page is obtained, wherein the shared display page includes a floating screen control and an instrument software interface. The display layer corresponding to the floating screen control is located above the display layer corresponding to the instrument software interface. The instrument software interface is used to display the operation page corresponding to one instrument at the same time. The floating screen control includes a dynamic identifier area, which is used to display the target identifier information of the instrument software interface of other instruments. The target identifier information displayed in the dynamic identifier area is dynamically determined according to the switching record. The switching record is used to record the source instrument identifier and target instrument identifier of at least one interface switching. An interface control operation is received on the floating screen control, wherein the interface control operation is used to control the interface displayed on the instrument software interface. In response to the interface control operation, corresponding control is performed on the interface displayed on the instrument software interface. By adopting a multi-screen sharing and floating control approach, a floating screen control that is always on top and contains a dynamic identification area is integrated into the shared display page. The target identification information displayed in the dynamic identification area is dynamically determined based on the switching record. This achieves the goal of centralized display and control of the operation interface of each instrument using a single shared screen in multi-instrument online scenarios. This solves the technical problems of high hardware cost, low operation efficiency, and complex system maintenance caused by the one-machine-one-screen mode in multi-instrument online scenarios. Attached Figure Description

[0012] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0013] Figure 1 This is a flowchart of a method for displaying the instrument software interface according to an embodiment of the present invention;

[0014] Figure 2 This is a schematic diagram of the interface of the floating screen control provided in an optional embodiment of the present invention;

[0015] Figure 3 This is a schematic diagram of the floating state of the floating screen control when displaying the current instrument software interface, provided by an optional embodiment of the present invention;

[0016] Figure 4 This is a schematic diagram of the interface update after switching to another instrument software interface, provided by an optional embodiment of the present invention;

[0017] Figure 5This is a structural block diagram of a display device for an instrument software interface according to an embodiment of the present invention. Detailed Implementation

[0018] 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.

[0019] 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 embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0020] Example 1

[0021] According to an embodiment of the present invention, an embodiment of a method for displaying an instrument software interface is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0022] Figure 1 This is a flowchart of a method for displaying the instrument software interface according to an embodiment of the present invention, such as... Figure 1 As shown, the method includes the following steps:

[0023] Step S102: Obtain the shared display page, wherein the shared display page includes a floating screen control and an instrument software interface. The display layer corresponding to the floating screen control is located above the display layer corresponding to the instrument software interface. The instrument software interface is used to display the operation page corresponding to one instrument at the same time. The floating screen control includes a dynamic identification area, which is used to display the target identification information of the instrument software interface of other instruments. The target identification information displayed in the dynamic identification area is dynamically determined according to the switching record. The switching record is used to record the source instrument identification and target instrument identification of at least one interface switching.

[0024] Among them, the shared display page refers to the same display area used to centrally display the operation interfaces of multiple instruments, which can avoid configuring a separate dedicated screen for each instrument. For example, the operation interface containers of the pretreatment instrument and the chemiluminescence analyzer can be displayed on one screen at the same time.

[0025] Among them, floating screen controls refer to interactive elements that float in the shared display page. Their display layer is located above the instrument software interface, ensuring that they can be operated by the user at any time without being covered by other interfaces, such as a clickable circular icon.

[0026] The instrument software interface refers to the operation page corresponding to each instrument, which can display the operating status and operation options of each instrument, such as the control panel of the pretreatment instrument or the parameter setting page of the chemiluminescence analyzer.

[0027] Among them, the display layer refers to the hierarchical order of interface elements. The display layer corresponding to the floating screen control is located above the display layer corresponding to the instrument software interface, which can ensure that the floating screen control is always visible and operable. For example, the floating screen control will not be obscured by the pop-up window of the instrument software interface.

[0028] The dynamic identifier area refers to a variable area on the floating screen control used to display switching target information. It can update the displayed content in real time according to the switching record, such as displaying an icon or text for "Return to Preprocessor".

[0029] Among them, target identification information refers to the identification content of the operating interface of other instruments that are different from the current instrument. It can indicate the target instrument to be switched to next, such as displaying the icon or name of the chemiluminescence analyzer.

[0030] The switching record refers to the historical data of instrument software interface switching stored in the system, which is used to dynamically determine target identification information, such as instrument information before and after the most recent switching.

[0031] Among them, the source instrument identifier refers to the unique identifier corresponding to the instrument software interface displayed before the switching operation occurs, which can be used to identify the starting point of the switching, such as the preprocessor.

[0032] Among them, the target instrument identifier refers to the unique identifier corresponding to the instrument software interface displayed after the switching operation occurs, which can be used to identify the endpoint of the switching, such as a chemiluminescence analyzer.

[0033] In this step, a shared display page containing floating controls and instrument software interfaces is acquired. The floating controls are always on top, and their dynamic identification area displays target identification information for other instruments based on the switching history. This step enables centralized management of multiple instrument software interfaces on a single screen, providing a foundation for subsequent switching operations and avoiding hardware redundancy across multiple screens. Simultaneously, the dynamic identification mechanism based on switching history provides a data basis for subsequent one-click reversal, further reducing the user's operational burden and screen hardware redundancy.

[0034] Step S104: Receive interface control operation on the floating screen control, wherein the interface control operation is used to control the interface displayed by the instrument software interface.

[0035] Interface control operations refer to the interactive actions performed by the user on the floating screen controls, which are used to control the interface displayed by the instrument software, such as clicking on the dynamic indicator area or dragging the floating screen controls.

[0036] In this step, the system receives user input to control the floating screen controls, which is intended to control the currently displayed instrument software interface. This step establishes an interaction channel between the user and the single-screen system, enhancing the directness of operation.

[0037] Step S106: In response to the interface control operation, perform corresponding control on the interface displayed on the instrument software interface.

[0038] Among them, executing the corresponding control refers to the behavior of changing the displayed content or status of the instrument software interface according to the interface control operation, such as switching the interface, adjusting the layout, or updating data.

[0039] In this step, in response to the interface control operation, corresponding control actions are executed on the interface displayed on the instrument software. This step enables users to uniformly control multiple instrument software interfaces via floating screen controls, eliminating the need to move between multiple physical screens, thereby reducing operation time and the risk of accidental touches, and improving operational efficiency and accuracy.

[0040] [Keywords] Through the above steps S102-S106, a shared display page is obtained, wherein the shared display page includes a floating screen control and an instrument software interface. The display layer corresponding to the floating screen control is located above the display layer corresponding to the instrument software interface. The instrument software interface is used to display the operation page corresponding to one instrument at the same time. The floating screen control includes a dynamic identifier area, which is used to display the target identifier information of the instrument software interface of other instruments. The target identifier information displayed in the dynamic identifier area is dynamically determined according to the switching record, wherein the switching record is used to record the source instrument identifier and target instrument identifier of at least one interface switching; receive interface control operations on the floating screen control, wherein the interface control operations are used to control the interface displayed by the instrument software interface; respond to the interface control operations, perform corresponding control on the interface displayed by the instrument software interface. By adopting a multi-screen sharing and floating control approach, a floating screen control that is always on top and contains a dynamic identification area is integrated into the shared display page. The target identification information displayed in the dynamic identification area is dynamically determined based on the switching record. This achieves the goal of centralized display and control of the operation interface of each instrument using a single shared screen in multi-instrument online scenarios. This solves the technical problems of high hardware cost, low operation efficiency, and complex system maintenance caused by the one-machine-one-screen mode in multi-instrument online scenarios.

[0041] As an optional embodiment, in response to the interface control operation, corresponding control is performed on the interface displayed on the instrument software interface, including: when the interface control operation includes a click operation on the dynamic identification area and the corresponding control is a switching control, in response to the click operation, determining the click identification information corresponding to the click position; determining the target instrument software interface of the instrument to be switched to corresponding to the click identification information; and controlling the instrument software interface to switch to the target instrument software interface.

[0042] Among them, the click operation refers to the interactive action of pressing and releasing on the dynamic marker area by the user, which can trigger interface switching instructions, such as left mouse click or finger touch click.

[0043] The click location refers to the specific coordinates of the click operation within the dynamically marked area. This can be used to distinguish the target selected by the user. For example, clicking the left side of the area corresponds to the previous instrument, and clicking the right side corresponds to the next instrument.

[0044] Among them, the click identification information refers to the identification content corresponding to a specific instrument that is parsed from the click location, which can uniquely determine the target instrument software interface to be switched.

[0045] The instrument to be switched to refers to the instrument that the user intends to switch to. Its operation interface will replace the current interface, for example, switching from the pretreatment instrument to the chemiluminescence immunoassay analyzer.

[0046] The target instrument software interface refers to the operation page corresponding to the instrument to be switched, which can display the status, parameters and control items of the instrument, such as the main control interface of a chemiluminescence analyzer.

[0047] Optionally, the click operation can be triggered by different methods such as single click, double click, or long press; the click identification information can be obtained through a click area mapping table or a dynamic parsing algorithm; transition animations can be added during the switching process to enhance visual feedback.

[0048] In this embodiment, when a user clicks the dynamic indicator area of ​​the floating screen control, the system first parses the corresponding click indicator information based on the click location, then locates the target instrument software interface based on the indicator information, and finally performs a complete switch from the current instrument software interface to the target instrument software interface. This method achieves precise switching based on click location, eliminating the need for users to move their gaze between multiple screens or perform complex menu selections; a single click is sufficient to complete the interface transition. This mechanism significantly shortens the operation path and reduces the risk of accidental touches caused by multiple clicks or cross-screen operations. It is particularly suitable for scenarios in production lines where frequent switching of monitoring instruments is required, significantly improving operational efficiency and accuracy.

[0049] As an optional embodiment, after the control instrument software interface is switched to the target instrument software interface, the method further includes: determining an update switching record based on the instrument software interface before the switch; updating the target identification information displayed in the dynamic identification area of ​​the floating screen control based on the update switching record to obtain updated identification information, so as to indicate the instrument software interface to be switched to by the next click operation.

[0050] The instrument software interface before switching refers to the instrument operation page displayed on the screen before this switching operation is performed. It can serve as a candidate target for the next switching, such as the preprocessor interface currently being displayed.

[0051] Among them, updating the switching record refers to storing the instrument information before and after the current switching into the system memory, replacing the old most recent switching information, which can be used for subsequent quick switching back. For example, if the record is changed from A to B, the next time it can be directly switched back to A.

[0052] Among them, updating the identification information refers to the content displayed in the dynamic identification area that is regenerated based on the latest switching record. This information can prompt the user to return to the instrument software interface the next time they click, such as displaying a text label indicating that they will return to the preprocessor.

[0053] Optionally, the switching history can store the most recent switching history and provide a history list for users to select through a floating screen control; the form of updating the identification information can change dynamically (such as color, animation, text description) to enhance the prompt effect; this mechanism can also be combined with quick gestures to achieve more flexible switching back.

[0054] In this embodiment, after the interface switch is completed, the system updates the internally stored switching record based on the instrument software interface before the switch, and then regenerates the target identification information displayed in the dynamic identification area based on the updated record. This allows the user to intuitively know which instrument software interface will be switched to the next time the floating screen control is clicked. This method achieves quick back-and-forth switching based on memory (i.e., a one-click back-switch mechanism). Users do not need to manually remember the instrument they last operated on, nor do they need to reselect from multiple options; they only need to click the floating screen control again to return to the previous interface. This design aligns with operational intuition, effectively reducing the time spent searching and repeatedly selecting, and is particularly suitable for pipeline scenarios that require frequent back-and-forth monitoring between two main instruments, significantly improving the smoothness of operation and the user-friendliness of human-computer interaction.

[0055] As an optional embodiment, controlling the switching of the instrument software interface to the target instrument software interface includes: obtaining the current resolution parameters of the shared display page; performing an interface parameter adjustment operation on the target instrument software interface based on the current resolution parameters and a resolution adaptation algorithm to obtain the target instrument software interface after parameter adjustment, wherein the interface parameter adjustment operation includes at least one of the following: adjusting the display ratio parameters of the instrument software interface, adjusting the control size parameters in the instrument software interface; and controlling the switching of the instrument software interface to the target instrument software interface after parameter adjustment.

[0056] The current resolution parameter refers to the current pixel width and height values ​​of the shared display page, which reflects the screen's display capabilities, such as 1920×1080.

[0057] Among them, the resolution adaptation algorithm refers to the rule of calculating the scaling factor based on the ratio of the original design resolution to the actual display resolution. It can automatically match display devices of different specifications. For example, when the target resolution is different from the reference resolution, the interface elements are enlarged or reduced proportionally.

[0058] Among them, the interface parameter adjustment operation refers to the process of modifying the display attributes of the target instrument software interface, which can ensure that the interface is presented completely and without distortion at different resolutions, such as overall scaling or partial rearrangement.

[0059] The display scaling parameter refers to the scaling factor of the overall width and height of the interface, which can maintain the relative position and proportional relationship of the interface content, such as enlarging the original 800×600 interface to 1600×1200.

[0060] Among them, the control size parameter refers to the width, height, font size and other values ​​of interactive elements such as buttons, text boxes, and charts in the interface, which can ensure that the control is clearly clickable on both large and small screens. For example, the button width can be adjusted from 80 pixels to 160 pixels.

[0061] Optionally, the resolution adaptation algorithm can support real-time adjustment during dynamic screen rotation (switching between portrait and landscape modes); different adaptation strategies can be preset for different instrument software interfaces (such as maintaining aspect ratio scaling, filling the screen, leaving black borders, etc.); the adjusted parameters can be cached to accelerate subsequent switching.

[0062] Optionally, the specific steps of the resolution adaptation algorithm include: Step a1, obtaining the original design resolution (W0, H0) of the target instrument software interface and the current resolution (W1, H1) of the shared display page; Step a2, calculating the width scaling factor Sw = W1 / W0 and the height scaling factor Sh = H1 / H0; Step a3, determining the final scaling factor S according to the preset adaptation strategy, wherein S = min(Sw, Sh) under the aspect ratio maintenance strategy, Sw and Sh are applied respectively under the filling strategy, and S = min(Sw, Sh) and centered in the shorter direction under the black border retention strategy; Step a4, adjusting the display ratio parameters of the target instrument software interface according to the final scaling factor S, and scaling the control size parameters in the interface proportionally by S; Step a5, rendering the adjusted target instrument software interface to the shared display page.

[0063] In this embodiment, before switching to the target instrument software interface, the system first obtains the current resolution parameters of the shared display page. Then, using a built-in resolution adaptation algorithm, it automatically adjusts the display ratio and / or control size of the target instrument software interface, and finally presents the adjusted interface to the user. In this way, different instrument software interfaces can seamlessly adapt to a shared screen of any resolution without manual intervention or the development of a separate interface version for each resolution. This avoids problems such as content clipping, controls being too small to touch, blurry fonts, or layout errors caused by resolution mismatches in traditional solutions, ensuring a consistent user experience under different hardware conditions. At the same time, this mechanism reduces the development and maintenance costs of multi-resolution adaptation and improves the system's versatility and deployment flexibility.

[0064] As an optional embodiment, after obtaining the shared display page, the method further includes: receiving a drag operation on the floating screen control; moving the display position of the floating screen control to the drag target position according to the drag operation; determining whether the drag target position is within the visible area boundary of the shared display page according to a boundary constraint algorithm; constraining the floating screen control within the visible area boundary and fixing the floating screen control at the constrained display position if the drag target position exceeds the visible area boundary, wherein the constrained display position is the position within the visible area boundary that is closest to the drag target position in a straight line, and / or fixing the floating screen control at the drag target position if the drag target position does not exceed the visible area boundary.

[0065] The drag-and-drop operation refers to the action of a user pressing and holding a floating control and moving the mouse or finger on the screen, which can change the position of the control on the screen, such as long-pressing the control and dragging it to the lower right corner.

[0066] The drag target position refers to the screen coordinates where the control should have reached when the drag operation ended. It reflects the position the user intended to place the control, such as coordinates (100, 200).

[0067] Among them, the boundary constraint algorithm refers to the calculation logic used to determine whether the dragged target position exceeds the visible area of ​​the screen and to calculate the legal final position. It can prevent the control from being dragged off the screen and becoming inoperable. For example, when the right edge of the target position exceeds the right boundary of the screen, the control is automatically moved to the left.

[0068] The visible area boundary refers to the four edge lines of the effective display area that the user can see in the shared display page. Controls outside this area will not be visible. For example, the left edge of the screen is x=0 and the right edge is x=1920.

[0069] Among them, the constraint display position refers to the legal control position after being corrected by the boundary constraint algorithm, which can ensure that the entire control is completely within the visible area. For example, the target position (1900,100) is corrected to (1840,100) (assuming the control width is 80 pixels).

[0070] Optionally, it can provide a function to remember the position of the control, and automatically restore the last position when it is launched again; it can set the control to snap to the edge or automatically hide part of the area; it can support multi-finger gestures or use shortcut keys to make more precise position adjustments.

[0071] Optionally, the specific steps of the boundary constraint algorithm include: Step b1, obtaining the width Cw and height Ch of the floating screen control, and the coordinates (Tx, Ty) of the drag target position; Step b2, determining whether Tx < 0 or Tx + Cw > Sw or Ty < 0 or Ty + Ch > Sh, where Sw and Sh are the width and height of the visible area of ​​the shared display page, respectively; Step b3, if Tx < 0, then Tx is corrected to 0; if Tx + Cw > Sw, then Tx is corrected to Sw - Cw; if Ty < 0, then Ty is corrected to 0; if Ty + Ch > Sh, then Ty is corrected to Sh - Ch; Step b4, using the corrected coordinates (Tx', Ty') as the constraint display position, and controlling the floating screen control to be fixed at this position.

[0072] In this embodiment, users can freely drag and drop floating controls to any position on the screen using a mouse or touch. The system detects the target position in real time and uses a boundary constraint algorithm to determine whether it exceeds the visible area boundary. If it does, the control is automatically constrained to the nearest legal position within the boundary; if it does not exceed the boundary, it is directly fixed at the user-specified position. In this way, users can flexibly adjust the position of the floating controls according to their personal operating habits and the interface area of ​​the main instrument software currently being monitored, preventing them from obscuring key information. Simultaneously, the boundary constraint mechanism ensures that the controls will never be dragged off-screen and lost, guaranteeing their continued availability. This design enhances the personalization and convenience of the interaction while improving the system's robustness, avoiding the problem of controls becoming invisible due to accidental operation and preventing subsequent switching.

[0073] As an optional embodiment, the method further includes: obtaining the new instrument software interface corresponding to the new instrument; associating the new instrument software interface with the set of displayable interfaces of the shared display page to obtain an updated display interface set, so that when performing interface control operations on the floating screen control, the identification information corresponding to the new instrument software interface is used as one of the candidate identification information that can be displayed in the dynamic identification area.

[0074] Among them, the newly added instrument software interface refers to the software operation page developed for the new equipment after it is added to the production line, which can control or monitor the new equipment, such as the operation interface of the newly added sample sorter.

[0075] The set of displayable interfaces refers to the total set of all instrument operation pages that can be switched and displayed on the shared display page. It can limit the scope that users can access through the floating screen control, such as including the interfaces of the pretreatment instrument, chemiluminescence analyzer, and biochemical analyzer.

[0076] The updated display interface set refers to the new set of displayable interfaces obtained after adding the software interfaces of the newly added instruments. This can expand the management scope of the system, for example, to become a set of interfaces that includes four instruments.

[0077] Among them, candidate identifier information refers to the target identifier that users can select and switch in the dynamic identifier area. After clicking, users can switch to the interface of the corresponding newly added instrument, such as the icon or text label corresponding to the newly added instrument.

[0078] Optionally, newly added instrument software interfaces can be automatically discovered and pushed to the shared display page via the network; existing instrument software interfaces can be dynamically removed or disabled without affecting other instruments; priority or group display can be set for newly added instrument software interfaces.

[0079] In this embodiment, when a new instrument needs to be introduced into the pipeline, the system only needs to obtain the software interface of the new instrument through software configuration and associate it with the set of displayable interfaces on the shared display page, thereby forming an updated set of interfaces. Subsequently, when the user operates the floating screen controls, the identification information corresponding to the new instrument's software interface will automatically appear in the dynamic identification area, becoming one of the selectable candidate targets. In this way, the entire expansion process does not require adding any physical display screens, rewiring, or changing the hardware structure; it can be completed solely through software configuration. This significantly reduces the hardware cost and implementation cycle of pipeline expansion, avoiding the rigid constraint of needing to add a dedicated screen for each new instrument in the traditional one-machine-one-screen model. At the same time, this mechanism maintains the consistency of the unified operation entry point on a single screen, allowing operators to manage and monitor new instruments without learning new interaction methods, significantly improving the system's scalability and maintenance efficiency.

[0080] As an optional embodiment, the dynamic identification area is provided with predetermined identification parameters, which include at least one of the following: predetermined icon style, predetermined icon color, and predetermined text label.

[0081] Among them, the predefined identification parameters refer to the set of appearance attributes that can be configured when the dynamic identification area displays content, which enables the target identification information to be presented in a variety of visual forms, such as icons, colors, text, or combinations thereof.

[0082] Among them, the predetermined icon style refers to the type or shape of the graphic symbol set in advance, which can intuitively represent the type or function of a specific instrument. For example, a test tube icon can represent a pretreatment instrument, and a luminescent symbol can represent a chemiluminescence analyzer.

[0083] Among them, the pre-assigned icon colors refer to the different colors assigned to different icons in advance, which can help users quickly distinguish the target instruments. For example, red represents alarm instruments and green represents standby instruments.

[0084] Among them, the pre-defined text label refers to the short text attached next to the icon or displayed separately, which can clearly indicate the name of the instrument or operation, such as returning to the centrifuge or switching to the biochemical analyzer.

[0085] Optionally, it can support users to customize preset identification parameters (such as uploading personalized icons or changing colors); it can support dynamically changing preset parameters according to the instrument status (such as the icon flashing red when there is a malfunction); and it can support automatic switching of multilingual text labels.

[0086] In this embodiment, the dynamic identification area is pre-configured with at least one predetermined parameter among icon style, icon color, and text label to define how the target identification information is displayed. This allows users to quickly identify the target instrument to be switched to based on color, graphics, or text content, without needing to read lengthy instructions or engage in additional thought, thus reducing cognitive burden and operational error rates. Simultaneously, the flexibility of the predetermined identification parameters allows for customized displays based on different usage scenarios (such as dark environments, high brightness, multiple languages, and user color perception differences), enhancing the user-friendliness and universality of the interface. Furthermore, unified identification parameter settings also help maintain visual consistency when switching between multiple instruments, improving professionalism and brand recognition.

[0087] As an optional embodiment, the update switching record includes a source instrument identifier and a target instrument identifier. The source instrument identifier is the instrument identifier corresponding to the instrument software interface displayed before the switch, and the target instrument identifier is the instrument identifier corresponding to the instrument software interface displayed after the switch. The update method of the update switching record is to replace the corresponding identifiers in the previous switching record with the source instrument identifier and target instrument identifier of this switch.

[0088] In this embodiment, after each interface switch, the system directly overwrites the corresponding identifiers in the previous switch record with the source instrument identifier (instrument before the switch) and the target instrument identifier (instrument after the switch). This ensures that the switch record always retains only the correspondence of the most recent switch. For example, if the previous record was (A→B), and the current switch is from B to C, the record is updated to (B→C). In this way, the switch record always maintains only the source and target of the most recent switch, resulting in minimal storage overhead and eliminating the need to maintain complex historical linked lists. When the user clicks the floating screen control again, the system can directly and quickly locate the previously displayed instrument interface based on the latest record, achieving efficient one-click back navigation. This mechanism simplifies the data model, reduces memory usage, and ensures the real-time performance and accuracy of back-and-forth switching.

[0089] As an optional embodiment, switching the control instrument software interface to the target instrument software interface includes: acquiring the operating status information of the instrument to be switched; generating a safety confirmation prompt when the operating status information indicates that the instrument to be switched is in a preset protection state; receiving a confirmation operation on the safety confirmation prompt; and switching the control instrument software interface to the target instrument software interface in response to the confirmation operation.

[0090] Among them, the operating status information refers to the data that characterizes the current working status of the instrument to be switched, and can reflect whether the instrument can safely switch interfaces, such as running, standby, fault, cleaning, etc.

[0091] Among them, the preset protection state refers to a set of instrument states that are predefined and require user confirmation before switching interfaces. This can prevent data loss or equipment malfunction caused by accidental switching during critical operations, such as when testing is in progress, centrifugation has not stopped, or the reaction has not been completed.

[0092] Among them, the safety confirmation prompt message refers to the dialog box or prompt bar generated by the system asking the user whether to continue switching. It can remind the user that the current instrument is in a protection state. For example, a pop-up window may show that the instrument is running and ask whether the user still wants to switch.

[0093] The confirmation action refers to the user's positive response to the security confirmation prompt, such as clicking the confirmation switch button or pressing the Y key.

[0094] In this embodiment, before switching to the target instrument interface, the system first obtains the operating status of the instrument to be switched to. If the instrument is in a preset protection state (such as undergoing an uninterrupted test), a safety confirmation prompt is generated, and the switch is only executed after the user explicitly confirms. This method avoids situations where users cannot monitor critical processes in a timely manner or accidentally interrupt important workflows due to arbitrary interface switching, and is particularly suitable for scenarios in medical testing pipelines where certain instruments cannot be interrupted during sample analysis. This mechanism provides flexible interface switching while adding a security protection layer, reducing the risk of accidental operation, and improving system reliability and user trust.

[0095] As an optional embodiment, the predetermined identifier parameters displayed in the dynamic identifier area of ​​the floating screen control are dynamically determined according to the operating status of the corresponding instrument, wherein the operating status includes at least one of the following: running status, standby status, and fault status; when the corresponding instrument is in a fault status, the predetermined icon color is changed to a preset alarm color, and / or the predetermined icon style is displayed in the form of a preset animation.

[0096] The "operating status" indicates that the instrument is performing major tasks such as testing, analysis, and pipetting, and can indicate that the instrument is not idle, such as a chemiluminescence analyzer incubation.

[0097] The standby state refers to an instrument that is powered on but not performing its main tasks, is capable of accepting new tasks, or is in an idle preparation stage, such as a preprocessor waiting to load samples.

[0098] Among them, fault status refers to an instrument malfunction or abnormality that requires manual intervention, which can prompt the user to handle it in a timely manner, such as a centrifuge rotor jamming.

[0099] Among them, preset alarm colors refer to pre-set color values ​​used for warning, which can attract users' attention, such as red and orange.

[0100] Among them, preset animation forms refer to pre-set dynamic visual effects that can enhance the warning effect, such as icons flashing, rotating, or jumping.

[0101] In this embodiment, the icon style, color, or text label displayed in the dynamic identification area automatically changes according to the real-time operating status of the corresponding instrument. For example, when an instrument malfunctions, its icon turns red and flashes. In this way, users can intuitively perceive the health status of each instrument through the indicators on the floating screen control without switching to the instrument's interface, facilitating quick location and priority handling of malfunctioning devices. This design integrates status monitoring with the interface switching control, reducing additional status monitoring operations, improving problem response speed, and reducing the risk of production line downtime due to delayed fault detection.

[0102] As an optional embodiment, the floating screen control is a system-level top-mounted window, whose window properties are set to not be covered by a predetermined window of the instrument software interface, and the window level value of the floating screen control is greater than the window level value of the instrument software interface. The predetermined window includes at least one of the following: a pop-up window, or other application windows.

[0103] Among them, system-level top-mounted windows refer to window types set at the operating system level to always be displayed on the front. Their display position is not affected by other applications or pop-ups, ensuring that floating screen controls are visible under any operation, such as the Topmost property in Windows systems.

[0104] Among them, the window level value refers to the Z-order value assigned to each window by the operating system. The larger the value, the higher the display priority. It can quantify and control the relationship between the upper and lower layers of the window. For example, the level value of the floating screen control is 100, and the level value of the instrument software interface is 10.

[0105] Pop-ups refer to temporary sub-windows that appear from the instrument software interface, used for prompts, input, or confirmation, such as parameter setting dialog boxes.

[0106] Other application windows refer to software windows other than the current instrument software interface and floating screen controls, such as the system notification bar and third-party monitoring program windows.

[0107] In this embodiment, the floating control is set as a system-level top-level window, with a window hierarchy value greater than that of the instrument software interface, any pop-ups, and other applications, thus ensuring that the floating control is never covered. In this way, regardless of the user's operation within the instrument software interface (such as opening deep menus or popping up modal dialog boxes), the floating control remains visible and operable, guaranteeing the absolute availability of the interface switching entry point. This avoids the problem of traditional controls becoming unclickable due to being obscured by pop-ups, and is particularly suitable for pipeline monitoring scenarios requiring frequent instrument switching, significantly improving the continuity and reliability of operations.

[0108] As an optional embodiment, when the instrument software interface currently displayed on the shared display page is not the target alarm instrument, alarm identification information corresponding to the target alarm instrument is overlaid on the floating screen control. The alarm identification information is presented in a preset visual form according to the alarm level of the target alarm instrument. The preset visual form includes at least one of the following: flashing animation, alarm color overlay, and alarm text prompt.

[0109] Among them, the target alarm instrument refers to the instrument that has malfunctioned or requires user attention, rather than the instrument that is currently being displayed. For example, the pretreatment instrument is currently being displayed, but the chemiluminescence analyzer has malfunctioned.

[0110] Among them, alarm label information refers to visual symbols or text used to indicate abnormal instrument status, which can attract users' attention to problems of instruments that are not displayed, such as the text indicating a malfunction of a light source.

[0111] Alarm level refers to the classification based on the severity of the anomaly, used to differentiate the presentation of alarms, such as general prompts, warnings, and serious errors.

[0112] Among them, blinking animation refers to the logo being displayed and hidden or changing its style alternately at a certain frequency, which can enhance the effect of capturing attention, such as blinking twice per second.

[0113] Among them, the warning color overlay refers to overlaying a warning color on the original icon or changing the overall color, so that the level can be distinguished by color. For example, yellow represents caution and red represents danger.

[0114] Among them, alarm text prompts refer to displaying brief descriptive text that can provide specific problem information, such as temperature exceeding the limit.

[0115] In this embodiment, when the currently displayed instrument is functioning normally but other instruments in the background are triggering alarms, the system will overlay alarm indicator information (such as flashing red dots or text) onto the floating screen control. The visual form of this alarm is related to the alarm level; the higher the level, the more prominent the alert. This method allows users to grasp the anomalies of all devices without having to switch between each instrument's interface individually, achieving focused interface coverage of the current instrument while ensuring comprehensive alarm coverage. This significantly improves anomaly response speed, prevents overlooking critical background faults due to the current interface only displaying normal instruments, and enhances the overall safety of the production line.

[0116] As an optional embodiment, the resolution adaptation algorithm adopts different adaptation strategy parameters for different instrument software interfaces. The adaptation strategy parameters are determined based on the original design resolution and interface layout type of each instrument software interface. The interface layout type includes at least one of the following: fixed size layout, flexible layout, and grid layout.

[0117] Among them, the adaptation strategy parameters refer to the set of preset scaling, alignment, and cropping rules for a specific instrument interface, which can enable different interfaces to achieve the best display effect at the same resolution, such as scaling ratio threshold, maintaining aspect ratio, and allowing margins.

[0118] Fixed-size layout refers to a layout method in which the position and size of interface elements are defined using absolute pixel values. This method can precisely control the display effect, but may require cropping or leaving margins when scaling, such as the numerical display area of ​​a dashboard.

[0119] Flexible layout refers to the positioning and scaling of interface elements according to a relative proportion (percentage), which can adapt to the screen size. For example, toolbar buttons are enlarged proportionally.

[0120] Among them, grid layout refers to the interface being divided into several rows and columns of grid, with elements placed within the grid cells. This allows for flexible adaptation to different resolutions while maintaining alignment, such as in a parameter settings panel.

[0121] In this embodiment, the resolution adaptation algorithm does not use the same scaling rules for all instrument interfaces. Instead, it employs different adaptation strategy parameters based on the original design resolution and layout type (fixed size, flexible, grid) of each interface. For example, a strategy of maintaining the aspect ratio and centering is used for fixed-size layout interfaces, while a percentage scaling strategy is used for flexible layout interfaces. In this way, each instrument interface can obtain the most suitable display effect for its own design on the shared display page, avoiding problems such as stretching distortion, content overlap, or inaccessible controls. This improves the visual consistency and operational accessibility of multiple instrument interfaces and reduces the probability of user misoperation due to poor adaptation.

[0122] As an optional embodiment, in response to interface control operations, an operation audit log is generated, which includes at least one of the following: operation time, operation type, source instrument identifier, target instrument identifier, and operator identity information; the operation audit log is stored in a traceable storage medium.

[0123] Among them, the operation audit log refers to the structured data entries that record user interface operation behavior. It can be used for post-event traceability, analysis of operation compliance or troubleshooting. For example, 2025-01-15, 10:23:45, switch, from preprocessor to light source, operator XX.

[0124] Operation time refers to the specific moment when the user performs an interface control operation, which can determine the timeline of the operation, such as the system timestamp.

[0125] Among them, operation type refers to the specific category of interface control operation, which can distinguish different control behaviors, such as switching, dragging, and clicking.

[0126] Among them, operator identity information refers to the unique identifier or role of the currently logged-in user, which can clearly identify the person responsible for the operation, such as employee ID or username.

[0127] Traceable storage media refers to non-volatile storage devices (such as hard drives, databases, and log servers) that can store logs for a long time without being tampered with, and support subsequent querying and analysis.

[0128] In this embodiment, each time a user performs an interface control operation on the floating screen control, the system generates an audit log containing fields such as operation time, operation type, source instrument identifier, target instrument identifier, and operator identity information, and stores it in a traceable storage medium. In this way, all interface switching behaviors are traceable, facilitating the identification of responsible persons and operation sequences in the event of operational errors or equipment accidents, and also meeting the compliance audit requirements of industries such as healthcare and pharmaceuticals. Simultaneously, the log data can be used to analyze operation frequency and habits, providing data support for optimizing interface layout and training operators.

[0129] As an optional embodiment, the role and permission information of the current operator is obtained; based on the role and permission information, a subset of candidate identifier information that can be displayed in the dynamic identifier area is determined; and the corresponding control is executed only if the target identifier information corresponding to the interface control operation belongs to the subset.

[0130] Among them, role permission information refers to the role to which the current operator belongs and the set of operating permissions granted to that role. This can restrict the range of instruments that different users can access. For example, the operator role can only switch to ordinary analyzers, while the administrator role can switch to all instruments, including the calibration interface.

[0131] The subset of candidate identifier information refers to the portion that the current operator is authorized to use, selected from all displayable candidate identifier information based on role and permission information. This enables refined control over interface switching; for example, the operator can only see and switch to instruments A and B, but not instrument C.

[0132] In this embodiment, the system first obtains the role and permission information of the currently logged-in operator. Then, based on this permission, it dynamically filters the candidate identifier information that can be displayed in the dynamic identifier area, showing only the identifiers corresponding to the instruments that the operator is authorized to switch. Users can only click to switch target identifier information within a subset. This method achieves multi-level permission management, preventing unauthorized users from accessing critical instruments (such as calibration and maintenance interfaces), ensuring the operational safety and data compliance of the production line. Simultaneously, permission filtering takes effect directly at the UI layer, reducing backend verification overhead and improving user experience and system security.

[0133] As an optional embodiment, the interface control operation includes at least one of the following: double-click operation on the floating screen control, preset gesture operation, and keyboard shortcut operation; wherein, the double-click operation is used to trigger a one-click back switch based on the switching record, the preset gesture operation includes a swiping operation on the floating screen control, and the keyboard shortcut operation includes an interface switching instruction corresponding to a preset shortcut combination.

[0134] Double-click operation refers to the action of quickly clicking the floating screen control twice in succession. It can be used as a quick trigger for one-click switching back. For example, double-clicking the control can immediately switch back to the previous instrument interface.

[0135] Among them, preset gesture operation refers to the predefined sliding trajectory of the finger on the touch screen, which can provide intuitive switching control, such as swiping left on the floating screen control to switch to the next instrument.

[0136] Keyboard shortcut operation refers to switching commands issued through key combinations (such as Ctrl and Tab), which can satisfy users who are accustomed to keyboard operation, such as pressing the F2 key to switch to a specific instrument.

[0137] One-click return refers to the function of directly returning to the most recently displayed instrument interface with a single operation, without having to select a target again. For example, after switching from interface A to B, double-clicking the floating screen control will immediately return to A.

[0138] In this embodiment, the interface control operation is not limited to clicking on the dynamic marker area, but also supports double-clicking, swipe gestures, keyboard shortcuts, and other methods. Double-clicking is specifically used to trigger a one-click back-switch based on the switching record, while swiping and shortcuts can quickly switch to a specific instrument. This approach meets the diverse needs of different operating habits and scenarios: touchscreen users can switch quickly using gestures, skilled operators can use keyboard shortcuts to improve efficiency, and double-clicking back-switching provides the most convenient switching path. This further shortens operation time, reduces the intensity of repetitive operations, and improves the flexibility and efficiency of human-computer interaction.

[0139] As an optional embodiment, the shared display page includes at least two floating screen controls, each of which corresponds to a set of software interfaces of a group of instruments. The display priority of different floating screen controls is coordinated through a hierarchical management module. In the case where the display areas of at least two floating screen controls overlap, the top-level floating screen control is determined according to the alarm level of the instrument corresponding to each floating screen control.

[0140] Among them, at least two floating screen controls refer to two or more independent floating controls existing on the same shared display page. Each control manages the switching of a group of instruments and can classify and manage instruments of different categories or locations. For example, one control manages the instruments in the sample pretreatment group, and another control manages the instruments in the detection and analysis group.

[0141] The hierarchy management module is a software component used to coordinate the display priority among multiple floating screen controls, which can avoid display conflicts, such as dynamically adjusting the Z order according to the alarm level.

[0142] Among them, the instrument alarm level refers to the highest alarm level in the instrument group corresponding to the floating screen control. It is used to determine whether the control should be displayed on the top layer. For example, if there is a serious fault in the instrument group corresponding to a control, its display priority is higher than that of other controls.

[0143] In this embodiment, multiple floating controls can coexist on the shared display page, each managing a different set of instruments. When controls overlap, the hierarchical management module displays the control with the highest alarm level on the top layer, based on the alarm level of the instrument group corresponding to each control. In this way, instruments in different areas or functions within the pipeline can be managed in groups, and emergency alarms will not be obscured by other controls. This supports flexible grouping operations for complex pipelines (such as dozens of instruments) while ensuring the visibility of important alarms, avoiding delays in processing due to interface obstruction.

[0144] As an optional embodiment, the instrument software interfaces of at least two instruments are simultaneously displayed in a split-screen layout on the shared display page, wherein the instrument software interface displayed in at least one split-screen area is in an active interactive state, and the instrument software interfaces displayed in the other split-screen areas are in a read-only monitoring state; the floating screen control is used to switch the instrument corresponding to the active interactive state in each split-screen area.

[0145] Split-screen layout refers to dividing a shared display page into multiple independent display areas, which can simultaneously display the interfaces of multiple instruments, such as two screens on the left and right or a four-grid layout.

[0146] The active interactive state refers to the state in which the user can interact with the controls in the split-screen area, such as clicking buttons or inputting parameters.

[0147] The read-only monitoring state refers to a state in which the user can only view the interface content but cannot perform any operations. This can prevent accidental operation while providing a monitoring view, such as displaying the instrument's operating curve in real time but disabling the control buttons.

[0148] Among them, the instruments corresponding to the active interactive states in each split-screen area refer to the instrument interfaces that are currently allowed to be operated by the user. The floating screen control can switch which instrument is in an active state.

[0149] In this embodiment, the shared display page uses a split-screen layout to simultaneously display multiple instrument interfaces, but only one split-screen area is in an active interactive state, while the others are only for read-only monitoring. A floating screen control is used to switch which instrument interface is in the active interactive state. In this way, users can monitor multiple instruments while centrally operating a single instrument, avoiding the overhead of frequent interface switching, while maintaining real-time observation of other devices. This is extremely useful for scenarios requiring parallel monitoring of multiple production lines, improving multitasking capabilities and operational efficiency.

[0150] As an optional embodiment, during the current instrument software interface display, the next target instrument to be switched is predicted based on the switching history, and the software interface instance of the target instrument is preloaded into the memory cache so that the software interface instance of the target instrument can be directly loaded from the memory cache when a switching command is received.

[0151] The switching history refers to the stored sequence data of multiple switching operations, which can be used to analyze user operation patterns, such as recording the sequence of the last 5 switching operations.

[0152] Among them, predicting the next target instrument to be switched to refers to estimating the instrument that the user is most likely to operate next based on historical patterns (such as frequently switching between the preprocessor and the luminescence analyzer), so as to prepare in advance.

[0153] Preloading refers to loading the resources (layout, data, controls) required by the instrument software interface into memory in advance, but not displaying them, which can shorten the waiting time during actual switching.

[0154] Among them, memory cache refers to the temporary storage area allocated in RAM, which has a much faster access speed than hard disk or network loading and can achieve instant switching.

[0155] In this embodiment, during the current interface display, the system predicts the instrument the user is most likely to switch to next based on the switching history (e.g., based on recently frequently switched instrument pairs), and then preloads the software interface instance of that instrument into the memory cache. When the user actually triggers the switching command, it is loaded directly from the cache with almost no delay. This significantly reduces the waiting time for interface switching, especially when instrument interface resources are large or network loading is slow. This improves the smoothness of operation and user satisfaction, meeting the needs of efficient pipeline operations.

[0156] Based on the above embodiments and optional embodiments, an optional implementation method is provided, which is described in detail below.

[0157] An optional embodiment of the present invention provides a method for displaying instrument software interfaces, which can also be described as a method and system for switching software interfaces of multiple instruments in an online scenario. This method utilizes single-screen sharing and floating control technology to centrally manage and quickly switch the software interfaces of multiple instruments using a single display screen, thereby reducing hardware costs, optimizing space layout, and improving operational efficiency and system maintainability. Figure 2 This is a schematic diagram of the interface of the floating screen control provided in an optional embodiment of the present invention. Figure 3 This is a schematic diagram of the floating state of the floating screen control when displaying the current instrument software interface, provided by an optional embodiment of the present invention. Figure 4 This is a schematic diagram of the interface update after switching to other instrument software interfaces, provided by an optional embodiment of the present invention, such as... Figure 2-4 As shown, a detailed introduction is given below:

[0158] In a multi-unit system, multiple instruments are connected to a central control terminal via a communication bus (e.g., TCP / IP LAN, serial communication bus, or USB interface). The central control terminal runs a host program with a shared display page, and the software interfaces of each instrument are integrated into this host program in a component-based manner. Specifically, each instrument transmits its interface data to the central control terminal via the communication bus. The core control module of the central control terminal instantiates and manages the software interfaces of each instrument and loads the software interface of the currently active instrument on the shared display page. The floating screen control, as an independent interaction layer of the central control terminal, communicates with the core control module through an internal message mechanism. When a user operates the floating screen control and triggers a switching command, the core control module unloads the current instrument software interface instance and loads the target instrument software interface instance according to the command content, while simultaneously updating the display content of the dynamically marked area of ​​the floating screen control.

[0159] 1. Floating screen control design and integration

[0160] Within the basic interface loaded on the shared display screen, a floating control is integrated. This floating control possesses the following characteristics: As the core interactive entry point for switching between multiple instrument software interfaces, this floating control has three core characteristics: floating capability, adjustable position, and visual label display. The specific descriptions of each characteristic are as follows:

[0161] (1) Floating: Global top-level persistent, unaffected by interface interaction: The floating screen control adopts an application-level top-level control, and its display layer is always above all instrument software interfaces. No matter which instrument's operation interface the user switches to, or performs various interactive operations such as clicking, inputting, or triggering pop-ups within that interface, the floating screen control will not be covered, obscured, or disappear by other windows or controls, ensuring that it is always visible and operable.

[0162] (2) Drag-and-drop customizable position: The floating screen control allows users to drag it using the mouse, touch screen, etc., and position it at any position in the screen's coordinate system (such as the upper right corner, middle, lower right corner, etc.). Operators can flexibly adjust the position of the control according to their personal operating habits and the current main focus area, and it can be stably fixed in the target position after release without offset or automatic reset; at the same time, the built-in boundary constraint algorithm can prevent the control from being dragged outside the visible area of ​​the screen, ensuring the practicality and convenience of position adjustment.

[0163] (3) Multi-form switching support: The switching of the icons is not limited to a single graphic replacement, but can be extended to: icon style switching, icon color switching, icon with attached text label switching, or a combination of the above elements switching.

[0164] 2. Implementation of switching logic for multiple instrument software interfaces

[0165] This controls and manages all instances of the instrument software interface. When the user clicks the switching icon on the floating screen control, a switching command is triggered. The following logic is executed.

[0166] (1) According to the instructions, switch the instrument software interface currently displayed on the shared screen to the target instrument software interface.

[0167] (2) Interface switching memory and quick return mechanism: The core control module records the user's most recent interface switching record. When the user operates the floating screen control again, the user can quickly switch back to the previous display interface (e.g., after switching from the pretreatment instrument software interface to the chemiluminescence instrument software interface, clicking the floating screen control again can directly switch back to the pretreatment interface), realizing flexible switching back and forth.

[0168] 3. Compatibility Design

[0169] (1) Resolution Adaptive: Built-in resolution adaptation algorithm can automatically adjust the display ratio and control size of each instrument software interface according to the resolution of the shared display screen, avoiding problems such as interface stretching, compression or content loss, and adapting to the access requirements of different display devices in the pipeline scenario.

[0170] As can be seen, through the above settings, the proposed multi-instrument software interface switching scheme based on floating screen controls uses a single display screen to achieve shared display of multiple instrument software interfaces in the production line. It can quickly and flexibly switch between different instrument software interfaces through floating screen controls, solving at least the following technical problems:

[0171] (1) High hardware cost and large space occupation. In the traditional way, each additional instrument requires a display screen and supporting hardware, which leads to a significant increase in procurement, installation and maintenance costs. Multiple display screens also occupy a lot of workbench or equipment installation space, which is not conducive to the miniaturization and integration of the production line.

[0172] (2) Low operational efficiency and prone to errors: Operators need to move frequently between screens in different locations, and the switching of their gaze can easily lead to visual fatigue and operation interruption. Differences in the interface layout of different instruments may also cause misoperation, affecting the accuracy and efficiency of the process.

[0173] (3) Complex system maintenance: The software interface of each instrument needs to be upgraded, debugged and maintained separately. When system-level updates are performed, the workload is large and the cycle is long, and version inconsistency is likely to occur.

[0174] (4) Low resource utilization: Each screen serves only a single instrument. When the instrument is idle or only displays static information, the screen and driver hardware are in a low utilization state, resulting in idle resources.

[0175] The above optional implementation methods can achieve at least the following beneficial effects:

[0176] (1) Significantly reduce hardware costs and space requirements. Replacing multiple dedicated displays with a single shared screen directly reduces the number of display devices and related driver hardware, generally reducing the procurement cost of display devices by more than 50%, while also greatly saving installation space and supporting a compact layout for production lines.

[0177] (2) Improve operational efficiency and accuracy. Operators can monitor and operate various instruments on the same screen without moving between multiple physical screens, shortening the operation path by more than 70% and significantly reducing operation time. The floating screen control clearly prompts the target switching through dynamic text, effectively preventing misoperation caused by interface confusion.

[0178] (3) Simplify system maintenance and management. All instrument software interfaces are managed uniformly through the core control module. Software updates can be completed at the central node in one go, without the need for upgrades to each instrument individually. This can improve maintenance efficiency by more than 60%, ensure system version consistency, and reduce maintenance complexity.

[0179] (4) Enhance system scalability and resource utilization. New instruments do not require additional screens and can be connected with only software configuration, reducing the system expansion cycle from several days to several hours. A single screen can efficiently serve multiple instruments, increasing the utilization rate of display devices to over 80%.

[0180] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the present invention is not limited to the described order of actions, because according to the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to the present invention.

[0181] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods of the various embodiments of the present invention.

[0182] Example 2

[0183] According to embodiments of the present invention, an apparatus for implementing the above-described display method for an instrument software interface is also provided. Figure 5 This is a structural block diagram of the display device for the instrument software interface according to an embodiment of the present invention, such as... Figure 5 As shown, the device includes: an acquisition module 502, a receiving module 504, and a control module 506. The device will be described in detail below.

[0184] The acquisition module 502 is used to acquire a shared display page, which includes a floating screen control and an instrument software interface. The display layer corresponding to the floating screen control is located above the display layer corresponding to the instrument software interface. The instrument software interface is used to display the operation page corresponding to one instrument at the same time. The floating screen control includes a dynamic identifier area, which is used to display the target identifier information of the instrument software interface of other instruments. The target identifier information displayed in the dynamic identifier area is dynamically determined based on the switching record. The switching record is used to record the source instrument identifier and target instrument identifier of at least one interface switching. The receiving module 504 is connected to the acquisition module 502 and is used to receive interface control operations on the floating screen control, wherein the interface control operations are used to control the interface displayed on the instrument software interface. The control module 506 is connected to the receiving module 504 and is used to respond to the interface control operations and perform corresponding control on the interface displayed on the instrument software interface.

[0185] Optionally, the device further includes a switching record update module, used to update the switching record based on the source instrument identifier and the target instrument identifier of the interface switching, wherein the source instrument identifier is the instrument identifier corresponding to the instrument software interface displayed before the switching, and the target instrument identifier is the instrument identifier corresponding to the instrument software interface displayed after the switching.

[0186] Optionally, the device further includes a safety confirmation module, which is used to obtain the operating status information of the instrument to be switched before switching to the target instrument software interface, generate a safety confirmation prompt message when the operating status information indicates that the instrument to be switched is in a preset protection state, and perform interface switching after receiving a confirmation operation for the safety confirmation prompt message.

[0187] Optionally, the device further includes: a status sensing and identification module, used to dynamically determine the predetermined identification parameters displayed in the dynamic identification area of ​​the floating screen control according to the operating status of the corresponding instrument, wherein the operating status includes at least one of the following: running status, standby status, and fault status; when the corresponding instrument is in a fault state, the predetermined icon color is changed to a preset alarm color, and / or the predetermined icon style is displayed in the form of a preset animation.

[0188] Optionally, the device further includes: a window management layer module, used to set the floating screen control as a system-level top window, whose window properties are set to not be covered by a predetermined window of the instrument software interface, and the window layer value of the floating screen control is greater than the window layer value of the instrument software interface, wherein the predetermined window includes at least one of the following: a pop-up window, or other application windows.

[0189] It should be noted that the above-mentioned acquisition module 502, receiving module 504 and control module 506 correspond to steps S102 to S106 in the method of displaying the instrument software interface. The multiple modules and the corresponding steps implement the same instances and application scenarios, but are not limited to the content disclosed in the above embodiment 1.

[0190] Example 3

[0191] According to another aspect of the present invention, an in vitro diagnostic device is also provided, comprising: multiple instruments, a central control terminal, and a floating screen control, wherein the central control terminal includes a core control module and a shared display page, and the core control module is used in the above-described method.

[0192] Multiple instruments and devices are connected to the central control terminal via a communication bus to transmit their respective instrument software interface data to the central control terminal.

[0193] The core control module is also used to manage the instantiation of the software interfaces of each instrument, load the software interface of the currently active instrument in the shared display page, and when the user operates the floating screen control to trigger a switching command, unload the current instrument software interface instance and load the target instrument software interface instance according to the switching command, while updating the display content of the dynamic identification area of ​​the floating screen control.

[0194] The floating screen control, as an independent interactive layer of the central control terminal, communicates with the core control module through an internal message mechanism. The display layer corresponding to the floating screen control is located above the display layer corresponding to the instrument software interface. The floating screen control includes a dynamic identifier area, which is used to display the target identifier information of the software interface of other instruments. The target identifier information displayed in the dynamic identifier area is dynamically determined according to the switching record.

[0195] Among them, multiple instruments and equipment refer to multiple hardware analysis or processing devices with different functions in the production line, which can perform tasks such as sample pretreatment, biochemical analysis, and immunoassay, such as sample pretreatment instruments, chemiluminescence analyzers, and biochemical analyzers.

[0196] The central control terminal refers to a host computer or embedded system that communicates with multiple instruments and equipment, and is used to centrally manage and display the software interface of each instrument, such as an industrial tablet computer or server.

[0197] Among them, the communication bus refers to the physical or wireless communication link connecting multiple instruments and equipment with the central control terminal, which can realize the transmission of data and control commands, such as TCP / IP LAN, serial communication bus or USB interface, CAN bus, Ethernet, RS485.

[0198] The core control module refers to the software unit in the central control terminal that is responsible for managing instrument software interface instances, processing switching logic, and updating dynamic identifiers. It can coordinate the lifecycle of interface resources in a unified manner, such as an interface manager or window controller.

[0199] Instantiation management refers to the process of creating, maintaining, and destroying memory objects for each instrument's software interface. It can efficiently control the occupation and release of interface resources, such as generating a unique interface object for each instrument and caching its state.

[0200] The independent interaction layer refers to the floating screen control existing as an independent layer at the same level as or even higher than the instrument software interface in the software architecture of the central control terminal. It does not depend on any specific instrument interface and can ensure its global availability. For example, the floating screen control is designed as a desktop-level floating window rather than embedded inside the instrument interface.

[0201] The internal message mechanism refers to the communication method between the core control module and the floating screen control through a predefined message protocol, which can decouple the interface display and switching logic. For example, when the user clicks the floating screen control, the control sends a message, and the core control module receives it and performs the switching.

[0202] This system, with its aforementioned architecture, enables centralized display and control of multiple instruments on a single shared screen, reducing hardware costs and improving operational efficiency. The entire system consists of multiple instruments, a central control terminal (including a core control module and a shared display page), and floating screen controls. Instruments transmit their respective software interface data to the central control terminal via a communication bus. The core control module instantiates and manages the interfaces, loads the interface of the currently active instrument on the shared display page, and responds to switching commands from the floating screen controls by unloading the old interface and loading the new one, while simultaneously updating the dynamic identifier area. The floating screen controls, as an independent interaction layer, communicate with the core control module through an internal message mechanism. This approach forms a complete closed-loop system from physical devices to interface management and user interaction, achieving centralized hardware deployment (multiple instruments connected to a single screen), dynamic software switching (based on instantiation loading / unloading), and highly reliable communication (internal message decoupling). In actual pipeline deployments, this system significantly reduces hardware procurement and cabling costs, shortens system response time, and, due to centralized management of the core control module, upgrades and maintenance of all instrument interfaces can be completed on the terminal side without requiring individual instrument operation, greatly improving system integration and operational efficiency. Simultaneously, the independent interaction layer and messaging mechanism ensure that the floating screen controls respond promptly to switching commands under any interface operation, enhancing system robustness and user experience.

[0203] Example 4

[0204] According to another aspect of the present invention, an electronic device is also provided, comprising: a processor; and a memory for storing processor-executable instructions, wherein the processor is configured to execute instructions to implement the instrument software interface display method of any of the above embodiments.

[0205] Example 5

[0206] According to another aspect of the present invention, a computer-readable storage medium is also provided, which, when the instructions in the computer-readable storage medium are executed by the processor of an electronic device, enables the electronic device to perform the instrument software interface display method described above.

[0207] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0208] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0209] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0210] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0211] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0212] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0213] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for displaying an instrument software interface, characterized in that, include: A shared display page is obtained, wherein the shared display page includes a floating screen control and an instrument software interface. The display layer corresponding to the floating screen control is located above the display layer corresponding to the instrument software interface. The instrument software interface is used to display the operation page corresponding to one instrument at the same time. The floating screen control includes a dynamic identification area. The dynamic identification area is used to display the target identification information of the instrument software interface of other instruments. The target identification information displayed in the dynamic identification area is dynamically determined based on the switching record. The switching record is used to record the source instrument identification and target instrument identification of at least one interface switching. Receive interface control operations on the floating screen control, wherein the interface control operations are used to control the interface displayed by the instrument software interface; In response to the interface control operation, corresponding control is performed on the interface displayed by the instrument software interface.

2. The method according to claim 1, characterized in that, In response to the interface control operation, corresponding control is performed on the interface displayed by the instrument software interface, including: When the interface control operation includes a click operation on a dynamic identifier area, and the corresponding control is a switching control, the click identifier information corresponding to the click position is determined in response to the click operation. Determine the target instrument software interface of the instrument to be switched to corresponding to the click identifier information; The instrument software interface is switched to the target instrument software interface.

3. The method according to claim 2, characterized in that, After controlling the instrument software interface to switch to the target instrument software interface, the method further includes: Based on the instrument software interface before the switch, determine and update the switch record; Based on the update switching record, the target identifier information displayed in the dynamic identifier area of ​​the floating screen control is updated to obtain updated identifier information, which indicates the instrument software interface to be switched to the next click operation.

4. The method according to claim 2, characterized in that, Controlling the switching of the instrument software interface to the target instrument software interface includes: Obtain the current resolution parameters of the shared display page; Based on the current resolution parameters and the resolution adaptation algorithm, an interface parameter adjustment operation is performed on the target instrument software interface to obtain the target instrument software interface after parameter adjustment. The interface parameter adjustment operation includes at least one of the following: adjusting the display ratio parameter of the instrument software interface, and adjusting the control size parameter in the instrument software interface. The instrument software interface is switched to the target instrument software interface after the parameters are adjusted.

5. The method according to claim 1, characterized in that, After obtaining the shared display page, it also includes: Receive drag operations on the floating screen control; Based on the drag operation, the display position of the floating screen control is moved to the drag target position; Based on the boundary constraint algorithm, determine whether the position of the dragged target is within the visible area boundary of the shared display page; If the dragged target position exceeds the boundary of the visible area, the floating screen control is constrained within the boundary of the visible area and fixed at the constrained display position, wherein the constrained display position is the position within the boundary of the visible area that is closest to the dragged target position in a straight line, and / or, if the dragged target position does not exceed the boundary of the visible area, the floating screen control is fixed at the dragged target position.

6. The method according to claim 1, characterized in that, The method also includes: Obtain the new instrument software interface corresponding to the new instrument; The newly added instrument software interface is associated with the set of displayable interfaces of the shared display page to obtain an updated set of display interfaces. When performing interface control operations on the floating screen control, the identification information corresponding to the newly added instrument software interface is used as one of the candidate identification information that can be displayed in the dynamic identification area.

7. The method according to claim 2, characterized in that, Controlling the switching of the instrument software interface to the target instrument software interface includes: Obtain the operating status information of the instrument to be switched; if the operating status information indicates that the instrument to be switched is in a preset protection state, generate a safety confirmation prompt message; Receive confirmation of the security confirmation prompt message; In response to the confirmation operation, the instrument software interface is switched to the target instrument software interface.

8. The method according to claim 1, characterized in that, The shared display page includes at least two floating screen controls, each of which corresponds to a set of instrument software interfaces. The display priority of different floating screen controls is coordinated through a hierarchical management module. In the case where the display areas of the at least two floating screen controls overlap, the top-level floating screen control is determined based on the instrument alarm level corresponding to each floating screen control.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: simultaneously displaying the instrument software interfaces of at least two instruments in a split-screen layout on the shared display page, wherein the instrument software interface displayed in at least one split-screen area is in an active interactive state, and the instrument software interfaces displayed in the other split-screen areas are in a read-only monitoring state; the floating screen control is used to switch the instruments corresponding to the active interactive state in each split-screen area.

10. A display device for an instrument software interface, characterized in that, include: The acquisition module is used to acquire a shared display page, wherein the shared display page includes a floating screen control and an instrument software interface. The display layer corresponding to the floating screen control is located above the display layer corresponding to the instrument software interface. The instrument software interface is used to display the operation page corresponding to one instrument at the same time. The floating screen control includes a dynamic identification area, which is used to display the target identification information of the instrument software interface of other instruments. The target identification information displayed in the dynamic identification area is dynamically determined based on the switching record. The switching record is used to record the source instrument identification and target instrument identification of at least one interface switching. A receiving module is used to receive interface control operations on the floating screen control, wherein the interface control operations are used to control the interface displayed by the instrument software interface. The control module is used to respond to the interface control operation and perform corresponding control on the interface displayed by the instrument software interface.

11. The apparatus according to claim 10, characterized in that, Also includes: The switching record update module is used to update the switching record based on the source instrument identifier and the target instrument identifier of the interface switching, wherein the source instrument identifier is the instrument identifier corresponding to the instrument software interface displayed before the switching, and the target instrument identifier is the instrument identifier corresponding to the instrument software interface displayed after the switching.

12. The apparatus according to claim 10, characterized in that, Also includes: The window management layer module is used to set the floating screen control as a system-level top window, whose window properties are set to not be covered by a predetermined window of the instrument software interface, and the window layer value of the floating screen control is greater than the window layer value of the instrument software interface. The predetermined window includes at least one of the following: a pop-up window, or other application windows.

13. An in vitro diagnostic device, characterized in that, include: The system includes multiple instruments and equipment, a central control terminal, and floating screen controls. The central control terminal comprises a core control module and a shared display page. The core control module is used to execute the method described in claim 1. The multiple instruments and devices are connected to the central control terminal via a communication bus, which is used to transmit their respective instrument software interface data to the central control terminal. The core control module is also used to instantiate and manage the software interfaces of each instrument, load the software interface of the currently active instrument in the shared display page, and when the user operates the floating screen control to trigger a switching command, unload the current instrument software interface instance and load the target instrument software interface instance according to the switching command, while updating the display content of the dynamic identification area of ​​the floating screen control. The floating screen control, as an independent interaction layer of the central control terminal, communicates with the core control module through an internal message mechanism. The display layer corresponding to the floating screen control is located above the display layer corresponding to the instrument software interface. The floating screen control includes a dynamic identification area, which is used to display target identification information of the software interface of other instruments. The target identification information displayed in the dynamic identification area is dynamically determined based on the switching record.

14. An electronic device, characterized in that, include: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the instructions to implement the display method of the instrument software interface as described in any one of claims 1 to 9.

15. A computer-readable storage medium, characterized in that, When the instructions in the computer-readable storage medium are executed by the processor of the electronic device, the electronic device is able to perform the display method of the instrument software interface as described in any one of claims 1 to 9.

Images