JP5616859B2 - Medical support system and program - Google Patents

Description

  The present invention relates to a system for supporting judgment (medical treatment) on medical-related work by medical staff and a program for realizing the system.

  In recent years, with the spread of medical information systems, a wide variety of medical information is electronically accumulated in hospitals. The digitization of medical information has facilitated the secondary use of stored medical information, as well as reducing hospital paperlessness and improving operational efficiency.

  Specific examples of secondary use of medical information include analysis of medical statistical data and management improvement support, as well as search / reference of past cases. For example, a past case image similar to a diagnosis target image is retrieved from a PACS (Picture Archiving and Communication System) and provided to a doctor, thereby assisting the doctor in creating an image diagnosis and a treatment plan. Patent Document 1 describes a system that supports a diagnosis by setting a region of interest in an image and displaying similar cases on a screen by a search that takes into account the time-series change and the interval between imaging dates and times.

JP 2007-287027 A

  However, in the system of Patent Document 1 described above, there is no mechanism that can support individual diagnosis after evaluating the entire medical care process including information on examinations other than image information and judgment of the attending physician.

  Therefore, the present inventor can manage a series of flow of medical related work as a workflow, and can both evaluate the entire process and support individual diagnosis. In addition, a mechanism is provided to assist the worker so that an appropriate workflow name can be assigned to the workflow.

More specifically, the following invention is proposed.
(A) One invention described in the present specification is provided as a medical assistance system and program having the following means.
(1) (a1) workflow information for identifying a workflow that is a flow of medical treatment of a series of medical related work, (a2) information for identifying a workflow step that is a unit of medical related work that constitutes the workflow, and the medical Information relating to a request source and / or request destination of related work, workflow step information including information related to the type of the medical related work, and (a3) medical information that is information related to the medical related work are associated with each other. Medical information storage means for storing in a first storage area (for example, a medical information database)
(2) Current workflow acquisition means for acquiring the current workflow (currently executed workflow)
(3) Similar workflow search means for searching for a workflow similar to the current workflow from the first storage area
(4) Similar workflow display means for displaying a workflow similar to the current workflow
(5) Selected workflow reception means for receiving information on the selected workflow
(6) Workflow name assigning means for assigning the workflow name of the selected workflow as the workflow name of the current workflow.

(B) One invention described in the present specification is provided as a medical assistance system and program having the following mechanism with respect to the invention shown in (A).
(1) Second storage area for storing conditions for displaying similar workflows (similar workflow display condition storage means)
(2) The similar workflow display means displays the similar workflow according to the conditions stored in the second storage area.
(C) One invention described in this specification is provided as a medical assistance system and program having the following mechanism with respect to the invention shown in (B).
(a1) The second storage area contains the workflow name assignment status of the current workflow, (a2) the workflow name match status between the current workflow and similar workflow, and (a3) the similarity between the current workflow and similar workflow One or more conditions are stored.

  According to one of the above-described inventions, an operator can easily assign an appropriate workflow name to a workflow that represents a series of flows of medical related work. As a result, it is possible to reduce the work burden required for organizing and inputting medical-related work by the workflow. Problems, configurations, and effects other than those described above will be clarified by the following description of embodiments.

The figure which showed an example of the structure at the time of a medical assistance system being installed in a hospital. The figure which showed an example of another structure of a medical treatment assistance system. The figure which shows the data structure example of the workflow table which comprises a medical information database. The figure which shows the 1st data structure example of the workflow step information table which comprises a medical information database. The figure which shows the data structure example of the medical information table which comprises a medical information database. The figure which shows the example of a data structure of the evidence data table which comprises a medical information database. The figure which shows the example of a data structure of the process history table which comprises a medical information database. The figure which shows the example of a data structure of the input data table which comprises a medical information database. The figure which shows the example of a data structure of the test value table which comprises a test | inspection information database. The figure which shows the example of a data structure of the test | inspection item master table which comprises a test | inspection information database. The figure which shows the data structure example of the measured value table which comprises a test | inspection information database. The figure which shows the example of a data structure of the measurement item master table which comprises a test | inspection information database. The figure which shows the example of a data structure of the image table which comprises a test | inspection information database. The figure which shows an example of the flowchart performed when extracting a workflow step from a workflow and assisting medical treatment using medical information and a judgment sentence. The figure which shows an example of the screen before performing the reference of a test | inspection graph and the input of a judgment sentence based on a workflow. The figure which shows an example of the screen at the time of referring an inspection graph. The figure which shows an example of the screen at the time of inputting a judgment sentence. The figure which shows an example of the flowchart performed when supporting a medical treatment by the data processing with respect to evidence data. The figure which shows an example of the screen at the time of referring image data. The figure which shows an example of the screen at the time of inputting a judgment sentence with reference to image data based on a workflow. The figure which shows an example of the screen which sets and displays the destination and transmission sentence to a next workflow step. The figure which shows one of the structural examples of a workflow name process means. The flowchart which shows the outline | summary of operation | movement of a workflow name process means. The figure which shows the example of a screen when a workflow name process means operate | moves. The figure which shows the other structural example of a workflow name process means. The figure which shows the example of a table structure of a similar workflow display condition memory | storage means.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. The embodiment of the present invention is not limited to the embodiments described later, and various modifications can be made within the scope of the technical idea.

<Definition of terms>
Hereinafter, definitions of terms used in the present specification will be described.
-“Workflow” refers to a series of medical-related work flows performed by medical personnel on patients. For example, there is a flow of a series of medical treatments for diagnosis, treatment, and follow-up for each disease, a flow of medical treatment during hospitalization (hospital day to discharge date), one flow defined by medical treatment guidelines, and the like.
“Workflow information” refers to information related to workflow identification. The workflow information also includes a patient identifier that identifies a patient related to the corresponding workflow.
“Workflow step” means a unit of medical-related work that constitutes a workflow. For example, each operation at the patient's medical care stage (diagnosis, treatment, follow-up), diagnosis work determined by the attending physician, work such as medication by a nurse, and exchange between medical departments such as medical departments and radiology departments There are order business units.
The “workflow step information” includes information for identifying a workflow step and information on at least one of a request source or a request destination of medical related work. The workflow step information may be edited, for example, newly generated or deleted by a medical staff at each workflow step. Further, the workflow step information may be prepared based on predetermined medical treatment guidelines.
-“Request for medical related work” refers to ordering of medical related work to each medical department, for example, an examination department or an image diagnosis department.
-“Healthcare professional” is used to include not only the physician in charge, laboratory technician, radiographer, and interpreting doctor, but also nurses and medical accounting personnel.
“Start and end of workflow” is determined by, for example, the attending physician among clinicians.

<Description of system configuration>
<System example 1>
FIG. 1A shows an example of a usage pattern in which the medical assistance system 101 is installed in a hospital. The medical assistance system 101 includes a terminal 104, an interface 111, a memory 112, a storage device 113 such as a hard disk drive, and a CPU 114. A medical assistance system 101 shown in FIG. 1A is connected to an electronic medical record system 102, a PACS (Picture Archiving and Communication System) 103, and the like via a network.

  The terminal 104, the interface 111, the memory 112, and the storage device 113 are connected to the CPU 114. The terminal 104 is a terminal device operated by a medical worker. Information input to the terminal 104 is given to the CPU 114 through the interface 111 connected via a network or the like. In response to the instruction input, the CPU 114 reads and processes the program stored in the memory 112, and outputs the processing result to the terminal 104 via the interface 111. Processing functions for assisting healthcare professionals are provided through program-based data processing. The interface 111 includes a device configuration including a display screen.

  As described above, each terminal 104 is a terminal device that receives an operation input by a medical worker such as a doctor, nurse, laboratory technician, or interpretation doctor. Each terminal 104 can use not only the medical assistance system 101 but also the electronic medical record system 102 and the PACS 103 as a medical assistance system. It can also be used as a terminal device for operating the electronic medical record system 102 and the PACS 103.

  Each of the electronic medical record system 102 and the PACS 103 may store medical history (including findings from medical staff), patient examination values, image data, and the like. In that case, the storage device 113 of the medical assistance system 101 may have information indicating a link to those databases, or may have a copy of the data stored in those databases. good. Further, as shown in FIG. 1B described later, the examination support database 101 may include an examination information database 116 that is a database included in the electronic medical record system 102 and the PACS 103.

<System example 2>
FIG. 1B shows another configuration example of the medical assistance system 101. The medical assistance system 101 shown in FIG. 1B includes a medical information database 105, and a medical information storage unit 106 that stores information in the database is connected. In the case of this embodiment, the medical information database 105 stores workflow information, workflow step information, and medical information that is information related to medical related work in association with each other.

  The “medical information” includes information input by a medical worker, evidence data that is objective biological information acquired from a patient, and the like. In the case of this example, a text sentence (determination sentence) indicating a judgment made in medical related work is used as an example of information input by a medical worker. “Evidence data” refers to data such as test values and image data acquired from modalities (medical devices), for example.

  Further, the medical support system 101 includes a workflow input unit 107, an input information reception unit 108, a medical information output unit 109, a workflow step request input unit 117, a workflow output unit 118, and a workflow end unit 119. It has been. Functions corresponding to these means are stored in the memory 112 in FIG. 1A.

  The workflow input unit 107 provides a function of accepting an input when selecting workflow step information from the medical information database 105.

The input information receiving unit 108 provides a function of receiving an input of a judgment sentence.
The medical information output unit 109 provides a function of extracting and outputting medical information from the medical information database 105 based on the workflow step information.

  The workflow step request input unit 117 provides a function of accepting input of information related to a workflow step request.

  The workflow output unit 118 provides a function of acquiring workflow information from the medical information database 105 based on a patient identifier for identifying a patient, and outputting the acquired workflow information to the interface 111.

  The workflow end unit 119 provides a function of storing the workflow end information in the medical information database 105.

  Here, the medical assistance system 101 provides a function of reading medical information from the medical information database 105 based on the workflow step information selected through the workflow step input unit 107 and displaying it on a display screen (not shown). Further, the medical assistance system 101 has a function of storing information input through the input information receiving unit 108 and medical information displayed on the display screen in the medical information database 105 in association with the workflow step information being executed. provide.

  As described above, the medical information referred to in the current workflow step is also stored in the medical information database 105 in association with the input information, so that the information referred to as the basis of the medical treatment at the time of executing the workflow step can be accumulated. It becomes possible. By referring to the accumulated information, it becomes possible to grasp the process of medical related work by the medical staff after the fact.

  The medical information database 105 stores and manages medical information, which is information related to medical related work in each workflow step, via the medical information storage unit 106. The medical information database 105 includes (1) a judgment sentence associated with each workflow step input through the input information receiving means 108, and (2) evidence data processed by the evidence data processing means 115 and its processing history. (3) Medical information and the like referred to in each workflow step are accumulated.

  As in the case of the medical support system 101 illustrated in FIG. 1A, the medical information database 105 may include link information to medical information stored in the electronic medical record system 102 or the PACS 103.

  The medical information storage unit 106 is a unit (apparatus) that realizes a function of storing workflow information, workflow step information, and medical information in the medical information database 105. The medical information to be stored includes, for example, (1) evidence data processed by evidence data processing means 115, (2) data processing history including the processing source data, and (3) input information receiving means 108, There is information entered by.

  The test information database 116 accumulates and manages information on test results related to medical care such as blood tests and image tests at each work slow step. This database may be realized by sharing with the database of the electronic medical record system 102, the ordering system, or other hospital information system, or may be realized by sharing with the database of the image management system such as the PACS 103.

  Further, data import means (apparatus) (not shown) may be provided, and data may be imported from these systems into the inspection information database 116. Further, a data input means (apparatus) (not shown) may be provided so that data can be directly input by a doctor, nurse, technician or other medical staff. In addition, patient examination results based on examination methods newly developed by doctors for research purposes are also entered into the examination information database 116 from a data input means (device) (not shown) and stored together with general examination results. Also good.

  Furthermore, when the electronic medical record system 102 and the PACS 103 are installed separately from the medical care support system 101, only the link information to the examination information stored in the electronic medical record system 102 or the PACS 103 may be included.

  Further, when a data processing workstation is installed, a history of data processing executed by the data processing workstation may be stored in the inspection information database 116.

  The evidence data processing means 115 is means (apparatus) that executes data processing using data stored in the examination information database 116. The evidence data processing unit 115 includes a plurality of processing modules.

  The evidence data processing means 115 for doctors specializing in image diagnosis (hereinafter referred to as “interpretation doctors”) is not only a basic module such as image data input / output processing and various filter processing, but also advanced image processing algorithms. It also has functional modules such as region extraction processing and image alignment processing that require image processing. The operator can execute a series of data processing necessary for medical treatment by freely combining the processing modules according to the processing purpose and the nature of the data, and executing them in order.

  In the case of this embodiment, the medical information database 105 and the examination information database 116 are logically divided and configured, but may be configured by physically the same database. For example, the medical information database 105 and the examination information database 116 may be combined into one database. Similarly to the case of the medical support system 101 shown in FIG. 1A, when the electronic medical record system 102 or the PACS 103 is used separately, link information for them may be included in the database.

  Furthermore, like the medical assistance system 101 shown to FIG. 1B, you may further have the similar case search means 160 and the process analysis means 170 with respect to the system structure mentioned above.

  The similar case search means 160 is a means (apparatus) used for the purpose of supporting the judgment of the medical staff. For example, the similar case search unit 160 provides a function of searching the medical information database 105 for a case similar to a case of a specified patient. In the case of this embodiment, the similar case search means 160 outputs (1) the searched medical information and (2) the workflow information to which the workflow step information associated with the medical information belongs.

  By using the similar case search unit 160, the medical staff can not only refer to the medical information related to the similar case, but can also refer to the workflow information associated with the referred medical information. In other words, the similar case search means 160 is configured so that the medical operator (1) includes information on other workflow steps positioned before and after the workflow step associated with the medical information referred to, and (2) Provide a function that supports the utilization of medical information related to similar cases in consideration of the associated prognosis information of the patient.

  The process analysis means 170 analyzes the medical process based on the data of a plurality of patients stored in the medical information database 105 in order to improve the quality and efficiency of the medical care, and information necessary for improving and optimizing the process. Means (apparatus) for extracting.

  Furthermore, the medical assistance system 101 illustrated in FIG. 1B may include a workflow name processing unit 180. The workflow name processing means 180 is executed when a workflow step execution event is received. The workflow name processing unit 180 is a unit (apparatus) that searches the medical information database 105 for a workflow similar to the workflow associated with the current workflow step and displays the workflow together with the similarity information. The detailed operation of the workflow name processing unit 180 will be described later.

<Database table structure>
<Medical information database>
Below, the table structure which comprises the medical information database 105 is demonstrated. FIG. 2A shows the data structure of the workflow information table 200. FIG. 2B shows the data structure of the workflow step information table 210. FIG. 3A shows the data structure of the medical information table 300. FIG. 3B shows the data structure of the evidence data table 310. FIG. 3C shows the data structure of the processing history table 320. FIG. 3D shows the data structure of the input data table 330.

<Workflow information table 200>
The workflow information table 200 (FIG. 2A) is a table that stores workflow information that is information for identifying a workflow, and is basically registered by the attending physician. The table includes a patient ID field 201, a workflow number (No.) field 202, a workflow name field 203, a workflow start date / time field 204, a workflow end date / time field 205, an attending physician ID field 206, and a conference flag field 207. .

  Here, the patient ID field 201 stores a patient identifier that is an identifier for identifying a patient.

  The workflow number field 202 stores a number that becomes key information for uniquely specifying each piece of workflow information.

  The workflow name field 203 stores a workflow name indicated by a disease name, a treatment name, or the like. In the case of this embodiment, the workflow name field 203 stores a text sentence, but may also store the standard master ID of a disease name or treatment name.

The workflow start date / time field 204 stores a workflow start date and the like.
The workflow end date / time field 205 stores the end date of the workflow, and is registered when the workflow ends.

  The attending physician ID field 206 stores identification information of the attending physician who is responsible for the workflow.

  The conference flag field 207 stores an execution flag indicating whether or not a conference has been executed in the workflow.

<Workflow step information table 210>
The workflow step information table 210 (FIG. 2B) is a table that stores workflow step information that is information for identifying each step of the workflow, and one step becomes one record. The table includes a patient ID field 211, a workflow step number (No.) field 212, a workflow step execution scheduled department ID field 213, a workflow step execution date / time field 214, a workflow step performer ID field 215, a workflow step execution flag field 216, A conference step flag field 217, a workflow number (No.) field 218, a parent workflow step number (No.) field 219, a child workflow step number (No.) field 220, and a workflow step type field 221 are configured.

  Here, the workflow step no. The field 212 stores a number that becomes key information for uniquely specifying each workflow step.

  The workflow step execution scheduled department ID field 213 stores identification information for uniquely identifying a department, a medical department, an examination department, or the like that is scheduled to execute the workflow step.

  The workflow step execution date and time field 214 stores the date and time when the workflow step is executed.

  The workflow step performer ID field 215 stores identification information for uniquely identifying the medical staff who actually executed the workflow step.

  The workflow step execution flag field 216 stores an execution / non-execution flag of the workflow step.

  The conference step flag field 217 stores a flag indicating that the conference step is a workflow step.

  Workflow No. The field 218 stores identification information for uniquely identifying the workflow to which the workflow step belongs.

  Parent workflow step No. The field 219 stores identification information for identifying a workflow step that appears before the corresponding workflow step in time and is associated with the corresponding workflow step.

  Child workflow step No. The field 220 stores identification information that identifies a workflow step that appears later in time than the corresponding workflow step and is associated with the corresponding workflow step. Parent workflow step No. And child workflow step no. Has a role of connecting the order request source and the request destination.

  The workflow step type field 221 stores identification information for uniquely identifying the workflow step type. The workflow step type indicates the type of medical related work. For example, “Inpatient treatment”, “Outpatient treatment”, “XX surgery” etc. in the clinical department, “CT examination”, “MRI examination” etc. in the radiology department, “Blood test” etc. in the specimen examination department It is. These are defined in advance in the master database or the like for each hospital, department, or department.

<Medical information table 300>
The medical information table 300 (FIG. 3A) is a table that stores medical information that is information related to medical related work based on workflow steps, and stores one medical information in one record. This table includes a patient ID field 301, a workflow step number. Field 212, workflow step execution date / time field 214, workflow step executor ID field 215, judgment statement field 305, workflow number. A field 218, an evidence number (No.) field 311, and a reference workflow step number (No.) field 306 are configured.
Here, the patient ID field 301 stores a patient identifier for identifying a patient.

  The judgment sentence field 305 stores the judgment sentence input for the corresponding workflow step. Incidentally, when the judgment text is included in the medical information referred to when the judgment text is input in the judgment text field 305, the judgment text included in the referred medical information can also be stored in the judgment text field 305. In this case, the distinction between the input judgment sentence and the judgment sentence included in the referred medical information is made by referring to the reference workflow step no. Can be performed based on

  Workflow step No. The field 212 indicates a workflow step No. in the workflow step information table 210 when medical information is registered. The link information to the field 212 is stored. Through this link information, the workflow step table information 210 and the medical information table 300 are associated.

  Evidence No. A field 311 is an identifier that designates evidence data that is a basis for the determination, and is associated with the evidence data table 310. As described above, the medical information table 300 stores the determination sentence and the evidence data that is the basis of the determination based on the workflow step information.

  Reference workflow step no. A field 306 is a workflow step number of a record. The workflow step No. referred to in FIG. Is stored.

<Evidence data table 310>
The evidence data table 310 (FIG. 3B) is a table that stores evidence data, and stores one piece of evidence data in one record. The table includes an evidence number (No.) field 311, an evidence type field 312, an evidence display icon field 313, an evidence display text field 314, a workflow step execution date / time field 214, a workflow step performer ID field 215, and a workflow step. No. A field 212 is included.

  Here, evidence no. The field 311 stores a number that becomes key information for uniquely specifying each piece of evidence data. In the evidence data processing means 115 described above, different processing is executed depending on the type of inspection information input, such as image processing for images and graphing or statistical processing for inspection values. In this embodiment, evidence data corresponding to different types of processing such as image processing and inspection value graphing is stored as separate records.

  The evidence type field 312 stores the type of medical assistance processing from which evidence data is extracted.

  The evidence display icon field 313 and the evidence display text field 314 store information capable of recognizing the content of the evidence data. In the evidence display icon field 313, as shown in FIG. 3B, an icon image may be directly stored, or icon image identification information such as a file name may be stored.

  Workflow step No. The field 212 is a workflow step number in the medical information table 300. The link information to the field 212 is stored. With this link information, various data of the evidence data stored in the evidence data table 310 is associated with the medical information table 300.

<Processing history table 320>
The processing history table 320 (FIG. 3C) is a table that stores processing history applied to examination information that is information before processing of evidence data, and stores one processing history in one record. The processing history includes a processing history for the examination value and a processing history for the image data, and these processing histories are also included in the medical information.

  The table includes a processing number (No.) field 321, a processing content field 322, an evidence number (No.) field 323, a processing parameter field 324, and a processing time field 325.

  Here, the process No. The field 321 stores a number serving as key information for uniquely identifying each process constituting the process history.

  The processing content field 322 stores information necessary for the computer to reproduce, analyze, and reuse the processing afterwards, that is, information that can identify the processing content. In the case of this embodiment, information relating to the processing history of image processing and inspection value processing is stored.

  For example, in the inspection value processing (evidence No. = 3), when the inspection result is read and graphing with a real scale of a plurality of inspection items is executed, “input” and “real scale display” are registered.

  For example, in the case of image processing (evidence No. = 4), when an examination image is read, a region extraction process of a tumor region (for example, a region growing method) is executed, and calculation and filtering of the tumor region volume are executed, “input” , “Region Growing”, “Volume Calculation”, and “Filtering” are registered in the order of processing.

  Evidence No. A field 323 is an evidence number in the evidence data table 310. The value of the field 311 is stored. The same evidence No. The evidence data identified by the The process is executed in the order of the numbers in the field 321.

  The process parameter field 324 stores parameters set when executing each process. In the case of this embodiment, for convenience of explanation, parameters are entered in one field, but this differs depending on the process. Therefore, a separate processing parameter table may be prepared for each type of processing.

  In this embodiment, the individual processes constituting the evidence data are individually stored in the database table. However, the evidence history table 310 is provided with a process history binary field, and the process history and input / output data of each process are also stored. It may be stored in its own binary format. In this case, the binary data can be directly passed to the evidence data processing means 115 without referring to the processing history table 320 or the input data table 330 at the time of reproducing the processing, thereby speeding up the reproduction of the processing and facilitating the implementation. Can be realized. As described above, the processing history table 320 includes the evidence number. The evidence data table 310 and the records stored in the medical information table 300 are associated with each other in terms of processing contents.

<Input data table 330>
The input data table 330 (FIG. 3D) stores the input data used in the first processing of the processing history in the evidence data linked with the examination information database 116. One input data is stored in one record. The table includes an evidence number (No.) field 331, an input data ID field 332, and an input data type field 333.

  The input data ID field 332 stores, as input data for each piece of evidence data, a number serving as key information for uniquely specifying the inspection information in the inspection information database 116.

  The input data type field 333 stores a data type for defining the link destination of the ID stored in the input data ID field 332. For example, in the case of “blood test”, a test value ID for uniquely identifying a patient test value is stored, and in the case of “image test”, an image ID for uniquely identifying a patient image is stored. If “new marker test”, the measurement value ID for uniquely identifying the measurement value of the patient of the new marker test is stored.

  As described above, the input data table 330 is stored in the evidence number. The records stored in the evidence data table 310 and the medical information table 300 are associated via the field 331.

<Inspection information database>
Below, the table structure which comprises the test | inspection information database 116 is demonstrated. The examination information database 116 stores detailed information of evidence data related to medical care, and includes an examination value table 400, an examination item master table 410, a measurement value table 420, a measurement item master table 430, and an image table 440. .

  FIG. 4A shows the data structure of the inspection value table 400. FIG. 4B shows the data structure of the inspection item master table 410. FIG. 4C shows the data structure of the measurement value table 420. FIG. 4D shows the data structure of the measurement item master table 430. FIG. 4E shows the data structure of the image table 440.

<Inspection value table 400>
The test value table 400 (FIG. 4A) is a table for storing the contents of the “blood test” data, and stores one test value in one record. The table includes an examination value ID field 401, a patient ID field 402, an examination result date / time field 403, an item code field 404, and a value field 405. Records in the inspection value table 400 are associated with the inspection item master table 410 (FIG. 4B) using the item code as key information.

<Inspection item master table 410>
The test item master table 410 (FIG. 4B) is an item master table of “blood test”, and includes an item code field 411, an item name field 412, and a unit name field 413.

<Measured value table 420>
The measurement value table 420 (FIG. 4C) is a table for storing the contents of the “new marker test” data, and stores one measurement value in one record. The measurement value table 420 has the same data structure as the inspection value table 400. The measurement value table 420 includes a measurement value ID field 421, a patient ID field 422, a measurement result date / time field 423, an item code field 424, and a value field 425.

<Measurement item master table 430>
The measurement item master table 430 (FIG. 4D) has the same data structure as the inspection item master table 410. The measurement item master table 430 includes an item code field 431, an item name field 432, and a unit name field 433. The measurement item master table 430 includes a field for storing measurement item registration information (for example, a registration date field 434) in addition to the fields constituting the inspection item master 410, so that item version management can be performed. You may do it.

  As described above, in this embodiment, the test information database 116 separately manages the contents of input data for “blood test” and “new marker test”, and the input data table 330 (FIG. 3D) includes only link information. A configuration that centrally manages the system is adopted. By adopting this method, both test values measured in normal operations and test values newly developed for research purposes can be stored as evidence data. Therefore, it becomes possible to analyze the effectiveness of the newly developed inspection method.

<Image table 440>
The image table 440 (FIG. 4E) stores an image ID field 441 that stores an identifier for identifying an image, a patient ID field 442 that stores a patient identifier, an image acquisition date field 443 that stores the date and time when the image was acquired, and an item code. An item code field 444 for storing images and an image field 445 for storing images.

<Data input operation example according to usage>
Next, processing operations executed in the system when the image interpretation doctor inputs data to the medical support system according to the embodiment will be described. System-side processing is provided through data processing of a program executed on the CPU 114. FIG. 5 shows an example of a flowchart to be executed.

(Step S500)
This system accepts a login input to the login screen through an operation input by the operator on the terminal 104.

(Step S501)
Next, the present system accepts the patient's selection through the operator's operation input to the terminal 104. Specifically, the selection of the patient identifier is accepted through the selection operation of one patient on the patient selection screen.

(Step S502)
Next, the medical information storage means 106 is a record corresponding to the patient acquired in step S501, and the workflow No. currently in progress. Is identified from the workflow information table 200 (FIG. 2A). Here, the current workflow No. For example, there is a method of identifying a record in which the value of the workflow end date / time field 205 is not registered. Further, for example, a method may be used in which all records corresponding to the patient acquired in step S501 are extracted from the workflow information table 200 and displayed on the workflow selection screen, and one operator is designated and input one workflow.

(Step S503)
The medical information storage unit 106 uses the workflow No. identified in step S502. Is used to obtain the corresponding workflow step information from the workflow step information table 210 (FIG. 2B).

(Step S504)
The medical information storage means 106 determines the current workflow step No. from the department information of the login information acquired in step S500. Identify Here, the “current workflow step” represents a workflow step currently being executed in the workflow.

  For identification of the current workflow step, for example, the medical information storage unit 106 refers to the workflow step execution scheduled department ID field 213 and the workflow step execution flag field 216 in the record acquired in step S502, and the department of the login person and the corresponding department Workflow step No. that has not been executed in the previous step. Current workflow step No. It can be identified by extracting as. When all the steps of the corresponding department have been executed, the final step No. Current workflow step No. And

(Step S505)
The workflow output unit 118 sets and displays each workflow step information acquired in step S503 on the workflow step execution screen 600 shown in FIG. 6A. This workflow step execution screen 600 is displayed on the interface 111 (FIG. 1).

  The workflow step execution screen 600 (FIG. 6A) includes, for example, a workflow step selection area 601, a login information display area 602, a judgment sentence input / output area 603, an evidence data display area 604, a medical information registration button 605, a medical assistance button group 606, and a workflow. A step type input area 607 is included.

  The workflow step selection area 601 includes a parent workflow step No. in the workflow step information table 210 (FIG. 2B). Based on the information in the field 219, the workflow steps from the workflow start step to the current step are displayed in a flow format.

  For example, in the case of the workflow step information table 210 (FIG. 2B), the workflow step No. 2 and No. The workflow step No. 3 is the parent workflow step no. Are both “1”. Therefore, the workflow step No. 2 and No. The workflow steps No. 3 are all workflow step numbers. Displayed in association with one workflow step. In addition, workflow step No. The workflow step No. 4 is the parent workflow step No. 4. Is “3”, the workflow step No. 3 connected to the workflow step.

  Such a connection between the workflow steps is associated with the child workflow step No. This can also be realized in the same manner.

  In this way, the workflow step selection area 601 (FIG. 6A) displays the workflow information and the workflow step information obtained by connecting the request source workflow step and the request destination workflow step to each other.

  The login information display area 602 is an area for displaying operator information that is currently logged in to the system. The judgment sentence input / output area 603 is an area for displaying the contents input and output in text format by the medical staff. The evidence data display area 604 is an area for displaying evidence data. The medical information registration button 605 is a button for registering data obtained by combining evidence data and a text sentence in the medical information database 105 by an operator's click operation.

  The medical assistance button group 606 is a button used by the medical staff to call up the function of the evidence data processing means 115 that performs data processing such as image processing and test value processing for medical treatment of the patient. The medical assistance button group 606 may be set to selectable / impossible from the job type information of the login information acquired in step S500.

  In the present embodiment, the current workflow step identified in step S504 is highlighted in the workflow step selection area 601, for example. In each workflow step, information that indicates the progress status of the workflow is displayed. In the case of FIG. 6A, for example, the display format is such that the completion / incompleteness is known, such as changing the display color according to the contents of the workflow step execution flag field 216 (FIG. 2B). For the completed workflow step, the contents of the workflow step execution date / time field 214 (FIG. 2B) and the workflow step executor ID field 215 (FIG. 2B) are displayed.

(Step S509)
In this embodiment, it is assumed that the interpretation doctor A starts interpretation work and registers medical information at this stage. Interpreting doctor A performs an interpretation operation by the processing (described later) in steps S701 to S712 in FIG. When the interpretation work is completed, the current workflow step No. identified by the medical information storage unit 106 in step S504 is displayed. In association with the medical information, the medical information displayed on the screen is registered in the medical information database 105 (FIG. 1B).

  Hereinafter, the processing operation executed in the system when the doctor A interprets medical information in the system will be described. The processing on the system side is also provided through data processing of a program executed on the CPU 114.

  The interpreting doctor A who uses this system performs interpretation while referring to the medical information in the workflow steps of the laboratory technician A and CT engineer A in the workflow step of the interpretation work, and is executing the referred medical information and the interpretation result. Save it in association with the workflow step.

(Step S701)
FIG. 7 shows details of the processing operation executed in step S509. The operator performs an input for selecting the workflow step information of the laboratory technician A through the operation on the terminal 104. At this time, the workflow input unit 107 receives an input for selecting the workflow step information from the medical information database 105.

(Step S702)
The medical information output unit 109 searches the medical information database 105 for medical information associated with the selected workflow step (workflow step No. 2) of the laboratory technician A, and displays it on the workflow step execution screen 600. In the present embodiment, the evidence No. acquired by laboratory technician A is shown. Assume that one test value graph is registered in the medical information.

(Step S703)
Interpretation doctor A specifies the displayed examination value graph as data to be processed through an operation on terminal 104.

(Step S704)
The present system displays an inspection value graph screen 610 (FIG. 6B) on the screen.

(Step S705)
Interpretation doctor A inputs data processing such as selection of examination items to be displayed on examination value graph screen 610, setting of a graph format, extraction of a point of interest and data fluctuation, through operation on terminal 104. Here, it is assumed that image interpretation doctor A operates the “AFP extraction” button to input selective extraction of AFP values. At this time, the operation of the “AFP extraction” button is given to the evidence data processing means 115. In this case, the evidence data processing means 115 extracts the AFP value selected by the operator from the AFP data in the inspection value graph. In FIG. 6B, the selected AFP data is shown by enlarging the dots indicating the data of the two selected points.

(Step S706)
The evidence data processing unit 115 acquires the AFP value and date extracted in step S705 as evidence data together with the displayed examination value graph. By this acquisition process, evidence data is generated.

(Step S707)
The medical information output unit 109 generates evidence data display data “graph icon file 1” and “20091001, AFP: 17.1, 20010106, AFP: 17.3” from the acquired data, and the evidence data display area 604. Is displayed in the first line (FIG. 6C).

(Step S708)
Interpreting doctor A who is an operator inputs a judgment sentence “no AFP fluctuation” related to the data processing of the examination value graph to judgment sentence input / output area 603 through operation of terminal 104. The input information accepting unit 108 accepts this input.

(Step S709)
The system determines whether or not the operator performs another data process. If another data process is performed, the system returns to step S701 and repeats the process. In the case of the present embodiment, it is assumed that the interpreting doctor A who is an operator continues the processing on the CT image captured in the workflow step of the CT engineer A.

  In this case, the workflow input unit 107 receives an input for selecting the workflow step (workflow step No. 3) of the CT engineer A.

  Thereafter, in step S702, image data (evidence No. 2) is acquired and displayed on the screen. In the next step S703, the displayed image data is specified as processing target data. In step S704, the image processing screen 800 shown in FIG. 8A is displayed on the screen. In the next step S705, the image interpretation doctor A extracts a tumor region from the CT image. Details of processing on the image processing screen 800 will be described later. In step S <b> 706, the image processing history and the input data “image ID <b> 1” from the image processing screen 800 to the calculation of the volume of the tumor region through region extraction are acquired. In step S707, the display data “image icon file 1” and “# 1: 10 mm # 2: 15 mm” of the evidence data are generated using the information of the image processing history and displayed in the evidence data display area 604 (FIG. 8B). In step S <b> 708, the operator inputs a determination sentence related to image processing “# 1: Nodal of 10 mm in S <b> 7 and # 2: 15 mm in S <b> 6” into the determination sentence input / output area 603. The input information accepting unit 108 accepts this input.

(Step S710)
If it is determined in step S709 that the operator does not perform additional processing, the system adds a determination sentence that is not for each evidence data, for example, “highly differentiated HCC is suspected” to the determination sentence input / output area 603 as necessary. input. The input information receiving means 108 receives this input.

(Step S711)
The interpreting doctor A who is an operator selects “CT examination” in the workflow step type input area 607 and selects the medical information registration button 605 as necessary. In the case of the present embodiment, interpretation doctor A selects the workflow step type at the time of registration, but may automatically reflect the contents set at the time of inputting the request destination at the time of generating the workflow step described later.

(Step S712)
When the medical information registration button 605 is selected, the medical information storage unit 106 acquires the current date and time from, for example, hardware in which a medical assistance system is installed. In addition, the medical information storage unit 106 acquires, from the medical information database 105, for example, the medical staff information “radiographer A” of the login person. The medical information storage means 106 stores the text sentence in the judgment sentence input / output area 603, the history of processing extracted by the evidence data processing means 115 and the input data, the patient identifier selected in step S501, the date and time, the medical worker information, and the workflow step. The type, the workflow step execution flag “true”, and the workflow step number are registered in each table of the medical information database 105 described above. In the case of this embodiment, the evidence number corresponding to the test value graph subjected to the data processing is shown. 3 corresponds to the evidence No. corresponding to the image processed data. 4 are registered respectively.

  In the judgment sentence input / output area 603 in this embodiment, the text sentence input / output in step S708 and step S710 is handled as one data, but the judgment sentence input / output area 603 is used as a judgment sentence for each evidence data. The input / output areas (the judgment sentence area of the inspection value graph, the judgment sentence area of the image processing) and the input / output areas of judgment sentences related to all evidence data are configured separately, and in step S712, tags are used to distinguish them. Each judgment sentence may be registered separately by adding information or the like. Moreover, about the judgment sentence for every evidence data, you may give link information with evidence data.

<Summary 1>
As described above, this system displays evidence data corresponding to a workflow step (medical related work) executed before the current workflow step, executes data processing, and the data is processed in the current workflow step. The judgment sentence based on the evidence data is received, and the judgment sentence and the evidence data displayed when the judgment sentence is inputted are automatically associated with the current workflow step and registered.

  By adopting this mechanism, it is possible to store the process of how the medical staff sees what data and how to make a decision in each workflow step in association with each workflow step. As a result, it is possible to support the medical practice while utilizing the tacit knowledge of each medical worker along the workflow.

  Furthermore, the system also stores evidence data processing history based on the workflow steps. For this reason, it is possible to accumulate the correspondence between the medical worker's judgment performed in each workflow step and the data processing history.

<About workflow step generation and workflow end>
The generation of the workflow step and the end of the workflow will be described with reference to FIG. The screen shown in FIG. 9 includes a request destination workflow step type input area 900, a transmission sentence input area 901 for inputting a transmission sentence, a next workflow step setting button 902, a scheduled date input area, an attached file area, a reply flag input area, and the like. It is shown. When the operator presses the next workflow step setting button 902 in a state where the requested workflow type, transmission sentence, and scheduled date are input, the input information is reflected in the workflow step display map 903.

  The workflow step request input means 117 receives these inputs. The transmitted message input in the transmitted message input area 901 is displayed on the transmitted message display unit 904 in the workflow step display map 903 by the medical information output means 109.

  Furthermore, the workflow request input means 117 receives a new workflow step No. via the medical information storage means 106. Are assigned to the requested execution department, workflow step type, and child workflow step No. from the request destination input in the request destination input area 901. To get. Requested current work step No. To the parent workflow step No. Is acquired, a new record is stored in the workflow step information table 210 of the medical information database 105. It is also possible to send an attached file and attach a reply flag.

<Summary 2>
As described above, the system can generate workflow step information by receiving input of a request destination, a scheduled date, a comment, and the like. Thereby, this system can manage a workflow step efficiently. Further, the system displays the input request destination, scheduled date, and comment on the workflow step display map 903, so that the operator can easily grasp the workflow. Further, as shown in FIG. 1A, the above-described request input may operate separately using the electronic medical record system 102 and in cooperation with ordering information managed by the electronic medical record system.

<Input workflow name>
As described above, in the medical assistance system 101, the workflow name is stored in the workflow name field 203 of the workflow information table 200 (FIG. 2A). Assigning an appropriate name to the workflow name is important from two aspects of diagnosis support and data analysis.

  First, the importance from the aspect of diagnosis support will be explained. In actual operation, it is assumed that the workflow is not named until the diagnosis is confirmed or the treatment policy is determined. In this case, a workflow name is input for an unfinished workflow at a timing when diagnosis is confirmed or a treatment policy is determined. The reason why the operation without input is assumed is that even if the workflow name is input once, the optimal workflow name may change as the medical treatment progresses.

  Next, the importance from the aspect of data analysis will be explained. In the data analysis, it is assumed that the workflow information accumulated in the medical information database 105 is grouped based on the workflow name and a statistical method such as a group relation test is used. For this reason, it is important that an appropriate workflow name is input.

  Some diseases have a standard medical process, such as a clinical path. For such diseases, a standard workflow is created in advance to determine the diagnosis and treatment policy. By applying the standard workflow to the patient who is doing it, it becomes easy to provide the patient with a standardized and uniform medical practice.

  For the standard workflow, it is desirable to input a workflow name using a disease name or treatment name such as “liver tumor (RFA)”. When starting the standard workflow, the standard workflow name is entered in the workflow name field 203.

  On the other hand, for diseases that do not have a standard medical process such as clinical path, or for diseases for which diagnosis has not yet been confirmed, the standard workflow can be applied at the start of the workflow, or an appropriate workflow name can be entered. Is difficult. Therefore, it is assumed that the workflow is started in a state where a temporary workflow name is input or the workflow name is not set, and the workflow name is input based on the judgment of the attending physician at the timing when the diagnosis and treatment policy are determined.

  Note that what kind of workflow name is input for the workflow depends on the operation of the hospital. However, if the disease name or treatment name is used as the workflow name, it becomes easy to grasp the contents of the workflow.

<System configuration 1 of workflow name processing means>
FIG. 10 shows one configuration example of the workflow name processing means 180. The workflow name processing unit 180 includes a current workflow acquisition unit 1000, a similar workflow display unit 1001, a selected workflow reception unit 1002, and a workflow name assignment unit 1003. In the case of this embodiment, the workflow name processing means 180 and its constituent functions are realized through a program executed on a computer.

  Here, the “current workflow” represents a workflow that is currently being executed. The current workflow acquisition unit 1000 is a unit that acquires information on the currently executed workflow. The similar workflow display unit 1001 is a unit that receives and displays a workflow similar to the workflow acquired by the current workflow acquisition unit 1000 from the similar case search unit 160. The selected workflow receiving unit 1002 is a unit that receives a workflow selected by the user from the workflows displayed on the similar workflow display unit 1001. The workflow name assigning unit 1003 is a unit that inputs the workflow name of the workflow selected by the user as the workflow name of the current workflow.

  With this system configuration, a workflow name similar to the current workflow can be presented to the user as a workflow name candidate for the current workflow. The user inputs the workflow name of the execution workflow with reference to the displayed workflow name candidates. With this workflow name input support function, the user can easily input an appropriate workflow name.

<Example 1 of workflow name input support>
Next, the processing operation of the workflow name processing unit 180 will be described. FIG. 11 shows an outline of the processing operation. When the workflow name processing unit 180 receives the execution event of the workflow step, the workflow name processing unit 180 starts the processing flow shown in FIG.

(Step S1100)
The current workflow acquisition unit 1000 acquires a current workflow record from the workflow information table 200 (FIG. 2A).

(Step S1101)
The current workflow acquisition unit 1000 passes the acquired workflow information of the current workflow to the similar case search unit 160 as a search query.

(Step S1102)
The similar case search unit 160 extracts a workflow similar to the current workflow from the workflow information table 200. In this embodiment, workflow step information is used to determine the similarity between workflows. Specifically, the similarity using text data such as the judgment sentence field 305 (FIG. 3A), the similarity using numerical data such as the value field 405 (FIG. 4A), the workflow step executor ID field 215 ( Similarity using category data as shown in FIG. 2B) is used. Note that the similarity may be determined by combining a plurality of similarities described above.

(Step S1103)
The similar workflow display unit 1001 receives the extracted workflow and presents it to the user in a list format, for example.

(Step S1104)
The similar workflow display unit 1001 determines whether or not there is an instruction input to adopt the workflow name of the similar workflow as the workflow name of the current workflow. Here, when a positive determination result is obtained, the similar workflow display unit 1001 proceeds to step S1105. On the other hand, when a negative determination result is obtained, the similar workflow display unit 1001 skips step S1105 and ends the process.

(Step S1105)
If a positive result is obtained in step S1104, the selected workflow receiving unit 1002 gives the workflow name of the workflow selected in the similar workflow list to the workflow name assigning unit 1003. The workflow name assigning unit 1003 inputs the notified workflow name to the workflow information table 210 as the workflow name of the current workflow.

  FIG. 12 shows a display screen example. FIG. 12 shows a workflow step execution screen 600. In the workflow step selection area 601, a workflow whose workflow name display 1200 is “untitled” is displayed as the current workflow. In the case of FIG. 12, four workflow steps are already associated with the current workflow. In addition, judgment text and evidence data are input to the judgment text input / output area 603 and evidence data display area 604 on the same screen as shown in the figure.

  When the medical information registration button 605 is selected by a user operation input, steps S1100 to S1103 shown in FIG. 11 are executed in order, and a similar workflow screen 1201 is presented to the user. As shown in FIG. 12, the similar workflow screen 1201 may be displayed so as to overlap the workflow step execution screen 600 or may be displayed side by side with the workflow step execution screen 600.

  It is assumed that the similar workflow screen 1201 includes a similar workflow list 1202, for example. In the similar workflow list 1202, all workflows whose calculated similarity exceeds a predetermined threshold are displayed as similar workflow candidates. However, in the similar workflow list 1202, only the workflow having the highest calculated similarity may be displayed as a similar workflow candidate.

  In the case of FIG. 12, the workflow name and the similarity are displayed in the similar workflow list 1202 for each workflow. When the user selects the workflow name registration button 1203 on the similar workflow list 1202 screen, steps S1104 to S1105 shown in FIG. 11 are executed, and the current workflow name is updated.

<Summary 3>
With the processing flow and screen example described above, each time a workflow step that is a component of a workflow is executed, a candidate for a workflow name similar to the current workflow is presented to the user. The user can enter a workflow name through selection of any of the presented workflow names. With this function, it becomes easy to re-evaluate the entire workflow at the timing when the medical care process proceeds, that is, when the workflow step that is a component of the workflow is executed.

  Note that the similar workflow screen 1201 may be automatically displayed only when the registered workflow name and the workflow name with high similarity searched in the background do not match.

<System configuration 2 of workflow name input means>
FIG. 13 shows another configuration example of the workflow name processing means 180. The workflow name processing unit 180 here includes a similar workflow display condition storage unit 1300 in addition to the apparatus configuration shown in FIG.

  The similar workflow display unit 1001 in this embodiment determines whether to display a similar workflow according to the display conditions stored in the similar workflow display condition storage unit 1300.

  FIG. 14 shows an example of a table structure stored in the similar workflow display condition storage unit 1300. The similar workflow display condition table 1400 includes a condition ID field 1401, a user ID field 1402, an operation flag field 1403 when no workflow name is assigned, an operation flag field 1404 when a workflow name does not match, and an inter-workflow similarity threshold field 1405.

  The value of the user ID 1402 is used for collation with the value of the attending physician ID field 206 shown in FIG. 2, and the matching record becomes a display candidate. The setting of the operation flag field 1403 when the workflow name is not assigned means “1” means that the similar workflow screen 1201 is presented to the user only when the workflow name display 1200 is “unset name”. On the other hand, when the setting of the operation flag field 1403 when the workflow name is not assigned is “0”, it means that the display of the similar workflow screen 1201 does not depend on the display content of the workflow name display 1200.

  The setting of the operation flag field 1404 when the workflow name does not match is “1” means that the similar workflow screen 1201 is presented to the user only when the workflow names of the similar workflow and the similar workflow are different. On the other hand, the setting of the workflow name mismatch operation flag field 1404 “0” means that the similar workflow screen 1201 is always presented to the user.

  A numerical value of 0 to 1 is input to the inter-workflow similarity threshold field 1405. The input numerical value gives a threshold value for determining a workflow to be displayed as a similar candidate on the similar workflow screen 1201.

<Summary 4>
As described above, by preparing the similar workflow display condition storage unit 1300, it is possible to control the frequency of presenting a list of similar workflows to the user and the number of workflows presented as similar workflows. As a result, workflow name input support can be performed more efficiently.

<Other forms>
The invention described in this specification is not limited to the above-described embodiments, and includes various modifications. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described. Moreover, it is possible to replace a part of a certain form example with the structure of another form example, and it is also possible to add the structure of another form example to the structure of a certain form example. Moreover, it is also possible to add, delete, or replace another structure with respect to a part of structure of each form example.

  Moreover, you may implement | achieve some or all of each structure, a function, a process part, a process means, etc. which were mentioned above as an integrated circuit or other hardware, for example. Each of the above-described configurations, functions, and the like may be realized by the processor interpreting and executing a program that realizes each function. That is, it may be realized as software. Information such as programs, tables, and files for realizing each function can be stored in a memory, a hard disk, a storage device such as an SSD (Solid State Drive), or a storage medium such as an IC card, an SD card, or a DVD.

  Control lines and information lines indicate what is considered necessary for the description, and do not represent all control lines and information lines necessary for the product. In practice, it can be considered that almost all components are connected to each other.

  The present invention relates to a medical care support system that handles patient test values, image data, and findings of medical staff, and relates to a technology that supports judgment of medical staff in medical-related work and analysis of medical care processes.

101 Medical support system 102 Electronic medical record system 103 PACS
104 terminal 105 medical information database 106 medical information storage means 107 workflow input means 108 input information reception means 109 medical information output means 111 interface 112 memory 113 storage device 114 CPU
115 Evidence data processing means 116 Examination information database 117 Workflow step request input means 118 Workflow output means 119 Workflow end means 160 Similar case search means 170 Process analysis means 180 Workflow name processing means 200 Workflow information table 201 Patient ID field 202 Workflow No. Field 203 Workflow name field 204 Workflow start date / time field 205 Workflow end date / time field 206 Physician ID field 207 Conference flag field 210 Workflow step information field 211 Patient ID field 212 Workflow step No. Field 213 Workflow step execution scheduled department ID field 214 Workflow step execution date / time field 215 Workflow step performer ID field 216 Workflow step execution flag field 217 Conference step flag field 218 Workflow No. Field 219 Parent workflow step No. Field 220 Child workflow step No. Field 221 Workflow step type field 300 Medical information table 301 Patient ID field 305 Judgment statement field 306 Reference workflow step No. Field 310 Evidence Data Table 311 Evidence No. Field 312 Evidence type field 313 Evidence display icon field 314 Evidence display text field 320 Processing history table 321 Processing No. Field 322 Processing content field 323 Evidence No. Field 324 Processing parameter field 330 Input data table 331 Evidence No. Field 332 Input data ID field 333 Input data type field 400 Examination value table 401 Examination value ID field 402 Patient ID field 403 Examination result date field 404 Item code field 405 Value field 410 Examination item master table 411 Item code field 412 Item name field 413 Unit name field 420 Measurement value table 421 Measurement value ID field 422 Patient ID field 423 Measurement result date / time field 424 Item code field 425 Value field 430 Measurement item master table 431 Item code field 432 Item name field 433 Unit name field 434 Registration date field 440 Image table 441 Image ID field 442 Patient ID field 443 Image Date field 444 Item code field 445 Image field 600 Workflow step execution screen 601 Workflow step selection area 602 Login information display area 603 Judgment input / output area 604 Evidence data display area 605 Medical information registration button 606 Medical care support button group 607 Workflow step type Input area 610 Inspection value graph display screen 800 Image processing screen 900 Requested workflow type input area 901 Transfer sentence input area 902 Next workflow step setting button 903 Workflow step display map 904 Transfer sentence display unit 1000 Current workflow acquisition means 1001 Similar workflow display means 1002 Selected workflow accepting means 1003 Workflow name assigning means 1200 Workflow name table 1201 Similar workflow screen 1202 Similar workflow list 1203 Workflow name registration button 1300 Similar workflow display condition storage means 1400 Similar workflow display condition table 1401 Condition ID field 1402 User ID field 1403 Workflow name unassigned operation flag field 1404 Workflow name mismatched operation flag Field 1405 Inter-workflow similarity threshold field

Claims (5)

(a1) workflow information for identifying a workflow that is a flow of a series of medical treatments of medical related work; (a2) information for identifying a workflow step that is a unit of medical related work that constitutes the workflow; and Information relating to the request source and / or the request destination, workflow step information including information related to the type of the medical-related business, and (a3) medical information that is information related to the medical-related business are associated with each other. Medical information storage means for storing in the storage area;
Current workflow acquisition means for acquiring the current workflow;
Similar workflow search means for searching for a workflow similar to the current workflow from the first storage area;
Similar workflow display means for displaying a workflow similar to the current workflow;
A selected workflow receiving means for receiving information of the selected workflow;
And a workflow name assigning means for assigning a workflow name of the selected workflow as a workflow name of the current workflow. The medical assistance system according to claim 1,
A second storage area for storing a condition for displaying the similar workflow;
The said similar workflow display means displays a similar workflow according to the conditions memorize | stored in the said 2nd storage area. The medical treatment support system characterized by the above-mentioned. The medical assistance system according to claim 2,
The second storage area includes a workflow name assignment state of the current workflow, a workflow name matching state between the current workflow and the similar workflow, and a similarity between the current workflow and the similar workflow. A medical support system characterized by storing one or more conditions. (a1) workflow information for identifying a workflow that is a flow of a series of medical treatments of medical related work; (a2) information for identifying a workflow step that is a unit of medical related work that constitutes the workflow; and Information relating to the request source and / or the request destination, workflow step information including information related to the type of the medical-related business, and (a3) medical information that is information related to the medical-related business are associated with each other. A computer constituting a medical support system having medical information storage means for storing in a storage area;
Current workflow acquisition means for acquiring the current workflow;
Similar workflow search means for searching for a workflow similar to the current workflow from the first storage area;
Similar workflow display means for displaying a workflow similar to the current workflow;
A selected workflow receiving means for receiving information of the selected workflow;
A program that operates as a workflow name assigning unit that assigns the workflow name of the selected workflow as the workflow name of the current workflow. The program according to claim 4, wherein
The similar workflow display means displays a similar workflow according to a condition stored in a second storage area for storing a condition for displaying the similar workflow.

Images