JP6592172B1 - Order management system and program - Google Patents

Abstract

To make it possible to use data in which a doctor who has made a prescription and information on a medicine actually received by a patient are linked. An order management system for managing waiting in a plurality of facilities, comprising a list of waiting lists of medical institutions including information for identifying users and information of doctors in charge, information for identifying users and users Use the waiting list storage unit that holds the waiting list of pharmacies that contains information on the drugs actually received by the patient, the records included in the waiting list of medical institutions, and the records included in the waiting list of pharmacies. Data collation unit that collates based on information identifying the person, information on the doctor in charge included in the record of the medical institution that matches the information identifying the user, and the drug actually received by the user included in the record of the pharmacy A data management unit that manages the information in association with each other. [Selection] Figure 5

Description

  The present invention relates to an order management system and a program.

  Information on medicines prescribed to patients at medical institutions is managed by prescription data, receipt system data, and the like (for example, Patent Documents 1 and 2).

  On the other hand, a system for managing a series of operations from reception to medical examination and accounting is used to manage patient waiting in medical institutions and pharmacies.

JP2018-185813 JP 2007-280134 A

  When a pharmaceutical manufacturer tries to use prescription data or receipt data to know the tendency of a medicine prescribed to a patient by a doctor, in the former case, whether the medicine actually received by the patient at the pharmacy is a starting medicine It cannot be distinguished whether it is a medicine. In the latter case, the data is limited to the data of a medical institution that has introduced a reception system from which a pharmaceutical manufacturer can acquire data.

  The present invention has been made in view of the circumstances described above, and it is an object of the present invention to make it possible to use data in which a doctor who has prescribed a medicine and information on medicines actually received by a patient are linked. I will.

An order management system according to an embodiment of the present invention is an order management system that manages waiting for orders in a plurality of facilities,
The order in which the waiting list of the medical institution including information identifying the user and the information of the doctor in charge, and the waiting list of the pharmacy including the information identifying the user and the information of the drug actually received by the user are held. A waiting list storage unit;
A data collation unit that collates records included in the waiting list of the medical institution and records included in the waiting list of the pharmacy with information identifying a user,
The information of the doctor in charge included in the record of the medical institution that matches the information specifying the user to each other and the information of the medicine actually received by the user included in the record of the pharmacy are associated and managed A data management unit.

  Further, based on the information of the doctor in charge and the information of the drug actually received by the user, which are linked by the information for identifying the user, the drug actually received by the user for each doctor in charge You may make it provide the data total part which totals the number of cases.

  ADVANTAGE OF THE INVENTION According to this invention, the data which linked | related the doctor who performed prescription and the information of the pharmaceutical actually received by the patient can be utilized.

The figure which shows schematic structure of the order management system 1000 which concerns on embodiment of this invention. The block diagram which shows the main structures of order management terminal 200A, B which concerns on embodiment of this invention. The flowchart of the order management in the medical institution by the order management system 1000 which concerns on embodiment of this invention. The flowchart of the order management in the pharmacy by the order management system 1000 which concerns on embodiment of this invention. The flowchart of the update process of the prescription information management table TA3 by the order management system 1000 which concerns on embodiment of this invention.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In addition, the same code | symbol is attached | subjected to the same element and the overlapping description is abbreviate | omitted.

  FIG. 1 is a diagram showing a schematic configuration of an order management system 1000 according to the present embodiment. As shown in FIG. 1, the order management system 1000 is installed at an order management server 100 installed at a management center, etc., an order management terminal 200A installed at a clinic A reception, etc., and a reception at a pharmacy B, etc. The order management terminal 200B is included. The order management server 100 is connected to the order management terminals 200A and 200B via the communication network N.

  The order management server 100 manages the waiting order of the clinic A registered / updated via the order management terminal 200A and the waiting order of the pharmacy B registered via the order management terminal 200B. In the example of FIG. 1, only the clinic A and the pharmacy B are shown as the facilities, but the order management server 100 actually manages waiting for the order of other facilities. In the example of FIG. 1, one order management terminal 200 </ b> A, 200 B is illustrated for one facility, but the order management server 100 is actually connected to a plurality of order management terminals in one facility. The registration / update waiting for the turn is accepted from each terminal.

  The order management server 100 is configured by a general-purpose computer, and a server function is realized by operating a predetermined server program on the computer. The number of computers constituting the order management server 100 is not necessarily one, and may be composed of a plurality of computers distributed on the communication network N.

  The order management server 100 includes a management database 110 for managing the order management terminal 200 for each facility, and a processor (data collation unit, data management unit, data aggregation unit) 120. The management database 110 includes a client management table TA1, a status management table (order waiting list storage unit) TA2, and a prescription information management table TA3.

  In the client management table TA1, a unique ID and a passcode (account) assigned to the order management terminal 200 are registered for each facility. One record of the client management table TA1 includes, for example, a “clinic A” record, “ID: A1...”, “Passcode: AA2. ... ”,“ Pass code: BB2. These pieces of information are set by, for example, an administrator (for example, the owner of a facility) who performs management waiting in each facility at the time of system introduction. When a plurality of order management terminals 200 are used in one facility, the same ID and passcode may be used. For example, a plurality of IDs and passwords may be used properly according to predetermined conditions. .

  In the status management table TA2, a waiting list for each facility is registered. The order waiting list includes a list of persons who are waiting for an order (order waiting group) and information (status information) indicating a waiting state of each order waiting group.

  The information included in the waiting list can be set by the manager or the like for each facility. For example, one record in the “Clinic A” waiting list includes the reception number “1”, the reception time “13:03”, the status “Guided”, the examination ticket number “A1001”, the insurance card number (users Information to be identified) includes information such as “123456”, the medical department “internal medicine”, and the doctor in charge “X”. In addition, information such as name, contact e-mail address, and telephone number can be included.

  In addition, one record in the waiting list of “pharmacy B” includes a reception number “2”, a reception time “15:10”, a status “calling”, a health insurance card number “123456”, a generic request presence / absence “present”, Information such as drug information “abc” is included. In addition, information such as name, contact e-mail address, and telephone number can be included. The presence or absence of generic hope is information indicating whether or not the patient desires a generic drug (generic drug). The drug information is the product name of the drug actually received by the patient based on the prescription issued by the doctor. If the patient does not wish for a generic drug, the prescribed original drug is recorded, and if a generic drug is desired, the generic drug is recorded.

  The status includes “Waiting”, which is the state before the turn arrives, “Calling”, which indicates that the turn has arrived, and the person who has come to the turn is actually guided to the examination room or counter “Guided”, “correspondence completed” in which the examination and response have been completed, “cancelled” in which the waiting for the order is canceled, and the like are included. What items are set as the status can be appropriately set and changed by the manager of each facility.

  The contents of the waiting list are updated based on new registration information and status update information (details will be described later) in the waiting list transmitted from the order management terminals 200A and 200B.

  In the prescription information management table TA3, the total information of the medicines actually received by the patient is registered based on the prescription issued by each doctor. For example, for the doctor “X”, information such as the drug “abc”, the number “10”, the drug “def”, the number “5”, the drug “ghi”, and the number “3” is included. That is, it is recorded that the doctor X prescribed the pharmaceutical abc 10 times, the pharmaceutical def 5 times, and the pharmaceutical ghi 3 times. The information in the prescription information management table TA3 is aggregated by associating the records in the status management table TA2 of the medical institution such as the clinic and the records in the status management table TA2 of the pharmacy with the patient information (for example, insurance card number). Is done.

  The processor 120 includes an arithmetic and logic unit (such as a CPU) that processes arithmetic operations, logic operations, bit operations, and the like and various registers, and manages the order by executing various programs stored in storage means such as a ROM. Each part of the server 100 is centrally controlled. In addition, the processor 120 also executes a computer program (order management application) for managing turn waiting in cooperation with the order management terminals 200A and 200B.

  The communication network N includes a communication network capable of transmitting / receiving information to / from each other between the order management server 100 and the order management terminals 200A and 200B. The communication network N is, for example, the Internet, a LAN, a dedicated line, a telephone line, a corporate network, a mobile communication network, Bluetooth (registered trademark), WiFi (Wireless Fidelity), other communication lines, or a combination thereof. It does not matter whether it is wired or wireless.

  The order management terminals 200A and 200B can exchange data with the order management server 100 via the communication network N such as a tablet terminal, a personal computer (PC), a notebook PC, a smartphone, a mobile phone, and a personal digital assistant (PDA). Any terminal device can be used.

  FIG. 2 is a block diagram showing a main configuration of the order management terminals 200A and 200B. The order management terminal 200 includes a processor 210, an input device 215, a display device 216, a communication interface 220, and a storage resource 230. The order management terminal 200 accepts inputs such as registration and update to the waiting list by a user who has come to the facility or an employee of the facility operating the input device 215 such as a touch panel.

  The processor 210 includes an arithmetic logic unit (CPU or the like) that processes arithmetic operations, logic operations, bit operations, and the like and various registers, and executes various programs stored in the storage resource 230 to execute the order management terminal 200. Central control of each part. The various registers are, for example, a program counter, a data register, an instruction register, a general-purpose register, and the like.

  The input device 215 includes various operation buttons and a touch panel 215a for accepting an input such as acceptance to the waiting list or disappearance from the waiting list.

  The display device 216 is a device for displaying a waiting list, a reception screen, and a status management screen, and is configured by a liquid crystal display, for example.

  The communication interface 220 is a hardware module for connecting to the communication network N and communicating with other devices via the communication network N. The communication interface 220 is a modulation / demodulation device such as an ISDN modem, an ADSL modem, a cable modem, an optical modem, or a soft modem.

  The storage resource 230 is, for example, a logical device provided by a storage area of a physical device. The physical device is a computer-readable recording medium such as a disk drive or a semiconductor memory (ROM, RAM, etc.). The storage resource 230 may be constructed by mapping a plurality of physical devices to one logical device, or may be constructed by mapping one physical device to a plurality of logical devices.

  The storage resource 230 stores an operating system program, a driver program, various data, and the like. Examples of the driver program include a communication interface driver program for controlling the communication interface 220. In addition to these various programs and various data, the storage resource 230 stores a computer program (order management application) AP1 for managing the waiting in cooperation with the order management server 100 by being executed by the processor 210. Has been.

(Order management in medical institutions)
Next, the order management in the medical institution (clinic A) by the order management system 1000 of this embodiment will be described with reference to the flowchart of FIG.

  On the display device 216 of the order management terminal 200A, information on the number of patients (users) waiting for the examination order of each department and the waiting time is displayed. These pieces of information are periodically acquired from the order management server 100 and updated.

  When the patient to be accepted performs an operation such as touching the display device 216, the order management terminal 200A displays an acceptance screen for accepting on the display device 216 (step S101). On the reception screen, a message that prompts the user to insert an examination ticket or insurance card into a card reader (not shown) is displayed. In addition, a message prompting the user to enter a medical department for which a medical examination is desired, a doctor in charge, and other necessary items (whether or not he / she wants to call, a telephone number or a mail address of a contact person at the time of calling) is displayed.

  The order management terminal 200A acquires information such as an examination ticket number and a health insurance card number via the card reading device. In addition, the order management terminal 200A acquires information on other necessary items input by the patient via the touch panel 215a or the like. (Step S102). The examination ticket number and the insurance card number may be obtained by reading the number written on the surface by reading an image or reading data recorded on an IC chip. Alternatively, the patient may input the number directly.

  When the acquisition of information necessary for reception is completed (step S103: YES), the order management terminal 200A transmits the acquired information to the order management server 100 (step S104). In addition, the order management terminal 200A displays a reception completion screen on the display device 216 (step S105). The reception completion screen displays a reception number (waiting number), a waiting time at the present time, a message prompting to receive a turn ticket, and the like. Note that the registration method is not limited to the above. For example, a clinic employee may provide input on behalf of a patient.

  The order management server 100 adds a new record to the order waiting list of the clinic A based on the new reception information received from the order management terminal 200A, and updates the status management table TA2 (step S106). For example, as a new record, the reception number “1”, the reception time “12:30”, the status “waiting”, the examination ticket number “A1001”, the insurance card number “123456”, the medical department “internal medicine”, the doctor in charge “ A record such as “X” is registered. As for the department and doctor in charge, when the patient does not specify, a preset department and doctor may be provisionally registered.

  When the order of the patients waiting for the turn comes (step S107: YES), the patient is called by oral, telephone, e-mail, etc., and the clinic A employee (doctor, nurse, medical clerk, etc.) Performs an operation of updating the status of the patient to “calling” using the order management terminal 200A (step S108). When the operation is executed, the order management terminal 200A transmits information for specifying the record to be updated (for example, reception number “1”) and information about the update operation (updated while calling the status) to the order management server 100. (Step S109). The order management server 100 updates the waiting list for the clinic A based on the received information (step S110). For example, the status of the record with the reception number “1” is updated to “calling”.

  When the patient who received the call is actually guided to the examination room (step S111: YES), the employee of the clinic A performs an operation of updating the status of the patient to “Guided” using the order management terminal 200A. (Step S112). When the operation is executed, information for specifying the record to be updated and information on the update operation are transmitted from the order management terminal 200A to the order management server 100, and the order management server 100 stores the target record in the waiting list of the clinic A. Update (step S113).

  When the examination of the patient is completed (step S114: YES), an employee of the clinic A performs an operation of updating the status of the patient to “completion of correspondence” using the order management terminal 200A (step S115). When the operation is executed, information for specifying the record to be updated and information on the update operation are transmitted from the order management terminal 200A to the order management server 100, and the order management server 100 stores the target record in the waiting list of the clinic A. Update (step S116). The patient completes the accounting and receives a prescription if the drug is prescribed.

(Order management in pharmacies)
Next, the order management in the pharmacy (pharmacy B) by the order management system 1000 of this embodiment will be described with reference to the flowchart of FIG.

  The display device 216 of the order management terminal 200B displays information on the number of patients (users) waiting for an order at the pharmacy and information on waiting time. These pieces of information are periodically acquired from the order management server 100 and updated.

  When the patient to be accepted performs an operation such as touching the display device 216, the order management terminal 200B displays an acceptance screen for acceptance on the display device 216 (step S201). On the reception screen, a message that prompts the user to insert the insurance card into a card reader (not shown) is displayed. In addition, a message prompting the image scanner or camera to read the contents of the prescription brought is displayed. In addition, a message prompting the user to enter whether or not the generic drug is desired and other necessary items (whether or not to call, the telephone number or mail address of the contact person at the time of calling) is displayed.

  The order management terminal 200B acquires information such as the insurance card number via the card reading device. In addition, the order management terminal 200B acquires information on other necessary items input by the patient via the touch panel 215a or the like. (Step S202). The insurance card number may be obtained by decoding the number written on the surface by reading an image or reading data recorded on an IC chip. Alternatively, the patient may input the number directly.

  When the acquisition of information necessary for reception is completed (step S203: YES), the order management terminal 200B transmits the acquired information to the order management server 100 (step S204). In addition, the order management terminal 200B displays a reception completion screen on the display device 216 (step S205). The reception completion screen displays a reception number (waiting number), a waiting time at the present time, a message prompting to receive a turn ticket, and the like. Note that the registration method is not limited to the above. For example, a pharmacy employee may perform input on behalf of the patient. Further, the contents of the prescription may be directly input by operating the order management terminal 200B.

  The order management server 100 adds a new record to the order waiting list of the pharmacy B based on the new reception information received from the order management terminal 200B, and updates the status management table TA2 (step S206). For example, as a new record, records such as reception number “2”, reception time “15:30”, status “waiting”, health insurance card number “123456”, presence / absence of generic request “medicine information” “-” are registered. Is done. Drug information is not registered at the time of registration.

  When the order of the patients waiting for the turn comes (step S207: YES), the target patient is called and an employee of the pharmacy B (pharmacist, office worker, etc.) uses the order management terminal 200B to The status is updated to “calling” (step S208). When the operation is executed, information for specifying the record to be updated and information on the update operation are transmitted from the order management terminal 200B to the order management server 100, and the order management server 100 selects the target record in the waiting list of the pharmacy B. Update (step S209).

  When the patient who has received the call is guided to a counter that actually delivers the medicine (step S210: YES), the employee of the pharmacy B updates the status of the patient to “Guided” using the order management terminal 200B. An operation is performed (step S211). When the operation is executed, information for specifying the record to be updated and information on the update operation are transmitted from the order management terminal 200B to the order management server 100, and the order management server 100 selects the target record in the waiting list of the pharmacy B. Update (step S212).

  If the patient wants a generic drug (step S213: YES), the pharmacist at the pharmacy B gives the generic drug (for example, “abc”) and uses the order management terminal 200B to check the waiting list. An operation for registering the drug information “abc” given to the patient in the drug information of the patient is performed (step S214). On the other hand, if the patient does not want a generic drug (step S213: NO), the starting drug (for example, “def”) is handed to the patient, and the patient's drug in the waiting list is used using the order management terminal 200B. An operation of registering the information “def” of the medicine delivered to the patient in the information is performed (step S215).

  The order management terminal 200B transmits information specifying the record to be updated (for example, the receipt number “2”) and the input drug information (for example, “abc”) to the order management server 100 (step S216). The order management server 100 updates the target record in the order waiting list of the pharmacy B based on the received information (step S217). For example, the contents of the record of the reception number “2” are the reception number “2”, the reception time “15:30”, the status “Guided”, the insurance card number “123456”, the generic request presence / absence “present”, the drug information “ abc ".

  When the patient receives the medicine and the accounting is finished (step S218: YES), the employee of the pharmacy B uses the order management terminal 200B to update the patient's status to “completion completed” (step S219). When the operation is executed, information for specifying the record to be updated and information on the update operation are transmitted from the order management terminal 200B to the order management server 100, and the order management server 100 selects the target record in the waiting list of the pharmacy B. Update (step S220).

(Update of prescription information management table)
Next, update processing of the prescription information management table TA3 by the order management system 1000 of this embodiment will be described with reference to the flowchart of FIG.

  The order management server 100 matches the waiting list of medical institutions (for example, clinic A) registered in the status management table TA2 periodically (for example, 24:00 every day) with the waiting list of pharmacies (for example, pharmacy B). From both lists, a record whose status is “completion of correspondence” and whose insurance card number matches is extracted (step S301). For example, the reception time “12:30” from the clinic A list, the status “completion completed”, the examination ticket number “A1001”, the insurance card number “123456”, the medical department “internal medicine”, the record of the doctor “X” in charge, the pharmacy From the list of B, records of the reception number “2”, the reception time “15:30”, the status “completion of correspondence”, the insurance card number “123456”, the presence / absence of generic desire “present”, and the drug information “abc” are extracted.

  The order management server 100 acquires the information (“X”) of the doctor in charge from the record extracted from the clinic A list (step S302), and acquires the drug information (“abc”) from the record extracted from the list of the pharmacy B. Then, the prescription information management table TA3 is updated based on the acquired information (step S304). Specifically, for the corresponding doctor (“X”), 1 is added to the number of the corresponding medicine (“abc”).

  The information in the prescription information management table TA3 is used by pharmaceutical manufacturers and the like, and can be used for sales activities and the like by knowing the prescription tendency of each doctor.

  As described above, according to the present embodiment, the records in the waiting list of medical institutions and the records in the waiting list of pharmacies are collated with insurance card numbers, and the records of medical institutions having the same insurance card number are matched. The information of the doctor in charge included and the information of the drug actually received by the patient included in the pharmacy record are linked and managed. Thereby, it is possible to use data in which the doctor in charge who has prescribed the medicine and the information on the medicine actually received by the patient are associated with each other.

  For example, the prescription includes information on the medicine prescribed with the doctor in charge, but the medicine recorded here is basically the original medicine. For this reason, it is impossible to distinguish whether the medicine actually received by the patient at the pharmacy is an original medicine or a generic medicine from the prescription information. Moreover, when using the data of a receipt system, since the system introduced by medical institutions differs, it is difficult to actually acquire the receipt data of all medical institutions. According to the present embodiment, by associating the information of the waiting list between the medical institution and the pharmacy, it is possible to easily associate the doctor in charge who has performed the prescription with the information on the medicine actually received by the patient.

  In addition, based on the information of the doctor in charge linked by the insurance card number and the information of the drug actually received by the patient, the number of drugs actually received by the patient is counted for each doctor in charge. . Thereby, a pharmaceutical manufacturer or the like can provide data for knowing a tendency of a medicine prescribed to a patient by a doctor (a medicine actually used by the patient). In addition to prescription trends for each doctor, the data can also be used to understand trends for each pharmacy (such as the rate at which generic drugs are selected).

  In the present embodiment, the insurance card number is used to link the data of the medical institution and the pharmacy. However, any information that can identify the patient can be used without being limited to the insurance card number. For example, an e-mail address registered at the time of registration for registration, a my number, or the like may be used.

  The present invention is not limited to the above-described embodiment, and can be implemented in various other forms without departing from the gist of the present invention. For this reason, the said embodiment is only a mere illustration in all points, and is not interpreted limitedly. For example, the above-described processing steps can be arbitrarily changed in order as long as the processing contents do not contradict each other, or can be executed in parallel.

1000 ... Order management system 100 ... Order management server 110 ... Management database 120 ... Processor 200A, 200B ... Order management terminal 210 ... Processor 215 ... Input device 215a ... Touch panel 216 ... Display device 220 ... Communication interface 230 ... Storage resource TA1 ... Client management Table TA2 ... Status management table TA3 ... Prescription information management table N ... Communication network AP1 ... Order management application

Claims (3)

An order management system for managing waiting in a plurality of facilities,
The order in which the waiting list of the medical institution including information identifying the user and the information of the doctor in charge, and the waiting list of the pharmacy including the information identifying the user and the information of the drug actually received by the user are held. A waiting list storage unit;
A data collation unit that collates records included in the waiting list of the medical institution and records included in the waiting list of the pharmacy with information identifying a user;
The information of the doctor in charge included in the record of the medical institution that matches the information specifying the user to each other and the information of the medicine actually received by the user included in the record of the pharmacy are associated and managed And a data management unit for performing the order management system.   The number of drugs actually received by the user for each doctor in charge, based on the information of the doctor in charge and the information of the drug actually received by the user, linked by the information for identifying the user The order management system according to claim 1, further comprising a data totaling unit that counts. A computer that manages the waiting time in multiple facilities,
The order in which the waiting list of the medical institution including information identifying the user and the information of the doctor in charge, and the waiting list of the pharmacy including the information identifying the user and the information of the drug actually received by the user are held. A waiting list storage unit;
A data collation unit that collates records included in the waiting list of the medical institution and records included in the waiting list of the pharmacy with information identifying a user,
The information of the doctor in charge included in the record of the medical institution that matches the information specifying the user to each other and the information of the medicine actually received by the user included in the record of the pharmacy are associated and managed A program that functions as a data management unit.

Images