Information processing apparatus, program, information processing system, and information processing method

Abstract

To prevent a dispensing history and personal information from being leaked in an electronic medicine notebook application.SOLUTION: The information processing device includes means for acquiring dispensing data in response to storage of the dispensing data generated by the receipt computer in a predetermined address of a storage device of the pharmacy client device, the dispensing data including personal information of a patient, means for storing registered patient identification information for identifying the patient and registered personal information of the patient in association with each other, means for comparing the personal information included in the dispensing data with the registered personal information, and means for storing electronic medication notebook data based on the dispensing data in association with the registered patient identification information when the comparison is successful.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to an information processing device, a program, an information processing system, and an information processing method. [Background technology]

[0002] In recent years, applications (hereinafter referred to as "electronic medicine notebook applications") for managing medicine notebooks on computers used by patients (hereinafter referred to as "patient client devices") have become widespread. By using the electronic medicine notebook application, patients can keep track of their prescription history without using a paper medicine notebook. Pharmacies can keep track of patients' prescription history without using paper medication records.

[0003] For example, Patent Document 1 discloses a drug information management support device that includes a memory unit and a control unit, in which the memory unit stores a disease name database relating to the correspondence between drug names and disease names, and the control unit includes a data accepting unit that accepts first prescription data including the name of the disease diagnosed for a specific patient by an insurance medical institution and second prescription data including the name of the drug prescribed by the insurance medical institution, and a disease name identification unit that identifies which disease name included in the first prescription data corresponds to the drug name included in the second prescription data by referring to the disease name database. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2019-159700 Summary of the Invention [Problem to be solved by the invention]

[0005] In order to use the electronic medicine notebook application, the patient must perform certain operations (for example, register prescription information in the electronic medicine notebook application). Therefore, if the patient neglects to perform this operation, the electronic medicine notebook application will not be able to record the complete prescription history.

[0006] On the other hand, if this task is to be automated, a system is needed to protect personal information, ensuring that one patient's medication record information is not stored in association with information that identifies another patient (i.e., a system for protecting personal information).

[0007] Patent Document 1 does not disclose a mechanism for protecting personal information.

[0008] An object of the present invention is to prevent leakage of prescription history and personal information in an electronic medicine notebook application. [Means for solving the problem]

[0009] One aspect of the present invention is a means for acquiring the dispensing data generated by the receipt computer in response to the dispensing data being stored at a predetermined address in a storage device of the pharmacy client device; the dispensing data includes patient personal information; a means for storing registered patient identification information for identifying the patient and registered personal information of the patient in association with each other; A means for matching personal information included in the prescription data with the registered personal information, If the matching is successful, a means for storing electronic medicine notebook data based on the dispensing data in association with the registered patient identification information is provided. It is an information processing device. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a block diagram showing a configuration of an information processing system according to an embodiment of the present invention; [Figure 2]FIG. 2 is a functional block diagram of the information processing system of FIG. 1. [Figure 3] FIG. 1 is an explanatory diagram of an overview of the present embodiment. [Figure 4] FIG. 2 is a diagram illustrating a data structure of a database according to the present embodiment. [Figure 5] FIG. 2 is a diagram showing the overall flow of information processing according to the present embodiment. [Figure 6] FIG. 10 is a sequence diagram of a process for registering patient information according to the present embodiment. [Figure 7] 7A and 7B are diagrams showing examples of screens displayed in the information processing of FIG. 6. [Figure 8] FIG. 10 is a sequence diagram of the process of setting the pharmacy client device according to the present embodiment. [Figure 9] 9A and 9B are diagrams showing examples of screens displayed in the information processing of FIG. 8. [Figure 10] FIG. 10 is a sequence diagram of a process for setting automatic registration according to the present embodiment. [Figure 11] 11A and 11B are diagrams showing examples of screens displayed in the information processing of FIG. 10. [Figure 12] 10 is a sequence diagram of the process of automatically registering medication notebook information in this embodiment. FIG. [Figure 13] 13 is a diagram showing an example of a screen displayed in the information processing of FIG. 12. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. In the drawings for explaining the embodiment, the same components are generally designated by the same reference numerals, and repeated description thereof will be omitted.

[0012] (1) Information processing system configuration The configuration of the information processing system will be described below. Fig. 1 is a block diagram showing the configuration of the information processing system of this embodiment. Fig. 2 is a functional block diagram of the information processing system of Fig. 1.

[0013] As shown in FIG. 1, the information processing system 1 includes a pharmacy client device 10, a server 30, and a patient client device 50. The pharmacy client device 10, the server 30, and the patient client device 50 are connected via a network (for example, the Internet or an intranet) NW.

[0014] Pharmacy client device 10 is a computer (an example of an "information processing device") that transmits and receives information to and from server 30. Pharmacy client device 10 is, for example, a smartphone, a tablet terminal, or a personal computer.

[0015] The server 30 is a computer (an example of an "information processing device") that transmits and receives information between the pharmacy client device 10 and the patient client device 50. The server 30 is, for example, a web server.

[0016] The patient client device 50 is a computer (an example of an "information processing device") that transmits and receives information to and from the server 30. The patient client device 50 is, for example, a smartphone, a tablet terminal, or a personal computer.

[0017] (1-1) Configuration of Pharmacy Client Device The configuration of the pharmacy client device 10 will be described.

[0018] As shown in FIG. 2, pharmacy client device 10 includes a storage device 11, a processor 12, an input / output interface 13, and a communication interface 14.

[0019] The storage device 11 is configured to store programs and data, and is, for example, a combination of a read-only memory (ROM), a random access memory (RAM), and a storage (for example, a flash memory or a hard disk).

[0020] The programs include, for example, the following programs: OS (Operating System) programs Parameters, functions, and models used in information processing -Application programs that perform information processing (e.g., medicine notebook management applications)

[0021] The data includes, for example, the following data: Databases referenced in information processing Data obtained by performing information processing (i.e., the results of performing information processing)

[0022] Processor 12 is configured to realize the functions of pharmacy client device 10 by running a program stored in storage device 11. Processor 12 is, for example, a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or a combination thereof.

[0023] Input / output interface 13 is configured to receive user instructions from an input device connected to pharmacy client device 10 and to output information to an output device connected to pharmacy client device 10 . The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof. The output device is, for example, a display.

[0024] The communication interface 14 is configured to control communication between the pharmacy client device 10 and the server 30, and communication between the pharmacy client device 10 and the receipt computer RC.

[0025] (1-2) Server configuration The configuration of the server 30 will be described.

[0026] As shown in FIG. 2, the server 30 includes a storage device 31, a processor 32, an input / output interface 33, and a communication interface .

[0027] The storage device 31 is configured to store programs and data, and is, for example, a combination of ROM, RAM, and storage (for example, flash memory or a hard disk).

[0028] The programs include, for example, the following programs: OS programs Parameters, functions, and models used in information processing Application programs that perform information processing

[0029] The data includes, for example, the following data: Databases referenced in information processing - Results of information processing

[0030] The processor 32 is configured to implement the functions of the server 30 by running a program stored in the storage device 31. The processor 32 is, for example, a CPU, a GPU, an ASIC, an FPGA, or a combination thereof.

[0031] The input / output interface 33 is configured to receive user instructions from an input device connected to the server 30 and to output information to an output device connected to the server 30 . The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof. The output device is, for example, a display.

[0032] The communication interface 34 is configured to control communications between the server 30 and the pharmacy client device 10 .

[0033] (1-3) Configuration of patient client device The configuration of the patient client device 50 will now be described.

[0034] As shown in FIG. 2, the patient client device 50 includes a memory device 51, a processor 52, an input / output interface 53, and a communication interface .

[0035] The storage device 51 is configured to store programs and data, and is, for example, a combination of ROM, RAM, and storage (for example, flash memory or a hard disk).

[0036] The programs include, for example, the following programs: OS programs Parameters, functions, and models used in information processing -Application programs that perform information processing (e.g., electronic medicine notebook applications)

[0037] The data includes, for example, the following data: Databases referenced in information processing Data obtained by performing information processing (i.e., the results of performing information processing)

[0038] The processor 52 is configured to implement the functions of the patient client device 50 by running a program stored in the storage device 51. The processor 52 is, for example, a CPU, a GPU, an ASIC, an FPGA, or a combination thereof.

[0039] The input / output interface 53 is configured to receive user instructions from an input device connected to the patient client device 50 and to output information to an output device connected to the patient client device 50 . The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof. The output device is, for example, a display.

[0040] The communications interface 54 is configured to control communications between the patient client device 50 and the server 30 .

[0041] (2) Overview of the embodiment An outline of this embodiment will be explained below with reference to Fig. 3, which is an explanatory diagram of the outline of this embodiment.

[0042] As shown in Figure 3, the prescription computer RC generates prescription data. The prescription data includes information about the patient and information about the medicines dispensed to the patient. The prescription data is, for example, electronic prescription notebook data. The electronic prescription notebook data is an electronic file in which information about medical fee statements (hereinafter referred to as "prescription information") is written in a predetermined format (for example, a format specified by the Healthcare and Welfare Information Systems Industry Association, a general incorporated association).

[0043] The pharmacy client device 10 stores the dispensing data in a predetermined address (for example, a predetermined folder) in the storage device 11. In response to the prescription data being saved at the predetermined address, the pharmacy client device 10 transmits the prescription data saved at the predetermined address to the server 30 without an instruction from the pharmacy user.

[0044] The server 30 acquires the dispensing data transmitted from the pharmacy client device 10 and compares the patient information contained in the dispensing data (hereinafter referred to as "dispensing patient information") with the registered patient information pre-stored in the memory device 31. If the matching is successful, the server 30 stores the electronic medicine notebook data based on the dispensing data in the storage device 31. If the matching fails, the server 30 notifies the pharmacy client device 10 of a message according to the cause of the failure.

[0045] The patient client device 50 displays the electronic medication notebook data stored in the storage device 31 from the server 30 in response to an instruction from the patient.

[0046] (3) Data The data of this embodiment will be explained.

[0047] (3-1) Electronic medicine notebook data The electronic medicine notebook data of this embodiment will be described.

[0048] The electronic medicine notebook data is associated with electronic medicine notebook patient identification information. The electronic medicine notebook patient identification information is information that identifies a patient in the electronic medicine notebook data.

[0049] The electronic medicine notebook data includes the following information groups: Version Information Group Patient Basic Information Group Prescription Drugs and OTC Drug Dosage Information Group Dispensing Information Group Family Pharmacist Information Group Control Information Group

[0050] The version information group contains the following information: Version information (e.g., information about the version of the format of the electronic medicine notebook data)

[0051] The patient basic information group includes the following information (an example of dispensing patient information): Electronic medicine notebook patient information (e.g., patient name (hereinafter referred to as "electronic medicine notebook patient name information"), gender (hereinafter referred to as "electronic medicine notebook gender information"), date of birth (hereinafter referred to as "electronic medicine notebook date of birth information"), postal code, address, telephone number, emergency contact information, blood type, weight, and information about the patient's name in kana) Patient attribute information (e.g., patient attribute type, patient attribute content, and information about the record creator)

[0052] The prescription drug and over-the-counter drug dosage information group includes the following information: Prescription drug and over-the-counter drug information (e.g., drug name, start date, end date, record creator, prescription drug and over-the-counter drug record serial number, and JAN (Japanese Article Number) code information) Prescription drug and over-the-counter drug ingredient information (e.g., prescription drug and over-the-counter drug record serial number, ingredient name, code type, ingredient code, and information about the record creator) Diary memo information (e.g., information about the diary memo, the date of entry of the memo, and the record creator)

[0053] The dispensing information group includes the following information (hereinafter referred to as "electronic medicine notebook dispensing information"). Dispensing date information (e.g., information about the dispensing date and the record creator) Dispensing - Medical institution information (e.g., name of medical institution, prefecture of medical institution, medical institution fee schedule, medical institution code, medical institution postal code, medical institution address, medical institution telephone number, information about the record creator) Dispensing - Doctor / Pharmacist Information (e.g., doctor / pharmacist name, doctor / pharmacist contact information, and information about the record creator) Prescription - Medical institution information (e.g., medical institution name, medical institution prefecture, medical institution fee schedule, medical institution code, and information about the record creator) Prescription - Physician information (e.g., physician name, department name, and information about the record creator) Drug information (e.g., drug group number (hereinafter referred to as "RP number"), drug name, dosage, unit name, drug code type, drug code, information about the record creator, generic name, generic name code type, and information about the generic name code) Drug supplement information (e.g., RP number, drug supplement, and information about the record creator) Drug use warning information (e.g., RP number, content, and information about the record creator) Usage information (e.g., RP number, usage name, dispensing quantity, dispensing unit, dosage form code, usage code type, usage code, and information on the record creator) Usage notes (e.g., RP number, usage notes, and information about the record creator) Prescription medication information (e.g., RP number, content, and information about the record creator) - Prescription information (e.g., information about the content and the record creator) Information provided by medical institutions, etc. (e.g., content, type of information provided, and information about the record creator) -Remaining medication confirmation information (e.g., information about remaining medication and record creator) Remarks (e.g., remarks and information about the record creator) - Information entered by the patient, etc. (for example, information regarding the patient, etc. entry and the date of entry)

[0054] The Family Pharmacist Information Group includes the following information: Family pharmacist information (e.g., family pharmacist name, pharmacy name, contact information, start date, end date, and information about the record creator)

[0055] The control information group includes the following information: Division control information (e.g., data unique identification information, number of divisions, and information regarding data sequence numbers)

[0056] (3-2) Database The databases of this embodiment will now be described. The following databases are stored in the storage device 31. Figure 4 is a diagram showing the data structure of the databases of this embodiment.

[0057] (3-2-1) Pharmacy Database The pharmacy database of this embodiment will be described.

[0058] Pharmacy information is stored in the pharmacy database of Figure 4. The pharmacy information is information relating to pharmacies. The pharmacy database includes a "pharmacy ID" field, a "pharmacy name" field, a "pharmacy address" field, a "pharmacy contact" field, and a "device model" field. Each field is associated with the others.

[0059] The "pharmacy ID" field stores pharmacy identification information. The pharmacy identification information is information that identifies a pharmacy.

[0060] The "pharmacy name" field stores pharmacy name information. The pharmacy name information is information about the name of the pharmacy.

[0061] The "pharmacy location" field stores pharmacy location information. The pharmacy location information is information about the location of the pharmacy.

[0062] The "Pharmacy Contact" field stores pharmacy contact information. The pharmacy contact information is information about how to contact the pharmacy.

[0063] The "Model" field stores model information. The model information is information about the model of the receipt computer RC.

[0064] (3-2-2) Registered patient database The registered patient database of this embodiment will be described.

[0065] Registered patient information is stored in the registered patient database of Fig. 4. The registered patient information is information about patients registered in the server 30. The registered patient database includes a "registered patient ID" field, a "electronic medication notebook patient ID" field, a "registered personal information" field, an "automatic registration flag" field, a "corrected patient name" field, a "family pharmacy ID" field, and a "family patient ID" field. Each field is associated with the others. The registered patient database is associated with the pharmacy identification information.

[0066] The “registered patient ID” field stores registered patient identification information. The registered patient identification information is information for identifying a patient registered in the server 30.

[0067] The "Electronic Medicine Notebook Patient ID" field stores the patient identification information for the electronic medicine notebook.

[0068] The "registered personal information" field stores the patient's personal information. The "registered personal information" field includes a "registered patient name" field, a "registered gender" field, and a "registered date of birth" field.

[0069] The "registered patient name" field stores registered patient name information. The registered patient name information is information related to the patient's name. The registered patient name information is information entered by the patient.

[0070] The "registered gender" field stores registered gender information. The registered gender information is information about the gender of the patient. The registered gender information is information entered by the patient.

[0071] The "registered date of birth" field stores registered date of birth information. The registered date of birth information is information related to the patient's date of birth. The registered date of birth information is information entered by the patient.

[0072] The "automatic registration flag" field stores automatic registration flag information. The automatic registration flag information indicates whether a patient is a target for automatic registration of medication notebook information (hereinafter referred to as "target patient").

[0073] The "corrected patient name" field stores corrected patient name information. The corrected patient name information is information related to the patient's name. The corrected patient name information is information entered by the pharmacy user.

[0074] The "family pharmacy ID" field stores family pharmacy identification information. The family pharmacy identification information is the pharmacy identification information of the family pharmacy. A family pharmacy is a pharmacy that is arbitrarily designated by a patient.

[0075] The "family patient ID" field stores family patient identification information. The family patient identification information is registered patient identification information of the family member of the patient corresponding to the registered patient identification information.

[0076] (3-2-3) Registered medicine notebook database The registered medicine notebook database of this embodiment will be described.

[0077] The registered medicine notebook information is stored in the registered medicine notebook database of Figure 4. The registered medicine notebook information is information related to dispensing based on a prescription provided to a patient, and is medicine notebook information displayed on the patient client device 50. The registered medicine notebook database includes a "registered medicine notebook ID" field and an "electronic medicine notebook" field. Each field is associated with the other fields. The registered medication notebook database is associated with registered patient identification information.

[0078] The "Registered Medicine Notebook ID" field stores registered medicine notebook identification information. The registered medicine notebook identification information is information that identifies the registered medicine notebook information.

[0079] The "electronic medicine notebook" field stores the electronic medicine notebook data.

[0080] (4) Information processing The information processing of this embodiment will be described below with reference to Fig. 5, which is a diagram showing the overall flow of the information processing of this embodiment.

[0081] As shown in Figure 5, the information processing of this embodiment includes processing for registering patient information (OP1), processing for setting up automatic transmission (OP2), processing for setting up automatic registration (OP3), and processing for automatic registration of medication notebook information (OP4).

[0082] The patient information registration process (OP1) is a process for registering patient information in the patient information database.

[0083] The process for setting automatic transmission (OP2) and the process for setting automatic registration (OP3) are processes for registering, in the pharmacy client device 10, settings required for executing the process for automatically registering medication notebook information (OP4).

[0084] The process for automatically registering medicine notebook information (OP4) is a process for registering medicine notebook information in the medicine notebook database.

[0085] (4-1) Patient information registration process The process (OP1) for registering patient information according to this embodiment will be described. Fig. 6 is a sequence diagram of the process for registering patient information according to this embodiment. Fig. 7 is a diagram showing an example of a screen displayed in the information processing of Fig. 6.

[0086] The trigger for the processing in Figure 6 is, for example, when a patient completes login (for example, authentication of registered patient identification information) via an electronic medicine notebook application and gives a user instruction to start the process of registering patient information.

[0087] [Patient information registration request (S1150)] As shown in FIG. 6, the patient client device 50 executes a patient information registration request. Specifically, the processor 52 displays a screen P1150 (FIG. 7) on the display.

[0088] The screen P1150 includes an operation object B1150 and field objects F11500 to F11501.

[0089] The operation object B 1150 is an object that receives a user instruction to transmit patient information registration request data to the server 30.

[0090] The field object F11500 is an object that receives input of pharmacy information (for example, pharmacy name information) of the pharmacy used by the patient.

[0091] The field object F11501 is an object that accepts input of patient information to be registered in the server 30 (for example, patient name information, sex information, and date of birth information).

[0092] When the patient operates the operation object B 1150, the processor 52 transmits patient information registration request data to the server 30. The patient information registration request data includes, for example, the following information: - Pharmacy name information entered in field object F11500 Patient information entered in field object F11501

[0093] [Database Update (S1130)] After step S1150, the server 30 updates the database. Specifically, processor 32 adds a new record to the registered patient database. Processor 32 stores the following information in the new record: "Registered Patient ID" field: Identification information for the newly registered patient "Electronic Medicine Handbook Patient ID" field: Blank "Registered patient name" field: Patient name information included in the patient information registration request data "Registered Gender" field: Gender information included in the patient information registration request data "Registered Date of Birth" field: Date of birth information included in the patient information registration request data "Primary Pharmacy ID" field: Pharmacy identification information associated with the pharmacy name information included in the patient information registration request data

[0094] [Notification of family doctor registration (S1131)] After step S1130, the server 30 executes notification of personal care registration. Specifically, processor 32 identifies the pharmacy contact information associated with the primary pharmacy identification information. The processor 32 sends a notification to the contact person indicated in the pharmacy contact information indicating that the pharmacy has been registered as a regular pharmacy.

[0095] (4-2) Processing automatic transmission settings The setting of automatic transmission (OP2) of this embodiment will be described. Fig. 8 is a sequence diagram of the setting process of the pharmacy client device of this embodiment. Fig. 9 is a diagram showing an example of a screen displayed in the information processing of Fig. 8.

[0096] The trigger for the processing in Figure 8 is, for example, when a pharmacy user completes login (for example, authentication of pharmacy identification information) via a medicine notebook management application and gives a user instruction to start the process of setting up automatic transmission.

[0097] [Registering setting information (S1210)] As shown in FIG. 8, the pharmacy client device 10 executes registration of setting information. Specifically, the processor 12 displays a screen P1210 (FIG. 9) on the display.

[0098] The screen P1210 includes an operation object B1210 and field objects F12100 to F12101.

[0099] A field object F12100 is an object that receives input of model information of the receipt computer RC used by the pharmacy user.

[0100] A field object F12101 is an object that receives input of destination folder information.

[0101] When the pharmacy user inputs any information into the field objects F12100 to F12101 and operates the operation object B1210, the processor 12 sets in the storage device 11 the destination folder information input into the field object F12101. This allows the processor 12 to save the dispensing data acquired from the prescription computer RC in the destination folder.

[0102] [Settings Request (S1211)] After step S1210, the pharmacy client device 10 executes the setting request. Specifically, the processor 12 transmits the setting request data to the server 30. The setting request data includes, for example, the following information: -Model information entered in field object F12100

[0103] [Database Update (S1230)] After step S1211, the server 30 updates the database. Specifically, processor 32 refers to the pharmacy database and stores the model information included in the setting request data in the "model" field associated with the pharmacy identification information used for login.

[0104] (4-3) Automatic registration setting process The automatic registration setting (OP3) of this embodiment will be described. Fig. 10 is a sequence diagram of the automatic registration setting process of this embodiment. Fig. 11 is a diagram showing an example of a screen displayed in the information processing of Fig. 10.

[0105] The trigger for the processing in Figure 10 is, for example, when a patient completes login (for example, authentication of registered patient identification information) via an electronic medicine notebook application and gives a user instruction to start the automatic registration setup process. The registered patient identification information is registered patient identification information (hereinafter referred to as "target registered patient identification information") of a patient who is the target of automatic registration (hereinafter referred to as "target patient").

[0106] [Application for Automatic Registration (S1350)] As shown in FIG. 10, the patient client device 50 performs an application for automatic enrollment. Specifically, the processor 52 displays a screen P1350 (FIG. 11) on the display.

[0107] The screen P1350 includes an operation object B1350 and a field object F1350.

[0108] The operation object B1350 is an object that receives a user instruction to confirm an input to the field object F1350.

[0109] The field object F1350 is an object that accepts the designation of a pharmacy that is the target of automatic registration (hereinafter referred to as a "target pharmacy"). For example, the field object F1350 accepts the designation of the target pharmacy by designating any pharmacy name information from the pharmacy name information that corresponds to the family pharmacy identification information associated with the registered patient identification information.

[0110] [Application Request (S1351)] After step S1350, the patient client device 50 executes the application request. Specifically, when the patient designates any target pharmacy in the field object F1350 and operates the operation object B1350, the processor 52 transmits the application request data to the server 30. The application request data includes, for example, the following information: - Target registered patient identification information - Pharmacy name information entered in field object F1350

[0111] [Forwarding application request (S1330)] After step S1351, the server 30 transfers the application request. Specifically, the processor 32 refers to the pharmacy database to identify the pharmacy identification information associated with the pharmacy name information included in the application request data. Processor 32 identifies pharmacy contact information associated with the pharmacy identification information. The processor 32 refers to the registered patient database to identify the registered patient name information, registered patient gender information, and registered patient date of birth information associated with the target registered patient identification information included in the application request data. The processor 32 sends the target registered patient identification information, the registered patient name information, the registered patient gender information, and the registered patient date of birth information contained in the application request data to the contact information indicated in the pharmacy contact information.

[0112] [Automatic Registration Approval (S1310)] After step S1330, the pharmacy client device 10 executes approval of the automatic registration. Specifically, the processor 12 displays screen P1310 (FIG. 11) on the display.

[0113] The screen P1310 includes a display object A1310, an operation object B1310, and field objects F13100 to F13101.

[0114] The display object A 1310 is an object that displays the following information: - Patient identification information included in the application request data - Registered patient name information included in application request data Registered gender information included in application request data Date of birth information included in application request data

[0115] The operation object B 1310 is an object that receives a user instruction to approve automatic registration.

[0116] The field object F13100 is an object that accepts input of corrected patient name information (that is, correct patient name information) when the patient name information of the target patient differs from the registered patient name information displayed in the display object A1310.

[0117] The field object F13101 is an object that receives input of patient identification information from the electronic medicine notebook of the target patient.

[0118] [Approval Request (S1311)] After step S1310, the pharmacy client device 10 executes the approval request. Specifically, when a pharmacy user checks the registered patient name information displayed in display object A1310 and, if the registered patient name information is correct, inputs the patient identification information for the electronic prescription hand into field object F13101 and operates operation object B1310, processor 12 sends approval request data to server 30. The approval request data includes, for example, the following information: - Electronic medicine notebook patient identification information entered in field object F13101

[0119] When a pharmacy user checks the registered patient name information displayed in display object A1310 and finds that the registered patient name information is incorrect, the pharmacy user inputs corrected patient name information (i.e., correct patient name information) into field object F13100, inputs electronic medication notebook patient identification information into field object F13101, and operates operation object B1310, the processor 12 sends approval request data to the server 30. The approval request data includes, for example, the following information: Corrected patient name information entered in field object F13100 - Electronic medicine notebook patient identification information entered in field object F13101

[0120] [Database Update (S1331)] After step S1311, the server 30 updates the database. Specifically, the processor 32 refers to the registered patient database and updates the following fields of the record associated with the electronic medication notebook patient identification information included in the approval request data. "Automatic registration flag" field: Information indicating that the patient is eligible for automatic registration "Modified patient name" field: Corrected patient name information included in the approval request data

[0121] (4-4) Automatic registration of medication notebook information The process (OP4) for automatically registering medication notebook information in this embodiment will be described. Fig. 12 is a sequence diagram of the process for automatically registering medication notebook information in this embodiment. Fig. 13 is a diagram showing an example of a screen displayed in the information processing in Fig. 12.

[0122] In the following, an example is shown in which the dispensing data is electronic medicine notebook data (an example of "electronic medicine notebook data based on dispensing data").

[0123] The trigger for the processing in Figure 12 is when the pharmacy user completes login (for example, authentication of pharmacy identification information) via the medicine notebook management application and the prescription computer RC sends dispensing data to the pharmacy client device 10.

[0124] [Saving dispensing data (S1410)] As shown in FIG. 12, the pharmacy client device 10 stores the dispensing data. Specifically, the processor 12 saves the electronic medicine notebook data in the save destination indicated by the save destination folder information set in the storage device 11 in step S1210. The processor 12 transmits to the server 30 the electronic medicine notebook patient identification information (for example, a list of file names including the electronic medicine notebook patient identification information) corresponding to the electronic medicine notebook data stored in the storage location.

[0125] [First butt (S1430)] After step S1410, the server 30 performs a first match. Specifically, processor 32 refers to the registered patient database updated in step S1331 to identify the record associated with the electronic medicine notebook patient identification information transmitted in step S1410. If the "automatic registration flag" field of the record stores information indicating that the patient is an eligible patient for automatic registration, the processor 32 determines that the match was successful. If the "automatic registration flag" field of the record does not store information indicating that the patient is an eligible patient for automatic registration, the processor 32 determines that the matching has failed. If there are multiple records associated with the electronic medicine notebook patient identification information transmitted in step S1410, processor 32 determines that the matching has failed.

[0126] [Notification of Matching Results (S1431)] After step S1430, the server 30 notifies the matching result. Specifically, if the matching is successful in step S1430, the processor 32 transmits a notification indicating that the matching is successful to the pharmacy client device 10. If the matching fails in step S1430, the processor 32 sends a notification indicating that the matching failed to the pharmacy client device 10.

[0127] [Transmission of dispensing data (S1411)] After step S1431, the pharmacy client device 10 transmits the dispensing data. Specifically, when the processor 12 receives the notification sent from the server 30 in step S1431, the processor 12 sends the electronic medicine notebook data saved in the save destination in step S1410 to the server 30.

[0128] [Temporary storage of dispensing data (S1431)] After step S1411, the server 30 temporarily stores the prescription data. Specifically, the processor 32 temporarily stores the electronic medicine notebook data transmitted in step S1411 in the storage device 31.

[0129] [Extraction of second matching information (S1435)] After step S1431, the server 30 extracts the second matching information. Specifically, processor 32 extracts the following information (hereinafter referred to as "second matching information") from the electronic medicine notebook data temporarily saved in step S1431. Electronic medicine notebook patient identification information Electronic medicine notebook patient name information Electronic medicine notebook gender information Electronic medicine notebook and date of birth information

[0130] [Second butt (S1434)] After step S1435, the server 30 executes the second matching. Specifically, processor 32 refers to the registered patient database associated with the pharmacy identification information used for logging in and searches for registered patient identification information corresponding to the patient information that corresponds to the second matching information extracted in step S1435. The registered patient identification information is information that satisfies all of the following conditions. The electronic medicine notebook patient name information extracted in step S1435 is associated with registered patient name information or revised patient name information that matches the patient name information. The electronic medicine notebook gender information extracted in step S1435 is associated with registered gender information that matches the gender information. The date of birth information is associated with the registered date of birth information that matches the date of birth information in the electronic medicine notebook extracted in step S1435.

[0131] [Notification of failure cause (S1435)] If the registered patient identification information is not found in step S1434 (that is, if the matching fails) (S1434-A), the server 30 notifies the cause of the failure. The cause of the matching failure is one of the following failure patterns. First failure pattern: At least one of the gender and date of birth does not match. Second failure pattern: The patient name corresponding to the registered patient name information stored in the "Registered Patient Name" field or the corrected patient name information stored in the "Corrected Patient Name" field does not match, and the gender and date of birth match.

[0132] In the case of the first failure pattern, the processor 32 sends a message indicating the cause of the failure to the pharmacy client device 10. The message includes the following information: - Items that failed to match (at least one of gender and date of birth) Registered patient name information

[0133] In the case of the second failure pattern, the processor 32 transmits to the pharmacy client device 10 the cause of the failure and a message prompting the user to correct the patient name.

[0134] [Suggestion of the cause of failure (S1412)] After step S1435, the pharmacy client device 10 executes presentation of the cause of failure. Specifically, the processor 12 displays screen P1410 or P1411 (FIG. 13) on the display based on the message sent in step S1435.

[0135] The screen page P1410 is an example of a screen that presents the cause of failure in the case of the first failure pattern. The screen P1410 includes a message indicating that the cause of the failure is a mismatch in at least one of gender and date of birth.

[0136] The screen P1411 is an example of a screen that presents the cause of failure in the case of the second failure pattern. The screen P1411 includes a message urging the user to correct the registered patient name information because the cause of the failure is a mismatch in the patient name, and an operation object B1411.

[0137] The operation object B1411 is an object that receives a user instruction to display the screen P1412.

[0138] When the pharmacy user operates the operation object B1411, the processor 12 displays a screen P1412 (FIG. 13) on the display. The screen P1412 includes the patient information of the patient corresponding to the second failure pattern, an operation object B1412, and a field object F1412.

[0139] The patient information of a patient that falls under the second failure pattern includes a combination of registered patient identification information, electronic medicine notebook patient identification information, registered patient name information, registered gender information, and registered date of birth information.

[0140] The field object F1412 is an object that receives input of corrected patient name information.

[0141] The operation object B1412 is an object that receives a user instruction to confirm an input to the field object F1412.

[0142] [Correction Request (S1413)] When screens P1411 to P1412 are displayed in step S1412 (when the failure cause is the second failure pattern), the pharmacy client device 10 executes the correction request. Specifically, when a pharmacy user operates operation object B1411 on screen P1411, inputs corrected patient name information into field object F1412 on screen P1412, and operates operation object B1412, the processor 12 sends correction request data to the server 30. The modification request data includes, for example, the following information: Corrected patient name information entered in field object F1412

[0143] [Register corrected patient name (S1436)] After step S1413, the server 30 executes registration of the corrected patient name. Specifically, processor 32 refers to the registered patient database to identify the registered patient identification information to be modified. The processor 32 stores the corrected patient name information included in the correction request data in the "corrected patient name" field associated with the registered patient identification information.

[0144] After step S1436, the server 30 re-executes the second matching (S1434).

[0145] [Database Update (S1437)] If the registered patient identification information is found in step S1434 (that is, if the matching is successful) (S1434-B), the server 30 updates the database. Specifically, the processor 32 identifies the registered patient identification information corresponding to the combination of patient name information, gender information, and date of birth information that matches the second matching information. The processor 32 adds a new record to the registered medication notebook database associated with the registered patient identification information. Processor 32 stores the following information in the new record: "Registered medicine notebook ID" field: Identification information for newly registered medicine notebook "Electronic medicine notebook" field: Electronic medicine notebook data temporarily saved in step S1432

[0146] [Delete dispensing data (S1438)] After step S1435 when the matching fails in step S1434 due to the first failure pattern, or after step S1437 (that is, when the matching is successful in step S1434), the server 30 executes deletion of the dispensing data. Specifically, the processor 32 deletes the electronic medicine notebook data temporarily saved in step S1432 from the storage device 31. As a result, information (particularly, personal information of the patient) that does not need to be presented to the electronic medicine notebook application is deleted from the server 30 from the electronic medicine notebook data.

[0147] (5) Summary of this embodiment According to this embodiment, the information of the patient basic information group contained in the electronic medicine notebook data (hereinafter referred to as "electronic medicine notebook personal information") is matched with the patient's personal information associated with the registered patient identification information, and if the match is successful, the electronic medicine notebook data based on the dispensing data is stored in association with the registered patient identification information. This prevents leakage of prescription history and personal information in the electronic medicine notebook application.

[0148] According to this embodiment, matching is performed based on the patient's name, gender, and date of birth, which more reliably prevents leakage of prescription history and personal information in the electronic medicine notebook application.

[0149] According to this embodiment, if there is a mismatch in at least the gender and date of birth of the patient, it is determined that the matching has failed. This makes it possible to more reliably prevent leakage of prescription history and personal information in the electronic medicine notebook application.

[0150] According to this embodiment, if the patient names do not match, it is determined that the matching has failed, and a message is displayed prompting the user to correct the patient name. This prevents leakage of prescription history and personal information in the electronic medicine notebook application, and also makes it easy to correct any matching errors that may have occurred.

[0151] According to this embodiment, the match is performed using the corrected patient name. This prevents leakage of prescription history and personal information in the electronic medicine notebook application, and also makes it easy to correct any matching errors that may have occurred.

[0152] According to this embodiment, after the electronic medicine notebook data is stored in the database, or after a matching failure occurs, the temporarily stored prescription data is deleted. This makes it possible to prevent unnecessary data from remaining in the server 30.

[0153] (6) Variations A modification of this embodiment will now be described.

[0154] (6-1) Variation 1 A description will be given of Modification 1. Modification 1 is an example in which processing is performed according to the model of the receipt computer RC.

[0155] (6-1-1) Automatic registration of medicine notebook information in Modification 1 The process of automatic registration of medicine notebook information in Modification 1 will be described.

[0156] The trigger for the process of automatically registering medicine notebook information in Modification 1 is the same as in this embodiment.

[0157] [Saving dispensing data (S1410)] As shown in FIG. 12, the pharmacy client device 10 stores the dispensing data in the same manner as in the present embodiment.

[0158] [First match (S1430) ~ Notification of successful match (S1431)] After step S1410, the server 30 executes the first matching and notification of successful matching, similarly to the present embodiment.

[0159] [Transmission of dispensing data (S1411)] After step S1431, the pharmacy client device 10 transmits the dispensing data in the same manner as in the present embodiment.

[0160] [Temporary storage of electronic medicine notebook data (S1431) ~ Extraction of second matching information (S1435)] After step S1411, the server 30 executes the process of temporarily storing the electronic medicine notebook data and extracting the second matching information, similar to the present embodiment.

[0161] [Second butt (S1434)] After step S1435, the server 30 executes the second matching. Specifically, the storage device 31 stores a format table and a format conversion model for each format of the electronic medicine notebook data. The format table describes the correlation between the model of the receipt computer RC and the format conversion model. The format conversion model describes the correlation between text information specific to the format of the electronic medicine notebook data (for example, text information in external characters) and text information in a specified format that can be handled by the server 30 (hereinafter referred to as the "server format").

[0162] The processor 32 references the pharmacy database to identify the model information associated with the pharmacy identification information used for login. The processor 32 refers to the format table and identifies the format conversion model corresponding to the model information. Processor 32 inputs the patient name information (that is, text information) of the second matching information extracted in step S1435 into the format conversion model, thereby converting the patient name information into text information in the server format. Processor 32 refers to the registered patient database associated with the pharmacy identification information used for logging in, and searches for registered patient identification information corresponding to the gender information and date of birth information contained in the second matching information extracted in step S1435 and the converted text information (i.e., patient name information in server format).

[0163] [Notification of failure cause (S1435) ~ Deletion of dispensing data (S1438)] After step S1434, the server 30 executes the processes from notifying the cause of the failure to deleting the prescription data, as in the present embodiment.

[0164] [Suggestion of cause of failure (S1412) ~ Request for correction (S1413)] After step S1435, pharmacy client device 10 executes the presentation of the cause of failure and the correction request, similarly to the present embodiment.

[0165] (6-1-2) Summary of Modification 1 According to the first modification, the second matching is performed according to the format of the electronic medicine notebook data, which depends on the model of the receipt computer RC. This allows the second matching to be performed reliably regardless of the model of the receipt computer RC.

[0166] (6-2) Variation 2 A description will be given of Modification 2. Modification 2 is an example in which the prescription computer RC generates dispensing data including electronic medicine notebook data and information other than the electronic medicine notebook data.

[0167] The dispensing data of variant 2 is, for example, medical cooperation data. Medical cooperation data is data for linking medical institutions with each other. The medical cooperation data includes electronic medicine notebook data (an example of "electronic medicine notebook data based on dispensing data") and information other than the electronic medicine notebook data. The medical cooperation data includes at least one of the following: Data conforming to the HL7 (Health Level Seven) standard Data conforming to NSHIPS (registered trademark) standards

[0168] (6-2-1) Automatic registration of medicine notebook information in variant 2 The process of automatic registration of medicine notebook information in Modification 2 will be described.

[0169] The trigger for the process of automatically registering medicine notebook information in the second modification is the same as in the present embodiment.

[0170] [Saving dispensing data (S1410)] As shown in FIG. 12, the pharmacy client device 10 stores the dispensing data. Specifically, the processor 12 saves the medical cooperation data in the save destination indicated by the save destination folder information set in the storage device 11 in step S1210. The processor 12 transmits to the server 30 the electronic medicine notebook patient identification information corresponding to the medical cooperation data stored in the storage location (for example, the electronic medicine notebook patient identification information included in the medical cooperation data).

[0171] [First match (S1430) ~ Notification of successful match (S1431)] After step S1410, the server 30 executes the first matching and notification of successful matching, similarly to the present embodiment.

[0172] [Transmission of dispensing data (S1411)] After step S1431, the pharmacy client device 10 transmits the dispensing data. Specifically, when the processor 12 receives the notification sent from the server 30 in step S1431, the processor 12 sends to the server 30 the medical cooperation data saved in the save destination in step S1410.

[0173] [Temporary storage of dispensing data (S1432)] After step S1411, the server 30 temporarily stores the prescription data. Specifically, the processor 32 temporarily stores in the storage device 31 the medical cooperation data transmitted in step S1411.

[0174] [Extraction of second matching information (S1432) - Registration of corrected patient name (S1436)] After step S1432, the server 30 executes the processes from extraction of the second matching information to registration of the corrected patient name, as in the present embodiment.

[0175] [Database Update (S1437)] If the registered patient identification information is found in step S1434 (that is, if the matching is successful) (S1434-B), the server 30 updates the database. Specifically, the processor 32 extracts the electronic medicine notebook data from the medical cooperation data temporarily saved in step S1432. The processor 32 identifies the registered patient identification information corresponding to the combination of patient name information, gender information, and date of birth information that matches the second matching information. The processor 32 adds a new record to the registered medication notebook database associated with the registered patient identification information. Processor 32 stores the following information in the new record: "Registered medicine notebook ID" field: Identification information for newly registered medicine notebook "Electronic medicine notebook" field: extracted electronic medicine notebook data

[0176] [Delete dispensing data (S1438)] After step S1435 when the matching fails in step S1434 due to the first failure pattern, or after step S1437 (that is, when the matching is successful in step S1434), the server 30 executes deletion of the dispensing data. Specifically, the processor 32 deletes from the storage device 31 the medical cooperation data that was temporarily saved in step S1432.

[0177] [Suggestion of cause of failure (S1412) ~ Request for correction (S1413)] After step S1435, pharmacy client device 10 executes the presentation of the cause of failure and the correction request, similarly to the present embodiment.

[0178] (6-2-2) Summary of Modification 2 According to the second modification, even if the prescription data includes electronic medicine notebook data and information other than the electronic medicine notebook data, the same effect as that of the present invention can be obtained.

[0179] (7) Other variations Other modifications will be described.

[0180] Storage device 11 may be connected to pharmacy client device 10 via network NW. Storage device 31 may be connected to server 30 via network NW. Storage device 51 may be connected to server 30 via network NW.

[0181] Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited to the above-described embodiments. Furthermore, the above-described embodiments can be improved or modified in various ways without departing from the spirit of the present invention. Furthermore, the above-described embodiments and modifications can be combined. [Explanation of symbols]

[0182] 1: Information processing system 10: Pharmacy client device 11:Storage device 12: Processor 13: Input / output interface 14: Communication interface 30: Server 31:Storage device 32: Processor 33: Input / output interface 34: Communication interface 50: Patient client device 51:Storage device 52: Processor 53: Input / output interface 54: Communication interface

Claims

1. a means for acquiring the dispensing data generated by the receipt computer in response to the dispensing data being stored at a predetermined address in a storage device of the pharmacy client device; the dispensing data includes patient personal information; a means for storing registered patient identification information for identifying the patient and registered personal information of the patient in association with each other; A means for matching personal information included in the prescription data with the registered personal information, If the matching is successful, a means for storing electronic medicine notebook data based on the dispensing data in association with the registered patient identification information is provided. Information processing device.

2. The personal information included in the dispensing data and the registered personal information each include patient name information related to the patient's name, gender information related to the patient's gender, and date of birth information related to the patient's date of birth. The information processing device according to claim 1 .

3. The matching means determines that the matching has failed when at least one of the gender information and the date of birth information does not match. The information processing device according to claim 2 .

4. The matching means determines that the matching has failed if the patient name information does not match, a means for notifying a message prompting correction of registered patient name information associated with the registered patient identification information; The information processing device according to claim 2 .

5. means for obtaining corrected patient name information from the pharmacy client device; The matching means matches the patient name information included in the dispensing data with the corrected patient name information. The information processing device according to claim 4 .

6. means for converting patient name information included in the prescription data into text information in a predetermined format according to the format of the prescription data; the matching means matches the text information with registered patient name information associated with the registered patient identification information; 6. The information processing device according to claim 2.

7. The storage means comprises: Temporarily storing the prescription data; The electronic medicine notebook data included in the dispensing data is stored in association with the registered patient identification information; deleting the temporarily stored dispensing data; 6. The information processing device according to claim 1.

8. Computer, When the prescription data generated by the prescription computer is stored at a predetermined address in the storage device of the pharmacy client device, the pharmacy client device functions as a means for acquiring the prescription data; the dispensing data includes patient personal information; functioning as a means for storing registered patient identification information for identifying the patient and registered personal information of the patient in association with each other; A means for matching personal information included in the prescription data with the registered personal information, If the matching is successful, the electronic medicine notebook data based on the dispensing data is stored in association with the registered patient identification information. Program for.

9. An information processing system including a pharmacy client device and a server, the pharmacy client device; a storage device; a means for transmitting the prescription data generated by the prescription computer to the server in response to the prescription data being stored in a predetermined address of the storage device; the dispensing data includes patient personal information; The server means for acquiring the dispensing data from the pharmacy client device; a means for storing registered patient identification information for identifying the patient and registered personal information of the patient in association with each other; A means for matching personal information included in the prescription data with the registered personal information, If the matching is successful, a means for storing electronic medicine notebook data based on the dispensing data in association with the registered patient identification information is provided. Information processing system.

10. The computer In response to the prescription data generated by the receipt computer being stored at a predetermined address in a storage device of the pharmacy client device, a step of acquiring the prescription data is performed; the dispensing data includes patient personal information; Execute a step of storing registered patient identification information that identifies the patient and registered personal information of the patient in association with each other; Execute a step of matching personal information included in the prescription data with the registered personal information; If the matching is successful, a step of storing electronic medicine notebook data based on the dispensing data in association with the registered patient identification information is executed. Information processing methods.

Images