JP2006172369A - Medical information management system, common master management system used for it, and individual master management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To efficiently manage a master file about medical information. <P>SOLUTION: In this medical information management system, a common master management system 140 manages a common master file about medical information to be used in common between a plurality of medical institutes/sections on the outside of the medial institute. An individual master management system 130 is arranged in each medical institute/section to manage an individual master file about individual information to be used in the institute/section. The individual master management system uses the common master file via a network. A common master maintenance part 14 performs maintenance of the common master file. An individual master maintenance part 32 performs maintenance of the individual master file. The common master maintenance part 14 and the individual mater maintenance part 32 carry out maintenance independently of each other. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a medical information management technique, and more particularly to a medical information management system that manages a master file of medical information, and a common master management system and an individual master management system used therefor.

A system for managing medical practice includes a server, a personal computer (hereinafter referred to as “PC”), and a portable terminal (for example, PDA (Personal Digital Assistants)), and further includes a wired or wireless LAN (Local Area). Network). In such a configuration, the server records data used in the entire system, and the PC accepts order registration or the like from a nurse or the like. In addition, the nurse carries a drip to the patient with reference to a work schedule list such as a drip scheduled to be carried with the portable terminal. Furthermore, after completion of the infusion, the nurse inputs the implementation result to the mobile terminal. Since the portable terminal transmits the input implementation result to the PC or server, the PC or server can manage the implementation result (see, for example, Patent Document 1).
JP 2004-110818 A

  In the system as described above, a master file for managing medical information such as medical equipment, medical fees, and hospital staff is used. Such a master file has a large amount of data. In particular, there are hundreds of thousands of types of medical equipment, and if it is managed with images, the amount of data becomes very large.

  In addition, when a change occurs in the contents of the above master file, such as when new medical equipment is released, medical fees are revised, or personnel changes are made, additions, updates, and deletions are made to the master file. Such maintenance work is required. This maintenance work is complicated for medical institutions. However, if you neglect the maintenance work, the contents of the master file will become obsolete and deviate from the actual situation.

  The present invention has been made in view of such circumstances, and an object thereof is to provide a medical information management system that efficiently manages a master file related to medical information, and a common master management system and an individual master management system used therefor. It is in.

  In order to solve the above-described problems, a medical information management system according to an aspect of the present invention is a common management system for managing a common master file related to medical information that should be commonly used in a plurality of medical institutions or medical departments. A master management system; and an individual master management system that is provided for each medical institution or medical department and manages individual master files related to individual information to be used in the institution or department. The individual master management system can use the common master file via the network. “Individual information” may include personnel information of the institution or department.

  According to this aspect, since a part of the master file related to medical information to be managed by each medical institution or medical department can be managed by the common master management system, the master file can be efficiently managed.

  The common master management system may include a common master maintenance unit that executes a maintenance process for the common master file. The individual master management system may include an individual master maintenance unit that performs maintenance processing of individual master files. The common master maintenance unit and the individual master maintenance unit may perform maintenance processing independently. According to this aspect, it is possible to reduce redundant maintenance work that may occur in each medical institution or medical department, and it is possible to increase the efficiency of the maintenance work.

  The common master management system may further include a notification unit that notifies the individual master management system of the update of the common master file. According to this aspect, each medical institution or medical department can recognize the update of the common master file, and can accurately grasp the status of the entire master file.

  The individual master management system includes at least one of an individual master file and a common master file with an implementation information input unit that inputs implementation information of medical practice and one or more identification information or basic information included in the input implementation information as a key. One embodiment may be further provided with an implementation information recording unit that acquires the information to be registered by converting the identification information or supplementing the basic information and recording the implementation information including the acquired information. According to this aspect, the implementation information can be easily input and recorded with reference to at least one of the individual master file and the common master file.

  The common master file may manage at least information related to medical fees. By managing items common to each medical institution such as medical fees with a common master management system, each medical institution manages highly confidential information and individual information internally, and such common matters Can be managed externally, it is possible to build a system that is easy to participate.

  Another aspect of the present invention is a common master management system. This common master management system manages a common master file related to medical information to be used in common by multiple medical institutions or medical departments outside the medical institution and is connected to the same network for each medical institution or medical department. A common master file is provided to the individual master management system provided.

  Yet another aspect of the present invention is an individual master management system. This individual master management system is provided for each medical institution or medical department, manages individual master files related to individual information to be used by that institution or department, and should be used in common by multiple medical institutions or medical departments. A common master file related to medical information is connected via a network to a common master management system that manages outside the medical institution, and the common master file is used.

  It should be noted that any combination of the above-described constituent elements and a conversion of the expression of the present invention between a method, an apparatus, a system, a recording medium, a computer program, etc. are also effective as an aspect of the present invention.

  ADVANTAGE OF THE INVENTION According to this invention, the master file regarding medical information can be managed efficiently.

  Before specifically describing the embodiment of the present invention, a medical information management system to which the present embodiment can be applied will be briefly described. The medical information management system manages schedules and implementation details of medical practices such as surgery. Specifically, input is performed in situations such as when creating a schedule for surgery or when recording the details of surgery, and the results of surgery stored as a result are used for accounting and inventory management of equipment. be able to.

  FIG. 1 shows an overall configuration of a medical information management system according to the present embodiment. The medical information management system 100 has a configuration in which a plurality of individual master management systems 130 and 131 and a common master management system 140 are connected by a WAN (Wide Area Network) such as the Internet. The individual master management systems 130 and 131 are installed in each hospital, for example. In addition, it may be installed in each department or ward even in one hospital. Conversely, one may be installed at a plurality of hospitals. For example, you may install for every administrative district, such as a municipality. In short, medical information may be set for each group to which a predetermined medical institution or medical department belongs. The common master management system 140 is installed, for example, in a company building or facility of a contractor who undertakes information management.

  Each individual master management system 130, 131 includes one or more PCs 110 and 112, portable terminals 102 to 107 that can wirelessly access access points included in the PCs 110 and 112, PCs 110 and 112, and a common master management system 140. And a server 120 that controls transmission / reception of data to / from an external system. The PCs 110 and 112 are installed in, for example, a nurse station of each medical department in a hospital, and the portable terminals 102 to 107 may be placed in each operating room or examination room, or may be carried by a nurse. A certain PC 110 or 112 may also serve as the server 120. The PC may be replaced with a computer such as a workstation or a general-purpose computer. In FIG. 1, a plurality of individual master management systems 130 and 131 are connected on the same network.

  FIG. 2 is a block diagram showing a configuration of a unit of the medical information management system 100 in the present embodiment. This configuration can be realized in hardware by any device such as CPU, memory, other LSI, display device, etc. of any server, PC, and portable terminal, and software loaded in memory, etc. Here, functional blocks realized by their cooperation are depicted. Accordingly, those skilled in the art will understand that these functional blocks can be realized in various forms by hardware only, software only, or a combination thereof.

  The individual master management system 130 installed in a medical facility includes a communication unit 20, a control unit 22, an implementation information input unit 24, a display unit 26, an implementation information recording unit 28, a notification unit 30, a maintenance unit 32, and an implementation information database. 34 and an individual master database 36. The communication unit 20 transmits / receives schedule information and implementation information of medical practices and data registered in various master files to / from the common master management system 140. The control unit 22 controls the individual master management system 130 as a whole.

  The implementation information input unit 24 is used by nurses and the like to input implementation information when performing medical treatment such as surgery. The implementation information includes information such as the identification number of the medical device, the time required for the medical practice, the name of the practitioner, the procedure name, the addition item, and the gas used. The implementation information input unit 24 may have a function of reading the identification number assigned to the equipment used by recognizing the identification information attached to the equipment used. The display unit 26 displays medical practice schedule information, implementation information, a master file, and the like.

  The implementation information recording unit 28 receives the registration of the implementation information input from the implementation information input unit 24, refers to the individual master database 36, the common master database 10, etc., and implements it as implementation information including the name of the equipment. Record in the information database 34. The maintenance unit 32 performs maintenance of the individual master database 36 when a reason for updating the master file such as personnel change occurs or periodically. Moreover, you may implement with respect to the implementation information database 34. FIG. When the maintenance unit 32 adds a master file to the individual master database 36, or changes, deletes, invalidates, or cancels the invalidation of the registered master file, the notification unit 30 notifies the common master management system 140 to that effect. Notify If the common master management system 140 is not involved in the maintenance of the individual master database 36, the notification unit 30 may not be provided.

  The implementation information database 34 accumulates and stores implementation information. The individual master database 36 manages a master file of information to be used in a medical institution or medical department where the individual master management system 130 is installed. For example, other medical institutions such as personnel information that is highly confidential and should not be leaked to the outside, the name of the ward uniquely used by the medical institution, and the medical equipment custom-made by the medical institution or department Manage unique information that is not used by

  The common master management system 140 includes a communication unit 18, a control unit 12, a maintenance unit 14, a notification unit 16, and the common master database 10. The communication unit 18 transmits / receives schedule information and implementation information of medical practice and data registered in various master files to / from the individual master management system 130. The control unit 12 controls the common master management system 140 as a whole.

  The maintenance unit 14 performs maintenance of the common master database 10 when a reason for updating the master file such as medical fee revision occurs or periodically. When the maintenance unit 14 adds a master file to the common master database 10 or changes, deletes, invalidates, or cancels the invalidation of the registered master file, the notification unit 16 notifies the individual master management system 130 to that effect. Notify When a plurality of individual master management systems 130 and 131 are connected on the same network, they may be transmitted simultaneously. The notification unit 16 may notify the individual master management systems 130 and 131 of the update of the common master database 10 by electronic mail. In addition, prior notice may be given before the maintenance is performed.

  The common master database 10 manages a master file of information to be used in common in medical institutions and medical departments where individual master management systems connected on the same network are installed. For example, it manages information related to medical fee regulations and commonly used medical equipment and drugs.

  FIG. 3 is a diagram showing master files allocated to the common master database 10 and the individual master database 36. The common master database 10 includes a medical fee master database 38, a medical equipment master database 40, and a medicine master database 42. The individual master database 36 includes a personnel master database 44, a facility equipment master database 46, a medical equipment master database 48, a medicine master database 50, a patient master database 52, and an external supplier master database 54.

  The medical fee master database 38 manages the official price of the medical fee that the medical institution receives for each treatment action such as medication, examination, and surgery. Since medical equipment and drugs are also subject to medical fees, the official price is also managed. The medical device master database 40 includes identification numbers, names, and device classifications indicating whether the device is for surgery or anesthesia, manufacturer name, product number, lot number, expiration date, unit price, medical accounting code, slip code, single item It manages information such as the device type indicating whether it is a kit or the presence or absence of designation of a specific medical material. The medicine master database 42 also manages information related to medicines, similar to the medical equipment master database 40. These medical device master database 40 and medicine master database 42 may manage all medical devices and medicines, or may selectively manage general-purpose products and those of famous manufacturers.

  The personnel master database 44 manages the personnel system of a medical institution or medical department. In addition, the name, employee code, job title, gender, date of birth, salary, etc. are managed for each medical practitioner such as a surgeon, nurse, or engineer. The facility equipment master database 46 manages facilities such as medical departments, wards, operating rooms, and medical equipment. For example, it manages information related to medical devices such as facility names and arrangements, endoscopes, and X-rays, such as lease fees and maintenance inspection costs when these devices are leased.

  The medical equipment master database 48 and the medicine master database 50 manage medical equipment and medicines that a medical institution or medical department wants to manage individually. For example, if you do not want other medical institutions to know what medical equipment or medicine you are using, or if you want to use custom-made products when only common products are managed in the common master database 10 To do. Basically, it is desirable not to overlap with those of the common master database 10 from the viewpoint of reducing the memory capacity, but there may be some overlap. Depending on the medical institution or medical department, at least one of the medical equipment master database 48 and the drug master database 50 may not be provided in the individual master database 36.

  The patient master database 52 manages identification information such as patient names and numbers, gender, date of birth, address, blood type, medical history, cases, treatment records, and the like. If a so-called electronic medical record system exists separately, it may be linked with it. The external trader master database 54 manages information related to a trader when a medical institution or a medical department outsources a part of business. For example, maintenance and repair of medical equipment and facilities, disposable products such as forceps and treatment tools, treatment of medical waste such as scalpels, ampoules, absorbent cotton, bandages, waste blood, used endoscopes and treatment tools, scalpels, When outsourcing the cleaning / disinfection / sterilization of medical equipment such as tweezers and syringes to external contractors, the names and contracts of such equipment are managed.

  In addition, the common master database 10 and the individual master database 36 appropriately sort an operation master, a cautions master, a disease name master, an operation reason master, a technique master, an addition master, a gas master, a unit master, a default execution master, an equipment kit master, and the like. Can be managed. Here, the surgical procedure master can manage the surgical procedure associated with the clinical department, and the same surgical procedure can be associated with a plurality of clinical departments. For example, surgical thoracoscopic bractomy and respiratory surgery thoracoscopic bractomy are possible. The precautions master manages precautions such as infections and drug allergies. The operation reason master can manage a fixed sentence of the operation reason. The unit master manages the units used in this system. The default execution master manages each input item at the time of execution input for each technique, for example, items for displaying a procedure, addition, medicine, equipment, and gas on the display window by default. The equipment kit master manages the equipment by making the equipment kit into an item with the equipment type of the equipment master as an equipment kit.

  Next, a processing procedure performed in the medical information management system 100 in the present embodiment will be described below. FIG. 4 is a diagram showing the procedure from the execution information input process to the recording process. These processes are performed in the individual master management system 130. The medical practitioner inputs implementation information such as patient information, surgery information, time, and medical equipment used from the implementation information input unit 24 during and after the implementation of the medical procedure (S10).

  For example, when a display unit, an input key, or an identification number reader is mounted on the mobile terminal 102, for example, the following input method is possible. A medical practitioner who recognizes the identification information affixed to the device by the identification number reader, selecting an input screen on which the schedule information registered in advance on the display unit of the portable terminal 102 is displayed with a stylus pen or the like. In this method, identification information such as an employee code and a patient identification number is key-input. Of course, you may input from PC110. In addition, when the schedule information etc. which were registered beforehand are displayed on the display part of the portable terminal 102, the items registered in the various master files managed in the common master database 10 and the individual master database 36 are changed to each item. Can be used as a selection candidate.

  The implementation information recording unit 28 searches the individual master database 36 and the common master database 10 based on the implementation information including the identification number input from the implementation information input unit 24 (S12, S14). For each item of implementation information, it may be set in advance whether the location of the master file to be referred to is the individual master database 36 or the common master database 10.

  For example, when a medical device master file is managed by the common master database 10, the identification number read from the device is transmitted to the common master management system 140 via the network. The common master management system 140 returns the equipment name corresponding to the identification number to the individual master management system 130. When the patient master file is managed by the individual master database 36, the name, sex, age, etc. corresponding to the patient identification number are acquired by referring to the master file. In addition to obtaining desired information from identification information such as an identification number, refer to the individual master database 36 or the common master database 10 for items that are missing in a certain item using the registered item as a key. And you may acquire. For example, when a patient's name is input, it may be used as a key to acquire gender and age.

  Here, when the location of the master file to be referred to is not set for each item of the implementation information, first, the individual master database 36 is searched, and when the desired information cannot be obtained therefrom, the common master is next searched. Processing such as searching the database 10 may be used. Furthermore, when desired information cannot be acquired from any database, a predetermined error process may be executed. For example, it is a process of displaying that the medical device is not registered, and recording the identification number of the device as implementation information as it is. Next, the implementation information recording unit 28 records the implementation information supplemented with information in the implementation information database 34 (S16).

  FIG. 5 shows the structure of data stored in the medical equipment master database 48. The medical device master database 48 includes at least an identification number item 72 and a device name item 74. If it is known by the standardized identification number system that the number representing the equipment name is a part having all the identification numbers, for example, 6 to 10 digits from the beginning of the number, the identification number item 72 includes that part. Only the number may be stored. The common master management system 140 extracts only the part indicating the instrument name from the read identification number, and searches the identification number item 72 based on the number, thereby storing the instrument stored in the corresponding instrument name item 74. Read the name. In addition to the equipment name item 74, the medical equipment master database 48 may have a plurality of items that store all information that can be acquired from all digits of the identification number, such as a unit price item that stores the unit price of the equipment. Good.

  FIG. 6 is a diagram showing a maintenance process procedure for the common master database 10 and the individual master database 36. The maintenance unit 14 of the common master management system 140 performs maintenance of the common master database 10 (S22) when a predetermined time arrives (Y in S20).

  Here, the predetermined time may be regular. For example, the master file managed in the common master database 10 may be updated once a week every day. In addition, it may be when the contents of the managed master file are changed, such as when the medical fee is revised or when a notification of the release of a new product is received from a medical equipment manufacturer or drug manufacturer. Further, a predetermined number of notifications, for example, 10 may be accumulated. In addition, if such notification is not made, the administrator of the common master management system 140 makes inquiries by telephone or e-mail to related places such as an organization or equipment manufacturer that allocates medical device identification numbers, or By searching a database published on the WWW (World Wide Web), it may be recognized that the contents of the master file have changed. This search may be automatically performed periodically by the system. For example, communication with an external organization information system is established when the system is started, and it is checked whether or not master information to be updated exists in the system.

  The maintenance unit 14 adds, changes, or deletes the contents of the master file of the common master database 10 manually or automatically. When performing automatically, data is downloaded from the WWW database. For example, when downloading from the information system, the master information to be updated is automatically downloaded according to the rules established by the agreement with the organization. When valid start date information accompanies that information, the master file is updated so that it becomes valid from that date. When updating the contents of such a master file, there may be a monitoring function so that duplicate items are not assigned to the master file. The notification unit 16 transmits a notification to the effect that the contents of the common master database 10 have been updated to the individual master management systems 130 and 131 (S24). This notification may be displayed on the display unit 26 of each individual master management system 130, 131 or transmitted by e-mail. Further, the update time of the contents of the common master database 10 may be notified in advance.

  Next, the maintenance unit 32 of the individual master management system 130 performs maintenance on the individual master database 36 when a predetermined time comes (Y in S26) (S28). This predetermined time is set or arrives independently from the maintenance time of the common master management system 140. Also, the maintenance timing differs for each individual master management system 130, 131. Note that the notification unit 30 may send a notification to the common master management system 140 that the contents of the individual master database 36 have been updated.

  As described above, according to the present embodiment, a master file related to medical information used by a medical institution or medical department is distributed and managed to the individual master management system 130 and the common master management system 140. Files can be managed efficiently. In other words, since the common master management system 140 collectively manages master files that do not need to be managed for each medical institution or medical department, the master files that should be held in a plurality of medical institutions or medical departments as a whole are managed. The amount of data can be reduced. In addition, even in each medical institution or medical department unit, it is possible to reduce the amount of data to be managed by its own system. As a result, since the range and types of master files to be handled are reduced, maintenance work can also be reduced. Moreover, even when viewed as a whole, it is possible to eliminate redundant maintenance work on the same data. Or at least it can be reduced.

  In addition, when the common master management system 140 updates the master file, the individual master management systems 130 and 131 notify the fact, so that each medical institution or medical department recognizes that the master file has been updated. Can be operated with a sense of security.

  In addition, each medical institution or medical department can manage information that is highly confidential to the outside, such as personnel information, by itself, so it is possible to achieve both efficiency and safety of master file management. .

  The present invention has been described based on the embodiments. This embodiment is an exemplification, and it will be understood by those skilled in the art that various modifications can be made to combinations of the respective constituent elements and processing processes, and such modifications are also within the scope of the present invention. is there.

  In the embodiment described above, the common master database 10 and the individual master database 36 are referred to when inputting or recording the execution information. In this regard, if the input implementation information includes identification information, the information may be registered in the implementation information database 34 as it is. When the hospital staff browses the implementation information on the PC 110 or the like or prints it, the control unit 22 displays the equipment name corresponding to the identification information registered in the implementation information database 34, etc. Alternatively, it may be acquired by referring to the individual master database 36 and displayed or printed. In this case, since the implementation information is registered in the implementation information database 34 in a simple data format including identification information and the like, the data capacity managed by the implementation information database 34 can be reduced.

  Further, in the embodiment, one common master management system 140 is assumed on the same network, but a plurality of common master management systems 140 may be connected. For example, a system for managing medical equipment and a system for managing medicine may be separated.

  Note that the implementation information input by the implementation information input unit 24 is stored in the implementation information database 34 as implementation information including the name of the equipment with reference to the individual master database 36 and the common master database 10. At this time, if each master management system does not exist in the individual master database 36 or the common master database 10 that the information necessary for recording the implementation information is referenced, the data necessary for reference in each master management system Is recorded in an unregistered information database (not shown) as unregistered information. The master management system extracts each record of the unregistered information table in the unregistered information database, narrows down the records in the unregistered information table based on specific items included in the record, and unregistered information with a large number of occurrences To extract. Based on the extracted unregistered information, each master management system notifies a preset notification destination by notification means such as an e-mail so as to prompt registration of the unregistered information.

  Specifically, the contents of the implementation information input by the implementation information input unit 24 are registered in the implementation information database 34. At that time, the control unit 22 corresponds to the identification number of the used equipment included in the implementation information from the equipment information table recorded in the common master database of the common master management system via the communication unit 20. Extract records. When this record is extracted, if there is no record that matches the corresponding identification number in the corresponding equipment name table, the control unit 12 of the common master management system 140 sends the identification number information to the unregistered database. Add a new record that contains it and store the information. Unregistered information with a large number of occurrences is extracted from the records accumulated in this way. That is, an identification number in which the name of the equipment is not registered although it is used is extracted. The control unit 12 extracts the extracted information, sets the email address of the administrator of the common master management system set in advance and the email address of the sales person in charge of the corresponding medical device, and notifies the email prompting registration To do.

  Thereby, although it is being used, it is possible to easily prompt the update of the information on the medical device that is not registered in the master table. Similarly, it may be performed in the individual master database of the individual master management system. Moreover, it is not limited to medical equipment information, What is necessary is just the data contained in an individual master database or a common master database.

It is a figure showing the whole medical information management system composition concerning an embodiment of the invention. It is a block diagram which shows the structure of a certain unit of the medical information management system in this Embodiment. It is a figure which shows the master file allocated to the common master database and individual master database in this Embodiment. It is a figure which shows the procedure of the recording process from the input process of the implementation information in this Embodiment. It is a figure which shows the structure of the data memorize | stored in the medical device master database in this Embodiment. It is a figure which shows the procedure of the maintenance process of the common master database and individual master database in this Embodiment.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 Common master database, 14 Maintenance part, 16 Notification part, 24 Implementation information input part, 28 Implementation information recording part, 30 Notification part, 32 Maintenance part, 34 Implementation information database, 36 Individual master database, 130, 131 Individual master management system 140 Common master management system.

Claims (7)

A common master management system for managing a common master file related to medical information to be used in common by a plurality of medical institutions or medical departments outside the medical institution;
An individual master management system that is provided for each medical institution or medical department and manages an individual master file related to individual information to be used in the institution or department;
The individual master management system can use the common master file via a network. The common master management system includes a common master maintenance unit that performs maintenance processing of the common master file,
The individual master management system includes an individual master maintenance unit that performs maintenance processing of the individual master file,
The medical information management system according to claim 1, wherein the common master maintenance unit and the individual master maintenance unit independently perform maintenance processing.   The medical information management system according to claim 2, wherein the common master management system further includes a notification unit that notifies the update of the common master file to the individual master management system. The individual master management system includes an implementation information input unit that inputs implementation information of medical practice;
Converting the identification information with reference to at least one of the individual master file and the common master file using one or more identification information or basic information included in the input implementation information as a key, or the basic The medical information management according to any one of claims 1 to 3, further comprising an implementation information recording unit that acquires information to be registered by supplementing the information and records implementation information including the information. system.   The medical information management system according to any one of claims 1 to 4, wherein the common master file manages at least information related to medical fees.   A common master file related to medical information that should be used in common by multiple medical institutions or medical departments is managed outside the medical institution, connected to the same network, and an individual master management system provided for each medical institution or medical department. A common master management system that provides the common master file.   Manages individual master files related to individual information that should be used in each medical institution or department, and should be used in common by multiple medical institutions or departments. An individual master management system which is connected to a common master management system managed outside a medical institution via a network and uses the common master file.

Images