JP2003331215A - Drugstore data processing device, drugstore data management device and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce a load for character recognition of a prescription of each medical institution. <P>SOLUTION: Medicine-preparing drugstore terminals 2A, 2B used as drugstore data processing devices and a medicine-preparing drugstore server 1 used as a drugstore data management device are connected each other through a communication network 4, and OCR definition information which is information for performing character recognition of read prescription data and prescription recognition information corresponding to a medical institution name, respectively, is stored. When acquiring the medical institution name by character recognition and storing the OCR definition information corresponding to the medical institution name in the own terminal, the medicine-preparing drugstore terminals 2A, 2B performs character recognition of the prescription data by using the stored OCR definition information. When the object OCR definition information is not stored in the own terminal, the terminals 2A, 2B download the OCR definition information of the medical institution name acquired from the medicine-preparing drugstore server 1 and use it for character recognition of the prescription data. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a pharmacy data processing device for processing pharmacy data, a pharmacy data management device for managing pharmacy data, and a program thereof.

[0002]

2. Description of the Related Art Conventionally, in hospitals and their dispensing pharmacies, patients bring prescriptions issued by the hospitals to the dispensing pharmacies and dispense the medicines according to the prescriptions brought by the staff. Therefore, there has been a demand for computerization of the dispensing method.

[0003]

As a computerized dispensing system, a prescription is an OCR (Optical Characte).
r Reader: An optical character recognition device) can be used to acquire information on dispensing. In this case, in order to recognize the OCR characters on the prescription, the OCR reads the original prescription for each prescription issued by each hospital, and the position and size on the paper, the surname, etc. are unique for each input item such as the patient name. It is necessary to define attributes such as noun attributes and related master files one by one.

However, the prescription format differs from hospital to hospital, and in the case of the form definition method, it is not realistic for the SE (system engineer) to define the formats of all hospitals to be handled at the time of introduction, which is a huge amount of work. .

Further, it is almost impossible for the staff of the dispensing pharmacy (clerk or pharmacist) to carry out the above-mentioned work because of the lack of OCR expertise and computer. Furthermore, the above work is required even after the system is introduced, such as defining the format of a new hospital.

An object of the present invention is to reduce the burden of character recognition of a prescription for each medical institution.

[0007]

In order to solve the above-mentioned problems, the invention according to claim 1 is a pharmacy data processing device for creating and storing a dispensing history from a prescription corresponding to each of a plurality of medical institutions. The prescription recognition information includes position information of the item area in the prescription and data type of data in the item area, and is information for character recognition of the prescription data using the position information and the data type. , A medical institution name corresponding to each medical institution, the prescription recognition information corresponding to each medical institution name, and a processing-side storage unit that stores a patient's dispensing history, and a prescription for a patient issued from the medical institution. Reading means for reading as prescription data, character recognizing means for recognizing characters of the prescription data read by the reading means, and character recognition for the character recognizing means. Specifying means for specifying the medical institution name from the prescription data, and the processing-side storage means for reading the prescription recognition information corresponding to the medical institution name specified by the specifying means, and based on the read prescription recognition information, Dispensing history creating means for creating a dispensing history from the prescription data recognized by the character recognizing means and storing the dispensing history in the processing side storage means is provided.

According to the first aspect of the invention, the pharmacy data processing device character-recognizes the prescription data, retrieves the prescription recognition information corresponding to the recognized medical institution name from the processing side storage means, and retrieves it. Character recognition is performed using the prescribed prescription recognition information, and the dispensing history is created and stored. Therefore, the character recognition of the prescription can be automated and swiftly and reliably performed, and the burden of character recognition can be reduced.

For example, it further comprises a processing side communication means for communicating with the medical institution name and a pharmacy data management device for managing prescription recognition information corresponding to the medical institution name via a communication network, and the processing side storage means. In the case where the prescription recognition information corresponding to the medical institution name specified by the specifying means is not stored, the processing side communication means,
The acquisition request of the prescription recognition information corresponding to the medical institution name specified by the specifying means is transmitted to the pharmacy data management device, the prescription recognition information is newly received from the pharmacy data management device, and the dispensing history creation means is , Creating a dispensing history from the prescription data character-recognized by the character recognizing means based on the new prescription recognition information received by the processing-side communication means, and storing the dispensing history in the processing-side storage means May be configured as.

Further, for example, the processing side storage means may be configured to store the prescription recognition information newly received by the processing side communication means.

Further, for example, it further comprises registration information setting means for setting registration information for registering the self-pharmacy data processing device in the pharmacy data management device, wherein the processing side communication means is the registration information setting means. The set registration information may be transmitted to the pharmacy data management device for registration.

Further, for example, the prescription recognition information received by the processing side communication means includes identification information for identifying the pharmacy data processing device, and the identification information included in the received prescription recognition information is the self-pharmacy. In the case of indicating a data processing device, the dispensing history creating means stores the prescription recognition information corresponding to the medical institution name specified by the specifying means from the processing side storage means in which the received prescription recognition information is stored. On the basis of the prescription recognition information received by the processing-side communication means, the dispensing history is created from the prescription data character-recognized by the character recognizing means, and the dispensing history is stored in the processing-side storage means. You may comprise.

Further, for example, it further comprises a recognition information setting means for setting the prescription recognition information, and the processing side communication means transmits the prescription recognition information set by the recognition information setting means to the pharmacy data management device. The data may be stored in the pharmacy data management device.

Further, for example, when the prescription recognition information stored in the pharmacy data management device is changed, the processing side communication means receives the changed prescription recognition information from the pharmacy data management device, The processing-side storage means may be configured to store the changed prescription recognition information received by the processing-side communication means.

Further, for example, the processing side communication means receives from the pharmacy data management device change information indicating that the prescription recognition information stored in the pharmacy data management device has been changed, and the processing side communication means. In the case where the change information is received in, the system further comprises a transmission request input unit for inputting a transmission request for the changed prescription recognition information, and when the transmission request is input in the transmission request input unit, the processing side The communication means transmits a transmission request for the changed prescription recognition information to the pharmacy data management device, receives the changed prescription recognition information from the pharmacy data management device, and the processing-side storage means The modified prescription recognition information received by the processing-side communication means may be stored.

According to a ninth aspect of the present invention, there is provided a pharmacy data management device for managing prescription recognition information of a prescription corresponding to each of a plurality of medical institutions, wherein the prescription recognition information is an item area in the prescription. Position information, including the data type of the data in the item area, is information for character recognition of prescription data using the position information and data type, the medical institution name corresponding to each medical institution,
And a management-side storage unit that stores prescription recognition information corresponding to each medical institution name, and a management-side communication unit that connects via a communication network to a pharmacy data processing device that creates and stores a dispensing history from the prescription, In the management-side communication means, when a transmission request for prescription recognition information corresponding to the medical institution name is received from the pharmacy data processing device, prescription recognition information corresponding to the acquisition request is received from the management-side storage means. The management-side communication unit transmits the prescription recognition information searched by the search unit to the pharmacy data processing device that is the transmission request source.

According to the invention of claim 9, even when the pharmacy data processing device does not store the prescription recognition information used for character recognition, the pharmacy data management device stores the prescription recognition information stored in the device itself. Since it can be provided to the pharmacy data processing device, the pharmacy data processing device can easily perform character recognition using the received prescription recognition information even for a prescription of a medical institution that is rarely handled.

For example, the management side storage means stores registration information of the pharmacy data processing device, and when the registration information of the pharmacy data processing device which is the transmission request source is stored, the management side communication means. May transmit the prescription recognition information retrieved by the retrieval means to the pharmacy data processing device that is the transmission request source.

Further, for example, the management side storage means further stores identification information for identifying the pharmacy data processing device, and the prescription recognition information retrieved by the retrieval means is added to the pharmacy data processing device of the transmission request source. Further, the management side communication means transmits the prescription recognition information to which the identification information is added by the addition means to the pharmacy data processing device of the transmission request source. It may be configured to do so.

Further, for example, the management side storage means stores charging information relating to use of the prescription recognition information for each of the pharmacy data processing devices, and the management side communication means requests the transmission of the prescription recognition information. When the information is transmitted to the original pharmacy data processing device, it may be configured to further include a billing update unit that updates the billing information stored in the management side storage unit corresponding to the pharmacy data processing device.

Further, for example, it is assumed that the management side communication means receives prescription recognition information from the pharmacy data processing device, and the management side storage means stores the prescription recognition information received by the management side communication means. You may comprise.

Further, for example, the management side storage means stores, in correspondence with the prescription recognition information transmitted from the pharmacy data processing device, reward amount information given to each pharmacy data processing device of the information transmission source. When the prescription recognition information is received from the pharmacy data processing device in the management side communication means, the remuneration amount information stored in the management side storage means is updated corresponding to the pharmacy data processing device of the information transmission source. It may be configured to further include a reward amount updating means.

Further, for example, it further comprises recognition information changing means for changing the prescription recognition information stored in the management side storage means, and when the prescription recognition information is changed by the recognition information changing means, the management side communication is performed. The means may be configured to transmit the changed prescription recognition information to the pharmacy data processing device for storage.

Further, for example, it further comprises recognition information changing means for changing the prescription recognition information stored in the management side storage means, and when the prescription recognition information is changed by the recognition information changing means, the management side communication is performed. The means transmits change information indicating that the prescription recognition information has been changed to the pharmacy data processing device, and when the transmission request of the information is received from the pharmacy data processing device of the information transmission destination, the changed prescription The recognition information may be transmitted to and stored in the pharmacy data processing device that is the transmission request source.

[0025]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described below with reference to the accompanying drawings.

This embodiment will be described with reference to FIGS. First, the features of the apparatus will be described with reference to FIGS. FIG. 1 is a diagram showing a configuration of a pharmacy system α of the present embodiment, FIG. 2 is a block diagram showing an internal configuration of the dispensing pharmacy server 1 in FIG. 1, and FIG. It is a block diagram which shows the internal structure of dispensing pharmacy terminal 2A, 2B.

As shown in FIG. 1, the pharmacy system α of the present embodiment is a dispensing pharmacy server 1 that manages data used for dispensing, and a dispensing pharmacy terminal 2A that belongs to each dispensing pharmacy and processes prescription data. 2B, a bank management server 3 that manages account data of all banks, a dispensing pharmacy server 1, dispensing pharmacy terminals 2A and 2B, and a communication network 4 that communicatively connects the bank management server 3.

There are at least one hospital and one dispensing pharmacy, and the numbers of dispensing pharmacy terminals 2A and 2B are representatively shown in FIG. 1 and may be other numbers. Further, it may be configured such that a plurality of dispensing pharmacy servers 1 are provided. For example, there is a plurality of hospitals, and the dispensing pharmacy server 1 is provided for each hospital.

The communication network 4 is the Internet in the present embodiment, but the present invention is not limited to this. For example, a LAN (Local Area Network), WAN (Wide Are).
a Network), telephone line network, ISDN line network, wide band communication line network, leased line, mobile communication network, communication satellite line, CATV line, optical communication line, wireless communication line, and connecting them. It may be configured to include an Internet service provider that operates.

Dispensing pharmacy server 1 and dispensing pharmacy terminal 2
Each of A and 2B is represented by one information processing device in the present embodiment, but for example, a plurality of devices are installed via the communication network 4 and various functions are distributed among the devices. It may be configured to be executed by executing. In this case, loads for executing various functions are distributed.

Next, referring to FIG. 2, the dispensing pharmacy server 1
The internal configuration of will be described. As shown in FIG. 2, the dispensing pharmacy server 1 has a CPU inside which centrally controls each unit.
(Central Processing Unit) 1a, input unit 1b via administrator's input, and RAM for temporarily storing information
(Random Access Memory) 1c, display unit 1d for displaying information to the administrator, storage device 1d for storing information, communication control unit 1f for controlling communication with devices on communication network 4, and current date and time CP that outputs 1g
Bus 1 connecting U1a, input unit 1b, display unit 1d, RAM 1c, storage device 1e, communication control unit 1f, and clock unit 1g
and h.

The CPU 1a of the dispensing pharmacy server 1 executes definition information transmission / reception processing and change notification processing. CPU1a
When the information received from the dispensing pharmacy terminal is an OCR definition information request due to execution of the definition information transmission / reception process (transaction category = 0), the definition information file F5 stored in the storage device 1e is the definition information file to be requested. To the bank management server 3 to send the searched OCR definition information to the dispensing pharmacy terminal and withdraw the usage charge of the transmitted OCR definition information from the destination dispensing pharmacy account. Send.

When the information received from the dispensing pharmacy terminal is an OCR definition information provision request (transaction category = 1), the CPU 1a stores the OCR definition information in the OCR definition information provision request in the storage device 1e. Definition information file F
5, the information indicating that the compensation fee of the received OCR definition information is to be transferred to the account of the dispensation pharmacy that is the transmission source is transmitted to the bank management server 3 (see FIG. 16).

Further, the CPU 1a refers to the record of the transaction transaction file F1 stored in the storage device 1e by executing the change notification process, and the dispensing pharmacy server 1
Side obtains a record in which the changed hospital code of the hospital whose OCR definition information has been changed matches the hospital code of the record, and changes the OCR definition information to the mail address corresponding to the pharmacy code of the obtained record. A mail notifying of is sent (see FIG. 17).

The input unit 1b includes a keyboard provided with cursor keys, numeral input keys and various function keys, and a pointing device such as a mouse. The input unit 1b outputs a depression signal depressed by the operator by the keyboard and a position signal of the pointing device. Output to the CPU 1a.

The RAM 1c stores various data such as various programs, input instructions, input data and processing results in the CPU.
The memory 1a has a work area for storing random access and can store various states.

The display unit 1d is a CRT (Cathode Ray Tub).
e), LCD (Liquid Crystal Display), PDP (Pla
sma Display Panel) or EL (Electro Luminescenc
e) A display or the like is provided, and various display data are displayed on the screen according to a display instruction input from the CPU 1a.

The storage device 1e has a recording medium (not shown) in which various programs, various data, etc. are stored in advance or writable, and the recording medium is a magnetic or optical recording medium or a semiconductor or the like. CP such as non-volatile memory
It is composed of a U1a readable recording medium. The recording medium is a fixed one such as a fixed hard disk, a CD-RW, a DVD + RW, a DVD-RAM,
Includes removable types such as memory cards and portable hard disks that can be removably attached.

The RAM 1c and the storage device 1e are the CPU 1
The internal data can be read and rewritten under the control of a. As the recording medium, a readable / writable flexible disk, a magneto-optical disk, or a flash memory may be adopted. In particular, a read-only CD-RO is used as a recording medium for recording a program.
A configuration that employs M, DVD, ROM or the like may be used.

Further, a part or all of the programs, data, etc. stored in the storage device 1e are transferred from an external device to a LAN (Local Area Network) or WAN (Wide Area Neighbor).
communication control unit 1 via a communication network 4 such as two
The storage device 1e may be configured to be received from f and stored, and the storage device 1e may be a storage device of an external device built on the communication network 4. Furthermore, the various programs may be transmitted and installed to an external device via the communication network 4.

The communication control unit 1f is composed of a network card, a modem, a TA (Terminal Adapter), a router and the like for communicating with an external device via the communication network 4. The timer unit 1g outputs the current date and time at the request of the CPU 1a.

Next, referring to FIG. 3, the dispensing pharmacy terminal 2A,
The internal configuration of 2B will be described. Dispensing pharmacy terminals 2A, 2B
Includes a CPU 2a, an input unit 2b, a RAM 2c, a display unit 2d, a storage device 2e, a communication control unit 2f, a printing device 2i, an image reader 2j, and a bus 2h. CPU 2a, input unit 2b, RAM 2c, display unit 2
d, the storage device 2e, and the communication control unit 2f are the CPU 1 described above.
a, input unit 1b, RAM 1c, display unit 1d, storage device 1
e, it has the same function as the communication control unit 1f, and different parts will be described.

The CPU 2a of the dispensing pharmacy terminals 2A and 2B is
A pharmacy registration process, a prescription OCR process, and a change process are executed. The CPU 2a communicates with the dispensing pharmacy server 1 through the communication control unit 2f by executing the pharmacy registration process, and transmits the information of the self-dispensing pharmacy input by the operator from the input unit 2b to the dispensing pharmacy server 1. The input information of the self-prepared pharmacy is stored in the pharmacy master file E1 of the storage device 1e (see FIG. 11).

Further, the CPU 2a reads the prescription by executing the prescription OCR process, recognizes OCR characters in the read data, and stores the OCR definition file corresponding to the hospital name of the recognized prescription in the storage device 2e. If so, the read data is character-recognized by using the stored and stored OCR definition file, and a dispensing record database is created from the character-recognized data and stored in the storage device 2e.

If the target OCR definition file is not stored in the storage device 2e, the CPU 2a executes OCR.
When the definition file is received from the dispensing pharmacy server 1, the read data is character-recognized using the received OCR definition file, and when the OCR definition file cannot be received from the dispensing pharmacy server 1, the user is prompted to input the OCR definition file. , The input OCR definition file is transmitted to the dispensing pharmacy server 1, and the read data is character-recognized using the input OCR definition file (FIGS. 12 to 15).
reference).

When the mail received from the dispensing pharmacy server 1 is the change notification mail of the OCR definition information due to the execution of the change processing, the CPU 2a downloads the changed OCR definition information to the input unit 1b. If user input is accepted and input to download is made,
The changed OCR definition information is downloaded from the dispensing pharmacy server 1 and stored in the storage device 2e (see FIG. 18).

The printing device 2i is of a dot impact type, a thermal transfer type, a laser type, an ink jet type, or the like.
An apparatus for printing on a print recording medium such as paper. The image reader 2j is a device that optically reads an image printed on a print recording medium such as paper. Bus 2h is CPU2
a, input unit 2b, RAM 2c, display unit 2d, storage device 2
e, communication control unit 2f, printing device 2i, image reader 2
j is communicatively connected.

Information stored in the storage device 1e of the dispensing pharmacy server 1 and the storage devices 1e of the dispensing pharmacy terminals 2A and 2B will be described below with reference to FIGS. FIG. 4 is a diagram showing the configuration of the pharmacy master file E1, and FIG. 5 is a diagram showing the configuration of the hospital specifying character table E2.
Is a diagram showing information about a hospital, (I) is a diagram showing a structure of a hospital master file E3, and (II) is a diagram showing
7 is a diagram showing the structure of an OCR definition file E4, and FIG.
[Fig. 6] is a diagram showing a structure of a dispensing record database E5.

FIG. 8 is a diagram showing information relating to transactions, and is a diagram showing the structure of the total amount memory E7. Figure 9
Is a diagram showing information on the dispensing pharmacy server side, (I)
Is a diagram showing a transaction transaction file F1, (II) is a diagram showing a pharmacy master file F2, (III) is a diagram showing the configuration of an account data file F3, and FIG. 10 is a prescription G. FIG.

As shown in FIG. 4, the dispensing pharmacy terminals 2A, 2
A pharmacy master file E1 that is information about the self-dispensing pharmacy is stored in the storage device 2e of B. Pharmacy master file E1
Stores a pharmacy name E11 of the self-dispensing pharmacy, a mail address E12 of the self-dispensing pharmacy, an address E13 of the self-dispensing pharmacy, and a TELE14 which is a telephone number of the self-dispensing pharmacy.

Further, as shown in FIG. 5, the dispensing pharmacy terminal 2
In the storage devices 2e of A and 2B, a hospital specifying character table E2 for specifying a hospital at the time of OCR character recognition is stored. The hospital identification table E2 includes a hospital name E21 which is information for identifying a hospital name, an address E22 which is information for identifying an address, a TELE23 which is information for identifying a telephone number, and a postal code. The postal code E24, which is information for specifying, is stored.

Further, as shown in FIG. 6, the dispensing pharmacy terminal 2
A hospital master file E3 for specifying a hospital and an OCR definition file E4 that is definition information for character recognition are stored in the storage devices 2e of A and 2B. Figure 6 (I)
As shown in, the hospital master file E3 includes a hospital code E31 that is a hospital code, a hospital name E32, a hospital address E33, a hospital telephone number TELE34, a hospital zip code E35, and an OCR definition file. An OCR definition presence / absence E36 indicating presence / absence and an OCR definition file name E37 when an OCR definition file exists are stored.

As shown in FIG. 6 (II), the OCR definition file E4 includes an OCR definition file name E41 and a hospital name E4.
42, an item area in the prescription and a data type of the data in each item area, a public expense bearer number position E43, an insurer number position E44, and the like are stored. The public expense bearer number position E43 is the start point coordinates (X ₁ ,
Y ₁₎ and indicated by end point coordinates (X _11, Y _11), insurer number position E44 indicates the character recognition position of OCR at the start point coordinates (X _2, Y ₂₎ and the end point coordinates (X _22, Y ₂₂₎ For example, in the prescription G of FIG. 10, the coordinates of the starting point G1 are the starting point coordinates (X ₁ , Y ₁ ), the coordinates of the ending point G2 are the ending point coordinates (X ₁₁ , Y ₁₁ ), and the coordinates of the starting point G3 are the starting point coordinates ( X
₂ , Y ₂ ), and the coordinates of the end point G4 are the end point coordinates (X ₂₂ , Y ₂ ).
₂₂ ).

Further, as shown in FIG. 7, the dispensing pharmacy terminal 2
The storages 2e of A and 2B store the dispensation record database E5 which is a database of dispensation records. The dispensing record database E5 is a prescription header E which is header information of the prescription.
51, a prescription issuing hospital E52 that is information on the hospital that issued the prescription, patient information E53, dispensing pharmacy information E54 that is information on the dispensing pharmacy, and drug E55 that is information on the drug.
And are stored.

The prescription header E51 stores information such as a prescription ID, a prescription registration date, and a prescription expiration date. The prescription issuing hospital E52 is a hospital name related to the prescription issuing hospital,
Stores information such as hospital code and doctor name. Patient information E5
3 stores information such as the patient name, the birth date of the patient, and the insurance card number. The dispensation pharmacy information E54 stores information such as a pharmacist name and a receptionist name that belong to the dispensation pharmacy. The drug E55 stores, for each drug (1 to n: n is an arbitrary number), information such as a drug name, a drug price, the number of doses taken by a doctor, the number of doses / day, and the timing of taking after meals.

Further, as shown in FIG. 8, the dispensing pharmacy terminal 2
In the storage devices 2e of A and 2B, a total amount memory E6 for managing income and expenses on the side of the dispensing pharmacy terminal is stored. The total amount of money memory E6 is a total amount of usage charge memory E61, which is the total usage charge of the OCR definition file provided from the dispensing pharmacy server 1, and the total amount of remuneration of the OCR definition file, which is provided to the dispensing pharmacy server 1. And a total memory E62.

Further, as shown in FIG. 9, in the storage device 1e of the dispensing pharmacy server 1, a transaction transaction file F1 as transaction history information, a pharmacy master file F2 which is information relating to the dispensing pharmacy, and the dispensing pharmacy server 1 The server operator account data F3 of the operator of is stored. As shown in FIG. 9 (I), the transaction transaction file F1 includes a date F11 when the transaction transaction with the dispensing pharmacy terminals 2A and 2B occurred, and a time minute second F12.
A pharmacy code F13 of a dispensing pharmacy, a transaction classification F14 indicating the content of the transaction, and a hospital code F15 of the OCR definition file with which the transaction is performed are stored. Transaction category F14 is OCR
The definition file from the dispensing pharmacy server 1 to the dispensing pharmacy terminal 2
The transaction (download) transmitted to A and 2B is 0, and the transaction (upload) transmitted from the dispensing pharmacy terminals 2A and 2B to the dispensing pharmacy server 1 is 1.

As shown in FIG. 9 (II), the pharmacy master file F2 includes the pharmacy code F21 of the dispensing pharmacy and the pharmacy name F.
22, a mail address F23, an address F24, a telephone number TELF25, and pharmacy account data F26 of the operator of each dispensing pharmacy are stored. As shown in FIG. 9 (III), the server operator account data F3 stores a bank name F31, a store name F32, an account number F33, etc. in which the operator of the dispensing pharmacy server 1 has an account.

Although not shown, the hospital master file E3 and the OCR definition file E4 on the dispensing pharmacy terminal side are
It is assumed that the dispensing pharmacy server 1 also stores a file having a similar configuration in the storage device 1e. The files on the dispensing pharmacy server 1 side are the hospital master file F4 and the OCR definition file E5.

Next, the operation of the pharmacy system α is shown in FIG.
This will be described with reference to 0 to FIG. For simplicity, the dispensing pharmacy terminal 2A of the dispensing pharmacy terminals 2A and 2B will be described below as a representative.

FIG. 11 is a flowchart showing a pharmacy registration process on the dispensing pharmacy side, FIG. 12 is a flowchart showing a prescription OCR process on the dispensing pharmacy terminal side, and FIG. 13 is a continuation of FIG. 14 is a diagram showing a flowchart of the usage fee data receiving process in FIG. 12, and FIG. 15 is a diagram showing a flowchart of the reward amount data receiving process in FIG. FIG. 16 is a diagram showing a flow chart of a definition file transmission / reception process on the dispensing pharmacy server side, FIG. 17 is a diagram showing a flow chart of change notification processing on the dispensing pharmacy server side, and FIG. 18 is a diagram showing a dispensing pharmacy terminal side. It is a figure which shows the flowchart of a change process.

First, the pharmacy registration process will be described with reference to FIG. In the pharmacy registration process, unregistered pharmacy OCR
This is a process of registering in the dispensing pharmacy server 1 as a target for providing and receiving the definition file. Here, for simplification, assuming that the unregistered dispensing pharmacy terminal is the dispensing pharmacy terminal 2A,
A case where the pharmacy registration process is executed in the dispensing pharmacy terminal 2A will be described.

At the dispensing pharmacy terminal 2A, the CPU 2a stores in the storage device 2e, triggered by the operator of the dispensing pharmacy terminal 2A in the dispensing pharmacy inputting an instruction to execute the pharmacy registration process via the input unit 2b. The program for the registered pharmacy registration process is read out and expanded in the RAM 2c to execute the pharmacy registration process.

The flowchart shown in FIG. 11 is for explaining a program for causing a computer constituting the dispensing pharmacy terminal 2A to realize each function. This program will be described by taking an example in which it is stored in the storage device 2e in the form of a program code that can be read by the CPU 2a.
It is not necessary to store all the functions in the storage device 2e, and some or all of them may be received and realized via the communication network 4 as needed. This description applies to other processes as well, corresponding to the execution subject of the process.

First, the CPU 2a causes the communication controller 2f to
The Internet is connected on the communication network 4 (step S11). Then, the CPU 2a uses the communication control unit 2
In step f12, the dispensing pharmacy server 1 is communicatively connected so that data can be transmitted and received (step S12). Then, the CPU 2a
The input unit 2b is made to accept the input of the pharmacy name, mail address, address, TEL, and account data of the self-dispensing pharmacy from the operator (step S13). The account data is the bank name, store name, and account number that the self-dispensing pharmacy trades. The operator
When confirming the input, the confirmation instruction is input to the input unit 2b.

Then, the CPU 2a determines whether or not a confirmation instruction of the input data is input in step S13 (step S14). When the confirmation instruction has not been input (step S14; NO), the process returns to step S13. When the confirmation instruction is input (step S14; Y
ES), the CPU 2a transmits the data input in step S13 to the dispensing pharmacy server 1 via the communication control unit 1f and the communication network 4 (step S1).
5).

Then, the CPU 2a stores the data input in step S13 in the storage device 1e as the pharmacy master file E1 (step S16), and ends the pharmacy registration process. Step S16 is, specifically,
The pharmacy name corresponding to the entered pharmacy name, email address,
The address and TEL are the pharmacy name E11, the mail address E12, the address E13, and T of the pharmacy master file E1, respectively.
Store in ELE14.

Dispensing pharmacies that have not executed the pharmacy registration process and are not stored in the pharmacy master file F2 of the dispensing pharmacy server 1 have a contract with the operator of the dispensing pharmacy server 1 for uploading and downloading the OCR definition file. It does not mean that.

After the execution of step S15, on the dispensing pharmacy server 1 side, the CPU 1a executes the communication network 4
Also, the pharmacy name, mail address, address, TEL, and account data are received from the dispensing pharmacy terminal 2A via the communication control unit 1f. Then, the CPU 1a issues a pharmacy code corresponding to the pharmacy name, and issues the issued pharmacy code, the received pharmacy name, email address, address, TEL, and account data.
Pharmacy code F of the pharmacy master file F2 on the storage unit 1e
21, pharmacy name F22, email address F23, address F2
4. Stored in TELF25 and account data F26. The reception process on the side of the dispensing pharmacy server 1 is an interrupt process triggered by the reception at the dispensing pharmacy server 1 of the data transmission from the dispensing pharmacy terminal 2A.

Next, the prescription OCR processing on the dispensing pharmacy terminal side and the corresponding definition file transmission / reception processing on the dispensing pharmacy server side will be described in order. First, the prescription OCR processing in the dispensing pharmacy terminal 2A will be described with reference to FIGS. Prescription OCR processing is performed from the dispensing pharmacy server 1
This is a process for reading a prescription, recognizing OCR characters, and creating and storing a dispensing record database so that a CR definition file can be acquired and a new OCR definition file can be transmitted to the dispensing pharmacy server 1.

At the dispensing pharmacy terminal 2A, the CPU 2a stores in the storage device 2e, triggered by the operator of the dispensing pharmacy terminal 2A in the dispensing pharmacy inputting an instruction to execute the prescription OCR process via the input unit 2b. The prescription OCR processing program that has been read is read out, and the RAM 2c is read.
To execute the prescription OCR process.

In advance, the operator of the dispensing pharmacy terminal 2A sets the paper brought by the patient to the dispensing pharmacy in the image reader 2j. The paper is issued at the hospital where the patient received medical treatment.

First, the CPU 2a uses the image reader 2j.
Then, the image of the set paper is read (step S21). Then, the CPU 2a sets the read data of the sheet, which has been image-read in step S21, to OC.
The letter R is recognized (step S22).

Then, the CPU 2a determines whether the paper is a prescription (step S23). Step S23
Determines whether or not the characters "prescription" are recognized on the prescription. This is not only the exact match of the characters in the "prescription", but also the recognition of similar words such as "shoshosen" and the partial match such as "prescription" within the range that can be recognized as a prescription. is there.

If it is not a prescription (step S23; N)
O), the CPU 2a displays the reading error guidance on the display unit 2d (step S24), and ends the prescription OCR process. For example, the operator is prompted to instruct to reread the sheet or to confirm the sheet by the operator.

If it is a prescription (step S23; YE
S), the CPU 2a obtains hospital data from the character recognized in step S22 using the hospital specifying table E2 stored in the storage device 2e (step S25). Specifically, on the prescription, the hospital name E21, address E22, TELE2 of the hospital specifying table E2
3. The hospital name, address, TEL, and zip code are acquired from the part where the characters stored in the zip code E24 are recognized. For example, in the prescription G of FIG.
The postal code, address, hospital name, and telephone number are acquired from G6, G7, and G8.

Then, the CPU 2a refers to the hospital master file E3 on the storage device 2e, matches the hospital name, address, telephone number, and zip code acquired in step S23, and has the OCR definition presence / absence E36. The target record is searched (step S26).

Then, the CPU 2a determines whether or not the target record exists in step S26 (step S27). When the target record exists (step S27; YES), the CPU 2a sets the OC of the target record of the hospital master file E3 stored in the storage device 2e.
The OCR definition file name is acquired from the R definition file name E37, and the OCR definition file having the acquired OCR definition file name is acquired from the OCR definition file E4 stored in the storage device 2e and stored in the RAM 2c (step S28). ).

Then, the CPU 2a uses the acquired RAM 2
Using the OCR definition file on c, the read data of the prescription image-read in step S21 is recognized again by the OCR character (step S29). Then, the CPU 2a creates a prescription image in an actual prescription format from the character-recognized data acquired in step S29 and the OCR definition file, and the RAM 2c.
And the prescription image is displayed on the display unit 2d (step S30). The character-recognized data is specifically for storing in the dispensing record database E5,
Prescription header, prescription issuing hospital, patient information, dispensing pharmacy information, and drug information.

Then, the CPU 2a determines whether the operator has input through the input unit 2b that the character-recognized data displayed in step S30 is corrected.
It is determined whether there is a correction (step S31). If there is a correction (step S31; YES), the CPU 2a causes the input unit 2b to accept a correction input from the operator (step S32). In step S32, the prescription image data stored in the RAM 2c is also changed according to the correction input.

Then, in the CPU 2a, the operator operates the input unit 2
It is determined whether or not the character-recognized data on the prescription image is confirmed by inputting that there is no portion to be corrected in the character-recognized data via b (step S3).
3). If not confirmed (step S33; NO), the process returns to step S31. If there is no correction (step S3)
1; YES), and proceeds to step S33.

When it is confirmed (step S33; YE
S), the CPU 2a sets the character-recognized data stored in the RAM 2c and determined in step S33,
The information is stored in the dispensing record database E5 of the storage device 2e (step S34), and the prescription OCR process is ended. In step S34, the prescription header, the prescription issuing hospital, the patient information, the dispensing pharmacy information, and the drug information, which are character-recognized data, are stored in the prescription header E5 of the dispensing record database E5.
1. Prescription issuing hospital E52, patient information E53, dispensing pharmacy information E54, and drug E55 are stored.

After that, when the operator inputs a print instruction from the input section 2b, the dispensing record database E5 is stored in the printing device 2
It can be printed as a pharmacy record from i.

If the target record does not exist (step S27; NO), the CPU 2a causes the communication controller 2f to connect to the Internet on the communication network 4 (step S35). Then, the CPU 2a uses the communication control unit 2f.
Then, the dispensing pharmacy server 1 is communicatively connected so that data can be sent and received, and an OCR definition file request is sent to the dispensing pharmacy server 1 (step S36). The OCR definition file request is the hospital name, address,
In addition to the telephone number and zip code, the transaction division and the pharmacy master file (E1) are included. The transaction classification indicates 0 download of the OCR definition file at the dispensing pharmacy terminal 2A.
Is.

Then, the CPU 2a determines whether or not the reception of the OCR definition file and the hospital code from the dispensing pharmacy server 1 is started via the communication network 4 and the communication control unit 2f (step S37). When the reception is started (step S37; YES), the CPU 2a completes the reception of the OCR definition file and the hospital code, and stores the received OCR definition file in the OCR definition file E4 of the storage device 2e.

Further, the CPU 2a stores the received OCR definition file in the RAM 2c, and the hospital name, address, TEL, zip code, received hospital code, OCR definition present, and OCR of the received OCR definition file in step S22. The definition file names are the hospital name E32, the address E33, and the TELE3 of the hospital master file E3, respectively.
4. Newly store or overwrite store in the postal code E35, hospital code E31, OCR definition presence / absence E36, and OCR definition file name E37 (step S38).

Then, the CPU 2a executes a usage charge data receiving process (step S39), and proceeds to step S29. Here, the usage fee data receiving process will be described with reference to FIG. First, the CPU 2a uses the communication control unit 2f.
It is determined whether or not the usage charge data is received from the dispensing pharmacy server 1 via (step S391). The usage fee data is data of the fee paid to the dispensing pharmacy server 1 side when the dispensing pharmacy receives and uses the OCR definition file from the dispensing pharmacy server 1.

If the usage charge data has not been received, the process returns to step S391. When the usage charge data is received (step S391; YES), the CPU 2a accumulates the received usage charge data in the amount of the usage charge total memory E61 of the amount total memory E6 stored in the storage device 2e (step S392). Then, the CPU 2a stores the accumulated amount of money in step S392 in the storage device 2e.
The above-mentioned usage charge total memory E71 is overwritten and stored (step S393), the usage charge data receiving process is terminated, and the process proceeds to step S29.

Returning to FIG. 13, when the OCR definition file is not received (step S37; NO), the CPU 2a
Determines whether the OCR definition file non-notification is received from the dispensing pharmacy server 1 via the communication control unit 2f (step S40). When the OCR definition file non-notification is received (step S40; YES), the CPU 2a executes OCR.
The input guidance for creating the definition file input is displayed on the display unit 2d (step S41).

Then, the CPU 2a causes the display 2d to display an OCR definition file content input screen for creating an OCR definition file content input (step S42). Then, the CPU 2a causes the input unit 2b to receive the position information and data required for the OCR definition file from the operator, stores the input information in the OCR definition file E4 on the storage device 2e, and inputs the information. Information stored in RAM2c
(Step S43).

The input information is the OCR definition file name, the data such as the hospital name acquired in step S25, and the information about the position of the item area such as the public expense bearer number position and the insurer number position. Then, the CPU 2a determines whether to end the input depending on whether the operator inputs the end of input to the input unit 2b (step S44). When the input is not completed (step S44; NO), step S
Return to 43. When input is completed (step S44; Y
ES), CPU2a, OCR stored in RAM2c
An OCR definition file provision request including the definition file is transmitted to the dispensing pharmacy server 1 via the communication control unit 2g (step S45). The OCR definition file provision request is
The OCR definition file stored in the RAM 2c, the hospital name, the address, the telephone number acquired in step S25,
In addition to the postal code, the transaction classification (= 1) and the pharmacy master file E1 are included. The transaction category is 1 indicating the OCR definition file upload in the dispensing pharmacy terminal 2A.

Then, the CPU 2a executes a reward amount data receiving process (step S46), and proceeds to step S29. Here, with reference to FIG. 15, the reward amount data receiving process will be described. First, the CPU 2a uses the communication control unit 2f.
It is determined whether the remuneration amount data and the hospital code have been received from the dispensing pharmacy server 1 via (step S46).
1). The reward amount data is data of the amount of reward received from the dispensing pharmacy server 1 side for the dispensing pharmacy providing the OCR definition file to the dispensing pharmacy server 1.

If not received, the process returns to step S461. If received (step S461; YES), C
The PU 2a receives the received reward amount data and stores the reward amount total memory E in the amount total memory E6 stored in the storage device 2e.
The total amount of money is 62 (step S462). And
The CPU 2a overwrites and stores the amount of money accumulated in step S462 in the remuneration amount total memory E62 on the storage device 2e (step S463).

Then, the CPU 2a stores the transmitted OCR definition file in the RAM 2c, and receives the hospital name, address, TEL, zip code, hospital code received, OCR definition present, acquired in step S44 in step S22. The OCR definition file name of the OCR definition file is respectively the hospital name E32, address E33, TELE34, zip code E35, of the hospital master file E3.
Stored or overwritten in the hospital code E31, OCR definition presence / absence E36, and OCR definition file name E37 (step S4).
64), the reward amount data receiving process is terminated, and step S
Proceed to 29.

Returning to FIG. 13, when the OCR definition file no notification is not received (step S40; NO), CP
U2a is the dispensing pharmacy server 1 via the communication control unit 2f.
It is determined whether or not a non-contract notice that the self-dispensing pharmacy has not signed a contract is received from the dispensing pharmacy server 1 (step S47). When no notice of contract is not received (step S4)
7; NO), and returns to step S37. When the notification of no contract is received (step S47; YES), the CPU 2a
The use of the OCR definition file and the contract recommendation guide are displayed on the display unit 2d (step S48), and the prescription OCR process is ended.

Next, the definition file transmission / reception processing in the dispensing pharmacy server 1 will be described with reference to FIG. The definition file transmission / reception process transmits prescription data including the OCR definition file to the dispensing pharmacy terminal 2A, and the unregistered OC.
This is a process of receiving the R definition file from the dispensing pharmacy terminal 2A.

In the dispensing pharmacy server 1, the communication control unit 1
Upon receipt of arbitrary data via f, the CPU 1a reads the definition file transmission / reception processing program stored in the storage device 1e, and stores it in the RAM 1c.
The definition file transmission / reception processing is executed by expanding to.

The CPU 1a, via the communication control unit 1f,
It is determined whether or not the data including the transaction classification is received from the dispensing pharmacy terminal 2A (step S51). The data including the transaction category is an OCR definition file request or an OCR definition file provision request. If not received (step S
51; NO), the definition file transmission / reception process ends.

When received (step S51; YE)
S), the CPU 1a refers to the pharmacy master file F2 in the storage device 1e and determines whether or not there is a pharmacy record corresponding to the pharmacy master file in the received data (step S52). If there is no pharmacy record (step S5)
2; NO), the CPU 1a, via the communication control unit 1f,
A non-contract notice notifying that there is no contract with the dispensing pharmacy corresponding to the received data is transmitted to the dispensing pharmacy terminal (step S5
3), the definition file transmission / reception process ends.

If there is a pharmacy record (step S5)
2; YES), the CPU 1a determines whether the transaction classification included in the received data is 0 (step S5).
4). When the transaction classification is 0 (step S54; YE
S), the received data is an OCR definition file request including a hospital name, address, telephone number, zip code, transaction classification, and pharmacy master file, and the CPU 1a stores in the OCR definition file F5 stored in the storage device 1e. , OCR definition file is searched for a target OCR definition file whose hospital name matches (step S55).

Then, the CPU 1a determines whether or not the target OCR definition file is retrieved in step S55 (step S56). When there is no target OCR definition file (step S56; NO), the CPU 1a transmits an OCR definition file no notification indicating that there is no target OCR definition file to the dispensing pharmacy terminal 2A via the communication control unit 1f (step S57), The definition file transmission / reception processing ends.

When there is a target OCR definition file (step S56; YES), the CPU 1a refers to the hospital master file F4 of the storage device 1e to obtain the hospital code corresponding to the received hospital name, and then the target OCR definition file. Together with the hospital code are transmitted to the dispensing pharmacy terminal 2A via the communication control unit 1f (step S58). And CP
The U1a stores the received pharmacy master file data in the pharmacy master file F2 of the storage device 1e (step S59). Specifically, the pharmacy name, mail address, address, and TEL of the received pharmacy master file are stored in the target pharmacy record F2 of the pharmacy master file F2.
It overwrites and stores it in the mail address F23, the address F24, and the TELF25. Further, in step S59, the pharmacy code F21 and the bank account data F2 of the pharmacy master file F2.
6. Read pharmacy code and bank account data from 6.

Then, the CPU 1a obtains the current date and time from the clock unit 1g, and outputs the current date, time, minute, second, and step S5.
Pharmacy code read in 9, transaction category received (=
0), the hospital code acquired in step S58,
The transaction transaction file F1 on the storage device 1e is stored in the date F11, the time minute second F12, the pharmacy code F13, the transaction classification F14, and the hospital code F15 (step S).
60).

Then, the CPU 1a refers to the bank account data of the dispensing pharmacy obtained in step S59 and the server operator account data F3 stored in the storage device 1e, and changes the account of the dispensing pharmacy to the account of the server operator. OC
Information for deducting the usage fee of the R definition file is created, and the information for deducting the usage fee is transmitted to the bank management server 3 via the communication control unit 1f (step S61). After step S61, the bank management server 3 deducts the usage fee from the pharmacy pharmacy account to the server operator's account based on the received deduction information.

Then, the CPU 1a transmits, through the communication control unit 1f, usage charge data that is predetermined according to the number of OCR definition files and the like to the dispensing pharmacy terminal 2A (step S62), and the definition file transmission / reception processing To finish.

If the transaction category is not 0 (step S5)
4; NO), the received data is an OCR definition file,
It is an OCR definition file provision request including a hospital name, address, telephone number, zip code, transaction category, and pharmacy master file. The CPU 1a stores the received OCR definition file in the OCR definition file F5 stored in the storage device 1e. Then, a hospital code corresponding to the received hospital name is issued, and the hospital code, the received hospital name, address, telephone number, and zip code are stored in the hospital master file F4 stored in the storage device 1e (step S63). ).

Then, the CPU 1a stores the received data of the pharmacy master file in the pharmacy master file F2 of the storage device 1e (step S64). In particular,
Similar to step S59, the pharmacy code and bank account data are read from the pharmacy code F21 and bank account data F26 of the pharmacy master file F2.

Then, the CPU 1a acquires the current date and time from the clock unit 1g, and outputs the current date, time, minute, second, and step S6.
The pharmacy code read in 4, the received transaction classification (=
1), the hospital code acquired in step S63
The transaction transaction file F1 on the storage device 1e is stored in the date F11, the time minute second F12, the pharmacy code F13, the transaction classification F14, and the hospital code F15 (step S).
65).

Then, the CPU 1a refers to the bank account data of the dispensing pharmacy obtained in step S64 and the server operator account data F3 stored in the storage device 1e, and changes the account of the server operator to the account of the dispensing pharmacy. OC
Create information to transfer the remuneration amount in the R definition file,
The information indicating the transfer is transmitted to the bank management server 3 via the communication control unit 1f (step S66). Step S
After 66, the bank management server 3 deducts the remuneration fee from the account of the server operator to the account of the dispensing pharmacy based on the received information indicating the transfer.

Then, the CPU 1a, via the communication control unit 1f, the hospital code acquired in step S63,
And the OCR definition file F5 stored in the storage device 1e
Is transmitted to the dispensing pharmacy terminal 1a (step S67).

Next, the OCR stored in the dispensing pharmacy server 1
Dispensing pharmacy terminal 2 to notify that the definition file has been changed
The change notification process for transmitting to A and the change process for receiving the change notification at the dispensing pharmacy terminal 2A will be described in order. First, the change notification process executed by the dispensing pharmacy server 1 will be described with reference to FIG.

The case of changing the OCR definition file stored in the dispensing pharmacy server 1 is, for example, a case where the prescription format is newly changed on the hospital side, and the OCR definition file is transmitted / received in the above definition file transmission / reception processing. The change notification is sent to the dispensed pharmacy terminal. OCR
This is because the OCR definition file before the change is stored in the dispensing pharmacy terminal that has transmitted and received the definition file.

Before the change notification processing is executed, the changed OCR definition file changed in the dispensing pharmacy server 1,
And an Internet for receiving the changed hospital code, which is the changed hospital code of the OCR definition file, from the hospital, storing the changed OCR definition file in the OCR definition file F5 of the storage device 1e, and downloading the changed OCR definition file. URL (Uniform Resource Locator), which is the address of the web site of the
It is assumed to be stored in e.

From the administrator of the dispensing pharmacy server 1, the input unit 1
The CPU 1a reads the program of the change notification process stored in the storage device 1e, triggered by the input of the execution instruction of the change notification process via the RAM b, and the RAM 1c.
Change notification processing is executed by expanding to.

First, the CPU 1a reads the first record from the transaction transaction F1 stored in the storage device 1e (step S71). Then, the CPU 1a acquires the hospital code F15 from the record read in step S71 or S78 (step S72). Then, the CPU 1a determines whether the hospital code read in step S72 and the changed hospital code stored in the storage device 1e match (step S73).

If they match (step S73; YE)
S), the CPU 1a uses the pharmacy code F of the read record.
13 is acquired (step S74). And CPU1
a is a pharmacy master file F stored in the storage device 1e.
2, the mail address F23 corresponding to the pharmacy code read in step S74 is acquired (step S75).

Then, the CPU 1a guides the operator of the dispensing pharmacy terminal to change the OCR definition file, a change instruction code indicating the content of the change instruction, and the change stored in the storage device 1e. A change notification mail in an electronic mail format including the URL for change and the changed hospital code is created, and the created mail is transmitted to the mail address acquired in step S75 (step S76).

Then, the CPU 1a executes step S71,
In S72, it is determined whether all the records of the transaction transaction file F1 have been read (step S7).
7). If all records have not been read (step S7)
7; NO), the CPU 1a reads the next unread record from the transaction transaction F1 stored in the storage device 1e (step S78), step S
Return to 72. When all records have been read (step S7)
7; YES), the change notification process ends.

Next, referring to FIG. 18, the dispensing pharmacy terminal 2
The change process in A will be described. In the dispensing pharmacy terminal 2A, the CP is triggered by receiving an email from the dispensing pharmacy server 1 via the communication control unit 1d and inputting an email to open the email via the input unit 2b by the operator.
The U2a executes the change process by reading the change process program stored in the storage device 2e and expanding the program in the RAM 2c.

First, the CPU 2a analyzes the received mail document for a change instruction code (step S81). Then, the CPU 2a determines whether or not there is a change instruction code in step S81 (step S82). If there is a change instruction code (step S8)
2; YES), the received mail is a change notification mail, and the CPU 2a causes the communication control unit 2f to connect to the Internet on the communication network 4 and uses the change URL in the change notification mail to change the OCR definition file. To the download site (step S83).

Then, the CPU 2a determines whether or not the operator has input a download instruction of the modified OCR definition file via the input unit 2b (step S84). If there is no download instruction (step S84; NO), CP
The U2a determines whether or not the operator has input to cancel the download of the modified OCR definition file via the input unit 2b (step S85). When the download is not canceled (step S85; NO), the process returns to step S84. When canceling the download (step S85; YES), the changing process ends.

When there is a download instruction (step S84; YES), the CPU 2a issues a modified OCR definition file request via the communication control unit 2g.
(Step S86). In the dispensing pharmacy server 1, although not shown in the flow, when the CPU 1a receives a modified OCR definition file request from the requesting dispensing pharmacy terminal via the communication control unit 1f, the OC of the storage device 1e.
The modified OCR definition file is transmitted from the R definition file F5 to the requesting dispensing pharmacy terminal.

Then, the CPU 2a downloads the modified OCR definition file from the dispensing pharmacy server 1 via the communication control unit 2g (step S87). And CP
The U2a stores the modified OCR definition file downloaded in step S87 in the OCR definition file E4 of the storage device 2e (step S88), and ends the modification process.

If there is no change instruction code (step S8)
2; YES), the received mail is not a change notification mail, and the CPU 2a displays the content of the received mail on the display unit 1d.
Is displayed (step S89), and the change process ends.

Therefore, according to the present embodiment, the dispensing pharmacy terminal reads the image of the sheet, recognizes the read data of the read sheet by OCR characters, and outputs the OCR definition file corresponding to the recognized hospital name, The OCR definition file E4 stored in the storage device 2e is searched to find the searched O
Re-read the read data by using the CR definition file
The R character is recognized, and the dispensing record database E is obtained from this recognition result.
Since the number 5 is created and stored in the storage device 2e, the character recognition of the prescription can be automated, can be performed quickly and reliably, and the burden on the operator can be reduced.

Further, the dispensing pharmacy terminal can download the OCR definition file from the dispensing pharmacy server 1 even if it does not store the OCR definition file of the hospital in which the self-dispensing pharmacy terminal is located, so the handling frequency is low. Characters can be easily recognized even for prescriptions in hospitals.

Further, since the dispensing pharmacy terminal stores the downloaded OCR definition file in the storage device 2e, even if OCR character recognition of the prescription of the same hospital is required thereafter, without communicating with the dispensing pharmacy server 1. Since it is possible to acquire the OCR definition file, it is not necessary to spend time to acquire the OCR definition file.

Further, the dispensing pharmacy to which the dispensing pharmacy terminal belongs pays the usage fee by downloading the OCR definition file and receives the compensation fee by uploading the OCR definition file. Therefore, the dispensing pharmacy has the economical merit by the compensation fee. Yes, positively upload, and the operator of the dispensing pharmacy server 1 can surely collect the fee for the provision of the OCR definition file, efficiently collect the OCR definition file, and enhance its accumulation. You can

When the OCR definition file is changed, the dispensing pharmacy server 1 sends a change notification mail to the dispensing pharmacy terminal. Therefore, the dispensing pharmacy downloads the modified OCR definition file when it is necessary. I can do things. For example, if the dispensing pharmacy determines that it is unlikely to handle the prescription of the hospital whose OCR definition file has been changed in the future, it determines that the OCR definition file after the change is not needed and does not select to download. It is possible and the financial burden is reduced.

In the present embodiment, the prescription O
In the CR process, when there is no OCR definition file on the dispensing pharmacy server 1 side, the OCR definition file is uploaded on the dispensing pharmacy terminal side. In addition to this, the OCR definition file of a hospital is changed, and the dispensing pharmacy is changed. Server 1
Even if the OCR definition file of the hospital stored in is not changed and the prescription after the change of the hospital is handled by the dispensing pharmacy terminal side, the dispensing pharmacy terminal side creates and uploads the OCR definition file. Good. In addition, in the change notification process and the change process, not only the OCR definition file is changed, but also when each data in the hospital master file is changed, the pharmacy pharmacy server 1 sends a change notice mail to the pharmacy pharmacy terminal. Good.

Further, in the change notification process and the change process, in the present embodiment, a change notification mail is sent from the dispensing pharmacy server 1 to the dispensing pharmacy terminal, and the operator of the dispensing pharmacy terminal arbitrarily downloads the OCR definition information. But
Not limited to this, when the OCR definition file is changed in the dispensing pharmacy server 1, the dispensing pharmacy server 1 transmits information including the changed OCR definition file to the dispensing pharmacy terminal, and the dispensing pharmacy terminal sends the information. When received, the OCR definition information after the change may be automatically overwritten and stored in the OCR definition information E4 on the storage device 2e without the intervention of the operator. In this case, the burden on the operator when changing the OCR definition information is reduced.

(Modification) Here, a modification of the present embodiment will be described. This modification has a configuration similar to that of the above-described embodiment, and only different parts will be described. After the pharmacy registration process, the CPU 2a of the dispensing pharmacy terminal 2A receives the pharmacy code corresponding to the name of its own pharmacy from the dispensing pharmacy server 1 and stores the received pharmacy code in the storage device 2e.

At step S58 in the definition file transmission / reception process of FIG. 16, the dispensing pharmacy server 1 sends the OCR definition file to the dispensing pharmacy terminal. In this case, the CPU 1a of the pharmacy server 1 corresponds to the dispensing pharmacy terminal. Acquire the pharmacy code, and the acquired pharmacy code is OC
The R definition file itself is written, and the OCR definition file in which the pharmacy code is written is transmitted to the dispensing pharmacy terminal via the communication control unit 1f.

To obtain the pharmacy code corresponding to the dispensing pharmacy terminal, the CPU 1a refers to the pharmacy master file in the received OCR definition file request to obtain the pharmacy name,
The pharmacy code F21 of the pharmacy master file F2 stored in the storage device 1e corresponding to the pharmacy name is acquired.

Then, in step S38 in the prescription OCR processing of FIG. 13, the dispensing pharmacy terminal 2A receives the OCR definition file to which the pharmacy code is added. Before step S29 of FIG. 12, the CPU 2a inserts a step of collating the pharmacy code received in step S38 with the pharmacy code recorded in the storage device 2e to determine whether they match. In the determination step, if it is determined that they match, the process proceeds to step S30. If it is determined that they do not match, the CPU 2a causes the display unit 2d to display an error message and ends the prescription OCR process. .

According to this modification, on the dispensing pharmacy terminal side,
Since the OCR definition file in which the pharmacy code is written is downloaded, even if the downloaded OCR definition file is illegally distributed to another dispensing pharmacy, the dispensing pharmacy terminal of the illegal distribution destination uses the OCR definition file concerned. The prescription cannot be recognized by characters. Therefore, it is possible to prevent the downloaded OCR definition file from being illegally distributed to other dispensing pharmacies.

The dispensing pharmacy server 1 may be a server device belonging to a hospital. Further, in the present embodiment and the modified examples, the OCR character recognition is performed on the program using the image reader 2j, but it is also possible to use a dedicated OCR device.

Although the embodiments of the present invention have been described above, the present invention is not necessarily limited to the above-described means and techniques, and the objects referred to in the present invention can be achieved and the effects referred to in the present invention can be achieved. Modifications can be appropriately made within the range.

[0139]

According to the first aspect of the invention, the pharmacy data processing device character-recognizes the prescription data and retrieves the prescription recognition information corresponding to the recognized medical institution name from the processing side storage means. Since the character recognition is performed using the retrieved prescription recognition information and the dispensing history is created and stored, it is possible to automate the character recognition of the prescription, quickly and surely, and reduce the burden of character recognition.

According to the ninth aspect of the invention, even when the pharmacy data processing device does not store the prescription recognition information used for character recognition, the pharmacy data management device does not store the prescription recognition information stored in the device itself. Since it can be provided to the pharmacy data processing device, the pharmacy data processing device can easily perform character recognition using the received prescription recognition information even for a prescription of a medical institution that is rarely handled.

[Brief description of drawings]

FIG. 1 is a diagram showing a configuration of a pharmacy system α according to an embodiment of the present invention.

FIG. 2 is a block diagram showing an internal configuration of a dispensing pharmacy server 1 in FIG.

FIG. 3 is a block diagram showing an internal configuration of the dispensing pharmacy terminals 2A and 2B in FIG.

FIG. 4 is a diagram showing a structure of a pharmacy master file E1.

FIG. 5 is a diagram showing a configuration of a hospital specifying character table E2.

FIG. 6 is a diagram showing information about a hospital, where (I) is
It is a figure which shows the structure of the hospital master file E3, (II)
[Fig. 6] is a diagram showing the structure of an OCR definition file E4.

FIG. 7 is a diagram showing a structure of a dispensing record database E5.

FIG. 8 is a diagram showing a configuration of a total amount memory E7.

FIG. 9 is a diagram showing information on the dispensing pharmacy server side,
(I) is a diagram showing a transaction transaction file F1, (II) is a diagram showing a pharmacy master file F2, and (III) is a diagram showing a configuration of an account data file F3.

10 is a diagram showing a prescription G. FIG.

FIG. 11 is a diagram showing a flowchart of pharmacy registration processing on the dispensing pharmacy side.

FIG. 12 is a diagram showing a flowchart of prescription OCR processing on the dispensing pharmacy terminal side.

FIG. 13 is a diagram showing a flowchart continued from FIG. 12;

FIG. 14 is a diagram showing a flowchart of a usage fee data receiving process in FIG.

FIG. 15 is a diagram showing a flowchart of a reward amount data receiving process in FIG. 12.

FIG. 16 is a diagram showing a flowchart of definition file transmission / reception processing on the dispensing pharmacy server side.

FIG. 17 is a diagram showing a flowchart of change notification processing on the dispensing pharmacy server side.

FIG. 18 is a diagram showing a flowchart of a changing process on the dispensing pharmacy terminal side.

[Explanation of symbols]

α ... pharmacy system 1 ... Dispensing pharmacy device 1a, 2a ... CPU 1b, 2b ... Input section 1c, 2c ... RAM 1d, 2d ... Display section 1e, 2e ... Storage device 1f, 2f ... communication control unit 1g ... Timer 1h, 2h ... bus 2A, 2B ... Dispensing pharmacy terminal 2i ... Printing device 2j ... Image reader 3 ... Bank management server 4 ... communication network

Claims (18)

[Claims] 1. A pharmacy data processing device for creating and storing a dispensing history from a prescription corresponding to each of a plurality of medical institutions, wherein the prescription recognition information is position information of an item area in the prescription, and the item area. Including the data type of the data in
Information for character recognition of prescription data using the position information and data type, medical institution name corresponding to each medical institution, the prescription recognition information corresponding to each medical institution name, and dispensing history of a patient Processing side storage means for storing, a reading means for reading a patient's prescription issued from the medical institution as prescription data, a character recognition means for character recognition of the prescription data read by the reading means, and the character recognition Specifying means for specifying the medical institution name from the prescription data character-recognized by the means, and the prescription recognition information corresponding to the medical institution name specified by the specifying means, read from the processing side storage means, and the read prescription recognition information Based on the prescription data, the dispensing history is created from the prescription data recognized by the character recognizing means. Comprising a dispensing history creation means for storing the dispensing history means, pharmacy data processing apparatus characterized by. 2. The processing side communication means for communicating with the medical institution name and a pharmacy data management device for managing prescription recognition information corresponding to the medical institution name via a communication network, the processing side storage means. In the case where the prescription recognition information corresponding to the medical institution name specified by the specifying means is not stored, the processing side communication means acquires the prescription recognition information corresponding to the medical institution name specified by the specifying means. A request is transmitted to the pharmacy data management device, new prescription recognition information is received from the pharmacy data management device, and the dispensing history creation means is based on the new prescription recognition information received in the processing side communication means. Creating a dispensing history from the prescription data recognized by the character recognizing means, and storing the dispensing history in the processing side storage means. Pharmacy data processing apparatus according to claim 1, wherein. 3. The pharmacy data processing apparatus according to claim 2, wherein the processing side storage means stores prescription recognition information newly received by the processing side communication means. 4. The system further comprises registration information setting means for setting registration information for registering a self-pharmacy data processing device in the pharmacy data management device, wherein the processing side communication means is set in the registration information setting means. The pharmacy data processing device according to claim 2, wherein the registered information is transmitted to the pharmacy data management device for registration. 5. The prescription recognition information received by the processing-side communication means includes identification information for identifying a pharmacy data processing device, and the identification information included in the received prescription recognition information is self-pharmacy data processing. In the case of indicating a device, the dispensing history creating means reads the prescription recognition information corresponding to the medical institution name specified by the specifying means from the processing side storage means in which the received prescription recognition information is stored, The dispensing history is created from the prescription data character-recognized by the character recognizing means based on the prescription recognition information received by the processing-side communication means, and the dispensing history is stored in the processing-side storage means. Claim 2 or 4
The described pharmacy data processing device. 6. A recognition information setting means for setting prescription recognition information is further provided, wherein the processing side communication means transmits the prescription recognition information set by the recognition information setting means to the pharmacy data management device, The pharmacy data processing device according to claim 2, wherein the pharmacy data management device stores the pharmacy data management device. 7. When the prescription recognition information stored in the pharmacy data management device is changed, the processing side communication means is
The modified prescription recognition information is received from the pharmacy data management device, and the processing side storage unit stores the modified prescription recognition information received by the processing side communication unit. The pharmacy data processing device according to claim 2, 3, 4, 5, or 6. 8. The processing-side communication means receives, from the pharmacy data management device, change information indicating that prescription recognition information stored in the pharmacy data management device has been changed, and the processing-side communication means receives the change information. The system further comprises a transmission request input means for inputting a transmission request of the changed prescription recognition information when the change information is received, and when the transmission request is inputted by the transmission request input means, the processing side communication means Transmits a transmission request for the changed prescription recognition information to the pharmacy data management device, receives the changed prescription recognition information from the pharmacy data management device, and the processing side storage means is the processing side. 7. The pharmacy data processing device according to claim 2, wherein the changed prescription recognition information received by the communication means is stored. 9. A pharmacy data management device for managing prescription recognition information of a prescription corresponding to each of a plurality of medical institutions, wherein the prescription recognition information is position information of an item area in the prescription and in the item area. Is information for character recognition of prescription data using the position information and the data type, including the data type of the data, the name of the medical institution corresponding to each medical institution, and the prescription corresponding to the name of each medical institution. Management side storage means for storing recognition information, management side communication means for connecting via a communication network to a pharmacy data processing device for creating and storing a dispensing history from the prescription, the management side communication means, wherein the pharmacy data When the request for transmitting the prescription recognition information corresponding to the medical institution name is received from the processing device, the prescription recognition information corresponding to the acquisition request is received. And a search unit that searches from the management-side storage unit, wherein the management-side communication unit transmits the prescription recognition information searched by the search unit to the pharmacy data processing device that is the transmission request source. Characteristic pharmacy data management device. 10. The management side storage means stores registration information of the pharmacy data processing device, and when the registration information of the pharmacy data processing device that is the transmission request source is stored, the management side communication means. 10. The pharmacy data management device according to claim 9, wherein the prescription recognition information retrieved by the retrieval means is transmitted to the pharmacy data processing device of the transmission request source. 11. The management-side storage means further stores identification information for identifying the pharmacy data processing device, and the prescription recognition information retrieved by the retrieval means corresponds to the pharmacy data processing device of the transmission request source. Further comprising an addition unit for adding the identification information, the management-side communication unit transmits the prescription recognition information to which the identification information is added by the addition unit, to the pharmacy data processing device of the transmission request source, 11. The pharmacy data management device according to claim 9 or 10. 12. The management-side storage means stores charging information relating to use of the prescription recognition information for each of the pharmacy data processing devices, and the prescription recognition information is stored in the management-side communication means as the transmission request source. 11. A charging update means for updating the charging information stored in the management side storage means in correspondence with the pharmacy data processing device, when the data is transmitted to the pharmacy data processing device. Alternatively, the pharmacy data management device according to item 11. 13. The management-side communication means receives prescription recognition information from the pharmacy data processing device, and the management-side storage means stores the prescription recognition information received by the management-side communication means. The pharmacy data management device according to claim 9, 10, 11, or 12. 14. The management-side storage means stores, according to the prescription recognition information transmitted from the pharmacy data processing device, reward amount information given to each pharmacy data processing device of the information transmission source, When the prescription recognition information is received from the pharmacy data processing device in the management side communication means, the remuneration amount for updating the remuneration amount information stored in the management side storage means corresponding to the pharmacy data processing device of the information transmission source. 14. The pharmacy data management device according to claim 13, further comprising update means. 15. The management-side communication means further comprises recognition information changing means for changing the prescription recognition information stored in the management-side storage means, and when the prescription recognition information is changed by the recognition-information changing means. 15. The pharmacy data according to claim 9, 10, 11, 12, 13, or 14, wherein the changed prescription recognition information is transmitted to the pharmacy data processing device to store the changed prescription recognition information. Management device. 16. The management-side communication means further comprises recognition information changing means for changing the prescription recognition information stored in the management-side storage means, and when the prescription recognition information is changed by the recognition-information changing means. When the change information indicating that the prescription recognition information is changed is transmitted to the pharmacy data processing device and a transmission request for the information is received from the pharmacy data processing device of the information transmission destination, the changed prescription recognition information The information is transmitted to the pharmacy data processing device of the transmission request source and stored therein.
The pharmacy data management device according to 1, 12, 13 or 14. 17. A medical institution name corresponding to each of a plurality of medical institutions, information for character recognition of prescription data, prescription recognition information corresponding to each medical institution name, and a dispensing history of a patient are stored. A computer mounted on a device having a processing side storage means, a function of reading a prescription of a patient issued from the medical institution as prescription data, a function of character recognition of the read prescription data, and the character recognition A function of specifying a medical institution name from prescription data, a function of reading prescription recognition information corresponding to the specified medical institution name from the processing side storage unit, and a function of reading the prescription recognition information by using the read prescription recognition information. A function of character recognition of prescription data; a function of creating a dispensing history from the prescription data which is character-recognized by using the prescription recognition information; A program for realizing the function of storing the prepared dispensing history in the processing side storage means. 18. A medical institution name capable of communicating with a pharmacy data processing device for creating and storing a dispensing history from a prescription via a communication network, and for character recognition of medical institution names corresponding to a plurality of medical institutions and prescription data. Information stored in a device equipped with a management-side storage unit that stores the prescription recognition information corresponding to each medical institution name, and the prescription recognition information corresponding to the medical institution name from the pharmacy data processing device. And a prescription recognition information corresponding to the received transmission request,
A program for realizing a function of searching from the management-side storage means and a function of transmitting the searched prescription recognition information to the pharmacy data processing device that is the transmission request source.