WO2009128296A1 - Regional medical cooperation system, registration terminal, and program - Google Patents

Abstract

A burden of operation for registering medical data in the medical facility in a regional medical cooperation server is reduced. A registration terminal (10) installed in the medical facility (100) collects (acquires) various kinds of information relating to the examination (data relating to the examination) designated on a selection/registration screen, from an image server (20), a report management server (50), and an electronic medical chart server (80). The registration terminal (10) generates link information on the basis of the various kinds of collected information (information accompanying medical image data, remark report data, and a user information record). Then, the registration terminal (10) transmits the generated link information to the regional medical cooperation server (90), which registers the received link information to a registry.

Description

Regional medical cooperation system, registration terminal and program

The present invention relates to a regional medical cooperation system, a registration terminal, and a program.

In recent years, with the development of medical technology, a framework for regional medical cooperation in which medical facilities such as hospitals and clinics with specific functions cooperate to treat patients is becoming widespread.

For example, in order to share medical data managed in each medical facility with the entire group of medical facilities (the entire region), a server (regional medical cooperation server) that manages the location, data type, target patient, etc. of the medical data By installing and accessing the server, it is possible to supply and acquire each other's medical data.

Specifically, a technology is disclosed in which a medical facility that introduces a patient registers patient information in a regional medical cooperation server, and a medical facility that introduces a patient acquires patient information from the regional medical cooperation server (patent) Reference 1).
JP 2005-122380 A

However, when registering medical data in the regional medical cooperation server, a user such as a doctor needs to input information (patient information, examination information) and the like related to the medical data one by one, which is troublesome. In addition, there is a possibility that registration omission or registration error may occur due to user input.

The present invention has been made in view of the above-described problems, and an object of the present invention is to reduce the work load for registering medical data in a self-medical facility in a regional medical cooperation server.

In order to solve the above problems, the invention described in claim 1
A regional medical cooperation system in which a medical data liaison server that manages the location of medical data in each medical facility and a registration terminal installed in the medical facility are connected to enable data communication via a communication network,
The regional medical cooperation server
A communication means for transmitting / receiving various data to / from an external device;
Storage means for storing a registry for managing the location of medical data in each medical facility;
Control means for registering the location of the medical data and the various information about the medical data in the registry when the communication unit receives the location of the medical data and the various information about the medical data from the registration terminal;
With
The registered terminal
A communication means for transmitting / receiving various data to / from an external device;
A designation means for designating medical data of a self-care facility to be registered in the registry;
Information relating to medical data designated by the designation means via the communication means for each device installed in the own medical facility that has storage means for storing information relating to the medical data and manages information relating to the medical data To obtain various information related to the designated medical data from each device, and together with the location of the designated medical data, send the various information related to the designated medical data via the communication means. Control means for transmitting to the regional medical cooperation server;
Is provided.

The invention according to claim 2 is the invention according to claim 1,
The control means of the registration terminal includes:
The consistency of various information related to the specified medical data acquired from each device is determined, and if there is no consistency, the fact is displayed on the display screen.

The invention described in claim 3
A registration terminal installed in a medical facility,
A communication means for transmitting / receiving various data to / from an external device;
A designation means for designating medical data of a self-care facility to be registered in a registry for managing the location of medical data in each medical facility;
Information relating to medical data designated by the designation means via the communication means for each device installed in the own medical facility that has storage means for storing information relating to the medical data and manages information relating to the medical data To obtain various information related to the designated medical data from each device, and together with the location of the designated medical data, send the various information related to the designated medical data via the communication means. Control means for transmitting to a regional medical cooperation server having storage means for storing the registry;
Is provided.

The program according to claim 4 is:
Computers installed in medical facilities
Communication means for sending and receiving various data with external devices,
A designation means for designating medical data of the own medical facility, which is to be registered in the registry for managing the location of the medical data in each medical facility;
Information relating to medical data designated by the designation means via the communication means for each device installed in the own medical facility that has storage means for storing information relating to the medical data and manages information relating to the medical data To obtain various information related to the designated medical data from each device, and together with the location of the designated medical data, send the various information related to the designated medical data via the communication means. Control means for transmitting to a regional medical cooperation server having storage means for storing the registry;
To function as.

According to the first, third, and fourth aspects of the invention, the control means of the registration terminal installed in a certain medical facility designates each device installed in the own medical facility that stores and manages information related to medical data. A request for acquiring information on the designated medical data, obtaining various types of information on the designated medical data from each of the devices, and providing various types of information on the designated medical data together with the location of the designated medical data. Send to regional medical cooperation server. Therefore, it is possible to reduce the work burden of registering medical data in the self-care facility with the regional medical cooperation server.

According to a second aspect of the present invention, the control means of the registration terminal determines the consistency of various information related to medical data acquired from each device, and if there is no consistency, displays that fact on the display screen. To do. Therefore, the user can know that the information registered in the regional medical cooperation server is not consistent.

It is a system configuration figure of a community medicine cooperation system in one embodiment of the present invention. It is a data block diagram of medical image data. It is a data block diagram of observation report data. It is a block diagram of a regional medical cooperation server. It is a data block diagram of a registry. It is a block diagram of an image server. It is a block diagram of a report management server. It is a block diagram of an electronic medical record server. It is a data block diagram of a user information database. It is a block diagram of a registration terminal. It is a ladder chart which shows the process performed in a regional medical cooperation system, when registering the location of medical data. It is a screen example of a selection registration screen. It is a screen example of a selection registration screen. It is a screen example of a selection registration screen. It is a ladder chart which shows the process performed in a regional medical cooperation system, when acquiring medical data.

Hereinafter, an embodiment of a regional medical cooperation system according to the present invention will be described with reference to the drawings.

[System configuration of regional medical cooperation system]
FIG. 1 shows a system configuration of the regional medical cooperation system 1. As shown in FIG. 1, the regional medical cooperation system 1 manages medical facilities 100, 200, 300, and 400 such as university hospitals, cancer centers, and clinics in a certain region and the location of medical data in each medical facility. Each medical facility and apparatus are connected to each other via a communication network N so that data communication is possible.

The medical facility 100 includes a registration terminal 10, an image server 20, an RIS (Radiological Information System) 30, a clinician PC terminal 40, a report management server 50, an image viewer terminal 60, and a modality 70. The electronic medical record server 80 is connected to each device via a LAN (Local Area Network) which is a communication network in the facility so that data communication is possible. The LAN can communicate with the communication network N via a communication device such as a router (not shown).

RIS 30 performs information management such as medical appointment reservation, diagnosis result report, results management, material inventory management, etc. in the radiology department of the medical facility 100. The RIS 30 transmits the imaging order information received from the electronic medical record server 80 to the modality 70, the image server 20, and the registration terminal 10.

The modality 70 is an imaging device that images a patient according to the imaging order information received from the RIS 30 and generates image data of a medical image. Further, the modality 70 generates incidental information related to the image data based on the photographing order information. The modality 70 generates medical image data by attaching the accompanying information to the image data (hereinafter referred to as image actual data). That is, the medical image data is composed of actual image data and incidental information related to the actual image data. The medical image data is data conforming to the DICOM standard, for example.

Then, the modality 70 transmits the generated medical image data to the image server 20. As the modality 70, an imaging apparatus that captures various types of medical images such as a CR apparatus, a CT apparatus, and an MRI apparatus can be applied.

FIG. 2 shows a data structure of medical image data generated by the modality 70. As described above, medical image data is composed of incidental information and actual image data. The incidental information includes patient information, examination information, series information, and image information.

Patient information is information about the patient such as patient ID, patient name, date of birth, and sex. The examination information is information relating to the examination such as the examination instance UID that identifies the examination, the examination date, the examination time, the reception number, and the doctor in charge. The series information is information regarding a series (unit) of a series of medical images for each modality generated in one examination, such as a series instance UID that identifies the series, a modality name, an examination part, and a series number. The image information is information related to a medical image such as an SOP instance UID that identifies an image and an image number.

Also, one or more tests are linked (related) to one patient. Therefore, there is a one-to-one relationship or a one-to-multiple relationship between patient information and examination information. In addition, one or a plurality of series is associated with (related to) one inspection. Therefore, there is a one-to-one relationship or a one-to-multiple relationship between the inspection information and the series information. In addition, one or more medical images are associated with (related to) one series. Therefore, there is a one-to-one relationship or a one-to-multiple relationship between the series information and the image information. Hereinafter, medical image data corresponding to one medical image is referred to as a medical image data object.

Returning to FIG. 1, the image server 20 stores and manages (stores and manages) medical image data and the like generated in the modality 70. When the image server 20 receives a medical image data acquisition request from an external device, the image server 20 transmits medical image data corresponding to the acquisition request to the external device. When the image server 20 receives a supplementary information acquisition request from an external device, the image server 20 transmits the supplementary information included in the medical image data corresponding to the acquisition request to the external device.

The image viewer terminal 60 has a monitor (viewer) that displays medical images, and is a terminal such as a PC (Personal Computer) that is installed mainly for the purpose of creating interpretation report data of medical images by an interpretation doctor. . The image viewer terminal 60 transmits a medical image data acquisition request to the image server 20 based on a user operation by the interpretation doctor, and acquires medical image data corresponding to the acquisition request. Then, a medical image is displayed on the monitor based on the medical image data. Then, the image viewer terminal 60 creates actual data of the finding report (hereinafter referred to as finding report actual data) based on the user operation by the image interpretation doctor. Further, the image viewer terminal 60 generates supplementary information related to the finding report actual data based on the supplementary information included in the medical image data acquired from the image server 20. Then, the image viewer terminal 60 appends the incidental information to the finding report actual data to generate finding report data. That is, the finding report data includes report actual data and incidental information related to the report actual data. The finding report data is data conforming to, for example, the HL7 LDA (Laboratory Device Automation) standard.

Then, the image viewer terminal 60 transmits the generated finding report data to the report management server 50.

FIG. 3 shows the data structure of the finding report data generated by the image viewer terminal 60. As described above, the finding report data is composed of incidental information and actual report data. The incidental information includes patient information, examination information, and the like. Hereinafter, the finding report data corresponding to one examination is referred to as a finding report data object. That is, the actual report data of the finding report data object is the finding report information for an image group of one examination.

Referring back to FIG. 1, the report management server 50 stores and manages (stores and manages) the finding report data generated in the image viewer terminal 60. Upon receiving the finding report data from the image viewer terminal 60, the report management server 50 stores the finding report data.

The clinician PC terminal 40 is a terminal such as a PC that is installed mainly for the purpose of creating medical record data by a clinician. The clinician PC terminal 40 creates medical record data based on a user operation by the clinician. Then, the clinician PC terminal 40 transmits the generated medical record data to the electronic medical record server 80. Further, the clinician PC terminal 40 transmits an instruction signal for generating imaging order information to the electronic medical record server 80 based on a user operation by the clinician.

The electronic medical record server 80 stores and manages (stores and manages) medical record data created in the clinician PC terminal 40. When receiving the medical record data from the clinician PC terminal 40, the electronic medical record server 80 stores the medical record data. Hereinafter, medical record data corresponding to one examination is referred to as a medical record data object.

The electronic medical record server 80 stores a user information database 851. The user information database 851 will be described later. The electronic medical record server 80 generates imaging order information based on the instruction signal from the clinician PC terminal 40, and transmits the generated imaging order information to the RIS 30.

The registration terminal 10 is a terminal that registers the location of medical data in the medical facility 100 in the regional medical cooperation server 90. Here, medical data refers to information such as medical image data, finding report data, medical record data, and physical measurement data.

The registration terminal 10 generates link information indicating the location of medical data in the medical facility 100 (medical data stored in a storage medium provided in the medical facility 100), and uses the link information as the regional medical cooperation server 90. Send to. In addition, the registration terminal 10 generates and displays a list of examinations performed in the medical facility 100 based on the imaging order information received from the RIS 30.

The medical facilities 200, 300, and 400 include some or all of the devices in the device group constituting the medical facility 100. For example, the medical facility 400 includes a clinical doctor PC terminal 410, an electronic medical record server 420, an image viewer terminal 430, and the like, and each device is connected to be able to perform data communication via a LAN that is a communication network in the medical facility 400. ing.

[Functional configuration of regional medical cooperation server]
FIG. 4 shows a functional configuration of the regional medical cooperation server 90. As shown in FIG. 4, the regional medical cooperation server 90 includes a control unit 91, an operation unit 92, a communication unit 93, a display unit 94, and a storage unit 95, and each unit is connected by a bus 96.

The control unit 91 includes a CPU (Central Processing Unit), a RAM (Random Access Memory), and the like, and comprehensively controls processing operations of each unit of the regional medical cooperation server 90. Specifically, the CPU reads various processing programs stored in the storage unit 95 according to an operation signal input from the operation unit 92 or an instruction signal received by the communication unit 93, and is formed in the RAM. The work area is expanded and various processes are performed in cooperation with the program.

The operation unit 92 includes a keyboard having cursor keys, numeric input keys, various function keys, and the like, and a pointing device such as a mouse. The operation unit 92 controls operation signals input by key operations or mouse operations on the keyboard. To 91.

The communication unit 93 includes a LAN adapter, a router, a TA (Terminal Adapter), and the like, and exchanges data with external systems and external devices such as medical facilities 100, 200, 300, and 400 connected via the communication network N. Send and receive.

The display unit 94 is configured by an LCD (Liquid Crystal Display), and displays various screens based on display data input from the control unit 91.

The storage unit 95 is composed of a hard disk or the like, and stores a control program, parameters and files necessary for executing the program. The storage unit 95 stores a registry 951 that is a database indicating the location of medical data in each medical facility.

Fig. 5 shows the data structure of the registry 951. As shown in FIG. 5, one record in the registry 951 includes “publisher information”, “save destination information”, “medical data type information”, “patient information”, “examination information”, and “medical data identification information”. Consists of. Here, one record indicates the location of one medical data object (medical image data object, finding report data object, medical record data object, etc.). Hereinafter, the record of the registry 951 is referred to as link information. Further, link information corresponding to one record of the registry 951 is referred to as a link information object. That is, the registry 951 is a set of link information objects.

“Publisher information” is information of a user who registers the location of an object of medical data in the registry 951. The “publisher information” includes items “publisher name”, “publisher role”, “publisher contact information”, “publisher specialty”, and the like. The “publisher role” is an item indicating a role such as an interpreting doctor or a diagnostician. “Publisher specialty” is an item indicating a specialized field such as internal medicine or surgery.

“Storage destination information” is information relating to a medical facility and apparatus provided with a storage medium storing medical data objects. The “storage destination information” includes items “medical facility name”, “medical facility ID”, “device name”, “device ID”, and the like. The “medical facility ID” is a unique ID assigned to each medical facility. The “device ID” is a unique ID assigned to each device in each medical facility.

“Medical data type information” is information indicating the type of medical data. “Medical data type information” includes an item “medical data type” and the like. The “medical data type” takes values such as medical image data, finding report data, medical record data, and the like.

“Patient information” is information about a patient who is the target of medical data. The “patient information” includes items “patient ID”, “patient name”, “birth date”, “sex”, and the like.

“Examination information” is information relating to an examination in which an object of medical data is generated. The “examination information” includes items “examination instance UID”, “examination date”, “examination time”, “reception number”, “doctor in charge”, and the like.

“Medical data identification information” is information for identifying an object of medical data. “Medical data identification information” includes items “unique ID”, “title”, and the like. The “unique ID” is a unique ID for each medical data object. For example, when the type of medical data is medical image data, “unique ID” is the value of the SOP instance UID. A medical data object is specified by the unique ID.

Note that the data structure of the registry 951 is not limited to the above example, and can be changed as appropriate.

Returning to FIG. 4, when receiving the link information from the registration terminal 10, the control unit 91 registers the link information in the registry 951. Specifically, when the control unit 91 receives one or more link information objects from the registration terminal 10, the control unit 91 adds the link information object as a record of the registry 951. In addition, the control unit 91 includes the value of “unique ID” included in “medical data identification information” of the received link information object in “medical data identification information” of the link information object already registered in the registry 951. If it is equal to the “unique ID” value, the received link information object is overwritten (updated) on the record of the link information object already registered in the registry 951.

Further, when receiving a link information acquisition request from an external device via the communication unit 93, the control unit 91 reads a link information object corresponding to the link information acquisition request from the registry 951. Then, the control unit 91 transmits the read link information object to the external device that is the transmission source of the link information acquisition request via the communication unit 93.

[Functional configuration of image server]
FIG. 6 shows a functional configuration of the image server 20. As shown in FIG. 6, the image server 20 includes a control unit 21, an operation unit 22, a communication unit 23, a display unit 24, and a storage unit 25, and each unit is connected by a bus 26.

The control unit 21 includes a CPU (Central Processing Unit), a RAM (Random Access Memory), and the like, and comprehensively controls the processing operation of each unit of the image server 20. Specifically, the CPU reads various processing programs stored in the storage unit 25 according to an operation signal input from the operation unit 22 or an instruction signal received by the communication unit 23, and is formed in the RAM. The work area is expanded and various processes are performed in cooperation with the program.

The operation unit 22 includes a keyboard having cursor keys, numeric input keys, various function keys, and the like, and a pointing device such as a mouse. The control unit 22 controls operation signals input by key operations or mouse operations on the keyboard. To 21.

The communication unit 23 includes a LAN (Local Area Network) adapter, a router, a TA (Terminal Area Adapter), etc., and the registration terminal 10, the RIS 30, the image viewer terminal 60, the modality 70 connected via the LAN of the medical facility 100. Data is transmitted / received to / from an external device such as the image viewer terminal 430 of the medical facility 400 connected via the communication network N.

The display unit 24 is configured by an LCD (Liquid Crystal Display), and displays various screens based on display data input from the control unit 21.

The storage unit 25 is composed of a hard disk or the like, and stores a control program, parameters and files necessary for executing the program. Further, the storage unit 25 stores medical image data (one or a plurality of medical image data objects) generated by the modality 70.

When receiving the medical image data object group from the modality via the communication unit 23, the control unit 21 stores the medical image data object group in the storage unit 25.

In addition, when receiving a medical image data acquisition request from an external device via the communication unit 23, the control unit 21 reads a medical image data object corresponding to the medical image data acquisition request from the storage unit 25. Then, the control unit 21 transmits the read medical image data object to the external device that is the transmission source of the medical image data acquisition request via the communication unit 23.

Further, when receiving the supplementary information acquisition request from the external device via the communication unit 23, the control unit 21 reads the supplementary information included in the medical image data object corresponding to the supplementary information acquisition request from the storage unit 25. Then, the control unit 21 transmits the read incidental information to the external device that is the transmission source of the incidental information acquisition request via the communication unit 23.

[Functional configuration of the report management server]
FIG. 7 shows a functional configuration of the report management server 50. As shown in FIG. 7, the report management server 50 includes a control unit 51, an operation unit 52, a communication unit 53, a display unit 54, and a storage unit 55, and each unit is connected by a bus 56.

The control unit 51 is composed of a CPU (Central Processing Unit), a RAM (Random Access Memory), and the like, and comprehensively controls the processing operation of each unit of the report management server 50. Specifically, the CPU reads various processing programs stored in the storage unit 55 in accordance with an operation signal input from the operation unit 52 or an instruction signal received by the communication unit 53, and is formed in the RAM. The work area is expanded and various processes are performed in cooperation with the program.

The operation unit 52 includes a keyboard having cursor keys, numeric input keys, various function keys, and the like, and a pointing device such as a mouse, and controls operation signals input by keyboard operations or mouse operations. To 51.

The communication unit 53 includes a LAN (Local Area Network) adapter, a router, a TA (Terminal Area Adapter), and the like, and is connected via the registration terminal 10, the image viewer terminal 60, and the communication network N connected via the LAN of the medical facility 100. Data is transmitted to and received from an external device such as the image viewer terminal 430 of the medical facility 400 that is connected.

The display unit 54 is configured by an LCD (Liquid Crystal Display), and displays various screens based on display data input from the control unit 51.

The storage unit 55 includes a hard disk or the like, and stores a control program, parameters and files necessary for executing the program. Further, the storage unit 55 stores the finding report data (one or a plurality of finding report data objects) generated by the image viewer terminal 60.

When receiving the finding report object from the image viewer terminal 60 via the communication unit 53, the control unit 51 stores the finding report object in the storage unit 55.

Further, when receiving the finding report data acquisition request from the external device via the communication unit 53, the control unit 51 reads out the finding report data object corresponding to the finding report data acquisition request from the storage unit 55. Then, the control unit 51 transmits the read finding report data object to the external device that is the transmission source of the finding report data acquisition request via the communication unit 53.

[Functional configuration of electronic medical record server]
FIG. 8 shows a functional configuration of the electronic medical record server 80. As shown in FIG. 8, the electronic medical record server 80 includes a control unit 81, an operation unit 82, a communication unit 83, a display unit 84, and a storage unit 85, and each unit is connected by a bus 86.

The control unit 81 is configured by a CPU (Central Processing Unit), a RAM (Random Access Memory), and the like, and comprehensively controls processing operations of each unit of the electronic medical record server 80. Specifically, the CPU reads various processing programs stored in the storage unit 85 in accordance with an operation signal input from the operation unit 82 or an instruction signal received by the communication unit 83, and is formed in the RAM. The work area is expanded and various processes are performed in cooperation with the program.

The operation unit 82 includes a keyboard having cursor keys, numeric input keys, various function keys, and the like, and a pointing device such as a mouse. The control unit 82 controls operation signals input by keyboard operations or mouse operations. 81.

The communication unit 83 includes a LAN (Local Area Network) adapter, a router, a TA (Terminal Adapter), and the like, and is connected to external devices such as the registration terminal 10 and the clinical doctor PC terminal 40 connected via the LAN of the medical facility 100. Send and receive data between them.

The display unit 84 is configured by an LCD (Liquid Crystal Display), and displays various screens based on display data input from the control unit 81.

The storage unit 85 includes a hard disk or the like, and stores a control program, parameters and files necessary for executing the program, and the like. In addition, the storage unit 85 stores medical record data created by the clinician PC terminal 40. The storage unit 85 stores a user information database 851.

FIG. 9 shows the data structure of the user information database 851. As shown in FIG. 9, one record in the user information database 851 includes “personal information”, “role information”, “contact information”, and “affiliation information”. Here, one record indicates information related to one user of each device (for example, the electronic medical record server 80) of the medical facility 100.

“Personal information” includes items “user name”, “user ID”, and the like. The “role information” includes an item “user role” and the like. The “user role” is an item indicating a role such as an interpreting doctor or a diagnostician. “Contact information” includes the item “contact information of user” and the like. “Affiliation information” includes an item “user specialty” and the like. “User specialty” is an item indicating a specialized field such as internal medicine or surgery.

Returning to FIG. 8, when receiving a user information acquisition request from an external device via the communication unit 83, the control unit 81 reads a record corresponding to the user information acquisition request from the user information database 851. Then, the control unit 51 transmits the read record (hereinafter referred to as a user information record) to the external device that is the transmission source of the user information acquisition request via the communication unit 53.

[Functional configuration of registered terminal]
FIG. 10 shows a functional configuration of the registration terminal 10. As shown in FIG. 10, the registration terminal 10 includes a control unit 11, an operation unit 12, a communication unit 13, a display unit 14, and a storage unit 15, and each unit is connected by a bus 16.

The control unit 11 includes a CPU (Central Processing Unit), a RAM (Random Access Memory), and the like, and comprehensively controls the processing operation of each unit of the registration terminal 10. Specifically, the CPU reads various processing programs stored in the storage unit 15 according to an operation signal input from the operation unit 12 or an instruction signal received by the communication unit 13, and is formed in the RAM. The work area is expanded and various processes are performed in cooperation with the program.

The operation unit 12 includes a keyboard having cursor keys, numeric input keys, various function keys, and the like, and a pointing device such as a mouse, and controls operation signals input by keyboard operations or mouse operations. 11 is output.

The communication unit 13 includes a LAN (Local Area Network) adapter, a router, a TA (Terminal Area Adapter), and the like, and is connected to the image server 20, the report management server 50, and the electronic medical chart connected via the LAN or the communication network N of the medical facility 100. Data is transmitted / received to / from external devices such as the server 80 and the regional medical cooperation server 90.

The display unit 14 is configured by an LCD (Liquid Crystal Display), and displays various screens based on display data input from the control unit 11.

The storage unit 15 is composed of a hard disk or the like, and stores a control program, parameters and files necessary for executing the program.

The control unit 11 transmits a user information acquisition request to the electronic medical record server 80 via the communication unit 13. Then, the control unit 11 acquires a user information record corresponding to the acquisition request from the electronic medical record server 80 via the communication unit 13.

Further, the control unit 11 transmits a supplementary information acquisition request to the image server 20 via the communication unit 13. Then, the control unit 11 acquires incidental information included in the medical image data object from the image server 20 via the communication unit 13 in response to the acquisition request.

Further, the control unit 11 transmits a finding report data acquisition request to the report management server 50 via the communication unit 13. Then, the control unit 11 acquires the finding report data object corresponding to the acquisition request from the report management server 50 via the communication unit 13.

Further, the control unit 11 generates link information (one or a plurality of link information objects) based on each information acquired from each of these devices. Then, the control unit 11 transmits the generated link information (one or a plurality of link information objects) to the regional medical cooperation server 90 via the communication unit 13.

[Processes executed in the regional medical cooperation system when registering the location of medical data]
Next, specific operations of each device executed in the regional medical cooperation system 1 when registering the location of medical data in the regional medical cooperation server 90 will be described with reference to FIG. In this process, an interpreting doctor working at the medical facility 100 registers the location of the medical image data and the finding report data generated in a certain examination performed at the medical facility 100 in the regional medical cooperation server 90. A scene is assumed.

First, a certain examination and diagnosis are performed in the medical facility 100. Specifically, in the modality 70, a patient is imaged, and medical image data is generated by the imaging. The generated medical image data is stored in the image server 20. Further, the image viewer terminal 60 interprets the medical image data by an interpreting doctor, and generates finding report data. The generated finding report data is stored in the report management server 50.

That is, medical data such as medical image data and finding report data is generated in one examination. The medical image data is stored in the image server 20, and the finding report data is stored in the report management server 50.

At the registration terminal 10, an interpreting doctor or the like performs user operations such as login. Then, the registration terminal 10 performs a login process based on the user operation (step S1). When the registration terminal 10 performs the login process, the registration terminal 10 displays a list of patients on the display unit 14 (not shown). Then, in the registration terminal 10, the interpretation doctor selects a patient who is a subject of the examination to be registered. Then, the registration terminal 10 displays a screen (selection registration screen 141 (see FIGS. 12A, 12B, and 12C)) for selecting and registering the examination related to the selected patient on the display unit 14 based on the user operation. To do. The registration terminal 10 displays a list of patients and a selection / registration screen 141 based on imaging order information transmitted from the RIS 30, medical record data acquired from the electronic medical record server 80, and the like.

FIG. 12A, FIG. 12B, and FIG. 12C show screen examples of the selection registration screen 141. As shown in FIG. 12A, the selection registration screen 141 includes a patient information display area e1, an examination history display area e2, a registration button b1, and the like. In the patient information display area e1, patient information of a patient selected by a user such as an interpretation doctor is displayed. In the examination history display area e2, a list of examinations performed on the patient displayed in the patient information display area e1 is displayed. The user selects an examination to be registered in the registry 951 of the regional medical cooperation server 90 from the examination list. Then, the user registers the location of the selected examination in the registry 951 of the regional medical cooperation server 90 by pressing the registration button b1.

Returning to FIG. 11, when the examination is selected on the selection registration screen 141 and the registration button b1 is pressed (step S2), the registration terminal 10 transmits a user information acquisition request to the electronic medical record server 80 (step S3). ). The user information acquisition request is an acquisition request for information of a user (user) who has logged in to the registration terminal 10. The user information acquisition request includes the user ID of the user (user) to be acquired, and the acquired information is specified by the user ID.

When receiving the user information acquisition request from the registration terminal 10, the electronic medical record server 80 reads a user information record having the same value as the user ID included in the user information acquisition request from the user information database 851. . And the electronic medical record server 80 transmits the said user information record (information of the user who has logged into the registration terminal 10) to the registration terminal 10 (step S4).

Next, the registration terminal 10 transmits a supplementary information acquisition request to the image server 20 (step S5). The supplementary information acquisition request is a request for acquiring supplementary information of the medical image data object corresponding to the examination selected in step S2. The incidental information acquisition request includes “patient name”, “examination date”, and the like, and the acquired information is specified based on these information.

Upon receiving the supplementary information acquisition request from the registration terminal 10, the image server 20 identifies a medical image data object having the same value as “patient name”, “examination date”, etc. included in the supplementary information acquisition request, and The incidental information included in the specified medical image data object is read from the storage unit 25. Then, the image server 20 transmits the incidental information of the medical image data object to the registration terminal 10 (step S6).

Next, the registration terminal 10 transmits a finding report data acquisition request to the report management server 50 (step S7). The finding report data acquisition request is a finding report data object acquisition request corresponding to the examination selected in step S2. The finding report data acquisition request includes “patient name”, “examination date”, and the like, and the acquired information is specified based on these information.

Upon receiving the finding report data acquisition request from the registration terminal 10, the report management server 50 identifies an finding report data object having the same value as “patient name”, “examination date”, etc. included in the finding report data acquisition request. And read from the storage unit 55. Then, the report management server 50 transmits the read finding report data object to the registration terminal 10 (step S8).

Next, the registration terminal 10 receives the user information record received from the electronic medical record server 80, the incidental information of the medical image data object received from the image server 20, the observation report data object received from the report management server 50, and the RIS 30. The consistency between the imaging order information transmitted from the medical record data acquired from the electronic medical record server 80 is checked (step S9). For example, the “patient name” of the patient to be examined selected on the selection registration screen 141 matches the “patient name” of the patient information included in the incidental information of the medical image data object received from the image server 20. Check for consistency.

As a result of the consistency check in step S9, if there is no data consistency, the registration terminal 10 displays a character string “patient inconsistency” on the selection registration screen 141 (see FIG. 12C). Then, link information is not generated, and the process is terminated (the processes in steps S10 to S12 are not performed).

As a result of the consistency check in step S9, if there is data consistency, the registration terminal 10 receives the user information record received from the electronic medical record server 80, the incidental information of the medical image data object received from the image server 20, Based on the finding report data object received from the report management server 50, link information as a result of the examination selected in step S2 is generated (step S10).

Specifically, the registration terminal 10 generates link information objects related to the medical image data object by the number of incidental information of the medical image data object received from the image server 20. Further, the registration terminal 10 generates link information objects related to the finding report data objects by the number of finding report data objects received from the report management server 50. For example, in a case where 1000 medical images are created in one examination, and a finding report for these medical images is created, the registration terminal 10 creates 1000 link information objects related to the medical image data object and link information objects related to the finding report data object. One is generated.

First, a process in which the registration terminal 10 generates a link information object related to a medical image data object will be described. The registration terminal 10 executes this process the number of times of the incidental information of the medical image data object received from the image server 20.

The registration terminal 10 generates “publisher information” of the link information object based on the user information record received from the electronic medical record server 80. The registration terminal 10 manages the “medical facility name” and “medical facility ID” of the medical facility 100 and the “device name” and “device ID” of each device in the medical facility 100 managed by the registration terminal 10. Based on the above, “save destination information” of the link information object is generated. Specifically, each item of “storage destination information” is a value corresponding to the image server 20 of the medical facility 100. Also, the registration terminal 10 generates “medical data type information” of the link information object with the value of the item “medical data type” as “medical image data”. Also, the registration terminal 10 generates “patient information”, “examination information”, and “medical data identification information” of the link information object based on the supplementary information of the medical image data object received from the image server 20.

Next, a process in which the registration terminal 10 generates a link information object related to the finding report data object will be described. The registration terminal 10 executes this process for the number of finding report objects received from the report management server 50.

The registration terminal 10 generates “publisher information” of the link information object based on the user information record received from the electronic medical record server 80. The registration terminal 10 manages the “medical facility name” and “medical facility ID” of the medical facility 100 and the “device name” and “device ID” of each device in the medical facility 100 managed by the registration terminal 10. Based on the above, “save destination information” of the link information object is generated. Specifically, each item of “storage destination information” is a value corresponding to the report management server 50 of the medical facility 100. Also, the registration terminal 10 generates “medical data type information” of the link information object with the value of the item “medical data type” as “finding report data”. Further, the registration terminal 10 reads the incidental information from the finding report data object received from the report management server 50. Then, the registration terminal 10 generates “patient information”, “examination information”, and “medical data identification information” of the link information object based on the incidental information. The above is a specific description of the process of generating link information in step S10.

When the link information is generated in step S10, the registration terminal 10 transmits the generated link information (one or a plurality of link information objects) to the regional medical cooperation server 90 (step S11).

Upon receiving the link information (one or a plurality of link information objects) from the registration terminal 10, the regional medical cooperation server 90 registers the link information (one or a plurality of link information objects) in the registry 951 (step S12).

Then, the regional medical cooperation server 90 transmits a notification of registration to the registration terminal 10. Upon receiving the notification, the registration terminal 10 displays a character string “registration completed” on the selection registration screen 141 (see FIG. 12B). The process ends here.

[Processes executed in the regional medical cooperation system when obtaining medical data]
Next, when the image viewer terminal 430 of the medical facility 400 acquires medical data managed in another medical facility, the specific operation of each device executed in the regional medical cooperation system 1 will be described with reference to FIG. I will explain. In this process, it is assumed that a doctor working at the medical facility 400 refers to medical image data and finding report data generated in a certain examination performed at the medical facility 100.

First, in the image viewer terminal 430 of the medical facility 400, a doctor or the like performs a user operation to input “patient ID”, “patient name”, “examination date”, and the like of a patient who is a target of medical data to be referred to. Do. Then, the image viewer terminal 430 transmits a link information acquisition request to the regional medical cooperation server 90 based on the user operation (step S101). Here, the link information acquisition request includes “patient ID”, “patient name”, “examination date”, etc., and the acquisition information is specified based on these information.

When receiving the link information acquisition request from the image viewer terminal 430 of the medical facility 400, the regional medical cooperation server 90 has the same value as “patient ID”, “patient name”, “examination date”, etc. included in the link information acquisition request. The link information object including the patient information and the examination information having is identified from the registry 951 and read out. Then, the regional medical cooperation server 90 transmits the read link information object to the image viewer terminal 430 (step S102). Specifically, the examination corresponding to “patient ID”, “patient name”, and “examination date” is one examination, and 1000 medical images and one finding report for these medical images are created in the examination. If so, the regional medical cooperation server 90 transmits 1000 link information objects corresponding to 1000 medical images and 1 link information object corresponding to 1 finding report to the image viewer terminal 430.

Next, the image viewer terminal 430 generates a medical image data acquisition request based on the one or more link information objects received from the regional medical cooperation server 90, and transmits the medical image data acquisition request to the image server 20 of the medical facility 100 (step S103). ).

Specifically, the image viewer terminal 430 refers to the value of the item “medical data type” of the medical data type information included in the one or more link information objects received from the regional medical cooperation server 90, and this value is “medical use”. The link information object which is “image data” is extracted. Then, the image viewer terminal 430 generates a medical image data acquisition request based on “medical data identification information” included in the extracted link information object. In this case, medical image data acquisition requests are generated for the number of extracted link information objects. Then, the image viewer terminal 430 refers to the value of the storage destination information included in the extracted link information object, and determines the transmission destination of the medical image data acquisition request based on the values of “medical facility ID” and “device ID”. To do. Then, the image viewer terminal 430 transmits the generated medical image data acquisition request to the image server 20.

Upon receiving the medical image data acquisition request from the image viewer terminal 430, the image server 20 transmits the corresponding medical image data object to the image viewer terminal 430 (step S104).

Next, the image viewer terminal 430 generates a medical image data acquisition request based on the one or more link information objects received from the regional medical cooperation server 90, and transmits the medical image data acquisition request to the report management server 50 of the medical facility 100 (step). S105).

Specifically, the image viewer terminal 430 refers to the value of the item “medical data type” of the medical data type information included in the one or more link information objects received from the regional medical cooperation server 90, and this value is “ The link information object which is “report data” is extracted. Then, the image viewer terminal 430 generates a finding report data acquisition request based on “patient information”, “examination information”, and “medical data identification information” included in the extracted link information object. In this case, the finding report data acquisition request is generated by the number of extracted link information objects. Then, the image viewer terminal 430 refers to the value of the storage destination information included in the extracted link information object, and determines the transmission destination of the finding report data acquisition request based on the values of “medical facility ID” and “device ID”. To do. Then, the image viewer terminal 430 transmits the generated finding report data acquisition request to the report management server 50.

Upon receiving the finding report data acquisition request from the image viewer terminal 430, the report management server 50 transmits the corresponding finding report data object to the image viewer terminal 430 (step S106).

The image viewer terminal 430 displays the examination result (medical image, finding report, etc.) on the screen based on the medical image data object group received from the image server 20 and the finding report data object received from the report management server 50. (Step S107).

As described above, according to the present embodiment, the registration terminal 10 installed in the medical facility 100 displays various information related to the examination (examination data) designated on the selection registration screen 141, the image server 20, the report management server 50, Collect (acquire) from the electronic medical record server 80. Then, the registration terminal 10 generates link information based on the collected various information (accompanying information of medical image data, finding report data, user information record). Then, the registration terminal 10 transmits the generated link information to the regional medical cooperation server 90. Then, the regional medical cooperation server 90 registers the received link information in the registry 951.

Therefore, the user does not need to input information (patient information, examination information), etc. regarding medical data to be registered in the registry 951 on the registration terminal 10 one by one. The work load registered in the registry 951) can be reduced. Furthermore, since the information regarding the medical data to be transmitted to the regional medical cooperation server 90 is automatically generated, registration omission and registration error due to user input can be prevented.

In addition, the registration terminal 10 collects (acquires) various types of information related to the examination (examination data) specified on the selection registration screen 141 from the image server 20, the report management server 50, and the electronic medical record server 80, and the various information. Is checked (determined), and if there is no consistency, a character string to that effect is displayed on the selection registration screen 141 (see FIG. 12C).

Therefore, the user can know that the link information registered in the regional medical cooperation server 90 is not consistent before registration.

The description in the present embodiment is an example of the medical image system according to the present invention, and the present invention is not limited to this. The detailed configuration and detailed operation of each device constituting the system can be appropriately changed.

For example, the electronic medical record server 80 may have the function of the registration terminal 10.

In this embodiment, an example in which a hard disk is used as a computer-readable medium storing a program is disclosed, but the present invention is not limited to this example. As other computer-readable media, a non-volatile memory such as a flash memory and a portable storage medium such as a CD-ROM can be applied. Also, a carrier wave can be applied as a medium for providing program data via a communication line.

A local medical cooperation server that can be used in the medical field and manages the location of medical data in each medical facility, and a registration terminal installed in the medical facility are connected so that data communication is possible via a communication network It can be applied to a regional medical cooperation system.

Explanation of symbols

1 regional medical cooperation system 10 registration terminal 11 control unit 12 operation unit 13 communication unit 14 display unit 15 storage unit 16 bus 20 image server 21 control unit 22 operation unit 23 communication unit 24 display unit 25 storage unit 26 bus 30 RIS
40 Clinician PC terminal 50 Report management server 51 Control unit 52 Operation unit 53 Communication unit 54 Display unit 55 Storage unit 56 Bus 60 Image viewer terminal 70 Modality 80 Electronic medical record server 81 Control unit 82 Operation unit 83 Communication unit 84 Display unit 85 Storage Unit 86 Bus 90 Regional medical cooperation server 91 Control unit 92 Operation unit 93 Communication unit 94 Display unit 95 Storage unit 96 Bus 100 Medical facility 141 Selection registration screen 200 Medical facility 300 Medical facility 400 Medical facility 410 Clinical medical PC terminal 420 Electronic medical record server 430 Image viewer terminal 851 User information database 951 Registry b1 Registration button e1 Patient information display area e2 Examination history display area N Communication network

Claims (4)

A regional medical cooperation system in which a medical data liaison server that manages the location of medical data in each medical facility and a registration terminal installed in the medical facility are connected to enable data communication via a communication network,
The regional medical cooperation server
A communication means for transmitting / receiving various data to / from an external device;
Storage means for storing a registry for managing the location of medical data in each medical facility;
Control means for registering the location of the medical data and the various information about the medical data in the registry when the communication unit receives the location of the medical data and the various information about the medical data from the registration terminal;
With
The registered terminal
A communication means for transmitting / receiving various data to / from an external device;
A designation means for designating medical data of a self-care facility to be registered in the registry;
Information relating to medical data designated by the designation means via the communication means for each device installed in the own medical facility that has storage means for storing information relating to the medical data and manages information relating to the medical data To obtain various information related to the designated medical data from each device, and together with the location of the designated medical data, send the various information related to the designated medical data via the communication means. Control means for transmitting to the regional medical cooperation server;
Regional medical cooperation system with The control means of the registration terminal includes:
The consistency of various information related to the specified medical data acquired from each device is determined, and if there is no consistency, the fact is displayed on the display screen.
The regional medical cooperation system according to claim 1. A registration terminal installed in a medical facility,
A communication means for transmitting / receiving various data to / from an external device;
A designation means for designating medical data of a self-care facility to be registered in a registry for managing the location of medical data in each medical facility;
Information relating to medical data designated by the designation means via the communication means for each device installed in the own medical facility that has storage means for storing information relating to the medical data and manages information relating to the medical data To obtain various information related to the designated medical data from each device, and together with the location of the designated medical data, send the various information related to the designated medical data via the communication means. Control means for transmitting to a regional medical cooperation server having storage means for storing the registry;
A registration terminal comprising: Computers installed in medical facilities
Communication means for sending and receiving various data with external devices,
A designation means for designating medical data of the own medical facility, which is to be registered in the registry for managing the location of the medical data in each medical facility;
Information relating to medical data designated by the designation means via the communication means for each device installed in the own medical facility that has storage means for storing information relating to the medical data and manages information relating to the medical data To obtain various information related to the designated medical data from each device, and together with the location of the designated medical data, send the various information related to the designated medical data via the communication means. Control means for transmitting to a regional medical cooperation server having storage means for storing the registry;
Program to function as.

Images