JP5541527B2 - Electronic medical record management apparatus, electronic medical record management method, and program - Google Patents

Description

  The present invention relates to an electronic medical record management apparatus, an electronic medical record management method, and a program for realizing them, which are used for management of an electronic medical record.

  2. Description of the Related Art Conventionally, in medical institutions, ordering systems have been introduced that digitize routine processing such as inspection requests, prescription / inspection result references, and medical office work accounting (see, for example, Patent Document 1). The ordering system improves operational efficiency at medical institutions.

  In recent years, in medical institutions, the introduction of electronic medical record systems that digitize medical records created by doctors has been promoted, and ordering systems are increasingly being provided in electronic medical record systems. Yes.

  By the way, in a large-scale medical institution, one patient may visit a plurality of departments during one day. In such a case, a doctor in each department may request the examination department to conduct the same examination for the same patient. In order to avoid such duplicate requests, it is necessary for the doctor who performed the medical care to take measures such as inquiring of the patient and examining the status of the examination request, which is a burden on the doctor.

  In order to deal with such a problem, for example, Patent Document 1 proposes an ordering system that performs an aggregation process on overlapping inspection requests. The ordering system disclosed in Patent Document 1 searches for duplicate examination items when a plurality of doctors make the same examination request for the same patient, and automatically aggregates the duplicate examination requests into one examination request. To do. For this reason, the burden on the doctor mentioned above is reduced.

JP 2002-56087 A

  However, in the ordering system disclosed in Patent Document 1, the inspection request is transmitted to the inspection department server as it is, and the inspection department server executes the aggregation. Therefore, information related to the aggregation is described in the electronic medical record. No state.

  As a result, the authenticity and storability of the three principles required for electronic medical records are not guaranteed. Moreover, since the accounting department of a medical institution usually makes a claim for each medical department, when the examination requests are collected, a duplicate receipt is made.

  An example of an object of the present invention is to provide an electronic medical record management apparatus and an electronic medical record management method capable of solving the above-described problems and ensuring the three principles of an electronic medical record and avoiding a duplicate receipt request while consolidating inspection requests. And providing a program.

In order to achieve the above object, an electronic medical record management apparatus according to an aspect of the present invention is an electronic medical record management apparatus that manages an electronic medical record for each patient,
An inspection request receiving unit that receives an inspection request from each of a plurality of terminals;
An aggregation processing unit that identifies two or more examination requests to be aggregated for each patient from the accepted examination requests, and aggregates the identified two or more examination requests into a new one examination request When,
An electronic medical record information processing unit that identifies an electronic medical record of a patient on which aggregation has been performed, and gives information related to the aggregation to the identified electronic medical record;
It is characterized by providing.

In order to achieve the above object, an electronic medical record management method according to one aspect of the present invention is a method for managing an electronic medical record for each patient,
(A) receiving an inspection request from each of a plurality of terminals;
(B) identifying two or more examination requests to be aggregated for each patient from the accepted examination requests, and collecting the identified two or more examination requests into a new one examination request; Steps,
(C) identifying an electronic medical record of a patient on which aggregation has been performed, and providing information relating to the aggregation to the identified electronic medical record;
It is characterized by having.

Furthermore, in order to achieve the above object, a program according to one aspect of the present invention is a program for causing a computer to manage electronic medical records for each patient.
In the computer,
(A) receiving an inspection request from each of a plurality of terminals;
(B) identifying two or more examination requests to be aggregated for each patient from the accepted examination requests, and collecting the identified two or more examination requests into a new one examination request; Steps,
(C) identifying an electronic medical record of a patient on which aggregation has been performed, and providing information relating to the aggregation to the identified electronic medical record;
Is executed.

  As described above, according to the electronic medical record management apparatus, the electronic medical record management method, and the program of the present invention, it is possible to guarantee the three principles of the electronic medical record and to avoid the duplicate receipt request while performing the aggregation of inspection requests. To do.

FIG. 1 is a block diagram showing a configuration of an electronic medical record management apparatus according to an embodiment of the present invention. FIG. 2 is a diagram showing an example of an examination inquiry screen displayed on the administrator's terminal in the embodiment of the present invention. FIG. 3 is a flowchart showing the operation of the electronic medical chart management apparatus according to the embodiment of the present invention. 4A to 4C are diagrams showing examples of inspection request information registered in the inspection request information database in the embodiment of the present invention. Each of FIGS. 5A to 5C is a diagram showing an example of electronic medical record information registered in the electronic medical record information database in the embodiment of the present invention. FIG. 6 is a diagram showing an example of the aggregation condition set in the embodiment of the present invention. FIG. 7 is a diagram showing an example of the aggregate inspection information registered in the inspection aggregate information database in the embodiment of the present invention. Each of FIGS. 8A to 8C is a diagram illustrating an example of the aggregated electronic medical record information registered in the electronic medical record information database in the embodiment of the present invention. FIG. 9 is a diagram showing another example of the aggregated inspection information registered in the inspection aggregated information database in the embodiment of the present invention. FIGS. 10A to 10D are diagrams showing other examples of the consolidated electronic medical record information registered in the electronic medical record information database in the embodiment of the present invention. FIG. 11 is a flowchart showing an operation at the time of the aggregation release processing of the electronic medical record management apparatus according to the embodiment of the present invention. FIG. 12 is a diagram showing an example of an aggregation status confirmation screen displayed on the administrator's terminal in the embodiment of the present invention. Each of FIGS. 13A to 13D is a diagram illustrating an example of the electronic medical record information after aggregation cancellation registered in the electronic medical record information database in the embodiment of the present invention. FIG. 14 is a block diagram illustrating an example of a computer that implements the electronic medical record management apparatus according to the embodiment of the present invention.

(Embodiment)
Hereinafter, an electronic medical record management apparatus, an electronic medical record management method, and a program according to an embodiment of the present invention will be described with reference to FIGS.

[Configuration of electronic medical record management device]
First, the configuration of the electronic medical record management apparatus according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing a configuration of an electronic medical record management apparatus according to an embodiment of the present invention. An electronic medical record management apparatus 1 in the present embodiment shown in FIG. 1 is an apparatus that manages an electronic medical record for each patient, and has a function as an ordering system. As shown in FIG. 1, the electronic medical record management apparatus 1 includes an examination request receiving unit 2, an aggregation processing unit 3, and an electronic medical record information processing unit 4.

  The inspection request reception unit 2 receives inspection requests from each of the plurality of terminals 9. The aggregation processing unit 3 identifies two or more examination requests to be aggregated for each patient from the examination requests received by the examination request receiving unit 2. Then, the aggregation processing unit 3 aggregates the specified two or more examination requests into a new one examination request for each patient. The electronic medical record information processing unit 4 specifies the electronic medical record of the patient on which the aggregation is performed, and gives information related to the aggregation to the specified electronic medical record.

  As described above, when an examination request is made from the terminal 9, the electronic medical chart management apparatus 1 performs aggregation processing before the examination is performed in the examination department of the medical institution, and writes information relating to aggregation into the electronic medical chart. For this reason, according to the electronic medical record management apparatus 1, it is possible to guarantee the three principles of the electronic medical record and to avoid duplicate receipt requests while consolidating examination requests.

  Here, the configuration of the electronic medical chart management apparatus 1 will be described more specifically with reference to FIG. 2 in addition to FIG. FIG. 2 is a diagram showing an example of an examination inquiry screen displayed on the administrator's terminal in the embodiment of the present invention.

  As shown in FIG. 1, in the present embodiment, the electronic medical record management device 1 includes an inspection request information database 5, an integrated inspection information database 6, and an electronic medical record information database 7. The inspection request information database 5 stores information (hereinafter referred to as “inspection request information”) for specifying the inspection request received by the inspection request receiving unit 2. The integrated inspection information database 6 stores information (hereinafter referred to as “aggregated inspection information”) that identifies a new inspection request obtained by the aggregation performed by the aggregation processing unit 3.

  In addition, the electronic medical record information database 7 stores information (hereinafter referred to as “electronic medical record information”) for specifying a patient's medical record. Further, in the electronic medical record information database 7, the electronic medical record information includes information related to aggregation given by the electronic medical record information processing unit 4. For this reason, the three principles of electronic medical records are guaranteed.

  The electronic medical record management apparatus 1 is constructed by a server computer. Furthermore, an administrator terminal 8 is connected to the electronic medical record management apparatus 1. An instruction of aggregation processing by the administrator is performed via the terminal 8. The administrator may be a doctor or a person in charge of the examination department.

  Furthermore, as shown in FIG. 1, a terminal 9 used in the medical department is also connected to the electronic medical chart management apparatus 1. The examination request from each medical department is made through each terminal 9. In the example of FIG. 1, one of the terminals 9 is a terminal used in internal medicine, and the other is a terminal used in surgery. In FIG. 1, only terminals used in two medical departments, ie, internal medicine and surgery, are shown, but the present embodiment is not limited to this. A terminal used in another medical department may be connected to the electronic medical record management apparatus 1.

  Moreover, since the examination request screen 20 is displayed on the display screen of each terminal 9, an operator such as a doctor inputs necessary items on the examination request screen 20, and data including the input items (examination request information). Send. The transmitted examination request information is received by the electronic medical chart management apparatus 1 via the LAN in the medical institution.

  When the inspection request information is transmitted from each terminal 9, in the electronic medical record management apparatus 1, the inspection request receiving unit 2 receives and receives them. The inspection request reception unit 2 sends the received inspection request information to the inspection request information database 5. Thereby, in the examination request information database 5, examination request information transmitted from the doctors of each medical department via the terminal 9 is registered.

  In the present embodiment, the aggregation processing unit 3 acquires the examination request information from the examination request information database 5 and, according to an instruction from the administrator, two or more examinations to be aggregated for each patient. Identify the request. Specifically, the aggregation processing unit 3 displays the inspection inquiry screen 10 shown in FIG. 2 on the display screen of the administrator's terminal 8, and on the inspection inquiry screen, the administrator requests the inspection to be an aggregation target. Instruct.

  Furthermore, in this embodiment, each inspection request can include a plurality of inspection types. The examination type means each examination included in the examination request, and is represented by an examination object such as “blood”, “urine”, and “stool”. In this case, the aggregation processing unit 3 specifies the inspection request to be aggregated for each inspection type. That is, the aggregation processing unit 3 can also specify only a part of the inspection types included in the inspection request that is an object of aggregation.

  In the example of FIG. 2, the examination inquiry screen 10 displays patient information 11 and an examination request list 12 that indicates a list of examination requests that have not been performed on the patient. The inspection request list 12 includes three inspection requests 14 to 16. Each examination request is issued from each clinical department every day and includes a plurality of examination types. Further, the inspection inquiry screen 10 is configured such that an inspection request to be aggregated can be selected for each inspection type from inspection requests displayed in the inspection request list 12 by input.

  The administrator determines whether or not each inspection request displayed in the inspection request list 12 is to be aggregated for each examination type, clicks on the examination type to be aggregated, and selects it. In the examination inquiry screen 10, a mark is displayed on the examination type selected by the administrator so that the administrator can determine that the examination is selected on the screen. In the example of FIG. 2, “☆” is displayed for the selected examination type.

  In FIG. 12, reference numeral 13 denotes an “aggregation execution button”. When the administrator presses the aggregation execution button 13, the aggregation processing unit 3 aggregates inspection requests including the inspection type selected in the inspection order list 12 and creates a new inspection request.

  Further, in the present embodiment, the aggregation processing unit 3 determines whether or not aggregation is possible for each of two or more inspection requests specified as the aggregation target based on the inspection contents and the reservation status of the inspection. Can do. In this case, the aggregation processing unit 3 aggregates two or more inspection requests determined to be able to be aggregated into a new one inspection request. Note that determination and aggregation in this case can also be performed in units of examination types.

  When the aggregation processing unit 3 creates a new inspection request by aggregation, the aggregation processing unit 3 sends aggregate inspection information for specifying the request to the aggregation inspection information database 6. When the aggregate inspection information database 6 receives the aggregate inspection information, it stores it.

  Further, in the present embodiment, the electronic medical record information processing unit 4 acquires aggregated inspection information from the aggregated inspection information database 6, and each inspection request that is the source of aggregation, and a new inspection request obtained by the aggregation, Is identified. Then, the electronic medical record information processing unit 4 includes information (see FIGS. 8A and 8B to be described later) for specifying the examination request that is the source of the aggregation, and new information obtained by the aggregation as information relating to the aggregation. Information for specifying an inspection request (see FIG. 8C described later) is used. Further, the electronic medical record information processing unit 4 gives these pieces of information to the electronic medical record information stored in the electronic medical record information database.

[Operation of electronic medical record management device]
Next, operation | movement of the electronic medical chart management apparatus 1 in embodiment of this invention is demonstrated using FIGS. FIG. 3 is a flowchart showing the operation of the electronic medical chart management apparatus according to the embodiment of the present invention.

  In the following description, FIGS. 1 and 2 are referred to as appropriate. Moreover, in this Embodiment, the electronic medical chart management method is implemented by operating the electronic medical chart management apparatus 1. Therefore, the description of the electronic medical chart management method in the present embodiment is replaced with the following description of the operation of the electronic medical chart management apparatus 1.

  As shown in FIG. 3, first, the examination request accepting unit 2 accepts an examination request sent from the terminal 9 in each department (step A1). Specifically, the inspection request reception unit 2 receives inspection request information transmitted by the terminal 9. Then, the inspection request reception unit 2 stores the received inspection request information in the inspection request information database 5 as shown in FIGS. 4A to 4C are diagrams showing examples of inspection request information registered in the inspection request information database in the embodiment of the present invention. 4A to 4C, reference numerals 21 to 23 denote inspection request information, respectively.

  Moreover, in this Embodiment, when step A1 is performed, the electronic medical chart information processing part 4 will perform FIG. 5 (a)-based on each test | inspection request information shown to Fig.4 (a)-(c). Electronic medical chart information shown in FIG. 5C is created and stored in the electronic medical chart information database 7. Each of FIGS. 5A to 5C is a diagram showing an example of electronic medical record information registered in the electronic medical record information database in the embodiment of the present invention. 5A to 5C, reference numerals 31 to 33 denote electronic medical record information, respectively.

  Next, the aggregation processing unit 3 acquires two or more examination requests selected by the administrator via the terminal 8 for each patient (step A2). In the present embodiment, on the inspection inquiry screen 10 shown in FIG. 2, the administrator aggregates the inspection requests on the same day, that is, all inspection types of the inspection request 14 and all inspection types of the inspection request 15. Selected as the target of Therefore, the aggregation processing unit 3 acquires the inspection request information shown in FIG. 4A and the inspection request information shown in FIG.

  Next, the aggregation processing unit 3 selects one of the inspection requests acquired in Step A2 (Step A3). Then, the aggregation processing unit 3 determines whether or not the selected inspection request can be aggregated (step A4). Specifically, the aggregation processing unit 3 determines whether or not aggregation is possible based on the reservation status of each examination type included in the selected examination request.

  That is, since the aggregation is performed on an inspection performed on a future date, the month in which the inspection is performed may be changed. In addition, since there are inspection types that have a fixed number of times that can be performed on a monthly basis, there may be cases where the inspection cannot be performed depending on the inspection reservation status at the inspection organization. For this reason, in step A4, for example, the aggregation processing unit 3 accesses the server of the inspection organization and checks how many times the corresponding inspection (inspection type) is scheduled to be executed in the scheduled month. It is determined whether or not the feasible number has been reached.

  As a result of the determination in step A4, if the acquired inspection requests are not in a state where they can be aggregated, that is, if the scheduled number of executions in the inspection organization of any of the inspection types included therein has reached the possible number of times, step A8 Is executed. On the other hand, as a result of the determination in step A4, when the acquired inspection requests are in a state where they can be aggregated, that is, when the scheduled number of times of execution in the inspection organization included in the inspection type has not reached the possible number of times, the aggregation process Unit 3 executes step A5.

  In step A5, the aggregation processing unit 3 selects one examination type included in the examination request selected in step A3, and determines whether the examination contents of the selected examination type are contents that can be aggregated. Specifically, the bacteria test and the load / day test cannot be performed on the same day as other tests, and cannot be integrated. In the present embodiment, only general inspections can be collected. Therefore, the aggregation processing unit 3 selects one inspection type included in the inspection request selected in step A3, and determines whether the inspection content is a general inspection for the selected inspection type.

  As a result of the determination in step A5, if the examination contents are not contents that can be aggregated, the aggregation processing unit 3 executes step A7. On the other hand, as a result of the determination in step A5, if the contents of the inspection are contents that can be consolidated, the aggregation processing unit 3 executes step A6.

  In step A6, the aggregation processing unit 3 checks whether or not the inspection request selected in step A3 includes the same inspection type as the inspection type selected in step A4. It is determined that the inspection contents can be consolidated for the inspection types.

  Next, the aggregation processing unit 3 determines whether another inspection type is included in the inspection request selected in Step A3 (Step A7). If the result of determination in step A7 is that another examination type is included, the aggregation processing unit 3 executes step A5 again. On the other hand, as a result of the determination in step A7, when another examination type is not included, the aggregation processing unit 3 executes step A8.

  In step A8, the aggregation processing unit 3 determines whether there is another inspection request that has not yet been selected. If there is another inspection request that has not been selected as a result of the determination in step A8, the aggregation processing unit 3 executes step A3 again. On the other hand, if the result of determination in step A8 is that there is no other inspection request that has not yet been selected, the aggregation processing unit 3 executes step A9.

  In step A9, the aggregation processing unit 3 performs aggregation using the examination type determined to be aggregated in step A5 in the examination request determined to be in a status that can be aggregated in step A3, and creates a new Create an inspection request.

  In the present embodiment, the aggregation processing unit 3 executes the aggregation processing according to the conditions shown in FIG. Further, the aggregation processing unit 3 creates aggregated inspection information 40 shown in FIG. 7 and stores it in the inspection consolidated information database 6. FIG. 6 is a diagram showing an example of the aggregation condition set in the embodiment of the present invention. FIG. 7 is a diagram showing an example of the aggregate inspection information registered in the inspection aggregate information database in the embodiment of the present invention.

  Next, after the execution of step A9, as shown in FIGS. 8A to 8C, the electronic medical record information processing unit 4 specifies the electronic medical record information of the patient on which the aggregation is performed, and the specified electronic medical record information Information about the aggregation is given to (step A10). Each of FIGS. 8A to 8C is a diagram illustrating an example of the aggregated electronic medical record information registered in the electronic medical record information database in the embodiment of the present invention.

  Specifically, in step A <b> 10, first, the electronic medical record information processing unit 4 acquires the aggregate examination information 40 from the aggregate examination information database 6. Then, the electronic medical record information processing unit 4 specifies the electronic medical record information of each inspection request that is the source of the aggregation, based on the “old request number” included in the aggregate inspection information 40. Then, as shown in FIGS. 8A and 8B, the electronic medical record information processing unit 4 sets the processing classification of the electronic medical record information 41 and 42 of the examination request that is the source of aggregation to “aggregate deletion”. . As a result, in the electronic medical record, it is clearly indicated that the inspection request that is the source of aggregation is deleted.

  Furthermore, the electronic medical record information processing unit 4 specifies a new examination request obtained by aggregation based on the acquired aggregate examination information. Then, as shown in FIG. 8C, the electronic medical record information processing unit 4 creates electronic medical record information 43 corresponding to a new examination request obtained by aggregation. Further, the electronic medical record information processing unit 4 sets the processing category of the electronic medical record information 43 to “aggregate new”. This clearly indicates that this inspection request is a new inspection request obtained by aggregation.

  As described above, the processing in the electronic medical chart management apparatus is completed by executing Steps A1 to A10. The combined inspection request is sent to a server device or the like of the inspection department, and then the inspection is executed in the inspection department.

  As described above, in the present embodiment, the fact that the aggregation process has been performed on a plurality of inspection requests is stored in the electronic medical record, so that authenticity and storability corresponding to the three principles of the medical record are ensured. Moreover, it is thought that this suppresses generation | occurrence | production of the lawsuit between a patient and a medical institution. In addition, since the accounting department of a medical institution can make a claim for each examination request, duplicate receipt requests are suppressed. Thereby, it is considered that the economic burden on the patient side can be reduced.

[Modification 1]
In the example described with reference to FIGS. 1 to 8, the administrator selects the inspection request 14 and the inspection request 15 requested on the same day as the aggregation target on the inspection inquiry screen 10 illustrated in FIG. 2. However, the present embodiment is not limited to the above example. In the present embodiment, if an inspection request is not yet performed, aggregation can be performed without being influenced by the requested date.

  An example in which inspection requests having different requested dates are collected will be described below with reference to FIGS. 9 and 10. FIG. 9 is a diagram showing another example of the aggregated inspection information registered in the inspection aggregated information database in the embodiment of the present invention. FIGS. 10A to 10D are diagrams showing other examples of the consolidated electronic medical record information registered in the electronic medical record information database in the embodiment of the present invention.

  In this example, on the inspection inquiry screen 10 shown in FIG. 2, the administrator selects all inspection types of the inspection request 14, all inspection types of the inspection request 15, and all inspection types of the inspection request 16. Select as the target of aggregation. The aggregation processing unit 3 creates aggregate inspection information 50 shown in FIG. 9 and stores it in the inspection aggregation information database 6.

  In this example, as shown in FIGS. 10A to 10D, the electronic medical record information processing unit 4 gives information related to aggregation to the electronic medical record information 51 to 54. Specifically, as illustrated in FIGS. 10A to 10C, the electronic medical record information processing unit 4 performs “aggregation deletion” as the processing classification of the electronic medical record information 51 to 53 of the examination request that is the source of the aggregation. Set to. As a result, in the electronic medical record, it is clearly indicated that the inspection request that is the source of aggregation is deleted.

  Further, the electronic medical record information processing unit 4 specifies a new examination request obtained by aggregation based on the aggregate examination information 50. Then, as shown in FIG. 10D, electronic medical record information 54 corresponding to a new inspection request is created. In addition, the electronic medical record information processing unit 4 sets the processing category of the electronic medical record information 54 to “aggregate new”. This clearly indicates that this inspection request is a new inspection request obtained by aggregation.

[Modification 2]
In the present embodiment, the aggregation can be canceled for the inspection request newly created by the aggregation (hereinafter referred to as “aggregated inspection request”). Hereinafter, an example in which the electronic medical record management apparatus 1 cancels aggregation will be described with reference to FIGS. 11 to 13. In the following description, FIG. 1 is taken into consideration as appropriate.

  FIG. 11 is a flowchart showing an operation at the time of the aggregation release processing of the electronic medical record management apparatus according to the embodiment of the present invention. FIG. 12 is a diagram showing an example of an aggregation status confirmation screen displayed on the administrator's terminal in the embodiment of the present invention. Each of FIGS. 13A to 13D is a diagram illustrating an example of the electronic medical record information after aggregation cancellation registered in the electronic medical record information database in the embodiment of the present invention.

  First, as shown in FIG. 11, the aggregation processing unit 3 (see FIG. 1) displays an aggregation status confirmation screen 60 shown in FIG. 12 on the display screen of the terminal 8 in response to an instruction from the terminal 8 of the administrator. Display (step B1). In the present embodiment, when the administrator presses the aggregation execution button 3 on the examination inquiry screen 10 shown in FIG. 2, an aggregation status confirmation screen 60 is displayed.

  In the example of FIG. 12, the aggregation status confirmation screen 60 displays patient information 61, an aggregated examination request list 62 that shows a list of aggregated examination requests that have not been performed on the patient, and an aggregation cancellation button 63. In the example of FIG. 12, there is one aggregated inspection request displayed in the aggregated inspection request list 62.

  Next, when the administrator selects an aggregation inspection request for which aggregation cancellation is requested on the aggregation status confirmation screen 60 and presses the aggregation cancellation button 63, the aggregation processing unit 3 causes the aggregation inspection information 50 of the selected aggregation inspection request. (See FIG. 9) is acquired (step B2).

  Next, the aggregation processing unit 3 creates inspection request information (see FIGS. 4A to 4C) that identifies the original inspection request, using the old request number registered in the aggregation inspection information 50. The created inspection request information is stored in the inspection request information database 5 (step B3). Subsequently, the aggregation processing unit 3 deletes the aggregation inspection information 50 of the selected aggregation inspection request from the inspection aggregation information database 6 (step B4). As a result, the selected aggregation inspection request is deleted, and the aggregation is released.

  Next, the electronic medical record information processing unit 4 identifies the electronic medical record information of the patient whose aggregation has been canceled, and gives information regarding the aggregation cancellation to the identified electronic medical record information (step B5).

  Specifically, in step B5, first, the electronic medical record information processing unit 4 uses the old request number registered in the centralized inspection information 50 to obtain the electronic medical record information of each inspection request that is the source of the aggregation. Identify. Then, as shown in FIGS. 13A to 13C, the electronic medical record information processing unit 4 sets the processing classification of the electronic medical record information 71 to 73 of the examination request that is the source of the aggregation to “cancel aggregation”. To do. As a result, in the electronic medical record, it is clearly indicated that the aggregation is cancelled.

  Furthermore, the electronic medical record information processing unit 4 specifies the electronic medical record information of the intensive examination request using the request number registered in the intensive examination information 50. Then, as illustrated in FIG. 13D, the electronic medical record information processing unit 4 sets the processing classification of the electronic medical record information 74 of the intensive examination request to “delete”. This clearly indicates that this aggregate inspection request has been deleted.

[program]
The program in the present embodiment may be a program that causes a computer to execute steps A1 to A10 shown in FIG. 3 and further steps B1 to B5 shown in FIG. By installing and executing this program on a computer, the electronic medical chart management apparatus 1 and the electronic medical chart management method according to the present embodiment can be realized. In this case, a CPU (Central Processing Unit) of the computer functions as the inspection request reception unit 2, the aggregation processing unit 3, and the electronic medical record information processing unit 4 to perform processing.

  The examination request information database 5, the examination aggregation information database 6, and the electronic medical record information database 7 are realized by a storage device such as a hard disk. Furthermore, the storage device may be provided in a computer in which the program according to the present embodiment is installed, or may be provided in another computer connected to the computer via a network.

  Here, a computer that realizes the electronic medical record management 1 by executing the program in the embodiment will be described with reference to FIG. FIG. 14 is a block diagram illustrating an example of a computer that implements the electronic medical record management apparatus according to the embodiment of the present invention.

  As illustrated in FIG. 14, the computer 110 includes a CPU 111, a main memory 112, a storage device 113, an input interface 114, a display controller 115, a data reader / writer 116, and a communication interface 117. These units are connected to each other via a bus 121 so that data communication is possible.

  The CPU 111 performs various calculations by developing the program (code) in the present embodiment stored in the storage device 113 in the main memory 112 and executing them in a predetermined order. The main memory 112 is typically a volatile storage device such as a DRAM (Dynamic Random Access Memory). Further, the program in the present embodiment is provided in a state of being stored in a computer-readable recording medium 120. Note that the program in the present embodiment may be distributed on the Internet connected via the communication interface 117.

  Specific examples of the storage device 113 include a hard disk and a semiconductor storage device such as a flash memory. The input interface 114 mediates data transmission between the CPU 111 and an input device 118 such as a keyboard and a mouse. The display controller 115 is connected to the display device 119 and controls display on the display device 119. The data reader / writer 116 mediates data transmission between the CPU 111 and the recording medium 120, and reads a program from the recording medium 120 and writes a processing result in the computer 110 to the recording medium 120. The communication interface 117 mediates data transmission between the CPU 111 and another computer.

  Specific examples of the recording medium 120 include general-purpose semiconductor storage devices such as CF (Compact Flash) and SD (Secure Digital), magnetic storage media such as a flexible disk, or CD-ROM (Compact Disk). Optical storage media such as Read Only Memory).

  Part or all of the above-described embodiment can be expressed by (Appendix 1) to (Appendix 15) described below, but is not limited to the following description.

(Appendix 1)
An electronic medical record management device for managing an electronic medical record for each patient,
An inspection request receiving unit that receives an inspection request from each of a plurality of terminals;
An aggregation processing unit that identifies two or more examination requests to be aggregated for each patient from the accepted examination requests, and aggregates the identified two or more examination requests into a new one examination request When,
An electronic medical record information processing unit that identifies an electronic medical record of a patient on which aggregation has been performed, and gives information related to the aggregation to the identified electronic medical record;
An electronic medical chart management apparatus comprising:

(Appendix 2)
The electronic medical chart management apparatus according to appendix 1, wherein the aggregation processing unit identifies the two or more examination requests to be aggregated based on an instruction from the outside.

(Appendix 3)
The aggregation processing unit determines whether aggregation is possible for each of the two or more specified inspection requests, and sets the two or more inspection requests that are determined to be aggregation as the new one inspection request. Summarize,
The electronic medical chart management apparatus according to appendix 1 or 2.

(Appendix 4)
The electronic medical record information processing unit specifies information for identifying each of the two or more examination requests that are a source of aggregation and the new one examination request as information relating to the aggregation in the identified electronic medical chart. The electronic medical chart management apparatus according to any one of supplementary notes 1 to 3, which provides information.

(Appendix 5)
Any one of appendices 1 to 4, wherein when the received inspection request includes a plurality of inspection types, the aggregation processing unit specifies the two or more inspection requests to be aggregated in units of inspection types. The electronic medical chart management apparatus according to 1.

(Appendix 6)
A method for managing an electronic medical record for each patient,
(A) receiving an inspection request from each of a plurality of terminals;
(B) identifying two or more examination requests to be aggregated for each patient from the accepted examination requests, and collecting the identified two or more examination requests into a new one examination request; Steps,
(C) identifying an electronic medical record of a patient on which aggregation has been performed, and providing information relating to the aggregation to the identified electronic medical record;
An electronic medical chart management method characterized by comprising:

(Appendix 7)
The electronic medical chart management method according to appendix 6, wherein in the step (b), the two or more examination requests to be aggregated are specified based on an instruction from the outside.

(Appendix 8)
In the step (b), for each of the two or more specified inspection requests, it is determined whether it can be aggregated, and two or more inspection requests that are determined to be capable of being aggregated are referred to as the new one inspection. Consolidate requests,
The electronic medical chart management method according to appendix 6 or 7.

(Appendix 9)
In the step (c), information specifying each of the two or more inspection requests that are the source of aggregation and the new one inspection request are specified as information relating to the aggregation in the identified electronic medical record. The electronic medical chart management method according to any one of appendices 6 to 8, wherein information is provided.

(Appendix 10)
When the inspection request received in the step (a) includes a plurality of inspection types, in the step (b), the two or more inspection requests to be aggregated are specified for each inspection type. The electronic medical chart management method according to any one of appendices 6 to 9.

(Appendix 11)
A program for causing a computer to manage electronic medical records for each patient,
In the computer,
(A) receiving an inspection request from each of a plurality of terminals;
(B) identifying two or more examination requests to be aggregated for each patient from the accepted examination requests, and collecting the identified two or more examination requests into a new one examination request; Steps,
(C) identifying an electronic medical record of a patient on which aggregation has been performed, and providing information relating to the aggregation to the identified electronic medical record;
A program that executes

(Appendix 12)
The program according to appendix 11, wherein in the step (b), the two or more inspection requests to be aggregated are specified based on an instruction from the outside.

(Appendix 13)
In the step (b), for each of the two or more specified inspection requests, it is determined whether it can be aggregated, and two or more inspection requests that are determined to be capable of being aggregated are regarded as the new one inspection. Consolidate requests,
The program according to appendix 11 or 12.

(Appendix 14)
In the step (c), information specifying each of the two or more inspection requests that are the source of aggregation and the new one inspection request are specified as information relating to the aggregation in the identified electronic medical record. The program according to any one of appendices 11 to 13, which provides information.

(Appendix 15)
When the inspection request received in the step (a) includes a plurality of inspection types, in the step (b), the two or more inspection requests to be aggregated are specified for each inspection type. The program according to any one of appendices 11 to 14.

  As described above, according to the present invention, it is possible to guarantee the three principles of the electronic medical record and avoid duplicate receipt requests while collecting examination requests in a medical institution. The present invention is useful for an electronic medical record system in a general hospital or the like having many departments.

DESCRIPTION OF SYMBOLS 1 Electronic medical record management apparatus 2 Examination request reception part 3 Consolidated processing part 4 Electronic medical record information processing part 5 Examination request information database 6 Examination aggregation information database 7 Electronic medical record information database 8 Manager's terminal 9 Terminal of each medical department 10 Examination inquiry screen 11 Patient Information 12 List of Examination Requests 13 Aggregation Execution Button 14, 15, 16 Examination Request 20 Examination Request Screen 21, 22, 23 Examination Request Information 31, 32, 33 Electronic Medical Record Information 40 Central Examination Information 41, 42, 43 Electronic Medical Record Information 50 Centralized Examination Information 51, 52, 53, 54 Electronic Medical Record Information 60 Consolidation Status Confirmation Screen 61 Patient Information 62 Centralized Examination Request List 63 Consolidation Cancel Button 71, 72, 73, 74 Electronic Medical Record Information 110 Computer 111 CPU
112 Main Memory 113 Storage Device 114 Input Interface 115 Display Controller 116 Data Reader / Writer 117 Communication Interface 118 Input Device 119 Display Device 120 Recording Medium 121 Bus

Claims (6)

An electronic medical record management device for managing an electronic medical record for each patient,
An inspection request receiving unit that receives an inspection request from each of a plurality of terminals;
An inspection request information storage unit for storing inspection request information that is information included in the inspection request received by the inspection request reception unit;
Reading the examination request information stored in the examination request information storage unit, and based on the examination request information, creating an electronic medical record information of a patient; and
An electronic medical record information storage unit for storing the electronic medical record information created by the electronic medical record information processing unit;
The two or more examination requests received by the examination request accepting unit are acquired, and two or more examination requests to be aggregated are identified and specified for each patient from the obtained examination requests. An aggregation processing unit that aggregates the above inspection requests into a new inspection request;
An aggregate inspection information storage unit that stores aggregate inspection information for specifying the one new inspection request aggregated by the aggregation processing unit and the two or more inspection requests that are the source of the aggregation; ,
The electronic medical record information processing unit reads the aggregated inspection information stored in the aggregated inspection information storage unit, and based on the aggregated inspection information, the two or more inspection requests that are the sources of the aggregation, Information specifying a new one examination request and setting a processing category for each of the two or more examination requests that are the source of the aggregation in the electronic medical record of the patient stored in the electronic medical record information storage unit And an electronic medical record information processing unit for assigning information in which a processing category is set to the new one inspection request ,
An electronic medical chart management apparatus comprising: The aggregation processing unit identifies the two or more inspection requests to be aggregated from two or more of the inspection requests received by the inspection request receiving unit based on an instruction from the outside. The electronic medical record management apparatus according to 1. The aggregation processing unit acquires information for determining whether the two or more inspection requests can be aggregated , and aggregates each of the two or more inspection requests specified based on the acquired information. Determining whether it is possible and consolidating the two or more inspection requests determined to be capable of being aggregated into the new one inspection request;
The electronic medical chart management apparatus according to claim 1 or 2. When the inspection request received by the inspection request reception unit includes a plurality of inspection types, the aggregation processing unit specifies the two or more inspection requests to be aggregated in units of inspection types. Item 4. The electronic medical chart management device according to any one of Items 1 to 3 . A method for managing an electronic medical record for each patient,
(A) computer, a plurality of terminals, Installing inspected request, and stores the inspection request information is information included in the inspection request accepted in the storage device of the computer, the steps,
(B) The computer reads the examination request information stored in the storage device, creates electronic medical record information of a patient based on the examination request information, and stores the created electronic medical record information in the storage device. Remember, step,
( C ) The computer identifies, for each patient, two or more examination requests to be aggregated from the accepted examination requests, and the identified two or more examination requests are a new one examination request. Storing in the storage device aggregate examination information for identifying the new one examination request that has been aggregated and the two or more examination requests that are the source of the aggregation ;
( D ) The computer reads the aggregate inspection information stored in the storage device, and based on the aggregate inspection information, the two or more inspection requests that are the basis of the aggregation, and the new one The examination request is specified, and the information of setting the processing category for each of the two or more examination requests that is the source of the aggregation in the electronic medical record of the patient stored in the storage device, and the new one A step of assigning information in which a processing category is set to the inspection request ; and
An electronic medical chart management method characterized by comprising: A program for causing a computer to manage electronic medical records for each patient,
In the computer,
From each (a) a plurality of terminals, Installing inspected request, and stores the inspection request information is information included in the inspection request accepted in the storage device of the computer, the steps,
(B) reading the examination request information stored in the storage device, creating electronic medical record information of a patient based on the examination request information, and storing the created electronic medical record information in the storage device; When,
( C ) Identifying two or more examination requests to be aggregated for each patient from the accepted examination requests, collecting the identified two or more examination requests into a new one examination request , Storing in the storage device aggregate inspection information for specifying the new one inspection request that has been aggregated and the two or more inspection requests that have been the source of the aggregation ;
( D ) Reading the aggregate inspection information stored in the storage device, and based on the aggregate inspection information, the two or more inspection requests that are the source of the aggregation, and the new one inspection request Identify and process information for each of the two or more examination requests that are the source of aggregation in the patient's electronic medical record stored in the storage device and the new one examination request A step of assigning information with set divisions, and
A program that executes

Images