JP2014191815A - Medical system, medical server and medical dictionary information management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a medical system capable of effectively sharing medical dictionary data among different document creation terminals in a medical institution.SOLUTION: The medical system includes a server, a first computer terminal, and a second computer terminal, which are communicable with one another. A medical dictionary information storage unit is provided in the server or the first computer terminal, or another server, to store multiple pieces of medical dictionary information associated with attribute information. The attribute information includes user identification information or use application identification information. Also, the second computer terminal transmits the input attribute information to the server. The server comprises a medical dictionary information acquisition unit. When receiving the attribute information, the medical dictionary information acquisition unit acquires the medical dictionary information associated with the attribute information from the medical dictionary storage unit. Further, the server transmits information based on the acquired medical dictionary information to the second computer terminal.

Description

  Embodiments described herein relate generally to a medical system that manages medical dictionary information, a medical server, and a medical dictionary information management method.

  Conventionally, document creation software has been used to create documents and the like in medical institutions. To convert the input character string (hereinafter referred to as “character string before conversion”) into another pre-registered character string (hereinafter referred to as “character string after conversion”) in the document creation software. Dictionary data is used (see Patent Document 1).

  When creating a document in a medical institution, dictionary data suitable for creating a document in a medical institution is used in addition to dictionary data of commonly used document creation software (hereinafter referred to as “medical dictionary data”). For example, medical dictionary data for creating an interpretation report, medical dictionary data for creating a document relating to medical accounting, and the like can be given.

JP 05-012257 A

  A person in charge of a medical institution may engage in other departments other than his / her department (affiliation). In addition, the worker may be engaged in the duties of other medical institutions (affiliated hospitals, etc.). In this case, the worker uses a terminal other than the terminal normally used. However, since the medical dictionary data normally used by the worker is not stored in the other terminal, the document creation software is used in the other terminal.

  If dictionary data suitable for creation of a document of a medical institution cannot be used, there is a possibility that the creation efficiency of the document is lowered because an appropriate conversion candidate is not shown for the input character string.

  Moreover, using different medical dictionary data between different medical institutions or between different medical departments leads to describing the same content in various expressions. As a result, there is a risk of causing variations in expression in a document whose expression should be unified.

  In addition, it is complicated to register or update the same medical dictionary data in all terminals of different medical institutions or different medical departments.

  An object of this embodiment is to provide a medical system that can efficiently share medical dictionary data between different document creation terminals in a medical institution.

The embodiment is a medical system including a server, a first computer terminal, and a second computer terminal, which can communicate with each other. The medical system further includes a medical dictionary storage unit provided in the server, the first computer terminal, or another server.
The medical dictionary storage unit stores a plurality of medical dictionary information associated with the attribute information. The attribute information includes user identification information or use identification information.
The second computer terminal includes a display unit, an input unit, and a terminal side control unit. The input unit is used for inputting attribute information. The second computer terminal transmits the attribute information input through the input unit to the server.
The server includes a medical dictionary information acquisition unit. When receiving the attribute information, the medical dictionary information acquisition unit acquires medical dictionary information associated with the attribute information from the medical dictionary storage unit. Further, the server transmits information based on the acquired medical dictionary information to the second computer terminal.

1 is a schematic block diagram illustrating an example of a medical system and a cloud server according to a first embodiment. Schematic which shows an example of the classification | category of the dictionary data of dictionary DB in the medical system concerning embodiment. The schematic block diagram which shows an example of the 2nd report terminal concerning 1st Embodiment. The conceptual diagram which shows the outline | summary of the report creation screen concerning 1st Embodiment. The conceptual diagram which shows the outline | summary of the report preparation screen concerning 1st Embodiment, and the display screen of a conversion candidate. The flowchart which shows the outline of operation | movement of the cloud server concerning 1st Embodiment. The flowchart which shows the outline of operation | movement of the 2nd report terminal concerning 1st Embodiment. The flowchart which shows the outline of operation | movement of the 2nd report terminal concerning 1st Embodiment. The schematic block diagram which shows an example of the 1st report terminal concerning 1st Embodiment. The flowchart which shows the outline of operation | movement of the cloud server concerning 1st Embodiment. The schematic block diagram which shows an example of the cloud server concerning a 1st modification. The flowchart which shows the outline of operation | movement of the cloud server concerning a 1st modification. The flowchart which shows the outline of operation | movement of the cloud server concerning a 1st modification. The schematic block diagram which shows an example of the 1st report terminal concerning a 2nd modification.

  With reference to FIGS. 1-13, the medical system concerning 1st Embodiment-4th Embodiment is demonstrated.

[First Embodiment]
(Medical system)
The overall configuration of the medical system according to the first embodiment will be described with reference to FIG. FIG. 1 is a schematic block diagram illustrating an example of a medical system 100 according to the first embodiment. As shown in FIG. 1, the medical system 100 includes a cloud server 1, a first report terminal 20, a second report terminal 30A, and a third report terminal 30B connected to each other via a network N so as to be able to perform data communication with each other. Has been. The first report terminal 20 corresponds to an example of “first computer terminal”, and the second report terminal 30A or the third report terminal 30B corresponds to an example of “second computer terminal”.

  In one example, the medical system 100 is configured by connecting a basic hospital and each affiliated hospital through a regional medical information network such as VPN. In another example, the medical system 100 may be configured by connecting each report terminal, medical office terminal, and the like of each medical department of a medical institution via a network such as a LAN. In FIG. 1, the first report terminal 20, the second report terminal 30 </ b> A, and the third report terminal 30 </ b> B are shown, but this is for convenience of illustration, and terminals connected to the network N in the medical system 100. The number is not limited to the illustration of FIG.

  In addition, as will be described later, in an example, the first report terminal 20 is a computer terminal that is normally used by a user to create a document of a medical institution, and the storage unit or the like stores medical dictionary data for document creation customized by the user. It is remembered. This medical dictionary data is a data used for conversion of input characters, including character strings such as terms that have been registered to improve the efficiency of document creation when a user creates a document such as an interpretation report or a medical report. is there.

(Overall configuration of cloud server)
Next, the overall configuration of the cloud server 1 according to the first embodiment will be described with reference to FIG. As shown in FIG. 1, the cloud server 1 includes a main control unit 3, a transmission / reception unit 5, a medical dictionary data storage unit 7, an acquisition unit 9, and an interface storage unit 11. In one example, the cloud server 1 has a function of collectively storing and managing information in the medical system 100. However, not all data in the medical system 100 but only a part of information including at least medical dictionary data may be stored and managed.

<Main control unit>
The main control unit 3 is composed of, for example, a CPU, a ROM, a RAM, and the like. In the ROM, a control program is stored in advance, and the CPU functions as the main control unit 3 by expanding the control program on the RAM as appropriate. For example, in response to a medical dictionary data acquisition request from the second report terminal 30A or the third report terminal 30B, the main control unit 3 executes medical dictionary data acquisition processing based on attribute information relating to the acquisition request. As another example, the main control unit 3 performs control to transmit data related to an interface (screen data such as a window) for displaying conversion candidates based on dictionary data to the second report terminal 30A or the like. The interface is screen data (display window or the like) for displaying conversion candidates when a document creation application or the like is executed in the second report terminal 30A or the like. The window indicates a display screen that occupies a predetermined display area of the display unit. Details of each control of the main control unit 3 according to the present embodiment will be described below.

<Transmitter / receiver>
The transmission / reception unit 5 is a communication interface for exchanging medical dictionary data and attribute information associated with the data with the first report terminal 20, the second report terminal 30A, and the third report terminal 30B. Further, the cloud server 1 transmits the update result data of the medical dictionary data and the log data thereof via the transmission / reception unit 5.

<Outline of medical dictionary data storage unit>
The outline | summary of the medical dictionary data storage part 7 concerning 1st Embodiment is demonstrated with reference to FIG. FIG. 2 is a schematic diagram illustrating an example of classification of dictionary data in the dictionary DB in the medical system according to the embodiment. The medical dictionary data storage unit 7 includes a hard disk drive (HDD; Hard Disk Drive), a Flash SSD (Solid State Drive), a RAM SSD, and the like. The medical dictionary data storage unit 7 stores medical dictionary data and attribute information in association with each other using the dictionary DB. The medical dictionary data storage unit 7 corresponds to an example of a “medical dictionary storage unit”.

  When receiving the medical dictionary data associated with the attribute information together with the attribute information from the first report terminal 20 or the like, which will be described later, via the transmission / reception unit 5, the main control unit 3 determines whether the attribute information matches the dictionary DB. judge. If the main control unit 3 determines that the data matches, the main control unit 3 stores the medical dictionary data in the medical dictionary data storage unit 7. Furthermore, the main control unit 3 stores the file name of the medical dictionary data and various attribute information in the dictionary DB of the medical dictionary data storage unit 7 in association with each other. The contents of the process (medical dictionary data registration process) related to registration and update of the medical dictionary data will be described in relation to the first report terminal 20 described later.

<Dictionary DB; attribute information>
As shown in the table of FIG. 2, the dictionary DB in the medical dictionary data storage unit 7 is a database that stores the file name of medical dictionary data and various attribute information in the dictionary data in association with each other. The attribute information classifies dictionary data from various viewpoints. In the example of FIG. 2, when attribute information is roughly divided, it can be classified into user identification information and use identification information. In addition to the user identification information and the application identification information, the attribute information may include second priority information indicating the priority of the medical dictionary data. Although details of the medical dictionary data will be described later, information indicating the priority of each conversion candidate with respect to the same (including substantially the same; hereinafter the same) input characters in the medical dictionary data is included in the medical dictionary data. ing. Hereinafter, the priority for each conversion candidate in the medical dictionary data may be referred to as “first priority information”.

<< Attribute information; user identification information >>
Among these, as user identification information, for example, the name or identification information of the user who created (or possesses (the same applies below)) medical dictionary data or the identification of the individual user, or the medical organization to which the user who created the medical dictionary data belongs Etc. Examples of user identification information include the name or identification information of a hospital group to which the medical institution belongs. Further, examples of user identification information include the name of the department (affiliation department) such as the department of medical care at the user's medical institution or identification information. Examples of user identification information include account information such as a logon account, a login account, and a sign-in account for the user to use the first report terminal 20, the second report terminal 30A, the third report terminal 30B, etc. To do. For example, the operating system logon account of each terminal. However, when these account information is divided into accounts for each use, such as an interpretation report account, an observation report account, a paper creation account, etc., the account information can also be regarded as use identification information. That is, there is no need to strictly separate user identification information and use identification information in attribute information. “Affiliation department such as a medical department at a user's medical institution” corresponds to an example of “affiliation destination identification information”. Further, “affiliation department name” or “affiliation department identification information” corresponds to an example of “affiliation destination identification information”.

  Note that the user identification information is not limited to the example of FIG. 2, and any identification information for identifying the user who created the medical dictionary data can be included. The dictionary DB may be configured not to include some of the user identification information shown in FIG. Furthermore, user identification information does not have to be included as attribute information. That is, since it is sufficient that the attribute information can be used for storing or reading medical dictionary data, the attribute information does not include the identification information of the creator of the medical dictionary data or the identification information about the affiliation of the creator. There can be.

<< Attribute information; Usage identification information >>
On the other hand, the usage identification information of the attribute information corresponds to, for example, usage of medical dictionary data or identification information indicating the usage. Specific examples of the use identification information include identification information for identifying an application that uses medical dictionary data. Hereinafter, this identification information may be referred to as “application identification information”.

  For example, medical dictionary data “xxx.dic” is created by a user of the first report terminal 20 or the like to improve the character input efficiency when using the application “Report A” for creating an interpretation report. To do. In this case, the identification information of the application “Report A” is associated as attribute information with the medical dictionary data “xxx.dic” by the user in the first report terminal 20 or the like. Thereafter, medical dictionary data “xxx.dic” is stored in the medical dictionary data storage unit 7 of the cloud server 1 together with the attribute information. Accordingly, the medical dictionary data storage unit 7 stores the medical dictionary data “xxx.dic” and the application identification information “Report A” in the dictionary DB of the medical dictionary data storage unit 7 in association with each other.

  Another example of use identification information corresponds to clinical department identification information for identifying medical dictionary data for each clinical department as shown in FIG. Even if the application used for creating the observation report is the same, it is also possible that the words used are characteristic for each clinical department to which the user belongs. Therefore, clinical department identification information may be associated as attribute information of medical dictionary data. Assuming such a situation, it is also possible to adopt a configuration in which clinical department identification information is included in the items of the attribute information table in the dictionary DB.

  Another example of the application identification information is part identification information for each part of the human body. There may be a case where there is a characteristic in a symptom or a unit used in combination with a word for each part of the human body. For example, in the case of a part of a human body, the name of each tissue may be different for each part. In addition, the name of the disease may be different for each part of the human body. Therefore, part identification information may be associated as attribute information of medical dictionary data, and the attribute information table in the dictionary DB may be configured to include part identification information assuming such a situation. It is.

  Another example of use identification information is disease identification information for identifying medical dictionary data for each disease. There may be cases where the word used for each finding of the disease is characteristic. Similarly, as another example, modality identification information for identifying medical dictionary data for each modality for generating an image, which is used for creating an interpretation report, corresponds. Therefore, disease identification information or modality identification information may be associated as attribute information of medical dictionary data, and the attribute information table in the dictionary DB includes such identification information assuming such a situation. It is also possible.

  The medical dictionary data to be stored only needs to be associated with at least one type of attribute information in the attribute information table in the dictionary DB. For example, medical dictionary data associated only with application identification information may be stored. However, the cloud server 1 is not limited to such a configuration. If all types of attribute information in the attribute information table in the dictionary DB are not associated, the cloud server 1 rejects registration or update of medical dictionary data. There may be. As another example, if one or more specific attribute information (essential attribute information) in the table of the dictionary DB is not associated, the cloud server 1 may refuse to register or update medical dictionary data. Good. As a specific example, it is possible to include at least the application identification information and the identification information of the medical institution to which the user who created the medical dictionary data belongs among the attribute information.

<Main control unit; attribute information determination process>
In acquiring medical dictionary data from the medical dictionary data storage unit 7, attribute information determination processing described below is performed. The main control unit 3 of the cloud server 1 receives an acquisition request for medical dictionary data together with attribute information from a report terminal such as the second report terminal 30A or the third report terminal 30B via the transmission / reception unit 5. The main control unit 3 determines whether the attribute information in the acquisition request is appropriate. For example, the main control unit 3 determines whether the attribute information in the acquisition request is in the attribute information table in the dictionary DB. This determination is made by determining whether the format of attribute information in the acquisition request conforms to any of the formats of various attribute information in the dictionary DB table.

  When it is determined that the format of the attribute information related to the acquisition request does not conform to the format in the dictionary DB table, the main control unit 3 outputs attribute error determination data to the report terminal that has transmitted the acquisition request. Upon receiving the error determination data, the report terminal displays an acquisition request error based on the data. When the main control unit 3 determines that the attribute information related to the acquisition request is compatible with the format in the table of the dictionary DB, the main control unit 3 instructs the acquisition unit 9 to execute a medical dictionary data search process to be described later.

  If the main control unit 3 conforms to the format of the various attribute information in the dictionary DB even with at least one of the attribute information in the acquisition request, the other attribute information in the acquisition request becomes the format of the various attribute information. It is good also as a structure which judges that it does not need to adapt.

  On the other hand, if the main control unit 3 does not conform to the corresponding attribute information format of the dictionary DB for all the attribute information in the acquisition request, the attribute information related to the acquisition request does not conform to the dictionary DB format. It is good also as a structure judged as.

<Outline of the acquisition unit>
An outline of the acquisition unit 9 will be described. The acquisition unit 9 searches the medical dictionary data storage unit 7 for corresponding medical dictionary data in response to a medical dictionary data acquisition request from each report terminal such as the second report terminal 30A and the third report terminal 30B. As a result of the search, if there is corresponding medical dictionary data, the medical dictionary data is transmitted to the report terminal relating to the acquisition request. The acquisition unit 9 performs a search process for medical dictionary data according to the result of the attribute information determination process. Further, the acquisition unit 9 receives, via the main control unit 3 and the transmission / reception unit 5, an acquisition request for data related to an error display indicating that there is no combination of medical dictionary data and attribute information or no corresponding data as a result of search processing. Send to the reporting terminal. Hereinafter, a specific example of the search process of the acquisition unit 9 will be described. The acquisition unit 9 corresponds to an example of a “medical dictionary acquisition unit”.

<Acquisition part; search processing>
If the attribute information in the acquisition request matches with the dictionary DB by the attribute information determination process, the acquisition unit 9 receives the instruction from the main control unit 3 and searches for medical dictionary data. That is, the acquisition unit 9 searches corresponding medical dictionary data from the dictionary DB of the medical dictionary data storage unit 7 based on all attribute information determined to be compatible with the format among the attribute information related to the acquisition request.

  When the acquisition unit 9 determines that there is medical dictionary data having the attribute information in the dictionary DB as a result of the search processing using the attribute information, the acquisition unit 9 specifies a file name registered in the dictionary DB for the medical dictionary data. To do. For example, the acquisition unit 9 searches the dictionary DB for medical dictionary data associated with these attribute information based on the user identification information “user A” and the department identification information “radiology”.

  The acquisition unit 9 specifies a storage destination of the medical dictionary data (for example, an address for designating a storage area in the medical dictionary data storage unit 7) based on the file name of the further specified medical dictionary data. The acquisition unit 9 acquires medical dictionary data from the specified storage destination. For example, the acquisition unit 9 specifies the file name “XXX.dic” of medical dictionary data in which the user identification information “user A” and the department identification information “radiology” are associated, and the file name “XXX.dic”. Is identified in the medical dictionary data storage unit 7.

  In one example of the search process, the acquisition unit 9 executes the search process using all attribute information included in the acquisition request and determined to be compatible with the format of the dictionary DB in the attribute information determination process. As another example, the acquisition unit 9 may execute a search process using each of various attribute information related to the acquisition request. That is, as a result of the determination in the attribute information determination process described above, appropriate attribute information is specified from the attribute information related to the acquisition request. However, even if the medical dictionary data associated with all the specified attribute information is searched, Alternatively, medical dictionary data associated with at least one of the specified attribute information may be searched.

  As a specific example of the former, the acquisition unit 9 includes a medical dictionary corresponding to all of the user identification information, the medical institution identification information (or hospital group identification information), the department identification information, the account information, and the application identification information related to the acquisition request. Search for data.

  As another example, the acquisition unit 9 searches medical dictionary data using each attribute information that has not been determined to be an attribute error in the attribute information determination process among the attribute information related to the acquisition request. As a specific example, the acquisition unit 9 searches medical dictionary data corresponding to any of user identification information, belonging medical institution identification information (or hospital group identification information), belonging department identification information, account information, and application identification information. However, in this example, for example, the medical dictionary data searched by the user identification information related to the acquisition request may be the same as the medical dictionary data searched by the application identification information. When a plurality of identical medical dictionary data correspond as search results, the acquisition unit 9 acquires only one data among the plurality.

  As a result of the search, the acquisition unit 9 acquires each piece of attribute information associated with the medical dictionary data together with the corresponding medical dictionary data. The acquisition unit 9 acquires not only attribute information used for the search but also all attribute information associated with the acquired medical dictionary data. For example, even when the acquisition unit 9 performs a search process using the user identification information “User A” and the department identification information “Radiology”, as long as other attribute information is associated with the medical dictionary data. The other attribute information is also acquired. In this case, the other attribute information includes belonging medical institution identification information, hospital group identification information, second priority information, application identification information, and the like.

  In consideration of the fact that a plurality of medical dictionary data is acquired in the search process, the second priority information among the attribute information related to the medical dictionary data may always be acquired together with the medical dictionary data. .

  Even when there are a plurality of corresponding medical dictionary data, each attribute information associated with each medical dictionary data is acquired. The acquisition unit 9 sends the acquired medical dictionary data and each attribute information to the main control unit 3. Next, the main control unit 3 identifies the report terminal related to the acquisition request. For example, when the identified report terminal is the second report terminal 30A, the main control unit 3 sends the second report terminal 30A via the transmission / reception unit 5 while maintaining the association between the medical dictionary data and each attribute information. The main control unit 3 may send a search log according to the acquisition request to the second report terminal 30A together with these data.

  If the acquisition unit 9 determines that the attribute information related to the acquisition request is not in the table of the dictionary DB, the acquisition unit 9 displays data for displaying an error indicating that there is no corresponding medical dictionary data to the report terminal that has transmitted the acquisition request. Output. The report terminal receives the data and displays an acquisition request error (details will be described later).

<Interface storage unit>
The interface storage unit 11 will be described. The interface storage unit 11 includes an HDD, a flash SSD, a RAM SSD, and the like. The interface storage unit 11 stores the screen data (interface; see FIG. 4B) of the selection screen for conversion candidates for medical dictionary data and the types of various document creation applications in association with each other. The interface storage unit 11 and the medical dictionary data storage unit 7 can be configured as the same storage device.

  The interface storage unit 11 may store a program for creating medical dictionary data acquisition request data. For example, when an access request to the acquisition request creation program in the cloud server 1 is made by the web browser activated in the second report terminal 30A, the main control unit 3 accepts the access request. Further, in response to the access request, the main control unit 3 reads screen data of an acquisition request creation screen that can be displayed via the web browser from the interface storage unit 11. The main control unit 3 performs control to send the screen data to the second report terminal 30A. The second report terminal 30A displays the acquisition request creation screen on the display unit (see reference numeral 6 in FIG. 3) via the web browser. When an application for creating acquisition request data is stored in the second report terminal 30A, the interface storage unit 11 may not be configured to store the program.

  Further, the interface storage unit 11 may store setting information regarding the display format of the conversion candidate selection screen data. As an example of the setting information, information on the arrangement position of the conversion candidate selection screen displayed on the second report terminal 30A described later can be given. The information regarding the arrangement position is information set in advance as to where the selection screen is arranged with respect to the display screen of the document creation application. Since the document creation application may be different for each report terminal and usage, the setting information is set at least for each type of document creation application.

  Another example of setting information stored in the interface storage unit 11 is information regarding the size of the selection screen. The information regarding the size is information set with respect to the ratio of the size of the selected screen to the size of the entire screen in the display unit of each report terminal. In addition, when the conversion candidates for each dictionary data are displayed in parallel in order of dictionary data priority as will be described later, it is possible to set the size of the selection screen for selecting conversion candidates for dictionary data having a high priority to be relatively large. is there.

  Further, as another example of the setting information stored in the interface storage unit 11, setting information related to the array display of a plurality of dictionary data may be stored. As described above, a plurality of medical dictionary data may correspond to the attribute information in one acquisition request. In some cases, the plurality of medical dictionary data can be used in the same document creation application. In that case, there is a possibility that inconvenience may arise in the setting for displaying only the selection screen for selecting one of the medical dictionary data conversion candidates. For example, there may be cases where the priorities (second priority information) of a plurality of medical dictionary data are the same, and it may not be possible to determine which of the selection screens based on two or more medical dictionary data is displayed on the report terminal. is there. Alternatively, there may be a problem that only one type of medical dictionary data conversion candidate is displayed even though the medical dictionary data has the same priority.

  In order to deal with such a problem, information related to array display is set in advance. That is, when a plurality of medical dictionary data is acquired in accordance with the acquisition request, the interface storage unit 11 has setting information related to the array display so that a user who creates a document can refer to conversion candidates of the plurality of medical dictionary data. May be remembered. Several display examples of the conversion candidate selection screen will be described below.

<< Selection screen display example-1 >>
As an array of conversion candidate selection screens in the setting information of the interface storage unit 11, for example, the following types are conceivable. As a first example, there is an arrangement method in which conversion candidate selection screens based on all medical dictionary data corresponding to attribute information are displayed in parallel. In this arrangement method based on setting information, when three types of dictionary data are stored in the report terminal, conversion candidate selection screens based on all three types of dictionary data are arranged in parallel in a predetermined direction on the display unit of the report terminal. To display.

  When the second priority information is associated with the medical dictionary data, the selection screens may be arranged in the order of priority of the medical dictionary data. There are an arrangement method in which selection screens are arranged from top to bottom in descending order of priority, an arrangement method in which selection screens are arranged from left to right in order of high priority, and the like.

  Furthermore, in the parallel display in order of priority in the first example, medical dictionary data having a low priority may be displayed. In the case of the configuration in which medical dictionary data is displayed in order of priority as described above, medical dictionary data having a low priority has a low display frequency and may not be used. However, even if the set priority is low, there may exist dictionary data that can present conversion candidates useful for creating a predetermined document. That is, the priority of the medical dictionary data set by the user's judgment may not always correspond to the substantial usefulness of the medical dictionary data. Accordingly, in the setting information related to the array display of the interface storage unit 11, both the medical dictionary data conversion candidates that are set to the low priority according to the second priority information and the conversion candidates based on the high priority medical dictionary data are displayed together. It is good also as composition set up to do.

  Further, in the parallel display in order of priority in the first example, the number of conversion candidates for each dictionary data to be displayed in parallel may be set. For example, conversion candidates for two types of medical dictionary data “XXX.dic” and “ZZZ.dic” are displayed in order of high priority, and conversion candidates for one type of low priority medical dictionary data “YYY.dic” are displayed. May be displayed. Further, conversion candidates for high-priority medical dictionary data are displayed, and not the medical dictionary data acquired from the medical dictionary data storage unit 7 but dictionary data stored in advance in the report terminal is displayed in parallel. It may be. The display in order of priority may be different for each application that uses dictionary data. In order to change the priority for each application, application identification information in the attribute information is used.

<< Selection screen display example-2 >>
As a second example of the arrangement of conversion candidate selection screens, a conversion candidate based on one type of medical dictionary data among a plurality of types is first displayed in the document creation application of the report terminal, and sequentially according to the switching operation. There is a method of switching medical dictionary data. For example, high-priority medical dictionary data is selected from a plurality of medical dictionary data acquired by the acquisition unit 9 and displayed first. In this example, the selection screen data in the interface storage unit 11 is set to display a screen switching button on the selection screen. When the switching button is operated by the operation unit or the like in the report terminal, the medical dictionary data is switched, and a screen for selecting other conversion candidates is displayed. With such a configuration, it is possible to sequentially switch medical dictionary data according to a switching operation.

  It is possible to combine the second example and the first example. For example, medical dictionary data can be switched by operation and medical dictionary data is switched in descending order of priority, and medical dictionary data with low priority is always displayed together with the first selection screen. The second selection screen may be displayed in parallel. As another example of combining the second example and the first example, even if conversion candidates of a plurality of medical dictionary data are displayed in parallel in order of high priority, conversion candidates of all medical dictionary data cannot be displayed. In some cases, the display may be controlled so as to switch to another dictionary data conversion candidate in response to a user operating a switching button on the selection screen.

<< Selection screen display example-3 >>
As a third example of the arrangement of conversion candidate selection screens, there is a display method for displaying on one selection screen without distinguishing conversion candidates based on a plurality of types of medical dictionary data in the document creation application of the report terminal. It is done. For example, first, high priority medical dictionary data is selected based on the second priority information. Next, based on the first priority information, a conversion candidate having the highest priority for the same input in the selected medical dictionary data is extracted. This conversion candidate is the first conversion candidate. Next, the medical dictionary data of the next point in the priority is selected based on the second priority information. Further, based on the first priority information of the next point medical dictionary data, the highest priority conversion candidate is extracted from the medical dictionary data. This conversion candidate is the second conversion candidate.

  In this way, the reporting terminal based on the setting information in the interface storage unit 11 selects a conversion candidate having a higher priority based on the first priority information from the high priority medical dictionary data selected based on the second priority information. Extract sequentially. For example, when there is high priority medical dictionary data “XXX.dic” selected by the second priority information, the report terminal assigns each conversion candidate in the medical dictionary data “XXX.dic” to the first priority. Based on information, "ABCDE" (first rank), "ABCD" (second rank), "ABC" (third rank), "AB" (fourth rank), "ABCDE" (fifth rank) . . . And so on.

  Furthermore, the report terminal arranges the extracted conversion candidates in the order of extraction based on the setting information. That is, the report terminal displays the conversion candidates rearranged based on the setting information in a lump, not for each medical dictionary data. In the third example, a configuration in which extraction and rearrangement processing are not performed as described above may be used.

  That is, the conversion candidates may be displayed in series in the order of high-priority medical dictionary data. For example, the report terminal displays each conversion candidate of the medical dictionary data with the highest priority based on the setting information in the interface storage unit 11 in order based on the first priority information, and then the priority of the next point in the selection screen. Each conversion candidate of the medical dictionary data is displayed in order based on the first priority information. The report terminal repeats this process according to the setting information and displays conversion candidates for all of the acquired medical dictionary data. In all of the above first to third examples, the setting information in the interface storage unit 11 is configured so that a scroll operation can be performed to display lower conversion candidates on the selection screen. And

  It is possible to combine the third example with the second example or the first example. For example, in the third example, when conversion candidates for each medical dictionary data are serially connected and displayed, a switching button for switching to other medical dictionary data may be provided on the selection screen. Further, the selection screen of the third example that collectively displays conversion candidates for all medical dictionary data and another selection screen that displays medical dictionary data with low priority may be displayed in parallel. Further, the selection screen for the combination of the third example, the second example, and the first example may be displayed based on the setting information in the interface storage unit 11.

(Overall configuration of second report terminal)
Next, the overall configuration of the second report terminal according to the first embodiment will be described with reference to FIG. 3 in the example of the second report terminal 30A. As shown in FIG. 3, the second report terminal 30 </ b> A includes a terminal-side control unit 2, a transmission / reception unit 4, a display unit 6, an operation unit 8, a storage unit 10, a conversion unit 12, and a display control unit 14. Yes. In one example, the second report terminal 30 </ b> A has a function of creating an acquisition request for acquiring medical dictionary data from the cloud server 1 and a function of transmitting the acquisition request to the cloud server 1. However, it is also possible to have a configuration in which the cloud server 1 is responsible for all functions specific to the present embodiment.

<Terminal control unit>
The terminal-side control unit 2 is composed of, for example, a CPU, ROM, RAM, and the like. In the ROM, a control program is stored in advance, and the CPU functions as the terminal-side control unit 2 when the control program is appropriately expanded on the RAM. For example, the terminal-side control unit 2 reads a program for creating medical dictionary data acquisition request data from the storage unit 10 and sends the program to the display control unit 14. In addition, an input indicating attribute information related to a medical dictionary data acquisition request is received from the operation unit 8 and reflected on the acquisition request creation screen. Further, the main control unit 3 transmits an acquisition request for medical dictionary data with attribute information to the cloud server 1 via the transmission / reception unit 4 in response to receiving an instruction to complete the acquisition request data from the operation unit 8. . In the configuration in which the acquisition request data for medical dictionary data is created via the web browser, the process for reading the acquisition request creation program from the storage unit 10 is not performed.

  Further, the terminal side control unit 2 causes the storage unit 10 to store medical dictionary data acquired from the cloud server 1. At this time, the attribute information associated with the medical dictionary data is stored while maintaining the associated state.

<Transmitter / receiver>
The transmission / reception unit 4 is a communication interface for transmitting / receiving acquisition request data, medical dictionary data, attribute information associated with the data, search log, and the like between the second report terminal 30A and the cloud server 1. In addition, data transmission / reception at the time of creating an acquisition request is performed with the cloud browser 1 via the transmission / reception unit 4 by the web browser.

<Display section>
The display unit 6 is a CRT (Cathode Ray Tube) display, an LCD (Liquid Crystal Display), an organic EL (OELD; Organic Electro-Luminescence), or an FED (Field Emission Display) arbitrary display device. The The display unit 6 displays various screens under the control of the display control unit 14, for example, display screens based on an acquisition request data creation screen or a document creation application. Also, a conversion candidate selection screen (to be described later) or an error in the above acquisition request is displayed.

<Operation unit>
The operation unit 8 is configured by an arbitrary type of operation device or input device such as a keyboard, a mouse, a trackball, a joystick, or a control panel. The terminal-side control unit 2 receives an operation signal output from the operation unit 8 based on the performed operation, and executes control and calculation corresponding to the operation content. The operation unit 8 corresponds to an example of an “input unit”.

<Storage unit>
The storage unit 10 includes an HDD, a Flash SSD, a RAM SSD, and the like. The storage unit 10 stores programs such as a general-purpose web browser, document creation, and spreadsheet. Further, the storage unit 10 stores dictionary data that can be used in the document creation application used in the second report terminal 30A. The dictionary data may be general-purpose dictionary data in the document creation application, or the dictionary data may be customized by the user of the second report terminal 30A. The storage unit 10 stores medical dictionary data acquired from the cloud server 1. The storage unit 10 corresponds to an example of a “terminal side storage unit”.

  Depending on the configuration of the storage unit 10 of the present embodiment, a program for creating medical dictionary data acquisition request data may be stored. For example, the program is screen data of a medical dictionary data acquisition request creation screen. In addition, when the acquisition request creation screen is displayed, the program receives input of attribute information related to the acquisition request (such as selection from a drop-down menu), and the terminal-side control unit 2 generates acquisition request data. It is. The attribute information determination process may be executed in the program. In the case of this configuration, the cloud server 1 may be configured not to execute the attribute information determination process.

<Conversion unit>
The conversion unit 12 determines dictionary data that can be used in the program at a predetermined timing such as when a program that involves character input such as a document creation application is started. For example, the conversion unit 12 compares the format of each dictionary data stored in the storage unit 10 including the medical dictionary data acquired in response to the acquisition request with a dictionary format that can be used in the activated program. In the configuration in which the application identification information is associated with the medical dictionary data, the conversion unit 12 executes the comparison process based on the application identification information. As a result of the comparison, the conversion unit 12 reads the dictionary data determined to be usable in the activated program.

  Moreover, the conversion part 12 receives the input from the operation part 8 via the terminal side control part 2 at the time of execution of the said program, and memorize | stores the said input content temporarily. Next, the conversion unit 12 converts the character into a pre-conversion character (see FIG. 4B; see “****”) that is uniquely determined for the input based on a preset input language. Next, the conversion unit 12 temporarily stores the character before conversion. Furthermore, the conversion unit 12 extracts conversion candidates corresponding to the stored pre-conversion characters from each of the read dictionary data. Further, the conversion unit 12 temporarily stores the extracted conversion candidates for each dictionary data.

  For example, based on each dictionary data, the conversion unit 12 converts the conversion candidates “ABCDE”, “ABCD”, “ABC”, “AB”, “ABCDE” corresponding to the pre-conversion character “***” from each dictionary data. ". . . To extract. The conversion unit 12 extracts the extracted conversion candidates together with information in order of priority according to the first priority information of each dictionary data. The conversion unit 12 sends at least conversion candidates for each dictionary data to the display control unit 14 together with the first priority information in the dictionary data.

  Here, in the configuration in which data related to the conversion candidate selection screen and the arrangement of the selection screen is transmitted to the report terminal that has issued the acquisition request from the cloud server 1 in the present embodiment, the conversion unit 12 is stored in the storage unit 10. Read the selected screen data. Further, the conversion unit 12 sends the conversion candidate and the first priority order information for each dictionary data, and the read conversion candidate selection screen data to the display control unit 14. When the conversion unit 12 also reads out data related to the array display of the selection screen, the data is also sent to the display control unit 14.

<Display control unit>
The display control unit 14 will be described with reference to FIGS. 4A and 4B. FIG. 4A is a conceptual diagram showing an outline of a report creation screen according to the first embodiment. FIG. 4B is a conceptual diagram illustrating an overview of a report creation screen and a conversion candidate display screen according to the first embodiment. The display control unit 14 controls the display content of the display unit 6 in the second report terminal 30A. For example, various screen data is received from the storage unit 10 via the terminal-side control unit 2 and various display screens are displayed on the display unit 6. The various display screens are initial screens after startup in the second report terminal 30A, and display screens of the started document creation application, web browser, and the like. Further, the display control unit 14 receives conversion candidates for each dictionary data from the conversion unit 12 during execution of an application involving character input, assigns the conversion candidate data to the conversion candidate selection screen data, and converts the conversion candidate data together with the application. Generate a candidate selection screen. The display control unit 14 displays the generated conversion candidate selection screen on the display unit 6. The outline of this process will be described below with reference to FIGS. 4A and 4B.

<< Display Control Unit; Example 1 of Display Processing of Acquisition Request Creation Screen >>
When an operation to instruct display of the medical dictionary data acquisition request creation screen is performed by the operation unit 8, the instruction is sent to the terminal-side control unit 2. In response to the instruction, the terminal-side control unit 2 acquires screen data of the acquisition request creation screen. In one example, this screen data is data acquired from the cloud server 1 via a general-purpose web browser stored in the storage unit 10. That is, when an instruction to display the acquisition request creation screen is given via the web browser, the terminal-side control unit 2 of the second report terminal 30A sends a request for screen data to the cloud server 1 via the transmission / reception unit 4. Run. The instruction to display the acquisition request creation screen is, for example, an operation for designating a storage destination of screen data. The cloud server 1 receives the request via the transmission / reception unit 5. In response to the request, the main control unit 3 reads the screen data of the acquisition request creation screen from the interface storage unit 11 and sends it to the second report terminal 30 </ b> A via the transmission / reception unit 5.

  The terminal-side control unit 2 of the second report terminal 30 </ b> A receives the acquisition request creation screen from the cloud server 1 via the transmission / reception unit 4 and sends it to the display control unit 14. The display control unit 14 causes the display unit 6 to display an acquisition request creation screen via a web browser. If attribute information is input via the operation unit 8 when the screen is displayed, the input content is reflected and displayed on the acquisition request creation screen by the display control unit 14 via the terminal-side control unit 2. Further, in the second report terminal 30A, the input attribute information is temporarily stored in the RAM or the like of the terminal side control unit 2. Further, when the second report terminal 30 </ b> A displays the screen, if there is an operation indicating that the creation of the acquisition request data has been completed via the operation unit 8, the terminal-side control unit 2 includes the temporarily stored attribute information. Then, an instruction to complete the creation data of the medical dictionary data acquisition request is sent to the cloud server 1. At this time, the identification information of the report terminal concerning the acquisition request may be transmitted together.

<< Display Control Unit; Example 2 of Display Processing of Acquisition Request Creation Screen >>
Another example from acquisition request creation screen display processing to acquisition request transmission will be described. When an operation for instructing display of a medical dictionary data acquisition request creation screen is performed based on the operation unit 8 via the browser, an instruction based on the operation is sent to the cloud server 1 via the transmission / reception unit 4. When the cloud server 1 receives the request for the screen data, the main control unit 3 reads the screen data of the acquisition request creation screen in response to the request and sends it to the second report terminal 30A via the transmission / reception unit 5.

  Similarly to the above, when the attribute information is input through the operation unit 8 while the acquisition request creation screen is displayed on the display unit 6 of the second report terminal 30A, the input content is the terminal-side control unit 2, transmission / reception. It is sent to the main control unit 3 via the unit 4 and the transmission / reception unit 5. The main control unit 3 of the cloud server 1 temporarily stores the input attribute information and creates screen data reflecting the input content. The screen data is sent to the display control unit 14 of the second report terminal 30A. The display control unit 14 causes the display unit 6 to display an acquisition request creation screen in which the input content is reflected. Further, if there is an operation indicating that the creation of the acquisition request data is completed via the operation unit 8 when the screen is displayed on the second report terminal 30A side, the terminal-side control unit 2 creates the medical dictionary data and the acquisition request creation data. A completion instruction is sent to the cloud server 1. In the case of this configuration, the completion instruction is an acquisition request. The cloud server 1 receives the acquisition request, and executes the above-described processing for acquiring medical dictionary data based on the temporarily stored attribute information.

<< Display Control Unit; Example 3 of Display Processing of Acquisition Request Creation Screen >>
Another example from acquisition request creation screen display processing to acquisition request transmission will be described. When an operation for instructing display of a medical dictionary data acquisition request creation screen is performed based on the operation unit 8, the terminal-side control unit 2 executes a program for creating medical dictionary data acquisition request data from the storage unit 10. read out. Based on the program, when the acquisition request creation screen is displayed on the display unit 6 by the display control unit 14, if the attribute information is input via the operation unit 8, the input content is sent to the terminal-side control unit 2. It is done. The terminal-side control unit 2 temporarily stores the input attribute information and sends the input content to the display control unit 14. Based on the above program, the display control unit 14 creates screen data that reflects the input content on the acquisition request creation screen. The subsequent processing is the same as in Example 1 above.

<< Display control unit: Example of display processing for acquisition request error determination >>
In the second report terminal 30A, after transmitting the acquisition request, as a result of the attribute information determination process and search process in the cloud server 1, data for displaying an error in the acquisition request may be received. For example, when an attribute information determination error occurs although the acquisition request is executed, the cloud server 1 notifies the second report terminal 30A of an error message indicating that the format of the attribute information related to the acquisition request does not match the format of the dictionary DB. Send display screen data. The second report terminal 30A causes the display control unit 14 to display an error message on the display unit 6 based on the data.

  In addition, when a determination error indicating no match is found as a result of the search processing, the cloud server 1 displays an error message display screen indicating that there is no medical dictionary data corresponding to the attribute information related to the acquisition request to the second report terminal 30A. Send data. The second report terminal 30A causes the display control unit 14 to display an error message on the display unit 6 based on the data.

<< Display control unit; example of selection screen arrangement processing >>
In the second report terminal 30 </ b> A, when an operation for displaying an interpretation report creation screen is performed from the operation unit 8, the terminal-side control unit 2 reads an interpretation report creation application from the storage unit 10. Further, the terminal-side control unit 2 sends screen data of the interpretation report creation screen to the display control unit 14. The display control unit 14 displays an interpretation report creation screen as shown in FIG. 4A based on the screen data. Note that a medical image and a thumbnail of the medical image related to the interpretation report are displayed on the right side in FIG. 4A. In addition, an interpretation report display field is displayed on the left side in FIG. 4A. A character string is displayed in the display column of the interpretation report.

  This character string includes a character string that has already been converted and confirmed as a character string. In addition, as shown in FIG. 4B, a pre-conversion character (unconverted character) corresponding to the input content input by the user via the operation unit 8 may be displayed. Prior to the display of the conversion candidate selection screen described below, the following processing is generally performed by the conversion unit 12 or the like. First, when an input operation is performed via the operation unit 8 when the document creation application is started, the conversion unit 12 determines a pre-conversion character that is uniquely determined for the input based on a preset input language, input mode, and the like. Convert to The display control unit 14 receives the pre-conversion character and displays the pre-conversion character on the display unit 6 (see FIG. 4B; “******”). At this time, if the configuration performs predictive conversion, the process proceeds to display processing of the next selection screen at this point. As another example, the conversion unit 12 may shift to the next selection screen display process in response to a conversion operation of the pre-conversion character from the operation unit 8.

  The display control unit 14 receives, for example, conversion candidates for each dictionary data, first priority information and second priority information, and data related to conversion candidate selection screens and selection screen arrangement displays from the conversion unit 12. First, the display control unit 14 assigns a plurality of conversion candidates in each dictionary data to selection screen data in order of priority based on the first priority information. The display control unit 14 performs this process for each dictionary data. Further, the display control unit 14 determines the order of priority of each dictionary data based on the second priority information. Further, the display control unit 14 arranges the conversion candidate selection screens for each dictionary data (window display or the like; refer to the lower left column in FIG. 4B) in the order of priority of the specified dictionary data based on the data related to the array display of the selection screen. To decide.

  Further, the display control unit 14 displays the conversion candidate selection screen on the interpretation report creation screen in accordance with the information on the determined arrangement and the information on the position and size of the conversion candidate selection screen set in advance. Control to display on the screen. Note that the display format of the conversion candidate selection screen by the display control unit 14 is in accordance with the setting information regarding the display format received from the interface storage unit 11 of the cloud server 1.

  For example, as shown in FIG. 4B, the respective dictionary data are arranged in a predetermined direction (such as the horizontal direction of the screen) in a predetermined order (the horizontal direction of the screen, etc.) in the order of the priority of the dictionary data. Here, an example of display in the case where there are five pieces of dictionary data for the acquisition request received by the display control unit 14 and the number of arrays is three data will be described. For dictionary data of five data, suppose that the first-ranked medical dictionary data “xxx.dic”, the second-ranked medical dictionary data “yyy.dic”, and the third-ranked medical dictionary data “zzz” in order of priority. .Dic ”, the fourth-ranked medical dictionary data“ vvv.dic ”, and the fifth-ranked medical dictionary data“ uu.dic ”. The standard dictionary data stored in the storage unit 10 of the second report terminal 30A and not related to the acquisition request is “AAA.dic”.

  In this example, there are five pieces of dictionary data related to the acquisition request. When combined with the standard dictionary data in the second report terminal 30A, there are six pieces of medical dictionary data. However, in this example, the selection screen setting information received from the cloud server 1 is set to arrange three selection screens for each medical dictionary data. Here, according to the setting information, the display control unit 14 determines conversion candidates for three dictionary data to be displayed first among conversion candidates existing for six dictionary data. Temporarily, the first order data “xxx.dic”, the second order data “yyy.dic”, and the medical dictionary with the lowest priority order are arranged in order from the left as the breakdown of the three data to be displayed first in the setting information. If it is set to display the data “uu.dic”, the display control unit 14 determines the dictionary data to be displayed and the arrangement order thereof based on the setting and the second priority information of each dictionary data. To do. In the setting information, the first and second conversion candidates to be displayed are set according to the second priority information, and the standard dictionary data in each report terminal is selected for the third selection screen. The structure set to may be sufficient. In this case, “xxx.dic”, “yyy.dic” and “AAA.dic” are determined as conversion candidates for the dictionary data to be displayed first.

  In addition, the display control unit 14 can switch the displayed conversion candidate selection screen to another selection screen according to the setting information. For example, the display control unit 14 displays the conversion candidate selection screen displayed on the display unit 6 as another dictionary according to the switching operation by the user via the operation unit 8 as well as the dictionary data displayed first. It is possible to switch to and display the conversion candidate selection screen based on the data.

<< Display control unit: Example of processing after selection operation >>
When the user selects one of the conversion candidates via the operation unit 8 on any of the conversion candidate selection screens as illustrated in FIG. 4B, the terminal-side control unit 2 selects the conversion candidate selected from the operation unit 8. Receive input. For example, according to the selection operation, the type of dictionary data and the order of priority of conversion candidates in the dictionary data (first priority information) are input from the operation unit 8 to the terminal-side control unit 2. The terminal-side control unit 2 temporarily stores the information and sends the information to the display control unit 14. Based on such information, the display control unit 14 reflects the converted characters corresponding to the selected conversion candidate in the display column of the interpretation report.

  Here, when the user performs an operation to confirm the converted character displayed via the operation unit 8, the terminal-side control unit 2 confirms the converted character and causes the display control unit 14 to finish displaying the selection screen. Send instructions. Upon receiving the instruction, the display control unit 14 ends the display of the selection screen using each dictionary data. As a result, the conversion candidate selection screen is not displayed on the display unit 6.

  In addition, there is a case where none of the converted characters desired by the user corresponds to the conversion candidate indicated by each dictionary data. In that case, the user performs a character conversion operation using the standard dictionary data (for example, AAA.dic) or the like so that a desired converted character is displayed via the operation unit 8. Since the post-conversion character based on the conversion operation is a conversion candidate not included in any of the dictionary data, the terminal-side control unit 2 additionally registers the post-conversion character in one or more medical dictionary data or the like It may be. For example, the terminal-side control unit 2 additionally registers (stores) the converted character in the medical dictionary data or the like stored in the storage unit 10. The additional registration may be for all dictionary data stored in the storage unit 10 or only for dictionary data acquired from the cloud server 1. Alternatively, the user may select dictionary data for which additional characters to be converted are to be registered.

  As another example, each dictionary data may have a screen data of an editing screen that enables conversion candidates to be edited. In this case, the user performs an operation for additionally registering a desired conversion candidate on the editing screen. For example, when an operation for displaying the screen data of the editing screen included in each dictionary data is executed by the user via the operation unit 8, the terminal-side control unit 2 edits the dictionary data related to the operation from the storage unit 10. Read screen data. The display control unit 14 receives the editing screen data read from the terminal-side control unit 2 and causes the display unit 6 to display the editing screen of the dictionary data. Further, the user inputs an input character and a converted character on the editing screen via the operation unit 8 and performs a confirmation operation. By this operation, the terminal-side control unit 2 additionally stores a new conversion candidate in the dictionary data in the storage unit 10.

  The terminal-side control unit 2 makes a request for updating the medical dictionary data in the medical dictionary data storage unit 7 of the cloud server 1 based on the conversion candidate data of the additionally registered medical dictionary data. For example, the terminal-side control unit 2 transmits the file name of the additionally registered medical dictionary data and the additionally registered conversion candidate data to the cloud server 1 via the transmission / reception unit 4. Note that the conversion candidate data may include the first priority information of the conversion candidate. The cloud server 1 additionally stores the conversion candidate in the medical dictionary data having the same file name in the medical dictionary data storage unit 7 (details will be described later). At this time, additional registration log information or the like may be associated with the conversion candidate data transmitted from the report terminal to the cloud server 1. That is, the log information includes application identification information used for additional registration, additional registered user identification information, report terminal identification information, and the like.

  Further, the terminal-side control unit 2 transmits the additionally registered conversion candidates to the cloud server 1 at a predetermined timing. For example, it is transmitted at any time according to the additional registration process by the terminal-side control unit 2. Further, it may be transmitted when there is an operation for terminating the application used for the additional registration. Further, it may be transmitted at the time of system logout of the report terminal used for additional registration. Further, it may be transmitted from the report terminal stop operation (shutdown operation) used for the additional registration until the report terminal is turned off. The “additionally registered conversion candidate” corresponds to an example of “update information”.

  The update process of the medical dictionary data in the medical dictionary data storage unit 7 will be described in the description of the first report terminal 20.

(Cloud server operation)
Next, the operation of the cloud server 1 will be described with reference to FIG. FIG. 5 is a flowchart showing an outline of the operation of the cloud server 1 according to the first embodiment. FIG. 5 shows an outline of the operation of the cloud server 1 related to acquisition of medical dictionary data. The operation of the cloud server 1 related to new registration and update of medical dictionary data is shown in FIG.

<Step 01>
The main control unit 3 of the cloud server 1 receives a medical dictionary data acquisition request using attribute information as a search query from the second report terminal 30A via the transmission / reception unit 5 (corresponding to an example of “attribute information reception step”). .

<Step 02>
The main control unit 3 determines whether the attribute information in the acquisition request is appropriate. For example, the main control unit 3 determines whether the format of the attribute information in the acquisition request matches any of the various attribute information formats in the dictionary DB table. In the case where the report terminal that has transmitted the acquisition request is configured to execute the attribute information determination process, the cloud server 1 does not perform the process of S02.

<Step 03>
As a result of the determination in S02, when the attribute information in the acquisition request is determined to be appropriate (S02; Yes), the main control unit 3 outputs a search processing execution instruction to the acquisition unit 9. The acquisition unit 9 receives the instruction, and searches corresponding medical dictionary data from the dictionary DB of the medical dictionary data storage unit 7 based on the attribute information related to the acquisition request. The acquisition unit 9 searches for medical dictionary data included in the acquisition request and corresponds to all attribute information related to the attribute information determination process, or uses at least one of various attribute information included in the acquisition request. Search for.

<Step 04>
As a result of the determination in S02, when it is determined that the attribute information in the acquisition request is not appropriate (S02; No), the main control unit 3 sends the attribute information determination error data to the report terminal related to the acquisition request via the transmission / reception unit 5. Send. In this case, the cloud server 1 ends the series of acquisition processing of medical dictionary data.

<Step 05>
The acquisition unit 9 determines whether the medical dictionary data related to the acquisition request exists in the medical dictionary data storage unit 7 as a result of the search process in S03.

<Step 06>
As a result of the determination in S05, when it is determined that there is medical dictionary data related to the acquisition request (S05; Yes), the acquisition unit 9 extracts the corresponding medical dictionary data from the medical dictionary data storage unit 7 (“acquire medical dictionary information”). Corresponds to an example of “step”). Furthermore, the acquisition part 9 acquires each attribute information linked | related with medical dictionary data with applicable medical dictionary data. When there are a plurality of corresponding medical dictionary data, the acquisition unit 9 acquires each attribute information associated with each medical dictionary data.

  In S03, when the acquisition unit 9 performs a search using at least one of various attribute information included in the acquisition request, and a plurality of identical medical dictionary data corresponds as a search result, only one data is stored. To get. In this case, only the corresponding attribute information in the dictionary DB is acquired together with the medical dictionary data.

<Step 07>
As a result of the determination in S05, when it is determined that there is no medical dictionary data related to the acquisition request (S05; No), the acquisition unit 9 transmits display screen data indicating a determination error indicating that there is no corresponding data via the transmission / reception unit 5. To the report terminal related to the acquisition request. In this case, the cloud server 1 ends the series of acquisition processing of medical dictionary data.

<Step 08>
The medical dictionary data extracted in S06 is sent to the second report terminal 30A via the transmission / reception unit 5 while maintaining the association between the medical dictionary data and each attribute information by the main control unit 3 (“dictionary information transmission step”). Corresponds to an example). The main control unit 3 may send a search log according to the acquisition request to the second report terminal 30A together with these data.

(Operation of the second report terminal)
Next, the operation of the second report terminal that receives medical dictionary data in response to an acquisition request will be described with reference to FIG. FIG. 6 is a flowchart showing an outline of the operation of the second report terminal 30A according to the first embodiment. FIG. 6 shows an outline of the operation of the second report terminal 30 </ b> A, but the same operation can be executed in all report terminals capable of data communication with the cloud server 1.

  In addition, before the process after acquisition request transmission demonstrated below, preparation and transmission of an acquisition request are performed by the 2nd report terminal 30A. For example, the second report terminal 30 </ b> A transmits an instruction to display the acquisition request creation screen executed via the operation unit 8 to the cloud server 1. Further, the second report terminal 30A receives the screen data of the acquisition request creation screen and displays the acquisition request creation screen. Further, when the acquisition request creation screen is displayed, the user inputs attribute information through the operation unit 8 or the like.

<Step 11>
When the acquisition request creation screen is displayed on the display unit 6 of the second report terminal 30A, when the acquisition request creation completion operation is performed via the operation unit 8 of the second report terminal 30A, the input attribute information is displayed. The associated acquisition request is transmitted to the cloud server 1.

<Step 12>
As a result of the acquisition request, the terminal-side control unit 2 receives the result of the medical dictionary data acquisition request from the cloud server 1. The terminal-side control unit 2 determines whether the cloud server 1 has received medical dictionary data as a result of the acquisition request. That is, the terminal-side control unit 2 determines whether medical dictionary data has been received or display screen data indicating various errors has been received.

<Step 13-1>
As a result of the determination in S12, when it is determined that display screen data indicating an error such as an attribute error or a search error has been received (S12; No), the main control unit 3 sends the display screen data to the display control unit 14. . The display control unit 14 causes the display unit 6 to display an acquisition request error based on the display screen data. The terminal-side control unit 2 ends the following medical dictionary data acquisition process. Note that a selection screen for re-creating an acquisition request or the like may be displayed.

<Step 13-2>
When it is determined that the medical dictionary data has been received as a result of the determination in S12 (S12; Yes), the main control unit 3 stores the attribute information in the storage unit 10 together with the medical dictionary data. When the main control unit 3 also receives a search log or the like, the main control unit 3 also stores the search log or the like together.

<Step 14>
When a document creation application activation operation such as an interpretation report is executed after storing in S13-2, the main control unit 3 reads the document creation application corresponding to the operation from the storage unit 10 and sends it to the display control unit. The display control unit 14 causes the display unit 6 to display a display screen based on the received application.

<Step 15>
The conversion unit 12 compares the format of each dictionary data stored in the storage unit 10 with a dictionary format that can be used in the started application at a predetermined timing such as when the application is started in S14. As a result of the comparison, the conversion unit 12 reads the dictionary data determined to be usable in the activated program. Further, the conversion unit 12 reads the second priority information together with the dictionary data.

<Step 16>
When an input from the operation unit 8 is received via the terminal-side control unit 2 after the application is started in S14, the terminal-side control unit 2 displays the pre-conversion characters (unconverted characters) converted by the conversion unit 12 according to the input. The display control unit 14 is temporarily displayed. The conversion unit 12 temporarily stores the pre-conversion character.

<Step 17>
Furthermore, the conversion unit 12 receives an instruction for conversion processing from the terminal-side control unit 2 or the like at a predetermined timing (such as when character conversion is performed via the operation unit 8). In addition, before receiving the operation of character conversion, it is also possible to display a candidate for predictive conversion corresponding to the input character. In this case, the terminal-side control unit 2 responds to the above input by the conversion unit. Send instructions to 12. The conversion unit 12 determines whether there is a conversion candidate corresponding to the stored pre-conversion character from each of the read dictionary data. Moreover, the conversion part 12 memorize | stores temporarily the conversion candidate applicable to the said input content for every dictionary data.

<Step 18>
The display control unit 14 receives, for example, conversion candidates for each dictionary data, first priority information and second priority information, and data related to conversion candidate selection screens and selection screen arrangement displays from the conversion unit 12. The display control unit 14 assigns a plurality of conversion candidates in each dictionary data to the selection screen data in order of priority based on the first priority information. Further, the display control unit 14 determines the order of priority of each dictionary data based on the second priority information. Further, the display control unit 14 determines the arrangement of the conversion candidate selection screens (window display or the like; see the lower left column in FIG. 4B) in the priority order of the specified dictionary data based on the data related to the arrangement display of the selection screen.

  Further, the display control unit 14 displays the conversion candidate selection screen on the interpretation report creation screen in accordance with the information on the determined arrangement and the information on the position and size of the conversion candidate selection screen set in advance. Control to display on the screen.

<Step 19>
When the user selects one of the conversion candidates via the operation unit 8, the terminal-side control unit 2 determines the type of dictionary data and the conversion candidate in the dictionary data according to the conversion candidate selected from the operation unit 8. A priority order (first priority information) is input.

<Step 20>
The terminal-side control unit 2 specifies and temporarily stores conversion candidates selected from the type of dictionary data and the order of priority of conversion candidates in the dictionary data, and sends the information to the display control unit 14. .

<Step 21>
Based on the information received from the terminal-side control unit 2, the display control unit 14 reflects the converted characters corresponding to the selected conversion candidate in the display column of the interpretation report.

(Overall configuration of the first report terminal)
Next, the overall configuration of the first report terminal according to the first embodiment will be described in the example of the first report terminal 20 with reference to FIG. As shown in FIG. 3, the second report terminal 30 </ b> A includes a main control unit 21, a transmission / reception unit 22, a display unit 23, an operation unit 24, a display control unit 25, a conversion unit 26, and a storage unit 27. . In one example, the first report terminal 20 is a report terminal that is normally used by a user such as a doctor. The storage unit 27 stores medical dictionary data for creating a document of a medical institution.

  Note that the hardware configuration of the first report terminal 20, such as the main control unit 21, the transmission / reception unit 22, the display unit 23, the operation unit 24, the display control unit 25, the conversion unit 26, and the storage unit 27, is the second report terminal 30A. The explanation is omitted because it is the same.

<Medical dictionary data registration process>
In response to an operation from the operation unit 24, the main control unit 21 transmits a request for registration screen data of medical dictionary data to the cloud server 1 via the transmission / reception unit 22. The main control unit 21 sends screen data to the display control unit 25. The display control unit 25 causes the display unit 23 to display a registration screen for medical dictionary data based on the screen data. Note that, as described in display processing example 1 and example 2 of the acquisition request creation screen in the display control unit 14 of the second report terminal 30A, the medical dictionary data registration screen may be displayed via a web browser.

  When the selection operation of the medical dictionary data stored in the storage unit 27 and the input of the attribute information in the medical dictionary data are input on the registration screen, the main control unit 21 receives the selected medical dictionary data and the input Attribute information is temporarily stored. Further, when an operation for confirming medical dictionary data to be registered when the screen is displayed is performed via the operation unit 24, the temporarily stored attribute information and medical dictionary data are transmitted by the main control unit 21 via the transmission / reception unit 22. To the cloud server 1.

  The dictionary file name of the medical dictionary data may be input when the attribute information is input, and may be configured to prompt the input of the dictionary file name after the confirmation operation. Of the attribute information, the user name, the name of the medical institution to which the user belongs, the name of the hospital group to which the medical institution to which the user belongs, the department name and account information to which the user belongs, and the identification information thereof may not be input by the user. The main control unit 21 may obtain a medical dictionary data registration program. That is, the main control unit 21 acquires the identification information from various information such as system information stored in advance in the first report terminal 20.

  Another example of medical dictionary data registration processing will be described. In this example, the main control unit 21 transmits medical dictionary data to the cloud server 1 at a predetermined timing. For example, when there is an end operation of an application that uses medical dictionary data, first, the main control unit 21 acquires attribute information from system information or the like according to a registration program for medical dictionary data. Further, the medical dictionary data name and medical dictionary data corresponding to the attribute information are transmitted to the main control unit 21. As another example, these processes are performed from the stop operation (shutdown operation) of the report terminal (first report terminal 20 or the like) in which medical dictionary data is stored until the report terminal is turned off. Also good. In addition, these processes may be performed at the time of system logout of the report terminal in which medical dictionary data is stored.

(Cloud server registration process)
Next, a new registration process for medical dictionary data in the cloud server 1 will be described. When the cloud server 1 receives medical dictionary data and attribute information associated therewith together with a registration request for medical dictionary data from the first report terminal 20, the cloud server 1 sends it to the main control unit 3 via the transmission / reception unit 5. The main control unit 3 determines whether the format of the attribute information in the registration request corresponds to any of various attribute information formats in the dictionary DB table.

  When the main control unit 3 determines that the format of the attribute information related to the registration request is not compatible with the format in the dictionary DB table, the main control unit 3 outputs attribute error determination data to the report terminal that has transmitted the registration request. Upon receiving the error determination data, the report terminal displays a registration request error based on the data. When the main control unit 3 determines that the attribute information related to the registration request matches the format in the table of the dictionary DB, the main control unit 3 performs registration processing of medical dictionary data.

  If the main control unit 3 corresponds to various attribute information in the dictionary DB even with at least one of the attribute information in the acquisition request, the other attribute information in the acquisition request does not correspond to the various attribute information. It is good also as a structure which judges that it is good. However, in this case, the attribute information registered in the dictionary DB of the medical dictionary data storage unit 7 is only the information that matches the dictionary DB.

  On the other hand, if all of the attribute information in the acquisition request does not correspond to the corresponding attribute information format of the dictionary DB, the main control unit 3 determines that the attribute information is not applicable, and outputs attribute error determination data. It is good also as a structure.

  If the main control unit 3 determines that the format of the attribute information related to the registration request is compatible with the format in the table of the dictionary DB, the main dictionary 3 associates the medical dictionary data related to the registration request with the attribute information compatible with the format, and medical dictionary data The data is stored in the dictionary DB of the storage unit 7. Here, in the registration request attribute information determination process, if the registration request does not include all of all types of attribute information set in the dictionary DB, the medical dictionary has a configuration that outputs an attribute information error. All types of attribute information are registered together with the data. On the other hand, if the registration request includes one or more pieces of attribute information among all types of attribute information set in the dictionary DB, if the configuration is such that the attribute information is determined to be compatible, the registration request is applicable. Only attribute information is registered in association with medical dictionary data.

  When the registration process of the medical dictionary data is completed, the main control unit 3 transmits a process log to the report terminal for the registration process in any case (registration enabled / error).

(Cloud server update process)
Next, medical dictionary data update processing (additional registration processing) in the cloud server 1
Will be described. When the cloud server 1 receives a new conversion candidate data and attribute information associated therewith together with a request for updating medical dictionary data from a report terminal such as the second report terminal 30A, the main control unit via the transmission / reception unit 5 Send to 3. The main control unit 3 determines whether the format of the attribute information in the registration request corresponds to any of various attribute information formats in the dictionary DB table. The “update request” and “new conversion candidate data” correspond to an example of “update information”.

  When the main control unit 3 determines that the format of the attribute information relating to the update request does not match the format in the table of the dictionary DB, and the case where it is determined that the format matches, the same processing as that for registering medical dictionary data is performed. . However, in the update process, the main control unit 3 specifies medical dictionary data to be updated based on the update request data, and additionally stores the new conversion candidate data in the specified medical dictionary data. Note that the conversion candidate data includes input characters and corresponding converted characters. Further, the conversion candidate data may include first priority information of the conversion candidate. In either case, the main controller 3 determines and stores the priority order of new conversion candidates in the medical dictionary data to be updated.

  When the update process of the medical dictionary data is completed, the main control unit 3 transmits the process log to the report terminal related to the update process in any case (update possible / error).

(Operation of the cloud server 1 related to the update process)
Next, the operation of the cloud server 1 that receives a new conversion candidate for medical dictionary data in response to an update request will be described with reference to FIG. FIG. 9 is a flowchart showing the outline of the operation of the cloud server 1 according to the first embodiment, and shows the outline of the operation from the update request to the transmission of the log related to the update process.

<Step 31>
The main control unit 3 of the cloud server 1 receives an update request for medical dictionary data from the second report terminal 30 </ b> A via the transmission / reception unit 5. At this time, the update request includes attribute information and a new conversion candidate for medical dictionary data characterized by the attribute information. Note that the conversion candidate data may include the first priority information of the conversion candidate.

<Step 32>
The main control unit 3 determines whether the format of the attribute information in the update request matches any of the various attribute information formats in the dictionary DB table. In the case where the report terminal that has transmitted the update request is configured to execute the attribute information determination process, the cloud server 1 does not perform the process of S32.

<Step 33-1>
As a result of the determination in S32, when it is determined that the attribute information in the update request is not appropriate (S32; No), the main control unit 3 sends the attribute information determination error data to the report terminal related to the update request via the transmission / reception unit 5. Send. In this case, the cloud server 1 ends a series of update processing of medical dictionary data.

<Step 33-2>
As a result of the determination in S32, when it is determined that the attribute information in the update request is appropriate (S02; Yes), the main control unit 3 applies from the dictionary DB of the medical dictionary data storage unit 7 based on the attribute information related to the update request. The medical dictionary data to be specified is specified. The main control unit 3 specifies medical dictionary data included in the update request and corresponds to all attribute information related to the attribute information determination process, or uses at least one of various attribute information included in the update request. To identify.

<Step 34>
The main control unit 3 additionally stores new conversion candidates after setting the priority order for the medical dictionary data specified in S33-2 based on the first priority information related to the update request.

<Step 35>
After the update process of S34 or after the above error determination, the main control unit 3 creates a log of the result of the update process. For example, the main control unit 3 creates, as a log, information on attribute information in which an error has occurred and that update processing has resulted in an error. Or the log containing the information of the attribute information adapted by the main control unit 3 and the progress of the additionally stored process is created.

<Step 36>
The main control unit 3 transmits the log created in S35 to the report terminal such as the second report terminal 30A via the transmission / reception unit 5. Note that the log may be transmitted only when the log is requested together with the update request from the report terminal related to the update request.

(Action / Effect)
The operation and effect of the medical system 100 according to the first embodiment described above will be described.

  A user of a report terminal uses a registered term to improve the efficiency of document creation when creating a document such as an interpretation report or a medical report in a report terminal (such as the first report terminal 20) that is frequently used. Medical dictionary data used for conversion of input characters is created and stored. The medical system 100 in this embodiment manages this medical dictionary data in the cloud server 1 and can be used in other report terminals connected to the cloud server 1. Other report terminals (second report terminal 30A, third report terminal 30B, etc.) are report terminals that are used by the user but are less frequently used.

  According to such a configuration, even when the user uses the other report terminal, it is possible to use medical dictionary data in the report terminal that is frequently used. As a result, it is possible to use similar medical dictionary data between different medical institutions or between different medical departments. Therefore, since the same content can be described in the same expression in a document of a medical institution, it is possible to prevent variations in expression in a document whose expression should be unified.

  Further, the medical system 100 according to the present embodiment does not need to perform an operation for registering or updating the same medical dictionary data in all terminals of different medical institutions or different medical departments. Therefore, it is possible to reduce the user's labor.

  As described above, the medical system 100 can efficiently share medical dictionary data between different report terminals in a medical institution.

[Second Embodiment]
Next, the medical system 100 according to the second embodiment will be described. The medical dictionary data acquired in the search process of the acquisition unit 9 may be data in a format that cannot be used in the report terminal (second report terminal 30A or the like) related to the medical dictionary data acquisition request. In the second embodiment, for example, the medical dictionary data acquired by the cloud server 1 determines whether or not the report terminal related to the acquisition request can be used. As a result of the determination by the cloud server 1, when it is determined that the cloud server 1 cannot be used, the cloud server 1 performs a conversion process of the format of the medical dictionary data so that it can be used in the report terminal.

  For example, the cloud server 1 receives, as attribute information, application identification information indicating a document creation application in the second report terminal 30 </ b> A together with a medical dictionary data acquisition request from the second report terminal 30 </ b> A via the transmission / reception unit 5. Here, as in the first embodiment, the attribute information determination process is performed in the main control unit 3, and the search process is performed by the acquisition unit 9. When there is acquired medical dictionary data as a result of the search processing, the main control unit 3 extracts application identification information from the attribute information of the medical dictionary data. The main control unit 3 compares the extracted application identification information with the application identification information related to the acquisition request.

  As a result of the comparison, if these application identification information corresponds, the main control unit 3 determines that the report terminal can use it, and sends the medical dictionary data and attribute information to the second via the transmission / reception unit 5. Transmit to the report terminal 30A.

  On the other hand, when these pieces of application identification information do not correspond, the main control unit 3 determines that the medical dictionary data cannot be used in the report terminal relating to the acquisition request. The main control unit 3 performs conversion processing on the medical dictionary data determined to be unusable. For example, the format of the acquired medical dictionary data is converted into the format of application identification information related to the acquisition request. The processed medical dictionary data and attribute information that can be used in the report terminal by the conversion process are sent to the second report terminal 30A via the transmission / reception unit 5.

  Note that application identification information may not be included in the acquisition request. In that case, when receiving the medical dictionary data and the attribute information from the acquisition unit 9, the main control unit 3 executes the acquisition request for the application identification information to the report terminal related to the acquisition request. When the main control unit 3 receives the application identification information in the report terminal, the main control unit 3 determines whether or not the use including the above comparison is possible. Further, the main control unit 3 performs a conversion process or the like according to the determination result in the same manner as described above.

  In another example, the main control unit 3 may be configured not to make a determination as to whether or not use is possible, including the above comparison. In this case, the main control unit 3 sends medical dictionary data, attribute information, and a program for executing the determination and conversion processing. In this configuration, the determination and the conversion process are executed in a report terminal such as the second report terminal 30A based on the program.

(Action / Effect)
Operations and effects of the medical system 100 according to the second embodiment described above will be described.

  The medical system 100 according to the second embodiment manages medical dictionary data in the cloud server 1 and can be used in other report terminals connected to the cloud server 1. According to such a configuration, it is possible to use the same medical dictionary data between different report terminals, and it is possible to prevent variations in expression in a document of a medical institution where the expression should be unified. .

  Further, the medical system 100 determines whether or not the medical dictionary data can be used in the report terminal according to the acquisition request, and performs conversion processing according to the determination result. Therefore, for example, even if the document creation application for each report terminal is different, the same medical dictionary data can be used between different report terminals.

  As described above, the medical system 100 can efficiently share medical dictionary data between different report terminals in a medical institution.

[Third Embodiment]
Next, a medical system 100 according to the third embodiment will be described. As described above, in the attribute information determination process, the attribute information related to the acquisition request matches the dictionary DB of the medical dictionary data storage unit 7, but it may be determined that there is no corresponding medical dictionary data in the search process. In the third embodiment, when it is determined that there is no corresponding medical dictionary data in the search process, medical dictionary data having attribute information close to the attribute information related to the acquisition request is searched as similar medical dictionary data.

  In this configuration, for example, in the cloud server 1, essential attribute information (hereinafter simply referred to as “essential attribute information”) is set among the pieces of attribute information included in the acquisition request in the attribute information determination process. The essential attribute information is attribute information that is set as the format must be adapted to the dictionary DB among the attribute information included in the acquisition request. In one example, of the attribute information of medical dictionary data, user department identification information (radiology etc.) corresponds. In another example, it may be application identification information.

  In the search process, when it is determined that there is no medical dictionary data corresponding to the acquisition request including the required attribute information, the main control unit 3 removes attribute information other than the required attribute information from the search query and executes the search process again. To do. For example, when the belonging department identification information is essential attribute information and the belonging department is the radiology department, the main control unit 3 uses the condition of the radiology department for the re-search process, and searches the user identification information related to the acquisition request with the search query. The search process is executed again. That is, even if there is no medical dictionary data that matches the acquisition request, the main control unit 3 searches for medical dictionary data with similar conditions.

  When medical dictionary data with similar conditions is searched, the main control unit 3 requests the attribute information used for the search at the time of re-search, the medical dictionary data, and the search log via the transmission / reception unit 5. Send to report terminal (second report terminal 30A etc.).

  Here, it is possible to combine the second embodiment. For example, in the re-search, if medical dictionary data that matches the department identification information of the radiology department but uses a different application (application identification information) is searched, the main control unit 3 or the like converts the data in the second embodiment. You may comprise so that a process may be performed.

  The interface storage unit 11 stores display screen data for displaying that the acquired medical dictionary data is similar medical dictionary data, attribute information (such as user identification information) of the similar medical dictionary data, and the like. It may be. The main control unit 3 sends the display screen data to the medical dictionary data related to the acquisition request together with the similar medical dictionary data.

(Action / Effect)
Operations and effects of the medical system 100 according to the third embodiment described above will be described.

  The medical system 100 according to the third embodiment manages medical dictionary data in the cloud server 1 and can be used in other report terminals connected to the cloud server 1. According to such a configuration, it is possible to use the same medical dictionary data between different report terminals, and it is possible to prevent variations in expression in a document of a medical institution where the expression should be unified. .

  Further, the medical system 100 searches for medical dictionary data with similar conditions even when there is no medical dictionary data that matches the acquisition request. Therefore, for example, even when the medical dictionary data of a predetermined user is searched and not searched, it is possible to search medical dictionary data of other users in the same department as the predetermined user. That is, when using a report terminal that is not frequently used, the user may not know the attribute information to be searched or may have forgotten even though he / she wants to use medical dictionary data. Even in such a case, according to the above configuration, similar medical dictionary data can be acquired.

  As described above, the medical system 100 can efficiently share medical dictionary data between different report terminals in a medical institution.

[Fourth Embodiment]
Next, a medical system 100 according to the fourth embodiment will be described. As a result of the acquisition request, a plurality of medical dictionary data may be acquired in a report terminal such as the second report terminal 30A. However, the usable medical dictionary data may be different for each medical dictionary data due to a format difference or the like as described above. In the fourth embodiment, control is performed based on the attribute information so that the plurality of medical dictionary data are used only for necessary applications. This program is stored in the interface storage unit 11, for example.

(First example)
For example, the second report terminal 30A receives the attribute information associated with the data and the identification program of the activated application together with the medical dictionary data from the cloud server 1 via the transmission / reception unit 4. The activated application identification program is a program for determining whether the application activated in the report terminal and the medical dictionary data correspond to each other based on the application identification information.

  In one example, the terminal-side control unit 2 reads each dictionary data when reading a document creation application from the storage unit 10 according to an operation. Moreover, the terminal side control part 2 extracts application identification information from the attribute information concerning each dictionary data. Furthermore, the terminal side control part 2 reads an identification program. The terminal-side control unit 2 determines whether each dictionary data corresponds to the activated application based on each extracted application identification information according to the program. The terminal-side control unit 2 instructs to use only the dictionary data determined to be supported by the conversion unit 12 among the read dictionary data for the conversion process.

(Second example)
In the second example, it is assumed that usage identification information is set as essential attribute information in the attribute information determination process of the cloud server 1. The usage identification information is a type of sentence of a medical institution to be created, for example, for interpretation report creation, finding report creation for a specific medical department, for thesis creation, for medical accounting. The second report terminal 30A receives, along with the medical dictionary data, from the cloud server 1 via the transmission / reception unit 4 and attribute screen information associated with the data and display screen data for performing a use application selection operation. The display screen data is data for the user to select each use purpose set in the attribute information using the operation unit 8. Further, it is assumed that use attribute identification information as essential attribute information is included in the attribute information of the acquired medical dictionary data.

  In one example, the terminal-side control unit 2 reads each dictionary data when reading a document creation application from the storage unit 10 according to an operation. Further, the terminal-side control unit 2 extracts use purpose identification information from the attribute information related to each dictionary data. Further, the terminal-side control unit 2 reads out the display screen data and sends it to the display control unit 14. The display control unit 14 causes the display unit 6 to display a use application selection screen based on the display screen data. When any usage is selected by the user via the operation unit 8, usage identification information corresponding to the operation is sent to the conversion unit 12 via the terminal-side control unit 2. The conversion unit 12 reads only the storage unit 10 corresponding to the selected use purpose identification information. The conversion unit 12 performs an input character conversion process based only on medical dictionary data corresponding to the use purpose identification information. However, normal dictionary data stored in advance in the second report terminal 30A may be read out regardless of the usage identification information.

(Action / Effect)
Operations and effects of the medical system 100 according to the fourth embodiment described above will be described.

  The medical system 100 according to the fourth embodiment manages medical dictionary data in the cloud server 1 and can be used in other report terminals connected to the cloud server 1. According to such a configuration, it is possible to use the same medical dictionary data between different report terminals, and it is possible to prevent variations in expression in a document of a medical institution where the expression should be unified. .

  Further, the medical system 100 performs control based on the attribute information so that the plurality of medical dictionary data are used only for necessary applications. Therefore, it is possible to select the use application of the medical dictionary required by the user at the report terminal and display conversion candidates based on the medical dictionary data corresponding to the application.

  As described above, the medical system 100 can efficiently share medical dictionary data between different report terminals in a medical institution.

[First Modification]
Next, a medical system 200 according to a modification example of the first to fourth embodiments will be described as a first modification example. FIG. 10 is a schematic block diagram illustrating an example of a cloud server 1A according to the first modification. As illustrated in FIG. 10, the cloud server 1A includes a main control unit 3A, a transmission / reception unit 5A, a correspondence relationship storage unit 7A, and an acquisition unit 9A. In this configuration, unlike the above embodiment, medical dictionary data is not stored in the cloud server 1A but is stored in the file server 7B. That is, the cloud server 1A may be configured to have only a function of managing medical dictionary data in the medical system 200.

  The correspondence storage unit 7A stores the storage location of the medical dictionary data, the medical dictionary data name, and the correspondence of each attribute information. The main control unit 3 refers to the correspondence storage unit 7A in the attribute information determination process, and acquires medical dictionary data and attribute information from the file server 7B.

(Operation of the cloud server of the first modification)
Next, the operation of the cloud server 1A according to the first modification will be described with reference to FIG. 11 and FIG. 11 and 12 are flowcharts illustrating an outline of the operation of the cloud server 1A according to the first modification of the embodiment. 11 and 12 show an outline of the operation of the cloud server 1A related to the acquisition of medical dictionary data.

<Step 51>
The main control unit 3A of the cloud server 1A receives a medical dictionary data acquisition request using attribute information as a search query from the second report terminal 30A via the transmission / reception unit 5 (corresponding to an example of “attribute information reception step”). .

<Step 52>
The main control unit 3A determines whether the attribute information in the acquisition request is appropriate. For example, the main control unit 3A determines whether the format of attribute information in the acquisition request matches any of various attribute information formats in the table of the correspondence storage unit 7A. In the case where the attribute information determination process is executed at the report terminal that has transmitted the acquisition request, the cloud server 1A does not perform the process of S52.

<Step 53>
As a result of the determination in S52, when the attribute information in the acquisition request is determined to be appropriate (S52; Yes), the main control unit 3A outputs a search processing execution instruction to the acquisition unit 9A. The acquisition unit 9A receives the instruction, and searches for the corresponding medical dictionary data from the file server 7B via the transmission / reception unit 5 based on the attribute information related to the acquisition request. The acquisition unit 9A searches for medical dictionary data included in the acquisition request and corresponds to all attribute information related to the attribute information determination process, or uses at least one of various attribute information included in the acquisition request. Search for.

<Step 54>
As a result of the determination in S52, when it is determined that the attribute information in the acquisition request is not appropriate (S52; No), the main control unit 3A sends the attribute information determination error data to the report terminal that receives the acquisition request via the transmission / reception unit 5A. Send. In this case, the cloud server 1A also ends a series of acquisition processes for medical dictionary data.

<Step 55>
The acquisition unit 9A determines whether or not medical dictionary data related to the acquisition request exists in the file server 7B as a result of the search processing in S53.

<Step 56>
As a result of the determination in S55, if it is determined that there is medical dictionary data related to the acquisition request (S55; Yes), the acquisition unit 9A specifies the corresponding medical dictionary data storage location from the file server 7B (“medical dictionary information acquisition step” Corresponds to an example). Furthermore, the acquisition unit 9A acquires each attribute information associated with the medical dictionary data together with the corresponding medical dictionary data. When there are a plurality of corresponding medical dictionary data, the acquisition unit 9 acquires each attribute information associated with each medical dictionary data.
<Step 57>
As a result of the determination in S55, when it is determined that there is no medical dictionary data related to the acquisition request (S55; No), the acquisition unit 9A acquires determination error data indicating that there is no corresponding data via the transmission / reception unit 5A. Send to the requesting reporting terminal. In this case, the cloud server 1A also ends a series of acquisition processes for medical dictionary data.

<Step 58>
The cloud server 1A sends an acquisition request for medical dictionary data stored in the storage location of the medical dictionary data specified in S57 to the file server 7B via the transmission / reception unit 5A by the main control unit 3 or the like.

<Step 59>
The cloud server 1A receives medical dictionary data related to the acquisition request in S58 from the file server 7B via the transmission / reception unit 5A. In S53, when the acquisition unit 9A searches using at least one of the various attribute information included in the acquisition request, and a plurality of the same medical dictionary data corresponds as a search result, only one data is stored. To get. In this case, only the corresponding attribute information in the dictionary DB is acquired together with the medical dictionary data.

<Step 58>
The medical dictionary data extracted in S56 is sent to the second report terminal 30A via the transmission / reception unit 5A while maintaining the association between the medical dictionary data and each attribute information by the main control unit 3A (“dictionary information transmission step”). Corresponds to an example). The main control unit 3A may send the search log according to the acquisition request to the second report terminal 30A together with these data.

  The file server 7B may be provided with a storage area for storing each data stored in the interface storage unit 11 described in the first embodiment. Each data stored in the interface storage unit 11 may be stored in another file server.

  Also in the medical system according to the first modified example, medical dictionary data can be efficiently shared between different report terminals in a medical institution as in the above embodiment.

[Second Modification]
Next, a medical system 300 according to a modification example of the first to fourth embodiments will be described as a first modification example. FIG. 13 is a schematic block diagram illustrating an example of the first report terminal 20A of the medical system 300 according to the second modification. As shown in FIG. 13, the first report terminal 20A includes a main control unit 21A, a transmission / reception unit 22A, a display unit 23A, an operation unit 24A, a display control unit 25A, and a conversion unit 26A, as in the first to fourth embodiments. In addition to the storage unit 27A, a medical dictionary data storage unit 28A is included. In this configuration, unlike the above embodiment, the medical dictionary data is not stored in the cloud server 1A, and the cloud server 1 acquires from the first report terminal 20A. That is, the cloud server 1A may be configured to have only a function of managing medical dictionary data in the medical system 300.

  The hardware configuration of the first report terminal 20, such as the main control unit 21A, the transmission / reception unit 22A, the display unit 23A, the operation unit 24A, the display control unit 25A, the conversion unit 26A, and the storage unit 27A, is the same as in the above embodiment. Therefore, the explanation is omitted.

  For example, the acquisition unit 9 of the cloud server 1 performs a search process in the same manner as in the first modified example through the attribute information determination process. However, the target of the search process is the medical dictionary data storage unit 28A of the first report terminal 20A.

  The acquisition unit 9 searches medical dictionary data corresponding to attribute information determined to be compatible in the attribute information determination process. If it is determined that there is medical dictionary data as a result of the search, the acquisition unit 9 specifies the storage location of the searched medical dictionary data with reference to the medical dictionary data storage unit 28A of the first report terminal 20A. The main control unit 3 sends an acquisition request for medical dictionary data to the first report terminal 20A through the transmission / reception unit 5 together with information on the storage location specified by the acquisition unit 9.

  The main control unit 21A of the first report terminal 20A receives an acquisition request via the transmission / reception unit 22A, and reads medical dictionary data from the medical dictionary data storage unit 28A based on the storage location information. The read medical dictionary data is sent to the cloud server 1 by the main control unit 21A via the transmission / reception unit 22A. Other configurations in the second modification are the same as those in the above embodiment.

[Third Modification]
Next, a third modification of the first to fourth embodiments will be described. In the medical system in the above-described embodiment, a plurality of medical dictionary data may be searched according to a medical dictionary data acquisition request. In the above-described embodiment, the second report terminal 30A or the like may display conversion candidates based on a plurality of medical dictionary data in parallel for each medical dictionary data, or may display the switching candidates. In this case, when conversion candidates of a plurality of medical dictionary data are displayed, it is necessary to select conversion candidates for each medical dictionary data.

  Accordingly, the third modified example is a configuration in which, for example, the interface storage unit 11 of the cloud server 1 stores display screen data for displaying a conversion candidate display operation for medical dictionary data and an operation manual for the conversion operation. The data of the operation manual is sent to the report terminal concerning the acquisition request together with the medical dictionary data.

  The medical system according to the first to fourth embodiments and the modifications thereof can manage medical dictionary data in a cloud server and can be used in other report terminals connected to the cloud server. According to such a configuration, it is possible to use the same medical dictionary data between different report terminals, and it is possible to prevent variations in expression in a document of a medical institution where the expression should be unified. .

  Moreover, the said 1st-4th embodiment and its modification can be comprised combining suitably.

  Although the embodiment of the present invention has been described, the above-described embodiment has been presented as an example, and is not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

DESCRIPTION OF SYMBOLS 100 Medical system 1 Cloud server 2 Terminal side control part 3 Main control part 7 Medical dictionary data storage part 8 Operation part 11 Interface storage part 12 Conversion part 14 Display control part 20 1st report terminal 28A Medical dictionary data storage part 30A 2nd report Terminal

Claims (19)

A medical system in which a server and a first computer terminal and a second computer terminal can communicate with each other,
A medical dictionary provided in the server, the first computer terminal, or another server and storing a plurality of medical dictionary information associated with attribute information including user identification information or use identification information and capable of communicating with the server A storage unit,
The second computer terminal is
A display unit;
An input unit for inputting attribute information,
Send attribute information input via the input unit to the server,
The server
A medical dictionary information acquisition unit that acquires medical dictionary information associated with the attribute information from the medical dictionary storage unit when the attribute information is received;
Transmitting information based on the acquired medical dictionary information to the second computer terminal;
A medical system characterized by. The user identification information is individual user identification information, user affiliation identification information, or operating system account information used in the terminal,
The medical system according to claim 1. The usage identification information is identification information of an application that uses the medical dictionary information or operating system account information used in a terminal;
The medical system according to claim 1. The first computer terminal is disposed at a user's affiliation; and the second computer terminal is disposed at a location other than the affiliation;
The server receives, from the first computer terminal, new medical dictionary information associated with the attribute information or update information of the medical dictionary information associated with the attribute information, and new information is stored in the medical dictionary storage unit. Storing the medical dictionary information or updating the medical dictionary information stored in the medical dictionary storage unit based on the update information;
The medical system according to claim 1. The server receives update information of the medical dictionary information associated with the attribute information from the second computer terminal, and updates the medical dictionary information stored in the medical dictionary storage unit based on the update information;
The medical system according to claim 4. The server causes the second computer terminal to transmit the medical dictionary information associated with the attribute information or the update information of the medical dictionary information;
The medical system according to claim 1. The second computer terminal includes a terminal-side storage unit that stores an application using the medical dictionary information and a plurality of types of dictionary information including the medical dictionary information received from the server, and at the time of executing the application When receiving an input from the input unit, the display unit displays the conversion candidates for the input based on the plurality of types of dictionary data in parallel.
The medical system according to claim 1. The medical dictionary storage unit stores a database that associates the medical dictionary information with the attribute information;
The medical system according to any one of claims 1 to 3. The medical dictionary storage unit is provided in the first computer terminal,
The medical dictionary information acquisition unit in the server acquires the medical dictionary information from the first computer terminal based on the attribute information;
The medical system according to claim 1, wherein: The medical dictionary storage unit is provided in the other server,
The medical dictionary information acquisition unit in the server acquires the medical dictionary information from the other server based on the attribute information;
The medical system according to claim 1, wherein: The medical dictionary storage unit stores a plurality of types of medical dictionary information,
The medical dictionary information acquisition unit acquires all or part of the plurality of types of medical dictionary information based on the attribute information;
The medical system according to claim 1. The medical dictionary information includes a plurality of conversion candidates corresponding to the input, and first priority information indicating the priority of each of the conversion candidates in the medical dictionary,
When the second computer terminal receives an input from the input unit during execution of an application that uses the medical dictionary information, the conversion candidates are displayed in order of priority according to the first priority information.
The medical system according to claim 1 or 7, wherein The medical dictionary storage unit stores a plurality of types of medical dictionary information,
When the second computer terminal receives an input from the input unit during execution of an application that uses the medical dictionary information, the second computer terminal distinguishes the conversion candidates for each medical dictionary information and causes the display unit to display them.
The medical system according to claim 12. Each of the plurality of types of medical dictionary information is associated with second priority information that defines the priority of each medical dictionary information,
The second computer terminal displays the conversion candidates in parallel in order of priority according to the second priority information when displaying the conversion candidates separately for each medical dictionary information.
The medical system according to claim 13. The second computer terminal displays a conversion candidate of a medical dictionary information having a low priority in addition to a conversion candidate of medical dictionary information having a high priority in the second priority information;
The medical system according to claim 14. The attribute information includes the use identification information,
The second computer terminal receives the medical dictionary information and the use identification information associated with the medical dictionary information, and uses the medical dictionary information associated with the use identification information for the use identification information. Control only to use
The medical system according to claim 1. The usage identification information includes identification information of an application that uses the medical dictionary information,
The second computer terminal receives the medical dictionary information and identification information of the application associated with the medical dictionary information, and executes the application corresponding to the identification information of the associated application with the medical dictionary information Control to read only when
The medical system according to claim 16. A medical server capable of mutual communication with a first computer terminal and a second computer terminal,
A medical dictionary storage unit that stores a plurality of medical dictionary information transmitted from the first computer terminal and associated with attribute information including user identification information or use identification information;
A medical dictionary information acquisition unit that acquires medical dictionary information associated with the attribute information from the medical dictionary storage unit when the attribute information is received from the second computer terminal;
Transmitting information based on the acquired medical dictionary information to the second computer terminal;
A medical server characterized by With servers that can communicate with each other,
A first computer terminal and a second computer terminal;
A medical dictionary storage provided in the server, the first computer terminal, or another server and storing a plurality of medical dictionary information associated with attribute information including user identification information or use identification information, and capable of communicating with the server And
A medical dictionary information management method in a medical system including:
An attribute information receiving step for receiving attribute information including user identification information or use identification information from the second computer terminal by the server;
Medical dictionary information acquisition step of acquiring medical dictionary information associated with the attribute information from the medical dictionary storage unit when the server receives the attribute information;
A dictionary information transmission step for controlling the server to transmit information based on the acquired medical dictionary information to the second computer terminal;
Having
Medical dictionary information management method characterized by the above.

Images