Data processing method, system and device applied to smart hospital system

Abstract

The invention discloses a data processing method, system and device applied to an intelligent hospital system. A specific embodiment of the method comprises the steps of determining event data of a node event in a treatment process of a target user based on a plurality of service subsystems in a smart hospital system; according to the event data, updating a to-do event list corresponding to the target user; and displaying the to-do event list through the target terminal. According to the method, the to-do event list for displaying the hospital-wide-level to-do events is provided for the user, so that the query efficiency and convenience of the user are improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, specifically to the field of smart hospital technology, and in particular to a data processing method, device, computer-readable medium, and electronic device applied to a smart hospital system. Background Art

[0002] At present, the online smart hospital system can be accessed through channels such as official accounts and mini programs. In the hospital medical treatment business scenario, it mainly includes registration, queuing, prescription / examination / testing doctor's order issuance, payment, medication, examination and test appointment, examination and test execution, examination and test report and other business nodes. When the patient has a new status change or has pending events, the patient needs to enter the various business subsystems in the smart hospital system to see the corresponding pending events. For example, if the patient wants to view the registration record for the pending visit, he needs to enter the appointment registration subsystem to view the appointment registration record; if the patient wants to view the waiting information of the medical queue, he needs to enter the queuing subsystem to view the real-time queuing information. Summary of the invention

[0003] The embodiments of the present application propose a data processing method, system, device, computer-readable medium, electronic device and computer program product for application in a smart hospital system.

[0004] In the first aspect, an embodiment of the present application provides a data processing method applied to a smart hospital system, including: determining event data of node events in the target user's medical treatment process based on multiple business subsystems in the smart hospital system; updating a to-do event list corresponding to the target user based on the event data; and displaying the to-do event list through a target terminal.

[0005] In some examples, the above-mentioned event data of node events in the target user's medical treatment process are determined based on multiple business subsystems in the smart hospital system, including: receiving event data provided by multiple business subsystems based on a data template, wherein the data template includes multiple preset fields for characterizing attributes of the event data.

[0006] In some examples, the above-mentioned updating of the to-do event list corresponding to the target user based on the event data includes: determining the processing logic data for the event data based on the event type in the event data; in the to-do event list, executing at least one of adding a target to-do event and deleting an existing target to-do event according to the processing logic data.

[0007] In some examples, the above-mentioned processing logic data includes an event addition field for indicating a first event type of the target to-do event, and the above-mentioned adding of the target to-do event in the to-do event list according to the processing logic data includes: in response to the first event type being included under the event addition field, adding the target to-do event under the first event type in the to-do event list.

[0008] In some examples, the above-mentioned processing logic data includes a first judgement field for indicating an event addition judgement, and the event addition judgement is used to determine whether to add a target to-do event under the first event type, and the above-mentioned adding of the target to-do event under the first event type to the to-do event list includes: in response to the character data corresponding to the event addition judgement included in the first judgement field, determining whether to add the target to-do event through the event addition judgement; in response to determining yes, adding the target to-do event to the to-do event list.

[0009] In some examples, the above-mentioned processing logic data includes an event deletion field of a second event type for indicating that the target already has to-do events, and the above-mentioned deleting the target's existing to-do events in the to-do event list according to the processing logic data includes: in response to the second event type being included under the event deletion field, deleting the target's existing to-do events under the second event type in the to-do event list.

[0010] In some examples, the above-mentioned processing logic data includes a second judgement field for indicating an event deletion judgement, and the event deletion judgement is used to determine whether to delete the target's existing to-do event under the second event type, and the above-mentioned deleting the target's existing to-do event under the second event type in the to-do event list includes: in response to the character data corresponding to the event deletion judgement included in the second judgement field, determining whether to delete the target's existing to-do event through the event deletion judgement; in response to determining yes, deleting the target's existing to-do event in the to-do event list.

[0011] In some examples, the above method further includes: in response to the event data including a refresh identifier for indicating a timed refresh of the data, periodically acquiring and displaying target data of the target to-do event.

[0012] In some examples, the method further includes: in response to the event data including a page jump path and receiving a trigger operation of the target to-do event by the target user, jumping to the target page represented by the page jump path.

[0013] In some examples, the above-mentioned displaying the to-do event list through the target terminal includes: displaying the event content and effective time of the to-do events in the to-do event list through the target terminal, wherein the effective time is determined according to the expiration time in the event data.

[0014] On the second aspect, an embodiment of the present application provides a data processing system applied to a smart hospital system, including: multiple business subsystems, used to determine the event data of node events in the target user's medical treatment process; a to-do event center, used to update the to-do event list corresponding to the target user based on the event data; and display the to-do event list through the target terminal.

[0015] In some examples, the above-mentioned multiple business subsystems are further used to determine event data based on a data template, wherein the data template includes multiple preset fields for representing the event data.

[0016] In some examples, the to-do event center is further used to: determine processing logic data for the event data based on the event type in the event data; and in the to-do event list, execute at least one of adding a target to-do event and deleting an existing target to-do event according to the processing logic data.

[0017] In some examples, the processing logic data includes an event addition field for indicating a first event type of a target to-do event, and the to-do event center is further used to: in response to the event addition field including the first event type, add a target to-do event under the first event type in the to-do event list.

[0018] In some examples, the above-mentioned processing logic data includes a first judgement field for indicating an event addition judgement, the event addition judgement is used to determine whether to add a target to-do event under the first event type, and the above-mentioned to-do event center is further used to: respond to the character data corresponding to the event addition judgement included under the first judgement field, determine whether to add the target to-do event through the event addition judgement; in response to determining yes, add the target to-do event to the to-do event list.

[0019] In some examples, the processing logic data includes an event deletion field of a second event type for indicating that the target already has to-do events, and the to-do event center is further used to: in response to the event deletion field including the second event type, delete the target's existing to-do events under the second event type in the to-do event list.

[0020] In some examples, the above-mentioned processing logic data includes a second judgement field for indicating an event deletion judgement, and the event deletion judgement is used to determine whether to delete the target's existing to-do events under the second event type, and the above-mentioned to-do event center is further used to: respond to the character data corresponding to the event deletion judgement included in the second judgement field, determine whether to delete the target's existing to-do events through the event deletion judgement; in response to the determination of yes, delete the target's existing to-do events in the to-do event list.

[0021] In some examples, the to-do event center is further used to: in response to a refresh identifier included in the event data for indicating a timed refresh of the data, periodically obtain and display target data of the target to-do event.

[0022] In some examples, the to-do event center is also used to: in response to event data including a page jump path and receiving a trigger operation of a target to-do event by a target user, jump to a target page represented by the page jump path.

[0023] In some examples, the to-do event center is further used to: display the event content and effective time of the to-do events in the to-do event list through the target terminal, wherein the effective time is determined according to the expiration time in the event data.

[0024] In the third aspect, an embodiment of the present application provides a data processing device applied to a smart hospital system, including: a data determination unit, configured to determine the event data of node events in the target user's medical treatment process based on multiple business subsystems in the smart hospital system; a list updating unit, configured to update the to-do event list corresponding to the target user according to the event data; and a display unit, configured to display the to-do event list through the target terminal.

[0025] In some examples, the data determination unit is further configured to: receive event data provided by multiple business subsystems based on a data template, wherein the data template includes multiple preset fields for characterizing attributes of the event data.

[0026] In some examples, the list updating unit is further configured to: determine processing logic data for the event data based on the event type in the event data; and in the to-do event list, execute at least one of adding a target to-do event and deleting an existing target to-do event according to the processing logic data.

[0027] In some examples, the processing logic data includes an event addition field for indicating a first event type of a target to-do event, and the list update unit is further configured to: in response to the event addition field including the first event type, add a target to-do event under the first event type to the to-do event list.

[0028] In some examples, the above-mentioned processing logic data includes a first judgement field for indicating an event addition judgement, the event addition judgement is used to determine whether to add a target to-do event under the first event type, and the above-mentioned list update unit is further configured to: in response to the character data corresponding to the event addition judgement included under the first judgement field, determine whether to add the target to-do event through the event addition judgement; in response to determining yes, add the target to-do event to the to-do event list.

[0029] In some examples, the processing logic data includes an event deletion field of a second event type for indicating that the target already has to-do events, and the list update unit is further configured to: in response to the event deletion field including the second event type, delete the target's existing to-do events under the second event type in the to-do event list.

[0030] In some examples, the above-mentioned processing logic data includes a second judge field for indicating an event deletion judge, and the event deletion judge is used to determine whether to delete the target's existing to-do events under the second event type, and the above-mentioned list update unit is further configured to: in response to the character data corresponding to the event deletion judge included in the second judge field, determine whether to delete the target's existing to-do events through the event deletion judge; in response to determining yes, delete the target's existing to-do events in the to-do event list.

[0031] In some examples, the apparatus further includes a refresh unit configured to periodically acquire and display target data of a target to-do event in response to a refresh identifier included in the event data and used to indicate a timed refresh of the data.

[0032] In some examples, the apparatus further includes: a jump unit configured to: in response to the event data including a page jump path and receiving a trigger operation of a target to-do event by a target user, jump to a target page represented by the page jump path.

[0033] In some examples, the display unit is further configured to: display the event content and effective time of the to-do events in the to-do event list through the target terminal, wherein the effective time is determined according to the expiration time in the event data.

[0034] In a fourth aspect, an embodiment of the present application provides a computer-readable medium having a computer program stored thereon, wherein when the program is executed by a processor, the method described in any implementation manner of the first aspect is implemented.

[0035] In a fifth aspect, an embodiment of the present application provides an electronic device, comprising: one or more processors; a storage device on which one or more programs are stored, and when the one or more programs are executed by one or more processors, the one or more processors implement the method described in any implementation manner of the first aspect.

[0036] In a sixth aspect, an embodiment of the present application provides a computer program product, including: a computer program, which implements the method described in any implementation manner of the first aspect when executed by a processor.

[0037] The data processing method, system and device applied to the smart hospital system provided in the embodiments of the present application determine the event data of the node events in the medical treatment process of the target user based on multiple business subsystems in the smart hospital system; update the to-do event list corresponding to the target user according to the event data; and display the to-do event list through the target terminal, so as to provide the user with a to-do event list showing the to-do events at the hospital level, which helps to improve the user's query efficiency and convenience. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings:

[0039] Figure 1 is an exemplary system architecture diagram in which an embodiment of the present application may be applied;

[0040] Figure 2 is a flow chart of an embodiment of a data processing method applied to a smart hospital system according to the present application;

[0041] Figure 3 is a schematic diagram of the medical consultation process of the smart hospital system according to this embodiment;

[0042] Figure 4 is a schematic diagram of an application scenario of the data processing method applied to a smart hospital system according to this embodiment;

[0043] Figure 5 is a flowchart of another embodiment of a data processing method applied to a smart hospital system according to the present application;

[0044] Figure 6 is a structural diagram of an embodiment of a smart hospital system according to the present application;

[0045] Figure 7 is a structural diagram of an embodiment of a data processing device applied to a smart hospital system according to the present application;

[0046] Figure 8 It is a structural diagram of a computer system suitable for implementing the embodiments of the present application. DETAILED DESCRIPTION

[0047] The present application will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the relevant invention, rather than to limit the invention. It should also be noted that, for ease of description, only the parts related to the relevant invention are shown in the accompanying drawings.

[0048] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0049] It should be noted that the collection, collection, updating, analysis, processing, use, transmission, storage and other aspects of user personal information involved in the technical solution of this disclosure are in compliance with the provisions of relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken for user personal information to prevent illegal access to user personal information data and maintain the security of user personal information, network security and national security.

[0050] Figure 1 An exemplary architecture 100 to which the data processing method and apparatus for a smart hospital system of the present application can be applied is shown.

[0051] like Figure 1 As shown, the system architecture 100 may include terminal devices 101, 102, 103, a network 104 and a server 105. The communication connection between the terminal devices 101, 102, 103 constitutes a topological network, and the network 104 is used to provide a medium for the communication link between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0052] The terminal devices 101, 102, 103 can interact with the server 105 through the network 104 to receive or send data, etc. The terminal devices 101, 102, 103 can be hardware devices or software that support network connection for data interaction and data processing. When the terminal devices 101, 102, 103 are hardware, they can be various electronic devices that support network connection, information acquisition, interaction, display, processing and other functions, including but not limited to smart phones, car computers, tablet computers, e-book readers, laptop portable computers and desktop computers, etc. When the terminal devices 101, 102, 103 are software, they can be installed in the electronic devices listed above. It can be implemented as multiple software or software modules for providing distributed services, for example, or it can be implemented as a single software or software module. No specific limitation is made here.

[0053] Server 105 can be a server that provides various services, for example, in response to receiving a to-do event query request sent by a target user through terminal devices 101, 102, 103, based on multiple business subsystems in the smart hospital system, it determines the event data of the node event in the target user's medical process and updates the to-do event list. Optionally, the server can feed back the to-do event list to the terminal device. As an example, server 105 can be a cloud server.

[0054] It should be noted that the server can be hardware or software. When the server is hardware, it can be implemented as a distributed server cluster consisting of multiple servers, or it can be implemented as a single server. When the server is software, it can be implemented as multiple software or software modules (for example, software or software modules used to provide distributed services), or it can be implemented as a single software or software module. No specific limitation is made here.

[0055] It should also be noted that the data processing method applied to the smart hospital system provided in the embodiments of the present application is generally executed by a server, but the possibility of being executed by a terminal device, or being executed by a server and a terminal device in cooperation with each other, is not excluded. Accordingly, the various parts (such as various units) included in the data processing device applied to the smart hospital system can be all set in the server, or all set in the terminal device, or can be set in the server and the terminal device respectively.

[0056] It should be understood that Figure 1 The number of terminal devices, networks, and servers in the system is only illustrative. Depending on the implementation requirements, there may be any number of terminal devices, networks, and servers. When the electronic device on which the data processing method applied to the smart hospital system runs does not need to transmit data with other electronic devices, the system architecture may only include the electronic device (such as a server or terminal device) on which the data processing method applied to the smart hospital system runs.

[0057] Continue to refer Figure 2 , shows a process 200 of an embodiment of a data processing method applied to a smart hospital system, comprising the following steps:

[0058] Step 201, based on multiple business subsystems in the smart hospital system, determine the event data of the node events in the medical treatment process of the target user.

[0059] In this embodiment, the execution subject (eg Figure 1 The terminal device or server in the smart hospital system can determine the event data of the node events in the target user's medical treatment process based on multiple business subsystems in the smart hospital system.

[0060] The multiple business subsystems in the smart hospital system are subsystems used to provide the patient demand functions required by the smart hospital system in various aspects, mainly including HIS (Hospital Information System) system, queuing system, fee management system, PACS (picture archiving and communication system) system, LIS (Laboratory Information Management System) system, ECG system, medicine dispensing system and other business subsystems. The target user's medical treatment process involves multiple node events, such as appointment, registration, reception, inspection, report generation and other node events. Different node events have different task states.

[0061] As an example, for each business subsystem in the smart hospital system, the business subsystem obtains the event data of the node events of the target user in the business subsystem in real time, and sends the obtained event data to the to-do event center in the smart hospital system, so as to process the event data through the to-do event center, update and display the to-do event list.

[0062] As another example, for each business subsystem in the smart hospital system, the business subsystem detects in real time whether the node event of the target user in the business subsystem is updated. In response to the existence of an updated node event, the event data of the node event is sent to the to-do event center in the smart hospital system to process the event data through the to-do event center, and update and display the to-do event list.

[0063] In some implementations of this embodiment, the execution subject may perform step 201 in the following manner: receiving event data provided by multiple business subsystems based on a data template.

[0064] The data template includes a plurality of preset fields for representing attributes of event data.

[0065] As an example, several preset fields in the data template are shown in the following table:

[0066]

[0067]

[0068] The following are descriptions of each field:

[0069] patientId: The unique index of the patient, used to query all pending events under the patient. It comes from the patient ID (Identity document) in the HIS system, the core business subsystem of the hospital. Other business subsystems use the patient ID in the HIS system as the basis for transferring business events.

[0070] businessId: The unique ID number of the current business document when the business event flows, such as appointment registration ID, queue ID, doctor's order ID, payment item ID, inspection and test application form ID, medication prescription ID, etc.

[0071] relateBusinessId: The business document number that needs to be associated when the current business data occurs. Generally used to cancel pending events, for example, when canceling a registration, this field is the registration ID that needs to be canceled.

[0072] eventType: event type code, which uniformly codes all the business scenarios of the hospital and configures the corresponding task status change logic according to the event type code. For example: successful appointment registration event, successful cancellation of appointment registration event, successful queue registration event, successful payment event, etc.

[0073] eventTypeName: event type name, corresponding to the event type code.

[0074] eventContent: event content details, corresponding to the event type, which is the detailed information that needs to be displayed to the patient. Each business system customizes the event content and uses JSON (JavaScript Object Notation) format for transmission and storage. For example, the appointment registration event carries complete appointment registration information.

[0075] redirectUrl: The path to the page to be redirected, corresponding to the event type. If the status of some events changes, you need to click to jump to a specific page to display the content of the pending events, which is passed in through this field.

[0076] dynamicFlag: Whether to display the flag dynamically. Some pending events need to obtain the latest information in real time. The data changes dynamically. This flag is passed to indicate whether the current pending event needs to obtain information in real time. For example, in the event of queuing for medical treatment, it is necessary to determine the number of people in the queue before the target user in real time.

[0077] businessTime: business occurrence time, the time when the corresponding event of the pending event occurs.

[0078] expireTime: expiration time. The expiration time of the pending event is calculated based on the business event of the pending event and the expiration time range configured for the event type.

[0079] In this implementation, multiple business subsystems in the smart hospital system can transmit data with the to-do event center based on data templates. Based on a unified data template, it helps to improve the standardization and efficiency of the data transmission process.

[0080] Step 202: Update the to-do event list corresponding to the target user according to the event data.

[0081] In this embodiment, the above-mentioned execution entity can update the to-do event list corresponding to the target user according to the event data.

[0082] When the target user uses the smart hospital system for the first time, an empty to-do event list is generated for the target user. When the target user subsequently uses the smart hospital system, the to-do event list of the target user is updated through event data provided by multiple business subsystems in the smart hospital system.

[0083] As an example, the above-mentioned execution entity can determine the user's current unfinished to-do events and completed to-do events based on all to-do events provided by multiple business subsystems in the smart hospital system and refer to the standard medical treatment process of the smart hospital system; and then update the to-do event list based on the user's current unfinished to-do events and completed to-do events.

[0084] In some implementations of this embodiment, the execution subject may perform step 201 in the following manner:

[0085] The first step is to determine the processing logic data for the event data according to the event type in the event data.

[0086] According to the pending events generated by each business subsystem in the smart hospital system during the flow of medical events, the event type list is defined as follows:

[0087] BACKLOG_OP_WAITING: Waiting for medical treatment

[0088] BACKLOG_OP_QUEUING: Waiting for the number to be called

[0089] BACKLOG_RX_DISPENSING: medicine to be picked up

[0090] BACKLOG_INSPECT_WAITING: Waiting to be checked

[0091] BACKLOG_INSPECT_RESERVABLE: Waiting for scheduled inspection time

[0092] BACKLOG_INSPECT_QUEUING: Check in queue

[0093] BACKLOG_INSPECT_LAB_WAITING: Waiting for inspection

[0094] BACKLOG_INSPECT_LAB_QUEUING: Inspection queued

[0095] Continue to refer Figure 3 , which shows a schematic diagram of the medical consultation process of the smart hospital system. The medical consultation process is generally highly standardized, and its standardization is specifically reflected in the fact that the previous node event and the next node time of a node event are generally determined. For example, if the current node event is in the medical consultation queue, then its previous node event is generally waiting for medical consultation (appointment), and the next node event is generally medical consultation.

[0096] For each of the above event types, the processing logic data for the event type can be pre-set according to the standardized medical consultation process in the smart hospital system. The processing logic represented by the processing logic data is used to execute at least one of adding a target to-do event and deleting an existing target to-do event when an event of the corresponding event type occurs.

[0097] The second step is to execute at least one of adding a target to-do event and deleting an existing target to-do event in the to-do event list according to the processing logic data.

[0098] As an example, the above-mentioned execution entity can determine the newly generated target to-do events and / or the completed target existing to-do events according to the processing logic represented by the processing logic data, and then add the target to-do events and / or delete the target existing to-do events in the current to-do event list to obtain an updated to-do event list.

[0099] In this implementation, based on the processing logic data corresponding to the event type in the event data, the to-do event list corresponding to the target user is updated, which helps to improve the updating efficiency of the to-do event list while ensuring the accuracy of the update.

[0100] In some implementations of this embodiment, the processing logic data includes an event addition field for indicating the first event type of the target backlog event. For example, the event addition field is "produceBacklog", and the type code of the event type of the backlog event to be added can be filled in under this field.

[0101] In this implementation, the execution subject may execute the second step in the following manner: in response to the event addition field including the first event type, in the to-do event list, a target to-do event under the first event type is added.

[0102] When it is determined that the event addition field includes the first event type, a target to-do event under the first event type is added to the to-do event list based on the user information of the target user.

[0103] In this implementation, a method for adding a target to-do event to a to-do event list is provided, thereby improving the updating efficiency and accuracy of the to-do event list.

[0104] In some implementations of this embodiment, the processing logic data includes a first judgement field for indicating an event addition judgement, and the event addition judgement is used to determine whether to add a target to-do event under the first event type. For example, the first judgement field is "conditionClass", and the field is used to fill in the character data corresponding to the event addition judgement. When the event addition judgement returns true, the corresponding to-do event will be added.

[0105] For some event types, an event addition judgement can be set for them, and the input data of the event addition judgement can be clarified, so that when the first event type is included under the event addition field, the event addition judgement can be used to determine whether to add a to-do event of the first event type. It can be understood that some event types for which an event addition judgement is set generally have more complex addition logic, and it is not possible to directly determine that the target to-do event under the first event type can be added based on the inclusion of the first event type under the event addition field.

[0106] In this implementation, the execution subject can perform the operation of adding the target to-do event in the following manner:

[0107] First, in response to the character data corresponding to the event addition judgement included in the first judgement field, the event addition judgement is used to determine whether to add a target to-do event; then, in response to the determination of yes, the target to-do event is added to the to-do event list.

[0108] As an example, in response to the character data corresponding to the event addition judgement included under the first judgement field, the input data required by the event addition judgement is obtained, and the judge determines whether to add the target to-do event; in response to the determination of yes, the target to-do event under the first event type is added to the to-do event list.

[0109] In this implementation, the event addition judgement under the first judgement field determines whether to add a target to-do event under the first event type, thereby further improving the accuracy of the to-do event list.

[0110] In some implementations of this embodiment, the processing logic data includes an event deletion field of the second event type for indicating that the target already has a pending event.

[0111] In this implementation, the execution subject may perform the second step in the following manner: in response to the event deletion field including the second event type, in the to-do event list, delete the target existing to-do event under the second event type.

[0112] When it is determined that the event addition field includes the second event type, the target existing to-do events under the second event type are deleted from the to-do event list.

[0113] In this implementation, a method for deleting existing to-do events of a target in a to-do event list is provided, thereby improving the updating efficiency and accuracy of the to-do event list.

[0114] In some implementations of this embodiment, the processing logic data includes a second judgement field for indicating an event deletion judgement, and the event deletion judgement is used to determine whether to delete the target existing pending event under the second event type.

[0115] For some event types, an event deletion judgement can be set for them, and the input data of the event deletion judgement can be clarified so that when the second event type is included under the event deletion field, the event deletion judgement can be used to determine whether to add a to-do event of the second event type. It can be understood that some event types for which an event deletion judgement is set generally have more complex deletion logic, and it is not possible to directly determine that the target existing to-do event under the second event type can be deleted based on the inclusion of the second event type under the event deletion field.

[0116] In this implementation, the above-mentioned execution entity can execute the deletion operation of the above-mentioned target's existing to-do events in the following manner: first, in response to the character data corresponding to the event deletion judgement included in the second judgement field, determine whether to delete the target's existing to-do events through the event deletion judgement; then, in response to the determination of yes, delete the target's existing to-do events in the to-do event list.

[0117] As an example, in response to the character data corresponding to the event deletion judgement included under the second judgement field, the input data required by the event deletion judgement is obtained, and the judge determines whether to delete the target's existing to-do events; in response to the determination of yes, in the to-do event list, the target's existing to-do events under the second event type are deleted.

[0118] In this implementation, the event deletion determiner under the second determiner field determines whether to delete the target existing to-do event under the second event type, thereby further improving the accuracy of the to-do event list.

[0119] To further illustrate the update operation for the to-do list, the following data structure for processing logic data is given:

[0120] {

[0121] "eventType":"Event type code",

[0122] "eventTypeName":"Event type name",

[0123] "removeBacklogList":[cancel backlog event type encoding array],

[0124] "produceBacklogList":[

[0125] {

[0126] "conditionClass":"Add a new to-do event judgement",

[0127] "produceBacklog":"Add a new to-do event type code",

[0128] "expirtTime": "Expiration date of the pending event"

[0129] } ]

[0131] }

[0132] The meanings of the above fields are as follows:

[0133] eventType / eventTypeName: event type code and name, which refers to the event type of the flow node events of all business subsystems defined above.

[0134] removeBacklogList: Cancel the to-do event type code array. The information configured here is the to-do event type defined above, which means that when this event type code is sent and reported, the corresponding to-do event will be deleted.

[0135] produceBacklogList: adds an array of to-do event types, where the processing logic data of the newly added to-do events is configured.

[0136] conditionClass: Add a judgment selector for the target to-do event. When this judgment selector returns true, the corresponding to-do event will be added.

[0137] produceBacklog: The type of to-do event that needs to be added is encoded.

[0138] expirationTime: The validity period of the to-do event, in hours; this configuration represents the validity period of the to-do event.

[0139] Step 203: Display the to-do event list via the target terminal.

[0140] In this embodiment, the execution subject may display a list of to-do events through a target terminal.

[0141] As an example, the above-mentioned execution subject can display the updated to-do event list to the target user through the target terminal to help the user quickly determine the current to-do event.

[0142] The target terminal is any terminal device that can display a to-do list to the target user, such as a user's smart phone, a smart terminal in a hospital, etc.

[0143] In some optional implementations of this embodiment, the execution subject may perform step 203 in the following manner: displaying the event content and effective time of the to-do event in the to-do event list through the target terminal.

[0144] The effective time is determined according to the expiration time in the event data.

[0145] The event content can be determined based on the eventContent field in the data template, and the expiration time can be determined based on the expireTime field in the data template.

[0146] In this implementation, detailed to-do events are displayed in the to-do event list, which helps to further improve the user's information acquisition efficiency and experience.

[0147] Continue to see Figure 4 , Figure 4 FIG4 is a schematic diagram 400 of an application scenario of the data processing method applied to a smart hospital system according to the present embodiment. Figure 4 In the application scenario, user 401 accesses the smart hospital system deployed in server 403 through terminal device 402. The smart hospital system includes a to-do event center and multiple business subsystems, including HIS hospital information management system, queuing system, fee management system, PACS image management system, LIS inspection system, ECG system, and medicine dispensing system. The multiple business subsystems in the smart hospital system determine the event data of the node events in the target user's medical treatment process, and send the time data to the to-do event center; the to-do event center updates the to-do event list corresponding to the target user according to the event data, and feeds the to-do event list back to the terminal device; the terminal device 402 displays the to-do event list to the target user 401.

[0148] The method provided by the above-mentioned embodiments of the present application determines the event data of the node events in the target user's medical treatment process based on multiple business subsystems in the smart hospital system; updates the to-do event list corresponding to the target user according to the event data; and displays the to-do event list through the target terminal, thereby providing the user with a to-do event list that displays the to-do events at the hospital-wide level, which helps to improve the user's query efficiency and convenience.

[0149] In some implementations of this embodiment, the execution subject may further perform the following operation: in response to the event data including a refresh identifier for indicating a timed refresh of data, periodically acquiring and displaying target data of a target to-do event.

[0150] As an example, the refresh flag used to indicate the scheduled refresh of data is dynamicFlag. Some pending events need to obtain the latest information in real time, and the data changes dynamically. This flag is passed in to indicate whether the current pending event needs to obtain information in real time. For example, in the event of queuing for medical treatment, it is necessary to determine the number of people in the queue before the target user in real time.

[0151] In this implementation, data with real-time data refresh requirements are indicated by a refresh flag, which helps to improve the accuracy of such data.

[0152] In some implementations of this embodiment, the above-mentioned execution entity can also perform the following operations: in response to the event data including a page jump path and receiving a trigger operation of the target user on the target to-do event, jump to the target page represented by the page jump path.

[0153] As an example, the page jump path can be indicated by the redirectUrl field. If some event status changes, you need to click to jump to a specific page to display the to-do content, which is passed in through this field.

[0154] In this implementation, based on the page jump path, the page can be jumped to the target page represented by the page jump path, which can meet the user's detailed viewing needs.

[0155] Continue to refer Figure 5 , shows a schematic process 500 of another embodiment of a data processing method applied to a smart hospital system according to the present application, comprising the following steps:

[0156] Step 501: Receive event data of node events in the medical treatment process of a target user provided by multiple business subsystems in the smart hospital system based on a data template.

[0157] The data template includes a plurality of preset fields for representing attributes of event data.

[0158] Step 502: Determine processing logic data for the event data according to the event type in the event data.

[0159] Step 503, in response to the event adding field in the processing logic data including the first event type, and the first judgement field in the processing logic data including character data corresponding to the event adding judgement, determine whether to add the target to-do event through the event adding judgement.

[0160] Step 504 , in response to the determination being yes, adding a target to-do event under the first event type to the to-do event list.

[0161] Step 505, in response to the event deletion field in the processing logic data including the second event type, and the second judgement field in the processing logic data including character data corresponding to the event deletion judgement, determine whether to delete the target's existing pending events through the event deletion judgement.

[0162] Step 506 , in response to the determination being yes, in the to-do event list, deleting the target existing to-do event under the second event type.

[0163] Step 507: Display the to-do event list via the target terminal.

[0164] It can be seen from this embodiment that Figure 2 Compared with the corresponding embodiments, the process 500 of the data processing method applied to the smart hospital system in this embodiment specifically illustrates the data transmission process based on the data template and the list update process based on the processing logic data, providing users with a to-do event list that displays to-do events at the hospital level, which helps to improve the user's query efficiency and convenience.

[0165] Continue to refer Figure 6 , showing a structural schematic diagram of a data processing system 600 applied to a smart hospital system.

[0166] like Figure 6 As shown, the data processing system applied to the smart hospital system includes: multiple business subsystems 601, which are used to determine the event data of the node events in the target user's medical treatment process; a to-do event center 602, which is used to update the to-do event list corresponding to the target user according to the event data; and display the to-do event list through the target terminal.

[0167] In some implementations of this embodiment, the above-mentioned multiple business subsystems 601 are further used to determine event data based on a data template, wherein the data template includes multiple preset fields for representing the event data.

[0168] In some implementations of this embodiment, the above-mentioned to-do event center 602 is further used to: determine the processing logic data for the event data according to the event type in the event data; in the to-do event list, execute at least one of adding a target to-do event and deleting an existing target to-do event according to the processing logic data.

[0169] In some implementations of this embodiment, the above-mentioned processing logic data includes an event addition field for indicating the first event type of the target to-do event, and the above-mentioned to-do event center 602 is further used to: in response to the event addition field including the first event type, add the target to-do event under the first event type in the to-do event list.

[0170] In some implementations of this embodiment, the above-mentioned processing logic data includes a first judgement field for indicating an event addition judgement, and the event addition judgement is used to determine whether to add a target to-do event under the first event type, and the above-mentioned to-do event center 602 is further used to: respond to the character data corresponding to the event addition judgement included in the first judgement field, determine whether to add the target to-do event through the event addition judgement; in response to determining yes, add the target to-do event to the to-do event list.

[0171] In some implementations of this embodiment, the above-mentioned processing logic data includes an event deletion field of a second event type for indicating that the target already has to-do events, and the above-mentioned to-do event center 602 is further used to: in response to the event deletion field including the second event type, delete the target's existing to-do events under the second event type in the to-do event list.

[0172] In some implementations of this embodiment, the above-mentioned processing logic data includes a second judgement field for indicating an event deletion judgement, and the event deletion judgement is used to determine whether to delete the target's existing to-do events under the second event type, and the above-mentioned to-do event center 602 is further used to: respond to the character data corresponding to the event deletion judgement included in the second judgement field, determine whether to delete the target's existing to-do events through the event deletion judgement; in response to the determination of yes, delete the target's existing to-do events in the to-do event list.

[0173] In some implementations of this embodiment, the to-do event center 602 is further used to: in response to the event data including a refresh identifier for indicating a timed refresh of data, periodically acquire and display target data of a target to-do event.

[0174] In some implementations of this embodiment, the to-do event center 602 is also used to: in response to the event data including a page jump path and receiving a trigger operation of the target user on the target to-do event, jump to the target page represented by the page jump path.

[0175] In some implementations of this embodiment, the to-do event center 602 is further used to: display the event content and effective time of the to-do events in the to-do event list through the target terminal, wherein the effective time is determined according to the expiration time in the event data.

[0176] In this embodiment, multiple business subsystems in the smart hospital system are used to determine the event data of node events in the target user's medical treatment process. The to-do event center is used to update the to-do event list corresponding to the target user based on the event data, and display the to-do event list through the target terminal, thereby providing the user with a to-do event list that displays to-do events at the hospital level, which helps to improve the user's query efficiency and convenience.

[0177] Continue to refer Figure 7 As an implementation of the methods shown in the above figures, the present application provides an embodiment of a data processing device applied to a smart hospital system. Figure 2 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0178] like Figure 7 As shown, the data processing device 700 applied to the smart hospital system includes: a data determination unit 701, which is configured to determine the event data of the node events in the medical treatment process of the target user based on multiple business subsystems in the smart hospital system; a list updating unit 702, which is configured to update the to-do event list corresponding to the target user according to the event data; and a display unit 703, which is configured to display the to-do event list through the target terminal.

[0179] In some implementations of this embodiment, the data determination unit 701 is further configured to: receive event data provided by multiple business subsystems based on a data template, wherein the data template includes multiple preset fields for characterizing attributes of the event data.

[0180] In some implementations of this embodiment, the above-mentioned list updating unit 702 is further configured to: determine the processing logic data for the event data according to the event type in the event data; in the to-do event list, execute at least one of adding a target to-do event and deleting an existing target to-do event according to the processing logic data.

[0181] In some implementations of this embodiment, the above-mentioned processing logic data includes an event addition field for indicating the first event type of the target to-do event, and the above-mentioned list updating unit 702 is further configured to: in response to the event addition field including the first event type, add the target to-do event under the first event type to the to-do event list.

[0182] In some implementations of this embodiment, the above-mentioned processing logic data includes a first judgement field for indicating an event addition judgement, and the event addition judgement is used to determine whether to add a target to-do event under the first event type, and the above-mentioned list update unit 702 is further configured to: in response to the character data corresponding to the event addition judgement included in the first judgement field, determine whether to add the target to-do event through the event addition judgement; in response to determining yes, add the target to-do event to the to-do event list.

[0183] In some implementations of this embodiment, the above-mentioned processing logic data includes an event deletion field of a second event type for indicating that the target already has to-do events, and the above-mentioned list updating unit 702 is further configured to: in response to the event deletion field including the second event type, delete the target's existing to-do events under the second event type in the to-do event list.

[0184] In some implementations of this embodiment, the above-mentioned processing logic data includes a second judgement field for indicating an event deletion judgement, and the event deletion judgement is used to determine whether to delete the target's existing to-do events under the second event type, and the above-mentioned list update unit 702 is further configured to: in response to the character data corresponding to the event deletion judgement included in the second judgement field, determine whether to delete the target's existing to-do events through the event deletion judgement; in response to determining yes, delete the target's existing to-do events in the to-do event list.

[0185] In some implementations of this embodiment, the above-mentioned device also includes: a refresh unit (not shown in the figure), which is configured to: in response to the event data including a refresh identifier for indicating the timed refresh of data, regularly obtain and display the target data of the target to-do event.

[0186] In some implementations of this embodiment, the above-mentioned device also includes: a jump unit (not shown in the figure), which is configured to: in response to the event data including a page jump path and receiving a trigger operation of the target user on the target to-do event, jump to the target page represented by the page jump path.

[0187] In some implementations of this embodiment, the display unit 703 is further configured to: display the event content and effective time of the to-do events in the to-do event list through the target terminal, wherein the effective time is determined according to the expiration time in the event data.

[0188] In this embodiment, the data determination unit in the data processing device applied to the smart hospital system determines the event data of the node events in the target user's medical treatment process based on multiple business subsystems in the smart hospital system; the list updating unit updates the to-do event list corresponding to the target user according to the event data; the display unit displays the to-do event list through the target terminal, thereby providing the user with a to-do event list that displays the to-do events at the hospital level, which helps to improve the user's query efficiency and convenience.

[0189] Reference below Figure 8 , which shows a device suitable for implementing the embodiments of the present application (eg Figure 1 Schematic diagram of the structure of a computer system 800 of the devices 101, 102, 103, 105 shown. Figure 8 The device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0190] like Figure 8 As shown, the computer system 800 includes a processor (e.g., CPU, central processing unit) 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage part 808 into a random access memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the system 800 are also stored. The processor 801, ROM 802, and RAM 803 are connected to each other via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0191] The following components are connected to the I / O interface 805: an input section 806 including a keyboard, a mouse, etc.; an output section 807 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN card, a modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the I / O interface 805 as needed. A removable medium 811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 810 as needed, so that a computer program read therefrom is installed into the storage section 808 as needed.

[0192] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication part 809, and / or installed from a removable medium 811. When the computer program is executed by the processor 801, the above-mentioned functions defined in the method of the present application are executed.

[0193] It should be noted that the computer-readable medium of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0194] The computer program code for performing the operation of the present application can be written in one or more programming languages ​​or a combination thereof, including target-oriented programming languages ​​and conventional procedural programming languages. The program code can be executed entirely on the client computer, partially on the client computer, as an independent software package, partially on the client computer and partially on the remote computer, or completely on the remote computer or server. In the case of a remote computer, the remote computer can be connected to the client computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., using an Internet service provider to connect through the Internet).

[0195] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the device, method and computer program product according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0196] The units involved in the embodiments described in the present application may be implemented by software or by hardware. The described units may also be set in a processor, for example, may be described as: a processor comprising a data determination unit, a list update unit, and a display unit. Among them, the names of these units do not constitute a limitation on the unit itself under certain circumstances. For example, the data determination unit may also be described as "a unit for determining event data of node events in the medical treatment process of a target user based on multiple business subsystems in a smart hospital system."

[0197] As another aspect, the present application also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by the device, the computer device: determines the event data of the node events in the treatment process of the target user based on multiple business subsystems in the smart hospital system; updates the to-do event list corresponding to the target user according to the event data; and displays the to-do event list through the target terminal.

[0198] The above description is only a preferred embodiment of the present application and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the present application is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above invention concept. For example, the above features are replaced with the technical features with similar functions disclosed in this application (but not limited to) by each other to form a technical solution.

Claims

1. A data processing method applied to a smart hospital system, comprising: Based on multiple business subsystems in the smart hospital system, determine the event data of node events in the target user's medical process; According to the event data, updating the to-do event list corresponding to the target user; The to-do event list is displayed via the target terminal.

2. The method according to claim 1, wherein: The event data of node events in the target user's medical treatment process are determined based on multiple business subsystems in the smart hospital system, including: The event data provided by the multiple business subsystems based on a data template is received, wherein the data template includes multiple preset fields for characterizing attributes of the event data.

3. The method according to claim 1, wherein: The updating of the to-do event list corresponding to the target user according to the event data includes: Determining processing logic data for the event data according to the event type in the event data; In the to-do event list, at least one of adding a target to-do event and deleting an existing target to-do event is executed according to the processing logic data.

4. The method according to claim 3, wherein: The processing logic data includes an event addition field for indicating a first event type of the target to-do event, and In the to-do event list, adding a target to-do event according to the processing logic data includes: In response to the event addition field including the first event type, a target to-do event under the first event type is added to the to-do event list.

5. The method according to claim 4, wherein: The processing logic data includes a first judgement field for indicating an event addition judgement, wherein the event addition judgement is used to determine whether to add a target to-do event under the first event type, and Adding a target to-do event of the first event type to the to-do event list includes: In response to the first judgement field including character data corresponding to the event addition judgement, determining whether to add the target to-do event through the event addition judgement; In response to determining yes, the target to-do event is added to the to-do event list.

6. The method according to claim 3, wherein: The processing logic data includes an event deletion field of a second event type for indicating that the target already has a pending event, and In the to-do event list, deleting the target to-do event according to the processing logic data includes: In response to the event deletion field including the second event type, in the to-do event list, the target existing to-do event under the second event type is deleted.

7. The method according to claim 6, wherein: The processing logic data includes a second judgement field for indicating an event deletion judgement, wherein the event deletion judgement is used to determine whether to delete an existing pending event of the target under the second event type, and Deleting the target existing to-do event under the second event type in the to-do event list includes: In response to the character data corresponding to the event deletion judgement included in the second judgement field, determining whether to delete the existing pending event of the target through the event deletion judgement; In response to determining yes, in the to-do event list, deleting the existing to-do events of the target.

8. The method according to claim 3, wherein: Also includes: In response to the event data including a refresh identifier for indicating a timed refresh of data, the target data of the target to-do event is acquired and displayed timedly.

9. The method according to claim 3, wherein: Also includes: In response to the event data including a page jump path and receiving a trigger operation of the target user on the target to-do event, jumping to the target page represented by the page jump path.

10. The method according to claim 3, wherein: The displaying of the to-do event list by the target terminal includes: The event content and effective time of the to-do events in the to-do event list are displayed, wherein the effective time is determined according to the expiration time in the event data.

11. A smart hospital system, comprising: Multiple business subsystems are used to determine the event data of node events in the medical consultation process of the target user; A to-do event center, used to update the to-do event list corresponding to the target user according to the event data; The to-do event list is displayed via the target terminal.

12. A data processing device applied to a smart hospital system, comprising: A data determination unit is configured to determine event data of node events in a medical consultation process of a target user based on multiple business subsystems in the smart hospital system; A list updating unit, configured to update a to-do event list corresponding to the target user according to the event data; The display unit is configured to display the to-do event list through the target terminal.

13. A computer readable medium having a computer program stored thereon, wherein: When the program is executed by a processor, the method according to any one of claims 1 to 10 is implemented.

14. An electronic device comprising: one or more processors; a storage device having one or more programs stored thereon, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 10.

15. A computer program product comprising: A computer program which, when executed by a processor, implements the method according to any one of claims 1 to 10.

Images