Work order generation method and device based on functional componentization, equipment and medium

Abstract

The invention relates to the technical field of computers, and discloses a work order generation method and device based on function modularization, equipment and a medium, service demand information of a client is obtained through a work order creation request initiated by the client, and the communication time and labor cost of demand confirmation are reduced. The service work order type is determined according to the service demand information, the existing work order type can be quickly identified, repeated development is avoided, and the work order generation efficiency is improved. By querying and calling the existing components in the component library, service functions are modularized, component reuse is realized, redundant work of repeated development and test is avoided, professional requirements of developers are reduced, and work order generation is more flexible and efficient. Through combination of the target component and the work order content, the target work order is generated, rapid generation of the work order is realized, a service demand can be rapidly responded, and work order generation efficiency and flexibility in a medical care service business scene are improved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a work order generation method, device, equipment and medium based on functional componentization. Background Art

[0002] With the development of internet technology, medical institutions, such as internet hospitals, family doctors at physical examination institutions, and family doctors at nursing homes, have launched online doctor service platforms to provide better and more convenient medical services. Doctors can provide services to patients online through doctor work orders. In the healthcare and elderly care scenarios, diverse doctor work orders are particularly important for providing online services to clients and recording relevant information about home-based elderly care services.

[0003] In healthcare and elderly care scenarios, medical services are complex, and the content of different work orders is highly similar yet unique, resulting in a wide variety of doctor work orders. Due to differences in medical service processes and processing methods, each medical service requires one or more corresponding doctor work orders.

[0004] Currently, doctor work orders are typically created and generated by adding new work order types. This requires R&D and testing personnel to develop and test the work order before releasing it to the public. This existing work order generation method places high demands on the developer's expertise, and after each work order type is created, the development and testing process must be repeated. As the number of work order types increases, the development, testing, and release cycles of work orders lengthen, making business functionality maintenance difficult and leading to low work order generation efficiency. Summary of the Invention

[0005] The present invention provides a work order generation method, device, computer equipment and medium based on functional componentization to solve the technical problem of low work order generation efficiency.

[0006] In a first aspect, a work order generation method based on functional componentization is provided, comprising:

[0007] Based on the work order creation request initiated by the client, obtain the business requirement information of the target work order;

[0008] Determine the type of business work order based on the business demand information;

[0009] Searching a preset component library for at least one target component that matches the business work order type;

[0010] A target work order is generated based on the work order content sent by the client and each of the target components.

[0011] In a second aspect, a work order generation device based on functional componentization is provided, comprising:

[0012] The business requirement information acquisition module is used to obtain the business requirement information of the target work order based on the work order creation request initiated by the client;

[0013] A business work order type determination module, configured to determine a business work order type based on the business demand information;

[0014] A target component matching module, configured to search a preset component library for at least one target component that matches the business work order type;

[0015] The work order generation module is used to generate a target work order based on the work order content sent by the client and each target component.

[0016] In a third aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of the above-mentioned work order generation method based on functional componentization are implemented.

[0017] In a fourth aspect, a computer-readable storage medium is provided, which stores a computer program. When the computer program is executed by a processor, the steps of the above-mentioned work order generation method based on functional componentization are implemented.

[0018] In the solution implemented by the above-mentioned work order generation method, device, computer equipment and storage medium based on functional componentization, the client's business demand information is obtained through the work order creation request initiated by the client, which reduces the communication time and labor cost of demand confirmation and ensures the accuracy and timeliness of business demand information. By determining the business work order type based on the business demand information, the existing work order type can be quickly identified, duplicate development can be avoided, and the efficiency of work order generation can be improved. By querying and calling existing components in the component library, business functions are componentized and components can be reused, which avoids the redundant work of repeated development and testing, reduces the professional requirements of developers, and makes work order generation more flexible and efficient. By combining the target component and the work order content, the target work order is generated, and the rapid generation of the work order is achieved, which reduces manual intervention, can quickly respond to business needs, and improves the efficiency and flexibility of work order generation. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments of the present invention. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0020] Figure 1This is a schematic diagram of an application environment of a work order generation method based on functional componentization in one embodiment of the present invention;

[0021] Figure 2 A flowchart of a first embodiment of a method for generating a work order based on functional components provided by an embodiment of the present invention;

[0022] Figure 3 A schematic diagram of the data interaction process for creating a doctor's work order according to an embodiment of the present invention;

[0023] Figure 4 A flow chart of the process for operators to configure doctor work orders for this application;

[0024] Figure 5 A flowchart of a second embodiment of a method for generating a work order based on functional components provided by an embodiment of the present invention;

[0025] Figure 6 This is a structural diagram of a work order generation device based on functional componentization in one embodiment of the present invention;

[0026] Figure 7 is a structural diagram of a computer device in one embodiment of the present invention;

[0027] Figure 8 FIG. 2 is another structural diagram of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0028] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0029] The work order generation method based on functional componentization provided by the embodiment of the present invention can be applied in Figure 1In an application environment, the client communicates with the server through a network. In the present invention, in order to address the technical problem of low efficiency in generating doctor work orders in medical, health and elderly care service scenarios, the client's business demand information can be obtained through a work order creation request initiated by the client, which reduces the communication time and labor cost of demand confirmation and ensures the accuracy and timeliness of business demand information. By determining the business work order type based on the business demand information, the existing work order type can be quickly identified, avoiding repeated development and improving the efficiency of work order generation. By querying and calling existing components in the component library, business functions are componentized and components are reused, avoiding redundant work of repeated development and testing, reducing the professional requirements of developers, and making work order generation more flexible and efficient. The standardized design of the component library also ensures the consistency and stability of work orders, reducing errors and maintenance costs caused by inconsistent codes. By combining the target component and the work order content, the target work order is generated, and the rapid generation of the work order is achieved, which reduces manual intervention, can quickly respond to business needs, and improves the efficiency and flexibility of work order generation. Among them, the client can be, but is not limited to, various personal computers, laptops, smart phones, tablets and portable wearable devices. The server side can be implemented by an independent server or a server cluster composed of multiple servers. The present invention will be described in detail below through specific embodiments.

[0030] See also Figure 2 As shown, Figure 2 The flowchart of the first embodiment of the work order generation method based on functional componentization provided by the embodiment of the present invention includes the following steps:

[0031] S101: Based on the work order creation request initiated by the client, obtain the business requirement information of the target work order;

[0032] In one embodiment, in a medical service process, a user (such as a doctor, an operation staff, etc.) initiates a work order creation request to a server through a client (such as a doctor platform).

[0033] The work order creation request can include the business requirement information of the target work order, such as the work order type (such as a physical examination report interpretation work order), patient information (such as patient ID, name, and contact information), service content (such as physical examination report interpretation and medication recommendations), work order priority (such as high, medium, and low), and other relevant business requirement information.

[0034] For example, a user enters the customer work order module on the doctor platform, clicks the "Create Work Order" button, fills out a form containing business requirement information such as the work order type, patient information, service content, and work order priority, and submits the request. After receiving this request, the server parses the request data and extracts the business requirement information. Based on the business requirement information, a doctor's work order is created for the patient and the service is provided to the patient. For example, a physical examination report interpretation work order has the business function of viewing the physical examination report uploaded by the customer, and also has the function of pushing the medical order report to the customer after the work order service is completed. Based on the doctor's service content, the doctor administrator provides feedback to the operation staff to upgrade the work order.

[0035] For example, Figure 3 In the data interaction flow diagram for creating a doctor's work order, in the home-based nursing care doctor steward scenario, doctors can create, edit, and submit work orders directly on the doctor platform to provide services to patients. The doctor enters the customer work order module of the doctor platform and sends a creation request. The front-end service requests the back-end service to create the work order, and the back-end service returns a successful creation. The doctor edits the work order, and the front-end service queries the configured business function components and state flow components. The front-end service renders the work order content, and the doctor fills in and submits the work order. The back-end service saves the work order content, triggers the state machine to update the state, and executes the corresponding logic. Through component-based design and state machine management, flexible configuration and rapid online deployment of doctor work orders are achieved, significantly reducing development costs and improving doctor service efficiency and business operations capabilities.

[0036] S102: Determine the type of the business work order based on the business demand information;

[0037] In one embodiment, the server can maintain a predefined work order type library, which contains all possible work order types and their corresponding business requirement characteristics. Each work order type has a unique identifier and description information.

[0038] When a user (such as a doctor or operations staff) submits a work order creation request through the client, the server first receives and parses the request. During the parsing process, the server extracts the business requirement information from the request, which may include the work order type name, patient details, required service content, work order priority, and other relevant business parameters.

[0039] Typically, the server can perform integrity verification on this data, ensuring that all required fields are filled in and that the format is correct. For example, it can verify that the patient ID conforms to the required format and that the phone number is valid. If the data is incomplete or contains errors, the server will return a detailed error message to the user, guiding them to correct the request.

[0040] After data validation, the service can compare the business requirement information in the request with the characteristics in the work order type library to find the most suitable business work order type. The matching and identification of business work order types can be achieved through keyword matching, rule engine application, or complex algorithm calculation.

[0041] Furthermore, based on a data preprocessing algorithm, feature recognition is performed on the business demand information to obtain key information; based on a feature matching algorithm, feature matching is performed on the key information and a predefined work order type library to determine the business work order type.

[0042] In one embodiment, the server can pre-process the business requirement information submitted by the user using a data pre-processing algorithm, including text cleaning, standardization, and feature extraction. Text cleaning removes irrelevant characters and extra spaces, standardization converts the text to a uniform format (e.g., all lowercase), and feature extraction identifies key information, such as the work order type, service content keywords, and patient information.

[0043] After extracting key information from the business requirement information, the server can use a feature matching algorithm to match the extracted key information with a predefined ticket type library to determine the most appropriate ticket type. This matching algorithm can include one or more of direct matching of ticket type names, keyword matching of service content, and a comprehensive evaluation of business requirement characteristics.

[0044] For example, if the request explicitly specifies "Physical Examination Report Interpretation Work Order," the server can directly search for the record corresponding to that name in the work order type library. If the request does not explicitly specify the business work order type, the server can perform a fuzzy match based on other business requirement information (such as service content, patient information, etc.). Fuzzy matching can be based on keyword similarity, business logic relevance, or reference to historical matching records.

[0045] In one embodiment, in order to improve the accuracy of matching, the server may adopt a multi-level matching strategy.

[0046] First, an accurate match can be performed based on the clear business work order type name; if no match is found, a secondary match is performed based on the service content and patient information; finally, a comprehensive evaluation is performed based on the work order priority and other parameters.

[0047] During the matching process, the server can also evaluate the matching results to select the best match. For example, if the business requirement information in the request partially matches multiple business ticket types, the server will select the most appropriate business ticket type based on the matching score. If there is no match, the server can record the result and trigger a default business ticket type or issue an alert to operations personnel for manual intervention and confirmation.

[0048] After determining the most matching business work order type, the server records the information of the business work order type (including unique identifier and description, etc.) in the work order creation log and passes it to subsequent processing modules, such as the component query module.

[0049] S103: Searching a preset component library for at least one target component that matches the business work order type;

[0050] In one embodiment, after determining the type of work order, the server searches a pre-defined component library for components that match the target work order type. The component library contains multiple functional components, each corresponding to a specific business function, such as report parsing, medical order generation, medication recommendations, data visualization, and intelligent diagnostic assistance.

[0051] Each component in the component library can be configured with a unique identifier for quick location and calling, and comes with detailed description information and configuration parameters to help the server understand the function and usage of the component.

[0052] For example, when searching for components, the server first extracts key features of the target work order type, such as the work order type name, service content, and priority. The server then compares these features with components in the component library. This matching can be done through keyword matching or through a complex rules engine to evaluate the compatibility of components with the work order requirements. For example, for a "physical examination report interpretation work order," the server can search for components that support report parsing and medical order generation.

[0053] To ensure accurate matching, the server can employ a multi-dimensional matching strategy. Beyond basic functional matching, it can also consider factors such as component performance, resource consumption, and compatibility. For example, for high-priority work orders, the server can prioritize components with better performance and faster response times.

[0054] Generally, many complex work order requirements cannot be met by a single component and require the coordinated work of multiple target components. Therefore, the server can dynamically combine multiple target components based on the requirements of the work order type to form a complete processing flow. For example, a "physical examination report interpretation work order" must first call the "report parsing component" to process the medical examination report uploaded by the patient, and then call the "order generation component" to create the medical order report.

[0055] Furthermore, based on the business work order type, functional requirement information corresponding to at least one business function and status information corresponding to at least one work order status are determined; based on the functional requirement information, at least one business function component is determined; based on the status information, at least one work order status component is determined.

[0056] In the medical business process, after determining the business work order type, the server can further refine the business function and status management of the work order.

[0057] Business function components are modules that implement specific business functions, such as parsing physical examination reports, generating medical order reports, etc. Each business function component can be configured with data such as function description, scope of application, and configuration parameters based on the corresponding business requirements.

[0058] The work order status component is a module used to manage the work order life cycle. It is responsible for tracking the status changes of work orders, such as from "Created" to "Processing", and then to "Completed" or "Closed", to ensure the transparency and controllability of the work order processing process.

[0059] In one embodiment, the server can extract information such as the work order type name, service content keywords, and business requirement characteristics based on the business requirement type as functional requirement information. For example, for a "physical examination report interpretation work order," the server can extract functional requirements containing keywords such as "report parsing" and "medical order generation."

[0060] Generally, components in a component library can be divided into business function components and work order status components, with functional component sub-libraries and state component sub-libraries constructed separately. A functional component sub-library can contain multiple business function components, each corresponding to a specific business function; a state component sub-library can contain multiple work order status components, each corresponding to specific state management and transition logic.

[0061] Based on the functional requirement information, the server searches for matching business functional components from the functional component sub-library. The server finds the most suitable business functional component by comparing the functional requirement name, component description, and configuration parameters. For example, for the "report parsing function," the server can search for business functional components that support report parsing and further filter them based on their configuration parameters (such as supported file formats and parsing depth).

[0062] Similarly, to determine status information, the server can extract information such as the work order type name and status description based on the business requirement type. For example, for a "physical examination report interpretation work order," the server can extract information including statuses such as "created," "processing," and "completed." The server then searches for matching work order status components from a predefined status component library.

[0063] Based on the status information, the server searches the status component sub-library for matching ticket status components. The server compares the status name, component description, and transition logic to find the most appropriate ticket status component. For example, for the "Created" status, the server searches for components that support state transitions and further filters them based on the component's transition logic (such as the trigger condition for switching from "Created" to "Processing").

[0064] In one embodiment, by componentizing business functions and work order status, the professional ability requirements for work order generation are reduced, and front-end operators can call components in the component library to configure and generate work orders according to business needs. Figure 4 As shown, users (such as operators and doctors) log in to the operations system or doctor platform through the client. Using the work order management module, they configure the work order type, select the business function component, and the work order status process. If work order status events need to be configured, they directly select the configuration and then generate a new work order. If not, a new work order is generated directly based on the selected business function component and work order status component configuration. This reduces the professional skills required for work order generation and improves work order generation efficiency.

[0065] In this embodiment, the server determines the functional requirement information and status information based on the business work order type, and queries the matching business function components and work order status components, which not only ensures the efficiency and accuracy of work order processing, but also provides a solid foundation for subsequent work order execution and status management.

[0066] In one embodiment, after determining the target component, the server can configure the target component's operating parameters based on the business requirements information provided by the client and the actual needs of work order creation. For example, for the "report parsing component," parameters such as supported file formats and parsing depth can be set; for the "medical order generation component," parameters such as the medical order template and push method can be set.

[0067] Generally, during the query and combination process of the target components, log information can be recorded, including the query time, matched components, combination method, etc., to facilitate subsequent auditing and troubleshooting, as well as optimization of the component library and matching algorithm.

[0068] The server passes the matched components and their configuration information to subsequent processing modules, such as the work order processing module. Based on this information and the component configuration information, the work order processing module can call the components in sequence and execute specific business logic to complete the subsequent processing of the work order.

[0069] S104: Generate a target work order based on the work order content sent by the client and each target component.

[0070] In one embodiment, the server receives the work order content sent by the client, including the work order type, patient information, service content, priority, etc. The work order content is used as the basic data for the target work order and stored in the work order record. For example, if the work order type is "Physical Examination Report Interpretation Work Order," the server will record the patient's ID, name, contact information, and the upload path or content of the physical examination report.

[0071] The server dynamically combines target components based on their functionality and configuration parameters to generate targeted work orders to meet the business needs of the work order. For example, for a "physical examination report interpretation work order," the server can call the "report parsing component" to process the patient's uploaded physical examination report and the "medical order generation component" to create the medical order report. When calling components, the server can set operational parameters for the work order processing process, such as report format, parsing depth, and medical order templates.

[0072] During the ticket processing process, the server can set up a user feedback mechanism to promptly notify users of the progress of the ticket. For example, when the ticket status changes, the server sends a notification to the doctor or patient to inform them of the current processing progress. Notifications can be sent through the doctor platform's message center, email, or SMS push.

[0073] Additionally, doctors or administrators can submit escalation requests on the client based on the progress of the work order. Upon receiving the escalation request, the server updates the work order's priority and re-matches components to ensure that high-priority work orders receive sufficient resources. The server also sends a notification to operations staff or other relevant personnel, informing them of the escalation so they can take appropriate action.

[0074] After the work order is processed, the server can generate the final processing results and store them in the database. For example, for a "physical examination report interpretation work order", the server can store the parsed physical examination report data and the generated medical order report so that users can view detailed processing information.

[0075] In one embodiment, when the client initiates an event configuration request for the work order status component, based on the event selection instruction of the client, a work order status event corresponding to at least one of the status components is determined; based on the event dimension information of the work order status event, the status component is configured and updated so that the status component triggers the corresponding work order status event when the state changes.

[0076] In one embodiment, after configuring the target component for creating a target work order, the user can initiate an event configuration request for the state component within the target work order through the client. Based on the client's event selection instructions, the server determines the work order state event corresponding to at least one state component and integrates the dimensions of the selected work order state event into the work order state component.

[0077] Exemplarily, the event configuration request may include request information such as the configured work order type, status component identifier, and event selection instruction.

[0078] Furthermore, based on historical work order data, at least one work order status is obtained; based on the status value of each work order status, at least one event code is composed, and at least one work order status event is generated.

[0079] In one embodiment, event codes in the work order process can be pre-defined, and the event codes can be stored in tables, databases, etc. to generate an event code list, such as: pending service_cancelled, pending service_completed, etc. event codes, so that users can directly select the corresponding event code without the need for developers to temporarily participate in editing.

[0080] Specifically, organize all the states that have appeared in historical work orders, configure their dimension information into the state component, and define work order status events. The current state value and the next state value form an event code, which corresponds to different work order status events, and configure the processing logic of each work order status event. For example: If the current state is pending service, when the next state is canceled, send an email to the doctor administrator and operation staff so that the operation staff can pay attention to the work order change information in a timely manner. If the current state is pending service, when the next state is completed, you can send a service account message to the user to view the relevant information of the doctor's medical order report.

[0081] In one embodiment, the server determines the status components that need to be configured and the corresponding work order status events by parsing the event selection instruction initiated by the client.

[0082] First, the server validates the event selection instruction to determine whether the event code selected by the user complies with predefined state transition rules. If the event code is invalid, an error message is returned to the client, prompting the user to reselect the event code or cancel the selection. Once the server verifies the validity of the event code selected by the user, it configures the corresponding processing logic for each ticket state event selected by the event selection instruction, such as sending a notification or updating data.

[0083] Secondly, the server needs to define the dimensional information of each work order status event, including the event code, triggering conditions, and processing logic. The determined dimensional information of the work order status event is integrated into the state component, and the state component configuration is updated to ensure that the state component can trigger the corresponding event when the state changes.

[0084] After completing the event configuration for the status component, when a ticket status changes, the status component generates an event code based on the configured event dimension information and sends this code to the event processing system. The event processing system then searches for the corresponding processing logic based on the event code and executes it, such as sending a notification or updating data. After event processing is complete, the status component sends a feedback notification to the client, confirming the successful event configuration. This feedback notification can include information such as the event code, processing result, and processing time.

[0085] The relationship between ticket status events and status components is interdependent. Status events trigger status changes in status components, while status components execute status events. By linking event triggering, event processing, status updates, and feedback notifications, flexible management and flow of ticket status can be achieved, ensuring timely response and processing of ticket status changes.

[0086] For example, suppose that during the execution of the work order process, the work order status changes, such as from "pending service" to "cancelled". The status component detects the status change and generates the event code "pending service_cancelled". Based on the event code "pending service_cancelled", the event processing system executes the logic of sending an email notification, and the email notification is sent to the doctor administrator and operations staff. At this time, the status component updates the work order status to "cancelled" and records the historical information of the status change, such as the time of change and the reason for the change. The status component sends a confirmation notification of the status change to the doctor and operations staff, completing the feedback notification.

[0087] In this embodiment, the client can initiate an event configuration request for the work order status component. The server determines the corresponding work order status event based on the event selection instruction and integrates the event dimension into the status component. This ensures that corresponding events can be flexibly triggered when the work order status changes, ensuring the diversity and flexibility of work order configuration. Furthermore, through the configuration and management of event dimensions, refined control over the flow of work order status can be achieved.

[0088] As can be seen, in the above solution, the client's business requirement information is obtained through the work order creation request initiated by the client, reducing the communication time and labor costs for requirement confirmation and ensuring the accuracy and timeliness of business requirement information. By determining the business work order type based on business requirement information, existing work order types can be quickly identified, avoiding duplicate development and improving the efficiency of work order generation. By querying and calling existing components in the component library, business functions are componentized and components can be reused, avoiding redundant work such as duplicate development and testing, reducing the professional requirements of developers, and making work order generation more flexible and efficient. The standardized design of the component library also ensures the consistency and stability of work orders, reducing errors and maintenance costs caused by inconsistent code. By combining the target component and work order content, the target work order is generated, achieving rapid work order generation, reducing manual intervention, and enabling rapid response to business needs, thereby improving the efficiency and flexibility of work order generation.

[0089] See also Figure 5 As shown, Figure 5 A flowchart of a second embodiment of a work order generation method based on functional componentization provided in an embodiment of the present invention.

[0090] like Figure 5 As shown, based on the above Figure 2 In the embodiment shown, before step S103, the following steps are further included:

[0091] S201: Identify at least one work order business function and at least one work order status based on historical work order data;

[0092] In one embodiment, sources of historical work order data may include databases, log files, user feedback, and other business systems.

[0093] The database can store detailed information on all processed work orders, including work order type, patient information, service content, work order status, processing time, etc. Developers can extract relevant work order records from the database through data extraction scripts or using data query tools.

[0094] Log files are generated during ticket processing, recording detailed events such as ticket creation, processing, and status changes. Developers can parse log files to extract key information about ticket processing. Log files are typically stored in text format, and regular expressions or log parsing tools can be used to extract structured data. For example, information such as ticket ID, processing time, and processing results can be extracted.

[0095] During the work order processing process, you can collect user feedback data through user feedback forms or questionnaires, such as satisfaction with the work order processing, problems encountered, etc.

[0096] After acquiring historical work order data, it needs to be preprocessed, including data cleaning, standardization, and annotation. Data cleaning is used to remove duplicate, erroneous, or incomplete records to ensure data quality. Standardization converts the data into a unified format and encoding for subsequent analysis. Annotation categorizes and tags the data based on business needs, such as by marking the business function and status of the work order.

[0097] The server analyzes historical work order data to identify common work order business functions and work order statuses. For example, by counting and categorizing historical work orders, the system discovered that "patient information management," "work order basic information management," "service doctor information management," and "patient medication information management" are frequently occurring business functions. The system also identifies common work order statuses such as "created," "in progress," "completed," and "closed."

[0098] S202: Based on the at least one work order business function, construct a business function component corresponding to each work order business function;

[0099] S203: Based on the at least one work order status, construct a work order status component corresponding to each work order status;

[0100] In one embodiment, developers can construct corresponding business function components based on the work order business function. Each business function component can be targeted at a specific business function and have a clear functional description and configuration parameters.

[0101] In one embodiment, work orders are broken down into components based on their business functions. Developers develop component functions and publish them online, allowing operations personnel to configure doctor work orders. Business function components may include patient information components, basic work order information components, service doctor information components, and patient medication information components.

[0102] For example, the "Patient Information Component" is responsible for storing and managing the patient's personal information, including name, contact information, medical history, etc.; the "Work Order Basic Information Component" is responsible for recording the basic attributes of the work order, such as work order type, creation time, priority, etc.; the "Service Doctor Information Component" is used to associate the work order with the responsible doctor's information; the "Patient Medication Information Component" is used to record the patient's medication history and current medication status.

[0103] Similarly, based on the work order status, developers can build corresponding work order status components. The work order status component is responsible for managing the life cycle of the work order, including the state transition logic and trigger conditions.

[0104] For example, the "State Transition Component" manages the transition of work orders from "Created" to "Processing" and then to "Completed" or "Closed", and records the time and reason for each state change.

[0105] S204: Create the component library based on the business function component and the work order status component.

[0106] In one embodiment, in order to ensure the stability and maintainability of the components, each component in the component library (including business function components and work order status components) can be assigned a unique version number when it is released online, recording the changes and release time of each component for component content upgrades, while being compatible with the online use of components of different versions.

[0107] When a component in the component library needs to be upgraded, developers can release a new version without affecting existing functions and ensure that different versions of components can be used online in a compatible manner. This makes it easier to track the evolution history of the component and quickly roll back to the previous stable version when problems arise.

[0108] Furthermore, based on a preset version number rule, each preset component in the component library is version-marked, and the first version number of each preset component is determined, wherein the preset components include the business function component and the work order status component; when there is a component content change in the preset component in the component library, the changed component corresponding to the preset component is reconstructed based on the changed component content; the changed component corresponding to the preset component is stored in the component library, and the second version number of the changed component is determined.

[0109] In one embodiment, a version function can be configured for pre-set components to facilitate component content upgrades while maintaining compatibility with different versions of components online. This means that after a new version of a component is released, the old version will continue to function normally, without impacting existing services. Users can quickly identify component updates by version number, and flexible configuration of different versions of components is supported.

[0110] In one embodiment, the version number rule may be a semantic version number rule, such as a major version number, a minor version number, and a revision number. The major version number is incremented when a component has a significant functional change or an incompatible modification; the minor version number is incremented when a component adds a new function while maintaining compatibility; and the revision number is incremented when a component fixes a bug but does not introduce new functions.

[0111] Exemplarily, the initial version of a component may be marked as a first version number, and the version numbers of other components that subsequently undergo content changes based on the existing component may be marked as second version numbers, to distinguish and identify different versions of components of the same type.

[0112] For example, the initial version of a component can be labeled XComponent_1.0.0. If a major functional change occurs to the component and the old and new component contents are incompatible, the component after the change can be labeled XComponent_2.0.0. If a new function is added to the component while maintaining version compatibility, it can be labeled XComponent_1.1.0. If a bug is fixed while maintaining version compatibility, it can be labeled XComponent_1.1.1. XComponent_1.0.0 is the first version number of the component, and XComponent_2.0.0, XComponent_1.1.0, and XComponent_1.1.1 are the second version numbers corresponding to the component after the content change.

[0113] In the component library, each component is marked with its current version number and a version change log is recorded. Operations personnel can view the current version number and historical version information of each component in the component library. When configuring work orders, operators can select a specific version of the component to ensure that the work order function meets business requirements.

[0114] It is understandable that the above version number rule example is only an embodiment provided by the present application for ease of understanding, and other version number rules that can achieve the same function may also be used.

[0115] Generally, creating a component library is an ongoing iterative process. As the business evolves and user needs change, new business features and work order statuses may emerge continuously. The server can configure a component addition and update mechanism, allowing developers to dynamically expand the component library based on new requirements. For example, if "remote consultation" becomes a new business requirement, developers can build a "remote consultation component" and publish it to the component library for operations personnel to configure and use.

[0116] Operations personnel can select and combine these components through the configuration interface to meet the business needs of different doctor work orders. For example, when creating a "Physical Examination Report Interpretation Work Order," operations personnel can select the "Patient Information Component," "Work Order Basic Information Component," and "Report Parsing Component" to quickly build a processing flow that meets the work order's requirements. This componentized configuration approach not only improves the efficiency of work order creation but also enables the system to quickly adapt to business changes.

[0117] In this embodiment, component version management ensures compatibility when upgrading component content, reducing the risks associated with version changes. Furthermore, operators can flexibly configure components of different versions, improving the flexibility and stability of business operations.

[0118] It should be understood that the order of execution of the steps in the above embodiments does not necessarily mean the order of execution. The order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0119] In one embodiment, a work order generation device based on functional componentization is provided, which corresponds one-to-one to the work order generation method based on functional componentization in the above embodiment. Figure 6 As shown, the work order generation device based on functional componentization includes: a business demand information acquisition module 301, a business work order type determination module 302, a target component matching module 303 and a work order generation module 304. The functional modules are described in detail as follows:

[0120] The business requirement information obtaining module 301 is used to obtain the business requirement information of the target work order based on the work order creation request initiated by the client;

[0121] A business work order type determination module 302 is used to determine the business work order type based on the business demand information;

[0122] A target component matching module 303 is configured to search a preset component library for at least one target component that matches the business work order type;

[0123] The work order generation module 304 is configured to generate a target work order based on the work order content sent by the client and the target components.

[0124] In one embodiment, the target component matching module 303 includes:

[0125] An information determination unit, configured to determine, based on the business work order type, functional requirement information corresponding to at least one business function and status information corresponding to at least one work order status;

[0126] A business function component determining unit, configured to determine at least one business function component based on the function requirement information;

[0127] The work order status component determining unit is configured to determine at least one work order status component based on the status information.

[0128] In one embodiment, the work order generation device based on functional componentization further includes a work order status event configuration module, including:

[0129] a work order status event determining unit, configured to determine, when the client initiates an event configuration request for the work order status component, a work order status event corresponding to at least one of the status components based on an event selection instruction of the client;

[0130] The status component configuration update unit is used to update the configuration of the status component based on the event dimension information of the work order status event, so that the status component triggers the corresponding work order status event when the state changes.

[0131] In one embodiment, the work order generation device based on functional componentization further includes a work order status event generation module, including:

[0132] A work order status acquisition unit, configured to acquire at least one work order status based on historical work order data;

[0133] The work order status event generating unit is used to compose at least one event code based on the status value of each work order status and generate at least one work order status event.

[0134] In one embodiment, the work order generation device based on functional componentization further includes a component library creation module, including:

[0135] A data identification unit, configured to identify at least one work order business function and at least one work order status based on historical work order data;

[0136] A business function component construction unit, configured to construct a business function component corresponding to each work order business function based on the at least one work order business function;

[0137] A work order status component construction unit, configured to construct a work order status component corresponding to each work order status based on the at least one work order status;

[0138] A component library creation unit is used to create the component library based on the business function component and the work order status component.

[0139] In one embodiment, the component library creation module further includes:

[0140] a first version number determining unit, configured to perform version marking on each preset component in the component library based on a preset version number rule, and determine a first version number of each preset component, wherein the preset components include the business function component and the work order status component;

[0141] A component changing unit, configured to, when the content of the preset component in the component library is changed, rebuild the changed component corresponding to the preset component based on the changed component content;

[0142] The second version number determining unit is configured to store the changed component corresponding to the preset component in the component library and determine a second version number of the changed component.

[0143] In one embodiment, the business work order type determination module 302 includes:

[0144] A key information extraction unit, configured to perform feature recognition on the business demand information based on a data preprocessing algorithm to obtain key information;

[0145] The feature matching unit is used to perform feature matching on the key information and a predefined work order type library based on a feature matching algorithm to determine the business work order type.

[0146] The present invention provides a work order generation device based on functional componentization, which obtains the client's business demand information through a work order creation request initiated by the client, reduces the communication time and labor cost of demand confirmation, and ensures the accuracy and timeliness of the business demand information. By determining the business work order type based on the business demand information, the existing work order type can be quickly identified, avoiding repeated development and improving the efficiency of work order generation. By querying and calling existing components in the component library, business functions are componentized, and the reuse of components is realized, which avoids the redundant work of repeated development and testing, reduces the professional requirements of developers, and makes work order generation more flexible and efficient. The standardized design of the component library also ensures the consistency and stability of work orders, reduces errors and maintenance costs caused by inconsistent codes. By combining the target component and the work order content, the target work order is generated, and the rapid generation of the work order is realized, which reduces manual intervention and can quickly respond to business needs, thereby improving the efficiency and flexibility of work order generation.

[0147] For the specific limitations of the work order generation device based on functional componentization, please refer to the limitations of the work order generation method based on functional componentization above, which will not be repeated here. The various modules in the above-mentioned work order generation device based on functional componentization can be implemented in whole or in part through software, hardware and their combination. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0148] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 7 As shown. The computer device includes a processor, a memory, a network interface and a database connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile and / or volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external client via a network connection. When the computer program is executed by the processor, it realizes the functions or steps on the server side of a work order generation method based on functional componentization.

[0149] In one embodiment, a computer device is provided. The computer device may be a client, and its internal structure diagram may be as follows: Figure 8 As shown. The computer device includes a processor, memory, network interface, display screen and input device connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external server via a network connection. When the computer program is executed by the processor, it realizes the functions or steps on the client side of a work order generation method based on functional componentization.

[0150] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the following steps are performed:

[0151] Based on the work order creation request initiated by the client, obtain the business requirement information of the target work order;

[0152] Determine the type of business work order based on the business demand information;

[0153] Searching a preset component library for at least one target component that matches the business work order type;

[0154] A target work order is generated based on the work order content sent by the client and each of the target components.

[0155] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0156] Based on the work order creation request initiated by the client, obtain the business requirement information of the target work order;

[0157] Determine the type of business work order based on the business demand information;

[0158] Searching a preset component library for at least one target component that matches the business work order type;

[0159] A target work order is generated based on the work order content sent by the client and each of the target components.

[0160] It should be noted that the above functions or steps that can be implemented by the computer-readable storage medium or computer device can be found in the relevant descriptions of the server side and the client side in the aforementioned method embodiment. To avoid repetition, they will not be described one by one here.

[0161] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0162] Those skilled in the art will clearly understand that for the sake of convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0163] The embodiments described above are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present invention, and should all be included in the scope of protection of the present invention.

Claims

1. A work order generation method based on functional componentization, characterized in that: The method comprises: Based on the work order creation request initiated by the client, obtain the business requirement information of the target work order; Determine the type of business work order based on the business demand information; Searching a preset component library for at least one target component that matches the business work order type; A target work order is generated based on the work order content sent by the client and each of the target components.

2. The work order generation method based on functional componentization according to claim 1 is characterized in that: The step of searching a preset component library for at least one target component that matches the business work order type includes: Based on the business work order type, determining functional requirement information corresponding to at least one business function and status information corresponding to at least one work order status; Determining at least one business function component based on the function requirement information; At least one work order status component is determined based on the status information.

3. The work order generation method based on functional componentization according to claim 2 is characterized in that: Before generating a target work order based on the work order content sent by the client and each target component, the method further includes: When the client initiates an event configuration request for the work order status component, determining a work order status event corresponding to at least one of the status components based on an event selection instruction of the client; Based on the event dimension information of the work order status event, the status component is configured and updated so that the status component triggers the corresponding work order status event when the status changes.

4. The work order generation method based on functional componentization according to claim 3 is characterized in that: When the client initiates an event configuration request for the work order status component, before determining the work order status event corresponding to at least one of the status components based on the event selection instruction of the client, the method further includes: Based on historical work order data, obtain at least one work order status; Based on the status value of each work order status, at least one event code is composed to generate at least one work order status event.

5. The work order generation method based on functional componentization according to claim 1 is characterized in that: Before searching the preset component library for at least one target component that matches the business work order type, the method further includes: Based on historical work order data, identifying at least one work order business function and at least one work order status; Based on the at least one work order business function, construct a business function component corresponding to each work order business function; Based on the at least one work order status, construct a work order status component corresponding to each work order status; The component library is created based on the business function component and the work order status component.

6. The work order generation method based on functional componentization according to claim 5 is characterized in that: After creating the component library based on the business function component and the work order status component, the method further includes: Based on a preset version number rule, version-marking each preset component in the component library, and determining a first version number of each preset component, wherein the preset components include the business function component and the work order status component; When the content of the preset component in the component library is changed, rebuilding the changed component corresponding to the preset component based on the changed component content; The changed component corresponding to the preset component is stored in the component library, and a second version number of the changed component is determined.

7. The work order generation method based on functional componentization according to claim 1 is characterized in that: Determining the type of the business work order based on the business demand information includes: Based on the data preprocessing algorithm, feature recognition is performed on the business demand information to obtain key information; Based on a feature matching algorithm, feature matching is performed on the key information and a predefined work order type library to determine the business work order type.

8. A work order generation device based on functional componentization, characterized in that: The work order generation device based on functional componentization includes: The business requirement information acquisition module is used to obtain the business requirement information of the target work order based on the work order creation request initiated by the client; A business work order type determination module, configured to determine a business work order type based on the business demand information; A target component matching module, configured to search a preset component library for at least one target component that matches the business work order type; The work order generation module is used to generate a target work order based on the work order content sent by the client and each target component.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the work order generation method based on functional componentization as described in any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the work order generation method based on functional componentization as described in any one of claims 1 to 7 are implemented.

Images