Bill collection method, system, computer equipment and storage medium

Abstract

The present invention provides a bill collection method, including: obtaining basic information of a user, wherein the basic information of the user includes a target field; determining whether there is a mapping relationship between the target field and an electronic bill service provider on an electronic bill platform, if there is a mapping relationship, determining that the user is an electronic bill platform user, if there is no mapping relationship, determining that the user is a non-electronic bill platform user; when the user is an electronic bill platform user, calling the electronic bill platform to obtain a first bill collection result; when the user is a non-electronic bill platform user, calling an optical character recognition platform to obtain a second bill collection result; and sending the bill collection result to an associated terminal. The bill method, system, computer device, and computer-readable storage medium provided by the present invention can select different bill data acquisition methods according to different bill types provided by the user by setting an optical character recognition platform and an electronic bill platform, thereby improving the efficiency of bill data acquisition.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a bill collection method, system, computer equipment and storage medium. Background Art

[0002] The insurance industry is highly competitive. How to take effective measures to improve work efficiency, enhance customer satisfaction, and thus enhance core competitiveness has become the focus of major insurance companies. However, at this stage, there are a large number of medical bills that need to be manually entered to complete the filing and review of claims cases, which is very inefficient. At present, the electronicization of medical bills has not been fully implemented, and the proportion of electronic bills still depends on the payment method of the patient when visiting the doctor, resulting in a low actual proportion of electronic bills. When commercial insurance companies rely solely on electronic bills when settling claims, there may be a situation where there is no electronic bill data, resulting in low efficiency in bill acquisition. Summary of the invention

[0003] In view of this, embodiments of the present invention provide a bill collection method, system, computer device and computer-readable storage medium to solve the problem of low bill acquisition efficiency.

[0004] The embodiment of the present invention solves the above technical problems through the following technical solutions:

[0005] A bill collection method, comprising:

[0006] Obtaining basic user information, wherein the basic user information includes a target field;

[0007] Determine whether there is a mapping relationship between the target field and an electronic invoice service provider on the electronic invoice platform; if the mapping relationship exists, determine that the user is an electronic invoice platform user; if the mapping relationship does not exist, determine that the user is not an electronic invoice platform user;

[0008] When the user is an electronic bill platform user, the electronic bill platform is called, and the electronic bill platform includes multiple electronic bill service providers to obtain a first bill collection result; when the user is not an electronic bill platform user, the optical character recognition platform is called, and the optical character recognition platform includes multiple optical character recognition platform merchants to obtain a second bill collection result;

[0009] The first bill collection result or the second bill collection result is sent to an associated terminal.

[0010] Further, the determining whether there is a mapping relationship between the target field and the electronic invoice service provider on the electronic invoice platform, if the mapping relationship exists, determining that the user is an electronic invoice platform user, and if the mapping relationship does not exist, determining that the user is not an electronic invoice platform user includes:

[0011] Acquire a hospital identification code according to a target field, wherein the target field corresponds to the hospital identification code one by one;

[0012] Based on the hospital identification code, determine whether there is a mapping relationship between the hospital identification code and the electronic invoice service provider on the electronic invoice platform. If so, the user is an electronic invoice platform user, otherwise, the user is not an electronic invoice platform user.

[0013] Furthermore, before determining whether there is a mapping relationship between the hospital identification code and the electronic invoice service provider on the electronic invoice platform based on the hospital identification code, the method further includes:

[0014] The mapping relationship between the hospital identification code and the electronic invoice service provider is pre-configured and stored.

[0015] Further, when the user is an electronic bill platform user, the electronic bill platform is called, and the electronic bill platform includes multiple electronic bill service providers, and the first bill collection result is obtained including:

[0016] Obtain ticket identity information based on the user's basic information;

[0017] The bills matching the bill identity information are queried to obtain a first bill collection result.

[0018] Furthermore, if the user is not an electronic bill platform user, an optical character recognition platform is called, and the optical character recognition platform includes a plurality of optical character recognition platform merchants, and the second bill collection result is obtained including:

[0019] Receive bill photo collection instructions;

[0020] Starting the image acquisition device according to the bill photo acquisition instruction to acquire the bill photo;

[0021] The optical character recognition merchant is called to recognize the bill photo to obtain a second bill collection result.

[0022] Further, the calling of the optical character recognition platform, the optical character recognition platform including a plurality of optical character recognition platform merchants, and obtaining the second bill collection result include:

[0023] Selecting an optical character recognition merchant according to a preset rule, wherein the preset rule is used to select an optical character recognition merchant with the highest recognition accuracy according to the bill type;

[0024] The optical character recognition merchant with the highest recognition accuracy is called to recognize the bill photo to obtain a second bill collection result.

[0025] Furthermore, the method further comprises:

[0026] Comparing the information of the second bill collection result with the preset basic bill collection information;

[0027] If the information of the second bill collection result is less than the preset basic bill collection information, the information is supplemented to obtain the final bill collection result and

[0028] If the information of the second bill collection result is consistent with the preset basic bill collection information, the second bill collection result is used as the final second bill collection result;

[0029] The first bill collection result or the final second bill collection result is sent to an associated terminal.

[0030] In order to achieve the above object, an embodiment of the present invention further provides a bill collection system, comprising:

[0031] A user information acquisition module, used to acquire basic user information, wherein the basic user information includes a target field;

[0032] A user category determination module is used to determine whether there is a mapping relationship between the target field and the electronic invoice service provider on the electronic invoice platform. If the mapping relationship exists, the user is determined to be an electronic invoice platform user; if the mapping relationship does not exist, the user is determined to be a non-electronic invoice platform user;

[0033] The bill collection module is used to call the electronic bill platform when the user is an electronic bill platform user, the electronic bill platform includes multiple electronic bill platform merchants, and obtain a first bill collection result; when the user is not an electronic bill platform user, call the optical character recognition platform, the optical character recognition platform includes multiple optical character recognition platform merchants, and obtain a second bill collection result;

[0034] The bill result sending module is used to send the first bill collection result or the second bill collection result to an associated terminal.

[0035] In order to achieve the above objectives, an embodiment of the present invention also provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the above-mentioned ticket collection method when executing the computer program.

[0036] In order to achieve the above objectives, an embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored. The computer program can be executed by at least one processor so that the at least one processor performs the steps of the ticket collection method as described above.

[0037] The bill collection method, system, computer device and computer-readable storage medium provided in the embodiments of the present invention can select different bill data acquisition methods according to the information provided by the user by setting an optical character recognition platform and an electronic bill platform, thereby improving the efficiency of bill data acquisition.

[0038] The present invention is described in detail below with reference to the accompanying drawings and specific embodiments, but is not intended to limit the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 This is a flow chart of the steps of the bill collection method according to the first embodiment of the present invention;

[0040] Figure 2 A specific flow chart of an embodiment of the present invention for determining whether a mapping relationship exists between the target field and an electronic invoice service provider on an electronic invoice platform, and if so, determining that the user is an electronic invoice platform user; and if not, determining that the user is a non-electronic invoice platform user;

[0041] Figure 3 In the embodiment of the present invention, when the user is an electronic bill platform user, the electronic bill platform is called, and the electronic bill platform includes multiple electronic bill platform merchants, and a specific flow chart of obtaining a first bill collection result is provided;

[0042] Figure 4 A schematic diagram of a specific process of obtaining a second bill collection result by calling an optical character recognition platform, the optical character recognition platform including a plurality of optical character recognition platform merchants, if the user is a non-electronic bill platform user in an embodiment of the present invention;

[0043] Figure 5 A schematic diagram of a specific process of calling an optical character recognition platform according to an embodiment of the present invention, wherein the optical character recognition platform includes a plurality of optical character recognition platform merchants, and obtaining a second bill collection result;

[0044] Figure 6 A schematic diagram of a specific process of supplementing information on the first bill collection result or the second bill collection result according to an embodiment of the present invention;

[0045] Figure 7 A schematic diagram of modules for constructing a data scheduling management platform according to an embodiment of the present invention;

[0046] Figure 8 A schematic diagram of a scheduling scenario of the data scheduling management process of the present invention;

[0047] Fig. 9 This is a schematic diagram of program modules of the second embodiment of the bill collection system of the present invention;

[0048] Fig.10 Schematic diagram of the hardware structure of the third embodiment of the computer device of the present invention. DETAILED DESCRIPTION

[0049] In order to make the purpose, technical scheme and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0050] The technical solutions between the various embodiments can be combined with each other, but they must be based on the fact that they can be implemented by ordinary technicians in the field. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by the present invention.

[0051] Embodiment 1

[0052] See also Figure 1 , shows a flowchart of the steps of the bill collection method according to an embodiment of the present invention. It is understood that the flowchart in the embodiment of the method is not used to limit the order of executing the steps. The following is an exemplary description using a computer device as the execution subject, as follows:

[0053] S100: Obtaining basic user information, wherein the basic user information includes a target field;

[0054] Taking commercial insurance claims and obtaining hospital medical bills as an example, in this embodiment, the user refers to the business personnel of the commercial insurance company, and the user information is the information of the person to be compensated, including but not limited to the ID number, name, age, date of birth, hospital visited, etc. of the person to be compensated. In another embodiment, the user can also be the person to be compensated, and the user information is the person's own information, including but not limited to the person's ID number, name, age, date of birth, hospital visited, etc.

[0055] In an exemplary embodiment, step S100 further includes:

[0056] Receive the ticket collection instruction from the user end;

[0057] Generate a user information collection interface based on the ticket collection instruction;

[0058] According to the user basic information collection interface, the user basic information is obtained.

[0059] Specifically, in this embodiment, the ticket collection instruction is issued through the user terminal, and the user basic information collection interface can be a web page on the PC terminal or a page in the terminal application APP.

[0060] Taking commercial insurance claims and obtaining hospital medical treatment receipts as an example for further explanation, when a user needs to make a claim with a commercial insurance company, he or she can obtain the claim interface by triggering the claim button on the interface. The claim interface may include a basic information filling interface for the claimant and an image data uploading interface. The basic information includes but is not limited to ID number, name, age, date of birth, hospital visited, etc. The image data uploading interface includes but is not limited to medical expense receipts, medical prescriptions, examination sheets, test sheets, details of hospitalization charges, etc.

[0061] S200: Determine whether there is a mapping relationship between the target field and the electronic invoice service provider on the electronic invoice platform. If the mapping relationship exists, determine that the user is an electronic invoice platform user; if the mapping relationship does not exist, determine that the user is not an electronic invoice platform user.

[0062] In an exemplary embodiment, if Figure 2 As shown, step S200 further includes:

[0063] S201: Acquire a hospital identification code according to a target field, wherein the target field corresponds to the hospital identification code one by one;

[0064] S202: Based on the hospital identification code, determine whether there is a mapping relationship between the hospital identification code and the electronic invoice service provider on the electronic invoice platform. If so, the user is an electronic invoice platform user, otherwise, the user is not an electronic invoice platform user.

[0065] In an exemplary embodiment, before determining whether there is a mapping relationship between the hospital identification code and the electronic invoice service provider on the electronic invoice platform based on the hospital identification code, the method further includes:

[0066] The mapping relationship between the hospital identification code and the electronic invoice service provider is pre-configured and stored.

[0067] Specifically, in this embodiment, the target field of the user information is the hospital where the patient is being treated. Different hospitals match different hospital identification codes. In this embodiment, the specific hospital identification code can be pre-set in one-to-one correspondence with the hospital where the patient is being treated.

[0068] Specifically, the electronic invoice platform includes multiple electronic invoice service providers, and pre-establishes and stores the mapping relationship between the hospital identification code and multiple electronic invoice service providers, so that when the electronic invoice platform is called, the mapping relationship between the hospital identification code and multiple electronic invoice service providers is read to obtain the electronic invoice service provider corresponding to the target field. The electronic invoice service provider and the hospital identification code can be a one-to-one or many-to-one mapping relationship, that is, an electronic invoice service provider can serve one hospital or multiple hospitals at the same time. Through the visiting hospital in the basic information, it is determined whether there is an electronic invoice service provider in the claimant's visiting hospital. If there is a mapping relationship between the visiting hospital and the electronic invoice service provider, the user is an electronic invoice platform user, that is, after the visiting hospital and the electronic invoice service provider complete the code matching, it is determined that the user is an electronic invoice platform user.

[0069] In one embodiment, the electronic invoice platform connects to all electronic invoice suppliers through an interface connection method, and the interface follows the RESTful (Representational State Transfer) specification; the RESTful specification separates the front-end and back-end of the electronic invoice platform and the electronic invoice supplier, so that security issues are concentrated on the interface. Since the JSON format is accepted, injection-type security issues such as SQL injection and XSS injection vulnerabilities are prevented. SQL injection is to insert SQL commands into the query string of the Web form submission or input domain name or page request, and finally to deceive the server to execute malicious SQL commands. XSS injection vulnerabilities usually refer to exploiting the vulnerabilities left during web page development, by injecting malicious instruction codes into the web page, so that users load and execute the web page program maliciously created by the attacker. The back end is only responsible for data processing, and the front end expression can be any front end language (android, ios, html5). The front end and back end personnel are more focused on their own development, and only the interface document is needed to complete the front end and back end interaction, without too much mutual understanding of server performance optimization.

[0070] S300: When the user is an electronic invoice platform user, the electronic invoice platform is called to obtain a first invoice collection result; when the user is not an electronic invoice platform user, an optical character recognition platform is called, and the optical character recognition platform includes multiple optical character recognition platform merchants to obtain a second invoice collection result.

[0071] In an exemplary embodiment, if Figure 3 As shown, step S300 further includes:

[0072] S301A: Obtaining ticket identity information based on the user's basic information;

[0073] S302A: Query the bills matching the bill identity information to obtain the first bill collection result.

[0074] Specifically, the bill identity information refers to the ID number of the person being compensated. When the person being compensated visits a hospital, the hospital will record the basic information of the person being compensated, such as name, gender, ID number, etc. The hospital will collect the basic information of the person being compensated and all electronic receipts of the person being compensated during treatment in the hospital in the electronic bill repository corresponding to the hospital. After obtaining the ID number of the person being compensated, the ID number of the person being compensated is retrieved, and all electronic receipts of the person being compensated during treatment in the hospital are obtained to obtain the first bill collection result.

[0075] In an exemplary embodiment, if Figure 4 As shown, step S300 further includes:

[0076] S301B: Receive a bill photo collection instruction.

[0077] S302B: Start the image acquisition device according to the bill photo acquisition instruction to acquire the bill photo.

[0078] S303B: Calling the optical character recognition platform to recognize the bill photo to obtain a second bill collection result.

[0079] Specifically, the bill photo collection instruction can be issued by the user end, or it can be automatically triggered by the system when the user is determined to be a non-electronic bill platform user. This solution does not impose any restrictions on this.

[0080] Specifically, the bill photo can be collected by taking a photo through an image acquisition device, which has a camera for acquiring the bill photo.

[0081] In another embodiment, the ticket photo may also be pre-stored in the terminal device.

[0082] In an exemplary embodiment, if Figure 5 As shown, step S302B further includes:

[0083] S302B1: Select an optical character recognition merchant according to a preset rule, wherein the preset rule is used to select an optical character recognition merchant with the highest recognition accuracy according to the bill type.

[0084] When the user is classified as a non-electronic bill platform user, a recognition request is initiated to the optical character recognition platform, the optical character recognition platform includes multiple optical character recognition merchants, and the optical character recognition platform calls the optical character recognition merchants to recognize the bill photo.

[0085] In one embodiment, the optical character recognition platform is connected to all optical character recognition merchants through an interface connection method, and the interface complies with the RESTful (Representational State Transfer) specification. The RESTful specification separates the front-end and back-end of the optical character recognition platform and the optical character recognition merchant, so that security issues are concentrated on the interface. Since the JSON format is accepted, injection-type security issues such as SQL injection and XSS injection vulnerabilities are prevented. The back-end is only responsible for data processing, and the front-end expression can be any front-end language (android, ios, html5). The front-end and back-end personnel are more focused on their own development, and only the interface document is needed to complete the front-end and back-end interaction, without too much mutual understanding of server performance optimization.

[0086] S302B2: Call the optical character recognition merchant with the highest recognition accuracy to recognize the bill photo to obtain a second bill collection result.

[0087] The optical character recognition is the process of examining characters on paper or pictures, determining their shapes by detecting dark and light patterns, and then translating them into text using character recognition methods.

[0088] Specifically, the recognition process is to preprocess the bill photo, and the preprocessing steps include grayscale, noise reduction, binarization, character segmentation and normalization. The text in the bill photo is processed into a single text of the same size and color, and feature extraction and dimensionality reduction are performed on the single text. The feature extraction is used to identify the key information of the text. Each different text can be distinguished from other texts by its features. The dimensionality reduction process is suitable for when the dimension of the identified text feature is too high. In order to improve the recognition rate, the text feature is reduced in dimension, and the reduced features are classified and optimized. The classification process refers to using a classifier to classify the text features and determine the text corresponding to the text after the text feature recognition synthesis. The optimization refers to correcting the identified text according to semantics through a language model.

[0089] Furthermore, the optical character recognition platform includes multiple optical character recognition merchants, and the multiple optical character recognition merchants have different recognition accuracy for different recognition documents, such as medical expense receipts, medical prescriptions, examination forms, test forms, hospitalization charge item details and other fields.

[0090] Specifically, the preset rule is to select the optical character recognition merchant with the highest recognition accuracy according to the bill type. In one embodiment, the optical character recognition merchants on all optical character platforms are pre-ranked according to the recognition accuracy of each bill recognition type. For example, for optical character recognition of medical bills, the priority ranking of recognition accuracy is: optical character recognition merchant A>optical character recognition merchant B>optical character recognition merchant C.

[0091] Furthermore, when the optical character recognition technology merchants on the optical character platform change, the recognition priority of each optical character recognition merchant needs to be readjusted and updated. By integrating multiple optical character recognition merchants and providing more powerful and personalized service quality, commercial insurance companies can have enough options to choose the most suitable manufacturer at different stages of development.

[0092] S400: Sending the first bill collection result or the second bill collection result to an associated terminal.

[0093] In this embodiment, the associated terminal refers to a commercial insurance company.

[0094] In one embodiment, Figure 6 As shown, the method also includes:

[0095] S110: Compare the information of the second bill collection result with the preset basic bill collection information.

[0096] S111: If the information of the second bill collection result is less than the preset basic bill collection information, the information is supplemented to obtain the final bill collection result and

[0097] If the information of the second bill collection result is consistent with the preset basic bill collection information, the second bill collection result is used as the final second bill collection result.

[0098] S112: Send the first bill collection result or the final second bill collection result to an associated terminal.

[0099] Specifically, the information supplement refers to calling the information entry interface to correct or supplement the data or fields of the bill collection results that lack necessary information.

[0100] According to the bill collection result, determining whether the bill collection result lacks necessary information, and if necessary information is missing, performing intelligent entry includes:

[0101] Judging the bill collection result according to the preset basic information;

[0102] Specifically, the input field configuration information in the preset basic information is compared with the identified second bill collection result to determine which fields require additional calculation or supplementation. If the necessary information is not missing, it will be the final bill collection result. If information entry is required, the information entry interface is called to enter information for the fields that need to be calculated or supplemented to obtain the final second bill collection result.

[0103] The following describes the bill collection method of the present invention in combination with the platform construction of data scheduling management and the specific scenarios of the data scheduling management process.

[0104] like Figure 7 The construction of the data scheduling management platform is shown. The details are as follows:

[0105] OCR (Optical Character Recognition) platform construction: Specifically, in this embodiment, the OCR platform is directly integrated, as follows:

[0106] The OCR platform includes functions such as medical bill management, supplier management, service provider management, statistics management, fee settlement management, and intelligent input management. In the process of OCR construction, it relies on various components of the PAAS layer to reduce labor costs and improve development efficiency. One end of the OCR platform is connected to all OCR manufacturers through an interface connection, and the interface follows the restful specification; the other end of the OCR platform is connected to the electronic data platform through a unified interface as a unified channel, and then the electronic data service platform is connected to each commercial insurance company.

[0107] Electronic bill platform construction: Specifically, in this embodiment, the electronic bill platform is directly integrated, as follows:

[0108] The electronic invoice platform includes functions such as medical invoice management, supplier management, service provider management, statistics management, fee settlement management, and intelligent entry management. In the process of building the electronic invoice platform, we rely on various components of the PAAS (Platform as a Service) layer to reduce labor costs and improve development efficiency. One end of the electronic invoice platform is connected to all electronic invoice suppliers through an interface connection, which follows the restful specification; the other end of the electronic invoice platform is connected to the electronic data platform through a unified interface as a unified channel, and then the electronic data service platform is connected to each commercial insurance company.

[0109] Construction of electronic data service platform: Integrate the business data scheduling management of the electronic invoice platform and OCR platform, and build its own business functions.

[0110] The electronic data service platform includes functions such as hospital management, commercial insurance company management, operation management, code management, and dispatch management.

[0111] The electronic data service platform construction process relies on components at all levels of the PAAS layer to reduce labor costs and improve development efficiency. The electronic data service platform connects to external commercial insurance companies and is responsible for receiving business data related to commercial insurance companies' claims requests to the dispatch management center, which will call the electronic bill platform interface or the OCR platform interface in a unified manner, and dispatch the structured electronic data returned by the two to the commercial insurance company according to the needs of the commercial insurance company or flow into the intelligent input center for further processing, thereby completing the electronic data business processing requested by the commercial insurance company.

[0112] like Figure 8 As shown, it is based on Figure 7 The scheduling scenarios of the data scheduling management process of the data scheduling management platform are as follows:

[0113] (1) The commercial insurance company sends the claim and imaging data to the electronic data service platform. The platform determines whether there is an electronic invoice service provider in the hospital where the claimant is treated based on the basic hospital management information (i.e., whether the hospital provides electronic invoice services) and the matching management (the hospital code and the invoice supplier are matched). If there is, the scheduling management will initiate an electronic invoice query request for the patient to the electronic invoice platform, and return the electronic invoice result information to the commercial insurance company, completing the commercial insurance claim data response. If there is no electronic invoice service provider, the OCR platform will be scheduled.

[0114] (2) Receiving commercial insurance data. If the hospital does not have an electronic invoice supplier, the dispatch management will initiate an OCR recognition image information synchronization request to the OCR platform to call the OCR recognition service. The OCR platform will call different OCR suppliers based on the image information to achieve the best recognition result return. After the platform dispatch management receives the OCR recognition data, it will determine whether to perform intelligent entry based on the basic management information of the commercial insurance company. If no entry is required, the OCR recognition result will be pushed to the commercial insurance company to complete the commercial insurance claim data response; if intelligent entry is required, go to the intelligent entry business processing step.

[0115] (3) The OCR recognition results are transferred to the intelligent data entry stage. Based on the input field configuration information in the commercial insurance company's basic information (i.e., which fields require additional calculation or supplementation), the OCR recognition review and data entry are completed in the intelligent data entry module, and the final results are returned to the commercial insurance company to complete the claim data response.

[0116] The embodiment of the present invention can select different bill data acquisition methods according to different information provided by users by setting up an optical character recognition platform and an electronic bill platform, thereby improving the efficiency of bill data acquisition. In addition, according to different bill types, the most skilled optical character recognition supplier is found to provide the most accurate recognition service, thereby improving the accuracy of automatic recognition. At the same time, the electronic bill service provider and the optical character recognition supplier are managed in a unified manner, which can solve the problem of duplicate claims and improve overall work efficiency.

[0117] Embodiment 2

[0118] Please continue reading Fig. 9 , showing a schematic diagram of the program modules of the bill collection system of the present invention. In this embodiment, the bill collection system 20 may include or be divided into one or more program modules, one or more program modules are stored in a storage medium, and are executed by one or more processors to complete the present invention and implement the above-mentioned bill collection method. The program module referred to in the embodiment of the present invention refers to a series of computer program instruction segments that can complete specific functions, which is more suitable for describing the execution process of the bill collection system 20 in the storage medium than the program itself. The following description will specifically introduce the functions of each program module of this embodiment:

[0119] User information acquisition module 200: used to acquire basic user information, wherein the basic user information includes a target field;

[0120] User category determination module 202: used to determine whether there is a mapping relationship between the target field and the electronic invoice service provider on the electronic invoice platform, and if so, determine that the user is an electronic invoice platform user; if not, determine that the user is not an electronic invoice platform user;

[0121] Furthermore, the user category determination module 202 is also used for:

[0122] Acquire a hospital identification code according to a target field, wherein the target field corresponds to the hospital identification code one by one;

[0123] Based on the hospital identification code, determine whether there is a mapping relationship between the hospital identification code and the electronic invoice service provider on the electronic invoice platform. If so, the user is an electronic invoice platform user, otherwise, the user is not an electronic invoice platform user.

[0124] Furthermore, the user category determination module 202 is also used for:

[0125] The mapping relationship between the hospital identification code and the electronic invoice service provider is pre-configured and stored.

[0126] The bill collection module 204 is used to call the electronic bill platform when the user is an electronic bill platform user, and the electronic bill platform includes multiple electronic bill platform merchants to obtain a first bill collection result; when the user is not an electronic bill platform user, the optical character recognition platform is called, and the optical character recognition platform includes multiple optical character recognition platform merchants to obtain a second bill collection result.

[0127] Furthermore, the bill collection module 204 is also used for:

[0128] Obtain ticket identity information based on the user's basic information;

[0129] The bills matching the bill identity information are queried to obtain a first bill collection result.

[0130] Furthermore, the bill collection module 204 is also used for:

[0131] Receive bill photo collection instructions;

[0132] Starting the image acquisition device according to the bill photo acquisition instruction to acquire the bill photo;

[0133] The optical character recognition merchant is called to recognize the bill photo to obtain a second bill collection result.

[0134] Furthermore, the bill collection module 204 is also used for:

[0135] Selecting an optical character recognition merchant according to a preset rule, wherein the preset rule is used to select an optical character recognition merchant with the highest recognition accuracy according to the bill type;

[0136] The optical character recognition merchant with the highest recognition accuracy is called to recognize the bill photo to obtain a second bill collection result.

[0137] Furthermore, the bill collection module 204 is also used for:

[0138] Comparing the information of the second bill collection result with the preset basic bill collection information;

[0139] If the information of the second bill collection result is less than the preset basic bill collection information, the information is supplemented to obtain the final bill collection result and

[0140] If the information of the second bill collection result is consistent with the preset basic bill collection information, the second bill collection result is used as the final second bill collection result;

[0141] The first bill collection result or the final second bill collection result is sent to an associated terminal.

[0142] The bill result sending module 206 is used to send the first bill collection result or the second bill collection result to an associated terminal.

[0143] Embodiment 3

[0144] See also Fig.10 , is a schematic diagram of the hardware architecture of the computer device of the third embodiment of the present invention. In this embodiment, the computer device 2 is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions. The computer device 2 can be a rack server, a blade server, a tower server or a cabinet server (including an independent server, or a server cluster composed of multiple servers), etc. Fig.10 As shown, the computer device 2 at least includes, but is not limited to, a memory 21, a processor 22, a network interface 23, and a bill collection system 20 that can be interconnected and communicated via a system bus. Among them:

[0145] In this embodiment, the memory 21 includes at least one type of computer-readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, etc. In some embodiments, the memory 21 can be an internal storage unit of the computer device 2, such as a hard disk or memory of the computer device 2. In other embodiments, the memory 21 can also be an external storage device of the computer device 2, such as a plug-in hard disk equipped on the computer device 2, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. Of course, the memory 21 can also include both the internal storage unit of the computer device 2 and its external storage device. In this embodiment, the memory 21 is generally used to store the operating system and various application software installed on the computer device 2, such as the program code of the bill collection system 20 of the second embodiment. In addition, the memory 21 can also be used to temporarily store various types of data that have been output or are to be output.

[0146] The processor 22 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips in some embodiments. The processor 22 is generally used to control the overall operation of the computer device 2. In this embodiment, the processor 22 is used to run the program code stored in the memory 21 or process data, such as running the bill collection system 20 to implement the bill collection method of the above embodiment.

[0147] The network interface 23 may include a wireless network interface or a wired network interface, and the network interface 23 is generally used to establish a communication connection between the computer device 2 and other electronic devices. For example, the network interface 23 is used to connect the computer device 2 to an external terminal through a network, and to establish a data transmission channel and a communication connection between the computer device 2 and the external terminal. The network may be a wireless or wired network such as an Intranet, the Internet, the Global System of Mobile communication (GSM), Wideband Code Division Multiple Access (WCDMA), a 4G network, a 5G network, Bluetooth, or Wi-Fi.

[0148] It should be pointed out that Fig.10 Computer device 2 is shown only with components 20 - 23 , but it should be understood that implementation of all of the components shown is not a requirement, and more or fewer components may alternatively be implemented.

[0149] In this embodiment, the ticket collection system 20 stored in the memory 21 can also be divided into one or more program modules, and the one or more program modules are stored in the memory 21 and executed by one or more processors (processor 22 in this embodiment) to complete the present invention.

[0150] For example, Fig. 9 The program module schematic diagram of the second embodiment of the ticket collection system 20 is shown. In this embodiment, the ticket collection system 20 can be divided into a user information acquisition module 200, a user category judgment module 202, a ticket collection module 204 and a ticket result sending module 206. Among them, the program module referred to in the present invention refers to a series of computer program instruction segments that can complete specific functions, which is more suitable for describing the execution process of the ticket collection system 20 in the computer device 2 than a program. The specific functions of the program modules user information acquisition module 200-ticket result sending module 206 have been described in detail in the second embodiment and will not be repeated here.

[0151] Embodiment 4

[0152] This embodiment also provides a computer-readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory (for example, an SD or DX memory, etc.), a random access memory (RAM), a static random access memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a disk, an optical disk, a server, an App application store, etc., on which a computer program is stored, and the program realizes corresponding functions when executed by a processor. The computer-readable storage medium of this embodiment is used to store the bill collection system 20, and when executed by the processor, the bill collection method of the above embodiment is realized.

[0153] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0154] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method.

[0155] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A bill collection method, characterized in that: include: Obtaining basic user information, wherein the basic user information includes a target field; Determine whether there is a mapping relationship between the target field and an electronic invoice service provider on the electronic invoice platform; if the mapping relationship exists, determine that the user is an electronic invoice platform user; if the mapping relationship does not exist, determine that the user is not an electronic invoice platform user; When the user is an electronic bill platform user, the electronic bill platform is called, the electronic bill platform includes multiple electronic bill service providers, and a first bill collection result is obtained; When the user is not an electronic bill platform user, an optical character recognition platform is called, the optical character recognition platform includes a plurality of optical character recognition platform merchants, and a second bill collection result is obtained; sending the first bill collection result or the second bill collection result to an associated terminal; Wherein, the determining whether there is a mapping relationship between the target field and the electronic invoice service provider on the electronic invoice platform, if the mapping relationship exists, determining that the user is an electronic invoice platform user, and if the mapping relationship does not exist, determining that the user is not an electronic invoice platform user includes: Acquire a hospital identification code according to a target field, wherein the target field corresponds to the hospital identification code one by one; Based on the hospital identification code, determine whether there is a mapping relationship between the hospital identification code and the electronic invoice service provider on the electronic invoice platform, if yes, the user is an electronic invoice platform user, otherwise, the user is not an electronic invoice platform user; Wherein, before determining whether there is a mapping relationship between the hospital identification code and the electronic invoice service provider on the electronic invoice platform based on the hospital identification code, the method further includes: The mapping relationship between the hospital identification code and the electronic invoice service provider is pre-configured and stored.

2. The bill collection method according to claim 1, characterized in that: When the user is an electronic bill platform user, the electronic bill platform is called, and the electronic bill platform includes multiple electronic bill service providers. The first bill collection result obtained includes: Obtain ticket identity information based on the user's basic information; The bills matching the bill identity information are queried to obtain a first bill collection result.

3. The bill collection method according to claim 2, characterized in that: If the user is not an electronic bill platform user, an optical character recognition platform is called, and the optical character recognition platform includes multiple optical character recognition platform merchants, and the second bill collection result is obtained including: Receive bill photo collection instructions; Starting the image acquisition device according to the bill photo acquisition instruction to acquire the bill photo; The optical character recognition merchant is called to recognize the bill photo to obtain a second bill collection result.

4. The bill collection method according to claim 3, characterized in that: The calling of the optical character recognition platform, wherein the optical character recognition platform includes a plurality of optical character recognition platform merchants, and obtaining the second bill collection result includes: Selecting an optical character recognition merchant according to a preset rule, wherein the preset rule is used to select an optical character recognition merchant with the highest recognition accuracy according to the bill type; The optical character recognition merchant with the highest recognition accuracy is called to recognize the bill photo to obtain a second bill collection result.

5. The bill collection method according to claim 4, characterized in that: The method further comprises: Comparing the information of the second bill collection result with the preset basic bill collection information; If the information of the second bill collection result is less than the preset basic bill collection information, the information is supplemented to obtain the final bill collection result and If the information of the second bill collection result is consistent with the preset basic bill collection information, the second bill collection result is used as the final second bill collection result; The first bill collection result or the final second bill collection result is sent to an associated terminal.

6. A bill collection system, characterized in that: include: A user information acquisition module, used to acquire basic user information, wherein the basic user information includes a target field; The user category determination module is used to determine whether there is a mapping relationship between the target field and the electronic invoice service provider on the electronic invoice platform, and if so, determine that the user is an electronic invoice platform user; if not, determine that the user is not an electronic invoice platform user; wherein, the determination of whether there is a mapping relationship between the target field and the electronic invoice service provider on the electronic invoice platform, and if so, determine that the user is an electronic invoice platform user; if not, determine that the user is not an electronic invoice platform user includes: Acquire a hospital identification code according to a target field, wherein the target field corresponds to the hospital identification code one by one; Based on the hospital identification code, determine whether there is a mapping relationship between the hospital identification code and the electronic invoice service provider on the electronic invoice platform, if yes, the user is an electronic invoice platform user, otherwise, the user is not an electronic invoice platform user; Wherein, before judging whether there is a mapping relationship between the hospital identification code and the electronic invoice service provider on the electronic invoice platform based on the hospital identification code, the method further includes: Pre-configuring and storing the mapping relationship between the hospital identification code and the electronic invoice service provider; The bill collection module is used to call the electronic bill platform when the user is an electronic bill platform user, the electronic bill platform includes multiple electronic bill service providers, and obtain a first bill collection result; when the user is not an electronic bill platform user, call the optical character recognition platform, the optical character recognition platform includes multiple optical character recognition platform merchants, and obtain a second bill collection result; The bill result sending module is used to send the first bill collection result or the second bill collection result to an associated terminal.

7. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the bill collection method according to any one of claims 1 to 5 are implemented.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which can be executed by at least one processor so that the at least one processor executes the steps of the ticket collection method according to any one of claims 1 to 5.

Images