Method and system for generating digital asset based on user behavior
Patent Information
- Application Number
- TW114113419
- Authority / Receiving Office
- TW · TW
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-04-09
- Publication Date
- 2026-10-16
- Estimated Expiration
- 2045-04-08
AI Technical Summary
Current methods for understanding physician operational behaviors in Healthcare Information Systems (HIS) rely on manual interviews, which are time-consuming, lack data support, and often result in inaccurate requirements descriptions, failing to comprehensively cover operational behaviors and raising concerns about medical data privacy.
A method and system that collects user behavior data through an agent module, records it in a database, and generates digital assets like system specifications and test scripts based on user interface flows, reducing reliance on manual interviews and ensuring data privacy.
This approach automates the digital asset generation process, improving efficiency and accuracy while ensuring data privacy, by establishing user interface flows and generating comprehensive digital assets from user behavior data.
Smart Images

Figure TWG2TA001080188_001 
Figure TWG2TA001080188_002 
Figure TWG2TA001080188_003
Abstract
Description
Technical Field
[0001] This disclosure relates to a method and system for generating digital assets based on user behavior. Prior Technology
[0002] In the development of modern Healthcare Information Systems (HIS), understanding physicians' operational behaviors and needs is crucial. Current methods for understanding the various functions and usage patterns of HIS primarily rely on manual interviews and discussions, requiring significant time and manpower. Furthermore, the results are often recorded in natural language, lacking data support and prone to inaccurate requirements descriptions. These processes typically fail to reflect actual physician operating patterns, potentially leading to a system that does not meet real-world needs. Moreover, existing methods are often limited to specific application scenarios, failing to comprehensively cover physicians' operational behaviors and raising concerns about medical data privacy during data collection. These limitations render the requirements gathering process for HIS inefficient and inaccurate. Summary of the Invention
[0003] This disclosure provides a method for generating digital assets based on user behavior. This method includes the following steps: Collecting user behavior data of an information system through an agent module deployed on the user's device; Recording the user behavior data into a database; Establishing a user interface (UI) flow based on the user behavior data in the database; Generating digital assets of the information system based on the user interface flow.
[0004] This disclosure provides a digital asset generation system based on user behavior, including a storage device and one or more processors. The storage device records multiple instructions. The processors are coupled to the storage device and configured to execute the aforementioned instructions to perform the following operations: Collecting user behavior data of an information system through an agent module deployed on a user terminal device; Recording the user behavior data to a database; Establishing a user interface flow based on the user behavior data in the database; Generating digital assets of the information system based on the user interface flow.
[0005] Based on the above, in this disclosed embodiment, the agent module deployed on the user's terminal device can collect user behavior data on the user's operation of the information system. Subsequently, the user interface flow of the information system can be established based on the user behavior data, and digital assets of the information system, such as system specifications, test items, or test scripts, can be generated based on the user interface flow. This reduces reliance on manual interviews and automates the digital asset generation process, thereby improving efficiency and accuracy. Simple Explanation of the Diagram
[0006] Figure 1 is a schematic diagram of a digital asset generation system based on user behavior according to an embodiment of the present disclosure. Figure 2 is a block diagram illustrating a client device and a server device according to an embodiment of the present disclosure. Figure 3 is a flowchart illustrating a digital asset generation method based on user behavior according to an embodiment of this disclosure. Figure 4 is a schematic diagram illustrating the selection of keyframes according to an embodiment of the present disclosure. Figure 5 is a schematic diagram illustrating a digital asset generation method according to an embodiment of the present disclosure. Figure 6 is a schematic diagram illustrating a user interface flow according to an embodiment of the present disclosure. Figure 7 is a flowchart illustrating a method for generating digital assets based on user behavior according to an embodiment of this disclosure. Implementation
[0007] Some embodiments disclosed herein will be described in detail below with reference to the accompanying drawings. Component symbols used in the following description are considered identical or similar when appearing in different drawings. These embodiments are only a part of this disclosure and do not reveal all possible implementations of this disclosure. More precisely, these embodiments are merely examples of the systems and methods within the scope of this patent application.
[0008] Referring to Figure 1, in this disclosed embodiment, the digital asset generation method system 100 based on user behavior may include at least one user terminal device 110_1~110_N, a storage server 120, and an analysis server 130.
[0009] User-end devices 110_1 to 110_N may be, for example, smartphones, laptops, tablets, desktop computers, or various personal computing devices, etc., and this disclosure is not limited thereto. The number of user-end devices 110_1 to 110_N may be one or more, and this disclosure is not limited thereto. User-end devices 110_1 to 110_N provide an interface for users to interact with the information system, allowing users to access the functions and data of the information system. In some embodiments, user-end devices 110_1 to 110_N may collect user behavior data of the information system.
[0010] User devices 110_1 to 110_N can be connected to storage server 120 via a wired or wireless transmission interface. In different embodiments, user devices 110_1 to 110_N can be connected to storage server 120 via a network. The network can include any of a variety of wireless and / or wired networks. For example, the network can include any combination of public and / or private networks, local area networks, and / or wide area networks.
[0011] Storage server 120 can collect, store, and manage user behavior data. In some embodiments, storage server 120 may also be implemented by one or more electronic devices with storage capabilities, such as network-attached storage (NAS), storage area network (SAN), or cloud storage services (such as AWS S3, Google Cloud Storage, etc.).
[0012] Storage server 120 can be connected to analytics server 130 via a wired or wireless transmission interface. In different embodiments, storage server 120 can be connected to analytics server 130 via a network. The network can include any of a variety of wireless and / or wired networks. For example, the network can include any combination of public and / or private networks, local area networks, and / or wide area networks.
[0013] The analytics server 130 can analyze user behavior data to generate digital assets for the information system, such as UI flows, system specifications, test items, and test scripts. In some embodiments, the analytics server 130 may also be implemented by one or more electronic devices with computing capabilities. In some embodiments, the storage server 120 and the analytics server 130 may also be implemented by a single, independent server device with both storage and computing capabilities.
[0014] The following description will mainly use user terminal device 110_1 as an example, but the same operation and implementation can also be applied to other user terminal devices 110_2 to 110_N.
[0015] Please refer to Figure 2, which is a block diagram illustrating a client device and a server device according to an embodiment of this disclosure. The client device 110_1 may include an input device 111, a display 112, a storage device 113, a transceiver 114, and a processor 115. The analysis server 130 may include a storage device 133, a transceiver 134, and a processor 135.
[0016] The input device 111 is used to receive user operations, such as a mouse, keyboard, or touch device.
[0017] The display 112 may be, for example, a liquid crystal display (LCD), a light-emitting diode (LED) display, an organic light-emitting diode (OLED) display, or other types of displays; this disclosure is not limited thereto. In the embodiments disclosed herein, the display 112 may display the user interface of the information system. In other words, the display 112 may display multiple operation pages of the information system.
[0018] Storage device 113 can be used to store data and software modules, etc., for access by processor 115. Storage device 133 can be used to store data and software modules, etc., for access by processor 135. Storage devices 113 and 133 can be, for example, any type of fixed or removable random access memory (RAM), read-only memory (ROM), flash memory, hard disk, or a combination thereof.
[0019] Transceiver 114 and transceiver 134 can transmit and receive signals wirelessly or via wired means. The transceivers can also perform operations such as low-noise amplification, impedance matching, mixing, up- or down-frequency conversion, filtering, amplification, and similar functions. User device 110_1 can receive and send data via transceiver 114, and analysis server 130 can receive and send data via transceiver 134, such as sending and receiving data via the Internet.
[0020] Processor 115 is coupled to input device 111, display 112, storage device 113, and transceiver 114. Processor 135 is coupled to storage device 133 and transceiver 134. Processor 115 and processor 135 are, for example, central processing unit (CPU), application processor (AP), or other programmable general-purpose or special-purpose microprocessor, digital signal processor (DSP), image signal processor (ISP), graphics processing unit (GPU), or other similar devices, integrated circuits, and combinations thereof.
[0021] In some embodiments, processors 115 and 135 may access and execute software modules to implement the user behavior-based digital asset generation method in this disclosed embodiment. The aforementioned software modules can be broadly interpreted as instructions, instruction sets, code, program code, program, application, software suite, thread, procedure, function, etc.
[0022] Please refer to Figures 1 and 3 simultaneously. The method of this embodiment is applicable to the above-described digital asset generation method system 100 based on user behavior. The following describes the detailed steps of the digital asset generation method based on user behavior in this embodiment, along with the various components of the digital asset generation method system 100 based on user behavior.
[0023] In step S302, through the proxy module deployed on the user terminal device 110_1, the user terminal device 110_1 can capture multiple operation screen frames of the information system. The proxy module is a software component deployed on the user terminal device 110_1. Specifically, when the user uses the information system, the user terminal device 110_1 can display the operation window of the information system. In some embodiments, the proxy module of the user terminal device 110_1 can capture multiple operation screen frames of the information system at fixed time intervals. Alternatively, in some embodiments, the proxy module of the user terminal device 110_1 can capture multiple operation screen frames of the information system in response to the fulfillment of capture conditions. The aforementioned capture conditions are, for example, a significant change in the window screen or the receipt of user operation events, etc.
[0024] In some embodiments, the information system includes a Hospital Information System (HIS). A Hospital Information System is an information management system specifically designed for healthcare institutions, encompassing functions such as patient management, electronic medical records (EMR), prescription management, and financial settlement.
[0025] In step S304, the proxy module of the user terminal device 110_1 can monitor a user operation event. Specifically, when the input device 111 receives a user operation, the proxy module of the user terminal device 110_1 can monitor a user operation event.
[0026] In some embodiments, user operation events include mouse click events, touch click events, or keyboard input events. For example, when a user clicks a button, form, or menu on the user interface of an information system using a mouse or touchpad, the agent module can detect a click event. When text is entered into an input field, the agent module can detect a keyboard input event. When a user performs click, swipe, or zoom operations on a touchscreen, the agent module can detect touch events.
[0027] In the context of hospital information systems, the agent module of the user terminal device 110_1 can be used to monitor the user operation behavior of medical staff. Examples of such user operation behavior include a doctor clicking the "Patient Inquiry" interface, entering a patient's name, and searching; or a nurse clicking the "Medication Records" button to confirm a patient's prescription record.
[0028] In step S306, the agent module of the user terminal device 110_1 can select a keyframe corresponding to the user operation event from multiple operation screen frames based on the user operation event, so as to obtain user behavior data including the keyframe and the user operation event. Specifically, when the agent module detects a user operation event, such as a mouse click event, a touch click event, or a keyboard input event, the agent module can immediately capture the current operation screen frame and mark it as a keyframe related to the user operation event.
[0029] In some embodiments, the agent module can identify keyframes through an event-driven approach. For example, when a user clicks a button on the operation page of an information system, the agent module can capture and mark the operation screen frame at the moment the click occurs. In addition, if a user enters text in the search field, the agent module can capture and mark the current operation screen frame when the user presses the "Enter" key or clicks the search button.
[0030] Please refer to Figure 4, which is a schematic diagram illustrating the selection of key frames according to an embodiment of this disclosure. The proxy module of the user terminal device 110_1 can capture multiple operation screen frames F41. The proxy module can select key frames according to user operation events to record the screen content corresponding to the user operation events. In this example, the proxy module can select three key frames KF1, KF2, and KF3, each corresponding to three different user operation events.
[0031] As shown in Figure 4, when the agent module detects a click event at coordinates [890, 180], it can select the operation screen frame at the time of the click event as keyframe KF1 to record the specific location of the click and the corresponding UI element on the operation page. When the agent module detects that the user has entered the text "GASLAN" in the search field and pressed Enter to submit, it can select the operation screen frame at the time of pressing Enter as keyframe KF2. When the agent module detects another click event at coordinates [150, 240], it can select the operation screen frame at the time of the click event as keyframe KF3.
[0032] Therefore, through the keyframe selection process, the agent module can associate multiple user operation events with keyframes to form structured user behavior data. In some embodiments, the user behavior data may include information such as operation timestamps, operation types, and the screen content of the keyframes.
[0033] In step S308, the proxy module of client device 110_1 can remove personal data from user behavior data. Specifically, the proxy module of client device 110_1 can identify and remove data fields or elements that may contain personal information through data processing and cleaning mechanisms. For example, the proxy module can analyze whether there is personal data of patients or doctors in the user behavior data. This personal data may include, but is not limited to, the user's name, account number, email address, IP address, and other personally identifiable information. The proxy module of client device 110_1 can remove personal data from user behavior data through data masking or data deletion. For example, the proxy module of client device 110_1 can replace sensitive information with an anonymous marker. Alternatively, the proxy module of client device 110_1 can directly remove data fields containing personal data, such as deleting IP addresses or device identifiers unrelated to the operation event.
[0034] In step S310, the storage server 120 performs data structuring processing on the user behavior data to generate structured data. In step S312, the storage server 120 records the structured data to a database. Specifically, the client device 110_1 can transmit user behavior data to the storage server 120. The storage server 120 converts the raw user behavior data into a structured data format that is easy to retrieve and analyze, thereby improving data usability and analysis efficiency.
[0035] In some embodiments, data structuring includes classifying, organizing, and formatting user behavior data. For example, storage server 120 can decompose each operation event data in the user behavior data into standardized fields, such as "event type," "operation timestamp," "operation location," "operation target," and "keyframe." Furthermore, for screen frame data, storage server 120 can establish a corresponding index with user operation events to ensure efficient retrieval of user operation events and visual data. The structured data will be stored in a database.
[0036] In step S314, the analysis server 130 determines the association between multiple system functions and operation pages in the user interface flow (UI Flow) based on the event times of user operation events in the user behavior data. Specifically, the analysis server 130 can reconstruct the complete UI flow of the user's operation in the information system by analyzing the timestamps and execution order of user operation events in the user behavior data. Specifically, the analysis server 130 can combine user operation events with one or more corresponding keyframes and establish the jump and interaction relationships between operation pages through time sequence analysis of user operation events. In some embodiments, the analysis server 130 can identify the jump relationships between different operation pages by arranging user operation events in chronological order, thereby inferring the relative dependencies of different system functions based on the user's operation actions. For example, if the user frequently jumps from the first operation page to the second operation page of a specific functional module, the analysis server 130 can determine that the functional module and the first operation page have a high degree of association in the UI flow. Specifically, the first operation page may be the main entry point to the functional module. Alternatively, users may habitually navigate from the first operation page to the second operation page, indicating a logical continuity between the two pages in user behavior. Or, the second operation page might be a major extension of the first operation page's functionality.
[0037] In some embodiments, the analysis server 130 can identify candidate UI elements by analyzing rectangular outlines in keyframes and locate target UI elements based on the coordinates of user action events. The coordinates of the user action events may be approximately located within the central area of the target UI element. In some embodiments, the analysis server 130 can analyze displayed text or icons in the target UI element and subsequent operation pages to identify a specific system function of the information system. In some embodiments, the analysis server 130 can analyze rectangular outlines in keyframes to identify the view extent of a window and identify the window title to determine the system function to which the operation page belongs.
[0038] For example, when a user clicks a button, the user behavior data records the event time and coordinates of the click. The analysis server 130 can combine this with subsequent screen changes (such as page jumps or window updates) to determine the logical relationship between the click operation and subsequent operation pages. The establishment of these operation pages and their associations forms a clear user interface flow, describing the user's operation path within the information system. Based on this, the user interface flow of the hospital information system can be established according to the usage behavior of doctors operating the hospital information system.
[0039] In step S316, the analysis server 130 generates the system specifications of the information system based on the user interface logic flow. Specifically, the analysis server 130 analyzes the logical relationships between operation pages in the user interface flow and transforms these relationships into structured content for the specifications, accurately describing the system functions and interactive behaviors of the information system. By automatically generating the specifications based on the UI Flow, the system specifications can comprehensively and accurately reflect actual user behavior, reducing errors and biases in manual drafting and significantly improving the efficiency and accuracy of requirements analysis.
[0040] In step S318, the analysis server 130 generates test cases and test scripts for the information system based on the user interface logic flow. A test case is a test unit designed for a specific function or operation process of the information system, including test objectives, input conditions, execution steps, and expected results. A test script is an executable program or instruction set of an automated testing tool that automatically executes the test according to the steps of the test case and records the test results. More specifically, the reconstructed user interface flow can be further applied to the generation of test cases and test scripts. For example, the analysis server 130 can automatically generate test cases covering the complete operation process and ensure that the test scripts accurately simulate the user's actual behavior, thereby improving the comprehensiveness and efficiency of the test.
[0041] Please refer to Figure 5, which is a schematic diagram illustrating a digital asset generation method according to an embodiment of this disclosure. Agent modules 511-513 can be deployed on multiple user terminal devices. Agent modules 511-513 collect user behavior data from different user terminal devices and transmit it to data storage module 520. Data storage module 520 receives user behavior data from agent modules 511-513, performs data cleaning and structuring processing, and finally stores the structured data in database DB51. Analysis module 530 analyzes user behavior data to generate a user interface flow (UI Flow), and generates system specification SS1, test item TC1, and test script TS1 based on the UI Flow.
[0042] Please refer to Figure 6, which is a schematic diagram of a user interface flow according to an embodiment of this disclosure. The user interface flow may include multiple UI pages P61-P63 of the information system. Each UI page P61-P63 may include one or more UI elements.
[0043] UI page P61 is the starting point of the operation process. UI page P61 contains an "Add" button B61. When the user clicks this button B61, the page will redirect to UI page P62. On UI page P62, the user can enter a query in the search box B64, such as "GASLAN", and view the search results in the query results table L61.
[0044] Next, users can navigate from UI page P62 to UI page P63 as needed. When a user clicks on an item in the query results table L61, the page will redirect to UI page P63. UI page P63 provides a "Rate Unit" dropdown menu B63 for selecting the relevant unit setting. UI page P63 also includes a "Confirm" button B62. After the user completes the settings and clicks the "Confirm" button B62, the system will submit the settings and execute the relevant functions. This operation marks the end of the process and may redirect back to UI page P61.
[0045] The logical transitions between UI pages P61-P31 are driven by user interaction events (such as button clicks and text input), which are reflected in the UI Flow. This flow not only demonstrates the sequence of user actions but also reveals the interaction logic between each UI page (P61-P31) and its internal UI elements, thus constructing a complete user operation path. The generation of this user interface flow can not only accurately describe the system's functional requirements but also provide a basis for generating test cases and test scripts.
[0046] Please refer to Figure 7, which is a flowchart illustrating a method for generating digital assets based on user behavior according to an embodiment of this disclosure. In step S710, user behavior data of the information system is collected through an agent module deployed on the user's terminal device. In step S720, the user behavior data is recorded to a database. In step S730, a user interface flow is established based on the user behavior data in the database. In step S740, digital assets of the information system are generated based on the user interface flow. However, since each step in Figure 7 has been described in detail above, it will not be repeated here. Furthermore, the method in Figure 7 can be used in conjunction with the above exemplary embodiments or used independently; this disclosure does not impose any limitations.
[0047] In summary, in this disclosed embodiment, the agent module deployed on the user's terminal device can collect user behavior data on the operation of the information system. Subsequently, the user interface flow of the information system can be established based on the user behavior data, and digital assets of the information system, such as system specifications, test items, or test scripts, can be generated based on the user interface flow. This reduces reliance on human interviews and automates the digital asset generation process, thereby improving efficiency and accuracy. Furthermore, the removal of personal data ensures the security of personal privacy.
[0048] Although this disclosure has been disclosed above with reference to embodiments, it is not intended to limit this disclosure. Anyone skilled in the art may make some modifications and refinements without departing from the spirit and scope of this disclosure. Therefore, the scope of protection of this disclosure shall be determined by the appended claims and their equivalents.
[0049] 100: Digital Asset Generation Methodology System 110_1~110_N: User terminal device 111: Input device 112: Monitor 113, 133: Storage devices 114, 134: Transceiver 115, 135: Processors 120: Storage Server 130: Analysis Server 511~513: Proxy Module 520: Data Storage Module 530: Analysis Module B61, B62: Buttons B63: Drop-down menu B64: Search Box DB51: Database F41: Operation Screen Frame KF1, KF2, KF3: Keyframes L61: Query Results Table Pages 61, 62, and 63: UI Pages S302~S318, S710~S740: Steps SS1: System Specification TC1: Test Items TS1: Test Script
Claims
1. A method for generating digital assets based on user behavior, comprising: Collect user behavior data of an information system through a proxy module deployed on a user terminal device; Remove personal data from the user behavior data; Record the user behavior data to a database; establish a user interface (UI) flow based on the user behavior data in the database; And, based on the user interface flow, generate the digital assets of the information system.
2. The method for generating digital assets based on user behavior as described in claim 1, wherein the step of collecting the user behavior data of the information system through an agent module deployed on the user terminal device includes: Multiple operation screen frames of the information system are captured through a proxy module deployed on the user terminal device; Monitor user action events; Based on the user operation event, a key frame corresponding to the user operation event is selected from multiple operation screen frames to obtain the user behavior data including the key frame and the user operation event.
3. The digital asset generation method based on user behavior as described in claim 2, wherein the user operation events include mouse click events, touch click events, or keyboard input events.
4. The method for generating digital assets based on user behavior as described in claim 2, wherein the step of establishing the user interface process based on the user behavior data in the database includes: Based on the event time of the user operation event in the user behavior data, the association between multiple system functions in the user interface process is determined.
5. The method for generating digital assets based on user behavior as described in claim 1, wherein the step of recording the user behavior data into the database includes: The user behavior data is processed to generate structured data; And record the structured data into the database.
6. The method for generating digital assets based on user behavior as described in claim 1, wherein the step of generating digital assets of the information system according to the user interface process includes: The system specifications of the information system are generated based on the user interface flow.
7. The method for generating digital assets based on user behavior as described in claim 1, wherein the step of generating digital assets of the information system according to the user interface process includes: The test items and test scripts for the information system are generated based on the user interface flow.
8. The method for generating digital assets based on user behavior as described in claim 1, wherein the information system includes a Hospital Information System (HIS).
9. A medical data retrieval system, comprising: Storage device that records multiple instructions; and a processor, connected to the storage device, configured to execute the instructions to: collect user behavior data of an information system through an agent module deployed on a user terminal device; and remove personal data from the user behavior data; Record the user behavior data to a database; establish a user interface flow based on the user behavior data in the database; And, based on the user interface flow, generate the digital assets of the information system.
