JP2007011883A - Inquiry method for medication history, server device, and terminal device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a medication history inquiry method, a server device, and a terminal device, which can acquire suitable information by that patients inquire a pharmacist. <P>SOLUTION: A pharmacy server 400 of this system is provided with a data-holding part 50, which stores patient IDs by which patients are uniquely identified, corresponding with medicine name IDs which uniquely identify drug names that a patient has taken, a receiving part 41, which receives the patient IDs from terminal devices 100 which pharmacists has, a data acquiring part 42, which acquires the medicine name IDs corresponding with the patient ID which the receiving part 41 receives retrieving the data holding part 50, and a transmitting part 43, which transmits to the terminals 100 the medicine name IDs which the data acquiring part 42 acquires. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a medicine history inquiry method, a server device, and a terminal device.

  Conventionally, when a prescription of a medicine is issued from a doctor to a patient, the patient goes to a pharmacy etc. with the prescription, submits the prescription to a pharmacist, and dispenses the medicine. . However, the contents of the prescription are highly specialized and may be difficult for the patient to understand, or the patient himself / herself may have difficulty grasping the history of the medicine taken. For this reason, recently, notebooks called “medicine notebooks” that record the contents of prescriptions issued to the same patient are in circulation.

Moreover, in order to apply more detailed drug information to a patient, a technique is disclosed in which information about the prescription is transmitted to a patient's mobile terminal by e-mail (see, for example, Patent Document 1).
JP 2004-178265 A

  However, even if information is sent directly to the patient's mobile terminal, the information is highly specialized and sometimes difficult for the patient to understand. In addition, it is difficult for the patient to select and send only necessary information.

  In view of the above problems, an object of the present invention is to provide a medicine history inquiry method, a server device, and a terminal device that can acquire appropriate information when a patient makes an inquiry to a pharmacist.

  In order to achieve the above object, the first feature of the present invention is that medication history information (hereinafter referred to as “medicine history”) is transmitted from a terminal device possessed by a pharmacist to a server device connected to the terminal device via a communication network. And (b) a step in which the terminal device transmits a patient ID that uniquely identifies the patient to the server device, and (b) the server device is associated with the patient ID. A step of acquiring a medicine name ID for uniquely identifying a medicine name taken by the patient, (c) a step in which the server device transmits the medicine name ID to the terminal device, and (d) a terminal device in which the medicine name is The gist of the present invention is a drug history inquiry method including a step of displaying an ID. Here, the “communication network” refers to an information network (computer network) such as a LAN, WAN, Internet, or intranet.

  According to the information inquiry method according to the first feature, appropriate information can be acquired when the pharmacist who has received an inquiry from the patient makes an inquiry to the server.

  The second feature of the present invention is that: (a) a data holding unit that stores a patient ID that uniquely identifies a patient and a drug name ID that uniquely identifies a drug name taken by the patient; and (b) A receiving unit that receives a patient ID from a terminal device possessed by a pharmacist, (c) a data acquiring unit that searches the data holding unit and acquires a drug name ID associated with the patient ID received by the receiving unit; The gist of the invention is that the server device includes a transmission unit that transmits the medicine name ID acquired by the data acquisition unit to the terminal device.

  According to the server device concerning the 2nd characteristic, appropriate information can be acquired when the pharmacist who received the inquiry from a patient asks a server.

  The server device according to the second feature is a valid pharmacist by receiving a pharmacist ID for uniquely identifying the pharmacist and a password from the terminal device, and authenticating the pharmacist ID and the password. A determination unit for determining whether or not.

  According to this server device, information can be transmitted only to an inquiry from an authorized pharmacist.

  A third feature of the present invention is a terminal device possessed by a pharmacist, wherein (a) a patient ID for uniquely identifying a patient and a drug name ID for uniquely identifying a drug name taken by the patient are stored in association with each other. A connection unit connected to a server device having a data holding unit, (b) a transmission unit that transmits a patient ID to the server device, and (c) a medicine name ID associated with the patient ID is received from the server device. The gist is that the terminal device includes a receiving unit and (d) an output unit that displays a medicine name ID.

  According to the terminal device according to the third feature, appropriate information can be acquired when a pharmacist who has received an inquiry from a patient makes an inquiry to the server.

  According to the present invention, it is possible to provide a medicine history inquiry method, a server device, and a terminal device that can acquire appropriate information when a patient makes an inquiry to a pharmacist.

  Next, embodiments of the present invention will be described with reference to the drawings. In the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals. However, it should be noted that the drawings are schematic.

<First Embodiment>
(Configuration of drug history inquiry system)
The drug history inquiry system according to the first embodiment includes a terminal device 100 owned by a pharmacist, and a pharmacy server (server device) 400 connected to the terminal device 100 via the Internet 200. The drug history inquiry system inquires about the drug history from the terminal device 100 owned by the pharmacist to the pharmacy server 400 connected to the terminal device 100 via the communication network 200.

  The terminal device 100 is a device possessed by a pharmacist and may be any device that can communicate via the Internet 200, such as a mobile phone, a PHS, a PC, and a notebook PC. The terminal device 100 can be used regardless of time and place.

  The terminal device 100 may include a processing control device (CPU) 10 and have a connection unit 11, a transmission unit 12, and a reception unit 13 built in the CPU 10. Each of these units can be realized by executing a dedicated program for using a predetermined program language in a general-purpose computer such as a personal computer. The CPU 10 is connected to a data holding unit 20, a program holding unit 21, an input unit 30, and an output unit 31.

  The connection unit 11 connects to the pharmacy server 400 via the Internet 200.

  The transmission unit 12 transmits to the pharmacy server 400 the patient ID, the pharmacy code assigned to each pharmacy, the dispensing date, the inquiry date and time when the inquiry was made, and the like.

  The receiving unit 13 receives the drug name ID associated with the patient ID from the pharmacy server 400.

  The input unit 30 refers to devices such as a keyboard and a mouse. When an input operation is performed from the input unit 30, corresponding key information is transmitted to the CPU 10.

  The output unit 31 displays a medicine name ID transmitted from the pharmacy server 400, a medicine name associated with the medicine name ID, and the like. The output unit 31 indicates a screen such as a monitor, and a liquid crystal display (LCD), a light emitting diode (LED) panel, an electroluminescence (EL) panel, or the like can be used.

  The data holding unit 20 temporarily stores data in the middle of calculation or analysis, received data, and the like in the calculation in the CPU 10. The data holding unit 20 may be an internal storage device such as a RAM or an external storage device such as an HD.

  The program holding unit 21 is a storage medium that stores a control program for causing the CPU 10 to execute connection processing, transmission processing, reception processing, and the like. Examples of the recording medium include a RAM, a hard disk, a flexible disk, a compact disk, an IC chip, and a cassette tape. According to the recording medium holding such a program, the program can be easily stored, transported, sold, and the like.

  The pharmacy server 400 includes a processing control device (CPU) 40, and the receiving unit 41, the data acquisition unit 42, the transmission unit 43, and the determination unit 44 may be built in the CPU 10. Each of these units can be realized by executing a dedicated program for using a predetermined program language in a general-purpose computer such as a personal computer. In addition, a data holding unit 50, a program holding unit 51, an input unit 60, and an output unit 61 are connected to the CPU 40. Moreover, the pharmacy server 400 has been operating for 24 hours.

  The receiving unit 41 receives a patient ID, a pharmacist ID that uniquely identifies the pharmacist, and a password from the terminal device 100 of the pharmacist.

  The data acquisition unit 42 searches the data holding unit 50 and acquires the drug name ID associated with the patient ID received by the reception unit.

  The transmission unit 43 transmits the medicine name ID acquired by the data acquisition unit 42 to the terminal device 100. Further, the transmission unit 43 may transmit the medicine name ID to the terminal device 100 only by an inquiry from a valid pharmacist by the determination unit 44.

  The determination unit 44 determines whether or not the person is a valid pharmacist by authenticating the pharmacist ID and the password.

  The input unit 60 refers to devices such as a keyboard and a mouse. When an input operation is performed from the input unit 30, corresponding key information is transmitted to the CPU 40.

  The output unit 61 refers to a screen such as a monitor, and a liquid crystal display (LCD), a light emitting diode (LED) panel, an electroluminescence (EL) panel, or the like can be used.

  The data holding unit 50 stores a patient ID that uniquely identifies a patient and a drug name ID that uniquely identifies a drug name that the patient has taken. The data holding unit 50 may be an internal storage device such as a RAM or an external storage device such as an HD.

  The program holding unit 51 is a storage medium that stores a control program for causing the CPU 40 to execute reception processing, data acquisition processing, transmission processing, determination processing, and the like. Examples of the recording medium include a RAM, a hard disk, a flexible disk, a compact disk, an IC chip, and a cassette tape. According to the recording medium holding such a program, the program can be easily stored, transported, sold, and the like.

(Medication history inquiry method)
Next, the medicine history inquiry method according to the first embodiment will be described with reference to FIG.

  First, in step S101, an inquiry about a prescription is entered from the patient to the pharmacist. Various methods such as telephone and e-mail can be cited as an inquiry method. At this time, the patient informs the pharmacist of the pharmacy that received the prescription, the patient's name, patient ID, and specific inquiries.

  Next, in step S <b> 102, the pharmacist connects to the pharmacy server 400 via the Internet using the terminal device (for example, mobile phone) 100 owned by the pharmacist. Then, the pharmacist ID and password are input using the input unit 30 of the terminal device 100, and the terminal device 100 transmits the information to the pharmacy server 400. An example of a pharmacist ID and password input screen is shown in FIG.

  Next, in step S103, the pharmacy server 400 determines whether or not the user is a valid pharmacist by performing user authentication using the pharmacist ID and the password. Only in the case of a valid pharmacist, the processing from step S104 is performed.

  Next, in step S104, the pharmacist uses the input unit 30 of the terminal device 100 to input a pharmacy code, a patient ID, and a dispensing date as shown in FIG. Then, when the terminal device 100 transmits these pieces of information to the pharmacy server 400, a screen as shown in FIG. 6 is displayed on the output unit 31 of the terminal device 100.

  Next, in step S <b> 105, the pharmacy server 400 searches the data holding unit 50 and acquires a medicine name ID associated with the received patient ID. For example, the data holding unit 50 holds a database as shown in FIG. 3, and a patient ID and a medicine name ID are associated with each other.

  Next, in step S <b> 106, the pharmacy server 400 transmits a medicine history mail including a medicine name ID to the terminal device 100. In step S <b> 107, the terminal device 100 converts the medicine name ID into the medicine name, and displays the medicine history mail including the medicine name on the output unit 31. For example, as shown in FIG. 7, the medicine history mail may include an inquiry number, a medicine name, a patient ID, a name, a date of birth, a hospital name, and a doctor name that are uniquely assigned for each inquiry.

  In step S108, the pharmacist who has confirmed the medicine history mail notifies the patient of the inquiry content. This contact method includes various methods such as telephone and e-mail.

(Function and effect)
According to the pharmacy server 400, the terminal device 100, and the drug history inquiry method according to the first embodiment, the pharmacist who has received an inquiry from the patient uses the terminal device 100 to inquire about the drug history of the patient to the pharmacy server 400. Thus, appropriate information can be acquired.

  Further, the terminal device 100 can be used regardless of time and place, and the pharmacy server 400 is operated for 24 hours. Therefore, in response to an inquiry from a patient, a pharmacist can immediately obtain a drug history. . In this way, since it is possible to answer inquiries from patients even outside pharmacy business hours, it is possible to respond to emergencies.

  In addition, the pharmacy server 400 receives from the terminal device 100 a pharmacist ID that uniquely identifies the pharmacist and a password, and determines whether the pharmacist is a legitimate pharmacist by authenticating the pharmacist ID and password. Part 44 is provided. For this reason, information can be transmitted only to an inquiry from a legitimate pharmacist.

<Second Embodiment>
In the second embodiment, recording contents in the pharmacy server 400 of the contents inquired by the patient in the first embodiment will be described.

(Configuration of drug history inquiry system)
As shown in FIG. 1, the drug history inquiry system according to the second embodiment includes a terminal device 100 possessed by a pharmacist and a pharmacy server (server device) 400 connected to the terminal device 100 via the Internet 200. Prepare.

  The terminal device 100 is a device possessed by a pharmacist and may be any device that can communicate via the Internet 200, such as a mobile phone, a PHS, a PC, and a notebook PC.

  The terminal device 100 may include a processing control device (CPU) 10 and have a connection unit 11, a transmission unit 12, and a reception unit 13 built in the CPU 10. Each of these units can be realized by executing a dedicated program for using a predetermined program language in a general-purpose computer such as a personal computer. The CPU 10 is connected to a data holding unit 20, a program holding unit 21, an input unit 30, and an output unit 31.

  The transmission unit 12 transmits a pharmacy code, an inquiry number, an inquiry content classification code, a comment on the inquiry content, and the like to the pharmacy server 400.

  The connection unit 11, the reception unit 13, the input unit 30, the output unit 31, the data holding unit 20, and the program holding unit 21 are the same as those in the first embodiment, and thus description thereof is omitted here.

  Further, the pharmacy server 400 includes a processing control device (CPU) 40, and the reception unit 41, the data acquisition unit 42, the transmission unit 43, the determination unit 44, and the data recording unit 45 can be built in the CPU 40. . Each of these units can be realized by executing a dedicated program for using a predetermined program language in a general-purpose computer such as a personal computer. In addition, a data holding unit 50, a program holding unit 51, an input unit 60, and an output unit 61 are connected to the CPU 40.

  The data recording unit 45 records the pharmacy code, the inquiry number, the inquiry content classification code, and the comment for the inquiry content received from the terminal device 100 in the data holding unit 50. An example of the database stored in the data holding unit 50 is shown in FIG.

  Since the reception unit 41, data acquisition unit 42, transmission unit 43, determination unit 44, input unit 60, output unit 61, data storage unit 50, and program storage unit 51 are the same as those in the first embodiment, Then, explanation is omitted.

(Medication history inquiry method)
Next, a drug history inquiry method according to the second embodiment will be described with reference to FIG.

  First, in step S201, the pharmacist connects to the pharmacy server 400 via the Internet using the terminal device (for example, mobile phone) 100 that the pharmacist owns. Then, the pharmacist ID and password are input using the input unit 30 of the terminal device 100, and the terminal device 100 transmits the information to the pharmacy server 400.

  Next, in step S202, the pharmacy server 400 determines whether or not the user is a valid pharmacist by performing user authentication using the pharmacist ID and the password. Only in the case of a valid pharmacist, the processing from step S203 is performed.

  Next, in step S203, the pharmacist uses the input unit 30 of the terminal device 100 to input a pharmacy code and an inquiry number as shown in FIG. Then, the information is transmitted to the pharmacy server 400.

  Next, in step S204, the pharmacist uses the input unit 30 of the terminal device 100 to input a content classification code, an inquiry content, and an answer to the inquiry content, as shown in FIG. Then, the information is transmitted to the pharmacy server 400.

  Next, in step S205, the pharmacy server 400 records a response to the pharmacy code, content classification code, inquiry content, and inquiry content in association with the inquiry number.

(Function and effect)
According to the pharmacy server 400 according to the second embodiment, information on past inquiry contents can be accumulated.

(Other embodiments)
Although the present invention has been described according to the above-described embodiments, it should not be understood that the descriptions and drawings constituting a part of this disclosure limit the present invention. From this disclosure, various alternative embodiments, examples and operational techniques will be apparent to those skilled in the art.

  For example, in the first and second embodiments, it has been described that the data holding unit 50 holds the pharmacy code, the patient ID, the dispensing date, the inquiry date, and the drug name ID in association with each other, but other information is appropriately handled. You may hold it.

  In the first and second embodiments, it has been described that the pharmacy server 400 transmits the medicine name ID to the terminal device 100, converts the medicine name ID into the medicine name in the terminal device 100, and displays it. The server 400 may transmit the medicine name itself to the terminal device 100.

  As described above, the present invention naturally includes various embodiments not described herein. Therefore, the technical scope of the present invention is defined only by the invention specifying matters according to the scope of claims reasonable from the above description.

It is a composition block diagram of the medicine history inquiry system concerning the 1st and 2nd embodiment. It is a flowchart which shows the medicine history inquiry method which concerns on 1st Embodiment. It is an example of the database recorded on the data holding part of the pharmacy server which concerns on 1st Embodiment. It is an example of the input screen of the terminal device which concerns on 1st Embodiment (the 1). It is an example of the input screen of the terminal device which concerns on 1st Embodiment (the 2). It is an example of the output screen of the terminal device which concerns on 1st Embodiment (the 1). It is an example of the output screen of the terminal device which concerns on 1st Embodiment (the 2). It is a flowchart which shows the medical history inquiry method which concerns on 2nd Embodiment. It is an example of the database recorded on the data holding part of the pharmacy server which concerns on 2nd Embodiment. It is an example of the input screen of the terminal device which concerns on 2nd Embodiment (the 1). It is an example of the input screen of the terminal device which concerns on 2nd Embodiment (the 2).

Explanation of symbols

10 ... CPU
DESCRIPTION OF SYMBOLS 11 ... Connection part 12 ... Transmission part 13 ... Reception part 20 ... Data holding part 21 ... Program holding part 30 ... Input part 31 ... Output part 40 ... CPU
DESCRIPTION OF SYMBOLS 41 ... Reception part 42 ... Data acquisition part 43 ... Transmission part 44 ... Judgment part 45 ... Data recording part 50 ... Data holding part 51 ... Program holding part 60 ... Input part 61 ... Output part 100 ... Terminal apparatus 200 ... Internet 400 ... Pharmacy server

Claims (4)

A drug history inquiry method for inquiring drug history information from a terminal device possessed by a pharmacist to a server device connected to the terminal device via a communication network,
The terminal device transmitting a patient ID for uniquely identifying a patient to the server device;
The server device acquiring a drug name ID associated with the patient ID and uniquely identifying a drug name taken by the patient;
The server device transmitting the medicine name ID to the terminal device;
The terminal device includes the step of displaying the medicine name ID. A data holding unit for storing a patient ID for uniquely identifying a patient and a drug name ID for uniquely identifying a drug name taken by the patient;
A receiving unit for receiving the patient ID from a terminal device possessed by a pharmacist;
A data acquisition unit that searches the data holding unit and acquires a drug name ID associated with the patient ID received by the reception unit;
A server device comprising: a transmission unit that transmits the medicine name ID acquired by the data acquisition unit to the terminal device. The receiving unit receives a pharmacist ID for uniquely identifying the pharmacist and a password from the terminal device,
The server device according to claim 2, further comprising: a determination unit that determines whether or not the pharmacist ID is valid by authenticating the pharmacist ID and the password. A terminal device possessed by a pharmacist,
A connection unit connected to a server device having a data holding unit that stores a patient ID that uniquely identifies a patient and a drug name ID that uniquely identifies a drug name that the patient has taken;
A transmission unit for transmitting the patient ID to the server device;
A receiving unit that receives a drug name ID associated with the patient ID from the server device;
An output unit that displays the medicine name ID.

Images