Patient information management system, reception device, and patient information management method

By using a patient's insurance card number from an online eligibility verification system to manage patient information, the system reduces the cost of issuing medical cards while maintaining storage capacity, enhancing patient information management efficiency.

JP7839589B2Active Publication Date: 2026-04-02GLORY LTD
View PDF 4 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-12-14
Publication Date
2026-04-02

AI Technical Summary

Technical Problem

The existing patient information management systems face challenges in reducing the issuance cost of examination tickets without compressing the storage capacity of the storage unit that holds patient information.

Method used

A patient information management system that utilizes a patient's insurance card number obtained from an online eligibility verification system, associating it with patient identification information, and uses this number as a medical examination ticket number, along with devices like re-registration machines and medical fee payment machines to manage and update patient information.

Benefits of technology

This approach reduces the cost of issuing medical cards without compromising the storage capacity of the memory unit, enabling efficient patient information management and processing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007839589000001
    Figure 0007839589000001
  • Figure 0007839589000002
    Figure 0007839589000002
  • Figure 0007839589000003
    Figure 0007839589000003
Patent Text Reader

Abstract

To provide a patient information management system, a reception device, a payment device, a patient information recording device, a patient information management method and a patient information recording method which reduce an issuance cost of a consultation ticket without squeezing a capacity of a storage unit that stores patient information.SOLUTION: In a patient information management system in which a revisit reception machine, a medical expense payment machine, a patient information management server, an online qualification confirmation system are connected with each other via a communication line, the revisit reception machine comprises: a storage unit which stores patient information about a patient in association with patient identification information that uniquely identifies the patient and includes an insurance card number of the patient; a first acquisition unit (qualification information acquisition unit 112) which acquires the insurance card number of the patient from the online qualification confirmation system by using a medium recording a my-number of the patient; and a second acquisition unit (reservation information acquisition unit 113) which acquires the patient information associated with the patient identification information including the insurance card number from the storage unit by using the insurance card number acquired by the first acquisition unit.SELECTED DRAWING: Figure 2
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a patient information management system, a reception device, a payment device, a patient information recording device, a patient information management method, and a patient information recording method.

Background Art

[0002] In Patent Document 1, there is described a patient information management system including: a recording means for recording patient information composed of information regarding a patient in association with identification information for uniquely identifying the patient; a reception means for acquiring a unique number which is a unique number assigned to each individual of the nationals; a reading means for reading patient information from the recording means based on the identification information; and an updating means for associating the unique number acquired by the reception means with the identification information and updating the patient information read by the reading means.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] When adopting a configuration in which the my number is recorded in association with the examination ticket number in the storage unit that stores patient information, even if the issuance cost of the examination ticket can be reduced, the capacity of the storage unit will be compressed. An object of the present invention is to reduce the issuance cost of examination tickets without compressing the capacity of the storage unit that stores patient information.

Means for Solving the Problems

[0005] To this end, the present invention provides a patient information management system comprising: a storage unit that stores patient information relating to a patient in association with patient identification information that uniquely identifies the patient and includes the patient's insurance card number; a first acquisition unit that obtains the patient's insurance card number from an online eligibility verification system using a medium on which the patient's My Number is recorded; and a second acquisition unit that uses the insurance card number obtained by the first acquisition unit to obtain patient information associated with patient identification information including the insurance card number from the storage unit. The patient information management system may further include an inquiry unit that, if the insurance card number of a particular patient is not stored in the memory unit, inquires with the particular patient whether the patient is a new patient or whether the patient has visited the hospital before. In this case, the memory unit stores patient information in association with the patient's name information, the first acquisition unit acquires the patient's name information from the online eligibility verification system using a medium on which the patient's My Number is recorded, and the inquiry unit, if the insurance card number of a particular patient is not stored in the memory unit, and the name information of a particular patient acquired by the first acquisition unit is not stored in the memory unit, inquires with the particular patient whether the patient is a new patient or whether the patient has visited the hospital before. The patient information management system may further include an inquiry unit that, if the insurance card number of a particular patient is not stored in the storage unit, inquires with the particular patient whether the insurance card information of that particular patient has been changed. In that case, the storage unit may store patient information in association with the patient's name information, the first acquisition unit may acquire the patient's name information from the online eligibility verification system using a medium on which the patient's My Number is recorded, and the inquiry unit, if the insurance card number of a particular patient is not stored in the storage unit, and if the name information of the particular patient acquired by the first acquisition unit is stored in the storage unit, may inquire with the particular patient whether the insurance card information of that particular patient has been changed. The patient information management system further includes a third acquisition unit that acquires benefit information regarding the patient's receipt of publicly funded benefits from a medium on which the patient's My Number is recorded. The second acquisition unit may, if the patient's insurance card number is stored in the storage unit, acquire patient information associated with patient identification information including the insurance card number from the storage unit if the patient's benefit information acquired by the third acquisition unit is within its validity period and is stored in the storage unit associated with the patient's insurance card number. In this case, the patient information management system may further include a notification unit that notifies the patient if the patient's benefit information acquired by the third acquisition unit is outside its validity period. Alternatively, the patient information management system may further include a notification unit that notifies the patient if the patient's benefit information acquired by the third acquisition unit is not stored in the storage unit associated with the patient's insurance card number. Patient information may include time information regarding the time the patient booked an appointment, or it may include monetary information regarding the amount of money spent on the medical treatment the patient received.

[0006] The present invention also provides a reception device comprising: a first acquisition unit that acquires a patient's insurance card number from an online eligibility verification system using a medium on which the patient's My Number is recorded; a second acquisition unit that uses the insurance card number acquired by the first acquisition unit to acquire patient information from a hospital system, which is patient identification information for uniquely identifying the patient and is associated with patient identification information including the insurance card number; and a reception processing unit that uses the patient information acquired by the second acquisition unit to process the acceptance of a consultation request from the patient.

[0007] The present invention also provides a payment device comprising: a first acquisition unit that obtains a patient's insurance card number from an online eligibility verification system using a medium on which the patient's My Number is recorded; a second acquisition unit that uses the insurance card number obtained by the first acquisition unit to obtain patient information relating to the patient from a hospital system, which is patient identification information for uniquely identifying the patient and is associated with patient identification information including the insurance card number; and a payment processing unit that uses the patient information obtained by the second acquisition unit to process payment for the expenses incurred for the patient's medical examination.

[0008] Furthermore, the present invention also provides a patient information recording device comprising: a fourth acquisition unit for acquiring hospital identification information to uniquely identify a hospital; a fifth acquisition unit for acquiring patient identification information to uniquely identify a patient of the hospital; and a recording unit for associating the hospital identification information acquired by the fourth acquisition unit and the patient identification information acquired by the fifth acquisition unit and recording them on a medium on which the patient's My Number is recorded. The recording unit may associate the hospital identification information obtained by the fourth acquisition unit with the patient identification information obtained by the fifth acquisition unit and record it in a recording area of ​​the medium on which the patient's My Number is recorded, where no other hospital identification information or patient identification information is recorded.

[0009] Furthermore, the present invention also provides a patient information management method comprising the steps of: a computer storing patient information relating to a patient in a storage unit, associated with patient identification information for uniquely identifying the patient, which includes the patient's insurance card number; a computer obtaining the patient's insurance card number from an online eligibility verification system using a medium on which the patient's My Number is recorded; and a computer obtaining patient information associated with patient identification information including the insurance card number from the storage unit using the obtained insurance card number.

[0010] Furthermore, the present invention also provides a method for recording patient information, which includes the steps of: a computer obtaining hospital identification information for uniquely identifying a hospital; a computer obtaining patient identification information for uniquely identifying a patient of the hospital; and a computer associating the obtained hospital identification information with the obtained patient identification information and recording it on a medium on which the patient's My Number is recorded. [Effects of the Invention]

[0011] According to the present invention, the cost of issuing medical cards can be reduced without putting pressure on the capacity of the memory unit that stores patient information. [Brief explanation of the drawing]

[0012] [Figure 1] This figure shows an example of the overall configuration of the patient information management system in the first embodiment. [Figure 2] This is a block diagram showing an example of the functional configuration of the return visit registration machine in the first embodiment. [Figure 3] This is a block diagram showing an example of the functional configuration of a medical fee payment machine in the first embodiment. [Figure 4] This is a block diagram showing an example of the functional configuration of the patient information management server in the first embodiment. [Figure 5] This figure shows an example of patient management information in the first embodiment. [Figure 6-1] This is a sequence diagram showing an example of the operation of the patient information management system during a return visit registration in the first embodiment. [Figure 6-2] This is a sequence diagram showing an example of the operation of the patient information management system during a return visit registration in the first embodiment. [Figure 7] This is a sequence diagram showing an example of the operation of the patient information management system during medical fee payment in the first embodiment. [Figure 8] This figure shows an example of the overall configuration of the patient information management system in the second embodiment. [Figure 9]It is a block diagram showing a functional configuration example of a patient information recording device in the second embodiment. [Figure 10] It is a block diagram showing a functional configuration example of a re-reception machine in the second embodiment. [Figure 11] It is a block diagram showing a functional configuration example of a patient information management server in the second embodiment. [Figure 12] It is a diagram showing an example of patient management information in the second embodiment. [Figure 13] It is a sequence diagram showing an operation example at the time of recording patient information in a patient information management system in the second embodiment. [Figure 14] It is a sequence diagram showing an operation example at the time of re-reception in a patient information management system in the second embodiment. [Figure 15] It is a diagram showing an overall configuration example of a medical examination ticket number inquiry system in the third embodiment. [Figure 16] It is a diagram showing a specific example of correspondence information held by a server device in the third embodiment. [Figure 17] It is a diagram showing an overall configuration example of a dispensing pharmacy selection system in the fourth embodiment. [Figure 18] It is a diagram showing a specific example of a selection screen of a dispensing pharmacy displayed in the fourth embodiment. [Embodiments for Carrying Out the Invention]

[0013] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

[0014] [First Embodiment] [Overview] The first embodiment is to obtain an insurance certificate number from an online eligibility confirmation system using a My Number card and use this insurance certificate number as a medical examination ticket number.

[0015] [Overall Configuration of Patient Information Management System] Figure 1 is a diagram showing an example of the overall configuration of the patient information management system 1 in the first embodiment. As shown in the figure, the patient information management system 1 includes a re-registration machine 10, a medical fee payment machine 20, a patient information management server 30, and an online eligibility verification system 40. Of these, the re-registration machine 10, the medical fee payment machine 20, and the patient information management server 30 are installed in a medical institution such as a hospital and are connected to each other via a communication line 91. The online eligibility verification system 40 is connected via a communication line 92 to the medical institution's system, which includes the re-registration machine 10, the medical fee payment machine 20, and the patient information management server 30.

[0016] The re-registration machine 10 is installed, for example, around the reception desk of a medical institution, and is a device that registers a patient as a returning patient when a patient who made an appointment for a consultation during their previous visit returns to the institution. The re-registration machine 10 comprises a display and operation unit 14 located at the top and a card reader 15 located in the card slot to the lower right of the display and operation unit 14. The display and operation unit 14 is, for example, a touch panel display that displays various information to the patient and accepts operations from the patient. The card reader 15 is a device that reads information from a card inserted into the card slot, and includes, for example, a magnetic card reader and a contactless IC card reader. The part of the card reader 15 that includes a contactless IC card reader may also read information from a card held over it, but in the following description, we will use as an example a card that reads information from a card inserted into the card slot. In this embodiment, the re-registration machine 10 is provided as an example of a reception device.

[0017] The medical fee payment machine 20 is a device installed, for example, around the settlement counter of a medical institution, which displays the amount of medical fees to patients who have received medical treatment and accepts payment of medical fees from patients. The medical fee payment machine 20 comprises a display and operation unit 24 located at the top, a card reader 25 located in the card slot to the lower right of the display and operation unit 24, and a deposit and withdrawal unit 26 located in the center. The display and operation unit 24 is, for example, a touch panel display, which displays various information to patients and accepts operations from patients. The card reader 25 is a device that reads information from cards inserted into the card slot, and includes, for example, a magnetic card reader and a contactless IC card reader. The part of the card reader 25 that includes a contactless IC card reader may also read information from a card held over it, but in the following explanation, we will use as an example a card that reads information from a card inserted into the card slot. The deposit and withdrawal unit 26 is a mechanism for depositing medical fees and dispensing change. In this embodiment, the medical fee payment machine 20 is provided as an example of a payment device.

[0018] The patient information management server 30 manages patient information, which is information about a patient, by associating it with patient identification information that uniquely identifies the patient. Patient information can be any information related to a patient, but below, we will explain using appointment information, which includes the department and date and time of the patient's next appointment, and billing information for the patient's medical treatment as examples. Patient identification information will be insurance information, which includes the insurance card number. Insurance information is the information written on the insurance card. The insurance card number is a number that uniquely identifies the insured person. The insurer number may be a symbol and a number, but is not limited to this. For example, the insurance card number may further include a sub-number to identify each family member, or it may further include an insurer number to identify the name of the insurer. The patient information management server 30 may also manage patient information by associating it with registration information such as the patient's name, address, and date of birth. Here, the registration information is assumed to include name, address, date of birth, etc., but it may also include only the name. In this embodiment, appointment information or billing information is used as an example of patient information relating to a patient, and insurance card information is used as an example of patient identification information that uniquely identifies a patient and includes the patient's insurance card number. A patient information management server 30 is provided as an example of a storage unit that stores patient information in association with patient identification information. Furthermore, in this embodiment, a patient information management server 30 is provided as an example of a storage unit that stores patient information in further association with patient name information. Moreover, in this embodiment, a patient information management server 30 is provided as an example of a hospital system.

[0019] The online eligibility verification system 40 manages the eligibility of insured persons, verifies their eligibility in response to inquiries from medical institutions and pharmacies, and returns the verification results as a response. This online eligibility verification system 40 may be constructed, for example, based on the "Act to Amend Part of the Health Insurance Act, etc., for the Purpose of Ensuring the Appropriate and Efficient Operation of the Medical Insurance System."

[0020] The communication line 91 is a line for communicating information between the re-registration machine 10 or the medical fee payment machine 20 and the patient information management server 30. While not limited to this, a LAN (Local Area Network) is a suitable choice for the communication line 91.

[0021] The communication line 92 is a line for communicating information between the medical institution system, which includes the re-registration machine 10, the medical fee payment machine 20, and the patient information management server 30, and the online eligibility verification system 40. While not limited to this, the communication line 92 could, for example, use the internet.

[0022] (Configuration of the return visit registration machine) Figure 2 is a block diagram showing an example of the functional configuration of the re-registration machine 10 in the first embodiment. As shown in the figure, the re-registration machine 10 includes a control unit 11, a storage unit 12, a communication unit 13, a display operation unit 14, and a card reader 15.

[0023] The control unit 11 is equipped with an arithmetic circuit such as a CPU (Central Processing Unit) and controls each part of the re-registration machine 10 (communication unit 13, display operation unit 14, card reader 15, etc.) according to the operation program stored in the memory unit 12. The memory unit 12 includes ROM (Read Only Memory), RAM (Random Access Memory), etc., and stores the operation program of the control unit 11. It is also used as a work area during the control processing of the control unit 11. The operation program includes a program for the control unit 11, which is a computer, to execute the processes described later. The communications unit 13 communicates information with the patient information management server 30 via the communication line 91, and communicates information with the online eligibility verification system 40 via the communication lines 91 and 92. The display operation unit 14 and the card reader 15 have already been explained using Figure 1, so their explanation will be omitted here.

[0024] Here, the configuration of the control unit 11 will be described in detail. The control unit 11 comprises a card information acquisition unit 111, a qualification information acquisition unit 112, a reservation information acquisition unit 113, a reception processing unit 114, a notification processing unit 115, and a confirmation processing unit 116.

[0025] The card information acquisition unit 111 acquires the card information from the card reader 15 when the card reader 15 reads the patient's card information from the patient's My Number Card. The card information includes the My Number (registered trademark) and the beneficiary certificate information. The My Number is a personal number assigned to each citizen. The beneficiary certificate information is information related to the beneficiary certificate, which is proof that all or part of medical expenses are covered by public funds, other than the health insurance card. In this embodiment, the beneficiary certificate information is recorded in the publicly accessible area used to access various services on the My Number Card. Although a medium such as a smartphone that stores the My Number and beneficiary certificate information may be used instead of the My Number Card, the following explanation will assume the use of the My Number Card. In addition, the card information may include personal authentication information. Personal authentication information is information used to authenticate an individual in each service. Although personal authentication information may be used instead of the My Number, the following explanation will assume the use of the My Number. In this embodiment, a My Number card is used as an example of a medium on which the patient's My Number is recorded, and beneficiary certificate information is used as an example of benefit information related to the patient's receipt of publicly funded benefits. Furthermore, a card information acquisition unit 111 is provided as an example of a third acquisition unit that acquires benefit information from the medium.

[0026] The credential information acquisition unit 112 uses the My Number obtained from the My Number Card by the card information acquisition unit 111 to acquire credential information from the online credential verification system 40. Specifically, the credential information acquisition unit 112 sends a credential information request including the My Number to the online credential verification system 40. Then, the credential information acquisition unit 112 receives a credential information response including credential information from the online credential verification system 40 as a response to the credential information request. The credential information includes insurance card information including the insurance card number, and registration information including name, address, date of birth, etc. In this embodiment, the credential information acquisition unit 112 is provided as an example of a first acquisition unit that acquires the patient's insurance card number from the online credential verification system using a medium on which the patient's My Number is recorded. In this embodiment, the credential information acquisition unit 112 is also provided as an example of a first acquisition unit that acquires the patient's name information from the online credential verification system using a medium on which the patient's My Number is recorded.

[0027] The reservation information acquisition unit 113 uses the insurance card information and registration information acquired by the qualification information acquisition unit 112 and the beneficiary certificate information acquired by the card information acquisition unit 111 to acquire the patient's reservation information from the patient information management server 30. Specifically, the reservation information acquisition unit 113 sends a reservation information request including the insurance card information, registration information, and beneficiary certificate information to the patient information management server 30. Then, as a response to the reservation information request, the reservation information acquisition unit 113 receives a reservation information response from the patient information management server 30 that includes the reservation information stored in association with the insurance card information. Alternatively, if the insurance card information is stored in the patient information management server 30 and the beneficiary certificate information is within its validity period and matches that stored in the patient information management server 30, the reservation information acquisition unit 113 may receive a reservation information response including the reservation information from the patient information management server 30. Here, the reservation information includes information on the medical department and date and time that the patient has reserved. In this embodiment, reservation information is used as an example of patient information that includes time information regarding the time the patient has reserved a consultation. Furthermore, in this embodiment, a reservation information acquisition unit 113 is provided as an example of a second acquisition unit that uses the insurance card number acquired by the first acquisition unit to acquire patient information associated with patient identification information including the insurance card number from the storage unit.

[0028] The reception processing unit 114 performs reception processing using the reservation information acquired by the reservation information acquisition unit 113. Specifically, the reception processing unit 114 issues a reception number to the patient. The reception processing unit 114 may also notify the medical department included in the reservation information that the patient has returned. In this embodiment, the reception processing unit 114 is provided as an example of a reception processing unit that performs reception processing of a patient's consultation request using patient information acquired by the second acquisition unit.

[0029] The notification processing unit 115 displays notification information on the display operation unit 14 to notify the patient of predetermined information. Here, the notification information is, for example, information to notify the patient if the beneficiary certificate information read by the card information acquisition unit 111 from the My Number Card is outside its validity period or does not match the beneficiary certificate information stored in the patient information management server 30. Alternatively, the notification information may be information to notify the patient not only of that fact but also of the actions the patient should take in such cases. In this embodiment, the notification processing unit 115 is provided as an example of a notification unit that notifies the patient if the patient's beneficiary information acquired by the third acquisition unit is outside its validity period. Also in this embodiment, the notification processing unit 115 is provided as an example of a notification unit that notifies the patient if the patient's beneficiary information acquired by the third acquisition unit is not stored in the storage unit in association with the patient's insurance card number.

[0030] The confirmation processing unit 116 displays confirmation information on the display operation unit 14 to prompt the patient to perform a predetermined confirmation. Here, the confirmation information is, for example, information used to confirm whether a patient is a new patient or a patient who has visited the hospital before, when the patient's insurance card information is not stored in the patient information management server 30. Alternatively, the confirmation information may be, for example, information used to confirm whether a patient is a new patient or a patient who has visited the hospital before, when the patient's insurance card information is not stored in the patient information management server 30 and the patient's registration information is not stored in the patient information management server 30. In this embodiment, this function of the confirmation processing unit 116 is provided as an example of an inquiry unit that queries whether a particular patient is a new patient or a patient who has visited the hospital before, when the insurance card number of a particular patient is not stored in the storage unit. Furthermore, in this embodiment, this function of the confirmation processing unit 116 is provided as an example of an inquiry that queries whether a particular patient is a new patient or a patient who has visited the hospital before, when the insurance card number of a particular patient is not stored in the storage unit and the name information of a particular patient obtained by the first acquisition unit is not stored in the storage unit. Furthermore, the confirmation information is, for example, information that allows a patient to confirm whether their insurer is correct, that is, whether their insurance card has been changed, if the patient's insurance card information is not stored in the patient information management server 30. Alternatively, the confirmation information may be, for example, information that allows a patient to confirm whether their insurer is correct, that is, whether their insurance card has been changed, if the patient's registration information is stored in the patient information management server 30, even if the patient's insurance card information is not stored in the patient information management server 30. In this case, if the patient confirms that the insurer is correct, that is, that their insurance card has been changed, the confirmation processing unit 116 controls the communication unit 13 to send an insurance card information update request to the patient information management server 30 requesting an update of the insurance card information. In this embodiment, this function of the confirmation processing unit 116 is provided as an example of an inquiry unit that inquires whether a specific patient's insurance card information has been changed, when the insurance card number of a specific patient is not stored in the storage unit. Furthermore, in this embodiment, if the insurance card number of a specific patient is not stored in the storage unit, and the name information of the specific patient obtained by the first acquisition unit is stored in the storage unit, the confirmation processing unit 116 is provided with this function as an example of an inquiry unit that inquires with the specific patient whether or not the insurance card information of the specific patient has been changed.

[0031] (Configuration of the medical fee payment machine) Figure 3 is a block diagram showing an example of the functional configuration of the medical fee payment machine 20 in the first embodiment. As shown in the figure, the medical fee payment machine 20 includes a control unit 21, a storage unit 22, a communication unit 23, a display operation unit 24, a card reader 25, and a deposit / withdrawal unit 26.

[0032] The control unit 21 is equipped with an arithmetic circuit such as a CPU and controls each part of the medical fee payment machine 20 (communication unit 23, display operation unit 24, card reader 25, deposit / withdrawal unit 26, etc.) according to the operation program stored in the memory unit 22. The memory unit 22 is equipped with ROM, RAM, etc., and stores the operation program of the control unit 21. It is also used as a work area during the control processing of the control unit 21. The operation program includes a program for the control unit 21, which is a computer, to execute the processes described later. The communications unit 23 communicates information with the patient information management server 30 via the communication line 91, and communicates information with the online eligibility verification system 40 via the communication lines 91 and 92. The display and operation unit 24, the card reader 25, and the deposit / withdrawal unit 26 have already been explained using Figure 1, so their explanation will be omitted here.

[0033] Here, the configuration of the control unit 21 will be described in detail. The control unit 21 comprises a card information acquisition unit 211, a credential information acquisition unit 212, a billing information acquisition unit 213, and a payment processing unit 214.

[0034] The card information acquisition unit 211 acquires the card information from the card reader 25 when the card reader 25 reads the patient's card information from the patient's My Number Card. The card information includes the My Number (registered trademark). The My Number has already been explained, so an explanation will be omitted here. Note that a device such as a smartphone that stores the My Number may be used instead of the My Number Card, but the following explanation will assume the use of a My Number Card.

[0035] The credential information acquisition unit 212 uses the My Number obtained from the My Number Card by the card information acquisition unit 211 to acquire credential information from the online credential verification system 40. Specifically, the credential information acquisition unit 212 sends a credential information request including the My Number to the online credential verification system 40. Then, the credential information acquisition unit 212 receives a credential information response including the credential information from the online credential verification system 40 as a response to the credential information request. The credential information includes insurance card information including the insurance card number, and registration information including name, address, date of birth, etc. In this embodiment, the credential information acquisition unit 212 is provided as an example of a first acquisition unit that acquires the patient's insurance card number from the online credential verification system using a medium on which the patient's My Number is recorded. In this embodiment, the credential information acquisition unit 212 is also provided as an example of a first acquisition unit that acquires the patient's name information from the online credential verification system using a medium on which the patient's My Number is recorded.

[0036] The billing information acquisition unit 213 uses the insurance card information acquired by the eligibility information acquisition unit 212 to acquire the patient's billing information from the patient information management server 30. Specifically, the billing information acquisition unit 213 sends a billing information request, including the insurance card information, to the patient information management server 30. The billing information acquisition unit 213 then receives a billing information response from the patient information management server 30 as a response to the billing information request, which includes billing information stored in association with the insurance card information. Here, the billing information includes information on the amount billed for the medical treatment received by the patient. In this embodiment, billing information is used as an example of patient information that includes amount information regarding the amount spent on the medical treatment received by the patient. In this embodiment, the billing information acquisition unit 213 is also provided as an example of a second acquisition unit that uses the insurance card number acquired by the first acquisition unit to acquire patient information associated with patient identification information, including the insurance card number, from the storage unit. Furthermore, in this embodiment, a billing information acquisition unit 213 is provided as an example of a second acquisition unit that uses the insurance card number acquired by the first acquisition unit to acquire patient information associated with patient identification information including the insurance card number from the hospital system.

[0037] The payment processing unit 214 processes payments using the billing information acquired by the billing information acquisition unit 213. Specifically, the payment processing unit 214 presents the patient with the billing amount indicated by the billing information. The payment processing unit 214 also accepts the amount entered by the patient into the deposit / withdrawal unit 26 in response to the presented billing amount, and outputs change to the deposit / withdrawal unit 26 as necessary. In this embodiment, the payment processing unit 214 is provided as an example of a payment processing unit that processes payments for the costs incurred for the patient's medical examination using patient information acquired by the second acquisition unit.

[0038] (Patient information management server configuration) Figure 4 is a block diagram showing an example of the functional configuration of the patient information management server 30 in the first embodiment. As shown in the figure, the patient information management server 30 includes a control unit 31, a storage unit 32, and a communication unit 33.

[0039] The control unit 31 is equipped with an arithmetic circuit such as a CPU and controls each part of the patient information management server 30 (communication unit 33, etc.) according to the operation program stored in the memory unit 32. The memory unit 32 is equipped with ROM, RAM, etc., and stores the operation program of the control unit 31. It is also used as a work area during the control processing of the control unit 31. The operation program includes a program for the control unit 31, which is a computer, to execute the processes described later. The communication unit 33 communicates information with the re-registration machine 10 or the medical fee payment machine 20 via the communication line 91.

[0040] Here, the configuration of the control unit 31 will be described in detail. The control unit 31 comprises an information determination unit 311, a reservation information acquisition unit 312, an insurance card information update unit 313, and a billing information acquisition unit 314.

[0041] When the communication unit 33 receives a reservation information request from the re-registration machine 10, including insurance card information, reservation information, and beneficiary certificate information, the information determination unit 311 determines whether the insurance card information is stored in the storage unit 32. If it determines that the insurance card information is stored in the storage unit 32, the information determination unit 311 determines whether the beneficiary certificate information is within its validity period. If it determines that the beneficiary certificate information is within its validity period, it determines whether the beneficiary certificate information matches the beneficiary certificate information stored in the storage unit 32. On the other hand, if it determines that the insurance card information is not stored in the storage unit 32, the information determination unit 311 determines whether the registration information is stored in the storage unit 32.

[0042] The reservation information acquisition unit 312 acquires the reservation information stored in the storage unit 32 in association with the insurance card information if the insurance card information is stored in the storage unit 32 and the information determination unit 311 determines that the beneficiary certificate information is within its validity period and matches the beneficiary certificate information stored in the storage unit 32. Furthermore, as will be described later, if the insurance card information stored in the storage unit 32 is updated by the insurance card information update unit 313, the reservation information acquisition unit 312 also acquires the reservation information stored in the storage unit 32 in association with the updated insurance card information.

[0043] When the communication unit 33 receives a request to update insurance card information from the re-registration machine 10, the insurance card information update unit 313 updates the insurance card information stored in the storage unit 32.

[0044] When the communication unit 33 receives a billing information request including insurance card information from the medical fee payment machine 20, the billing information acquisition unit 314 acquires the billing information stored in the storage unit 32 in association with the insurance card information.

[0045] Next, we will explain in detail the information that the memory unit 32 stores. The memory unit 32 stores patient management information 321.

[0046] Figure 5 shows an example of patient management information 321. As shown in the figure, patient management information 321 associates insurance card information, registration information, beneficiary certificate information, reservation information, and billing information. Insurance information is the information written on the insured person's insurance card. Insurance information includes the insurance card number, insurer name, etc. Registration information includes name, date of birth, address, etc. Beneficiary certificate information includes the beneficiary certificate number, payer name, etc. Reservation information includes the reservation number, reservation date and time, etc. Billing information includes the billing number, medical expenses, etc. The diagram shows, for example, that for a patient with insurance card number "12345678", the insurer's name is "A", the patient's name is "〇yama〇o", the beneficiary certificate number is "123456", the appointment date and time is "November 1st, 9:00", and the medical fee is "○○ yen".

[0047] (Operation of the patient information management system) Figures 6-1 and 6-2 are sequence diagrams showing an example of the operation of the patient information management system 1 during a return visit registration in the first embodiment.

[0048] When a patient inserts their My Number Card into the card slot, the re-registration machine 10 uses a card reader 15 to read card information from the My Number Card (step 131). The card information includes the My Number and the recipient certificate information, and is acquired by the card information acquisition unit 111. Then, in the re-registration machine 10, under the control of the qualification information acquisition unit 112, the communication unit 13 transmits the qualification information request, including the My Number acquired in step 131, to the online qualification verification system 40 (step 132).

[0049] As a result, the online eligibility verification system 40 receives the eligibility information request from the re-registration machine 10 (step 431). The online eligibility verification system 40 then obtains the eligibility information corresponding to the My Number included in the eligibility information request received in step 431 and sends the eligibility information response containing this eligibility information to the re-registration machine 10 (step 432).

[0050] As a result, the communication unit 13 of the re-registration machine 10 receives a qualification information response from the online qualification verification system 40 (step 133). The qualification information included in the qualification information response includes insurance card information and registration information, and is acquired by the qualification information acquisition unit 112. Then, in the re-registration machine 10, under the control of the reservation information acquisition unit 113, the communication unit 13 sends a reservation information request to the patient information management server 30, which includes the insurance card information and registration information acquired in step 133 and the beneficiary card information acquired in step 131 (step 134).

[0051] As a result, the patient information management server 30 receives a reservation information request from the re-registration machine 10 via the communication unit 33 (step 331). The reservation information request includes insurance card information, registration information, and beneficiary certificate information, and is acquired by the information determination unit 311. Next, in the patient information management server 30, the information determination unit 311 determines whether the insurance card information acquired in step 331 is stored in the storage unit 32 (step 332).

[0052] First, let's explain the case in step 332 where it is determined that the insurance card information obtained in step 331 is stored in the storage unit 32. In this case, the information determination unit 311 determines whether the beneficiary certificate information obtained in step 331 is within its validity period (step 333). For example, the beneficiary certificate information may include information that is within its validity period, and the information determination unit 311 may make this determination based on whether the current date falls within this validity period.

[0053] As a result, if it is determined that the beneficiary certificate information obtained in step 331 is within its validity period, the information determination unit 311 determines whether the beneficiary certificate information obtained in step 331 matches the beneficiary certificate information stored in the storage unit 32 (step 334). If it is determined that the beneficiary certificate information obtained in step 331 matches the beneficiary certificate information stored in the storage unit 32, the reservation information acquisition unit 312 acquires the reservation information stored in association with the insurance certificate information obtained in step 331 from the storage unit 32 (step 335). Subsequently, under the control of the reservation information acquisition unit 312, the patient information management server 30 sends a reservation information response containing the reservation information acquired in step 335 to the re-registration machine 10 (step 336).

[0054] As a result, the communication unit 13 of the re-registration machine 10 receives a reservation information response from the patient information management server 30 (step 135). The reservation information response includes reservation information, which is acquired by the reservation information acquisition unit 113. Then, in the re-registration machine 10, the registration processing unit 114 uses the reservation information obtained in step 135 to perform patient registration processing (step 136). Registration processing includes, for example, adding the patient to the waiting line for the reserved time slot in the medical department for which the patient made a reservation.

[0055] On the other hand, consider the case in step 333 where it is determined that the beneficiary certificate information obtained in step 331 is outside its validity period, or in step 334 where it is determined that the beneficiary certificate information obtained in step 331 does not match the beneficiary certificate information stored in the storage unit 32. In this case, the patient information management server 30, under the control of the information determination unit 311, has the communication unit 33 send a beneficiary certificate renewal request to the re-registration machine 10 requesting the renewal of the beneficiary certificate (step 337).

[0056] As a result, the communication unit 13 of the re-registration machine 10 receives a request for renewal of the beneficiary certificate from the patient information management server 30 (step 137). The request for renewal of the beneficiary certificate is acquired by the notification processing unit 115. Then, in the re-registration machine 10, the notification processing unit 115 displays notification information about the renewal of the beneficiary certificate on the display operation unit 14 (step 138). The display operation unit 14 then displays information about the renewal of the beneficiary certificate. Specifically, since the beneficiary certificate cannot be automatically renewed, the display operation unit 14 displays instructions on how to go to the counter to renew the beneficiary certificate.

[0057] In this example, the re-registration machine 10 executed steps 137 and 138 after executing steps 135 and 136, but it may also execute steps 135 and 136 after executing steps 137 and 138.

[0058] Next, we will explain the case in step 332 when it is determined that the insurance card information obtained in step 331 is not stored in the storage unit 32. In this case, the information determination unit 311 determines whether the registration information obtained in step 331 is stored in the storage unit 32 (step 341).

[0059] As a result, if it is determined that the registration information obtained in step 331 is stored in the storage unit 32, the information determination unit 311 controls the communication unit 33 to transmit the insurer name included in the insurance card information stored in the storage unit 32 in association with this registration information to the re-registration machine 10 (step 342).

[0060] As a result, the communication unit 13 of the re-registration machine 10 receives the insurer name from the patient information management server 30 (step 141). The insurer name is obtained by the confirmation processing unit 116. Next, in the re-registration machine 10, the confirmation processing unit 116 displays confirmation information on the display operation unit 14 to verify whether the insurer name obtained in step 141 is correct, that is, whether it is the insurer name of the person before the change (step 142). The patient then checks whether the insurer's name is correct and inputs the result from the display operation unit 14. The confirmation processing unit 116 then determines whether the insurer's name has been entered as correct from the display operation unit 14 (step 143). As a result, if it is determined that the insurer name is correct as entered from the display operation unit 14, the communication unit 13, under the control of the confirmation processing unit 116, sends an insurance card information update request, including the insurance card information acquired in step 133, to the patient information management server 30 (step 144).

[0061] As a result, the patient information management server 30 receives an insurance card information update request from the re-registration machine 10 via the communication unit 33 (step 343). The insurance card information included in the insurance card information update request is acquired by the insurance card information update unit 313. Next, in the patient information management server 30, the insurance card information update unit 313 updates the insurance card information stored in the storage unit 32 with the insurance card information obtained in step 343 (step 344). In other words, the insurance card information update unit 313 updates the insurance card information before the change, which was managed by the patient information management server 30, with the changed insurance card information obtained from the online eligibility verification system 40. Next, in the patient information management server 30, the reservation information acquisition unit 312 acquires the reservation information stored in association with the updated insurance card information from the storage unit 32 (step 345). Subsequently, under the control of the reservation information acquisition unit 312, the patient information management server 30 sends a reservation information response containing the reservation information acquired in step 345 to the re-registration machine 10 (step 346).

[0062] As a result, the communication unit 13 in the re-registration machine 10 receives a reservation information response from the patient information management server 30 (step 145). The reservation information response includes reservation information, which is acquired by the reservation information acquisition unit 113. Then, in the re-registration machine 10, the registration processing unit 114 uses the reservation information obtained in step 145 to perform patient registration processing (step 146). Registration processing, as described above, is, for example, the process of adding the patient to the waiting line for the reserved time slot in the medical department for which the patient made a reservation.

[0063] On the other hand, in step 341, if it is determined that the registration information obtained in step 331 is not stored in the storage unit 32, the information determination unit 311 controls the communication unit 33 to send a new patient registration request to the re-registration machine 10, requesting the patient to register as a new patient (step 347).

[0064] As a result, the communication unit 13 of the re-registration machine 10 receives a new patient registration request from the patient information management server 30 (step 147). The new patient registration request is acquired by the notification processing unit 115. Then, in the re-registration machine 10, the notification processing unit 115 displays notification information for new patient registration on the display operation unit 14 (step 148). The display operation unit 14 then displays instructions for new patient registration.

[0065] Furthermore, if in step 143 it is determined that the insurer name is incorrect as entered from the display operation unit 14, the notification processing unit 115 of the re-registration machine 10 will display new patient registration notification information on the display operation unit 14 (step 148). Then, the display operation unit 14 will display instructions for new patient registration.

[0066] Figure 7 is a sequence diagram showing an example of the operation of the patient information management system 1 during medical fee payment in the first embodiment.

[0067] When a patient inserts their My Number Card into the card slot, the medical fee payment machine 20 uses a card reader 25 to read the card information from the My Number Card (step 251). The card information, including the My Number, is acquired by the card information acquisition unit 211. Then, in the medical fee payment machine 20, under the control of the credential information acquisition unit 212, the communication unit 23 transmits the credential information request, including the My Number acquired in step 251, to the online credential verification system 40 (step 252).

[0068] As a result, the online eligibility verification system 40 receives an eligibility information request from the medical fee payment machine 20 (step 451). The online eligibility verification system 40 then obtains the eligibility information corresponding to the My Number included in the eligibility information request received in step 451, and sends an eligibility information response containing this eligibility information to the medical fee payment machine 20 (step 452).

[0069] As a result, the communication unit 23 of the medical fee payment machine 20 receives a credential information response from the online credential verification system 40 (step 253). The credential information included in the credential information response includes insurance card information and is acquired by the credential information acquisition unit 212. Then, in the medical fee payment machine 20, under the control of the billing information acquisition unit 213, the communication unit 23 sends a billing information request, including the insurance card information acquired in step 253, to the patient information management server 30 (step 254).

[0070] As a result, the patient information management server 30's communication unit 33 receives a billing information request from the medical fee payment machine 20 (step 351). The billing information request includes insurance card information and is acquired by the billing information acquisition unit 314. Next, in the patient information management server 30, the billing information acquisition unit 314 acquires the billing information stored in the storage unit 32 in association with the insurance card information acquired in step 351 (step 352). Subsequently, under the control of the billing information acquisition unit 314, the patient information management server 30 sends a billing information response containing the billing information acquired in step 352 to the medical fee payment machine 20 via the communication unit 33 (step 353).

[0071] As a result, the medical fee payment machine 20's communication unit 23 receives a billing information response from the patient information management server 30 (step 255). The billing information response includes billing information, which is acquired by the payment processing unit 214. Then, in the medical fee payment machine 20, the payment processing unit 214 uses the billing information obtained in step 255 to process the payment of medical fees (step 256). The payment process is carried out, for example, when the patient deposits the billed amount into the deposit / withdrawal unit 26 of the medical fee payment machine 20.

[0072] (modified version) The online eligibility verification system 40 receives a large number of daily accesses for its original purpose of obtaining insurance card information. Inquiries about eligibility information for purposes other than its intended use could increase the load on the system and potentially cause problems. Furthermore, it is conceivable that the online eligibility verification system 40 may become inaccessible in the event of a disaster.

[0073] Therefore, in the first embodiment, it is also conceivable to write insurance information onto the My Number Card. In that case, the following process will be executed in the patient information management system 1. Specifically, first, when the re-registration machine 10 or the medical fee payment machine 20 reads the My Number Card, it determines whether or not insurance information can be obtained from the My Number Card. As a result, if it is determined that insurance information can be obtained from the My Number Card, the re-registration machine 10 or the medical fee payment machine 20 will perform processing such as querying the patient information management server 30 for reservation information or billing information based on the insurance information obtained from the My Number Card. On the other hand, if it is determined that insurance information cannot be obtained from the My Number Card, the re-registration machine 10 or the medical fee payment machine 20 will inquire about insurance information from the online eligibility verification system 40 and write the obtained insurance information to the My Number Card.

[0074] Furthermore, in the first embodiment, the eligibility information received from the online eligibility verification system 40 may be stored on a server within the hospital separate from the online eligibility verification system 40, and the eligibility information may be retrieved from that server for a certain period of time. For example, if the eligibility information is retrieved from the hospital server for one month, from one claim request to the next, the load on the online eligibility verification system 40 will be reduced.

[0075] (effect) According to the first embodiment, the cost of issuing medical cards can be reduced, and the medical card and health insurance card can be unified (the My Number Card can serve as both a medical card and a health insurance card).

[0076] [Second Embodiment] (overview) The second embodiment involves recording multiple patient ID card information on a My Number Card, associating each with its corresponding hospital identification information, and then obtaining the patient ID card information corresponding to the hospital identification information.

[0077] (Overall configuration of the patient information management system) Figure 8 shows an example of the overall configuration of the patient information management system 2 in the second embodiment. As shown in the figure, the patient information management system 2 includes a patient information recording device 50, a re-registration machine 60, and a patient information management server 70. The patient information recording device 50, the re-registration machine 60, and the patient information management server 70 are installed in a medical institution such as a hospital and are connected to each other via a communication line 93.

[0078] The patient information recording device 50 is installed, for example, around the reception desk of a medical institution, and is a device that reads the medical card information recorded on the medical card and records this medical card information on the My Number Card. The patient information recording device 50 comprises a display operation unit 54 located at the top and a card reader / writer 55 located in the card slot to the lower right of the display operation unit 54. The display operation unit 54 is, for example, a touch panel display, which displays various information to the patient and accepts operations from the patient. The card reader / writer 55 is a device that reads information from a card inserted into the card slot or writes information to a card inserted into the card slot, and includes, for example, a magnetic card reader and a contactless IC card reader / writer. The part of the card reader / writer 55 that includes the contactless IC card reader / writer may read and write information to a card that is held over it, but in the following explanation, we will use as an example a device that reads and writes information to a card inserted into the card slot.

[0079] The re-registration machine 60 is installed, for example, around the reception desk of a medical institution, and is a device that registers a patient as a returning patient when a patient who made an appointment for a consultation during their previous visit returns to the institution. The re-registration machine 60 comprises a display and operation unit 64 located at the top and a card reader 65 located in the card slot to the lower right of the display and operation unit 64. The display and operation unit 64 and the card reader 65 are the same as the display and operation unit 14 and card reader 15 in the first embodiment, respectively, so their description is omitted here. The re-registration machine 60 may also have the functions of a patient information recording device 50.

[0080] The patient information management server 70 manages patient information, which is information about a patient, by associating it with patient identification information that uniquely identifies the patient. Patient information can be any information related to a patient, but in the following explanation, registered information such as the patient's name, address, and date of birth will be used as an example. Note that, although the registered information is assumed to include name, address, and date of birth, it may also include only the name.

[0081] The communication line 93 is a line for communicating information between the patient information recording device 50 or the re-registration machine 60 and the patient information management server 70. While not limited to this, a LAN (Local Area Network) is a suitable choice for the communication line 93.

[0082] (Configuration of patient information recording device) Figure 9 is a block diagram showing an example of the functional configuration of the patient information recording device 50 in the second embodiment. As shown in the figure, the patient information recording device 50 includes a control unit 51, a storage unit 52, a communication unit 53, a display operation unit 54, and a card reader / writer 55.

[0083] The control unit 51 is equipped with an arithmetic circuit such as a CPU and controls each part of the patient information recording device 50 (communication unit 53, display operation unit 54, card reader / writer 55, etc.) according to the operation program stored in the memory unit 52. The memory unit 52 is equipped with ROM, RAM, etc., and stores the operation program of the control unit 51. It is also used as a work area during the control processing of the control unit 51. The operation program includes a program for the control unit 51, which is a computer, to execute the processes described later. The communications unit 53 communicates information with the patient information management server 70 via a communication line. The display operation unit 54 and the card reader / writer 55 have already been explained using Figure 8, so their explanation will be omitted here.

[0084] Here, the configuration of the control unit 51 will be described in detail. The control unit 51 includes a hospital identification information acquisition unit 511, a patient identification information acquisition unit 512, a hospital determination unit 513, a patient information acquisition unit 514, and an information output unit 515.

[0085] The hospital identification information acquisition unit 511 acquires the hospital identification information from the card reader / writer 55 when the card reader / writer 55 reads the patient's medical card information, which includes hospital identification information and patient identification information. The hospital identification information is identification information that uniquely identifies a hospital participating in this system. In normal operation, an in-hospital hospital code, which is a hospital code determined independently by the hospital, is used to identify the hospital. However, since the in-hospital hospital code is not necessarily unique within this system, hospital identification information that is unique within the system is set separately from the in-hospital hospital code. In this embodiment, the hospital identification information acquisition unit 511 is provided as an example of a fourth acquisition unit that acquires hospital identification information to uniquely identify a hospital.

[0086] The patient identification information acquisition unit 512 acquires the patient identification information from the card reader / writer 55 when the card reader / writer 55 reads the patient's medical card information, which includes hospital identification information and patient identification information. In this embodiment, the patient identification information acquisition unit 512 is provided as an example of a fifth acquisition unit that acquires patient identification information for uniquely identifying patients of the hospital.

[0087] The hospital determination unit 513 compares the hospital identification information acquired by the hospital identification information acquisition unit 511 with the hospital identification information pre-set in its own device and determines whether these hospital identification information matches.

[0088] The patient information acquisition unit 514 uses the patient identification information acquired by the patient identification information acquisition unit 512 to acquire patient information from the patient information management server 70. Specifically, the patient information acquisition unit 514 sends a patient information request containing the patient identification information to the patient information management server 70. Then, as a response to the patient information request, the patient information acquisition unit 514 receives a patient information response from the patient information management server 70 that contains patient information stored in association with the patient identification information.

[0089] The information output unit 515 outputs information to the card reader / writer 55, thereby controlling the card reader / writer 55 to write the information to the My Number Card. Specifically, the information output unit 515 controls the card reader / writer 55 to write the hospital identification information acquired by the hospital identification information acquisition unit 511, the patient identification information acquired by the patient identification information acquisition unit 512, and the patient information acquired by the patient information acquisition unit 514 to the My Number Card as medical card information. In this case, it is assumed that medical card information from multiple hospitals will be recorded in the publicly accessible area of ​​the My Number Card. Therefore, the information output unit 515 controls the card reader / writer 55 to write the new medical card information to an area of ​​the My Number Card where medical card information from other hospitals is not recorded. Note that a medium such as a smartphone that stores the My Number may be used instead of the My Number Card, but the following explanation will assume the use of the My Number Card. In this embodiment, an information output unit 515 is provided as an example of a recording unit that associates the hospital identification information acquired by the fourth acquisition unit with the patient identification information acquired by the fifth acquisition unit and records it on the medium on which the patient's My Number is recorded. In addition, in this embodiment, an information output unit 515 is provided as an example of a recording unit that associates the hospital identification information acquired by the fourth acquisition unit with the patient identification information acquired by the fifth acquisition unit and records it in a recording area of ​​the medium on which the patient's My Number is recorded, where hospital identification information and patient identification information related to other hospitals are not recorded.

[0090] (Configuration of the return visit registration machine) Figure 10 is a block diagram showing an example of the functional configuration of the re-registration machine 60 in the second embodiment. As shown in the figure, the re-registration machine 60 includes a control unit 61, a storage unit 62, a communication unit 63, a display operation unit 64, and a card reader 65.

[0091] The control unit 61 is equipped with an arithmetic circuit such as a CPU and controls each part of the re-registration machine 60 (communication unit 63, display operation unit 64, card reader 65, etc.) according to the operation program stored in the memory unit 62. The memory unit 62 is equipped with ROM, RAM, etc., and stores the operation program of the control unit 61. It is also used as a work area during the control processing of the control unit 61. The operation program includes a program for the control unit 61, which is a computer, to execute the processes described later. The communications unit 63 communicates information with the patient information management server 70 via the communication line 93. The display operation unit 64 and the card reader 65 have already been explained using Figure 8, so their explanation will be omitted here.

[0092] Here, the configuration of the control unit 61 will be described in detail. The control unit 61 comprises a card information acquisition unit 611, a hospital determination unit 612, a reservation information acquisition unit 613, a reception processing unit 614, and a notification processing unit 615.

[0093] The card information acquisition unit 611 acquires the card information from the card reader 65 when the card reader 65 reads the patient's card information from the patient's My Number Card. The card information includes medical examination information and beneficiary certificate information. The medical examination information is information recorded by the patient information recording device 50 and includes hospital identification information and patient identification information. As described in the first embodiment, beneficiary certificate information is information related to a beneficiary certificate, which is proof that all or part of medical expenses are covered by public funds, other than an insurance card. In this embodiment, the medical examination information and beneficiary certificate information are recorded in the publicly accessible area used to access various services on the My Number Card.

[0094] The hospital determination unit 612 compares the hospital identification information acquired by the card information acquisition unit 611 with the hospital identification information pre-set in its own device to determine whether these hospital identification information matches. Based on this determination result, the hospital determination unit 612 also extracts the patient ID information of the hospital where the re-registration machine 60 is installed from the patient ID information acquired by the card information acquisition unit 611.

[0095] The reservation information acquisition unit 613 uses the patient identification information and beneficiary certificate information acquired by the card information acquisition unit 611 to acquire the patient's reservation information from the patient information management server 70. Specifically, the reservation information acquisition unit 613 sends a reservation information request, including the patient identification information and beneficiary certificate information, to the patient information management server 70. Then, as a response to the reservation information request, the reservation information acquisition unit 613 receives a reservation information response from the patient information management server 70, which includes the reservation information stored in association with the patient identification information. Alternatively, if the beneficiary certificate information is within its validity period and matches that stored in the patient information management server 70, the reservation information acquisition unit 613 may receive a reservation information response including the reservation information from the patient information management server 70. Here, the reservation information includes information on the medical department and date and time that the patient has reserved.

[0096] The reception processing unit 614 performs reception processing using the reservation information acquired by the reservation information acquisition unit 613. Specifically, the reception processing unit 614 issues a reception number to the patient. The reception processing unit 614 may also notify the medical department included in the reservation information that the patient has returned.

[0097] The notification processing unit 615 displays notification information on the display operation unit 64 to notify the patient of predetermined information. Here, the notification information is, for example, information that the beneficiary certificate information read by the card information acquisition unit 611 from the My Number Card is outside its validity period or does not match the beneficiary certificate information stored in the patient information management server 30.

[0098] (Patient information management server configuration) Figure 11 is a block diagram showing an example of the functional configuration of the patient information management server 70 in the second embodiment. As shown in the figure, the patient information management server 70 includes a control unit 71, a storage unit 72, and a communication unit 73.

[0099] The control unit 71 is equipped with an arithmetic circuit such as a CPU and controls each part of the patient information management server 70 (communication unit 73, etc.) according to the operation program stored in the memory unit 72. The memory unit 72 is equipped with ROM, RAM, etc., and stores the operation program of the control unit 71. It is also used as a work area during the control processing of the control unit 71. The operation program includes a program for the control unit 71, which is a computer, to execute the processes described later. The communication unit 73 communicates information with the patient information recording device 50 or the re-registration machine 60 via the communication line 93.

[0100] Here, the configuration of the control unit 71 will be described in detail. The control unit 71 comprises a patient information acquisition unit 711, an information determination unit 712, and a reservation information acquisition unit 713.

[0101] The patient information acquisition unit 711 acquires patient information stored in the storage unit 72 in association with patient identification information.

[0102] When the communication unit 73 receives a reservation information request including patient identification information and beneficiary certificate information from the re-registration machine 60, the information determination unit 712 determines whether the beneficiary certificate information is within its validity period. If it determines that the beneficiary certificate information is within its validity period, it then determines whether the beneficiary certificate information matches the beneficiary certificate information stored in the storage unit 72.

[0103] If the information determination unit 712 determines that the beneficiary certificate information is within its validity period and matches the beneficiary certificate information stored in the storage unit 72, the reservation information acquisition unit 713 acquires the reservation information stored in the storage unit 72 in association with the patient identification information.

[0104] Next, we will specifically explain the information stored in the memory unit 72. The memory unit 72 stores patient management information 721.

[0105] Figure 12 shows an example of patient management information 721. As shown in the figure, patient management information 721 associates patient identification information, registration information, beneficiary certificate information, and reservation information. Patient identification information is identification information used to uniquely identify a patient. Patient identification information only needs to be unique within the hospital. Registration information includes name, date of birth, address, etc. Beneficiary certificate information includes beneficiary certificate number, name of beneficiary, etc. Appointment information includes appointment number, appointment date and time, etc. The diagram shows, for example, that patient identification information "001" has the name "〇yama 〇o", the recipient certificate number is "123456", and the appointment date and time is "November 1st, 9:00".

[0106] (Operation of the patient information management system) Figure 13 is a sequence diagram showing an example of the operation of the patient information management system 2 when recording patient information in the second embodiment.

[0107] When a patient inserts their medical card into the card slot, the patient information recording device 50 uses a card reader / writer 55 to read the medical card information from the medical card (step 531). The medical card information includes hospital identification information and patient identification information. The hospital identification information is acquired by the hospital identification information acquisition unit 511, and the patient identification information is acquired by the patient identification information acquisition unit 512. Next, in the patient information recording device 50, the hospital determination unit 513 compares the hospital identification information acquired in step 531 with the hospital identification information pre-set in the device (step 532) and determines whether these hospital identification information matches (step 533). As a result, if it is determined that these hospital identification pieces do not match, the patient information recording device 50 determines that the patient card is incorrect and terminates the process. On the other hand, if it is determined that these hospital identification pieces match, the communication unit 53, under the control of the patient information acquisition unit 514, sends a patient information request including the patient identification piece acquired in step 531 to the patient information management server 70 (step 534).

[0108] As a result, the patient information management server 70's communication unit 73 receives a patient information request from the patient information recording device 50 (step 731). The patient information request includes patient identification information and is acquired by the patient information acquisition unit 711. Next, in the patient information management server 70, the patient information acquisition unit 711 acquires patient information stored in association with the patient identification information acquired in step 731 from the storage unit 72 (step 732). Here, the patient information acquisition unit 711 only needs to acquire registered information such as the patient's name as patient information. Subsequently, under the control of the patient information acquisition unit 711, the patient information management server 70 sends a patient information response containing the patient information acquired in step 732 to the patient information recording device 50 via the communication unit 73 (step 733).

[0109] As a result, the patient information recording device 50's communication unit 53 receives a patient information response from the patient information management server 70 (step 535). The patient information response includes patient information, which is acquired by the patient information acquisition unit 514. Next, in the patient information recording device 50, the information output unit 515 controls the card reader / writer 55 to determine whether a My Number Card has been inserted into the card slot (step 536). As a result, if it is determined that a My Number Card has been inserted into the card slot, the information output unit 515 controls the card reader / writer 55 to write the hospital identification information and patient identification information obtained in step 531, and the patient information obtained in step 535, onto the My Number Card (step 537). On the other hand, if it is determined that a My Number Card was not inserted into the card slot, the patient information recording device 50 terminates processing.

[0110] Figure 14 is a sequence diagram showing an example of the operation of the patient information management system 2 when a patient returns to the clinic in the second embodiment.

[0111] When a patient inserts their My Number Card into the card slot, the re-registration machine 60 uses a card reader 65 to read card information from the My Number Card (step 641). The card information includes medical card information and beneficiary certificate information, and is acquired by the card information acquisition unit 611. The medical card information includes hospital identification information and patient identification information. The medical card information may include medical card information from multiple hospitals; in this case, all medical card information is acquired by the card information acquisition unit 611. If medical card information is not recorded on the My Number Card, the re-registration machine 60 should prompt the patient to insert a conventional magnetic medical card.

[0112] Next, in the re-registration machine 60, the hospital determination unit 612 sets the variable N to 1 in order to count the patient information (step 642). Next, the hospital determination unit 612 obtains the Nth patient card information from the patient card information obtained in step 641 (step 643). Next, the hospital identification unit 612 compares the hospital identification information contained in the Nth patient ID card information obtained in step 643 with the hospital identification information pre-set in its own device (step 644), and determines whether these hospital identification information matches (step 645).

[0113] If, as a result, it is determined that these hospital identification pieces do not match, the hospital determination unit 612 adds 1 to the variable N (step 646) and determines whether the Nth medical card information exists in the medical card information obtained in step 641 (step 647). If it is determined that the Nth medical card information exists, the hospital determination unit 612 returns to step 643. If it is determined that the Nth medical card information does not exist, it means that the medical card information of the hospital where the re-registration machine 60 is installed is not recorded on the My Number Card, and the re-registration machine 60 terminates processing. In that case, the re-registration machine 60 should guide the user to insert a conventional magnetic medical card.

[0114] On the other hand, if it is determined that these hospital identification pieces match, the communication unit 63, under the control of the reservation information acquisition unit 613, sends a reservation information request, including the patient identification piece and beneficiary certificate information acquired in step 641, to the patient information management server 70 (step 648).

[0115] As a result, the patient information management server 70's communication unit 73 receives a reservation information request from the re-registration machine 60 (step 741). The reservation information request includes patient identification information and beneficiary certificate information, and is acquired by the information determination unit 712. Next, in the patient information management server 70, the information determination unit 712 determines whether the beneficiary certificate information obtained in step 741 is within its validity period (step 742). For example, the beneficiary certificate information may include information that is within its validity period, and the information determination unit 712 may make this determination based on whether the current date falls within this validity period.

[0116] As a result, if it is determined that the beneficiary certificate information obtained in step 741 is within its validity period, the information determination unit 712 determines whether the beneficiary certificate information obtained in step 741 matches the beneficiary certificate information stored in the storage unit 72 (step 743). If it is determined that the beneficiary certificate information obtained in step 741 matches the beneficiary certificate information stored in the storage unit 72, the reservation information acquisition unit 713 acquires the reservation information stored in association with the patient identification information obtained in step 741 from the storage unit 72 (step 744). Subsequently, under the control of the reservation information acquisition unit 713, the patient information management server 70 sends a reservation information response containing the reservation information acquired in step 744 to the re-registration machine 60 via the communication unit 73 (step 745).

[0117] As a result, the communication unit 63 of the re-registration machine 60 receives a reservation information response from the patient information management server 70 (step 649). The reservation information response includes reservation information, which is acquired by the reservation information acquisition unit 613. Then, in the re-registration machine 60, the registration processing unit 614 uses the reservation information obtained in step 649 to perform patient registration processing (step 650). Registration processing includes, for example, adding the patient to the waiting line for the reserved time slot in the medical department for which the patient made a reservation.

[0118] On the other hand, consider the case in step 742 where it is determined that the beneficiary certificate information obtained in step 741 is outside its validity period, or in step 743 where it is determined that the beneficiary certificate information obtained in step 741 does not match the beneficiary certificate information stored in the storage unit 72. In this case, the patient information management server 70, under the control of the information determination unit 712, has the communication unit 73 send a beneficiary certificate renewal request to the re-registration machine 60 requesting the renewal of the beneficiary certificate (step 746).

[0119] As a result, the communication unit 63 of the re-registration machine 60 receives a request for renewal of the beneficiary certificate from the patient information management server 70 (step 651). The request for renewal of the beneficiary certificate is acquired by the notification processing unit 615. Then, in the re-registration machine 60, the notification processing unit 615 displays notification information about the renewal of the beneficiary certificate on the display operation unit 64 (step 652). The display operation unit 64 then displays information about the renewal of the beneficiary certificate. Specifically, since the beneficiary certificate cannot be automatically renewed, the display operation unit 64 displays instructions on how to go to the counter to renew the beneficiary certificate.

[0120] (modified version) In the above example, the re-registration machine 60 reads all patient information from the My Number Card, but this is not the only option. The re-registration machine 60 may also read patient information one by one from the My Number Card, that is, for each hospital, and read the next patient information only if the hospital identification information does not match.

[0121] The above example shows a patient information management system 2 equipped with a re-registration machine 60, which uses the medical card information recorded on the My Number Card. However, this is not the only option. The patient information management system 2 may also be equipped with a medical fee payment machine, which uses the medical card information recorded on the My Number Card. In that case, the patient information management system 2 would perform the same operations as shown in Figure 14. Specifically, the medical fee payment machine first performs the processing in steps 641 to 646. If, as a result, it is determined in step 645 that the hospital identification information matches, the medical fee payment machine sends a billing information request, including patient identification information, to the patient information management server 70. As a result, the patient information management server 70 receives a billing information request from the medical fee payment machine. Next, the patient information management server 70 retrieves the billing information stored in association with the patient identification information. Subsequently, the patient information management server 70 sends a billing information response containing the billing information to the medical fee payment machine. As a result, the medical fee payment machine receives a billing information response from the patient information management server 70. The medical fee payment machine then uses the acquired billing information to process the payment of the patient's medical fees. At that time, the medical fee payment machine compares the name contained in the patient's medical card information with the name set in the billing information response. In other words, the medical fee payment machine performs identity verification. If the names match, the medical fee payment machine processes the payment.

[0122] The above describes the application of the present invention to the medical industry, but it is not limited to this. For example, the present invention can also be applied to other industries where membership cards exist, such as the lodging industry and the rental industry.

[0123] (effect) According to the second embodiment, the cost of issuing medical cards can be reduced, and furthermore, it eliminates the need to carry multiple medical cards.

[0124] [Third Embodiment] (overview) The third embodiment is a medical card number inquiry service using My Number Cards. When a My Number Card is held over a reader instead of a medical card, the unique information of the My Number Card and the terminal information of the device over which it is held are transmitted to inquire about the medical card number. The inquiry destination has previously registered correspondence information between the unique information of the My Number Card, the terminal information of the device, and the medical card number, and responds with the medical card number based on this correspondence information. In the following explanation, the device over which the My Number Card is held will be referred to as a re-registration machine, and the inquiry destination will be referred to as a server device.

[0125] (Overall structure of the patient ID number inquiry system) Figure 15 shows an example of the overall configuration of the patient ID number inquiry system 3 in the third embodiment. As shown in the figure, the patient ID number inquiry system 3 includes re-registration machines 81a, 81b, and 81c, and a server device 82. The re-registration machines 81a, 81b, and 81c and the server device 82 are connected via a communication line 94. It is assumed that the re-registration machines 81a, 81b, and 81c are installed in, for example, hospitals A, B, and C, respectively, but if they are not distinguished, they will be referred to as re-registration machine 81.

[0126] The re-registration machine 81 is installed, for example, around the reception desk of a medical institution, and is a device that registers patients as re-visiting patients when they return to the clinic after having made an appointment for a consultation during their previous visit. The server device 82 is a computer device that stores correspondence information for each patient, which associates the unique information of the My Number Card with the terminal information of the re-registration machine 81 and the patient's medical card number. The communication line 94 is a line for exchanging information between the re-registration machine 81 and the server device 82. While not limited to this, the communication line 94 could, for example, use the internet.

[0127] Figure 16 is a diagram showing a specific example of correspondence information held by the server device 82. In the diagram, the unique information of the My Number Card is abbreviated as "card-specific information". The diagram shows, for example, that the patient ID number of Hospital A, "12345", can be obtained based on the unique information of the My Number Card, "234587156", and the terminal information of the re-registration machine 81a of Hospital A, "Zdkl1523".

[0128] (Operation of the patient ID number inquiry system) In the third embodiment, the patient ID number inquiry system 3 performs the following processing steps. Although registration may be done at the counter, the following explanation will use the case where registration is done at the re-registration machine 10 as an example. (1) The patient performs the registration procedure using the re-registration machine 81. (2) When the patient uses their medical card to perform the registration procedure, the re-registration machine 10 proceeds with the registration process. (3) When a patient uses their My Number Card to perform the registration procedure, the re-registration machine 10 queries the server device 82. In other words, the re-registration machine 10 transmits the unique information of the My Number Card and the terminal information of the re-registration machine 81 to the server device 82. (4) The server device 82 identifies the patient ID number from the above correspondence information and sends it back to the re-registration machine 81. (5) The re-registration machine 81 processes the registration based on the returned patient ID number.

[0129] (modified version) In the above example, My Number was used as the unique information on the My Number Card, but other information such as facial features, address, and name may also be used as long as it is unique. In the above example, a pre-registered terminal number was used as the terminal information for the device to which the My Number Card is held, but other information such as GPS data may also be used.

[0130] (effect) According to the third embodiment, the following effects can be obtained. (1) For patients who visit multiple medical institutions, this eliminates the need to carry around numerous medical cards. (2) Patients who do not visit multiple medical institutions can continue to use their existing patient registration card. (3) The hospital also does not need to make significant changes to its existing system and can easily adapt to the situation. (4) When the My Number Card is given the function of an insurance card, everything can be completed with just one My Number Card. (5) Hospitals can reduce the cost of issuing patient cards, and patients will not have to pay a fee for reissuing their patient cards if they lose them.

[0131] [Fourth Embodiment] (overview) The fourth embodiment involves a system in which a patient selects a pharmacy (hereinafter also simply referred to as "pharmacy") when paying for medical treatment, and transmits prescription information to the selected pharmacy, allowing processing at the pharmacy to begin in advance. At this time, information for each pharmacy is displayed when the patient selects a pharmacy, enabling them to make the optimal choice. It is also possible to reserve a pickup time at the pharmacy. Furthermore, this pharmacy selection and transmission of prescription information can be performed using an application on a mobile device such as a smartphone. When using a mobile device in this manner, it is also possible to obtain prescription information from a QR code (registered trademark) on the prescription.

[0132] (Overall structure of the pharmacy selection system) Figure 17 shows an example of the overall configuration of the pharmacy selection system 4 in the fourth embodiment. As shown in the figure, the pharmacy selection system 4 includes a medical fee payment machine 86, a mobile terminal 87, pharmacy terminals 88a, 88b, and 88c, and a server device 89. The medical fee payment machine 86, the pharmacy terminals 88a, 88b, and 88c, and the server device 89 are connected via a communication line 95. The mobile terminal 87 is also connected to the communication line 95 via wireless communication. It is assumed that the pharmacy terminals 88a, 88b, and 88c are installed in pharmacy A, pharmacy B, and pharmacy C, respectively, but if they are not distinguished, they will be referred to as pharmacy terminal 88.

[0133] The medical fee payment machine 86 is installed, for example, near the settlement counter of a medical institution, and is a device that displays the amount of medical fees to patients who have received medical treatment and receives payment of medical fees from patients. In this embodiment, the medical fee payment machine 86 is also used to allow patients to select a dispensing pharmacy and transmit prescription information after they have paid their medical fees. The mobile terminal 87 is a terminal device carried by the patient. In this embodiment, the mobile terminal 87 is used to select a dispensing pharmacy and transmit prescription information after the patient has paid the medical fees at the medical fee payment machine 86. For example, a smartphone can be used as the mobile terminal 87. The pharmacy terminal 88 is a terminal device installed in a pharmacy that receives prescription information transmitted from the medical fee payment machine 86 or the mobile terminal 87. The server device 89 is a computer device that manages information related to dispensing pharmacies, provides that information to the medical fee payment machine 86 or mobile terminal 87, and mediates the transmission of prescription information from the medical fee payment machine 86 or mobile terminal 87 to the dispensing pharmacy terminal 88. The communication line 95 is a line for communicating information between the medical fee payment machine 86, the mobile terminal 87, or the pharmacy terminal 88 and the server device 89. While not limited to these, the communication line 95 could, for example, use the internet.

[0134] (Operation of the pharmacy selection system) In the fourth embodiment, the pharmacy selection system 4 performs the following processing steps. In reality, the server device 89 transmits information to the medical fee payment machine 86 or the mobile terminal 87, and receives information from the medical fee payment machine 86 or the mobile terminal 87 and transmits it to the pharmacy terminal 88. However, in the following description, only the processing performed by the medical fee payment machine 86, the mobile terminal 87, and the pharmacy terminal 88 will be explained.

[0135] First, we will explain the case where the patient selects a dispensing pharmacy using the medical fee payment machine 86 and transmits the prescription information. (1) The patient performs the operation to pay the medical fees using the medical fee payment machine 86. (2) The medical fee payment machine 86 displays a screen for selecting a dispensing pharmacy. The medical fee payment machine 86 also displays information about each dispensing pharmacy. This information about each dispensing pharmacy includes, for example, its location or distance from the current location, basic fee, and features (selling points, service details, etc.). (3) The patient selects a dispensing pharmacy at the medical fee payment machine 86 and enters an instruction to send prescription information. This instruction to send prescription information may also be entered as an appointment to pick up the medication. (4) At the dispensing pharmacy, the dispensing terminal 88 receives prescription information.

[0136] Next, we will explain the case where the patient selects a pharmacy using the mobile device 87 and sends the prescription information. (1) The patient opens the reservation app on the mobile device 87. The hospital where the patient received treatment may be identified by selecting it on the mobile device 87, or it may be identified based on GPS information. (2) The patient scans the QR code on the prescription with their mobile device 87. (3) The mobile terminal 87 displays a screen for selecting a dispensing pharmacy. The mobile terminal 87 also displays information about each dispensing pharmacy. This information about each dispensing pharmacy may include, for example, its location or distance from the current location, basic fee, and features (selling points, service details, etc.). (4) The patient selects a pharmacy on the mobile terminal 87 and enters an instruction to send prescription information. This instruction to send prescription information may also be entered as an appointment to pick up the medication. (5) At the dispensing pharmacy, the dispensing terminal 88 receives prescription information.

[0137] Figure 18 shows specific examples of the pharmacy selection screen displayed when using the medical fee payment machine 86 (2) and when using the mobile terminal 87 (3). In the figure, for example, Pharmacy A is shown to be characterized (selling points) by being 10m away from the current location, having a basic fee of 450 points, and having 3 pharmacists. The pharmacy selection screen may also display that pharmacy F is closed on that day. Alternatively, although not shown in the figure, the waiting time at each pharmacy may also be displayed on the pharmacy selection screen.

[0138] When prescription information is sent to a pharmacy from a screen like this, the patient begins their journey to the pharmacy. Meanwhile, the pharmacy begins preparing to accept the prescription based on the prescription information. After the patient arrives at the pharmacy, the pharmacist at the pharmacy performs the main processing of the prescription (medical interview, insurance card verification, etc.). The pharmacist then dispenses and explains the medication and handles the payment process.

[0139] (modified version) The above example allows users to schedule medication pickup when submitting prescription information, but this is not the only option. Instead of confirming a reservation simply by viewing the basic fee on the pharmacy selection screen, users could be required to confirm the reservation only after receiving a final price estimate from the selected pharmacy. In the above example, the search target was pharmacies, but the search target could also be nursing homes or ride-hailing service companies such as taxis.

[0140] (effect) According to the fourth embodiment, the following effects can be obtained. (1) Since the selection of a dispensing pharmacy and transmission of prescription information can be performed immediately after the mandatory settlement process at the hospital, the efficiency of receiving medication is improved. Furthermore, if the medical fee payment machine 86 is configured to allow the selection of a dispensing pharmacy and transmission of prescription information, even elderly people who do not have a mobile device such as a smartphone 87 can easily receive medication. (2) Patients can check information about pharmacies in advance (location, basic fees, services, etc.), allowing them to choose a pharmacy that meets their needs. (3) Pharmacies can promote the unique features of their own pharmacy, which is expected to lead to the acquisition of new customers. [Explanation of Symbols]

[0141] 1,2...Patient information management system, 10...Return visit registration machine, 111...Card information acquisition unit, 112...Eligibility information acquisition unit, 113...Reservation information acquisition unit, 114...Reception processing unit, 115...Notification processing unit, 116...Confirmation processing unit, 20...Medical fee payment machine, 211...Card information acquisition unit, 212...Eligibility information acquisition unit, 213...Billing information acquisition unit, 214...Payment processing unit, 30...Patient information management server, 311...Information determination unit, 312...Reservation information acquisition unit, 313...Insurance card information update unit, 314...Billing information Information acquisition unit, 40…Online eligibility verification system, 50…Patient information recording device, 511…Hospital identification information acquisition unit, 512…Patient identification information acquisition unit, 513…Hospital determination unit, 514…Patient information acquisition unit, 515…Information output unit, 60…Return visit reception machine, 611…Card information acquisition unit, 612…Hospital determination unit, 613…Reservation information acquisition unit, 614…Reception processing unit, 615…Notification processing unit, 70…Patient information management server, 711…Patient information acquisition unit, 712…Information determination unit, 713…Reservation information acquisition unit

Claims

1. A storage unit that stores patient reservation information in association with patient identification information that uniquely identifies the patient, including the patient's insurance card number, A qualification information acquisition unit obtains qualification information from an online qualification verification system in order to verify the insured status of the patient using a medium on which the patient's My Number is recorded. A first acquisition unit that acquires the patient's insurance card number included in the qualification information acquired by the qualification information acquisition unit, A second acquisition unit acquires the reservation information associated with the patient identification information, including the insurance certificate number, from the storage unit using the insurance certificate number acquired by the first acquisition unit, A reception processing unit that uses the reservation information acquired by the second acquisition unit to process the acceptance of a consultation request from the patient, A patient information management system equipped with the following features.

2. A storage unit that stores patient information relating to a patient in association with patient identification information for uniquely identifying the patient, which includes the patient's insurance card number, A first acquisition unit that uses a medium on which the patient's My Number is recorded to obtain the patient's insurance card number from an online eligibility verification system, A second acquisition unit acquires patient information associated with the patient identification information, including the insurance certificate number, from the storage unit using the insurance certificate number acquired by the first acquisition unit, If the insurance card number of a specific patient is not stored in the memory unit, the inquiry unit inquires with the specific patient whether or not the insurance card information of that patient has been changed. Equipped with, The memory unit stores the patient information in association with the patient's name information. The first acquisition unit acquires the patient's name information from the online eligibility verification system using a medium on which the patient's My Number is recorded. The aforementioned inquiry unit, if the insurance card number of a specific patient is not stored in the storage unit, and if the name information of the specific patient obtained by the first acquisition unit is stored in the storage unit, inquires with the specific patient whether or not the insurance card information of the specific patient has been changed, in a patient information management system.

3. A storage unit that stores patient information relating to a patient in association with patient identification information that uniquely identifies the patient and includes the patient's insurance card number, A first acquisition unit that uses a medium on which the patient's My Number is recorded to obtain the patient's insurance card number from an online eligibility verification system, A second acquisition unit acquires patient information associated with the patient identification information, including the insurance certificate number, from the storage unit using the insurance certificate number acquired by the first acquisition unit, A third acquisition unit that acquires information regarding the receipt of publicly funded benefits for the patient from a medium on which the patient's My Number is recorded, Equipped with, A patient information management system in which the second acquisition unit acquires, if the patient's insurance card number is stored in the storage unit, and the patient's benefit information acquired by the third acquisition unit is within its validity period and is stored in the storage unit in association with the patient's insurance card number, the second acquisition unit acquires, from the storage unit, the patient information associated with the patient identification information including the insurance card number.

4. The patient information management system according to claim 3, further comprising a notification unit that notifies the patient if the patient's benefit information acquired by the third acquisition unit is outside its validity period.

5. The patient information management system according to claim 3, further comprising a notification unit for notifying a patient if the patient's benefit information acquired by the third acquisition unit is not stored in the storage unit in association with the patient's insurance card number.

6. A qualification information acquisition unit obtains qualification information from an online qualification verification system in order to verify the patient's eligibility as an insured person using a medium on which the patient's My Number is recorded. A first acquisition unit that acquires the patient's insurance card number included in the qualification information acquired by the qualification information acquisition unit, A second acquisition unit uses the insurance card number acquired by the first acquisition unit to acquire patient identification information for uniquely identifying the patient, which includes the insurance card number, and the patient's reservation information associated with the patient identification information, from the hospital system. A reception processing unit that uses the reservation information acquired by the second acquisition unit to process the acceptance of a consultation request from the patient, A reception device equipped with the following features.

7. The computer stores patient reservation information in a memory unit, associating it with patient identification information that uniquely identifies the patient and includes the patient's insurance card number. The computer obtains eligibility information from an online eligibility verification system in order to verify the patient's eligibility as an insured person, using a medium on which the patient's My Number is recorded. The computer obtains the patient's insurance card number included in the acquired credentials, The computer uses the acquired insurance card number to obtain the reservation information associated with the patient identification information, including the insurance card number, from the storage unit. The computer processes the acceptance of the patient's request for a medical examination using the acquired reservation information. A patient information management method, including the following.

8. A storage unit that stores patient reservation information in association with patient identification information which is patient identification information for uniquely identifying the patient and does not include My Number, A qualification information acquisition unit obtains qualification information from an online qualification verification system in order to verify the insured status of the patient using a medium on which the patient's My Number is recorded. A first acquisition unit that acquires patient identification information of the patient included in the qualification information acquired by the qualification information acquisition unit, A second acquisition unit acquires the reservation information associated with the patient identification information from the storage unit using the patient identification information acquired by the first acquisition unit, A reception processing unit that uses the reservation information acquired by the second acquisition unit to process the acceptance of a consultation request from the patient, A patient information management system equipped with the following features.

9. A qualification information acquisition unit that acquires qualification information from an online qualification verification system in order to verify the patient's eligibility as an insured person using a medium on which the patient's My Number is recorded, A first acquisition unit acquires patient identification information, which is patient identification information for uniquely identifying the patient and does not include My Number, that is included in the qualification information acquired by the qualification information acquisition unit. A second acquisition unit obtains the patient's reservation information associated with the patient's identification information from the hospital system using the patient identification information obtained by the first acquisition unit, A reception processing unit that uses the reservation information acquired by the second acquisition unit to process the acceptance of a consultation request from the patient, A reception device equipped with the following features.

Citation Information

Patent Citations

  • Integral electronic medical record system, electronic medical record server, and individual electronic medical record system

    JP2003186997A

  • Health insurance information management system

    JP2013077208A

  • Medical examination support system, medical examination support method, and medical examination support program

    JP2014157416A

  • Patient information management system, and reception device to be used in the patient information management system

    JP2017151732A