JPH04205557A - Family control system - Google Patents

Abstract

PURPOSE:To accurately transmit a message to a patient and his/her family in a simple operation by producing automatically a family make-up file with automatic addition of the family record number and based on the information on the health insurance card of the patient and the proper information on the patient like the telephone number, etc. CONSTITUTION:The family record number is registered into a patient master file 3 in response to a unique patient number and at the same time the patient number is registered into a family make-up file 4 in response to the family record number. When a massage is registered to the patient, the message and its corresponding patient number are registered in a message file 5 in response to the message number. Then the message number is registered in a message number field of the corresponding family record number of the file 4. Thus the file 4 is automatically produced and at the same time a message can be accurately transmitted to the patient and his/her family in a simple operation.

Description

[Detailed Description of the Invention] [Summary] Regarding a family management system that transmits messages to a patient's family, a family record number is assigned based on patient information such as the patient's health insurance card information and telephone number. The purpose is to automatically create a family structure file using the system, and to enable messages to be conveyed accurately to patients and their families with simple operations.In addition to assigning a patient number and family record number to the patient and registering them, a message field is also added. A patient master file that has a patient master file, a family composition file that registers the patient numbers and message numbers of patients who make up the family in correspondence with the family record numbers of this patient master file, and a family composition file that registers the patient numbers and message numbers of patients who constitute the family in correspondence with the family record numbers of this patient master file, and a family composition file that corresponds to the message numbers in this family composition file. and a message file for registering a message and a patient number to transmit this message, and in response to input of patient-specific information, a family record number is registered in the patient master file in association with a unique patient number. Register the patient number in the record of the family structure file that corresponds to this family record number, and when registering a message to the patient, register the message and the patient number to which you want to transmit this message in the message file in association with the message number, and This message number is configured to be registered in the message number field of the corresponding family record number in the family composition file.

(Industrial Application Field) The present invention relates to a family management system that conveys messages to the patient's family.The main task of Nostem for medical administration is issuing receipts.Nowadays, issuing receipts is a matter of course. The system is also required to play a role as a medical support, and among these, the system is particularly desired for medical practitioners to improve patient services.

One of these patient services is family management. Specifically, we create a family structure file based on the patient who visits the hospital, and create a family management system that facilitates communication between doctors and patients through messages sent to patients. It is hoped that messages will be conveyed to patients and their families.

[Problems to be solved by the conventional technology and invention] In the conventional family management system dedicated to medical administration, a family number is prepared exclusively in order to create a family composition file, and an operator uses the Each child had a designated family number. In this method, the operator determines whether each patient is a family member or not, and if a family member of that patient has already visited the hospital and a family number has been issued, the family number that has already been assigned to this patient is retrieved from the ledger. It is necessary to search and register. In addition, messages to family members are registered based on the family number, so in order to register a message for a certain patient, search for the patient's family number, and then use the family number to register the message. I was registering using a special screen.

For this reason, the operator has to define the family number independently, which is cumbersome to operate, and it is also necessary to accurately convey the message not only to the patient but also to the family member who first visited the hospital.
There was a problem that the file structure became complicated.

The present invention automatically creates a family structure file by assigning a family record number based on patient-specific information such as the patient's health insurance card information and telephone number, and also accurately sends messages to patients with simple operations. The purpose is to make it possible to pass it on to their families.

[Means for solving the problem] Means for solving the problem will be explained with reference to FIG.

In FIG. 1, a patient master file 3 is a file in which a patient number and family record number are assigned and registered to a patient, and a message presence field is provided.

The family composition file 4 is a file in which patient numbers and message numbers of patients constituting a family are registered in association with family record numbers.

The message file 5 is a file in which a message and a patient number to which the message is transmitted are registered in association with the message number.

[Effect]

As shown in FIG. 1, the present invention registers a family record number in association with a unique patient number in a patient master file 3 in response to patient-specific information input, and also registers a family record number corresponding to this family record number. Register the patient numbers that make up the family in the records in the configuration file 4, and when registering a message to the patient, register the message and the patient number to which you want to transmit this message in correspondence with the message number in the message file 5. This message number is registered in the message number field of the corresponding family record number in file 4. Then, in response to the input of the patient number, the patient master file 3 is searched, and if a message is registered in the message presence/absence field of the corresponding patient, the message of the corresponding family record number in the family record configuration file 4 is searched. The number is searched and the message of this message number is displayed on the screen from the message file 5.

Therefore, a family record number is automatically created based on patient-specific information such as the patient's health insurance card information and telephone number, and a family structure file 4 is automatically created. It becomes possible to convey the information to family members.

〔Example〕

Next, the configuration and operation of the embodiment of the present invention will be explained in detail using FIGS. 1 to 10 [iJ].

In FIG. 1, a system 1 dedicated to medical affairs is a computer system exclusively used for medical affairs such as issuing receipts.

The family management system 2 is a system according to the present invention that provides messages to patients visiting the hospital (messages from doctors, notifications that test results have been received, forgotten items, etc.) as one of the patient services in the medical office dedicated system. This is a system to manage and notify messages (such as messages).

The patient master file 3 is a file in which the unique patient number given to the patient, the unique family record number automatically given to the patient's family, the presence or absence of messages, etc. are registered (see FIG. 2).

The family structure file 4 is a file that registers the patient numbers of all patients who make up the family in association with the family record number uniquely and automatically assigned to the patient's family, and the message numbers of the messages registered in the message file 5. Yes (see Figure 3).

The message file 5 is a file in which a message and a patient number to which the message is transmitted are registered in association with the message number (see FIG. 4).

FIG. 2 shows an example of the structure of the patient master file of the present invention. Here, information as shown in the figure is registered as a code for each patient. Each item will be explained below.

, Patient number: Patient identifier, unique code number.

Attribute information: Patient's name, date of birth, family classification, medical record number, etc. Insurance information: Insurer number, symbol/number, insurance burden rate, insurance expiration date, etc. Medical record header information: Occupation, relationship, address, Family record number, such as postal code, telephone number, recommendation, etc.: Relative address of family structure file 4. Message presence/absence classification: Whether or not there is a message for the family. Figure 3 shows the structure of the family structure file of the present invention. Give an example.

Here, information as shown is registered as a code for each family record number. Each item will be explained below.

Patient number: This is the patient number of each patient who makes up the family. For example, up to 10 patients can be registered.

Message number: Set the relative address of message file 5,
For example, you can receive up to 10 cents per family.

FIG. 4 shows an example of the structure of a message file according to the present invention, in which information as shown is registered as a code for each message. Each item will be explained below.

Message (Japanese): A message in Japanese.

Patient number of the patient to whom the message is to be sent: This is the patient number of the patient to whom the message is to be sent.

Next, in accordance with the order shown in the flowchart of FIG. 5, the operation at the time of new registration will be explained in detail using the eighth consenting person registration screen.

In FIG. 5, ■ displays the patient registration screen. This displays the patient registration screen shown in FIGS. 8(a) and 8(b) when a new patient comes for outpatient bone grafting.

■Enter from the screen. For example, from the patient registration screen in Figure 8 (a) and Figure 8 (b) displayed with
110.810532 Phone number: Enter 0044-777-1111, etc. Since the patient registration screen shown in FIG. 8(a) is not enough, press the right scroll key to display the patient registration screen shown in FIG. 8(b) as necessary for input.

■ is saved in the patient master file. This is done by associating the information entered from the patient registration screen in Figure 8 (a) and Figure 8 (b) with the sequentially uniquely assigned patient number in ■, and registering it in the second consenting person master file 3. .

[Phase] creates a family composition file. Creating this family structure file is required for newly registered patients.
If the newly registered patient's insurance number and symbol/number are found to be the same with YES, or if the phone number of the newly registered patient is found to be the same with YES, it is determined that the patient is a family member, and the new patient is identified with ■. Register the family record number of the patient's family that was already registered in the patient number record of the patient to be registered. On the other hand, in the case of ■No, 9No, it has been determined that the newly registered patient is not a family member of the already registered patient, so a unique family record number is associated with the patient's patient number in [phase]. register.

Further, the patient number is registered in the family number field of the family structure file 4 corresponding to this family record number.

Through the above process, if a patient to be newly registered has already been registered in the past with the same symbol/number as the insurer number, or a patient with the same phone number, the new patient is determined to be the patient's family. Therefore, the family record number is registered in the patient master file 3, and the patient number is also registered in the record of the family composition file 4 of this family record number.On the other hand, if the new patient has no family registered, a unique A new family record number is registered in the patient master file 3, and the patient number is also registered in the record of the family composition file 4 of this family record number.

Next, message registration will be described in detail in accordance with the order shown in the flowchart of FIG. 6 and with reference to FIG.

In FIG. 6, ■ indicates a repeat visit.

O inputs the patient number. Enter the patient number written on the patient's medical card.

[Phase] displays the outpatient accounting screen. This displays the outpatient accounting screen shown in FIG. 9 in response to the input of the patient number (2).

In [Phase], input the consultation fee, medication, etc. This is the 9th
Enter the "internal medicine re-examination fee" etc. from the outpatient accounting screen as shown in the figure.

[Phase] The operator determines whether there is a message or not and selects YES.
Enter S or NO. If YES, there is a message, so perform [phase] or [phase]. If No, there was no message, so the process ends.

For [phase], press the PF main key.

■Display the family management screen! This is, for example, the 10th
Display the family management screen.

[Phase] is PF primary key 1 which instructs PF primary key message registration.
) to change to the mode where you can register messages.

[Phase] registers a message for the corresponding patient. For example, as shown in ■ on the family management screen in Figure 10, "I forgot my umbrella when I came to the hospital yesterday," or as shown in ■, "The results of the test from the other day have arrived." input.

[Stock] saves the message. This storage involves (1) saving the message in the message file 5 and registering the patient number to which the message is to be conveyed; (2) Register the message number (relative address) of the message file in the message number field of the record of the applicable family record number in the family composition file 4.

Through the above process, both sides of the family management page where the patient number has been entered are displayed, and when the operator, doctor, laboratory technician, etc. enters the message in the column of the corresponding patient among the family members to whom the message is to be transmitted, the message file is automatically created. 5, register the patient number, register the message number in the record of the corresponding family record number in the family structure file 4, and further register whether there is a message for the corresponding patient number in the patient master file 3.

Next, in accordance with the order shown in the flowchart of FIG.
Message transmission will be explained in detail with reference to the figures.

In Fig. 7, ■ indicates a repeat visit.

0: Enter the patient number. Enter the patient number written on the patient's medical card.

■ determines whether there is a message for the patient or family.

This is done by searching the first consenting person master file 3 based on the patient number input in step (3) and determining whether "Yes" is registered in the message presence/absence field for the corresponding patient number.

If YES, perform [stock] or @. If NO, the process ends.

[Stocks] automatically displays the family management screen. This searches the family structure file 4 based on the family record number of the patient number and displays information on all the patients making up the family, as shown in FIG. 10, for example.

(2) is used to send a message to i= or input a message. This can be done, for example, by displaying the family management screen in Figure 1O, and at the outpatient counter, the operator looks at the messages displayed in the message fields (■, ■ in Figure 10) of the patients who make up the family, and inputs the contents. acknowledge the patient or their family, or enter a message as necessary.

[Phase] indicates whether the message is to be deleted (PF that instructs to delete the message)
(whether or not the primary key has been pressed). If YES, delete the message and proceed to ■. If NO, ■
Proceed to.

■Displays the outpatient accounting screen.

[Stocks] inputs medical fees, medication, etc.

[Phase] ends the patient input, etc. These ■ to @ display, for example, the outpatient accounting screen shown in FIG. 9, and the patient enters all consultation fees, medication, etc. on this screen in sequence.

As a result of the above processing, in response to inputting the patient number when receiving a return visit, when the patient master file 3 is searched and a message from the patient or the patient's family is registered,
By extracting the corresponding message from the message file 5 and displaying it on the screen (for example, as shown in FIG. 10), the patient and his/her family can be informed of the patient's message by displaying it on the screen with a simple operation. It becomes possible.

FIG. 8 shows an example of the patient registration screen of this embodiment.

In FIGS. 8(a) and 8(b), the patient registration west side cannot be displayed on one screen, so two screens are displayed, which can be switched arbitrarily by pressing the right scroll key.

In response to the operator inputting the patient's name using ■ on this patient registration screen, entering the insurer number, symbol/number using ■, and entering a telephone number using ■, the flowchart shown in Fig. 5 described above is executed. Accordingly, register in the patient master file 3 and also register a unique family record number, or if a family member has already been registered, register the family record number of the family member, or register the patient's family member in association with this family record number. A patient number is registered and a family composition file 4 is automatically created.

FIG. 9 shows an example of an outpatient checkout screen according to the present invention. This is a screen that is displayed in response to inputting the patient number printed on the patient's ticket at the time of a return visit. This screen is a screen for inputting and accounting for consultation fees, medication fees, etc. When this screen is displayed, the PF main key with message is pressed to display the family management screen shown in FIG. 10.

FIG. 10 shows an example of a family management screen according to the present invention.

This screen appears in response to manually inputting a certain patient number.
This is a screen that displays the information of a patient whose family record number is equal to this one-color patient number as shown in the diagram, and is used to display the patient's name, message, etc., and to input and register a message. .

〔Effect of the invention〕

As explained above, according to the present invention, a family record number is automatically assigned based on patient-specific information such as the patient's health insurance card information and telephone number, and the family structure file 4 is automatically created. This makes it possible to accurately convey messages to patients and their families with simple operations.

As a result, (1) regardless of the time of introduction of the family management system, the family structure file 4 can be automatically constructed from the information in the patient master file 3 without any burden on the operator;

(2) Messages can be registered and messages sent to a certain patient can be smoothly transmitted to the patient's family.

(3) In addition, when you want to issue one ticket per family when notifying patients of periodic checkups or other DM (direct mail) notifications, you can easily do so using this automatically constructed family management file 4. be able to.

[Brief explanation of the drawing]

FIG. 1 is a configuration diagram of one embodiment of the present invention. FIG. 2 is a structural example of a patient master file of the present invention. FIG. 3 is a structural example of a family composition file of the present invention. FIG. 4 is a structural example of a message file of the present invention. FIG. 5 is a new registration flowchart of the present invention. FIG. 6 is a message registration flowchart of the present invention.
8 is an example of a fool registration screen according to the invention. FIG. 9 is an example of an outpatient accounting screen according to the invention. FIG. 10 is an example of a family management screen according to the invention. In the diagram, 1: Medical office dedicated system 2: Family management system 3: Patient master file 4: Family composition file 5: Message file

Claims (2)

[Claims] (1) In a family management system that transmits messages to the patient's family, a patient master file (3) in which the patient is registered with a patient number and family record number and a message field is provided, and this patient master file ( A family structure file (4) in which the patient numbers and message numbers of patients constituting the family are registered in association with the family record numbers in 3), and messages and messages in association with the message numbers in this family structure file (4). Message file (5
), In response to patient-specific information input, a family record number is registered in the patient master file (3) in association with a unique patient number, and the family composition file ( Register the patient number in the record in step 4), and when registering a message to the patient, register the message and the patient number to which you want to transmit this message in association with the message number in the message file (5) above, and register the patient number to which you want to transmit this message in the family structure file (4) above. A family management system characterized in that a message number is registered in a message number field of a corresponding family record number. (2) In response to the input of the patient number, if the above patient master file (3) is searched and "Message present" is registered in the message presence/absence field for the corresponding patient, the corresponding family record configuration file (4) will be searched. 2. The family management system according to claim 1, wherein the family management system is configured to search for a message number corresponding to a family record number and display the message of this message number from the message file (5) on the screen.