JP2003076779A - Management system for acceptance of patient - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve the problem wherein it is impossible to re-display so frequent ly because of requiring of time to acquire information on an acceptance of a patient. SOLUTION: In a management system for acceptance of patient, at least the facts whether the patient is in waiting for medical care, in inviting to a consulting room, in getting medical care or in waiting for accounting are registered as an acceptance state of the patient to a patient management database, if the acceptance state is shifted, management information updated according to the shift of the acceptance state is further stored into a shared memory area. An application program representing registered contents of the management database maintains a copy of the management information stored into the shared memory and compares the management information with the copy owned itself, and reads out the registered contents in the management database to display only when the management information is not matched to the copy.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a patient reception management system for managing the state of a patient who is in the process of receiving an incoming patient at a medical institution, waiting for medical treatment, medical treatment, waiting for accounting after medical treatment, and ending accounting. Regarding

[0002]

2. Description of the Related Art In medical institutions such as hospitals and clinics, the general flow of outpatients in the outpatient department is as follows. First, the patient who came to the hospital is accepted and added to the queue. At that time, if the patient who came to the hospital is a new patient, so-called new patient registration is performed to register basic patient information such as insurance code number and name, and then added to the queue. On the other hand, if the patient is a returning patient, the patient is searched by the patient number or the like written on the consultation ticket and added to the queue. The patient who has been accepted waits for a call in the waiting room. When the order of medical treatment comes around, they are called and enter the medical office to receive medical treatment. After the medical treatment is completed, the patient is kept waiting in front of the accounting window until the medical treatment cost is calculated. Also, if you have prescription drugs,
Wait for the medicine to be delivered at the pharmacy window. On the other hand, the accounting window calculates medical fees and out-of-pocket costs based on medical treatment. Finally, the patient returns home after receiving the call from the accounting window and completing the accounting.

[0003] There is a patient reception management system for managing the progress of patient reception, medical treatment, and accounting. In such a system, when a patient is accepted by the terminal device at the reception desk, information on the patient is registered in a database that manages the reception patient. At the time of reception, the patient's management status is waiting for medical treatment. Then, the management state is changed every time the medical treatment is started, ended, and the accounting is completed. 9 and 10 are display examples of a patient reception status screen for patient management. Patients are displayed in the order of the reception numbers, and the reception statuses are waiting for medical treatment, under medical treatment, waiting for accounting, and patients who have completed accounting are displayed as returning home. This patient reception status screen can be displayed not only on the reception terminal but also on the terminal in the clinic.

Therefore, in the medical office, the next patient waiting for the medical care is put in the medical office when the medical examination table is vacant.
As shown in 0, the patient is designated on this screen of the medical office terminal 31. Then, as shown in FIG. 9, the reception status of the patient is changed to "call" and displayed. Therefore, the reception window calls the patient at the reception window by seeing the change in the display.
Then, at the reception desk, when the patient is confirmed, the reception state of the patient is changed to under medical treatment. In this way, while sharing the patient reception status screen between the clinic and the reception desk,
Patients are managed by mutually changing the acceptance status.

[0005]

[Problems to be Solved by the Invention] Reducing the waiting time between the time a patient receives a medical treatment and the time when he / she receives a medical examination and the time waiting for accounting after medical treatment are directly linked to the improvement of patient service. It's about to get lost.
Therefore, when a patient waiting for medical treatment is called by an instruction from the clinic, it must be immediately reflected on the patient reception status screen. Therefore, it is required for the terminal device to frequently update the patient reception status screen to keep the latest contents. However, when the number of patients to be accepted increases, it takes time to obtain the patient acceptance data, which may affect the processing of programs other than the accounting processing and patient registration. Therefore, conventionally, the patient reception data is acquired and the screen is updated with a certain period of time such as every 30 seconds or every 1 minute, so that there is a tendency that the patient's calling is delayed. Moreover, the redrawing of this screen is
It was implemented with or without changes in content.

[0006]

According to the present invention, in a patient reception management system for receiving a patient who has come to a hospital and registering the information in a patient management database for management, at least the patient is in a waiting state or a medical examination as a reception state of the patient. Whether a call to the room, medical treatment, or waiting for accounting is registered in the patient management database, and management information that is updated accordingly when the reception status of this patient is changed is further stored in the shared memory area. However, the application program for displaying the registered contents of the patient management database holds a copy of the management information of the shared memory area, compares the management information of the shared memory area with the copy held by itself, and The above problem is solved by reading and displaying the registered contents of the patient management database only when they do not match. A.

[0007]

FIG. 1 is a block configuration diagram of a patient reception management system according to an embodiment, in which a central control unit 10 which holds a database and a processing program uses a patient's name and date of birth who have a record of visiting a hospital, and insurance to be used. Patient database 12 that stores unique information such as symbols and numbers, and a patient search program 11 that searches for a patient from the patient database 12 according to an instruction from a terminal
And an accounting program 18 that calculates patient medical expenses and out-of-pocket expenses and performs accounting processing of receipt amount and unpaid money, an accounting database 19 that stores the accounting information, and a medical treatment database of medical treatments received by patients. A medical record program 16 registered in 17, a patient management program 13 that manages the reception status of patients from the reception of a patient who has visited the hospital to the end of accounting, and a patient management database 20 that stores the reception status. Further, a management flag 15 is provided whose value is updated by the patient management program 13 each time the patient acceptance status changes. This management flag 15
Are stored in a shared memory area that can be referenced by any program. A reception terminal 30 installed in a reception window and an office terminal 31 installed in the medical office, in which application programs for terminals operate, are connected to each other. Although only two terminal devices are provided here, a plurality of clinic terminals 31 may be installed as many as the clinics, or a plurality of reception terminals 30 may be similarly installed. Further, the reception terminal 30 is provided in the central controller 10.
It is also possible to incorporate the function of and use it as a dual function.

The record structure of the patient management database 20 that stores the acceptance status of the patients who have come to the hospital will be described with reference to FIG. One record is stored for each accepted patient, and the patient ID 21 such as the patient number, which is the identification information of the patient, the visit date 22, and the visit number when there are multiple visits within the visit date 23, a state flag 24 indicating a reception state of the patient, a reception time 25, and a time 26 when the medical treatment is finished are stored. Of these, the status flag 24
The value of indicates the current reception status of the patient, starting from "waiting for medical treatment" immediately after the reception, "calling" indicating that the medical treatment order has come, "indicating that the patient is in the medical office" It is sequentially changed by the patient management program 13 to “under medical treatment”, “waiting for accounting” after finishing medical treatment and clearing the medical treatment cost, and “returning home” after finishing accounting processing.

Further, the management flag 15 in the shared memory
Indicates that the initial value at the time of system startup is 1, and thereafter, the value is incremented by 1 each time the patient management program 13 changes the contents of the patient management database 20. Then, the application program of the terminal also holds a copy of this management flag 15. However, the initial value at startup is zero on the terminal side, and the central controller 10
If they do not match with each other, the value of the management flag 15 and the content of the patient management database 20 are acquired from the central control unit 10 by the application program of the terminal.

Next, the operation of the embodiment system will be described with reference to the flowcharts of FIGS. First, when a patient comes to the hospital, the application program of the reception terminal 30 executes patient search and registration. In response to this, the patient search program 11 searches for a patient (step S3
1) Next, the patient management program 13 sets the reception time, sets the status flag 24 to "waiting for medical treatment" (S32), and additionally registers the patient data in the patient management database 20 (S33). ). And management flag 1
5 is incremented (S34). This process is repeated each time a patient comes to the counter, and patients are registered one after another.

The application programs of the terminals 30 and 31 follow the flow of FIG.
The data of the visiting patients registered in
The patient acceptance status screen 80 as shown in is displayed. At that time, the value of the management flag 15 is compared with the value of the copy held by itself (S81), and only when they are different, the information of the patient management database 20 is updated to the patient management program 1
3 is acquired (S83), and the patient reception status screen 80 is updated (S84). And management flag 1
5 is copied (S85).

On the other hand, if the values of the flags 15 match,
Assuming that there is no change from the previous display contents, patient management data is not acquired and the screen is not updated. In the embodiment system, while the terminal devices 30 and 31 are displaying the patient acceptance status screen 80, the management flags 15 are compared every one second. As a result, the value of the management flag 15 is changed, that is, the content of the patient management database 20 is updated by 1
The detection can be made within a second, and the patient reception status screen 80 can always be kept up to date. However, since this work is only the comparison of flags, it does not take time and load on an external application program.

When the doctor terminal 31 is ready to accept the next patient, the operator designates the patient 85 waiting to be treated by the mouse cursor 86 on the patient acceptance status screen 80 shown in FIG. Press 83. In response to this, the patient management program 13 updates the status flag 24 of the patient to “call” according to the flow shown in FIG. 4 (S41), and increments the management flag 15 (S42).

Since the change in the value of the management flag 15 is immediately detected by the application program of the reception terminal 30 as described above, the patient reception status screen 80 of the reception terminal 30 becomes as shown in FIG. That is, the previous patient 85
The acceptance status of is displayed as "call". Moreover, in the embodiment, since the highlight display is performed, it is easy for the operator to visually recognize it, and thus the patient whose turn comes can be called immediately.

Then, when the operator of the reception terminal 30 calls the patient and guides him / her to the clinic, he / she is in the mid-care button 89.
Press. In response to this, the patient management database 20
Status flag 24 is updated to "under medical treatment" (S51),
The management flag 15 is incremented (S52). As a result, the display of the patient reception status screen 80 of the terminal devices 30 and 31 is updated by the processing of FIG. 8, and the reception status of the patient becomes “under medical treatment”.

Next, when the medical care data is input at the medical office terminal 31 and registered in the medical care database 17 by the medical record program 16 (S61), in response thereto,
The patient management program 13 sets the medical care end time of the patient on the patient management database 20, and updates the status flag 24 to "waiting for payment" (S62). Then, the management flag 15 is incremented (S63). As a result, the display of the patient acceptance status screen 80 of the terminal devices 30 and 31 is updated by the processing of FIG. 8, and the patient acceptance status is changed to “account waiting”.

Finally, when the patient who is "waiting for accounting" is accounted for at the reception terminal 30, the accounting program 18 calculates medical expenses and co-payments, and the accounting data is registered in the accounting database 19 (S71). In response to this, the patient management program 13 updates the status flag 24 of the patient to "go home" (S72), and the management flag 15
Is incremented (S73). As a result, the display of the patient reception status screen 80 of the terminal devices 30 and 31 is updated by the process of FIG. 8, and the reception status of the patient is changed to the display of "going home".

[0018]

According to the present invention, by providing the management flag indicating the change in the patient reception status in the shared memory area,
The application program can now refer to it and easily detect that the patient reception status has changed. This makes it possible to detect changes in the patient reception status in a short cycle, and since it is only necessary to acquire the patient reception data when there is a change, the patient reception status can be received without affecting external application programs. The screen that displays the status can always be kept up to date.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of an example system.

FIG. 2 is a diagram showing a record configuration of a patient management database in the example.

FIG. 3 is a flowchart showing the operation of the embodiment.

FIG. 4 is a flowchart showing the operation of the embodiment.

FIG. 5 is a flowchart showing the operation of the embodiment.

FIG. 6 is a flowchart showing the operation of the embodiment.

FIG. 7 is a flowchart showing the operation of the embodiment.

FIG. 8 is a flowchart showing the operation of the embodiment.

FIG. 9 is a screen display example showing a patient reception state.

FIG. 10 is a screen display example showing a patient reception state.

[Explanation of symbols]

10 Central controller 11 Patient search program
12 patient database 13 patient management program 15 management flag 16 medical record program
17 Medical database 18 Accounting program
19 Accounting database 20 Patient management database 30 Reception terminal 31 Clinic terminal

Claims (6)

[Claims] 1. A patient reception management system that receives a patient who has come to the hospital and registers the information in a patient management database to manage the information. In the patient reception status, at least the patient is waiting for medical treatment, is being called to a medical office, or medical treatment. Register in the patient management database, whether it is middle or waiting for accounting,
When the reception status of the patient is changed, the management information updated accordingly is further stored in the shared memory area, and the application program for displaying the registered contents of the patient management database copies the management information of the shared memory area. Patient reception management characterized by holding and comparing the management information of the shared memory area with the copy held by itself, and reading and displaying the registered contents of the patient management database only when they do not match. system. 2. The patient according to claim 1, wherein the application program displaying the registered contents of the patient management database periodically compares the management information of the shared memory area with a copy held by itself. Reception management system. 3. The application program for displaying the registered contents of the patient management database copies the management information of the shared memory area when the comparison result of the management information of the shared memory area and the copy held by itself does not match. The patient acceptance management system according to claim 1 or 2, wherein the patient acceptance management system is retained by being retained. 4. A patient management database means for storing reception information of an outpatient, and at least a patient waiting for medical treatment, calling to a medical office, under medical treatment, or waiting for accounting by a computer. Register the reception status as reception information in the patient management database means,
A patient management unit that stores management information that is updated each time the reception status of a patient is changed in a shared memory area, a copy of the management information in the shared memory area, and the management information in the shared memory area and itself. A program for functioning as reception information display means for comparing stored copies and reading and displaying the registered contents of the patient management database only when they do not match. 5. The program according to claim 4, wherein the reception information display means functions to periodically compare the management information in the shared memory area with a copy held by itself. 6. The management information of the shared memory area according to claim 4 or 5, when the comparison information of the management information of the shared memory area and the copy held by the reception information display means do not match each other. A program to make the function of copying and holding.