A payment processing method for hospital information system based on message machine

Abstract

The present invention relates to the technical field of payment management, and discloses a payment processing method for a hospital information system based on a message machine; the method comprises constructing information to be paid into an order to be paid, identifying the confirmation status of the order to be paid, aggregating the order to be paid and payment data to generate an order data packet, identifying the payment status of the order data packet, extracting the payment features of the order data packet in a correction processing mode, correcting the payment data, and backing up the valid order in a feedback processing mode; compared with the prior art, the present invention can accurately identify the matching degree between the order to be paid and the user end, avoid order data that does not match the user end, and determine the payment status of the order to be paid in combination with the payment data, so as to ensure the effective payment of the order to be paid by the user end, and send the paid order to the hospital end in time for order processing display.

Description

Technical Field

[0001] The present invention relates to the technical field of payment management, and more specifically, to a payment processing method for a hospital information system based on a message machine. Background Art

[0002] Hospital information system is an information system that uses modern means such as computer technology and network communication technology to collect, store, process, extract, transmit and summarize the data generated by the hospital and its departments at all stages of medical activities, and provides comprehensive automated management and various services for the overall operation of the hospital. When the user pays for the order, different payment statuses may appear due to problems such as incorrect order information or network delays. Therefore, the hospital information system needs to carry out targeted processing of orders with different payment statuses to ensure the efficient and stable operation of the hospital information system.

[0003] The patent application with reference publication number CN115775148A discloses a payment processing method, device and equipment for a hospital information system based on a message machine, which constructs a message body with a confirmation mechanism and a reporting mechanism for order information, processing information and notification information through a message machine, ensures accurate receipt of messages at each node, and can actively report fault information of the node when an abnormality occurs. After receiving the fault information and handling the fault according to the fault information, the message machine will automatically resend the failed order message, processing information or notification information, ensuring the original information transmission and business logic. The message machine greatly reduces the complexity of information transmission of the entire order payment system and improves the accuracy of fault detection.

[0004] When processing payment for existing hospital orders, the accuracy and rationality of the orders are analyzed by comparing the payment data on the user side with the related data in the order information on the hospital side one by one, and then payment is processed for orders in different states. Due to the large number and type of information contained in the order, the method of comparing the related data one by one will bring a large workload, and it is easy to omit erroneous information in the order, thereby increasing the probability of erroneous payment of the order and reducing the accuracy and rationality of the hospital information system's order payment processing.

[0005] In view of this, the present invention proposes a payment processing method for a hospital information system based on a message machine to solve the above problems. Summary of the invention

[0006] In order to overcome the above-mentioned defects of the prior art and to achieve the above-mentioned purpose, the present invention provides the following technical solution: a payment processing method for a hospital information system based on a message machine, applied to a cloud server, comprising:

[0007] S1: Filter out the information to be paid from the hospital information system, the information to be paid includes identity information, project information, price information and date information, and construct the information to be paid into an order to be paid based on the construction criteria;

[0008] S2: Send the order to be paid to the user end through the user message machine, identify the confirmation status of the order to be paid, which includes the correct status and the incorrect status, and determine whether the order payment requirements are met; if the order payment requirements are met, execute S3; if the order payment requirements are not met, repeat S1-S2;

[0009] S3: Obtain payment data from the user, aggregate the orders to be paid and the payment data to generate an order data packet, and send the order data packet to the cloud server through the hospital message machine;

[0010] S4: Identify the payment status of the order data packet, which includes a passed status and a failed status, divide the orders to be paid into order attributes according to the payment status, which includes a valid order and an invalid order, and select a correction processing mode or a feedback processing mode;

[0011] S5: In the correction processing mode, the payment features of the order data packet are extracted, the payment features include effective verification time, network transmission rate and verification similarity, and the failure features are identified from the payment features;

[0012] S6: Eliminate the failed features and correct the payment data until a valid order is generated and sent to the user end and the hospital end for display;

[0013] S7: In the feedback processing mode, valid orders are backed up and sent to the user end and the hospital end for display.

[0014] Furthermore, the construction criteria are: each order slot contains only one piece of information to be paid;

[0015] The construction method of the order to be paid includes:

[0016] Selecting blank orders with four information lines from the order database, and recording the four information lines in order from top to bottom as a first information line, a second information line, a third information line, and a fourth information line;

[0017] From left to right, two order positions are drawn in the first information row, the second information row, the third information row and the fourth information row, respectively recorded as the first order position and the second order position;

[0018] Use natural language processing technology to identify the text and number semantics in identity information, project information, price information, and date information one by one;

[0019] The textual semantics and numerical semantics in the identity information, project information, price information and date information are respectively imported into the first order position and the second order position of the first information line, the second information line, the third information line and the fourth information line to construct an order to be paid.

[0020] Furthermore, the method for identifying the error-free state and the error-indicated state includes:

[0021] Query the confirmation events in the confirmation management system, mark the remark box of the confirmation event, and identify the remark value in the remark box;

[0022] When the remark value in the remark box is 0, the confirmation status of the order to be paid is recorded as correct;

[0023] When the remark value in the remark box is 1, the confirmation status of the order to be paid is recorded as an error status;

[0024] Methods for determining whether order payment requirements are met include:

[0025] When the confirmation status of the order to be paid is in an error state, it is determined that the order to be paid does not meet the order payment requirements;

[0026] When the confirmation status of the order to be paid is correct, it is determined that the order to be paid meets the order payment requirements.

[0027] Furthermore, the method for generating the order data packet includes:

[0028] The payment management system queries the i operation data input by the user, and counts the operation attributes of the i operation data one by one;

[0029] Identify the keywords of i operation attributes one by one through natural language processing technology, and record the operation data with the keywords of password, fingerprint and face as payment data, and obtain p payment data;

[0030] After the payment data with the same keyword are aggregated, m data sets are obtained;

[0031] Draw out m data positions on the order to be paid respectively, and import the m data sets into the m data positions one by one to generate an order data packet.

[0032] Furthermore, the method for identifying the pass status and the fail status includes:

[0033] Mark the keywords of each payment data in the m data sets in the order data packet one by one;

[0034] When the keyword of the payment data is a password, the number of characters in the password in the payment data is counted and recorded as the password value, and the password value is compared with the standard password threshold for payment verification;

[0035] When the password value is consistent with the standard password threshold in terms of size and content, the payment status of the order data packet is recorded as passed;

[0036] When the password value is inconsistent with the standard password threshold in size or content, the payment status of the order data packet is recorded as failed;

[0037] Methods for selecting the correction processing mode or the completion feedback processing mode include:

[0038] When the payment status of the order data packet is passed, the order to be paid is classified as a valid order, and the feedback processing mode is selected;

[0039] When the payment status of the order data package is not passed, the order to be paid is classified as an invalid order and the correction processing mode is selected.

[0040] Furthermore, the method for obtaining the network transmission rate includes:

[0041] Query the payment structure of payment data and the storage structure of data stored in the database through the attribute management system;

[0042] The storage data with the same storage structure and payment structure are recorded as associated data, and the number of associated data is counted;

[0043] The time when the user end imported the first associated data and the time when the hospital end received the last associated data are queried through the timestamp, and recorded as the start time and the end time respectively;

[0044] The time between the start time and the end time is recorded as the transmission time, and the amount of associated data is compared with the transmission time to obtain the network transmission rate;

[0045] The expression of network transmission rate is:

[0046] ;

[0047] In the formula, is the network transmission rate, is the number of associated data, The transmission duration.

[0048] Furthermore, the method for obtaining the verification similarity includes:

[0049] Identify payment phrases in payment data through natural language processing technology, and split payment phrases into independent phrase units through word segmentation technology;

[0050] Compare the phrase unit with the standard unit in the database for coincidence, and identify the comparison status of the phrase unit;

[0051] The phrase units whose comparison status is an overlapping status are recorded as verification units, and the number of verification units is counted, and the number of verification units is compared with the number of phrase units to obtain verification similarity;

[0052] The expression for verifying similarity is:

[0053] ;

[0054] In the formula, To verify the similarity, is the number of verification units, is the number of phrase units.

[0055] Furthermore, the method for identifying failure features includes:

[0056] The effective verification time Verification time safety value Compare, when Greater than When , the effective verification time is recorded as a failure feature;

[0057] Set the network transmission rate Transmitting security values ​​with the network Compare, when Less than When , the network transmission rate is recorded as the failure feature;

[0058] Will verify similarity Similar to verification safety value Compare, when Less than When , the verification similarity is recorded as a failed feature.

[0059] Furthermore, the method for correcting payment data includes:

[0060] Count the number of failed features in the payment data and record it as the failure value;

[0061] When the failure value is 1, and the failure feature is the effective verification time or the verification similarity, the effective verification time or the verification similarity is removed, and the corrected effective verification time or the verification similarity is re-imported through the user end;

[0062] When the failure value is 2, and the failure characteristics are the effective verification time and the verification similarity, the effective verification time and the verification similarity are removed, and the corrected effective verification time and the verification similarity are re-imported through the user end;

[0063] When the failure value is 1, 2 or 3, and the failure feature includes the network transmission rate, the effective verification time, network transmission rate and verification similarity will all be eliminated, and after changing the communication network of the user end, the corrected effective verification time, network transmission rate and verification similarity will be re-imported through the user end.

[0064] Further, effective order backup methods include:

[0065] Get the date and name in the identity information of the valid order to be paid, and create a backup folder;

[0066] Import all pending orders and payment data in the valid orders into the backup folder, and note the date and name as the file name of the backup folder.

[0067] The technical effects and advantages of the payment processing method of a hospital information system based on a message machine of the present invention are as follows:

[0068] The present invention filters out the information to be paid from the hospital information system, and constructs the information to be paid into an order to be paid based on construction criteria, sends the order to be paid to the user end through a user message machine, identifies the confirmation status of the order to be paid, and determines whether the order payment requirements are met, obtains the payment data of the user end, aggregates the order to be paid and the payment data to generate an order data packet, and sends the order data packet to the cloud server through the hospital message machine, identifies the payment status of the order data packet, divides the order to be paid into order attributes according to the payment status, and selects a correction processing mode or a feedback processing mode. In the correction processing mode, the payment features of the order data packet are extracted, and the failure features are identified from the payment features, and the failure features are eliminated, and the payment data is corrected until a valid order is generated, and sent to the user end and the hospital end for display. In the feedback processing mode, the valid order is backed up. , and sent to the user end and the hospital end for display; compared with the existing technology, it can extract payment information from the hospital information system and constitute a pending payment order sent to the user end. After the user end confirms the pending payment order, the matching degree between the pending payment order and the user end can be accurately identified, avoiding the order data that does not match the user end, and preventing the phenomenon of erroneous payment. At the same time, the payment status of the pending payment order is determined in combination with the payment data, and the accuracy and rationality of the user end payment data can be effectively identified, which can not only ensure the effective payment of the pending payment order by the user end, but also send the paid order to the hospital end in time for order processing and display, realizing efficient and accurate payment processing effect of medical order information between the user end and the hospital end, ensuring that the hospital information system can perform efficient and comprehensive processing of medical orders, and effectively improving the operation and management efficiency of the hospital information system. BRIEF DESCRIPTION OF THE DRAWINGS

[0069] Figure 1 A schematic diagram of a payment processing method for a hospital information system based on a message machine provided in the first embodiment of the present invention;

[0070] Figure 2 A schematic diagram of components of a hospital information system payment processing system based on a message machine provided in Embodiment 2 of the present invention;

[0071] Figure 3 A schematic diagram of a module of a hospital information system payment processing system based on a message machine provided in the second embodiment of the present invention;

[0072] Figure 4 A schematic diagram of a structural diagram of an electronic device provided in Embodiment 3 of the present invention;

[0073] Figure 5 A schematic diagram of the structure of a computer-readable storage medium provided in Embodiment 4 of the present invention. DETAILED DESCRIPTION

[0074] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0075] Example 1: Please refer to Figure 1 As shown, the payment processing method of a hospital information system based on a message machine described in this embodiment is applied to a cloud server, including:

[0076] S1: Filter the information to be paid from the hospital information system, and construct the information to be paid into an order to be paid based on the construction criteria;

[0077] Information to be paid refers to information that is screened from the hospital information system and can comprehensively represent the payment data of the paying user, so that it can serve as the information basis for the subsequent construction of the order to be paid and provide a basis for the generation of the order to be paid;

[0078] The information to be paid includes identity information, project information, price information and date information; identity information is used to indicate the personal identity of the paying user, project information is used to indicate the medical project information of the paying user, price information is used to indicate the fee amount of the paying user, and date information is used to indicate the payment time of the paying user; the information to be paid is obtained by querying each type of information in the hospital information system.

[0079] After obtaining the information to be paid, all the information to be paid needs to be aggregated and constructed so that the information to be paid can be used to construct an order to be paid under certain criteria. At this time, the order to be paid can be used as a complete object to be sent to the paying user. When constructing the order to be paid, the construction criteria need to be used to ensure that the information to be paid in the order to be paid can remain valid and complete.

[0080] The construction principle is: each order position contains only one piece of information to be paid; this ensures that each piece of information to be paid in the order to be paid can remain independent and stable, and prevents the overlap or intersection of two pieces of information to be paid in adjacent positions;

[0081] The construction method of the order to be paid includes:

[0082] A blank order with four information lines is selected from the order database, and the four information lines are recorded as a first information line, a second information line, a third information line and a fourth information line in order from top to bottom; the blank order is a basic template for constructing an order to be paid, so that the blank order can be used as a basic framework for constructing multiple different types of orders to be paid;

[0083] From left to right, two order positions are drawn in the first information row, the second information row, the third information row, and the fourth information row, respectively recorded as the first order position and the second order position; the order position is used to provide an import position for different types of semantics to ensure that the order to be paid can be effectively constructed;

[0084] Use natural language processing technology to identify the text and number semantics in identity information, project information, price information, and date information one by one;

[0085] The textual semantics and numerical semantics in the identity information, project information, price information and date information are respectively imported into the first order position and the second order position of the first information line, the second information line, the third information line and the fourth information line to construct an order to be paid.

[0086] S2: Send the order to be paid to the user end through the user message machine, identify the confirmation status of the order to be paid, and determine whether the order payment requirements are met;

[0087] The user message machine refers to an information processing device that can send data information in the hospital information system to the user end, and the user end is a port provided to the paying user for payment. When the order to be paid is constructed, the user message machine sends the order to be paid to the user end, so that the paying user can receive and understand the order to be paid through the user end;

[0088] When the user receives the order to be paid, it is necessary to manually verify the relevant information data in the order to be paid to ensure that there is no error or confusion in the information data in the order to be paid, so as to determine the confirmation status of the order to be paid, so that the confirmation status can indicate whether the order to be paid is confirmed by the user;

[0089] The confirmation status includes a correct status and an incorrect status; the correct status means that the information to be paid in the order to be paid has been manually confirmed by the user, and at this time, there is no error in the information to be paid in the order to be paid; the incorrect status means that the information to be paid in the order to be paid has not been manually confirmed by the user, and at this time, there is an error in the information to be paid in the order to be paid;

[0090] The identification method of the error-free state and the error state includes:

[0091] Query the confirmation events in the confirmation management system, mark the remark box of the confirmation event, and identify the remark value in the remark box; the confirmation event is used to indicate whether the user side confirms the payment order or not, the remark box is an indication of whether the confirmation event is confirmed, and the remark value is the numerical representation of the real confirmation in the remark box; the remark value includes 0 and 1;

[0092] When the remark value in the remark box is 0, it means that there is no error signal in the confirmation event. At this time, the payment information in the order to be paid has been manually confirmed by the user, and the confirmation status of the order to be paid is recorded as correct;

[0093] When the remark value in the remark box is 1, it indicates that an error signal has occurred in the confirmation event. At this time, if all the payment information in the order to be paid has not been manually confirmed by the user, the confirmation status of the order to be paid is recorded as an error status.

[0094] After obtaining the confirmation status of the order to be paid, the validity and rationality of the order to be paid can be identified according to the different confirmation statuses. Only after all the payment information on the order to be paid is manually confirmed by the user end, can it be determined that the order to be paid is valid and rational and can meet the order payment requirements;

[0095] Methods for determining whether order payment requirements are met include:

[0096] When the confirmation status of the order to be paid is in an error state, an error message appears on the order to be paid, and the order to be paid is not valid and reasonable, and it is determined that the order to be paid does not meet the order payment requirements;

[0097] When the confirmation status of the order to be paid is correct, and no error information appears on the order to be paid, the order to be paid is valid and reasonable, and it is determined that the order to be paid meets the order payment requirements.

[0098] It should be noted that only the pending orders that meet the order payment requirements can enter the subsequent payment processing operation, while the pending orders that do not meet the order payment requirements cannot enter the subsequent steps. After returning the pending order to step S1, the steps S1-S2 are repeated until the order payment requirements are met. Only then will it enter the subsequent steps, which can ensure that the pending order can be valid and reasonable in the subsequent payment processing.

[0099] S3: Obtain payment data from the user, aggregate the orders to be paid and the payment data to generate an order data packet, and send the order data packet to the cloud server through the hospital message machine;

[0100] Payment data refers to the information that the user inputs based on the payment information in the order to be paid, which can be used to pay the fees in the order to be paid, and can be used as an object to be matched and bound with the order to be paid. When the payment data is obtained, the order to be paid and the payment data are aggregated to form an order data package, so that the order data package can be used as the basis for subsequent judgment on whether to pay;

[0101] The method for generating an order data packet includes:

[0102] The payment management system queries the i operation data input by the user, and counts the operation attributes of the i operation data one by one; the operation attribute is used to indicate the specific type of the operation data, so that each operation data can be effectively distinguished to facilitate the identification and acquisition of subsequent payment data;

[0103] Identify the keywords of i operation attributes one by one through natural language processing technology, and record the operation data with the keywords of password, fingerprint and face as payment data, and obtain p payment data;

[0104] After the payment data with the same keyword are aggregated, m data sets are obtained;

[0105] Draw m data positions on the order to be paid, and import the m data sets into the m data positions one by one to generate order data packets. The data positions are used to indicate the position where the data sets are imported to ensure that each order data packet can contain the corresponding payment data.

[0106] A hospital message machine refers to an information processing device that can send relevant data information in the hospital information system to the cloud server. After obtaining an order data packet, the order data packet can be sent to the cloud server through the hospital message machine, thereby importing the orders to be paid and the payment data into the cloud server, so as to provide the cloud server with payment verification operations for the orders to be paid and the payment data.

[0107] S4: Identify the payment status of the order data packet, classify the order to be paid by order attributes according to the payment status, and select a correction processing mode or a feedback processing mode;

[0108] The payment status is used to indicate the matching degree between the order to be paid and the payment data in the order data package. When the order to be paid and the payment data match each other, the payment verification review operation is satisfied between the order to be paid and the payment data.

[0109] The payment status includes a passed status and a failed status. The passed status indicates that the order to be paid in the order data packet matches the payment data, and the order to be paid has been paid by the user. The failed status indicates that the order to be paid in the order data packet does not match the payment data, and the order to be paid has not been paid by the user.

[0110] Methods for identifying the pass status and the fail status include:

[0111] Mark the keywords of each payment data in the m data sets in the order data packet one by one;

[0112] When the keyword of the payment data is a password, the number of characters in the password in the payment data is counted and recorded as the password value, and the password value is compared with the standard password threshold for payment verification; payment verification is used to verify whether the password value is consistent with the standard password threshold. The payment status of the order data packet can be obtained, and the payment verification includes a double verification method of numerical value size and content consistency;

[0113] When the password value is consistent with the standard password threshold in terms of size and content, the payment data can achieve payment matching with the order to be paid, and the order to be paid has been correctly paid by the user, then the payment status of the order data packet is recorded as passed;

[0114] When the password value is inconsistent with the size or content of the standard password threshold, the payment data cannot achieve payment matching with the order to be paid, and the order to be paid is not correctly paid by the user, then the payment status of the order data packet is recorded as failed.

[0115] After the payment status of the order data packet is queried, it can be determined whether the order to be paid has been correctly paid by the paying user according to the different payment statuses, and the orders to be paid that have been correctly paid can be screened;

[0116] Order attributes include valid orders and invalid orders. A valid order refers to an order to be paid that has completed the review operation of payment verification, and the order to be paid has completed the correct payment operation. An invalid order refers to an order to be paid that has not completed the review operation of payment verification, and the order to be paid has not completed the correct payment operation.

[0117] When the order attributes of the pending payment orders are divided, the corresponding processing modes can be selected for the pending payment orders with different order data, thereby providing different processing methods for the pending payment orders that have passed the payment verification and those that have not passed the payment verification, and realizing the different payment processing requirements for the pending payment orders in the hospital message system;

[0118] The correction processing mode is used to perform subsequent modifications on invalid orders, ensuring that the orders to be paid can be paid again after being corrected. The feedback processing mode is used to perform subsequent feedback processing on valid orders, ensuring that the orders to be paid can be backed up by the hospital side.

[0119] Methods for selecting the correction processing mode or the completion feedback processing mode include:

[0120] When the payment status of the order data package is passed, it means that the order to be paid has completed the review of payment verification, and the order to be paid is classified as a valid order. At this time, the order to be paid does not need to be corrected later, and the feedback processing mode is selected;

[0121] When the payment status of the order data package is Failed, it means that the order to be paid has not completed the review operation of payment verification, and the order to be paid will be classified as an invalid order. At this time, the order to be paid needs to be corrected and processed later. Select the correction processing mode.

[0122] S5: in the correction processing mode, extracting the payment features of the order data packet, and identifying the failure features from the payment features;

[0123] When the correction processing mode is selected, there is a mismatch between the order to be paid and the payment data, and there is a problem with the payment data. The problem may come from the payment data itself or from external factors such as the communication network. Therefore, it is necessary to extract features that can have a negative impact on payment failure from the order data packet and record these features as payment features, so as to serve as the object of subsequent correction processing;

[0124] Payment characteristics include effective verification time, network transmission rate, and verification similarity;

[0125] The effective verification time refers to the time taken for the payment data of the order to be paid in the order data packet to be received and the payment to be completed, which can be used to indicate the input time of the payment data. The longer the effective verification time is, the longer the time taken for the payment data of the order to be paid to be received and the payment to be completed, and the lower the degree of payment matching between the order to be paid and the payment data, and the greater the probability of payment failure. The effective verification time is obtained by querying the time between the time when payment starts and the time when payment ends through the timestamp;

[0126] The network transmission rate refers to the transmission speed of the communication network when the payment data of the order to be paid in the order data packet is input, which can be used to indicate the network communication quality of the payment data. The higher the network transmission rate, the faster the transmission speed of the communication network when the payment data of the order to be paid is input, the higher the degree of payment matching between the order to be paid and the payment data, and the lower the probability of payment failure.

[0127] Methods for obtaining network transmission rate include:

[0128] Query the payment structure of payment data and the storage structure of data stored in the database through the attribute management system;

[0129] The storage data with the same storage structure and payment structure are recorded as associated data, and the number of associated data is counted;

[0130] The time when the user end imported the first associated data and the time when the hospital end received the last associated data are queried through the timestamp, and recorded as the start time and the end time respectively;

[0131] The time between the start time and the end time is recorded as the transmission time, and the amount of associated data is compared with the transmission time to obtain the network transmission rate;

[0132] The expression of network transmission rate is:

[0133] ;

[0134] In the formula, is the network transmission rate, is the number of associated data, The transmission duration.

[0135] Verification similarity refers to the degree of overlap between the payment data of the order to be paid in the order data package and the standard data during verification and review, which can indicate the accuracy of the payment data. The greater the verification similarity, the greater the degree of overlap between the payment data of the order to be paid and the standard data during verification and review, the higher the degree of payment matching between the order to be paid and the payment data, and the lower the probability of payment failure.

[0136] The methods for obtaining verification similarity include:

[0137] The payment phrases in the payment data are identified through natural language processing technology, and the payment phrases are split into independent phrase units through word segmentation technology; the payment phrase is used to concisely express the true meaning of the payment data, and the phrase unit is the smallest unit that constitutes the payment phrase and serves as the basis for subsequent calculation of similarity verification;

[0138] Compare the phrase unit with the standard unit in the database and identify the comparison status of the phrase unit; the standard unit refers to the phrase unit pre-stored in the database that can achieve the normal payment effect of the order to be paid, so as to provide a comparison basis for the current phrase unit;

[0139] The phrase units whose comparison status is an overlapping status are recorded as verification units, and the number of verification units is counted, and the number of verification units is compared with the number of phrase units to obtain verification similarity;

[0140] The expression for verifying similarity is:

[0141] ;

[0142] In the formula, To verify the similarity, is the number of verification units, is the number of phrase units.

[0143] After the payment features are obtained, each payment feature can be analyzed and judged, and the payment features that fail the analysis and judgment are recorded as failed features. At this time, the failed features can be used as negative factors that cause invalid orders, and the failed features can be used as feature objects for subsequent correction processing;

[0144] Methods for identifying failure characteristics include:

[0145] The effective verification time Verification time safety value Comparison; The verification time safety value is used to distinguish the size of the effective verification time under normal circumstances when the effective verification time is not identified as a failure feature; The verification time safety value is obtained by collecting a large number of historical maximum values ​​of the effective verification time when it is not identified as a failure feature and calculating the average value;

[0146] when Greater than , it means that the time spent on inputting the payment data of the order to be paid exceeds the maximum value of the valid verification time under normal circumstances. At this time, the valid verification time will cause the order to be paid to become an invalid order, and the valid verification time will be recorded as a failure feature;

[0147] Set the network transmission rate Transmitting security values ​​with the network Comparison; The network transmission safety value is used to distinguish the size of the network transmission rate under normal circumstances when the network transmission rate is not identified as a failure feature; The network transmission safety value is obtained by collecting a large number of historical minimum values ​​of the network transmission rate when it is not identified as a failure feature and calculating the average value;

[0148] when Less than When , it means that the data transmission rate of the payment data of the order to be paid is lower than the minimum value of the network transmission rate under normal circumstances. At this time, the network transmission rate will cause the order to be paid to become an invalid order, and the network transmission rate is recorded as a failure feature;

[0149] Will verify similarity Similar to verification safety value Comparison; the verification similarity safety value is used to verify the minimum value of the similarity under normal circumstances when it is not identified as a failure feature, which can distinguish the size of the verification similarity; the verification similarity safety value is obtained by collecting a large number of historical minimum values ​​of verification similarities when they are not identified as failure features, and then calculating their average value;

[0150] when Less than , it means that the degree of overlap between the payment data of the order to be paid and the standard data during the verification and review is less than the minimum value of the verification similarity under normal circumstances. At this time, the verification similarity will cause the order to be paid to become an invalid order, and the verification similarity will be recorded as a failure feature.

[0151] S6: Eliminate the failed features and correct the payment data until a valid order is generated and sent to the user end and the hospital end for display;

[0152] When the failure feature is identified, the failure feature is the negative factor that causes the order to be paid to be unable to be paid normally and accurately. Therefore, the payment data needs to be corrected so that the failure feature can be removed and the correct and complete payment data is re-entered to ensure that the order to be paid can be generated as a valid order;

[0153] It should be noted that there may be one or three failed features at the same time. In this case, different correction and supplementary recording measures are required for different numbers of failed features to achieve different correction processing effects.

[0154] Methods for payment data correction include:

[0155] Count the number of failed features in the payment data and record it as the failure value;

[0156] When the failure value is 1, and the failure feature is the effective verification time or verification similarity, the effective verification time or verification similarity in the payment data is removed, and the corrected effective verification time or verification similarity is re-imported through the user end;

[0157] When the failure value is 2, and the failure characteristics are the effective verification time and the verification similarity, the effective verification time and the verification similarity in the payment data are removed, and the corrected effective verification time and the verification similarity are re-imported through the user end;

[0158] When the failure value is 1 and the failure feature is the network transmission rate, the effective verification time, network transmission rate and verification similarity in the payment data are all removed, and after the communication network of the user end is changed, the corrected effective verification time, network transmission rate and verification similarity are re-imported through the user end;

[0159] When the failure value is 2 and the failure feature includes the network transmission rate, the effective verification time, network transmission rate and verification similarity in the payment data are all removed, and after the communication network of the user end is changed, the corrected effective verification time, network transmission rate and verification similarity are re-imported through the user end;

[0160] When the failure value is 3, the effective verification time, network transmission rate and verification similarity in the payment data are all removed. After changing the communication network of the user end, the corrected effective verification time, network transmission rate and verification similarity are re-imported through the user end.

[0161] The corrected payment data and the order to be paid are re-aggregated to generate an order data packet, and after the above steps S3-S4 are processed until a valid order is generated. At this time, the corrected payment data and the order to be paid can obtain an effective payment matching effect, so that the paying user can make accurate and effective payment for the order to be paid. At the same time, the generated valid order is also sent to the user end and the hospital end through the user message machine and the hospital message machine respectively for display, finally realizing the complete payment processing effect of the medical order.

[0162] S7: In the feedback processing mode, the valid orders are backed up and sent to the user end and the hospital end for display;

[0163] When the feedback processing mode is selected, there is no mismatch between the pending payment order and the payment data, and there is no problem with the payment data. At this time, the generated valid order needs to be safely backed up so that the corresponding pending payment order and payment data in the valid order can be accurately recorded to facilitate subsequent query and browsing;

[0164] Methods for effective order backup include:

[0165] Get the date and name in the identity information of the valid order to be paid, and create a backup folder;

[0166] Import the pending payment orders and payment data in the valid orders into the backup folder, and annotate the date and name as the file name of the backup folder to realize the backup of valid orders;

[0167] After the valid orders are securely backed up, the orders to be paid in the valid orders at this time have also completed the entire payment processing process, which can achieve the complete feedback effect of the valid orders. Finally, the valid orders are sent to the user end and the hospital end through the user message machine and the hospital message machine respectively for display, ultimately achieving the complete payment processing effect of the medical order.

[0168] In this embodiment, the information to be paid is screened out from the hospital information system, and based on the construction criteria, the information to be paid is constructed into an order to be paid, and the order to be paid is sent to the user end through the user message machine, the confirmation status of the order to be paid is identified, and it is determined whether the order payment requirements are met, the payment data of the user end is obtained, the order to be paid and the payment data are aggregated to generate an order data packet, and the order data packet is sent to the cloud server through the hospital message machine, the payment status of the order data packet is identified, the order to be paid is divided into order attributes according to the payment status, and the correction processing mode or the feedback processing mode is selected. In the correction processing mode, the payment features of the order data packet are extracted, and the failure features are identified from the payment features, and the failure features are eliminated. The payment data is corrected until a valid order is generated and sent to the user end and the hospital end for display. In the feedback processing mode, the valid order is Backup and send it to the user side and the hospital side for display; compared with the existing technology, it can extract payment information from the hospital information system and constitute a pending payment order sent to the user side. After the user side confirms the pending payment order, the matching degree between the pending payment order and the user side can be accurately identified, avoiding the order data that does not match the user side, and preventing the phenomenon of erroneous payment. At the same time, the payment status of the pending payment order is determined in combination with the payment data, and the accuracy and rationality of the user side payment data can be effectively identified, which can not only ensure the effective payment of the pending payment order by the user side, but also send the paid order to the hospital side in time for order processing and display, realizing efficient and accurate payment processing effect of medical order information between the user side and the hospital side, ensuring that the hospital information system can perform efficient and comprehensive processing of medical orders, and effectively improving the operation and management efficiency of the hospital information system.

[0169] Example 2: Please refer to Figure 2 and Figure 3 As shown, the part not described in detail in this embodiment is described in the first embodiment, and a hospital information system payment processing system based on a message machine is provided, which is applied to a cloud server and is used to implement a hospital information system payment processing method based on a message machine, including an order building module, a payment determination module, a data aggregation module, a mode selection module, a feature extraction module, a correction display module and a backup display module, wherein each module is connected through a wired or wireless network;

[0170] An order building module is used to filter out information to be paid from the hospital information system, the information to be paid includes identity information, project information, price information and date information, and build the information to be paid into an order to be paid based on building criteria;

[0171] The payment determination module is used to send the order to be paid to the user end through the user message machine, identify the confirmation status of the order to be paid, which includes the correct status and the incorrect status, and determine whether the order payment requirements are met;

[0172] The data aggregation module is used to obtain the payment data of the user end, aggregate the orders to be paid and the payment data to generate an order data packet, and send the order data packet to the cloud server through the hospital message machine;

[0173] A mode selection module is used to identify the payment status of the order data packet, which includes a passed status and a failed status, and classify the orders to be paid according to the payment status, which includes a valid order and an invalid order, and select a correction processing mode or a feedback processing mode;

[0174] A feature extraction module is used to extract payment features of the order data packet in the correction processing mode, the payment features including effective verification time, network transmission rate and verification similarity, and identify failure features from the payment features;

[0175] The correction and display module is used to remove failed features and correct the payment data until a valid order is generated and sent to the user end and the hospital end for display.

[0176] The backup display module is used to back up valid orders in the feedback processing mode and send them to the user end and the hospital end for display.

[0177] Example 3: Please refer to Figure 4 As shown, this embodiment discloses an electronic device, including a processor and a memory;

[0178] Wherein, the memory stores a computer program that can be called by the processor;

[0179] The processor executes the message machine-based hospital information system payment processing method by calling the computer program stored in the memory.

[0180] Since the electronic device introduced in this embodiment is an electronic device used to implement a payment processing method for a hospital information system based on a message machine in the first embodiment of this application, based on the payment processing method for a hospital information system based on a message machine introduced in the embodiment of this application, the technical personnel of this field can understand the specific implementation of the electronic device of this embodiment and its various variations, so how the electronic device implements the method in the embodiment of this application will not be described in detail here. As long as the technical personnel of this field implement the electronic device used in the payment processing method for a hospital information system based on a message machine in the embodiment of this application, it belongs to the scope of protection of this application.

[0181] Example 4: Please refer to Figure 5 As shown, this embodiment discloses a computer-readable storage medium on which a rewritable computer program is stored;

[0182] When the computer program is run, it implements the message machine-based hospital information system payment processing method.

[0183] The above description is only a specific implementation mode of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be covered by the protection scope of the present invention.

Claims

1. A payment processing method for a hospital information system based on a message machine, applied to a cloud server, characterized in that: include: S1: Filter out the information to be paid from the hospital information system, the information to be paid includes identity information, project information, price information and date information, and construct the information to be paid into an order to be paid based on the construction criteria; S2: Send the order to be paid to the user end through the user message machine, identify the confirmation status of the order to be paid, which includes the correct status and the incorrect status, and determine whether the order payment requirements are met; if the order payment requirements are met, execute S3; if the order payment requirements are not met, repeat S1-S2; S3: Obtain payment data from the user, aggregate the orders to be paid and the payment data to generate an order data packet, and send the order data packet to the cloud server through the hospital message machine; S4: Identify the payment status of the order data packet, which includes a passed status and a failed status, divide the orders to be paid into order attributes according to the payment status, which includes a valid order and an invalid order, and select a correction processing mode or a feedback processing mode; S5: In the correction processing mode, the payment features of the order data packet are extracted, the payment features include effective verification time, network transmission rate and verification similarity, and the failure features are identified from the payment features; The methods for obtaining verification similarity include: Identify payment phrases in payment data through natural language processing technology, and split payment phrases into independent phrase units through word segmentation technology; Compare the phrase unit with the standard unit in the database for coincidence, and identify the comparison status of the phrase unit; The phrase units whose comparison status is an overlapping status are recorded as verification units, and the number of verification units is counted, and the number of verification units is compared with the number of phrase units to obtain verification similarity; The expression for verifying similarity is: ； In the formula, To verify the similarity, is the number of verification units, is the number of phrase units; Methods for identifying failure characteristics include: The effective verification time Verification time safety value Compare, when Greater than When , the effective verification time is recorded as a failure feature; Set the network transmission rate Transmitting security values ​​with the network Compare, when Less than When , the network transmission rate is recorded as the failure feature; Will verify similarity Similar to verification safety value Compare, when Less than When , the verification similarity is recorded as a failure feature; S6: Eliminate the failed features and correct the payment data until a valid order is generated and sent to the user end and the hospital end for display; Methods for payment data correction include: Count the number of failed features in the payment data and record it as the failure value; When the failure value is 1, and the failure feature is the effective verification time or the verification similarity, the effective verification time or the verification similarity is removed, and the corrected effective verification time or the verification similarity is re-imported through the user end; When the failure value is 2, and the failure characteristics are the effective verification time and the verification similarity, the effective verification time and the verification similarity are removed, and the corrected effective verification time and the verification similarity are re-imported through the user end; When the failure value is 1, 2, or 3, and the failure feature includes the network transmission rate, the effective verification time, network transmission rate, and verification similarity are all removed, and after the communication network of the user end is changed, the corrected effective verification time, network transmission rate, and verification similarity are re-imported through the user end; S7: In the feedback processing mode, valid orders are backed up and sent to the user end and the hospital end for display.

2. A payment processing method for a hospital information system based on a message machine according to claim 1, characterized in that: The construction principle is: each order slot contains only one piece of information to be paid; The construction method of the order to be paid includes: Selecting blank orders with four information lines from the order database, and recording the four information lines in order from top to bottom as a first information line, a second information line, a third information line, and a fourth information line; From left to right, two order positions are drawn in the first information row, the second information row, the third information row and the fourth information row, respectively recorded as the first order position and the second order position; Use natural language processing technology to identify the text and number semantics in identity information, project information, price information, and date information one by one; The textual semantics and numerical semantics in the identity information, project information, price information and date information are respectively imported into the first order position and the second order position of the first information line, the second information line, the third information line and the fourth information line to construct an order to be paid.

3. A payment processing method for a hospital information system based on a message machine according to claim 2, characterized in that: Methods for identifying error-free states and error-indicated states include: Query the confirmation events in the confirmation management system, mark the remark box of the confirmation event, and identify the remark value in the remark box; When the remark value in the remark box is 0, the confirmation status of the order to be paid is recorded as correct; When the remark value in the remark box is 1, the confirmation status of the order to be paid is recorded as an error status; Methods for determining whether order payment requirements are met include: When the confirmation status of the order to be paid is in an error state, it is determined that the order to be paid does not meet the order payment requirements; When the confirmation status of the order to be paid is correct, it is determined that the order to be paid meets the order payment requirements.

4. A payment processing method for a hospital information system based on a message machine according to claim 3, characterized in that: The method for generating an order data packet includes: The payment management system queries the i operation data input by the user, and counts the operation attributes of the i operation data one by one; Identify the keywords of i operation attributes one by one through natural language processing technology, and record the operation data with the keywords of password, fingerprint and face as payment data, and obtain p payment data; After the payment data with the same keyword are aggregated, m data sets are obtained; Draw out m data positions on the order to be paid respectively, and import the m data sets into the m data positions one by one to generate an order data packet.

5. A payment processing method for a hospital information system based on a message machine according to claim 4, characterized in that: Methods for identifying the pass status and the fail status include: Mark the keywords of each payment data in the m data sets in the order data packet one by one; When the keyword of the payment data is a password, the number of characters in the password in the payment data is counted and recorded as the password value, and the password value is compared with the standard password threshold for payment verification; When the password value is consistent with the standard password threshold in terms of size and content, the payment status of the order data packet is recorded as passed; When the password value is inconsistent with the standard password threshold in size or content, the payment status of the order data packet is recorded as failed; Methods for selecting the correction processing mode or the completion feedback processing mode include: When the payment status of the order data packet is passed, the order to be paid is classified as a valid order, and the feedback processing mode is selected; When the payment status of the order data package is not passed, the order to be paid is classified as an invalid order and the correction processing mode is selected.

6. A payment processing method for a hospital information system based on a message machine according to claim 5, characterized in that: Methods for obtaining network transmission rate include: Query the payment structure of payment data and the storage structure of data stored in the database through the attribute management system; The storage data with the same storage structure and payment structure are recorded as associated data, and the number of associated data is counted; The time when the user end imported the first associated data and the time when the hospital end received the last associated data are queried through the timestamp, and recorded as the start time and the end time respectively; The time between the start time and the end time is recorded as the transmission time, and the amount of associated data is compared with the transmission time to obtain the network transmission rate; The expression of network transmission rate is: ； In the formula, is the network transmission rate, is the number of associated data, The transmission duration.

7. A payment processing method for a hospital information system based on a message machine according to claim 6, characterized in that: Methods for effective order backup include: Get the date and name in the identity information of the valid order to be paid, and create a backup folder; Import all pending orders and payment data in the valid orders into the backup folder, and note the date and name as the file name of the backup folder.

Images