Service system and electronic equipment

By introducing business server and front-end server into the medical insurance payment system, it is directly connected with the medical information system HIS, and the problems of cumbersome payment processes and long development cycles are solved, and rapid development and efficient medical insurance payment processes are achieved.

CN119005964APending Publication Date: 2024-11-22BEIYIN FINANCIAL TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411178539.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-26
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The traditional medical insurance payment process is cumbersome and requires multiple queues to pay. The docking between the mini program and the medical insurance service platform and the banking system has led to a large number of transformation and development work and long-term cycles.

Method used

Design a service system, including the business server and the front server, which connects the front server with the medical information system HIS to directly transmit information, reduce docking work, and improve system practicality.

Benefits of technology

It shortens the system development cycle, reduces the transformation and development work, improves the practicality of the service system, simplifies the medical insurance payment, registration, refund, payment and other processes, and improves medical efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119005964A_ABST
    Figure CN119005964A_ABST
Patent Text Reader

Abstract

The invention discloses a service system and electronic equipment, the service system comprises a business server side and a front server side, the business server side is connected with a user side, and the front server side is connected with a medical insurance platform and an HIS (Hospital Information System). Therefore, the docking between an applet and a medical insurance service platform, a bank development platform and other systems does not need to be developed any more, a large amount of transformation and development work is reduced, the system development period is shortened, and the practicability of the service system is also improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of electronic technology, and in particular to a service system and electronic equipment. Background Art

[0002] At present, in the traditional outpatient medical insurance payment process, insured persons need to queue up at the window or automatic machine to pay many times, and they also need to show their medical insurance cards when paying, which is a cumbersome process. With the application of medical insurance mobile payment platform, insured persons can make appointments, process payments, check and pay medical insurance fees online, saving waiting time.

[0003] However, the above method also needs to rely on the payment method of medical insurance card. Patients need to carry physical medical insurance cards with them. There are many payment links, and they have to wait in line every time they settle the bill, which reduces the efficiency of medical treatment.

[0004] Even if medical insurance payment is achieved by jumping to other mini-programs, it is also necessary to develop connections between these mini-programs and other systems such as the medical insurance service platform and the bank development platform, which will result in a large amount of transformation and development work and a long implementation cycle. Summary of the invention

[0005] The present application provides a service system and electronic equipment to reduce system modification and development work and shorten the system development cycle.

[0006] In a first aspect, the present application provides a service system, the service system comprising a business service end and a front-end service end, the business service end is connected to a user end, and the front-end service end is connected to a medical information system HIS, wherein:

[0007] The business service end receives the instruction to create a medical insurance payment order sent by the user end, and sends the instruction to create a medical insurance payment order to the front-end service end;

[0008] The front-end server sends the instruction to create a medical insurance payment order to the HIS, receives the payment order creation result sent by the HIS, and returns the payment order creation result to the business server;

[0009] The business service end receives the payment authorization code request returned by the user end based on the payment order creation result, and forwards the payment authorization code request to the front-end service end;

[0010] The front-end server forwards the payment authorization code to the HIS, receives the authorization code returned by the HIS, and returns the authorization code to the business server;

[0011] The business service end returns the authorization code to the user end, so that the user end makes medical insurance payment based on the authorization code.

[0012] Through the above method, information between modules can be directly transmitted through the front-end server, so there is no need to develop docking between mini-programs and medical insurance service platforms, bank development platforms and other systems, thereby reducing a lot of transformation and development work, shortening the system development cycle, and improving the practicality of the service system.

[0013] In an optional embodiment, the business service end receives the registration query request and sends the query request to the front-end service end;

[0014] The front-end service end sends the registration query request to the medical information system HIS, receives the number source list fed back by the HIS, and returns the number source list to the business service end;

[0015] The service server sends the number source list to the user terminal, receives the number lock information returned by the user terminal, and sends the number lock information to the front-end server.

[0016] The front-end server forwards the lock number information to the HIS, receives the lock number result fed back by the HIS, and forwards the lock number result to the business server;

[0017] The business service end returns the number locking result to the user end.

[0018] In an optional embodiment, the business service end receives the cancellation confirmation information and forwards the cancellation confirmation information to the front-end service end;

[0019] The front-end service end forwards the cancellation confirmation information to the HIS, receives the cancellation identification returned by the HIS, and forwards the cancellation identification to the business service end;

[0020] The service server forwards the refund identification to the user terminal, receives the refund authorization code request initiated by the user terminal, and forwards the refund authorization code request to the front-end server;

[0021] The front-end server forwards the refund authorization code request to the HIS, receives the refund authorization code returned by the HIS, and forwards the refund authorization code to the business server;

[0022] The business service end forwards the refund authorization code to the user end, so that the user end makes a refund based on the refund authorization code.

[0023] In an optional embodiment, the business service end receives a payment list query request initiated by the user end, and forwards the payment list query request to the front-end service end;

[0024] The front-end server forwards the payment list query request to the HIS, receives the payment details returned by the HIS, and forwards the payment details to the business server;

[0025] The business service end forwards the payment details to the user end, so that the user end creates a payment order based on the payment details.

[0026] In an optional embodiment, the medical insurance refund request initiated by the front-end service-side medical insurance platform is forwarded to the bank system, and the refund result of the bank system is received, and the refund result is forwarded to the HIS through the medical insurance platform;

[0027] The business service end forwards the refund result notification fed back by the HIS through the front-end service end.

[0028] In an optional embodiment, the front-end service end receives the payment completion notification from the HIS, and forwards the payment completion notification to the business service end;

[0029] The business service end updates the payment result according to the received payment completion notification.

[0030] In an optional embodiment, the business service end receives the account reconciliation request sent by the user end, and forwards the account reconciliation request to the front-end service end;

[0031] The front-end server forwards the reconciliation request to the HIS, receives the reconciliation information returned by the HIS, and forwards the reconciliation information to the business server, wherein the reconciliation information at least includes self-paid expenses and medical insurance expenses;

[0032] The business service end forwards the reconciliation information to the user end.

[0033] In an optional embodiment, the business service end receives a reconciliation confirmation message from the user end, and forwards the reconciliation confirmation message to the front-end service end;

[0034] The front-end server receives the account reconciliation confirmation message, forwards the account reconciliation confirmation message to the HIS, receives a confirmation result message from the HIS, and forwards the confirmation result message to the business server;

[0035] The business service end forwards the confirmation result message to the medical insurance platform.

[0036] In a second aspect, the present application provides an electronic device, including the above-mentioned service system.

[0037] In a third aspect, the present application provides an electronic device, which includes a memory and a processor, and the processor is used to implement the above-mentioned service system.

[0038] For each aspect from the second to the fourth aspect and the technical effects that may be achieved by each aspect, please refer to the above description of the technical effects that can be achieved by the first aspect or various possible schemes in the first aspect, and no further details will be given here. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 A schematic diagram of an application scenario of the service system provided in an embodiment of the present application;

[0040] Figure 2 A timing diagram of payment services in the service system provided in an embodiment of the present application;

[0041] Figure 3 A timing diagram of the registration service in the service system provided in the embodiment of the present application;

[0042] Figure 4 A timing diagram of the number cancellation service in the service system provided in the embodiment of the present application;

[0043] Figure 5 A timing diagram of payment services in the service system provided in an embodiment of the present application;

[0044] Figure 6 A timing diagram of the refund service in the service system provided in the embodiment of the present application;

[0045] Figure 7 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0046] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings. The specific operating methods in the method embodiments can also be applied to device embodiments or system embodiments. It should be noted that in the description of the present application, "multiple" is understood as "at least two". "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. A is connected to B, which can represent: A is directly connected to B and A is connected to B through C. In addition, in the description of the present application, words such as "first" and "second" are only used to distinguish the purpose of description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order.

[0047] The embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0048] At present, in the traditional outpatient medical insurance payment process, insured persons need to queue up at the window or automatic machine to pay many times, and they also need to show their medical insurance cards when paying, which is a cumbersome process. With the application of medical insurance mobile payment platform, insured persons can make appointments, process payments, check and pay medical insurance fees online, saving waiting time.

[0049] However, the above method also needs to rely on the payment method of medical insurance card. Patients need to carry physical medical insurance cards with them. There are many payment links, and they have to wait in line every time they settle the bill, which reduces the efficiency of medical treatment.

[0050] Even if medical insurance payment is achieved by jumping to other mini-programs, it is also necessary to develop connections between these mini-programs and other systems such as the medical insurance service platform and the bank development platform, which will result in a large amount of transformation and development work and a long implementation cycle.

[0051] In order to solve the above technical problems, the present application provides a service system, which includes a business service end and a front-end service end. The business service end is connected to the user end, and the front-end service end is connected to the HIS. The application scenarios of the service system are as follows: Figure 1 shown.

[0052] First of all, the user end can access the service system, and the business service end in the service system can receive various information sent by the user end. The front-end service end in the service system is connected to the medical insurance platform and the hospital information system (English full name: Hospital Information System, abbreviated as: HIS).

[0053] Based on the above system architecture, the business sequence diagram of the service system in the payment environment can be referred to Figure 2 As shown, the execution steps of the timing diagram are as follows:

[0054] S2.1, the user end sends a command to create a medical insurance payment order to the business server end;

[0055] First, the user can choose medical insurance payment on the user side, at which time the user side will generate a medical insurance payment order instruction, and then the user side sends a create medical insurance payment order instruction to the business service side in the service system.

[0056] S2.2, the business server receives the instruction to create a medical insurance payment order sent by the user;

[0057] S2.3, the business server sends the instruction to create a medical insurance payment order to the front-end server;

[0058] S2.4, the front-end server sends the instruction to create the medical insurance payment order to HIS;

[0059] S2.5, the front-end server receives the payment order creation result sent by HIS;

[0060] S2.6, the front-end server returns the payment order creation result to the business server;

[0061] S2.7, the business service end returns the payment order creation result to the user end;

[0062] S2.8, the business server receives the payment authorization code request returned by the user based on the payment order creation result, and forwards the payment authorization code request to the front-end server;

[0063] S2.9, the front-end server forwards the payment authorization code request to the HIS;

[0064] S2.10, the front-end server receives the authorization code returned by the HIS;

[0065] S2.11, the front-end server returns the authorization code to the business server;

[0066] S2.12, the business server returns the authorization code to the user;

[0067] S2.13, the front-end server receives the payment completion notification from HIS;

[0068] S2.14, the front-end server forwards the payment completion notification to the business server;

[0069] S2.15, the business server updates the payment result according to the payment completion notification received.

[0070] The end user makes medical insurance payment based on the authorization code sent by the business server. Through the above method, the information between modules can be directly transmitted through the front-end server, so there is no need to develop docking between mini programs and medical insurance service platforms, bank development platforms and other systems, thereby reducing a lot of transformation and development work, shortening the system development cycle, and improving the practicality of the service system.

[0071] Further, in the embodiment of the present application, the service system can also realize the registration function in the hospital system, referring to Figure 3 The following is a hospital registration sequence diagram, which includes the following steps:

[0072] S3.1, the service server receives the registration query request from the user;

[0073] S3.2, the business server sends the registration query request to the front-end server;

[0074] S3.3, the front-end server sends the registration query request to the HIS;

[0075] S3.4, the front-end server receives the number source list fed back by the HIS;

[0076] S3.5, the front-end server returns the number source list to the business server;

[0077] S3.6, the service server sends the number source list to the user terminal;

[0078] S3.7, the service server receives the number lock information sent by the user based on the number source list;

[0079] S3.8, the business server sends the lock number information to the front-end server;

[0080] S3.9, the front-end server sends the lock number information to the HIS;

[0081] S3.10, the front-end server receives the number locking result returned by the HIS;

[0082] S3.11, the front-end server forwards the number locking result to the business server;

[0083] S3.12, the business server returns the number locking result to the user.

[0084] After receiving the number lock result sent by the business end, the user end can determine whether there is a corresponding number source, and then the user can initiate payment. Figure 2 The payment process is completed by the timing shown in Figure 2 and Figure 3 The combination of the processes shown can serve as the entire registration process.

[0085] Further, in the embodiment of the present application, in addition to completing registration through the above service system, the above service system can also be used to implement cancellation processing, refer to Figure 4 As shown, Figure 4 The withdrawal sequence diagram shown in the figure specifically includes the following steps:

[0086] S4.1, the service server receives the cancellation confirmation information from the user;

[0087] S4.2, the business server forwards the cancellation confirmation information to the front-end server;

[0088] S4.3, the front-end server forwards the cancellation confirmation information to the HIS;

[0089] S4.4, the front-end server receives the withdrawal flag returned by the HIS;

[0090] S4.5, the front-end server forwards the cancellation identifier to the business server;

[0091] S4.6, the service server forwards the cancellation ID to the user;

[0092] S4.7, the business server receives the refund authorization code request initiated by the user;

[0093] S4.8, the business server forwards the refund authorization code request to the front-end server;

[0094] S4.9, the front-end server forwards the refund authorization code request to the HIS;

[0095] S4.10, the front-end server receives the refund authorization code returned by HIS;

[0096] S4.11, the front-end server forwards the refund authorization code to the business server;

[0097] S4.12, the business server forwards the refund authorization code to the user;

[0098] After receiving the refund authorization code, the user terminal forwards the refund authorization code to the medical insurance payment platform, and the medical insurance payment platform will refund according to the refund authorization code, thereby realizing the refund function after registration through the service system. This method is only completed through the front-end server, and it is impossible to redevelop the software.

[0099] Further, in the embodiment of the present application, in addition to completing registration through the above service system, payment processing can also be achieved through the above service system, referring to Figure 5 As shown, Figure 5 The payment sequence diagram shown in the figure specifically includes the following steps:

[0100] S5.1, the service server receives a payment list query request initiated by the user;

[0101] S5.2, the business server forwards the payment list query request to the front-end server;

[0102] S5.3, the front-end server forwards the payment list query request to the HIS;

[0103] S5.4, the front-end server receives the payment details returned by HIS;

[0104] S5.5, the front-end server forwards the payment details to the business server;

[0105] S5.6, the service server forwards the payment details to the user terminal;

[0106] After receiving the payment details, the user will pay according to the payment details, so that the user can create a payment order through the server. Therefore, the payment function after registration is realized through the service system. This method is only completed through the front-end server, and the software cannot be redeveloped.

[0107] It should be noted here that the payment process after creating the payment order is the same as Figure 2 The process shown is the same and will not be repeated here.

[0108] Further, in the embodiment of the present application, in addition to payment, the service system can also realize the refund process, refer to Figure 6 The figure shows the refund sequence diagram of the service system, which includes the following steps:

[0109] S6.1, HIS receives the user's refund request and sends the medical insurance refund request to the medical insurance platform;

[0110] S6.2, the medical insurance platform receives the medical insurance refund request, processes the refund according to the medical insurance refund request, and sends the medical insurance refund request to the front-end server;

[0111] S6.3, the front-end server forwards the medical insurance refund request to the bank system;

[0112] S6.4, the front-end server receives the refund result returned by the bank system;

[0113] S6.5, the front-end server forwards the refund result to HIS through the medical insurance platform;

[0114] S6.6, HIS forwards the refund result notification to the front-end server;

[0115] S6.7, the front-end server forwards the refund result notification to the business server;

[0116] S6.8, the business server updates the refund result according to the refund result notification.

[0117] Through the above method, the refund information between each module can be directly transmitted through the front-end server, so there is no need to develop docking between the mini program and the medical insurance service platform, bank development platform and other systems, thereby reducing a lot of transformation and development work, shortening the system development cycle, and improving the practicality of the service system.

[0118] Furthermore, in the embodiment of the present application, in addition to realizing the above functions, other functions can also be configured in the front-end server so that the service system can realize other functions, which will not be illustrated one by one in the embodiment of the present application.

[0119] Furthermore, in an embodiment of the present application, the business service end can also receive a reconciliation request sent by the user end, and forward the reconciliation request to the front-end server end, and then the front-end server end forwards the reconciliation request to the HIS, the front-end server end receives the reconciliation information returned by the HIS, and forwards the reconciliation information to the business service end, and the business service end finally forwards the reconciliation information to the user end. The reconciliation information includes at least self-paid expenses and medical insurance expenses. Through the reconciliation information, the user can view the specific expense information on the user end, thereby reducing the development process of other codes and improving the practicality of the service system.

[0120] For example, a patient places three orders at a hospital, with total costs of 50, 100, and -100 respectively. During payment settlement, medical insurance pays 40, 80, and -80 respectively. The medical insurance mobile payment amounts are 10, 20, and -20 respectively. The records in the order tables of each party are shown in Table 1 and Table 2:

[0121] Table 1

[0122]

[0123] Table 2

[0124]

[0125]

[0126] The hospital's HIS2024100 order generates a 50 payment order with a total payment amount of 50 and a medical insurance mobile payment amount of 10; the hospital finds the medical insurance mobile payment merchant management center order through HIS2024100, the designated medical institution serial number is HIS2024100, the order transaction amount is 10, and the transaction type is payment, the hospital payment amount is consistent with the medical insurance mobile payment transaction amount, that is, it is successful; the hospital refund order HIS2024102, the refund amount is 20, which is consistent with the transaction type refund and transaction amount 20 in the medical insurance mobile payment designated medical institution serial number HIS2024102, that is, it is successful.

[0127] In summary, the service system provided by the embodiment of the present application can directly transmit information between modules through the front-end server, so that there is no need to develop docking between mini-programs and systems such as medical insurance service platforms and bank development platforms, thereby reducing a large amount of transformation and development work, shortening the system development cycle, and improving the practicality of the service system.

[0128] Based on the same inventive concept, an electronic device is also provided in the embodiment of the present application, and the electronic device can realize the functions of the aforementioned service system, referring to Figure 7 , the electronic device comprises:

[0129] At least one processor 701, and a memory 702 connected to the at least one processor 701. The specific connection medium between the processor 701 and the memory 702 is not limited in the embodiment of the present application. Figure 7 In the example, the processor 701 and the memory 702 are connected via a bus 700. Figure 7 The connections between other components are shown in bold lines, and are not intended to be limiting. The bus 700 can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, Figure 7 Only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. Alternatively, the processor 701 can also be called a controller, and there is no limitation on the name.

[0130] In the embodiment of the present application, the memory 702 stores instructions that can be executed by at least one processor 701. The at least one processor 701 can start the service system discussed above by executing the instructions stored in the memory 702. The processor 701 can implement Figure 1 The functions of each module in the service system are shown.

[0131] Among them, the processor 701 is the control center of the device, and can use various interfaces and lines to connect the various parts of the entire control device. By running or executing instructions stored in the memory 702 and calling data stored in the memory 702, the various functions of the device and process data, the device can be monitored as a whole.

[0132] In one possible design, the processor 701 may include one or more processing units, and the processor 701 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the modem processor may not be integrated into the processor 701. In some embodiments, the processor 701 and the memory 702 may be implemented on the same chip, and in some embodiments, they may also be implemented separately on separate chips.

[0133] The processor 701 may be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The service system disclosed in conjunction with the embodiments of the present application may be directly embodied as a hardware processor for execution, or may be executed by a combination of hardware and software modules in the processor.

[0134] The memory 702 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs and modules. The memory 702 may include at least one type of storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory, a random access memory (Random Access Memory, RAM), a static random access memory (Static Random Access Memory, SRAM), a programmable read-only memory (Programmable Read Only Memory, PROM), a read-only memory (Read Only Memory, ROM), an electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), a magnetic memory, a disk, an optical disk, etc. The memory 702 is any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. The memory 702 in the embodiment of the present application can also be a circuit or any other device that can realize a storage function, for storing program instructions and / or data.

[0135] The code corresponding to the service system described in the above embodiment can be fixed into the chip by designing and programming the processor 701. How to design and program the processor 701 is a technology well known to those skilled in the art and will not be described in detail here.

[0136] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0137] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0138] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0139] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0140] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A service system, characterized in that: The service system includes a business service end and a front-end service end, wherein the business service end is connected to the user end, and the front-end service end is connected to the medical information system HIS, wherein: The business service end receives the instruction to create a medical insurance payment order sent by the user end, and sends the instruction to create a medical insurance payment order to the front-end service end; The front-end server sends the instruction to create a medical insurance payment order to the HIS, receives the payment order creation result sent by the HIS, and returns the payment order creation result to the business server; The business service end receives the payment authorization code request returned by the user end based on the payment order creation result, and forwards the payment authorization code request to the front-end service end; The front-end server forwards the payment authorization code to the HIS, receives the authorization code returned by the HIS, and returns the authorization code to the business server; The business service end returns the authorization code to the user end, so that the user end makes medical insurance payment based on the authorization code.

2. The service system according to claim 1, characterized in that: The business service end receives the registration query request and sends the query request to the front-end service end; The front-end service end sends the registration query request to the medical information system HIS, receives the number source list fed back by the HIS, and returns the number source list to the business service end; The service server sends the number source list to the user terminal, receives the number lock information returned by the user terminal, and sends the number lock information to the front-end server. The front-end server forwards the lock number information to the HIS, receives the lock number result fed back by the HIS, and forwards the lock number result to the business server; The business service end returns the number locking result to the user end.

3. The service system according to claim 1, characterized in that: The service server receives the cancellation confirmation information and forwards the cancellation confirmation information to the front-end server; The front-end service end forwards the cancellation confirmation information to the HIS, receives the cancellation identification returned by the HIS, and forwards the cancellation identification to the business service end; The service server forwards the refund identification to the user terminal, receives the refund authorization code request initiated by the user terminal, and forwards the refund authorization code request to the front-end server; The front-end server forwards the refund authorization code request to the HIS, receives the refund authorization code returned by the HIS, and forwards the refund authorization code to the business server; The business service end forwards the refund authorization code to the user end, so that the user end makes a refund based on the refund authorization code.

4. The service system according to claim 1, characterized in that: The business service end receives the payment list query request initiated by the user end, and forwards the payment list query request to the front-end service end; The front-end server forwards the payment list query request to the HIS, receives the payment details returned by the HIS, and forwards the payment details to the business server; The business service end forwards the payment details to the user end, so that the user end creates a payment order based on the payment details.

5. The service system according to claim 1, characterized in that: The medical insurance refund request initiated by the front-end service-side medical insurance platform is forwarded to the bank system, and the refund result of the bank system is received, and the refund result is forwarded to the HIS through the medical insurance platform; The business service end forwards the refund result notification fed back by the HIS through the front-end service end.

6. The service system according to claim 1, characterized in that: The front-end server receives the payment completion notification from the HIS and forwards the payment completion notification to the business server; The business service end updates the payment result according to the received payment completion notification.

7. The service system according to claim 1, characterized in that: The business service end receives the reconciliation request sent by the user end, and forwards the reconciliation request to the front-end service end; The front-end server forwards the reconciliation request to the HIS, receives the reconciliation information returned by the HIS, and forwards the reconciliation information to the business server, wherein the reconciliation information at least includes self-paid expenses and medical insurance expenses; The business service end forwards the reconciliation information to the user end.

8. The service system according to claim 1, characterized in that: The business service end receives the reconciliation confirmation message from the user end, and forwards the reconciliation confirmation message to the front-end service end; The front-end server receives the account reconciliation confirmation message, forwards the account reconciliation confirmation message to the HIS, receives a confirmation result message from the HIS, and forwards the confirmation result message to the business server; The business service end forwards the confirmation result message to the medical insurance platform.

9. An electronic device, characterized in that: A service system comprising any one of claims 1-8.

10. An electronic device, characterized in that: The electronic device comprises a memory and a processor, and the processor is used to implement the service system according to any one of claims 1-8.