JP2009175863A - Medical care information display program and medical care information display device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To efficiently make a user input a technical term related to another medical care department by making a dictionary optimum for the user be started. <P>SOLUTION: An electronic medical chart client 200 receives a user ID and a medical care department code for identifying a medical care department wherein a patient is examined, refers to a user management table 250d wherein the user ID and the belonging medical care department code are associated and stored, acquires the belonging medical care department code corresponding to the user ID, compares the medical care department code of the patient and the belonging medical care department code of the user, starts a personal dictionary corresponding to the user ID when they coincide, and starts a medical care department common dictionary when they do not coincide. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a medical information display program and a medical information display device for executing a dictionary activation process in an electronic medical record system for inputting information to an electronic medical record.

  In recent years, doctors and the like (hereinafter referred to as users) who examine a patient use an electronic medical record system in order to efficiently manage various types of information related to the patient (diagnosis history, disease record, etc.). In addition, this electronic medical record system may have a dictionary function that includes multiple technical terms, and the user inputs technical terms into the patient's medical record by selecting technical terms contained in such a dictionary. This saves the user from having to input difficult technical terms directly.

  This dictionary function can use, for example, the techniques disclosed in Patent Documents 1 and 2, and provides the user with an optimal dictionary, thereby improving user convenience. For example, when a user (internal medicine doctor) inputs information into a medical record of an internal medicine patient, a dictionary optimized for internal medicine, which is a medical department to which the user belongs, is provided to the user, and the user Using such a dictionary, various technical terms can be entered in the medical chart.

JP-A-6-131328 JP 54-78042 A

  Usually, in a hospital, each user inputs information on a patient in the department at the terminal of the department to which the user belongs. However, in an emergency, a user examines a patient who is not the department to which he belongs and enters information related to this patient into a medical record (for example, a medical department user examines a surgical patient, There is a case where such patient information is input to a medical chart.

  In this case, the user cannot use a dictionary that is an alternative to the dictionary optimized for the department to which he belongs, so he can efficiently input technical terms related to other departments. There was a problem that the conventional dictionary function was not easy to use.

  The present invention has been made to solve the above-described problems caused by the prior art, and allows a user to activate an optimal dictionary and efficiently input technical terms relating to other medical departments. It is an object to provide a medical information display program and a medical information display device.

  In order to solve the above-described problems and achieve the object, the medical information display program uses a computer to receive a first receiving means for receiving a user ID and a medical department identification ID for identifying a medical department for examining a patient. Two acquisition means, an acquisition means for acquiring a department ID corresponding to the user ID received by the first reception means with reference to a user table stored in association with a user ID and a clinical department identification ID And the department identification ID received by the second receiving means and the department ID acquired by the acquisition means, and if they match, activate the conversion dictionary corresponding to the user ID, If they do not match, it is required to function as an activation unit that activates the common conversion dictionary.

  In the medical information display program, the computer stores management data for managing the conversion dictionary of the user ID corresponding to the common conversion dictionary in a storage device, and the conversion dictionary of the user ID is updated. It is a requirement that the computer further function as update means for updating the common conversion dictionary based on the management data.

  The medical information display device includes a first receiving unit that receives a user ID, a second receiving unit that receives a medical department identification ID that identifies a medical department that examines a patient, a user ID, and a clinical department identification ID. Referring to the user table stored in association with each other, acquisition means for acquiring a department ID corresponding to the user ID received by the first reception means, and clinical department identification received by the second reception means An activation unit that compares the ID with the department ID acquired by the acquisition unit and activates the conversion dictionary corresponding to the user ID if they match, and activates the common conversion dictionary if they do not match It is a requirement that

  According to this medical information display program, a user table that receives a user ID, receives a medical department identification ID that identifies a medical department that examines a patient, and stores the user ID and the clinical department identification ID in association with each other is stored. Refers to and acquires the department ID corresponding to the user ID, compares the patient's department identification ID with the user department ID, and activates the conversion dictionary corresponding to the user ID if they match. If they do not match, the common conversion dictionary is activated, so that it is possible to prepare a dictionary corresponding to the medical examination department of the patient in charge of the user, thereby reducing the user's stress.

  Also, according to the medical information display program, when the user ID conversion dictionary is updated, the common conversion dictionary is updated based on the management data, so that the clinical department common dictionary data is updated in an optimal form. I can do it.

  Exemplary embodiments of a medical information display program and a medical information display device according to the present invention will be described below in detail with reference to the accompanying drawings.

  First, the outline | summary and characteristic of the medical treatment information display system concerning a present Example are demonstrated. FIG. 1 is a diagram for explaining the outline and features of the medical care information display system according to the present embodiment. The medical information display system according to the present embodiment compares a medical department to which a doctor who examines a patient (hereinafter referred to as a user) belongs and a medical department where the patient is examined, and based on the comparison result, Start by changing the dictionary provided to the user.

  As shown in FIG. 1, for example, when a user (doctor A) whose medical department belongs to an internal medicine department examines a patient in the internal medicine, a personal dictionary corresponding to the user (optimized for the doctor A) (Personal dictionary) is activated to support the work of the user inputting technical terms in the patient's chart. In the example shown in FIG. 1, when a user inputs a technical term starting with “ka” in the past history frame, the technical term starting with “ka” registered in the personal dictionary (1 hay fever, 2 carini pneumonia,・ ・ ・) Is displayed and the user's input work is supported.

  On the other hand, if the department of surgery to which the department belongs is a surgeon (doctor B) who examines a patient in internal medicine, instead of a personal dictionary (personal dictionary optimized for the surgeon) corresponding to the user In addition, a diagnosis department common dictionary (for example, a dictionary including technical terms commonly used by each user of internal medicine) is activated to support the work of the user inputting technical terms into the patient's chart. In the example shown in FIG. 1, when a user inputs a technical term starting with “ka” in the past history frame, the technical term starting with “ka” registered in the clinical department common dictionary (1 carini pneumonia, 2 pollen) 3), 3 hyperventilation syndrome, 4 irritable enteritis, etc.) are displayed to support user input.

  In addition, when the user (surgeon B) of surgery belongs to the department to which the surgery belongs, the personal dictionary corresponding to the user (personal dictionary optimized for the surgeon B) is activated when the patient is examined. Thus, the user supports the operation of inputting technical terms in the patient's chart (see the lower right in FIG. 1).

  As described above, the medical information display system according to the present embodiment compares the clinical department to which the user belongs and the clinical department where the patient is examined, activates the personal dictionary or the common clinical department dictionary, and allows the user to Since the operation of inputting technical terms is supported, a dictionary corresponding to the consultation department of the patient in charge of the user can be prepared, and the stress on the user can be reduced.

  Next, the system configuration of the medical care information display system according to the present embodiment will be described. FIG. 2 is a block diagram illustrating the system configuration of the medical care information display system according to the present embodiment. As shown in the figure, this medical information display system includes an electronic medical record server 100 and an electronic medical record client 200, and the electronic medical record server 100 and the electronic medical record client 200 are connected to each other via a network 50.

  The electronic medical record server 100 is a device that manages information of a user's personal dictionary (hereinafter referred to as user personal dictionary data) and a medical department common dictionary (hereinafter referred to as medical department common dictionary data) of each clinical department, and an electronic medical chart client In response to a request from 200, user personal dictionary data and clinical department common dictionary data are transmitted to the electronic medical chart client 200.

  The electronic medical record client 200 acquires and stores the user personal dictionary data and the clinical department common dictionary data from the electronic medical record server 100, and when the user inputs information to the patient's medical record, the medical care to which the user belongs This is a device that compares a department and a medical department that a patient visits and activates a personal dictionary or a common clinical department dictionary according to a comparison result to support a user's input operation.

  Next, the configuration of the electronic medical record server 100 shown in FIG. 2 will be described. FIG. 3 is a functional block diagram illustrating the configuration of the electronic medical record server 100 according to the present embodiment. As shown in the figure, the electronic medical record server 100 includes an input unit 110, an output unit 120, a communication control IF unit 130, an input / output control IF unit 140, a storage unit 150, and a control unit 160. Configured. Other configurations are the same as those of the electronic medical record server in the well-known electronic medical record system, and thus the description thereof is omitted here.

  Among these, the input unit 110 is an input means for inputting various types of information, and includes a keyboard, a mouse, a microphone, and the like, and is stored in the storage unit 150 (for example, user personal dictionary data 150a, clinical department common dictionary data 150b). Various information to be stored is received and input from an administrator or the like. A monitor (output unit 120) described later also realizes a pointing device function in cooperation with the mouse.

  The output unit 120 is an output unit that outputs various types of information, and includes a monitor (or display, touch panel), a speaker, and the like. For example, the storage unit 150 (for example, user personal dictionary data 150a, clinical department common dictionary data) Various information stored in 150b) is output.

  The communication control IF unit 130 is a unit that mainly controls communication with the electronic medical chart client 200. The input / output control IF unit 140 is a unit that controls input / output of data by the input unit 110, the output unit 120, the communication control IF unit 130, the storage unit 150, and the control unit 160.

  The storage unit 150 is a storage unit that stores data and programs necessary for various types of processing by the control unit 160. In particular, as shown in FIG. 3, the user personal dictionary data 150a is closely related to the present invention. And clinical department common dictionary data 150b.

  Among these, the user personal dictionary data 150a is data for storing information of the personal dictionary for each user. FIG. 4 is a diagram showing an example of the data structure of the user personal dictionary data 150a. As shown in the figure, the user personal dictionary data 150a includes a user ID, a clinical department code, a reading pseudonym, a sequence number, a registration date, and a registration word.

  Among these, the user ID is identification information for identifying the user. The medical department code is identification information for identifying a medical department. For example, a medical code “10” indicates internal medicine, and a medical code “20” indicates surgery. The reading kana is information indicating the initial letter of the technical term. For example, the reading of the technical term “hay fever” is “ka”.

  The sequence number is information indicating the priority order of technical terms. The smaller the sequence number, the higher the priority and the priority is displayed to the user using the personal dictionary. The registration date / time is information indicating the date / time when the information of the corresponding line was registered. The registered word is information indicating a registered technical term.

  As shown in FIG. 4, here, for convenience of explanation, various types of information (diagnosis department code, reading kana, sequence number, registration date, registration word, etc.) corresponding to each user ID are stored together. However, various types of information may be stored in a plurality of directories separately for each user ID. For example, the directory structure in which the electronic medical record server 100 stores various information of the user ID “MD0000000001” of the user personal dictionary data 150a is “C: \ personal dictionary \ MD0000000001 \”.

  The clinical department common dictionary data 150b is data for storing information of a common medical department dictionary that can be used in common for each clinical department. FIG. 5 is a diagram illustrating an example of a data structure of the clinical department common dictionary data 150b. As shown in the figure, the medical department common dictionary data 150b includes a medical department code, a reading pseudonym, a sequence number, a registration date and a registration word.

  Here, the explanation of the examination department code, reading kana, sequence number, registration date / time, and registered word is the explanation of the examination department code, reading kana, sequence number, registration date / time, and registered word explained in the user personal dictionary data 150a. It is the same.

  Note that the clinical department common dictionary data 150b registers various types of information (diagnosis department code, reading pseudonym, sequence number, registration date, registration word, etc.) for each clinical department. The example shown in FIG. 5 has “internal medicine” common department data dictionary data whose medical code is “10” and “surgical” medical department common dictionary data whose medical code is “20”.

  Also, as shown in FIG. 5, here, for convenience of explanation, various types of information (reading pseudonym, sequence number, registration date, registration word, etc.) corresponding to each clinical department code (clinical department) are stored together. However, various types of information may be stored in a plurality of directories separately for each department code. For example, the directory structure in which the electronic medical record server 100 stores various information of the clinical department code “10” of the clinical department common dictionary data 150b is “C: \ clinical department common dictionary \ 10 \”.

  The control unit 160 has an internal memory for storing programs and control data that define various processing procedures, and is a control means for executing various processes by these, and is particularly closely related to the present invention. Includes a data management processing unit 160a.

  The data management processing unit 160a is a means for managing the user personal dictionary data 150a and the diagnosis department common dictionary data 150b stored in the storage unit 150. Specifically, the data management processing unit 160a outputs user personal dictionary data 150a or clinical department common dictionary data 150b in response to a data request from the electronic medical record client 200.

  The data request for the user personal dictionary data 150a includes a user ID. When the data request is received by the data management processing unit 160a, the user ID included in the data request is compared with the user personal dictionary data 150a, and the user personal dictionary data 150a corresponding to the user ID is compared. Is output to the electronic medical chart client 200. Here, when the data corresponding to the user ID does not exist in the user personal dictionary data 150a, the user personal dictionary data 150a is information indicating that the user personal dictionary data corresponding to the user ID does not exist. Is output.

  In addition, when the data management processing unit 160a acquires update data of the user personal dictionary data 150a (user personal dictionary data transmitted from the electronic medical record client 200; hereinafter, personal dictionary update data), the acquired personal The user personal dictionary data 150a is updated with the dictionary update data.

  The personal dictionary update data includes a user ID, and the data management processing unit 160a updates the user personal dictionary data 150a corresponding to the user ID with the personal dictionary update data.

  In addition, when the data management processing unit 160a acquires update data of the clinical department common dictionary data 150b (user personal dictionary data transmitted from the electronic medical record client 200; hereinafter, common dictionary update data), the acquired common data The medical department common dictionary data 150b is updated with the dictionary update data.

  The common dictionary update data includes the clinical department code, and the data management processing unit 160a uses the data corresponding to the clinical department code included in the common dictionary update data in the clinical department common dictionary data 150b. Update with dictionary update data.

  Next, the configuration of the electronic medical chart client 200 shown in FIG. 2 will be described. FIG. 6 is a functional block diagram illustrating the configuration of the electronic medical record client 200 according to the present embodiment. As shown in the figure, the electronic medical chart client 200 includes an input unit 210, an output unit 220, a communication control IF unit 230, an input / output control IF unit 240, a storage unit 250, and a control unit 260. Configured. The other configuration is the same as that of an electronic medical record client in a well-known electronic medical record system, and thus description thereof is omitted here.

  Among these, the input unit 210 is an output unit that outputs various types of information, and includes a monitor (or display, touch panel), a speaker, and the like. For example, the storage unit 250 (for example, default dictionary data 250a, user personal dictionary) Data 250b, clinical department common dictionary data 250c, user management table 250d, patient management table 250e, medical department master data 250f, and target user management data 250g) are received from the user and input. A monitor (output unit 220) described later also realizes a pointing device function in cooperation with the mouse.

  The output unit 220 is an output unit that outputs various types of information, and includes a monitor (or display, touch panel), a speaker, and the like. For example, the storage unit 250 (for example, default dictionary data 250a, user personal dictionary data 250b, The medical department common dictionary data 250c, the user management table 250d, the patient management table 250e, the medical department master data 250f, and the target user management data 250g) are output.

  The communication control IF unit 230 is a unit that mainly controls communication with the electronic medical record server 100. The input / output control IF unit 240 is means for controlling input / output of data by the input unit 210, the output unit 220, the communication control IF unit 230, the storage unit 250, and the control unit 260.

  The storage unit 250 is a storage unit that stores data and programs necessary for various types of processing by the control unit 260. In particular, as closely related to the present invention, as shown in FIG. User personal dictionary data 250b, clinical department common dictionary data 250c, a user management table 250d, a patient management table 250e, clinical department master data 250f, and target user management data 250g are provided.

  Of these, the default dictionary data 250a is different from the user personal dictionary data optimized for the user or the clinical department common dictionary data set for each clinical department, for example, general terms (for example, medical terms). ) (Default dictionary file common to all electronic medical record clients). Note that the default dictionary data 250a is stored in a predetermined directory. For example, the directory structure in which the electronic medical record client 200 stores the default dictionary data 250a is “C: \ default dictionary \”.

  The user personal dictionary data 250b is data for storing information of a personal dictionary for each user. The data structure of the user personal dictionary data 250b is the same as the data structure of the user personal dictionary data 150a shown in FIG. 4 (however, it has only various information corresponding to a single user ID). The description is omitted. The electronic medical record client 200 may store the user personal dictionary data 250b in a predetermined directory. For example, the directory structure in which the electronic medical record client 200 stores the user personal dictionary data 250b is “C: \ personal dictionary \”.

  The diagnosis department common dictionary data 250c is data for storing information of a diagnosis department common dictionary that can be used in common for each diagnosis department. The data structure of the clinical department common dictionary data 250c is the same as the data structure of the clinical department common dictionary data 150b shown in FIG. The electronic medical record client 200 may store various types of information in a plurality of directories by dividing the department common dictionary data 250c for each department code. For example, the structure of the directory in which the electronic medical record client 200 stores various information of the clinical department code “10” of the clinical department common dictionary data 250c is “C: \ clinical department common dictionary \ 10 \”.

  The user management table 250d is data that stores various types of information for users. FIG. 7 is a diagram illustrating an example of the data structure of the user management table 250d. As shown in the figure, the user management table 250d includes a user ID, a password, a job type, a user name, a department department code, and a date of birth.

  Here, the belonging department code is information for identifying the department to which the user belongs. For example, when the belonging department code is “10”, the department to which the user belongs is “internal department”, and when the belonging department code is “20”, the department to which the user belongs The department is "Surgery".

  The patient management table 250e is data that stores various types of information about the patient. FIG. 8 is a diagram illustrating an example of a data structure of the patient management table 250e. As shown in the figure, the patient management table 250e includes a patient ID for identifying a patient, a patient name, a sex, and an age.

  The clinical department master data 250f is data that stores a medical department code and a department name in association with each other. FIG. 9 is a diagram illustrating an example of a data structure of the clinical department master data 250f. As shown in the figure, the clinical department master data 250f associates a clinical department code with a clinical department name. For example, the department code “10” corresponds to the department name “internal medicine”, and the department code “20” corresponds to the department name “surgery”.

  The target user management data 250g is data for managing the user ID of the user personal dictionary data included in the medical department common dictionary data 250c. FIG. 10 is a diagram illustrating an example of the data structure of the target user management data 250g. As shown in the figure, the target user management data 250g stores a medical department code and a user ID in association with each other. For example, the data of the user personal dictionary data 250b corresponding to the user ID “MD0000000001” is associated with the clinical department of the clinical department code “10”, that is, the medical department common dictionary of “internal medicine”. Further, the user with the user ID “MD0000000122” is associated with the clinical department of the clinical department code “20”, that is, the clinical department common dictionary of “surgery”.

  Therefore, when the user personal dictionary data with the user ID “MD0000000001” is updated, the clinical department common dictionary data with the clinical department code “10” is updated. When the user personal dictionary data with the user ID “MD0000000122” is updated, the clinical department common dictionary data with the medical department code “20” is updated.

  Returning to the description of FIG. 6, the control unit 260 is a control unit that has an internal memory for storing programs and control data that define various processing procedures, and executes various processes using these programs. As closely related to the invention, a startup processing unit 260a, a login processing unit 260b, an upload processing unit 260c, and an FEP processing unit 260d are provided.

  Among these, the startup processing unit 260a is a means for executing an initial process when the electronic medical chart client 200 is started. Specifically, the initial process executed by the startup processing unit 260a will be described. The startup processing unit 260a accesses the electronic medical record server 100 and requests the clinical department common dictionary data 150b. When the medical department common dictionary data 150b is acquired, the startup processing unit 260a stores the acquired medical department common dictionary data 150b as the medical department common dictionary data 250c in the storage unit 250 (specified directory). To do.

  The login processing unit 260b is a means for executing various processes (user login process and patient information input process) resulting from login when a login request from a user or a patient login request is received. First, after describing the user login process executed by the login processing unit 260b, the patient information input process will be described.

(User login process)
First, the login processing unit 260b outputs a user login screen to the output unit 220 and prompts the user to input a user ID and password. FIG. 11 is a diagram illustrating an example of a login screen for the user.

  In this case, the user uses the input unit 210 to input the user ID and password in the user ID and password fields of the login screen. When the login processing unit 260b acquires the user ID and password from the input unit 210, the login processing unit 260b accesses the user management table 250d, and the user name and department department code corresponding to the acquired combination of user ID and password. , Get a job title.

  Then, the login processing unit 260b outputs information on the user name, the belonging department, and the occupation type on the login screen (see the right side of FIG. 11). Here, the information of the belonging department can be specified by comparing the belonging department code and the department master data 250f. If the combination of the user ID and password acquired from the input unit 210 does not exist in the user management table 250d, the login processing unit 260b outputs information indicating that the login has failed on the login screen.

  Subsequently, the login processing unit 260b transmits the data request storing the user ID acquired from the input unit 210 at the time of login to the electronic medical record server 100, whereby the user personal dictionary data corresponding to the user ID is electronically stored. Obtained from the chart server 100.

  When the login processing unit 260b acquires user personal dictionary data corresponding to the user ID (in other words, when the user personal dictionary data corresponding to the user ID exists in the electronic medical record server 100), A command for enabling the personal dictionary is output to the FEP processing unit 260d.

  On the other hand, the login processing unit 260b cannot acquire the user personal dictionary data corresponding to the user ID (in other words, the user personal dictionary data corresponding to the user ID does not exist in the electronic medical record server 100). Outputs, to the FEP processing unit 260d, a command for validating the department common dictionary to which the user belongs using the department code as a key.

(Patient information input process)
First, the login processing unit 260b outputs a patient information input screen to the output unit 220, and prompts the user to input a patient ID and a department. FIG. 12 is a diagram illustrating an example of a patient information input screen.

  In this case, the user uses the input unit 210 to input the patient ID and the department (patient department to be consulted by the patient) on the patient information input screen (the department code may be directly input). When the log-in processing unit 260b obtains the patient ID and the department from the input unit 210, the log-in processing unit 260b accesses the patient management table 250e, obtains information on the patient name, gender, and age corresponding to the patient ID. And obtain information on patient name, gender, and age.

  Subsequently, the login processing unit 260b accesses the clinical department master data 250f to determine the patient's clinical department code. For example, when the department is “internal medicine”, the department code is “10”, and when the department is “surgery”, the department code is “20”.

  The login processing unit 260b compares the user's belonging department code acquired from the input unit 210 with the patient's department code during the user login process to determine whether the values match, and the values do not match. In this case, a command for enabling the clinical department common dictionary is output to the FEP processing unit 260d.

  Further, the login processing unit 260b associates the user ID and the patient's clinical department code with each other when the values of the user's belonging department code and the patient's medical department code acquired from the input unit 210 do not match. Register in the target user management data 250g.

  The upload processing unit 260c is means for uploading the user personal dictionary data 250b to the electronic medical record server 100 when the user logs off. Specifically, when the upload processing unit 260c acquires a logoff request from the input unit 210, the upload processing unit 260c outputs the user ID of the user and the user personal dictionary data 250b to the electronic medical record server 100 as personal dictionary update data. To do.

  Also, the upload processing unit 260c determines whether the user personal dictionary data 250b with the user ID corresponds to the medical department common dictionary data 250c based on the target user management data 250g. For example, when the user ID is “MD0000000001”, it is determined that the user personal dictionary data 250b of the user ID corresponds to the medical department common dictionary data of the medical department code “10 (internal medicine)”. To do.

  If the upload processing unit 260c determines that the user personal dictionary data 250b of the user ID corresponds to the medical department common dictionary data 250c, the upload processing unit 260c determines the medical department code (in the target user management data 250g, the user The medical department code associated with the ID) and the user personal dictionary data are output to the electronic medical record server 100 as common dictionary update data. Also, the upload processing unit 260c outputs a command for enabling the default dictionary to the FEP processing unit 260d.

  The FEP processing unit 260d is a means for executing various processes related to data input of an electronic medical record. In particular, as closely related to the present invention, a default dictionary, a personal dictionary, or a medical department common dictionary is started. Thus, the user supports the operation of inputting technical terms into the electronic medical record via the input unit 210 (see FIG. 1).

  The FEP processing unit 260d holds a use dictionary management table for managing which of the default dictionary, personal dictionary, and clinical department common dictionary is used. FIG. 13 is a diagram illustrating an example of a usage dictionary management table.

  In FIG. 13, the default dictionary flag is information indicating whether to activate the default dictionary. When the default dictionary flag is “ON”, the default dictionary is activated. The personal dictionary flag is information indicating whether or not to activate the personal dictionary. When the personal dictionary flag is “ON”, the personal dictionary is activated. The medical department common dictionary flag is information indicating whether or not to start the medical department common dictionary. When the medical department common dictionary flag is “ON”, the medical department common dictionary is started.

  When the FEP processing unit 260 d receives a command for enabling the default dictionary, the FEP processing unit 260 d sets the default dictionary flag to “on” and sets other flags to “off”. When the FEP processing unit 260d receives a command for enabling the personal dictionary, the FEP processing unit 260d sets the personal dictionary flag to “on” and sets other flags to “off”. Further, when the FEP processing unit 260d receives a command for validating the medical department common dictionary, the FEP processing unit 260d sets the medical department common dictionary flag to “on” and other flags to “off”.

  The above commands are based on, for example, IME (Registered Commercial Code) 2007, and the command to enable the default dictionary is “IMJPUEXC.EXE SETCUSTOMDICTPATH C: \ default dictionary \ IMJP12 \ imjp12cu.dic” The command to enable the dictionary is `` IMJPUEXC.EXE SETCUSTOMDICTPATH C: \ Personal dictionary \ IMJP12 \ imjp12cu.dic ''. Common dictionary \ 10 \ IMJP12 \ imjp12cu.dic ".

  When the FEP processing unit 260d receives a request for starting a dictionary from the user via the input unit 210, the FEP processing unit 260d uses the default dictionary, the personal dictionary, or the clinical department common dictionary based on the use dictionary management table. Start up.

  Specifically, the FEP processing unit 260d activates a default dictionary based on the default dictionary data 250a when the default dictionary flag in the use dictionary management table is “ON”.

  The FEP processing unit 260d activates a personal dictionary based on the user personal dictionary data 250b when the personal dictionary flag in the use dictionary management table is “ON”. Further, in the process of using the personal dictionary by the user, when a new technical term is registered or deleted in the personal dictionary, the FEP processing unit 260d determines whether the user has registered or deleted the technical term. The personal dictionary data 250b is updated.

  In addition, when the medical department common dictionary flag in the use dictionary management table is “ON”, the FEP processing unit 260d activates the medical department common dictionary based on the medical department common dictionary data 250c.

  Next, various processing procedures of the electronic medical record client 200 according to the present embodiment will be described. First, the processing procedure of the electronic medical chart client starting process will be described. FIG. 14 is a flowchart showing the processing procedure of the electronic medical chart client activation processing.

  As shown in FIG. 14, when the electronic medical chart client 200 is activated (step S101), the activation processing unit 260a downloads all the clinical department common dictionary data (step S102), and stores the clinical department common dictionary data in the directory. (Step S103).

  Next, a processing procedure for user login processing will be described. FIG. 15 is a flowchart illustrating a processing procedure of user login processing. As shown in the figure, in the electronic medical record client 200, the login processing unit 260b receives the user ID and password (step S201), accesses the user management table 250d, and the user corresponding to the user ID and password. The name, department, department, and department code are acquired (step S202).

  Then, the login processing unit 260b outputs information on the user name, department, department, and occupation type to the display (output unit 220) (step S203), downloads the user personal dictionary data from the electronic medical record server 100, and stores it in the directory. Store (step S204).

  Subsequently, the login processing unit 260b determines whether or not user personal dictionary data corresponding to the user ID exists (step S205). If the user personal dictionary data exists (step S206, Yes), the personal dictionary is validated. A command to be issued is issued (step S207). On the other hand, if the user personal dictionary data corresponding to the user ID does not exist (No in step S206), a command for validating the department common dictionary belonging to the user is issued using the department code as a key. (Step S208).

  Next, a processing procedure of patient information input processing will be described. FIG. 16 is a flowchart showing a processing procedure of patient information input processing. As shown in the figure, in the electronic medical record client 200, the log-in processing unit 260b accepts a patient ID (step S301) and accepts a medical department that the patient consults (step S302).

  Then, the patient management table 250e is accessed to acquire information on the patient name, sex, and age corresponding to the patient ID (step S303), and the login processing unit 260b displays the patient name, sex, The age information is output (step S304), the clinical department master data 250f is accessed, and the clinical department code of the clinical department is determined (step S305).

  Subsequently, the login processing unit 260b compares the user's department code and the patient's department code to determine whether or not they match (step S306). If they do not match (step S307, No) ) A command for validating the clinical department common dictionary is issued using the patient's clinical department code as a key (step S308). On the other hand, if the user's department code matches the patient's department code (step S307, Yes), the process ends.

  Next, the processing procedure of the upload process will be described. FIG. 17 is a flowchart illustrating a processing procedure of upload processing. As shown in the figure, in the electronic medical record client 200, the upload processing unit 260c receives logoff (step S401), acquires the user personal dictionary data 250b corresponding to the user ID, and stores the storage unit of the electronic medical record server 100. Upload to 150 (user personal dictionary data 150a) (step S402).

  Then, the upload processing unit 260c determines whether or not the user of the user ID is a user who uses the medical department common dictionary (step S403), and when using it (step S404, Yes), The user personal dictionary data 250b corresponding to the user ID is uploaded to the storage unit 150 (clinical department common dictionary data 150b) of the electronic medical record server 100 (step S405), and a command for enabling the default dictionary is output (step S405). S406).

  On the other hand, when the user with the user ID is not a user using the medical department common dictionary (step S404, No), the process proceeds to step S406.

  As described above, in the medical care information display system according to the present embodiment, the electronic medical record client 200 receives the user ID and the clinical department code for identifying the medical department that examines the patient, and the user ID and the belonging medical department. Refer to the user management table 250d that stores the code in association with each other, obtain the department code corresponding to the user ID, compare the patient department code with the user department code, If they match, the personal dictionary corresponding to the user ID is activated, and if they do not match, the clinical department common dictionary is activated, so that a dictionary corresponding to the patient's medical examination department in charge of the user can be prepared, User stress can be reduced.

  In the medical information display system according to the present embodiment, the electronic medical record client 200 updates the medical department common dictionary data 150b of the electronic medical record server 100 based on the target user management data 250g. It can be updated in an optimal manner.

  Although not described in the above embodiment, the data management processing unit 160a displays a dictionary storage position designation screen as shown in FIG. 18, and stores the user personal dictionary data 150a and the clinical department common dictionary data 150b. The user can specify the storage location. FIG. 18 is a diagram illustrating an example of a dictionary storage position designation screen.

  By the way, among the processes described in the present embodiment, all or a part of the processes described as being automatically performed can be manually performed, or the processes described as being performed manually can be performed. All or a part can be automatically performed by a known method. In addition, the processing procedure, control procedure, specific name, and information including various data and parameters shown in the above-described document and drawings can be arbitrarily changed unless otherwise specified.

  Each component of the electronic medical record server 100 shown in FIG. 3 and the electronic medical record client 200 shown in FIG. 6 is functionally conceptual and does not necessarily have to be physically configured as shown. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. Furthermore, each processing function performed by each device may be realized by a CPU and a program that is analyzed and executed by the CPU, or may be realized as hardware by wired logic.

  FIG. 19 is a diagram illustrating a hardware configuration of the computer 30 included in the electronic medical record server 100 according to the embodiment. As shown in FIG. 19, the computer (electronic medical record server) 30 includes an input device 31, a monitor 32, a RAM (Random Access Memory) 33, a ROM (Read Only Memory) 34, and a medium reading device 35 that reads data from a storage medium. A communication device 36 for transmitting / receiving data to / from other devices, a CPU (Central Processing Unit) 37, and an HDD (Hard Disk Drive) 38 are connected by a bus 39.

  The HDD 38 stores a management processing program 38b that exhibits the same function as that of the electronic medical record server 100 described above. When the CPU 37 reads and executes the management processing program 38b, the management processing process 37a is activated. Here, the management processing process 37a corresponds to the data management processing section 160a shown in FIG.

  The HDD 38 stores various data 38a corresponding to the user personal dictionary data 150a and the clinical department common dictionary data 150b. The CPU 37 reads out various data 38 a stored in the HDD 38, stores it in the RAM 33, and performs data management using the various data 33 a stored in the RAM 33.

  FIG. 20 is a diagram illustrating a hardware configuration of the computer 40 configuring the electronic medical record client 200 according to the embodiment. As shown in FIG. 20, the computer (electronic medical record client) 40 includes an input device 41, a monitor 42, a RAM (Random Access Memory) 43, a ROM (Read Only Memory) 44, and a medium reading device 45 that reads data from a storage medium. A communication device 46 that transmits and receives data to and from other devices, a CPU (Central Processing Unit) 47, and an HDD (Hard Disk Drive) 48 are connected by a bus 49.

  The HDD 48 stores an electronic medical chart client processing program 48b that exhibits the same functions as those of the electronic medical chart client 200 described above. When the CPU 47 reads out and executes the electronic medical chart client processing program 48b, the electronic medical chart client processing process 47a is activated. Here, the electronic medical record client processing process 47a corresponds to the startup processing unit 260a, the login processing unit 260b, the upload processing unit 260c, and the FEP processing unit 260d illustrated in FIG.

  Further, the HDD 48 stores the default dictionary data 250a, user personal dictionary data 250b, clinical department common dictionary data 250c, user management table 250d, patient management table 250e, clinical department master data 250f, and target user management data 250g in FIG. The various data 48a corresponding to is stored. The CPU 47 reads out various data 48 a stored in the HDD 48, stores it in the RAM 43, and determines the position of the search object using the various data 43 a stored in the RAM 43.

  Incidentally, the management processing program 38b shown in FIG. 19 and the electronic medical record client processing program 48b shown in FIG. 20 are not necessarily stored in the HDDs 38 and 48 from the beginning. For example, a “portable physical medium” such as a flexible disk (FD), a CD-ROM, a DVD disk, a magneto-optical disk, or an IC card inserted into a computer, or a hard disk drive (HDD) provided inside or outside the computer. Management processing program 38b, electronic medical record client processing program, etc., to “fixed physical medium”, and “other computer (or server)” connected to the computer via a public line, Internet, LAN, WAN, etc. 48b may be stored, and the computer may read out and execute the management processing program 38b and the electronic medical record client processing program 48b from these.

  The following additional notes are disclosed with respect to the embodiments including the above-described examples.

(Appendix 1)
First receiving means for receiving a user ID;
A second receiving means for receiving a department identification ID for identifying a department that examines a patient;
An acquisition means for acquiring a department ID corresponding to the user ID received by the first reception means with reference to a user table storing the user ID and the department identification ID in association with each other;
The medical department identification ID received by the second reception means is compared with the department ID acquired by the acquisition means, and if they match, the conversion dictionary corresponding to the user ID is activated and matches. If not, an activation means for activating the common conversion dictionary;
A medical information display program characterized by being made to function.

(Additional remark 2) The said computer memorize | stores the management data which manage the conversion dictionary of user ID corresponding to the said common conversion dictionary in a memory | storage device, and the said management ID is updated when the said user ID conversion dictionary is updated. The medical information display program according to appendix 1, further causing a computer to function as update means for updating the common conversion dictionary based on data.

(Supplementary Note 3) First receiving means for receiving a user ID;
A second receiving means for receiving a department identification ID for identifying a department that examines a patient;
An acquisition means for acquiring a department ID corresponding to the user ID received by the first reception means with reference to a user table storing the user ID and the department identification ID in association with each other;
The medical department identification ID received by the second reception means is compared with the department ID acquired by the acquisition means, and if they match, the conversion dictionary corresponding to the user ID is activated and matches. If not, an activation means for activating the common conversion dictionary;
A medical information display device characterized by comprising:

(Additional remark 4) When the management data which manages the management dictionary which manages the conversion dictionary of user ID corresponding to the common conversion dictionary, and the conversion dictionary of user ID are updated, based on the management data The medical information display apparatus according to appendix 3, further comprising update means for updating the common conversion dictionary.

  As described above, the medical information display program and the medical information display device according to the present invention are useful for an electronic medical record system, and in particular, it is necessary to start a dictionary suitable for the user and reduce the burden on the user. Suitable for some cases.

It is a figure for demonstrating the outline | summary and characteristic of the medical treatment information display system concerning a present Example. It is a block diagram which shows the system configuration | structure of the medical treatment information display system concerning a present Example. It is a functional block diagram which shows the structure of the electronic medical record server concerning a present Example. It is a figure which shows an example of the data structure of user personal dictionary data. It is a figure which shows an example of the data structure of medical department common dictionary data. It is a functional block diagram which shows the structure of the electronic medical record client concerning a present Example. It is a figure which shows an example of the data structure of a user management table. It is a figure which shows an example of the data structure of a patient management table. It is a figure which shows an example of the data structure of clinical department master data. It is a figure which shows an example of the data structure of object user management data. It is a figure which shows an example of the login screen with respect to a user. It is a figure which shows an example of a patient information input screen. It is a figure which shows an example of a use dictionary management table. It is a flowchart which shows the process sequence of an electronic medical chart client starting process. It is a flowchart which shows the process sequence of a user login process. It is a flowchart which shows the process sequence of a patient information input process. It is a flowchart which shows the process sequence of an upload process. It is a figure which shows an example of a dictionary storage position designation | designated screen. It is a figure which shows the hardware constitutions of the computer which comprises the electronic medical record server concerning an Example. It is a figure which shows the hardware constitutions of the computer which comprises the electronic medical record client concerning an Example.

Explanation of symbols

30, 40 Computer 31, 41 Input device 32, 42 Monitor 33, 43 RAM
33a, 38a, 43a, 48a Various data 34, 44 ROM
35, 45 Medium reader 36, 46 Communication device 37, 47 CPU
37a Management processing process 38, 48 HDD
38b Management processing program 39, 49 Bus 47a Electronic medical record client processing process 48b Electronic medical record client processing program 50 Network 100 Electronic medical record server 110, 210 Input unit 120, 220 Output unit 130, 230 Communication control IF unit 140, 240 Input / output control IF Units 150 and 250 Storage unit 150a User personal dictionary data 150b Medical department common dictionary data 160 and 260 Control unit 160a Data management processing unit 200 Electronic medical record client 250a Default dictionary data 250b User personal dictionary data 250c Medical department common dictionary data 250d Person management table 250e Patient management table 250f Clinical department master data 250g Target user management data 260a Start-up processing unit 260b Login processing unit 260c Load processing unit 260d FEP processing unit

Claims (3)

Computer
First receiving means for receiving a user ID;
A second receiving means for receiving a department identification ID for identifying a department that examines a patient;
An acquisition means for acquiring a department ID corresponding to the user ID received by the first reception means with reference to a user table storing the user ID and the department identification ID in association with each other;
The medical department identification ID received by the second reception means is compared with the department ID acquired by the acquisition means, and if they match, the conversion dictionary corresponding to the user ID is activated and matches. If not, an activation means for activating the common conversion dictionary;
A medical information display program characterized by being made to function.   The computer stores management data for managing a conversion dictionary for user IDs corresponding to the common conversion dictionary in a storage device, and when the conversion dictionary for user IDs is updated, based on the management data The medical information display program according to claim 1, further causing a computer to function as update means for updating the common conversion dictionary. First receiving means for receiving a user ID;
A second receiving means for receiving a department identification ID for identifying a department that examines a patient;
An acquisition means for acquiring a department ID corresponding to the user ID received by the first reception means with reference to a user table storing the user ID and the department identification ID in association with each other;
The medical department identification ID received by the second reception means is compared with the department ID acquired by the acquisition means, and if they match, the conversion dictionary corresponding to the user ID is activated and matches. If not, an activation means for activating the common conversion dictionary;
A medical information display device characterized by comprising:

Images