Medical record management system, medical record management method and program

Abstract

This invention provides a medical record management system, a medical record management method, and a program that enable patients and healthcare professionals to easily and effectively utilize medical records. [Solution] The medical record management system 1 includes an authentication ID acquisition unit 501 (701) that acquires an authentication ID for a patient, a patient identification unit 503 (703) that identifies a patient ID based on the authentication ID, a first medical record management unit 303 that stores medical records associated with the patient ID in a storage area on the network, a medical record registration unit 507 (707) that registers the medical data in the first medical record management unit, and a medical record acquisition unit 505 (705) that acquires the medical data from the first medical record management unit. The authentication ID acquisition unit 501 (701) acquires the authentication ID stored in a predetermined recording medium by contactless communication.

Description

Technical Field

[0001] The present invention relates to a medical record management system, a medical record management method, and a program.

Background Art

[0002] There has been proposed a system for centrally managing records (hereinafter referred to as medical records) regarding examinations, prescriptions, dispensations, etc. (hereinafter referred to as medical acts) performed on patients in hospitals, clinics, dispensaries, or clinics (hereinafter referred to as medical institutions) or pharmacies (hereinafter referred to as pharmacies) on a network and allowing authorized doctors, pharmacists, etc. (hereinafter referred to as medical personnel) to access them.

[0003] For example, Patent Document 1 describes managing the history of prescribing or dispensing drugs to patients in a prescription drug data management device installed on a network. According to Patent Document 1, until now, patients carried a single medicine notebook and had the history of prescribing or dispensing recorded in the medicine notebook at medical institutions or pharmacies. However, patients may forget to carry the medicine notebook, and the medicine notebook may be lost due to loss, disaster, etc. Therefore, the device described in Patent Document 1 is configured to be able to view medical records stored in a database on the network by inputting authentication information of patients, medical personnel, etc. even if the patient does not carry the medicine notebook.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in the invention described in Patent Document 1, all medical records are stored in a network database, making them inaccessible offline like traditional paper medication notebooks. While it can be used in conjunction with traditional paper medication notebooks, this results in redundant storage of medical records in different ways, which is inefficient. Furthermore, accessing online medical records requires managing authentication information for each individual. For example, when receiving medical treatment, patients need to remember their own authentication information. Similarly, when parents have their children receive medical treatment, the parents also need to remember their children's authentication information. This is extremely cumbersome. Moreover, online medical records are primarily used only for viewing by medical professionals.

[0006] This invention was made to solve these problems and aims to provide a medical record management system, a medical record management method, and a program that enable patients and medical professionals to easily and effectively utilize medical records. [Means for solving the problem]

[0007] According to one embodiment, the medical record management system includes an authentication ID acquisition unit that acquires an authentication ID for a patient, a patient identification unit that identifies a patient ID based on the authentication ID, a first medical record management unit that stores medical records associated with the patient ID in a storage area on the network, a medical record registration unit that registers the medical data in the first medical record management unit, and a medical record acquisition unit that acquires the medical data from the first medical record management unit. The authentication ID acquisition unit acquires the authentication ID stored in a predetermined recording medium by contactless communication. According to one embodiment, in a medical record management system, the authentication ID acquisition unit acquires the authentication ID by performing biometric authentication in lieu of or in conjunction with contactless communication. According to one embodiment, in a medical record management system, the medical record is dispensing data from a pharmacy. According to one embodiment, in a medical record management system, the medical record is prescription data from a medical institution. According to one embodiment, the medical record management system further includes a points calculation unit that calculates insurance medical service points based on the medical records. According to one embodiment, the medical record management system further includes an accounting calculation unit that calculates accounting amounts based on the medical records. According to one embodiment, the medical record management system further includes an accounting processing unit that receives the accounting amount and performs cashless payment. According to one embodiment, the medical record management system has a second medical record management unit that stores the medical records in the patient's terminal device, and the second medical record management unit stores the medical records relating to a plurality of patient IDs. According to one embodiment, in a medical record management system, the medical record registration unit registers prescription data generated at the medical institution, and the medical record acquisition unit acquires the prescription data at the pharmacy. According to one embodiment, in a medical record management system, the medical record registration unit displays the results of duplicate prescriptions, drug interactions, side effects, or allergy checks related to the medical record to be registered. According to one embodiment, the medical record management system includes a location detection unit that detects the current location of the patient's terminal device, a pharmacy identification unit that identifies a pharmacy located near the current location, an inventory management unit that manages the inventory of drugs at the pharmacy, an inventory confirmation unit that queries the inventory management branch for the drug inventory included in the prescription data recorded in the first medical record management unit, and an inventory information provision unit that distributes information about the pharmacy and information about the drug inventory to the patient's terminal device. According to one embodiment, the medical record management method includes an authentication ID acquisition step of acquiring an authentication ID for a patient; a patient identification step of identifying a patient ID based on the authentication ID; a medical record registration step of registering the medical data with a first medical record management unit that stores the medical records associated with the patient ID in a storage area on a network; and a medical record acquisition step of acquiring the medical data from the first medical record management unit. In the authentication ID acquisition step, the authentication ID stored on a predetermined recording medium is acquired by contactless communication. According to one embodiment, the program causes the computer to execute the above method. [Effects of the Invention]

[0008] The present invention provides a medical record management system, a medical record management method, and a program that enable patients and medical professionals to easily and effectively utilize medical records. [Brief explanation of the drawing]

[0009] [Figure 1] This is a diagram illustrating the overview of Medical Record Management System 1. [Figure 2] This is a block diagram showing an example of the functional configuration of Medical Record Management System 1. [Figure 3] This flowchart shows an example of the operation of the medical record management system 1. [Figure 4] This flowchart shows an example of the operation of the medical record management system 1. [Figure 5] This flowchart shows an example of the operation of the medical record management system 1. [Figure 6] This is a block diagram showing an example of the functional configuration of Medical Record Management System 1. [Figure 7] This flowchart shows an example of the operation of the medical record management system 1. [Modes for carrying out the invention]

[0010] Hereinafter, specific embodiments to which the present invention is applied will be described in detail with reference to the drawings.

[0011] <Embodiment 1> Figure 1 is a diagram illustrating the outline of a medical record management system 1 according to Embodiment 1 of the present invention. The medical record management system 1 includes a patient terminal 10 used by patients, a management device 30, a medical institution terminal 50 used by medical institutions, and a pharmacy terminal 70 used by pharmacies. The management device 30 is connected to the patient terminal 10, the medical institution terminal 50, and the pharmacy terminal 70 via a network 90 so as to be able to communicate with them.

[0012] The patient terminal 10 is typically an information processing device such as a smartphone, tablet, or wearable device. The medical institution terminal 50 or pharmacy terminal 70 is typically an information processing device such as a tablet or PC (personal computer). The management device 30 is typically an information processing resource accessible via a network 90, such as a server computer, cloud computing environment, edge computing environment, or fog computing environment. These information processing devices (information processing environments) include hardware such as a CPU (central processing unit), storage device, communication device, display device, and input device, and the CPU can read and execute programs stored in the storage device to realize predetermined functions as shown below.

[0013] FIG. 2 is a block diagram showing the functional configuration of the medical record management system 1 according to Embodiment 1. The medical record management system 1 includes an authentication ID storage unit 101, a medical record management unit 103, an accounting processing unit 105, a patient ID acquisition unit 301, a medical record management unit 303, a score calculation unit 305, an accounting calculation unit 307, an authentication ID acquisition unit 501, a patient identification unit 503, a medical record acquisition unit 505, a medical record registration unit 507, a score processing unit 509, an accounting processing unit 511, an authentication ID acquisition unit 701, a patient identification unit 703, a medical record acquisition unit 705, a medical record registration unit 707, a score processing unit 709, and an accounting processing unit 711. Hereinafter, typical implementation examples of each processing unit will be shown. However, basically, it is arbitrary which hardware each processing unit is implemented on, and for example, a certain processing unit may be implemented in a distributed manner on a plurality of hardware.

[0014] The patient terminal 10 includes an authentication ID storage unit 101 and a medical record management unit 103.

[0015] The authentication ID storage unit 101 stores an authentication ID (identifier). Typically, an NFC (Near Field Communication) chip can be used as the authentication ID storage unit 101. The NFC chip can send out a unique identifier (authentication ID) stored in advance by non-contact communication. The authentication ID is typically device-specific, but may be arbitrarily set by an application program. The NFC chip can be built into not only information processing devices such as smartphones, tablets, and wearable terminals, but also plastic cards. Note that instead of the NFC chip, any short-range wireless transfer technology including RFID, Bluetooth (registered trademark), TransferJet, etc. may be adopted. Alternatively, the authentication ID storage unit 101 may send out the authentication ID stored in advance by displaying a visible code such as a QR code (registered trademark).

[0016] The medical record management unit 103 stores the medical records of patients. The medical records are replicated from the medical record management unit 303 of the management device 30. Then, the medical record management unit 103 displays the medical records of the patients on the display device. The medical records may include, for example, prescription data registered by a medical institution (records of prescription details for patients), examination data (records related to examinations of patients), care performance data (records related to care for patients), dispensing data registered by a pharmacy (records of dispensing details for patients), etc. For example, when handling dispensing data, the medical record management unit 103 can store and display the history of past dispensings for patients, similar to a conventional medicine notebook.

[0017] The accounting processing unit 105 obtains the accounting amount for newly registered medical records from the accounting calculation unit 307 of the management device 30. That is, the accounting calculation unit 307 of the management device 30 automatically calculates the amount that the patient should pay to the medical institution or pharmacy regarding the newly registered medical records and notifies the accounting processing unit 105. The accounting processing unit 105 receives the obtained accounting amount from the patient. For example, the accounting processing unit 105 has a function of accepting payments made by the patient using a credit card, debit card, electronic money, other payment agency services, etc., and performs cashless settlement of the accounting amount through this function.

[0018] The medical institution terminal 50 includes an authentication ID acquisition unit 501, a patient identification unit 503, a medical record acquisition unit 505, a medical record registration unit 507, a score processing unit 509, and an accounting processing unit 511.

[0019] The authentication ID acquisition unit 501 reads the authentication ID from the authentication ID storage unit 101 of the patient terminal 10. Typically, an NFC reader can be used as the authentication ID acquisition unit 501, but other short-range wireless communication technologies may also be used.

[0020] The patient identification unit 503 identifies the individual patient based on the authentication ID. For example, the patient identification unit 503 holds a table associating the authentication ID with the patient ID that identifies the individual patient, and identifies the patient ID from the authentication ID by referring to this table.

[0021] The medical record acquisition unit 505 acquires medical records corresponding to the patient ID from the medical record management unit 303 of the management device 30 and displays them on the display device.

[0022] The medical record registration unit 507 accepts input of medical records from medical professionals. The medical records entered here are records of medical procedures performed on patients at medical institutions and pharmacies, specifically including prescription data, test data, care record data, dispensing data, etc. The medical record registration unit 507 registers the entered medical records in the medical record management unit 303 of the management device 30.

[0023] The points processing unit 509 obtains the insurance points for the medical record that was just registered from the points calculation unit 305 of the management device 30. That is, the points calculation unit 305 of the management device 30 automatically calculates the insurance points for the newly registered medical record and notifies the points processing unit 509. The points processing unit 509 then transmits the obtained points to the computer of the insurer (health insurance association, etc.).

[0024] The accounting processing unit 511 obtains the accounting amount for the medical record registered in this instance from the accounting calculation unit 307 of the management device 30. That is, the accounting calculation unit 307 of the management device 30 automatically calculates the amount that the patient should pay to the medical institution or pharmacy for the newly registered medical record and notifies the accounting processing unit 511. The accounting processing unit 511 receives the obtained accounting amount from the patient. For example, the accounting processing unit 511 has a function to accept payments from patients using credit cards, debit cards, electronic money, and other payment processing services, and uses this function to process the accounting amount as a cashless payment.

[0025] The settlement of the payment amount may be performed either by the accounting processing unit 105 of the patient terminal 10 or by the accounting processing unit 511 of the medical institution terminal 50. In other words, the patient may complete the cashless payment on their own smartphone, or they may use the medical institution's terminal to make the cashless payment.

[0026] The pharmacy terminal 70 includes an authentication ID acquisition unit 701, a patient identification unit 703, a medical record acquisition unit 705, a medical record registration unit 707, a points processing unit 709, and an accounting processing unit 711. The functions of these processing units are the same as those of the authentication ID acquisition unit 501, patient identification unit 503, medical record acquisition unit 505, medical record registration unit 507, points processing unit 509, and accounting processing unit 511 of the medical institution terminal 50, so their explanation is omitted.

[0027] The management device 30 includes a patient ID acquisition unit 301, a medical record management unit 303, a points calculation unit 305, and an accounting calculation unit 307.

[0028] The patient ID acquisition unit 301 acquires the patient ID from the patient identification unit 503 of the medical institution terminal 50.

[0029] The medical record management unit 303 stores patient IDs in association with the medical records relating to those patients. The medical record management unit 303 transmits the medical records corresponding to the specified patient ID in response to a request from the medical record acquisition unit 505 of the medical institution terminal 50. The medical record management unit 303 also receives medical records sent from the medical record registration unit 507 of the medical institution terminal 50 and stores them in association with the specified patient ID.

[0030] In addition, when a new medical record for a patient is registered, the medical record management unit 303 copies the new medical record to the medical record management unit 103 on the patient's terminal 10. This allows the patient to view their latest medical record at any time on their smartphone or other device.

[0031] The points calculation unit 305 automatically calculates the insurance points for newly registered medical records. Typically, the points calculation unit 305 maintains a correspondence table between the content of medical procedures such as examinations, prescriptions, nursing care, and dispensing, and the corresponding insurance medical points, and performs the above calculation by referring to this table. The points calculation unit 305 notifies the points processing unit 509 of the medical institution terminal 50 of the calculation result.

[0032] The accounting unit 307 automatically calculates the accounting amount for newly registered medical records. Here, the accounting amount refers to the amount payable by the patient to the medical institution. Typically, the accounting unit 307 maintains a correspondence table between the content of medical procedures such as examinations, prescriptions, nursing care, and dispensing, and the corresponding patient co-payment, and provisionally calculates the patient co-payment by referring to this table. In addition, in the case of insured medical treatment, there may be a monthly limit on the patient co-payment. In this case, the accounting unit 307 records the cumulative amount of the patient co-payment for the current month for each patient, and if the current payment exceeds the limit, the actual patient co-payment is the amount obtained by subtracting the amount exceeding the limit from the provisionally calculated patient co-payment. The accounting unit 307 notifies the accounting processing unit 105 of the patient terminal 10 or the accounting processing unit 511 of the medical institution terminal 50 of the calculation result.

[0033] Figure 3 is a flowchart illustrating the operation of the medical record management system 1 according to Embodiment 1. Here, we will explain using the example of a case where one patient receives medication at one pharmacy.

[0034] S101: Presentation of identification ID The patient holds their smartphone (patient terminal 10) over an NFC reader (authentication ID acquisition unit 701) installed in the pharmacy. The smartphone (patient terminal 10) has a built-in NFC chip (authentication ID storage unit 101), and the authentication ID is stored in the NFC chip (authentication ID storage unit 101). The NFC reader (authentication ID acquisition unit 701) reads the authentication ID from the NFC chip (authentication ID storage unit 101).

[0035] The pharmacy may use biometric authentication means instead of the NFC reader (authentication ID acquisition unit 701). For example, the facial recognition system extracts features from the patient's facial image captured by the camera and outputs the features or information generated based on the features as an authentication ID.

[0036] Alternatively, the pharmacy may use an NFC reader (authentication ID acquisition unit 701) in combination with a biometric authentication method. For example, the NFC reader (authentication ID acquisition unit 701) reads the patient's face image that is pre-stored on the NFC card. The facial recognition system compares the feature quantities extracted from the patient's face image captured by the camera with the feature quantities extracted from the face image read from the NFC card. If the two match, the NFC reader (authentication ID acquisition unit 701) reads the authentication ID from the NFC chip (authentication ID storage unit 101).

[0037] S102: Patient identification The NFC reader (authentication ID acquisition unit 701) transmits the read authentication ID to the patient identification unit 703 of the PC (pharmacy terminal 70). The patient identification unit 703 identifies the patient ID corresponding to the authentication ID.

[0038] S103: Access to medical records The pharmacy dispenses medication to the patient. In this example, it is assumed that the patient brings a paper prescription issued by a medical institution to the pharmacy, and the pharmacist visually checks the paper prescription before dispensing the medication. When dispensing, the pharmacy uses the medical record acquisition unit 705 of the PC (pharmacy terminal 70) to check the patient's past dispensing history.

[0039] The medical record acquisition unit 705 transmits the patient ID to the cloud service (management device 30) that manages medical records. The patient ID acquisition unit 301 of the cloud service (management device 30) receives the patient ID, and the medical record management unit 303 transmits the past medical records corresponding to the patient ID to the medical record acquisition unit 705. The medical record acquisition unit 705 displays the acquired medical records on the screen.

[0040] S104: Registration of medical records The pharmacy uses the medical record registration unit 707 of the PC (pharmacy terminal 70) to register the details of the current prescription (medical record) for the patient. The prescription details include information such as the date of prescription, the name and quantity of the medication. The medical record acquisition unit 705 transmits the prescription details and patient ID to the medical record management unit 303 of the cloud service (management device 30). The medical record management unit 303 stores the received patient ID and prescription details in association.

[0041] S105: Synchronization of medical records The patient is assumed to have installed a medication record app (medical record management unit 103) on their smartphone (patient terminal 10). When new dispensing information is registered, the medical record management unit 303 of the cloud service (management device 30) delivers the new dispensing information to the patient's medication record app (medical record management unit 103). Here, the medical record management unit 303 of the cloud service (management device 30) is assumed to be able to identify the patient's medication record app (medical record management unit 103) to which the dispensing information is to be delivered based on the patient ID.

[0042] The medication record app (Medical Record Management Unit 103) stores the details of the dispensed medication received. The medication record app (Medical Record Management Unit 103) displays the stored details of the dispensed medication on the screen upon the patient's request. By using the medication record app (Medical Record Management Unit 103), patients can view past dispensed medication details in the same way as with a paper medication record book.

[0043] S106: Automatic calculation of insurance medical fee points The point calculation unit 305 of the cloud service (management device 30) calculates the insurance medical points corresponding to the dispensing content when new dispensing content is registered. The point calculation unit 305 sends the insurance medical points to the point processing unit 709 of the PC (pharmacy terminal 70). The point processing unit 709 receives and records the insurance medical points and sends the insurance medical points to the insurer's information processing device at an appropriate time. In other words, the point calculation unit 305 and the point processing unit 709 perform the calculation of insurance medical points, which was previously performed by a so-called prescription computer, almost automatically.

[0044] S107: Automatic calculation of accounting amount The accounting calculation unit 307 of the cloud service (management device 30) calculates the accounting amount corresponding to the dispensing details when new dispensing details are registered. The accounting calculation unit 307 transmits the accounting amount to the accounting processing unit 711 of the PC (pharmacy terminal 70). The accounting processing unit 711 receives the information from the accounting calculation unit 307 and collects the accounting amount from the patient using a known cashless payment method such as a credit card terminal, electronic money terminal, or QR code (registered trademark) payment terminal.

[0045] Alternatively, the accounting unit 307 may send the accounting amount to the cashless payment app (accounting processing unit 105) on the smartphone (patient terminal 10). The cashless payment app (accounting processing unit 105) receives the information from the accounting unit 307 and collects the accounting amount from the patient using known cashless payment methods such as credit cards, electronic money, QR code (registered trademark) payments, and carrier billing.

[0046] According to this embodiment, the exchange of authentication IDs for identifying patients is achieved through contactless communication or biometric authentication that can be performed using smartphones, etc., eliminating the need for patients or medical personnel to remember the authentication IDs. Furthermore, medical records stored in the network database are automatically synchronized with the patient's medication record app, etc., allowing patients to view the latest medical records at any time. In addition, insurance points and accounting amounts are automatically calculated and provided to medical institutions and pharmacies based on the medical records stored in the network database, significantly simplifying administrative tasks that were previously performed using prescription processing computers and accounting systems.

[0047] <Embodiment 2> In Embodiment 2, the medical record management unit 103 of the patient terminal 10 is capable of managing medical records for multiple patients.

[0048] Referring to Figure 2, the configuration of the medical record management system 1 in Embodiment 2 will be described. In this embodiment, the differences from Embodiment 1 will be mainly described, and the same configuration as in Embodiment 1 will be omitted from the explanation as appropriate.

[0049] Patient terminal 10: The authentication ID storage unit 101 stores one authentication ID (identifier), similar to the first embodiment.

[0050] The medical record management unit 103 stores the medical records of multiple patients. The medical record management unit 103 can manage the medical records of multiple patients separately by, for example, associating patient IDs with medical records. The medical records of multiple patients are each duplicated from the medical record management unit 303 of the management device 30. The medical record management unit 103 can then display the medical records of each of the multiple patients on a display device.

[0051] Medical institution terminal 50: The patient identification unit 503 obtains a list of patients associated with the read authentication ID. Here, the patient identification unit 503 maintains a table that associates one authentication ID with one or more patient IDs, and by referring to this table, it identifies one or more patient IDs from an authentication ID.

[0052] The patient identification unit 503 selects a patient to be treated from the acquired patient list. For example, it displays the patient list on the screen and has a medical professional select one patient.

[0053] The medical record acquisition unit 505 acquires the medical record corresponding to the patient ID of the selected patient from the medical record management unit 303 of the management device 30 and displays it on the display device.

[0054] The medical record registration unit 507 receives input of medical records relating to the selected patient and registers them in the medical record management unit 303 of the management device 30.

[0055] Pharmacy terminal 70: The patient identification unit 703, the medical record acquisition unit 705, and the medical record registration unit 707 operate in the same manner as the patient identification unit 503, the medical record acquisition unit 505, and the medical record registration unit 507 of the medical institution terminal 50.

[0056] Management device 30: When a new medical record for a patient is registered, the medical record management unit 303 copies the new medical record to the medical record management unit 103 of the patient terminal 10 that manages the patient's medical record.

[0057] Referring to Figure 3, the operation of the medical record management system 1 according to Embodiment 2 will be described. In this embodiment, the differences from Embodiment 1 will be mainly described, and the same processes as in Embodiment 1 will be omitted from the explanation as appropriate.

[0058] S101: Presentation of identification ID The patient holds their smartphone (patient terminal 10) over the NFC reader (authentication ID acquisition unit 701) installed in the pharmacy. The NFC reader (authentication ID acquisition unit 701) reads the authentication ID from the NFC chip (authentication ID storage unit 101).

[0059] Similar to Embodiment 1, the pharmacy may use biometric authentication means instead of the NFC reader (authentication ID acquisition unit 701). Alternatively, the NFC reader (authentication ID acquisition unit 701) and biometric authentication means may be used in combination. In this case, the biometric authentication means is used as a means to acquire an authentication ID and is not used to identify individual patients.

[0060] S102: Patient identification The patient identification unit 703 outputs a list of patients (one or more patient IDs) associated with the authentication ID. A healthcare professional selects one patient from the list.

[0061] S103: Access to medical records When dispensing medication, the pharmacy uses the medical record acquisition unit 705 of the PC (pharmacy terminal 70) to check the past dispensing history for the selected patient.

[0062] S104: Registration of medical records The pharmacy uses the medical record registration unit 707 of the PC (pharmacy terminal 70) to register the details of the current dispensing (medical record) for the selected patient.

[0063] S105: Synchronization of medical records The medical record management unit 303 of the cloud service (management device 30) distributes the new prescription details to the medication record app (medical record management unit 103) that manages the patient's medical records when new prescription details are registered. Here, the medical record management unit 303 of the cloud service (management device 30) can identify the patient's medication record app (medical record management unit 103) to which the prescription details will be distributed, based on the patient ID. In this embodiment, the relationship between the patient ID and the medication record app (medical record management unit 103) is many-to-one. In addition, when the medical record management unit 303 distributes the prescription details, it also transmits the patient ID associated with those prescription details.

[0064] The medication record app (medical record management unit 103) stores the received prescription details, associating them with the notified patient ID. The medication record app (medical record management unit 103) displays the stored prescription details on the screen for each patient ID. By using the medication record app (medical record management unit 103), patients can view past prescription details for multiple patients. For example, a parent can manage their own and their child's prescription details using the same medication record app (medical record management unit 103).

[0065] S106: Automatic calculation of insurance medical fee points The point calculation unit 305 of the cloud service (management device 30) calculates the insurance medical points corresponding to the dispensing details when new dispensing details are registered.

[0066] S107: Automatic calculation of accounting amount The accounting calculation unit 307 of the cloud service (management device 30) calculates the accounting amount corresponding to the dispensing details when new dispensing details are registered.

[0067] According to this embodiment, the medical record management unit 103 of the patient terminal 10 can manage the medical records of multiple patients. For example, when a parent has a child undergo medical treatment, the parent does not need to remember the child's authentication information. Furthermore, a single smartphone can be used to manage the medical records of the whole family, from management to payment.

[0068] <Embodiment 3> Embodiment 3 describes an example in which multiple medical institutions or pharmacies collaborate via medical records. Specifically, it considers a case where a medical institution registers prescription data, and a pharmacy views that prescription data and dispenses medication. This makes it possible to realize electronic prescriptions as an alternative to conventional paper prescriptions.

[0069] Referring to Figure 2, the configuration of the medical record management system 1 according to Embodiment 3 will be described. In this embodiment, the differences from Embodiment 1 will be mainly described, and the same configuration as in Embodiment 1 will be omitted from the explanation as appropriate.

[0070] Patient terminal 10: The functions of the authentication ID storage unit 101 and the medical record management unit 103 are the same as in Embodiment 1.

[0071] Medical institution terminal 50: The functions of the authentication ID acquisition unit 501, the patient identification unit 503, and the medical record acquisition unit 505 are the same as in Embodiment 1.

[0072] The medical record registration unit 507 accepts input of medical records from medical personnel. In this embodiment, the medical record registration unit 507 accepts input of prescription data from physicians. The medical record registration unit 507 registers the input medical records in the medical record management unit 303 of the management device 30.

[0073] The functions of the score processing unit 509 and the accounting processing unit 511 are the same as in Embodiment 1.

[0074] Pharmacy terminal 70: The functions of the authentication ID acquisition unit 701 and the patient identification unit 703 are the same as in Embodiment 1.

[0075] The medical record acquisition unit 705 acquires medical records corresponding to the patient ID from the medical record management unit 303 of the management device 30 and displays them on the display device. In this embodiment, the medical record acquisition unit 705 acquires prescription data entered by the physician. The pharmacist dispenses medication to the patient while viewing the prescription data displayed on the screen.

[0076] The functions of the medical record registration unit 707, the points processing unit 709, and the accounting processing unit 711 are the same as in Embodiment 1.

[0077] Management device 30: The function of the patient ID acquisition unit 301 is the same as in Embodiment 1.

[0078] The medical record management unit 303 stores patient IDs in association with the medical records relating to those patients. In this embodiment, the medical record management unit 303 receives and stores prescription data for patients created by physicians via the medical record registration unit 507. Then, it transmits the prescription data for those patients to pharmacists for viewing via the medical record acquisition unit 705. In this way, the medical record management unit 303 has the function of mediating prescription data between medical institutions and pharmacies.

[0079] The functions of the score calculation unit 305 and the accounting calculation unit 307 are the same as in Embodiment 1.

[0080] Figure 4 is a flowchart illustrating the operation of the medical record management system 1 according to Embodiment 3. Here, we will explain using the example of a patient who first visits a medical institution to receive a prescription for medication, and then receives dispensing of the medication at a pharmacy based on that prescription.

[0081] S201: Presentation of identification ID in medical institutions The patient holds their smartphone (patient terminal 10) over an NFC reader (authentication ID acquisition unit 501) installed at the medical institution. The NFC reader (authentication ID acquisition unit 501) reads the authentication ID from the NFC chip (authentication ID storage unit 101).

[0082] S202: Patient identification in medical institutions The NFC reader (authentication ID acquisition unit 501) transmits the read authentication ID to the patient identification unit 503 of the PC (medical institution terminal 50). The patient identification unit 503 identifies the patient ID corresponding to the authentication ID.

[0083] S203: Access to medical records in medical institutions Medical institutions examine patients and prescribe medication. The patient ID acquisition unit 301 of the cloud service (management device 30) transmits past prescription data (medical records) corresponding to the patient ID to the medical record acquisition unit 505. The medical record acquisition unit 705 displays the acquired prescription data on the screen.

[0084] S204: Registration of medical records in medical institutions The medical institution uses the medical record registration unit 507 of the PC (medical institution terminal 70) to register the details of the current prescription (medical record) for the patient.

[0085] S205: Automatic calculation of insurance medical service points in medical institutions The point calculation unit 305 of the cloud service (management device 30) calculates the insurance medical points corresponding to the prescription when new prescription details are registered. The point calculation unit 305 sends the insurance medical points to the point processing unit 509 of the PC (medical institution terminal 50).

[0086] S206: Automatic calculation of accounting amounts in medical institutions The accounting calculation unit 307 of the cloud service (management device 30) calculates the accounting amount corresponding to the prescription when a new prescription is registered. The accounting calculation unit 307 sends the accounting amount to the accounting processing unit 511 of the PC (medical institution terminal 50). Alternatively, the accounting calculation unit 307 may send the accounting amount to the cashless payment app (accounting processing unit 105) on the smartphone (patient terminal 10).

[0087] S207: Presentation of identification ID in pharmacies The patient holds their smartphone (patient terminal 10) over the NFC reader (authentication ID acquisition unit 701) installed in the pharmacy. The NFC reader (authentication ID acquisition unit 701) reads the authentication ID from the NFC chip (authentication ID storage unit 101).

[0088] S208: Patient identification in pharmacies The NFC reader (authentication ID acquisition unit 701) transmits the read authentication ID to the patient identification unit 703 of the PC (pharmacy terminal 70). The patient identification unit 703 identifies the patient ID corresponding to the authentication ID.

[0089] S209: Access to medical records in pharmacies The pharmacy dispenses the medication. The patient ID acquisition unit 301 of the cloud service (management device 30) transmits the prescription data (medical record) corresponding to the patient ID to the medical record acquisition unit 705. The medical record acquisition unit 705 displays the acquired prescription data on the screen and dispenses the medication. In other words, the prescription data functions as an electronic prescription.

[0090] S210: Registration of medical records in pharmacies The pharmacy uses the medical record registration unit 707 of the PC (medical institution terminal 70) to register the details of the medication dispensed to the patient (medical record).

[0091] S211: Synchronization of medical records The medical record management unit 303 of the cloud service (management device 30) distributes the new prescription details to the patient's medication record app (medical record management unit 103) when new prescription details are registered.

[0092] S212: Automatic calculation of insurance medical service points in pharmacies The point calculation unit 305 of the cloud service (management device 30) calculates the insurance medical points corresponding to the dispensing details when new dispensing details are registered. The point calculation unit 305 sends the insurance medical points to the point processing unit 709 of the PC (pharmacy terminal 70).

[0093] S213: Automatic calculation of accounting amounts in pharmacies The accounting calculation unit 307 of the cloud service (management device 30) calculates the accounting amount corresponding to the dispensing details when new dispensing details are registered. The accounting calculation unit 307 sends the accounting amount to the accounting processing unit 711 of the PC (pharmacy terminal 70). Alternatively, the accounting calculation unit 307 may send the accounting amount to the cashless payment app (accounting processing unit 105) of the smartphone (patient terminal 10).

[0094] According to this embodiment, multiple medical institutions can share medical data via the medical record management system 1. For example, medical institutions can register prescription data, and pharmacies can view that prescription data, thereby enabling the electronic exchange of prescription data.

[0095] <Embodiment 4> In Embodiment 4, when a medical institution or pharmacy prescribes or dispenses medication, it checks for duplicate prescriptions, drug interactions, allergies, and side effects.

[0096] Referring to Figure 2, the configuration of the medical record management system 1 according to Embodiment 4 will be described. In this embodiment, the differences from Embodiment 1 will be mainly described, and the same configuration as in Embodiment 1 will be omitted from the explanation as appropriate.

[0097] Patient terminal 10: The authentication ID storage unit 101, the medical record management unit 103, and the accounting processing unit 105 have the same functions as in Embodiment 1.

[0098] 50 terminals at medical institutions, 70 terminals at pharmacies: The authentication ID acquisition unit 501 (701), the patient identification unit 503 (703), and the medical record acquisition unit 505 (705) have the same functions as in Embodiment 1.

[0099] The medical record registration unit 507 (707) receives medical records entered by medical personnel and registers them in the medical record management unit 303 of the management device 30. In this embodiment, when prescription data or dispensing data is entered as medical records, the medical record management unit 303 checks for duplicate prescriptions, interactions, allergies, and side effects related to the patient, and if there are any problems, it notifies the medical record registration unit 507 (707). The medical record registration unit 507 (707) warns medical personnel by displaying an alert on the screen or by other means.

[0100] The medical record acquisition unit 505 (705) or the medical record registration unit 507 (707) can display the drug class when a drug name is acquired or registered as prescription data or dispensing data. A drug class is information that indicates the structure and characteristics of a drug; for example, antibiotics are classified into penicillin, cephalosporin, macrolide, aminoglycoside, and quinolone classes. The medical institution terminal 50 or pharmacy terminal 70 is assumed to have a table in which drug names and drug classes are pre-associated.

[0101] The score processing unit 509 (709) and the accounting processing unit 511 (711) have the same functions as in Embodiment 1.

[0102] Management device 30: The patient ID acquisition unit 301 has the same functions as in Embodiment 1.

[0103] When the Medical Records Management Department 303 receives prescription data and dispensing data as medical records from the Medical Records Registration Department 507 (707), it checks for duplicate prescriptions, drug interactions, allergies, and side effects related to the patient.

[0104] For example, when the medical record management unit 303 receives prescription data or dispensing data, it retrieves prescription data or dispensing data for the same patient for a predetermined period in the past. If the same type of medication has been prescribed or dispensed within the predetermined period, it notifies the medical record registration unit 507 (707) of an alert.

[0105] Furthermore, for example, when the medical record management unit 303 receives prescription data or dispensing data, it retrieves prescription data or dispensing data for the same patient for a predetermined period in the past. If there is a possibility of an undesirable interaction between the drug prescribed or dispensed within the predetermined period and the drug prescribed or dispensed this time, it notifies the medical record registration unit 507 (707) of an alert. Here, the medical record management unit 303 has a table in advance that defines combinations of drugs that may interact, and can determine whether or not an interaction is likely to occur by referring to this table.

[0106] Furthermore, for example, when the medical record management unit 303 receives prescription data or dispensing data, it determines whether the prescribed or dispensed drug may cause side effects or allergies, and if so, it notifies the medical record registration unit 507 (707) of an alert. Here, the medical record management unit 303 maintains a table in advance for each patient ID that records drugs that the patient has previously used to cause side effects or allergies, and can determine the likelihood of side effects or allergies occurring by referring to this table.

[0107] When the medical record management department 303 checks for duplicate prescriptions, drug interactions, allergies, and side effects, it can use not only drug names but also drug classifications. This allows for more accurate identification of drugs that should not be administered to patients. Here, it is assumed that the medical record management department 303 has a table that pre-associates drug names with drug classifications.

[0108] The score calculation unit 305 and the accounting calculation unit 307 have the same functions as in Embodiment 1.

[0109] Referring to Figure 5, the operation of the medical record management system 1 according to Embodiment 4 will be described. In this embodiment, the differences from Embodiment 1 will be mainly described, and the same processes as in Embodiment 1 will be omitted from the explanation as appropriate.

[0110] S301: Presentation of identification ID The patient holds their smartphone (patient terminal 10) over the NFC reader (authentication ID acquisition unit 701) installed in the pharmacy. The NFC reader (authentication ID acquisition unit 701) reads the authentication ID from the NFC chip (authentication ID storage unit 101).

[0111] S302: Patient Identification The NFC reader (authentication ID acquisition unit 701) transmits the read authentication ID to the patient identification unit 703 of the PC (pharmacy terminal 70). The patient identification unit 703 identifies the patient ID corresponding to the authentication ID.

[0112] S303: Access to medical records Pharmacies dispense medication to patients. The patient ID acquisition unit 301 of the cloud service (management device 30) transmits past medical records corresponding to the patient ID to the medical record acquisition unit 705. The medical record acquisition unit 705 displays the acquired medical records on the screen.

[0113] S304: Registration of medical records The pharmacy uses the medical record registration unit 707 of the PC (pharmacy terminal 70) to register the details of the current prescription (medical record) for the patient. The medical record acquisition unit 705 transmits the prescription details and patient ID to the medical record management unit 303 of the cloud service (management device 30).

[0114] S305: Checking for duplicate medication, etc. The medical record management unit 303 checks the received dispensing information for duplicate prescriptions, drug interactions, allergies, and side effects. If a problem is found, the medical record management unit 303 notifies the medical record registration unit 707 on the PC (pharmacy terminal 70) of an alert. If there is no problem, the medical record management unit 303 associates the received patient ID with the dispensing information and stores it in memory.

[0115] S306: Synchronization of medical records The medical record management unit 303 of the cloud service (management device 30) distributes the new prescription details to the patient's medication record app (medical record management unit 103) when new prescription details are registered.

[0116] S307: Automatic calculation of insurance medical fee points The point calculation unit 305 of the cloud service (management device 30) calculates the insurance medical points corresponding to the dispensing details when new dispensing details are registered. The point calculation unit 305 sends the insurance medical points to the point processing unit 709 of the PC (pharmacy terminal 70).

[0117] S308: Automatic calculation of accounting amount The accounting calculation unit 307 of the cloud service (management device 30) calculates the accounting amount corresponding to the dispensing details when new dispensing details are registered. The accounting calculation unit 307 sends the accounting amount to the accounting processing unit 711 of the PC (pharmacy terminal 70).

[0118] According to this embodiment, when a medical institution or pharmacy attempts to register prescription data or dispensing data, the medical record management system 1 automatically performs checks for duplicate prescriptions and other issues, and issues warnings as necessary. This makes it possible to prevent errors in prescriptions and dispensing in a simple and effective manner.

[0119] Traditionally, to prevent drug-related accidents, healthcare professionals would interview patients about previously prescribed or dispensed medications, medications prescribed or dispensed at other hospitals or pharmacies, and their history of side effects, interactions, and allergies, and then prescribe or dispense the medication deemed most appropriate for the patient. However, patients often forgot or concealed information about their past. This embodiment allows healthcare professionals to easily access records of past prescriptions or dispensing, as well as records of side effects, interactions, and allergies. Furthermore, it enables automatic checking of duplicate prescriptions, interactions, allergies, and side effects, thus proving highly effective in preventing drug-related accidents.

[0120] <Embodiment 5> Embodiment 5 discloses a configuration for providing patients with information about pharmacies where prescriptions can be dispensed, using prescription data already registered in the medical record management unit 303.

[0121] Figure 6 is a block diagram showing an example of the functional configuration of the medical record management system 1 according to Embodiment 5. In addition to the components shown in Embodiment 3 or 4, the medical record management system 1 according to this embodiment includes the following components.

[0122] The patient terminal 10 further includes a position detection unit 121. The location detection unit 121 detects the current location information and transmits it to the pharmacy identification unit 321 of the management device 30. The location detection unit 121 can, for example, use a satellite positioning system (GNSS: Global Navigation Satellite System) to detect the coordinates of the patient terminal 10 and use this as the current location information. GNSS includes, for example, GPS (Global Positioning System), GLONASS (Global Navigation Satellite System), Galileo, QZSS (Quasi-Zenith Satellite System), etc. Alternatively, the location detection unit 121 may detect a unique signal, such as a device ID, emitted by a beacon, WiFi base station, or Bluetooth® device installed in the pharmacy and use this as the current location information.

[0123] The location detection unit 121 can start detecting the current location information in response to a patient's request, such as when the "Pharmacy Search" button is pressed. Alternatively, the location detection unit 121 may automatically detect the current location information at any time.

[0124] The management device 30 further includes a pharmacy identification unit 321, an inventory confirmation unit 323, and an inventory information provision unit 325.

[0125] The pharmacy identification unit 321 receives current location information from the location detection unit 121 of the patient terminal 10. The pharmacy identification unit 321 also pre-stores a table that associates pharmacy information with pharmacy location information. The pharmacy identification unit 321 compares the current location information with the pharmacy location information and extracts the pharmacy if one exists near the patient terminal 10.

[0126] Here, pharmacy information is an identifier that uniquely identifies a pharmacy. Pharmacy location information is, for example, the coordinates of the pharmacy's location. Alternatively, it may be a unique signal emitted by a beacon, WiFi base station, or Bluetooth® device installed at the pharmacy, such as a device ID. The pharmacy identification unit 321 extracts pharmacy information associated with the current location information (coordinates) when the distance between the current location information (coordinates) and the pharmacy location information (coordinates) is below a predetermined threshold. Alternatively, it extracts pharmacy information associated with the current location information (device ID) when the pharmacy location information (device ID) matches. This allows the pharmacy identification unit 321 to identify a pharmacy located near the patient terminal 10.

[0127] The inventory confirmation unit 323 checks whether it is possible to prescribe medication to a patient with a patient terminal 10 at a pharmacy selected by the pharmacy identification unit 321. The confirmation procedure is as follows: First, the inventory confirmation unit 323 checks whether prescription details (medical records) associated with the patient ID corresponding to the patient terminal 10 exist in the medical record management unit 303. If it exists, it retrieves the prescription details and transmits them to the inventory management unit 721 of the pharmacy terminal 70. The inventory management unit 721 returns information to the inventory confirmation unit 323 regarding the availability of medication related to the received prescription details.

[0128] The inventory information provision unit 325 distributes information to the patient terminal 10, including whether or not the pharmacy can dispense the medication. Specifically, if the inventory confirmation unit 323 determines that a pharmacy identified by the pharmacy identification unit 321 is able to dispense the medication to the patient corresponding to the patient terminal 10, the inventory information provision unit 325 notifies the patient terminal 10 that "dispensing is possible at that pharmacy." For example, it displays an advertising message such as "Pharmacy A can dispense your prescription" on the display of the patient terminal 10. On the other hand, even if there is no stock and immediate dispensing is impossible, the inventory information provision unit 325 can still notify the patient terminal 10. For example, it displays an advertising message such as "Pharmacy B is accepting dispensing reservations" on the display of the patient terminal 10. In this case, additional information such as the expected arrival date may also be displayed.

[0129] Furthermore, if the location detection unit 121 is configured to automatically detect the current location information at any given time, the inventory information provision unit 325 may push the aforementioned advertising message to the patient terminal 10 when the patient approaches the pharmacy.

[0130] As another example, the inventory information provision unit 325 may display a list of pharmacies that can dispense medication on the display of the patient terminal 10. Alternatively, it may plot the pharmacies that can dispense medication on a map. In these cases, the pharmacy identification unit 321 extracts multiple pharmacies, and the inventory confirmation unit 323 queries the inventory management units 721 of the multiple pharmacies for inventory information. For example, if the pharmacy identification unit 321 finds multiple pharmacies where the distance between the current location information (coordinates) and the pharmacy location information (coordinates) is below a predetermined threshold, it can extract these pharmacies. Alternatively, if the location detection unit 121 has obtained multiple current location information (device IDs), the pharmacy identification unit 321 can extract multiple pharmacies that have pharmacy location information (device IDs) that match these.

[0131] The pharmacy terminal 70 further includes an inventory management unit 721 for managing the inventory of medicines in the pharmacy.

[0132] The inventory management unit 721 is a database that stores and manages drug inventory information in a pharmacy. In response to a request from the inventory confirmation unit 323, the inventory management unit 721 refers to the inventory information of the drugs included in the specified prescription. If the drug is in stock, the inventory management unit 721 sends a notification to the inventory confirmation unit 323 indicating that it is in stock. If the drug is not in stock, the inventory management unit 721 notifies the inventory confirmation unit 323 that it is out of stock. Additional information, such as the expected arrival date, may also be notified at this time.

[0133] Figure 7 is a flowchart showing an example of a characteristic operation of the medical record management system 1 according to Embodiment 5. S401: Detection of pharmacies located near the current location The location detection unit 121 of the patient terminal 10 attempts to detect signals from beacons installed in the pharmacy at regular intervals. If a beacon signal is detected, the location detection unit 121 transmits the device ID included in the beacon signal to the pharmacy identification unit 321 of the management device 30 as current location information. The pharmacy identification unit 321 identifies the pharmacy information using the device ID as a key.

[0134] S402: Referencing prescription details The inventory confirmation unit 323 retrieves prescription details associated with the patient ID corresponding to the patient terminal 10 from the medical record management unit 303.

[0135] S403: Check drug inventory The inventory confirmation unit 323 inquires with the inventory management unit 721 of the identified pharmacy whether or not they have the medication included in the prescription in stock. The inventory management unit 721 replies to the inventory confirmation unit 323 regarding the availability of the medication.

[0136] S404: Information Distribution The inventory information provision unit 325 notifies the patient terminal 10 of the information regarding the pharmacy identified in S401. This information may include information regarding the availability of the drug in stock, obtained in S403.

[0137] According to this embodiment, for example, information about a pharmacy can be provided to a patient walking near the pharmacy. Information regarding whether the pharmacy can dispense the medication corresponding to the patient's prescription can also be provided. This allows patients to easily obtain the necessary medication, and enables pharmacies to provide patients with the medication they need.

[0138] <Other embodiments> It should be noted that the present invention is not limited to the embodiments described above, and can be modified as appropriate without departing from the spirit of the invention. For example, it is possible to implement the invention by combining one or more embodiments from Embodiments 1 to 5 described above.

[0139] Furthermore, while the above-described embodiments focused on prescription data in medical institutions and dispensing data in pharmacies, the present invention is not limited to these and can be applied to data related to various medical procedures performed in medical institutions and pharmacies. For example, it is possible to manage test data and care performance data in medical institutions using a similar configuration.

[0140] Furthermore, the present invention can also be implemented in hardware, and any processing can be implemented by having a CPU (Central Processing Unit) execute a computer program. In this case, the computer program can be stored using various types of non-transitory computer-readable medium and supplied to the computer. Non-transitory computer-readable mediums include various types of tangible storage mediums. Examples of non-transitory computer-readable mediums include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical disks), CD-ROMs (Read Only Memory), CD-Rs, CD-R / Ws, and semiconductor memories (e.g., mask ROMs, PROMs (Programmable ROMs), EPROMs (Erasable PROMs), flash ROMs, RAMs (random access memory)). The program may also be supplied to the computer using various types of transient computer-readable mediums. Examples of transient computer-readable mediums include electrical signals, optical signals, and electromagnetic waves. Temporary computer-readable media can supply programs to a computer via wired communication channels such as electric wires and optical fibers, or via wireless communication channels. [Explanation of Symbols]

[0141] 1. Medical Record Management System 10 Patient terminals 30 Management device 50 Medical Institution Terminals 70 Pharmacy terminals 90 Networks 101 Authentication ID storage unit 103 Medical Records Management Department 105 Accounting Processing Department 121 Position detection unit 301 Patient ID acquisition department 303 Medical Records Management Department 305 Point calculation section 307 Accounting Department 321 Pharmacy Specialist Department 323 Inventory Check Department 325 Inventory Information Department 501 Authentication ID Acquisition Section 503 Patient Identification Department 505 Medical Record Acquisition Department 507 Medical Records Registration Department 509 Score Processing Unit 511 Accounting Processing Unit 701 Authentication ID Acquisition Unit 703 Patient Identification Department 705 Medical Record Acquisition Department 707 Medical Records Registration Department 709 Score Processing Unit 711 Accounting Department 721 Inventory Management Department

Claims

1. A device that obtains an authentication ID for the patient, A patient identification unit that identifies a patient ID based on the aforementioned authentication ID, A first medical record management unit stores medical records associated with the aforementioned patient ID in a network storage area, A medical record registration unit that registers the medical data in the first medical record management unit, The system includes a medical record acquisition unit that acquires the medical data from the first medical record management unit, The authentication ID acquisition unit acquires the authentication ID stored in a predetermined recording medium via contactless communication. Medical record management system.

2. The authentication ID acquisition unit acquires the authentication ID by performing biometric authentication in lieu of or in conjunction with the contactless communication. A medical record management system according to claim 1.

3. The aforementioned medical record is dispensing data from a pharmacy. A medical record management system according to claim 1.

4. The aforementioned medical records are prescription data from a medical institution. A medical record management system according to claim 1.

5. The system further includes a points calculation unit that calculates insurance medical service points based on the aforementioned medical records. A medical record management system according to claim 1.

6. The system further includes an accounting unit that calculates accounting amounts based on the aforementioned medical records. A medical record management system according to claim 1.

7. The system further includes an accounting processing unit that receives the aforementioned accounting amount and executes cashless payment. A medical record management system according to claim 6.

8. It has a second medical record management unit that stores the aforementioned medical records in the patient's terminal device, The second medical record management unit stores the medical records relating to multiple patient IDs. A medical record management system according to claim 1.

9. The aforementioned medical record registration unit registers prescription data generated at the aforementioned medical institution. The medical record acquisition unit acquires the prescription data at the pharmacy. The medical record management system according to claims 3 and 4.

10. The medical record registration unit displays the results of duplicate prescriptions, drug interactions, side effects, or allergy checks related to the medical record to be registered. A medical record management system according to claim 1.

11. A position detection unit that detects the current location of the patient's terminal device, A pharmacy identification unit that identifies a pharmacy located near the current location, The inventory management department manages the inventory of drugs at the aforementioned pharmacy, An inventory confirmation unit that inquires with the inventory management branch about the inventory of drugs included in the prescription data recorded in the first medical record management unit, The system includes an inventory information provision unit that distributes information about the pharmacy and information about the drug inventory to the patient's terminal device. A medical record management system according to claim 4.

12. The authentication ID acquisition step involves obtaining an authentication ID for the patient, A patient identification step that identifies the patient ID based on the aforementioned authentication ID, A medical record registration step involves registering the medical data in a first medical record management unit that stores the medical records associated with the aforementioned patient ID in a storage area on the network. The system includes a medical record acquisition step of acquiring the medical data from the first medical record management unit, In the authentication ID acquisition step, the authentication ID stored in a predetermined recording medium is acquired via contactless communication. Medical record management methods.

13. A program for causing a computer to perform the method described in claim 12.

Images