WO2018068490A1 - 医院自助式缴费系统及方法 - Google Patents

医院自助式缴费系统及方法 Download PDF

Info

Publication number
WO2018068490A1
WO2018068490A1 PCT/CN2017/080151 CN2017080151W WO2018068490A1 WO 2018068490 A1 WO2018068490 A1 WO 2018068490A1 CN 2017080151 W CN2017080151 W CN 2017080151W WO 2018068490 A1 WO2018068490 A1 WO 2018068490A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment
database
medical
patient
partition
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2017/080151
Other languages
English (en)
French (fr)
Inventor
张贯京
葛新科
高伟明
张红治
陈琦
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Qianhai AnyCheck Information Technology Co Ltd
Original Assignee
Shenzhen Qianhai AnyCheck Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Qianhai AnyCheck Information Technology Co Ltd filed Critical Shenzhen Qianhai AnyCheck Information Technology Co Ltd
Publication of WO2018068490A1 publication Critical patent/WO2018068490A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms

Definitions

  • the present invention relates to the field of medical information technology, and in particular, to a hospital self-service payment system and method.
  • the work intensity is high, the processing speed is slow, the payment efficiency is low, and it is easy to make mistakes, and often the staff member is not in the position to complete the payment, which results in the overall efficiency of the hospital.
  • the online medical payment system currently used due to the large user base, may cause many patients to send payment requests during the same day, which may cause the online medical payment system to be overloaded and unable to respond accurately and accurately. The medical payment due to the payment request sent is incorrect.
  • multiple payment terminal devices send different medical payment requests at the same time, it is prone to conflicts in medical payment requests, resulting in the patient and the collection of the payment list.
  • the main purpose of the present invention is to provide a hospital self-service payment system and method, which aims to solve the technical problem that the existing online medical payment system is likely to cause a request conflict and a payment error when processing multiple medical payment requests simultaneously. .
  • the present invention provides a hospital self-service payment system, which is operated in a cloud server, where the cloud server is connected to a payment database and a plurality of payment terminal devices, and the cloud server includes a database middleware.
  • the payment database is divided into a plurality of partition databases, wherein the hospital self-help
  • the payment system includes:
  • an information obtaining module configured to receive a medical payment request input by the patient from the payment terminal device, and generate a payment identification code for the medical payment request of the patient;
  • an information analysis module configured to parse the number information of the patient's medical department from the electronic medical record of the patient according to the medical payment request of the patient;
  • a partition determining module configured to determine a partition code of a partition database that is required to be accessed by the medical payment request of the patient according to the number information of the patient's medical department;
  • a data distribution module configured to add a partition code of the partition database that needs to be accessed to the medical payment request, forward the medical payment request to the database middleware, and the partition code according to the medical payment request
  • the database middleware is connected to a corresponding partition database in the payment database
  • a payment execution module configured to read medical expenses data of the patient from the connected partition database through the database middleware, execute a medical payment request according to the medical expense data, generate a medical payment list of the patient, and pay the medical payment of the patient
  • the list is sent to the patient's payment terminal device according to the payment identification code, receives the patient's payment amount from the patient's payment terminal device, and performs medical payment settlement based on the patient's medical payment list.
  • the data distribution module is further configured to obtain, from a preset database middleware, a database label and a database connection parameter corresponding to the medical payment request, and according to the database label, the database connection parameter, and the partition code,
  • the database middleware establishes a corresponding database connection with the partition database that needs to be accessed.
  • the medical payment request includes a patient name, a patient's age, a medical record number, and a contact information of the patient, and the payment identification code is a unique payment identification code generated according to the medical record number of the patient.
  • each partition database in the payment database is assigned a unique partition code, a partition code corresponds to a hospital department number, and a partition database records medical cost data of all patients in a hospital department.
  • the database middleware includes a database label of each partition database in the payment database and a database connection parameter, and a database label of each partition database corresponds to a partition code of the partition database.
  • the present invention also provides a hospital self-service payment method, which is applied to a cloud server, where the cloud server is connected to a payment database and a plurality of payment terminal devices, the cloud server includes a database middleware, and the payment database Divided into a plurality of partition databases, wherein the hospital self-service payment method comprises the following steps:
  • the hospital self-service payment method further comprises the steps of: obtaining a database label and a database connection parameter corresponding to the medical payment request from the preset database middleware; according to the database label, the database connection parameter, and the partition The code establishes a corresponding database connection between the database middleware and the partition database that needs to be accessed.
  • the medical payment request includes a patient name, a patient's age, a medical record number, and a contact information of the patient, and the payment identification code is a unique payment identification code generated according to the medical record number of the patient.
  • each partition database in the payment database is assigned a unique partition code, and a partition code corresponds to a hospital department number, and each partition database records a hospital department. The number of appointments registered in the scheduled period.
  • the database middleware includes a database label of each partition database in the payment database and a database connection parameter, and a database label of each partition database corresponds to a partition code of the partition database, and the database connection parameter is used. Establishing a database connection with the database middleware and the partition database in the payment database.
  • the hospital self-service payment system and method of the present invention adopts the above technical solution, and the technical effects are as follows:
  • the patient can be correctly treated according to the patient's medical payment request and connected to the patient
  • the corresponding partition database enables the patient's medical payment request to receive an accurate and unresponsive response, avoiding the payment error when calculating the patient's medical payment, thereby ensuring the accuracy of the patient's payment.
  • each payment terminal device can receive the medical payment list after the cloud server executes the respective medical payment request, thereby enabling each patient to understand the medical treatment.
  • the terminal equipment avoids the trouble caused by the long queue payment and saves the user's queue.
  • FIG. 1 is a schematic diagram of an application environment of a preferred embodiment of a hospital self-service payment system according to the present invention
  • FIG. 2 is a schematic diagram of functional modules of a preferred embodiment of the hospital self-service payment system of the present invention
  • FIG. 3 is a flow chart of a preferred embodiment of the hospital self-service payment method of the present invention.
  • FIG. 1 is a schematic diagram of an application environment of a preferred embodiment of a hospital self-service payment system according to the present invention.
  • the hospital self-service payment system 10 runs on the cloud server 1.
  • the cloud server 1 establishes a communication connection with a plurality of payment terminal devices 2 (illustrated by taking two as an example in Fig. 1) through the communication network 4, and connects to the payment database 3 through the database connection 5.
  • the cloud server 1 is a server in a cloud platform or a cloud platform. Through the data transmission capability and data storage capability of the cloud server 1, the payment terminal device 2 and the payment database 3 can be better processed and/or assisted.
  • the medical payment request facilitates the use of different payment terminal devices 2 by multiple users to perform medical payment request operations.
  • the payment terminal device 2 is configured to allow a user to input a medical payment request of the patient, where the medical payment request includes a patient name, a patient's age, a medical record number, and a contact information of the patient (eg, an email address, a mobile phone number, ie, ⁇ communication account) and other information.
  • the payment terminal device 2 may be a smart phone, a tablet computer, or a personal digital assistant capable of supporting the online payment function (Personal Digital
  • the billing database 3 is divided into a plurality of partition databases 30, for example, N partition databases 30, each of which is assigned a unique partition code, a partition code corresponding to the number of a hospital department, and a partition database 30.
  • Medical cost data for all patients in a hospital department was recorded.
  • a hospital contains different departments, such as internal medicine, surgery, gynaecology, pediatrics, otolaryngology, etc.
  • the medical cost data of the patient is automatically generated according to the electronic prescription of the doctor in the different hospital departments, including the prescription drug cost, the medical device usage fee, the radiology fee, the hospitalization fee, etc., and passes through the doctor terminal ( Figure 1 is not shown) transmitted and stored in the corresponding partition database 30 in the payment database 3.
  • the communication network 4 may be a wired communication network or a wireless communication network.
  • the communication network 4 is preferably a wireless communication network, including but not limited to, a GSM network, a GPRS network, a CDMA network, a TD-SCDMA network, a WiMAX network, a TD-LTE network, an FDD-LTE network, and the like. transporting network.
  • the database connection 5 can be a kind of open database connection (Open Database
  • the cloud server 1 includes, but is not limited to, a hospital self-service payment system 10, a database middleware 11, a communication unit 12, a storage unit 13, and a processing unit 14.
  • the database middleware 11 is a database access middleware (Database Access Middleware) for supporting the user's self-service payment system 10 and the payment database 3 of the cloud server 1 through the medical payment request sent by the payment terminal device 2, for example SQL middleware is a general-purpose database middleware11.
  • the database middleware 11 includes a database label of each partition database 30 in the payment database 3 and database connection parameters, and the database label of each partition database 30 corresponds to the partition code of the partition database 30.
  • the database connection parameter is used by the database middleware 11 to establish a database connection with the partition database 30 in the payment database 3.
  • the communication unit 12 is a wireless communication interface with remote wireless communication functions, for example, supporting communication technologies such as G SM, GPRS, WCDMA, CDMA, TD-SCDMA, WiMAX, TD-LTE, and FDD-LTE. Communication Interface.
  • the payment terminal device 2 performs information exchange with the cloud server 1 through the communication unit 12.
  • the storage unit 13 can be a read only memory unit ROM, an electrically erasable storage unit EEPROM, a flash memory unit FLASH or a solid hard disk.
  • the processing unit 14 may be a central processing unit (CPU), a microcontroller (MCU), a data processing chip, or an information processing unit having a data processing function.
  • FIG. 2 is a schematic diagram of functional modules of a preferred embodiment of the hospital self-service payment system of the present invention.
  • the hospital self-service payment system 10 includes, but is not limited to, an information acquisition module 101, an information analysis module 102, a partition determination module 103, a data distribution module 104, and a payment execution module 105.
  • the module referred to in the present invention refers to a series of computer program instruction segments that can be executed by the processing unit 14 of the cloud server 1 and that can perform fixed functions, which are stored in the storage unit 13 of the cloud server 1.
  • the information acquisition module 101 is configured to receive a medical payment request input by the patient from the payment terminal device 2, and generate a payment identification code for the medical payment request of the patient.
  • the medical payment request includes information such as the patient's name, the patient's age, the medical record number, and the patient's contact information (eg, email address, mobile number, instant communication account number).
  • the payment identification code is a unique patient payment identification code generated according to the patient's medical record number, and is used to identify the payment terminal device 2 for the patient to input the medical payment request, thereby
  • the patient's payment terminal device 2 is enabled to receive the medical payment list after the cloud server 1 executes the medical payment request, so that the patient knows his or her medical payment status.
  • the information parsing module 102 is configured to parse the number information of the patient's visited department from the electronic medical record of the patient according to the medical payment request of the patient. Since the patient's electronic medical record is prepared by the patient at the doctor's office and recorded by the doctor in the visiting department, the patient's electronic medical record is stored in the electronic medical record system of the server 1 (not shown in FIG. 1). Therefore, the information analysis module 102 can analyze the number information of the patient's medical department from the patient's electronic medical record based on the medical record number in the patient's medical payment request.
  • a patient may attend a different hospital department (for example, internal medicine, radiology, etc.) during the visit, so the number of the patient's medical department that the information analysis module 102 parses from the patient's electronic medical record is not limited. One, or possibly multiple, for example, the number including the medical and radiology sections of the visit.
  • a different hospital department for example, internal medicine, radiology, etc.
  • the partition determining module 103 is configured to determine a partition code of the partition database 30 that the medical payment request needs to access according to the number information of the patient's medical department.
  • the payment database 3 is divided into a plurality of partition databases 30, for example, N partition databases 30.
  • Each partition database 30 is assigned a unique partition code, one partition code corresponds to a hospital department number, and one partition database 30 records one. Medical cost data for all patients in the hospital department. Since the patient may be seen in a plurality of hospital departments, the number of the patient's visiting department may be plural, and thus the partitioning code determined by the partition determining module 103 may also have a plurality of partition codes.
  • the data distribution module 104 is configured to add the partition code of the partition database 30 to be accessed to the medical payment request, and forward the medical payment request to the database middleware 11.
  • the data distribution module 104 is further configured to connect the database middleware 11 to the corresponding partition database 30 in the partition of the payment database 3 according to the partition code of the medical payment request.
  • the data distribution module 104 connects the database middleware 11 to the corresponding partition database 30 in the partition of the payment database 3 according to the partition code of the medical payment request, and specifically includes: the data distribution module 104 from the preset database middleware 11 obtains the database label and the database connection parameter corresponding to the medical payment request, and establishes a corresponding database connection between the database middleware 11 and the partition database 30 to be accessed according to the database label, the database connection parameter and the partition code. Since each partition database 30 is assigned a unique partition code and a partition code corresponds to the number of a hospital department, it is possible to correctly distinguish the patient from the patient according to the patient's medical payment request. The department is connected to the corresponding partition database 30, so that the patient's medical payment request can be accurately and responsively avoided, and the payment error of the patient's medical payment is avoided, thereby ensuring the accuracy of the patient's payment.
  • the payment execution module 105 is configured to read the medical expense data of the patient from the connected partition database 30 through the database middleware 11, and execute the medical payment request according to the medical expense data of the patient to generate a medical payment list of the patient, and The patient's medical billing list is sent to the patient's payment terminal device 2 in accordance with the payment identification code.
  • the patient may have visited a plurality of hospital departments, and thus the total medical cost data for each of the visiting departments is required.
  • the payment execution module 105 reads the medical expenses data of the different visiting departments from the plurality of different partition databases 30, and adds the medical expenses of all the visiting departments to obtain the total The patient's total medical cost data, and a patient's medical billing list is generated based on the patient's total cost data.
  • the payment execution module 105 is further configured to receive the payment amount of the patient from the payment terminal device 2, and perform medical payment settlement based on the medical payment list of the patient. After the payment terminal device 2 receives the medical payment list, the user knows the payment amount required for the medical payment, and can pay the hospital for the patient through the WeChat payment, the Alipay payment, the bank card payment or the medical insurance card payment, thereby avoiding the payment. Due to the troubles caused by the long queues, the users are saved in the queue.
  • the payment identification code in the medical payment request can identify the payment terminal device 2 for the patient to input the medical payment request
  • the different patients send the medical payment request simultaneously at the plurality of payment terminal devices 2
  • Each payment terminal device 2 can receive the medical payment list after the cloud server 1 executes the respective medical payment request, so that each patient can know the medical payment result, and avoid multiple patient peers requesting the medical payment, causing the request conflict. The situation where the payment result is not received occurs.
  • FIG. 3 it is a flow chart of a preferred embodiment of the hospital self-service payment method of the present invention.
  • the hospital self-service payment method is applied to the cloud server 1, and as shown in Figs. 1 and 2, the hospital self-service payment method includes the following steps:
  • step S31 receiving a medical payment request input by the patient from the payment terminal device, and generating a payment identification code for the medical payment request; specifically, the information acquisition module 101 receives the medical payment request input by the patient from the payment terminal device 2, and A payment identification code is generated for the patient's medical payment request.
  • the medical payment request includes a patient name, a patient's age, a medical record number, and a patient's contact information (eg, electronic Email address, mobile number, instant messaging account, etc.
  • the payment identification code is a unique patient payment identification code generated according to the medical record number in the medical payment request, and is used to identify the payment terminal device 2 for the patient to input the medical payment request, so that the payment terminal device 2 of the patient can receive the cloud server. 1 Make a list of medical bills after the medical payment request, and let the patient know about their medical payment.
  • Step S32 parsing the number information of the patient's medical department from the medical payment request of the patient; specifically, the information analysis module 102 parses the number information of the patient's medical department from the electronic medical record of the patient according to the medical payment request of the patient. . Since the electronic medical record of the patient is prepared by the doctor at the doctor's office and the patient's medical department information is recorded, the electronic medical record of each patient is stored in the electronic medical record system of the server 1, so the information analysis module 102 The number information of the patient's visited department can be analyzed from the patient's electronic medical record based on the medical record number in the patient's medical payment request.
  • a patient may attend a different hospital department (for example, internal medicine, radiology, etc.) during the visit, so the number of the patient's medical department that the information analysis module 102 parses from the patient's electronic medical record is not limited. One, or possibly multiple, for example, the number including the medical and radiology sections of the visit.
  • a different hospital department for example, internal medicine, radiology, etc.
  • Step S33 determining, according to the number information of the patient's medical department, the partition code of the partition database in the access payment database required for the medical payment request; specifically, the partition determining module 103 determines the medical payment request according to the number information of the patient's medical department.
  • Step S34 adding the partition code of the partition database to be accessed to the medical payment request, and forwarding the medical payment request to the database middleware; specifically, the data distribution module 104 partitions the partition database 30 to be accessed.
  • the code is added to the medical payment request and forwarded to the database middleware 11 for the medical payment request.
  • Step S35 connecting the database middleware to the corresponding partition database in the payment database partition according to the partition code of the medical payment request; specifically, the data distribution module 104 connects the database middleware 11 to the payment according to the partition code of the medical payment request.
  • the step of connecting the database middleware to the corresponding partition database in the payment database partition according to the partition code of the medical payment request specifically includes the following steps: the data distribution module 104 receives the preset number The database middleware 11 obtains the database label and the database connection parameter corresponding to the medical payment request, and establishes a corresponding database connection between the database middleware 11 and the partition database 30 to be accessed according to the database label, the database connection parameter and the partition code.
  • Step S36 reading the medical expenses data of the patient from the connected partition database through the database middleware; specifically, the payment execution module 105 reads the medical treatment of the patient from the connected partition database 30 through the database middleware 11.
  • Cost data Since the patient may be seen in multiple hospital departments, the total medical cost data for each visit department is required. If the patient has visited the clinic in a plurality of different hospital departments, the payment execution module 105 reads the medical expenses data of the different visiting departments from the plurality of different partition databases 30 through the database middleware 11, and treats all the medical departments of the medical department. The sum of the costs always gives the patient's total medical cost data.
  • Step S37 Perform a medical payment request according to the medical expense data of the patient to generate a medical payment list of the patient, and send the medical payment list of the patient to the payment terminal device according to the payment identification code.
  • the payment execution module 105 generates a medical payment list of the patient according to the medical payment data of the patient, and sends the medical payment list of the patient to the payment terminal device 2 through the communication network 4 according to the payment identification code, thereby Let the patient know the amount of the payment required for the medical payment.
  • Step S38 receiving the payment amount of the patient from the payment terminal device, and performing medical payment settlement according to the medical payment list of the patient.
  • the payment execution module 105 receives the payment amount of the patient from the payment terminal device 2, and performs medical payment settlement based on the medical payment list of the patient.
  • the user knows the payment amount required for the medical payment, and can pay the hospital for the patient through the WeChat payment, the Alipay payment, the bank card payment or the medical insurance card payment, thereby avoiding the payment. Due to the troubles caused by the long queues, the users are saved in the queue.
  • each partition database 30 is assigned a unique partition code and a partition code corresponds to a hospital department number, and thus can be based on the patient's
  • the medical payment request correctly distinguishes the patient from the visiting department and connects to the corresponding partition database 30, so that the patient's medical payment request can be accurately and responsively avoided, and the payment error is prevented after calculating the patient's medical payment, thereby ensuring the patient's payment.
  • the accuracy because each partition database 30 is assigned a unique partition code and a partition code corresponds to a hospital department number, and thus can be based on the patient's
  • the medical payment request correctly distinguishes the patient from the visiting department and connects to the corresponding partition database 30, so that the patient's medical payment request can be accurately and responsively avoided, and the payment error is prevented after calculating the patient's medical payment, thereby ensuring the patient's payment.
  • the accuracy because each partition database 30 is assigned a unique partition code and a partition code corresponds to a hospital department number, and thus can be based on the patient
  • the payment identification code in the medical payment request can identify the payment terminal device 2 for the patient to input the medical payment request
  • the different patients simultaneously send the medical payment request to the plurality of payment terminal devices 2
  • each Each of the payment terminal devices 2 can receive the medical payment list after the cloud server 1 executes the respective medical payment request, so that each patient can understand the medical payment result and prevent the multiple patients from requesting the medical payment to make a request. Conflicts occur without receiving payment results.
  • the hospital self-service payment system and method of the present invention adopts the above technical solution, and the technical effects are as follows:
  • the patient can be correctly treated according to the patient's medical payment request and connected to the patient
  • the corresponding partition database enables the patient's medical payment request to receive an accurate and unresponsive response, avoiding the payment error when calculating the patient's medical payment, thereby ensuring the accuracy of the patient's payment.
  • each payment terminal device can receive the medical payment list after the cloud server executes the respective medical payment request, thereby enabling each patient to understand the medical treatment.
  • the terminal equipment avoids the trouble caused by the long queue payment and saves the user's queue.

Landscapes

  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Engineering & Computer Science (AREA)
  • Biomedical Technology (AREA)
  • Epidemiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Primary Health Care (AREA)
  • Public Health (AREA)
  • Medical Treatment And Welfare Office Work (AREA)

Abstract

一种医院自助式缴费系统及方法，该方法包括步骤：从缴费终端设备接收患者的医疗缴费请求；根据医疗缴费请求从电子病历解析出患者已就诊科室的编号；根据已就诊科室的编号确定医疗缴费请求所需访问的分区数据库的分区代码（S33）；将所述分区代码加入医疗缴费请求中，并将医疗缴费请求转发给数据库中间件（S34）；根据医疗缴费请求的分区代码将数据库中间件连接至缴费数据库中相应的分区数据库（S35）；根据所连接的分区数据库中的医疗费用数据生成患者的医疗缴费清单；从缴费终端设备接收付费金额，并根据医疗缴费清单进行医疗缴费结算（S38）。该方法在同时处理不同医疗缴费请求时能够准确地响应不同患者的医疗缴费请求，保证了医疗缴费的正确性。

Description

医院自助式缴费系统及方法 技术领域
[0001] 本发明涉及医疗信息化技术领域， 尤其涉及一种医院自助式缴费系统及方法。
背景技术
[0002] 目前， 人们对到医院看病往往涉及排队缴费的问题。 在现有技术中， 医院缴费 的方式主要为三种， 一是直接收取用户现金； 二是使用 POS系统由医院收款窗口 的工作人员帮助用户刷卡， 再由用户输入密码确认金额， 完成收款； 三是使用 医保卡付款。 以上三种缴费方式的弊端是： 一方面需要患者排队等候， 另一方 面都必须依靠医院收款窗口的工作人员来完成缴费， 如现金缴费吋需要人工清 点病人家属交来的现金， 同吋还要为交款人计算返回的零钱， 工作强度大， 处 理速度慢， 缴费效率低， 容易出错， 而且经常由于工作人员不在岗位而无法完 成缴费， 造成医院整体工作效率低下。 此外， 目前采用的网上医疗缴费系统， 由于用户群庞大， 当多个缴费终端设备在同一吋间可能很多患者发送缴费请求 ， 从而造成网上医疗缴费系统的负载过大而不能及吋准确无误响应患者发送的 缴费请求而造成的医疗缴费吋发生缴费错误。 此外， 当多个缴费终端设备同吋 发送不同的医疗缴费请求吋， 容易发生医疗缴费请求冲突而造成患者及吋收不 到缴费清单的情况。
技术问题
[0003] 本发明的主要目的在于提供一种医院自助式缴费系统及方法， 旨在解决现有网 上医疗缴费系统在同吋处理多个医疗缴费请求吋容易引起请求冲突而造成缴费 错误的技术问题。
问题的解决方案
技术解决方案
[0004] 为实现上述目的， 本发明提供了一种医院自助式缴费系统， 运行于云服务器中 ， 所述云服务器与缴费数据库以及多个缴费终端设备连接， 所述云服务器包括 数据库中间件， 所述缴费数据库划分为多个分区数据库， 其中， 所述医院自助 式缴费系统包括：
[0005] 信息获取模块， 用于从缴费终端设备接收患者输入的医疗缴费请求， 并为患者 的医疗缴费请求生成一个缴费标识码；
[0006] 信息解析模块， 用于根据患者的医疗缴费请求从患者的电子病历解析出患者已 就诊科室的编号信息；
[0007] 分区确定模块， 用于根据患者已就诊科室的编号信息确定患者的医疗缴费请求 所需访问的分区数据库的分区代码；
[0008] 数据分发模块， 用于将所需访问的分区数据库的分区代码加入医疗缴费请求中 ， 将该医疗缴费请求转发给所述数据库中间件， 以及根据所述医疗缴费请求的 分区代码将所述数据库中间件连接至所述缴费数据库中相应的分区数据库；
[0009] 缴费执行模块， 用于通过数据库中间件从所连接的分区数据库中读取患者的医 疗费用数据， 根据所述医疗费用数据执行医疗缴费请求生成患者的医疗缴费清 单， 将患者的医疗缴费清单按照缴费标识码发送至患者的缴费终端设备， 从患 者的缴费终端设备接收患者的付费金额， 以及根据患者的医疗缴费清单进行医 疗缴费结算。
[0010] 优选的， 所述数据分发模块进一步用于从预设的数据库中间件中获取与医疗缴 费请求对应的数据库标签及数据库连接参数， 并根据数据库标签、 数据库连接 参数和分区代码将所述数据库中间件与所需访问的分区数据库建立相应的数据 库连接。
[0011] 优选的， 所述医疗缴费请求包括患者姓名、 患者年齢、 病历编号及患者的联系 方式信息， 所述缴费标识码是根据患者的病历编号产生的一个唯一的缴费识别 码。
[0012] 优选的， 所述缴费数据库中的每一个分区数据库分配有唯一的分区代码， 一个 分区代码对应一个医院科室的编号， 一个分区数据库记录有一个医院科室的所 有患者的医疗费用数据。
[0013] 优选的， 所述数据库中间件包括缴费数据库中每一个分区数据库的数据库标签 以及数据库连接参数， 每一个分区数据库的数据库标签与该分区数据库的分区 代码相对应。 [0014] 本发明还提供了一种医院自助式缴费方法， 应用于云服务器中， 所述云服务器 与缴费数据库以及多个缴费终端设备连接， 所述云服务器包括数据库中间件， 所述缴费数据库划分为多个分区数据库， 其中， 所述医院自助式缴费方法包括 如下步骤：
[0015] 从缴费终端设备接收患者输入的医疗缴费请求， 并为患者的医疗缴费请求生成 一个缴费标识码；
[0016] 根据患者的医疗缴费请求从患者的电子病历解析出患者已就诊科室的编号信息
[0017] 根据患者已就诊科室的编号信息确定患者的医疗缴费请求所需访问的分区数据 库的分区代码；
[0018] 将所需访问的分区数据库的分区代码加入医疗缴费请求中， 并将该医疗缴费请 求转发给所述数据库中间件；
[0019] 根据所述医疗缴费请求的分区代码将所述数据库中间件连接至所述缴费数据库 中相应的分区数据库；
[0020] 通过数据库中间件从所连接的分区数据库中读取患者的医疗费用数据， 并根据 所述医疗费用数据执行医疗缴费请求生成患者的医疗缴费清单；
[0021] 将患者的医疗缴费清单按照缴费标识码发送至患者的缴费终端设备；
[0022] 从患者的缴费终端设备接收患者的付费金额， 并根据患者的医疗缴费清单进行 医疗缴费结算。
[0023] 优选的， 所述医院自助式缴费方法还包括步骤： 从预设的数据库中间件中获取 与医疗缴费请求对应的数据库标签及数据库连接参数； 根据所述数据库标签、 数据库连接参数和分区代码将所述数据库中间件与所需访问的分区数据库建立 相应的数据库连接。
[0024] 优选的， 所述医疗缴费请求包括患者姓名、 患者年齢、 病历编号及患者的联系 方式信息， 所述缴费标识码是根据患者的病历编号产生的一个唯一的缴费识别 码。
[0025] 优选的， 所述缴费数据库中的每一个分区数据库分配有唯一的分区代码， 一个 分区代码对应一个医院科室的编号， 每一个分区数据库记录有一个医院科室的 预定周期内的预约挂号数量。
[0026] 优选的， 所述数据库中间件包括缴费数据库中每一个分区数据库的数据库标签 以及数据库连接参数， 每一个分区数据库的数据库标签与该分区数据库的分区 代码相对应， 所述数据库连接参数用于所述数据库中间件与所述缴费数据库中 的分区数据库建立数据库连接。
发明的有益效果
有益效果
[0027] 相较于现有技术， 本发明所述医院自助式缴费系统及方法采用上述技术方案， 带来的技术效果为： 能够根据患者的医疗缴费请求正确区分出患者已就诊科室 并连接到相应的分区数据库， 从而使得患者的医疗缴费请求能够得到准确无误 的响应， 避免在计算患者的医疗缴费吋发生缴费错误， 从而保证了患者缴费的 准确性。 此外， 不同患者在多个缴费终端设备同吋发送医疗缴费请求吋， 每个 缴费终端设备都能够接收到云服务器执行各自医疗缴费请求后的医疗缴费清单 ， 从而能够让每一个患者及吋了解医疗缴费结果， 避免多个患者同吋请求医疗 缴费吋造成请求冲突而收不到缴费结果的情况发生。 多个患者可以不同的缴费 终端设备同吋进行自助式医疗缴费， 避免了因长吋间排队缴费带来的麻烦， 节 省了用户的排队吋间。
对附图的简要说明
附图说明
[0028] 图 1是本发明医院自助式缴费系统优选实施例的应用环境示意图；
[0029] 图 2是本发明医院自助式缴费系统优选实施例的功能模块示意图；
[0030] 图 3是本发明医院自助式缴费方法优选实施例的流程图；
[0031] 本发明目的的实现、 功能特点及优点将结合实施例， 参照附图做进一步说明。
实施该发明的最佳实施例
本发明的最佳实施方式
[0032] 为更进一步阐述本发明为达成预定发明目的所采取的技术手段及功效， 以下结 合附图及较佳实施例， 对本发明的具体实施方式、 结构、 特征及其功效， 详细 说明如下。 应当理解， 此处所描述的具体实施例仅仅用以解释本发明， 并不用 于限定本发明。
[0033] 参照图 1所示， 图 1是本发明医院自助式缴费系统优选实施例的应用环境示意图 。 在本实施例中， 所述医院自助式缴费系统 10运行于云服务器 1。 所述云服务器 1通过通信网络 4与多个缴费终端设备 2 (图 1中以两个为例进行说明） 建立通信 连接， 并通过数据库连接 5连接至缴费数据库 3。 所述云服务器 1是一种云平台或 云平台中的一台服务器， 通过云服务器 1的数据传输能力及数据存储能力， 可以 更好地处理及 /或协助缴费终端设备 2及缴费数据库 3的医疗缴费请求， 有利于多 个用户同吋利用不同缴费终端设备 2进行医疗缴费请求操作。
[0034] 所述缴费终端设备 2用于供用户输入患者的医疗缴费请求， 所述医疗缴费请求 包括患者姓名、 患者年齢、 病历编号以及患者的联系方式 （例如， 电子邮箱地 址、 手机号码、 即吋通信账号） 等信息。 所述缴费终端设备 2可以是能够支持网 上付费功能的智能手机、 平板电脑、 个人数字助理 （Personal Digital
Assistant, PDA) 、 个人电脑、 移动通信终端等其它任意合适的便携式电子设备 ， 也可以是设置医院的专门处理缴费的自助式终端设备。
[0035] 所述缴费数据库 3划分为多个分区数据库 30， 例如 N个分区数据库 30， 每一个分 区数据库 30分配有一个唯一的分区代码， 一个分区代码对应一个医院科室的编 号， 一个分区数据库 30记录有一个医院科室的所有患者的医疗费用数据。 一般 地， 一个医院包含有不同的科室， 例如， 内科、 外科、 妇科、 儿科、 耳鼻喉科 等。 所述患者的医疗费用数据根据不同医院科室的医生给患者看病吋所幵的电 子处方自动生成， 包括处方药品费用、 医疗器材使用费、 放射科费用、 住院费 等等， 并通过医生终端 （图 1中未画出） 传输并存储至缴费数据库 3中相应的分 区数据库 30中。
[0036] 所述通信网络 4可以是有线通信网络或无线通信网络。 在本实施例中， 所述通 信网络 4优选为无线通信网络， 包括但不限于， GSM网络、 GPRS网络、 CDMA 网络、 TD-SCDMA网络、 WiMAX网络、 TD-LTE网络、 FDD-LTE网络等无线传 输网络。 所述数据库连接 5可以为一种幵放数据库连接 （Open Database
Connectivity, ODBC) 以及 Java数据库连接 （Java Data Base Connectivity， JDBC [0037] 在本实施例中， 所述云服务器 1包括， 但不仅限于， 医院自助式缴费系统 10、 数据库中间件 11、 通信单元 12、 存储单元 13以及处理单元 14。 所述数据库中间 件 11为一种数据库访问中间件 （Database Access Middleware) ， 用于支持用户通 过缴费终端设备 2发送的医疗缴费请求访问云服务器 1的医院自助式缴费系统 10 以及缴费数据库 3， 例如 SQL中间件为一种通用的数据库中间件 11。 在本实施例 中， 所述数据库中间件 11包括缴费数据库 3中每一个分区数据库 30的数据库标签 以及数据库连接参数， 每一个分区数据库 30的数据库标签与该分区数据库 30的 分区代码相对应。 所述数据库连接参数用于所述数据库中间件 11与缴费数据库 3 中的分区数据库 30建立数据库连接。
[0038] 所述通信单元 12为一种具有远程无线通讯功能的无线通讯接口， 例如， 支持 G SM、 GPRS、 WCDMA、 CDMA、 TD-SCDMA、 WiMAX、 TD-LTE、 FDD-LTE 等通讯技术的通讯接口。 在本实例中， 所述缴费终端设备 2通过通信单元 12与云 服务器 1进行信息交互。 所述存储单元 13可以为一种只读存储单元 ROM, 电可擦 写存储单元 EEPROM、 快闪存储单元 FLASH或固体硬盘等。 所述的处理单元 14 可以为一种中央处理器 (Central Processing Unit, CPU) 、 微控制器 （MCU) 、 数据处理芯片、 或者具有数据处理功能的信息处理单元。
[0039] 参照图 2所示， 图 2是本发明医院自助式缴费系统的优选实施例的功能模块示意 图。 在本实施例中， 所述医院自助式缴费系统 10包括， 但不局限于， 信息获取 模块 101、 信息解析模块 102、 分区确定模块 103、 数据分发模块 104及缴费执行 模块 105。 本发明所称的模块是指一种能够被所述云服务器 1的处理单元 14执行 并且能够完成固定功能的一系列计算机程序指令段， 其存储在所述云服务器 1的 存储单元 13中。
[0040] 所述信息获取模块 101用于从缴费终端设备 2接收患者输入的医疗缴费请求， 并 为患者的医疗缴费请求生成一个缴费标识码。 所述医疗缴费请求包括患者姓名 、 患者年齢、 病历编号及患者的联系方式 （例如， 电子邮箱地址、 手机号码、 即吋通信账号） 等信息。 所述缴费标识码是根据患者的病历编号产生的一个唯 一的患者缴费识别码， 用于识别患者输入医疗缴费请求的缴费终端设备 2， 从而 使得患者的缴费终端设备 2能够接收到云服务器 1执行医疗缴费请求后的医疗缴 费清单， 让患者了解自己的医疗缴费情况。
[0041] 所述信息解析模块 102用于根据患者的医疗缴费请求从患者的电子病历解析出 患者已就诊科室的编号信息。 由于患者的电子病历是由患者在就诊吋由就诊科 室的医生幵具并记录有患者的已就诊科室信息， 每一个患者的电子病历均存储 在服务器 1的电子病历系统 （图 1未画出） 中， 因此信息解析模块 102根据患者的 医疗缴费请求中的病历编号就可从患者的电子病历中解析出患者已就诊科室的 编号信息。 在本实施例中， 一个患者在就诊过程中可能会同吋到不同医院科室 (例如内科、 放射科等） 就诊， 因此信息解析模块 102从患者的电子病历解析出 的患者已就诊科室的编号不仅限于一个， 也可能为多个， 例如， 同吋包括就诊 的内科和放射科的编号。
[0042] 所述分区确定模块 103用于根据患者已就诊科室的编号信息确定该医疗缴费请 求所需访问的分区数据库 30的分区代码。 所述缴费数据库 3划分为多个分区数据 库 30， 例如 N个分区数据库 30， 每一个分区数据库 30分配有一个唯一的分区代码 ， 一个分区代码对应一个医院科室的编号， 一个分区数据库 30记录有一个医院 科室的所有患者的医疗费用数据。 由于患者可能在多个医院科室进行就诊， 则 患者已就诊科室的编号可能为多个， 因此分区确定模块 103确定出的分区数据库 30的分区代码也可能为多个。
[0043] 所述数据分发模块 104用于将所需访问的分区数据库 30的分区代码加入医疗缴 费请求中， 并将该医疗缴费请求转发给数据库中间件 11。 所述数据分发模块 104 还用于根据医疗缴费请求的分区代码将数据库中间件 11连接至缴费数据库 3分区 中相应的分区数据库 30。 在本实施例中， 所述数据分发模块 104根据医疗缴费请 求的分区代码将数据库中间件 11连接至缴费数据库 3分区中相应的分区数据库 30 具体包括： 数据分发模块 104从预设的数据库中间件 11中获取与医疗缴费请求对 应的数据库标签及数据库连接参数， 并根据数据库标签、 数据库连接参数和分 区代码将数据库中间件 11与所需访问的分区数据库 30建立相应的数据库连接。 由于每一个分区数据库 30分配有一个唯一的分区代码以及一个分区代码对应一 个医院科室的编号， 因此能够根据患者的医疗缴费请求正确区分出患者已就诊 科室并连接到相应的分区数据库 30， 从而使得患者的医疗缴费请求能够得到准 确无误的响应， 避免在计算患者的医疗缴费吋发生缴费错误， 从而保证了患者 缴费的准确性。
[0044] 所述缴费执行模块 105用于通过数据库中间件 11从所连接的分区数据库 30中读 取患者的医疗费用数据， 根据患者的医疗费用数据执行医疗缴费请求生成患者 的医疗缴费清单， 并将患者的医疗缴费清单按照缴费标识码发送至患者的缴费 终端设备 2。 在本实施例中， 患者可能在多个医院科室进行了就诊， 因此需要每 一个就诊科室的医疗总费用数据。 如果患者在多个不同的医院科室进行了就诊 ， 则缴费执行模块 105从多个不同的分区数据库 30中读取不同的就诊科室的医疗 费用数据， 将所有就诊科室的医疗费用相加总得到该患者的医疗总费用数据， 并根据患者的总费用数据生成患者的医疗缴费清单。 缴费执行模块 105还用于从 缴费终端设备 2接收患者的付费金额， 并根据患者的医疗缴费清单进行医疗缴费 结算。 当缴费终端设备 2接收到医疗缴费清单后， 用户清楚医疗缴费所需的付费 金额， 可以通过微信支付、 支付宝支付、 银行卡支付或医保卡支付的方式向医 院为患者就诊进行缴费， 从而避免了因长吋间排队缴费带来的麻烦， 节省了用 户排队等待吋间。
[0045] 在本实施例中， 由于医疗缴费请求中的缴费标识码可以识别出患者输入医疗缴 费请求的缴费终端设备 2， 因此不同患者在多个缴费终端设备 2同吋发送医疗缴 费请求吋， 每个缴费终端设备 2都能够接收到云服务器 1执行各自医疗缴费请求 后的医疗缴费清单， 从而能够让每一个患者及吋了解医疗缴费结果， 避免多个 患者同吋请求医疗缴费吋造成请求冲突而收不到缴费结果的情况发生。
[0046] 参照图 3所示， 是本发明医院自助式缴费方法的优选实施例的流程图。 在本实 施例中， 所述医院自助式缴费方法应用于云服务器 1， 一并参考图 1和 2所示， 所 述医院自助式缴费方法包括以下步骤：
[0047] 步骤 S31， 从缴费终端设备接收患者输入的医疗缴费请求， 并为医疗缴费请求 生成一个缴费标识码； 具体地， 信息获取模块 101从缴费终端设备 2接收患者输 入的医疗缴费请求， 并为患者的医疗缴费请求生成一个缴费标识码。 所述医疗 缴费请求包括患者姓名、 患者年齢、 病历编号及患者的联系方式 （例如， 电子 邮箱地址、 手机号码、 即吋通信账号） 等信息。 所述缴费标识码是根据医疗缴 费请求中的病历编号产生的唯一的患者缴费识别码， 用于识别患者输入医疗缴 费请求的缴费终端设备 2， 从而使得患者的缴费终端设备 2能够接收到云服务器 1 执行医疗缴费请求后的医疗缴费清单， 让患者了解自己的医疗缴费情况。
[0048] 步骤 S32， 从患者的医疗缴费请求中解析出患者已就诊科室的编号信息； 具体 地， 信息解析模块 102根据患者的医疗缴费请求从患者的电子病历解析出患者已 就诊科室的编号信息。 由于患者的电子病历是由患者在就诊吋由就诊科室的医 生幵具并记录有患者的已就诊科室信息， 每一个患者的电子病历均存储在服务 器 1的电子病历系统中， 因此信息解析模块 102根据患者的医疗缴费请求中的病 历编号就可从患者的电子病历中解析出患者已就诊科室的编号信息。 在本实施 例中， 一个患者在就诊过程中可能会同吋到不同医院科室 （例如内科、 放射科 等） 就诊， 因此信息解析模块 102从患者的电子病历解析出的患者已就诊科室的 编号不仅限于一个， 也可能为多个， 例如， 同吋包括就诊的内科和放射科的编 号。
[0049] 步骤 S33， 根据患者已就诊科室的编号信息确定医疗缴费请求所需访问缴费数 据库中分区数据库的分区代码； 具体地， 分区确定模块 103根据患者已就诊科室 的编号信息确定该医疗缴费请求所需访问的分区数据库 30的分区代码。 由于患 者可能在多个医院科室进行就诊， 则患者已就诊科室的编号可能为多个， 因此 分区确定模块 103确定出的分区数据库 30的分区代码也可能为多个。
[0050] 步骤 S34， 将所需访问的分区数据库的分区代码加入医疗缴费请求中， 并将医 疗缴费请求转发给数据库中间件； 具体地， 数据分发模块 104将所需访问的分区 数据库 30的分区代码加入医疗缴费请求中， 并将该医疗缴费请求转发给数据库 中间件 11。
[0051] 步骤 S35， 根据医疗缴费请求的分区代码将数据库中间件连接至缴费数据库分 区中相应的分区数据库； 具体地， 数据分发模块 104根据医疗缴费请求的分区代 码将数据库中间件 11连接至缴费数据库 3分区中相应的分区数据库 30。 在本实施 例中， 所述根据医疗缴费请求的分区代码将数据库中间件连接至缴费数据库分 区中相应的分区数据库的步骤具体包括如下步骤： 数据分发模块 104从预设的数 据库中间件 11中获取与医疗缴费请求对应的数据库标签及数据库连接参数， 并 根据数据库标签、 数据库连接参数和分区代码将数据库中间件 11与所需访问的 分区数据库 30建立相应的数据库连接。
[0052] 步骤 S36， 通过数据库中间件从所连接的分区数据库中读取患者的医疗费用数 据； 具体地， 缴费执行模块 105通过数据库中间件 11从所连接的分区数据库 30中 读取患者的医疗费用数据。 由于患者可能在多个医院科室进行了就诊， 因此需 要每一个就诊科室的医疗总费用数据。 如果患者在多个不同的医院科室进行了 就诊， 则缴费执行模块 105通过数据库中间件 11从多个不同的分区数据库 30中读 取不同的就诊科室的医疗费用数据， 并将所有就诊科室的医疗费用相加总得到 该患者的医疗总费用数据。
[0053] 步骤 S37， 根据患者的医疗费用数据执行医疗缴费请求生成患者的医疗缴费清 单， 并将患者的医疗缴费清单按照缴费标识码发送至缴费终端设备。 在本实施 例中， 缴费执行模块 105根据患者的医疗费用数据执行医疗缴费请求生成患者的 医疗缴费清单， 并将患者的医疗缴费清单按照缴费标识码通过通信网络 4发送至 缴费终端设备 2， 从而让患者清楚医疗缴费所需的付费金额。
[0054] 步骤 S38， 从缴费终端设备接收患者的付费金额， 并根据患者的医疗缴费清单 进行医疗缴费结算。 具体地， 缴费执行模块 105从缴费终端设备 2接收患者的付 费金额， 并根据患者的医疗缴费清单进行医疗缴费结算。 当缴费终端设备 2接收 到医疗缴费清单后， 用户清楚医疗缴费所需的付费金额， 可以通过微信支付、 支付宝支付、 银行卡支付或医保卡支付的方式向医院为患者就诊进行缴费， 从 而避免了因长吋间排队缴费带来的麻烦， 节省了用户排队等待吋间。
[0055] 在本实施例中， 本发明所述医院自助式缴费系统及方法， 由于每一个分区数据 库 30分配有一个唯一的分区代码以及一个分区代码对应一个医院科室的编号， 因此能够根据患者的医疗缴费请求正确区分出患者已就诊科室并连接到相应的 分区数据库 30， 从而使得患者的医疗缴费请求能够得到准确无误的响应， 避免 在计算患者的医疗缴费吋发生缴费错误， 从而保证了患者缴费的准确性。 此外 ， 由于医疗缴费请求中的缴费标识码可以识别出患者输入医疗缴费请求的缴费 终端设备 2， 因此不同患者在多个缴费终端设备 2同吋发送医疗缴费请求吋， 每 个缴费终端设备 2都能够接收到云服务器 1执行各自医疗缴费请求后的医疗缴费 清单， 从而能够让每一个患者都能及吋了解医疗缴费结果， 避免多个患者同吋 请求医疗缴费吋造成请求冲突而收不到缴费结果的情况发生。
[0056] 以上仅为本发明的优选实施例， 并非因此限制本发明的专利范围， 凡是利用本 发明说明书及附图内容所作的等效结构或等效流程变换， 或直接或间接运用在 其他相关的技术领域， 均同理包括在本发明的专利保护范围内。
工业实用性
[0057] 相较于现有技术， 本发明所述医院自助式缴费系统及方法采用上述技术方案， 带来的技术效果为： 能够根据患者的医疗缴费请求正确区分出患者已就诊科室 并连接到相应的分区数据库， 从而使得患者的医疗缴费请求能够得到准确无误 的响应， 避免在计算患者的医疗缴费吋发生缴费错误， 从而保证了患者缴费的 准确性。 此外， 不同患者在多个缴费终端设备同吋发送医疗缴费请求吋， 每个 缴费终端设备都能够接收到云服务器执行各自医疗缴费请求后的医疗缴费清单 ， 从而能够让每一个患者及吋了解医疗缴费结果， 避免多个患者同吋请求医疗 缴费吋造成请求冲突而收不到缴费结果的情况发生。 多个患者可以不同的缴费 终端设备同吋进行自助式医疗缴费， 避免了因长吋间排队缴费带来的麻烦， 节 省了用户的排队吋间。

Claims

权利要求书
[权利要求 1] 一种医院自助式缴费系统， 运行于云服务器中， 所述云服务器与缴费 数据库以及多个缴费终端设备连接， 其特征在于， 所述云服务器包括 数据库中间件， 所述缴费数据库划分为多个分区数据库， 其中， 所述 医院自助式缴费系统包括： 信息获取模块， 用于从缴费终端设备接收 患者输入的医疗缴费请求， 并为患者的医疗缴费请求生成一个缴费标 识码； 信息解析模块， 用于根据患者的医疗缴费请求从患者的电子病 历解析出患者已就诊科室的编号信息； 分区确定模块， 用于根据患者 已就诊科室的编号信息确定患者的医疗缴费请求所需访问的分区数据 库的分区代码； 数据分发模块， 用于将所需访问的分区数据库的分区 代码加入医疗缴费请求中， 将该医疗缴费请求转发给所述数据库中间 件， 以及根据所述医疗缴费请求的分区代码将所述数据库中间件连接 至所述缴费数据库中相应的分区数据库； 缴费执行模块， 用于通过数 据库中间件从所连接的分区数据库中读取患者的医疗费用数据， 根据 所述医疗费用数据执行医疗缴费请求生成患者的医疗缴费清单， 将患 者的医疗缴费清单按照缴费标识码发送至患者的缴费终端设备， 从患 者的缴费终端设备接收患者的付费金额， 以及根据患者的医疗缴费清 单进行医疗缴费结算。
[权利要求 2] 如权利要求 1所述的医院自助式缴费系统， 其特征在于， 所述数据分 发模块进一步用于从预设的数据库中间件中获取与医疗缴费请求对应 的数据库标签及数据库连接参数， 并根据数据库标签、 数据库连接参 数和分区代码将所述数据库中间件与所需访问的分区数据库建立相应 的数据库连接。
[权利要求 3] 如权利要求 1所述的医院自助式缴费系统， 其特征在于， 所述医疗缴 费请求包括患者姓名、 患者年齢、 病历编号及患者的联系方式信息， 所述缴费标识码是根据患者的病历编号产生的一个唯一的缴费识别码
[权利要求 4] 如权利要求 1所述的医院自助式缴费系统， 其特征在于， 所述缴费数 据库中的每一个分区数据库分配有唯一的分区代码， 一个分区代码对 应一个医院科室的编号， 一个分区数据库记录有一个医院科室的所有 患者的医疗费用数据。
如权利要求 1至 4任一项所述的医院自助式缴费系统， 其特征在于， 所 述数据库中间件包括缴费数据库中每一个分区数据库的数据库标签以 及数据库连接参数， 每一个分区数据库的数据库标签与该分区数据库 的分区代码相对应。
一种医院自助式缴费方法， 应用于云服务器中， 所述云服务器与缴费 数据库以及多个缴费终端设备连接， 其特征在于， 所述云服务器包括 数据库中间件， 所述缴费数据库划分为多个分区数据库， 其中， 所述 医院自助式缴费方法包括如下步骤： 从缴费终端设备接收患者输入的 医疗缴费请求， 并为患者的医疗缴费请求生成一个缴费标识码； 根据 患者的医疗缴费请求从患者的电子病历解析出患者已就诊科室的编号 信息； 根据患者已就诊科室的编号信息确定患者的医疗缴费请求所需 访问的分区数据库的分区代码； 将所需访问的分区数据库的分区代码 加入医疗缴费请求中， 并将该医疗缴费请求转发给所述数据库中间件 ； 根据所述医疗缴费请求的分区代码将所述数据库中间件连接至所述 缴费数据库中相应的分区数据库； 通过数据库中间件从所连接的分区 数据库中读取患者的医疗费用数据， 并根据所述医疗费用数据执行医 疗缴费请求生成患者的医疗缴费清单； 将患者的医疗缴费清单按照缴 费标识码发送至患者的缴费终端设备； 从患者的缴费终端设备接收患 者的付费金额， 并根据患者的医疗缴费清单进行医疗缴费结算。 如权利要求 6所述的医院自助式缴费方法， 其特征在于， 所述医院自 助式缴费方法还包括步骤： 从预设的数据库中间件中获取与医疗缴费 请求对应的数据库标签及数据库连接参数； 根据所述数据库标签、 数 据库连接参数和分区代码将所述数据库中间件与所需访问的分区数据 库建立相应的数据库连接。
如权利要求 6所述的医院自助式缴费方法， 其特征在于， 所述医疗缴 费请求包括患者姓名、 患者年齢、 病历编号及患者的联系方式信息， 所述缴费标识码是根据患者的病历编号产生的一个唯一的缴费识别码
[权利要求 9] 如权利要求 6所述的医院自助式缴费方法， 其特征在于， 所述缴费数 据库中的每一个分区数据库分配有唯一的分区代码， 一个分区代码对 应一个医院科室的编号， 每一个分区数据库记录有一个医院科室的预 定周期内的预约挂号数量。
[权利要求 10] 如权利要求 6至 9任一项所述的医院自助式缴费方法， 其特征在于， 所 述数据库中间件包括缴费数据库中每一个分区数据库的数据库标签以 及数据库连接参数， 每一个分区数据库的数据库标签与该分区数据库 的分区代码相对应， 所述数据库连接参数用于所述数据库中间件与所 述缴费数据库中的分区数据库建立数据库连接。
PCT/CN2017/080151 2016-10-15 2017-04-11 医院自助式缴费系统及方法 Ceased WO2018068490A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610900357.4 2016-10-15
CN201610900357.4A CN106485081A (zh) 2016-10-15 2016-10-15 医院自助式缴费系统及方法

Publications (1)

Publication Number Publication Date
WO2018068490A1 true WO2018068490A1 (zh) 2018-04-19

Family

ID=58269675

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/080151 Ceased WO2018068490A1 (zh) 2016-10-15 2017-04-11 医院自助式缴费系统及方法

Country Status (2)

Country Link
CN (1) CN106485081A (zh)
WO (1) WO2018068490A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106485081A (zh) * 2016-10-15 2017-03-08 深圳市前海安测信息技术有限公司 医院自助式缴费系统及方法
CN109545344A (zh) * 2018-10-31 2019-03-29 平安医疗健康管理股份有限公司 医疗缴费方法、医疗缴费终端及医疗机构服务器
CN110009840A (zh) * 2019-04-04 2019-07-12 旭辉卓越健康信息科技有限公司 一种具备即时支付功能的ai医疗一体机
CN114067981A (zh) * 2021-11-29 2022-02-18 中国联合网络通信集团有限公司 医疗数据处理方法、装置及系统

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN201114139Y (zh) * 2007-08-31 2008-09-10 张春雨 用于提供网络就医服务的医疗终端设备及智能就医系统
KR101281886B1 (ko) * 2012-06-01 2013-07-05 주식회사 우리은행 진료비 카드 결제 시스템 및 방법
CN103902836A (zh) * 2014-04-14 2014-07-02 康博嘉信息科技（北京）有限公司 基于云服务平台的医疗信息交互方法、装置及系统
CN204537314U (zh) * 2015-04-11 2015-08-05 深圳市易特科信息技术有限公司 用于网络医院平台的自助缴费终端
CN105187503A (zh) * 2015-08-07 2015-12-23 北京思特奇信息技术股份有限公司 一种支持数据分区的服务连接方法及系统
CN106485081A (zh) * 2016-10-15 2017-03-08 深圳市前海安测信息技术有限公司 医院自助式缴费系统及方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN201114139Y (zh) * 2007-08-31 2008-09-10 张春雨 用于提供网络就医服务的医疗终端设备及智能就医系统
KR101281886B1 (ko) * 2012-06-01 2013-07-05 주식회사 우리은행 진료비 카드 결제 시스템 및 방법
CN103902836A (zh) * 2014-04-14 2014-07-02 康博嘉信息科技（北京）有限公司 基于云服务平台的医疗信息交互方法、装置及系统
CN204537314U (zh) * 2015-04-11 2015-08-05 深圳市易特科信息技术有限公司 用于网络医院平台的自助缴费终端
CN105187503A (zh) * 2015-08-07 2015-12-23 北京思特奇信息技术股份有限公司 一种支持数据分区的服务连接方法及系统
CN106485081A (zh) * 2016-10-15 2017-03-08 深圳市前海安测信息技术有限公司 医院自助式缴费系统及方法

Also Published As

Publication number Publication date
CN106485081A (zh) 2017-03-08

Similar Documents

Publication Publication Date Title
US11393580B2 (en) Systems and methods for determining and communicating a prescription benefit coverage denial to a prescriber
TWI649762B (zh) 用於雲端臨床資料庫管理的方法及系統
CN108053868A (zh) 一种互联网在线共享医疗平台及系统
US10909501B2 (en) Pet insurance system and method
WO2016201595A1 (zh) 一种基于rfid技术的自动化就诊系统
CN102254086A (zh) 医疗信息处理系统
CA2946608C (en) Pet insurance system and method
CN110010232A (zh) 区域公共医疗资源共享协同系统及方法
WO2018113292A1 (zh) 医疗信息化辅助开处方的系统和方法
CN112215713A (zh) 宠物保险系统和方法
WO2018113291A1 (zh) 基于识别码的辅助医生开处方的系统和方法
CN109801690A (zh) 区域医疗电子病历共享整合查询系统及方法
JP6921177B2 (ja) 医療情報システム、医療情報装置、医療情報装置の制御方法及び制御プログラム
CN112465172A (zh) 一种医院智能就诊方法及装置
CN104102807A (zh) 一种医疗系统、患者数据分析设备以及医院网关设备
Shukla et al. Blockiot-retel: Blockchain and iot based read-execute-transact-erase-loop environment for integrating personal health data
KR20060088142A (ko) 의료 정보 공유 방법 및 그 시스템
CN117851411B (zh) 患者主索引生成方法及系统
CN116032946A (zh) 一种检测报告的跨区域同步方法、设备及介质
US20150051915A1 (en) Systems and methods for allocating payments across multiple healthcare accounts
WO2018068489A1 (zh) 医疗信息化预约挂号系统及方法
CN106485081A (zh) 医院自助式缴费系统及方法
US8566117B1 (en) Systems and methods for facilitating healthcare provider enrollment with one or more payers
CN112614579A (zh) 医院预约挂号方法、装置、计算机设备
CN117453680A (zh) 基于数据治理的知识库管理方法、系统、终端及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17860869

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 19/09/2019)

122 Ep: pct application non-entry in european phase

Ref document number: 17860869

Country of ref document: EP

Kind code of ref document: A1