JPH08180120A - Medicine history management system - Google Patents

Abstract

PURPOSE: To provide a medicine history management system which enables the medicine history of a patient who visits doctors in a hospital group to easily be referred to at the respective hospitals. CONSTITUTION: A host hospital has a communication I/F 24 for connecting the hospitals in the group through a network, a prescription data file 110 for recording the medicine histories of all patients examined at the hospitals in the group and performing centralized management, and a host computer 4 which performs a process for assigning the uniform patient numbers common to all the hospitals in the hospital group to new patients at all the hospitals in the hospital group; when a request specifying the uniform patient number of a patient is received from a hospital in the hospital group, the medicine histories of the patient prescribed for at all the hospitals in the hospital group are taken out of the prescription data file 110 and sent.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a drug history management system, and more particularly to a drug history management system in which a patient's drug history can be easily referred to from any hospital in the group regardless of which hospital the patient is treated in. .

[0002]

2. Description of the Related Art FIG. 4 is a diagram showing a conventional drug history management system in each hospital. In the hospital, L
An AN (Local Area Network) is constructed, and a plurality of terminal devices 2 installed in each examination room and the like and a host computer 4 are connected to each other. An external storage device is connected to the host computer 4 and is classified into a medical affairs database 6, a management file 8, a prescription data file 10, a drug master file 12 and a general-purpose master file 14. The medical affairs database 6 records information on accounting processing such as expenses for medical examination. The management file 8 contains information for managing the system environment such as the printer connection destination. The prescription data file 10 records the medication history, which is the content of the prescription for the patient. The drug master file 12 contains information on drugs. Then, in the general-purpose master file 14,
The doctor's name, drug usage, efficacy, etc. are not always necessary for medical treatment and include other information that cannot be included in any of the above-mentioned databases or is difficult to classify. Further, the host computer 4 is connected to a plurality of printers 16 arranged in the vicinity of the pharmacy, the terminal device 2, etc. for printing the prescription.

The terminal device 2 is a general personal computer, and accesses the host computer 4 to issue a prescription or the like. Each terminal device 2 has a drug master file 12 and a general-purpose master file 14 having the same contents as the above-mentioned host computer 4, and is appropriately downline loaded from the host computer 4.

Next, in the above system, the flow until a patient visits a hospital and a prescription is issued will be described.

If the patient is a returning patient, the doctor requests prescription information for the patient from the terminal device 2. When the host computer 4 identifies the patient based on the patient number for the patient included in the request from the terminal device 2, the patient information text 18 including the information on the patient from the medical affairs database 6 and the prescription data file 10 and the patient information text 18 for the patient. A prescription information text 20 including information on a prescription and past medication history (medicine history) is created and transmitted to the terminal device 2. The doctor decides the prescription of this time while displaying the information on the screen and referring to the drug history and the like included in the prescription information. After the prescription is performed, the information about the prescription for this time is added to the prescription information text 20 from the terminal device 2 and the host computer 4
Send to. The host computer 4 edits the received prescription information text 20 and updates the prescription data file 10 with the medication history of the patient. The updated prescription data file 10 is used as reference data for the next medical examination or previous DO data when the same prescription as the previous one is performed. In addition, the host computer 4 uses the management file 8
Obtain the information of the output printer from and issue a prescription.

On the other hand, if the patient is new, a number unique to each patient, generally called a patient number, is newly assigned to the patient. The doctor treats the patient in the same manner as a returning patient, but since he is the first visit, he does not obtain information about the patient's prescription, medication history, etc. The process after determining the prescription is the same as that for the returning patient, but since it is the first visit, the medication history of the patient is newly recorded in the prescription data file 10.

By the way, in a large-scale hospital, there are cases where affiliated hospitals, branch hospitals, clinics, and other medical institutions are located in remote areas to form a hospital group. FIG. 5 shows a schematic configuration of a hospital group including such a plurality of affiliated hospitals. A main hospital (hereinafter referred to as a host hospital), affiliated hospitals, affiliated hospitals, etc. have the above-mentioned drug history management system. And each is operating independently. When medical institutions that provide medical treatment such as host hospitals, affiliated hospitals, and affiliated hospitals are collectively called hospitals, it is possible to refer to past medication history regardless of which hospital the patient receives, considering the patient's relocation or referral. This is especially desirable within such hospital groups.

[0008]

However, in the past, even if similar drug history management systems were introduced, they were operated independently of each other, and therefore, refer to the drug history at the hospital that had been previously visited. It is not possible.

Further, since each hospital assigned a unique patient number for each new patient, in order to obtain the drug history recorded at each hospital, the patient number assigned at each hospital was used. You need to know.

Further, even if information is simply exchanged by connecting to a network, it is extremely difficult to find out the drug history of patients scattered in each hospital.

[0012] Further, there is no means for referencing the drug history from a hospital at the patient's travel destination or business trip destination.

The present invention has been made to solve the above problems, and an object thereof is to manage the drug history so that the drug history of patients treated in a hospital group can be easily referred to in each hospital. To provide a system.

[0013]

In order to achieve the above-mentioned object, the invention according to claim 1 is a drug history management system for managing the history of drugs administered to patients in each group. A common patient number common to all hospitals in each group is assigned to each new patient in all hospitals in the group, and the medical history of patients treated in the hospitals in the group using the unified patient number from all hospitals in the group It is characterized in that it can be referred to.

According to a second aspect of the present invention, in the drug history management system according to the first aspect, communication means within a group for network connection with hospitals within a group and a new patient at all hospitals within the group with a unified patient number. It has a common number numbering means for each number and a drug history management database that records the drug history of all patients treated in the hospitals in the group, and the drug history of patients treated in the hospitals in the group It is characterized by unified management.

The invention according to claim 3 is the drug history management system according to claim 1, characterized in that the unified patient number is provided separately from the patient number unique to each hospital.

According to a fourth aspect of the present invention, in the medical history management system according to the first aspect, a medical history management database for recording the medical history of all patients treated in the hospitals in the group is connected to an external communication device. And a communication means for controlling the medication history of the patient corresponding to the unified patient number designated by the communication device.

According to a fifth aspect of the invention, in the drug history management system according to the first aspect, a password is set for each unified patient number, and the password designated together with the unified patient number matches the password of the unified patient number. It is characterized in that the medication history of the patient corresponding to the unified patient number is transmitted only when.

[0018]

In the drug history management system according to the first aspect of the present invention having the above-mentioned configuration, all the patients in the group who are new to patients in the hospital group who are not undergoing medical treatment in any hospital in the group are treated. Since a unified patient number common to all hospitals is assigned, using a unified patient number assigned from any hospital in the group will show the patient's medication history regardless of which hospital in the group the patient was treated with. Can be referenced.

According to the second aspect of the present invention, by connecting each hospital to a network and recording the medication history carried out at any hospital in the medication history management database for centralized management, the medication history can be obtained using a unified patient number. By accessing the management database, the medication history of all patients can be easily obtained from any hospital in the group.

According to the third aspect of the present invention, if a patient number unique to each hospital is set in addition to the unified patient number, hospitals that conventionally used only patient numbers unique to each hospital can be easily made into hospital groups. Can be controlled.

According to the fourth aspect, by accessing the drug history management database via the communication means, it is possible to obtain the drug history of the patient treated in the hospital group from a hospital other than the hospital group.

According to the fifth aspect of the present invention, a password is set for each unified patient number, and when referring to the medication history of the patient, the password is entered together with the unified patient number. The medication history of the patient corresponding to the unified patient number can be referred only when the password specified with the unified patient number matches the password of the set unified patient number. You can refer to the medical history.

[0023]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT A preferred embodiment of the present invention will be described below with reference to the drawings. The same elements as those in the conventional example are designated by the same reference numerals, and the description thereof will be omitted.

FIG. 1 is a system configuration diagram showing an embodiment of a drug history management system according to the present invention, and FIG. 2 shows a schematic configuration of a drug history management system in a hospital group in this embodiment. It is a figure. The hospitals in the hospital group are connected via the public network 22. Conversely,
Network-connected medical institutions will belong to the hospital group. In this embodiment, as shown in FIG. 1, the host computer 4 is connected with a communication interface (I / F) 24 as intra-group communication means for network connection with hospitals within the group. The prescription data file 110 in the present embodiment is a drug history management database that records the drug history of all patients treated in the hospitals in the group. The other components are the same as the conventional ones.

The feature of this embodiment is that a unified patient number common to all hospitals in the hospital group is assigned to each new patient in all hospitals in the hospital group. As a result, all patients in the hospital group can be identified by the unified patient number, so that the medication history of the patient can be easily referred to using the unified patient number. In addition, in this embodiment, since the medication history of all patients is centrally managed in the prescription data file 110, if a medication history management database is accessed from any hospital, a certain patient will be examined at any hospital in the hospital group. Even if you have been treated, you can easily refer to the past medication history. The common number numbering means for numbering in this embodiment is the host computer 4 and its CP
It is realized by software executed by the U and the CPU. However, the system in each hospital must have a communication I / F to connect to the network, but a drug history management database that records the drug history of all patients and a common number numbering means are provided in any hospital. Just do it. In this embodiment, the medication history management database and the common number numbering means are provided in the same host hospital.

The process of assigning a unified patient number will be described below. Unless otherwise specified, all hospitals in this embodiment mean all hospitals belonging to a hospital group.

First, when a patient visits any hospital as a new patient, it is determined whether the patient is not receiving any medical treatment in any hospital in the hospital group, that is, whether the patient is a new patient in all hospitals. Contact the host computer 4. In this inquiry, the kana name, sex, date of birth, etc. of the patient are transmitted as information for identifying the patient, and the host computer 4 in the host hospital
The combination of this information will determine if it is a new patient within the hospital group. If you have been examined at another hospital in the hospital group, you have already assigned a uniform patient number to that patient at the time of examination at the other hospital.
The unified patient number and that effect are returned to the hospital that examines the patient (hereinafter referred to as the examination hospital). Therefore, the examination hospital does not assign a unified patient number even if it is a new case. On the other hand, if the patient is a new patient in the hospital group, a new unified patient number is assigned and the fact is returned to the examining hospital. In this way, the unified patient number is assigned to each new patient in the hospital group.

By the way, using the unified patient number in this embodiment does not mean that each hospital assigns a unique patient number. By providing a patient number unique to each hospital separately from the unified patient number, it is possible to achieve patient management in each hospital using the patient number unique to each hospital. Further, by using the unified patient number and the patient number together, it is possible to easily control hospitals that conventionally used only patient numbers unique to their own hospital within the hospital group.
The unified patient number and the patient number may be numbered independently or a part of the patient number may be used. For example, a unified patient number may be numbered by adding alphanumeric characters to the patient number so that it becomes a unique number. However, regarding this numbering method and the method of determining whether or not a new patient is present, the gist of the present invention is Absent.

In the case of a returning patient, since the unified patient number has already been assigned to that patient, it is not necessary to perform the process of assigning the unified patient number.

As described above, when the unified patient number is assigned to the patient, the patient will undergo medical examination. Hereinafter, the process of referring to the medical history of the patient at the medical examination hospital will be described.

When the patient is a returning patient in the hospital group regardless of whether the patient is a new patient or a returning patient in the medical examination hospital, the doctor of the medical examination hospital requests the prescription information for the patient from the terminal device 2 to the host hospital. When the host computer 4 of the host hospital identifies the patient through the public network 22 based on the unified patient number for the patient, the patient information text 18 and the prescription information text 20 are read from the medical affairs database 6 and the prescription data file 110 as in the conventional case. Create and send to the consultation hospital. As described above, the prescription data file 110 centrally manages the prescription information of the patients in all hospitals, so that it is possible to obtain the entire medication history of the patient at the medical examination hospital. The doctor decides the prescription for this time while displaying the information on the screen and referring to the drug history and the like. When the patient is a new patient in the hospital group, there is no prescription information in the past, so the current prescription is determined by medical examination.

After the prescription is carried out, the information about the prescription for this time is added to the prescription information text 20 from the terminal device 2 and transmitted to the host computer 4 of the host hospital. If there is a new patient, create a new one and send it. The host computer 4 of the host hospital edits the received prescription information text 20 and updates or newly registers it in the prescription data file 110 as the medication history of the patient. The host computer 4 in the examination hospital obtains the information of the output destination printer from the management file 8 and issues the prescription.

In this way, by assigning a unified patient number to each patient and centrally managing the drug history of all the hospitals in the prescription data file 110, the patient can be seen in another hospital by moving or being referred. Even in this case, the past drug history can be easily obtained from the host hospital via the public network 22 at the hospital to which the drug is moved. Of course, when the host hospital and the consultation hospital are the same, it is not necessary to access the prescription data file 110 via the public network 22.

Further, in this embodiment, in addition to transmitting the prescription information of the patient to the host computer 4 of the host hospital, the prescription information of the patient is updated or newly registered in the prescription data file in the hospital. That is, regarding the prescription information of the patient who has been treated in his own hospital, the prescription data file 11
The same prescription information as 0 will be supplementarily held in the hospital. Thereby, the prescription information of the patient in the hospital can be immediately obtained without accessing the prescription data file 110 via the public network 22. Therefore, for a patient who is under medical treatment at his / her own hospital, the medication history of the patient can be obtained without accessing the prescription data file 110 of the host hospital. This can shorten the time required to obtain the medication history and also serve as a backup for writing errors in the prescription data file 110. The medication history is recorded for each patient, and one patient should not be seen at multiple hospitals at the same time. In addition, the prescription data file 110 and the in-house prescription data file are compared with the time interval at which the patient returns to the hospital. The time difference from the writing process is very small. Since the access to the prescription data file 110 in the host hospital does not go through the public network 22, no communication failure occurs. Therefore, the prescription information of the patient in the host hospital is recorded only in the prescription data file 110 as the drug history management database. deep. Of course, the prescription data file of the hospital may be provided separately from the prescription data file 110 for backup or the like.

FIG. 3 shows the data recording format of each patient recorded in the prescription data file owned by each hospital. The conventional patient data recording format consisting of the in-house patient number and prescription data is used as the unified patient number and will be described later. A password area is provided.

By the way, there are cases where a patient becomes ill at a destination or on a business trip and is examined at a hospital such as a destination. In the present embodiment, such a case can be dealt with. The host computer 4 in the present embodiment has a communication means for connecting to an external communication device, and is characterized in that it is possible to obtain the medication history of a patient from other than a hospital group via the communication means. The communication I / F 24 also serves as the communication means in this embodiment.

For example, the doctor of the hospital at the destination travels to ask the patient for the unified patient number, and the terminal device at the hospital uses the unified patient number to make an inquiry to the host hospital. As in the case where the host computer 4 of the host hospital transmits the drug history of the patient, the doctor of the hospital at the destination can refer to and utilize the drug history of the patient, as in the case where the host computer 4 in the hospital group transmits the drug history. Needless to say, it may be printed by a facsimile, which is a communication device, instead of the terminal device.

The present embodiment is also characterized in that a password can be set when the unified patient number is assigned. As described above, the medication history of a patient can be obtained from a group other than the hospital group by a request from the outside, but it is not preferable that anyone can freely refer to the information on the patient. Therefore, a password is set in the patient when the unified patient number is assigned, and the password is input together with the unified patient number from an external communication device. The communication device is a terminal device or the like having a communication function. If the medication history of the patient corresponding to the unified patient number is sent only when the entered password matches the password of the unified patient number, a third party cannot obtain the medication history of the patient without permission. , Even if you drop the ticket with the unified patient number, it will not be misused. In this case, the host computer 4 of the host hospital needs a password checking mechanism. This process of checking the password can be used not only from the outside but also within the hospital group. When the host computer 4 is accessed using the password, the history is recorded in the prescription data file 110.

As described above, according to the present embodiment, the unified patient number common to all hospitals in the hospital group is assigned to each new patient in all hospitals in the hospital group, so that other hospitals can use the same patient number. The patient's medication history can be easily obtained by using the unified patient number without knowing the assigned patient number.

Further, if the prescription data file of each hospital is referred to in order using the unified patient number, all the drug history of the patient can be obtained, but the prescription data file 110 is provided to unify the drug history of all patients. By managing it, it is possible to quickly and easily obtain the patient's entire medication history from any hospital.

As described above, the fact that the patient's medication history can be managed in an integrated manner enables not only the medication history information of the patient to be managed, but also the prescription information to be provided to other subsystems in medicine. For example, it is possible to easily grasp the medication status by doctor, drug effect, and hospital, and it can also be used for ordering and inventory management of drugs that are integrated by the hospital group.

Although the above embodiment has been described for the case of an outpatient, it goes without saying that it can be applied to an inpatient.

Further, if various databases can be accessed using the unified patient number, not only the medical history of each patient but also other information can be obtained from each hospital, so that the function can be expanded within the hospital group. be able to.

[0044]

According to the first aspect of the invention, the unified patient number common to all hospitals in the group is assigned to each new patient in all hospitals in the group. It can be used to easily refer to the patient's medication history.

According to the second aspect of the present invention, since the drug history of all patients is centrally managed in the drug history management database,
It is possible to easily refer to the entire medication history for the patient from any hospital, regardless of which hospital in the group the patient has been consulted with in the past.

According to the third aspect of the invention, by providing a patient number unique to each hospital in addition to the unified patient number, it is possible to achieve patient management at each hospital using the patient number unique to each hospital. Becomes Further, by using the unified patient number and the patient number together, it becomes possible to easily control hospitals that conventionally used only patient numbers unique to their own hospital within the hospital group.

According to the fourth aspect of the present invention, it is possible to refer to the medication history of the patient recorded in the medication history management database from other than the hospital in the group by providing communication means.

According to the invention of claim 5, a password is set for each unified patient number, and when referring to the medication history, the password is designated together with the unified patient number so that the password can be designated. Only the person who knows can refer to the medication history of the patient.

[Brief description of drawings]

FIG. 1 is a system configuration diagram showing an embodiment of a drug history management system according to the present invention.

FIG. 2 is a diagram showing a schematic configuration of a drug history management system in a hospital group in the present embodiment.

FIG. 3 is a diagram showing a format example of a prescription file for each patient stored in a prescription data file in the present embodiment.

FIG. 4 is a diagram showing a conventional drug history management system in each hospital.

FIG. 5 is a diagram showing a schematic configuration of a drug history management system in a hospital group.

[Explanation of symbols]

2 terminal device, 4 host computer, 6 medical database, 8 management file, 10 110 prescription data file, 12 drug master file, 14 general-purpose master file, 16 printer, 18 patient information text, 20 prescription information text, 22 public network, 24 Communication I / F.

Claims (5)

[Claims] 1. A drug history management system for managing a history of drugs administered to a patient for each patient, wherein a unified patient number common to all hospitals in the group is assigned to each new patient in all hospitals in the group, A drug history management system characterized in that it is possible to refer to the drug history of a patient treated in a hospital in a group by using a unified patient number from any hospital in the group. 2. The drug history management system according to claim 1, wherein a communication means within a group for network connection with a hospital within the group and a common patient number are assigned to each new patient at all hospitals within the group. It has a number numbering means and a drug history management database that records the drug history of all patients treated in the group hospital, and manages the drug history of patients treated in the group hospitals in a unified manner. Characteristic drug history management system. 3. The drug history management system according to claim 1, wherein the unified patient number is provided separately from the patient number unique to each hospital. 4. The drug history management system according to claim 1, further comprising: a drug history management database for recording drug history of all patients treated in hospitals in the group; and communication means for connecting to an external communication device. , And transmits the medication history of the patient corresponding to the unified patient number designated by the communication device. 5. The medicine history management system according to claim 1, wherein a password is set for each unified patient number, and the unified patient number is set only when the password specified together with the unified patient number matches the password of the unified patient number. A drug history management system characterized by transmitting the drug history of a corresponding patient.