JP2015111383A - Medical data management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a medical data management system capable of satisfactorily ensuring overview of entire medical treatment process.SOLUTION: Receiving a request for generating an overview data of a desired patient together with a piece of patient information for identifying the patient, the medical data management system acquires the medical data including the patient information from the target indicated by the stored data generation reference information. The medical data management system also generates an overview data relevant to the medical treatment process of the desired patient which can be presented to a user based on the acquired medical data, a piece of stored weighting coefficient information and a piece of stored data generation reference information. The medical data management system presents the generated overview data to the user.

Description

  Embodiments described herein relate generally to a medical data management apparatus.

  Usually, in general clinics (eg, clinics, clinics, etc.) and hospitals, doctors need to treat many patients a day.

  In making a medical examination, doctors need to refer to various data such as electronic medical records, medical image data obtained from past examinations, and letters of introduction from other hospitals.

  Currently, as an application that can support the above-described various information reference work, there is an application that displays specific information of a desired patient on a display device in time series, and develops details of the specific information as necessary.

JP 2007-233841 A

  However, in the above-mentioned application, in order to display one type of data, that is, an electronic medical record if the specific information is an electronic medical record, and medical image data in a time series if the specific information is medical image data, There is an inconvenience that it is not possible to sufficiently secure an overview of the entire medical course.

  The object is to provide a medical data management apparatus that can sufficiently ensure an overview of the entire clinical course.

  The medical data management apparatus according to the embodiment is an apparatus capable of managing medical data including at least patient information using a plurality of databases and generating overhead data using each medical data.

  The medical data management apparatus includes weight coefficient information storage means, data generation reference information storage means, data acquisition means, overhead data generation means, and presentation means.

  The weighting factor information storage unit stores weighting factor information defining a weighting factor indicating the importance of each medical data used when generating the overhead view data.

  The data generation reference information storage means displays at least one of the medical data acquisition destination, data type, and modality type, and displays each of the medical data in the overhead data set so as to correspond to the weighting factor. Data generation reference information defining a method (corresponding to the original expansion method) is stored.

  When the data acquisition means receives a bird's-eye view data generation request for generating bird's-eye view data of a desired patient together with patient information for specifying the patient, the data acquisition means stores the medical data including the patient information in the stored data Acquired from the acquisition destination indicated by the generation reference information.

  The bird's-eye view data generation means represents the bird's-eye view representing a medical course of the desired patient based on each of the acquired medical data, the stored weight coefficient information, and the stored data generation reference information. Based on each acquired medical data for generating data, the stored weighting factor information, and the stored data generation reference information, the medical course of the desired patient can be presented to the user The overhead view data is generated.

  The presenting means presents the generated overhead view data to the user.

It is a mimetic diagram showing an example of schematic composition of a medical data management system concerning one embodiment. It is a schematic diagram which shows an example of the data structure of the information memorize | stored in the information management memory | storage part which concerns on the embodiment. It is a schematic diagram which shows an example of the data structure of the information memorize | stored in the data generation reference | standard storage part which concerns on the embodiment. It is a schematic diagram which shows an example of the data structure of the information memorize | stored in the medical practice weight management memory | storage part which concerns on the embodiment. It is a schematic diagram which shows an example of the data structure of the information acquired from the other system which concerns on the embodiment. It is a sequence diagram which shows an example of operation | movement of the medical data management apparatus which concerns on the same embodiment. It is a schematic diagram for demonstrating the weighting process which concerns on the same embodiment. It is a schematic diagram which shows an example of the bird's-eye view data which concern on the embodiment. It is a schematic diagram which shows an example of the information used when embedding a hyperlink in the bird's-eye view data which concerns on the embodiment.

  Hereinafter, an embodiment will be described with reference to the drawings.

  FIG. 1 is a schematic diagram illustrating a schematic configuration example of a medical data management system according to an embodiment. FIGS. 2 to 4 are examples of data structures of various types of information stored in various storage units according to the embodiment. FIG. 5 is a schematic diagram illustrating an example of a data structure of information acquired from another system according to the embodiment. As shown in FIG. 1, the medical data management system includes a user interface 1, another system 2, and a medical data management device 3, and the user interface 1, other system 2, and medical data management device 3 are connected to a network (not shown) For example, they are connected to each other via a local area network (LAN).

  As shown in FIG. 1, the user interface 1 includes a registration unit 11 and an overhead data display unit 12.

  The registration unit 11 sends medical data including at least patient information to the medical data management device 3 in response to an operation of a user (for example, an operator of a user interface such as a doctor, a nurse, or a medical clerk). Is registered in the medical data management apparatus 3. As the above-mentioned medical data, for example, medical image data taken by a medical image diagnostic apparatus (not shown) (eg, X-ray CT (Computed Tomography) apparatus, MRI (Magnetic Resonance Imaging) apparatus, ultrasonic diagnostic apparatus, etc.), There are a diagnostic report (REPort) showing the result of diagnosis by a doctor, an electronic file of insurance card (document data (DOCument)) obtained by scanning an insurance card with a specific device, and the like. In addition to the above-described medical data, the registration unit 11 generates patient identification information (which is assumed to be patient identification information in this embodiment) that is generated with a patient visit and identifies the patient. It is sent to the management device 3.

  The overhead data display unit 12 assumes that the overhead data acquisition request for acquiring the overhead data (also referred to as summary data) generated by the medical data management device 3 is patient identification information (in this embodiment, patient identification information). In addition, the data is transmitted to the medical data management apparatus 3. Moreover, when the overhead data display unit 12 receives an input of overhead data transmitted from the medical data management device 3 in response to the overhead data acquisition request, the overhead data display unit 12 displays the overhead data that has received the input on a display device (display) (not shown). Let

  The other system 2 includes various systems such as an electronic medical record system, a regional cooperation system, and an external storage system. The electronic medical record system, the regional cooperation system, and the external storage system are examples of various systems included in the other system 2, and the other system 2 may include systems other than the above-described systems as appropriate.

  As shown in FIG. 1, the medical data management apparatus 3 includes an information management storage unit 31, a data generation reference storage unit 32, a medical practice weight management storage unit 33, a data reception unit 34, a data generation unit 35, and an interface unit 36. ing. The medical data management apparatus 3 further includes a main storage unit (not shown) (this main storage unit is composed of a plurality of storage areas). Medical data sent from the registration unit 11 is appropriately registered (stored).

  Below, the detail of the function of each part 31-36 contained in the medical data management apparatus 3 is demonstrated.

  The information management storage unit 31 is a storage device that stores management information indicating attributes and storage destinations (registration destinations) of medical data registered in the storage unit. Specifically, as shown in FIG. 2, the management information is information associated with patient identification information (patient ID (Identifier)), patient name, sex, date, type, details, and various types of information indicating a storage location. is there.

  In the following description, various information indicating the patient name, gender, date, type, details, and storage location are described with the term “information” at the end, for example, patient name information. The term “information” may be omitted as appropriate. The same applies to first generation criterion information, second generation criterion information, and medical practice weighting information described later.

  Here, details of various types of information included in the management information will be described.

  The patient identification information is information for identifying a patient. The patient name information is information indicating the name of the patient identified by the patient identification information. The sex information is information indicating the sex of the patient identified by the patient identification information. The date information is information indicating a date when medical data indicated by type information and detailed information described later is registered in a storage destination indicated by storage destination information described later. The type information is information indicating the type of medical data registered in the storage destination indicated by the storage destination information. The detailed information is information indicating details of medical data registered in the storage destination indicated by the storage destination information. The storage destination information is information indicating a storage destination of medical data indicated by the type information and the detailed information.

  For example, the management information a1 shown in FIG. 2 includes “medical patient A (patient identification information“ 1 ”) medical image data and diagnostic report obtained by ultrasonic examination (US: UltraSonography). This is information indicating that “Registered in the storage destination“ \\ Storage1 \ 1 \ 20100401 ”on the 1st of the month”. Here, the management information a1 has been described as an example, but the same applies to the other management information a2 to a14 shown in FIG.

  The data generation reference storage unit 32 includes first generation reference information (data generation reference) that defines the type and details of medical data required when generating the overhead view data, as well as the acquisition destination and expansion method of these medical data. Information) and second generation reference information (layout definition information) that defines the layout of the overhead view data. Specifically, as shown in FIG. 3A, the first generation reference information is information associated with various types of information indicating the type, details, acquisition destination, expansion method, and reference. The second generation reference information is information associated with various types of information indicating the layout type and setting, as shown in FIG.

  Here, details of various information included in the first generation reference information will be described. However, since the type information and the detailed information are the same as the type information and the detailed information included in the management information described above, detailed description thereof is omitted here.

  The acquisition destination information is information indicating an acquisition destination of medical data indicated by the type information and the detailed information. The expansion method information is set to correspond to a weighting factor indicated by reference information described later, and is information indicating a method for expanding medical data indicated by type information and detailed information regarding overhead data. The reference information is information indicating a weighting factor that serves as a reference in determining the expansion method indicated by the expansion method information.

  For example, the first generation reference information b1 shown in FIG. 3A is “the weighting factor is“ 10 ”, and the medical image data acquired from the own apparatus or another apparatus is developed into the overhead view data as a representative image. ". Here, the first generation reference information b1 has been described as an example, but the same applies to the other first generation reference information b2 to b10 illustrated in FIG. 3A, and detailed description thereof is omitted here. .

  Next, details of various types of information included in the second generation reference information will be described.

  The layout type information is information indicating the layout type of the overhead view data. The setting information is information indicating a specific setting (value) regarding the layout type indicated by the layout type information.

  For example, the second generation reference information c1 illustrated in FIG. 3B is information indicating that “the arrangement of various information in the overhead view data is in descending order”. Here, the second generation criterion information c1 has been described as an example, but the same applies to the other second generation criterion information c2 to c5 illustrated in FIG. 3B, and thus detailed description thereof is omitted here. .

  The medical practice weight management storage unit 33 is a storage device that stores medical practice weighting information (weighting coefficient information) that defines weighting factors indicating the importance of medical data used when generating overhead data. Specifically, as shown in FIG. 4, the medical practice weighting information is information associated with various types of information indicating type, details, part, normal weight, report weight, progress and no change weight, and others. .

  Here, details of various types of information included in the medical practice weighting information will be described. However, since the type information and the detailed information are the same as the type information and the detailed information included in the management information and the first generation reference information, detailed description is omitted here.

  The part information is information indicating which part the medical data indicated by the type information and the detailed information is related to. The normal weight information is information indicating a weighting coefficient when a diagnostic report is not included in the type of medical data indicated by the type information. The report weight information is information indicating a weighting coefficient when a diagnostic report is included in the type of medical data indicated by the type information. The progress and no-change weight information is information indicating a weight coefficient at the time of follow-up observation. The weight information without progress and change is mainly used when determining the weighting factor when the medical data acquired from the other system 2 indicates that “there is no particular symptom finding”. Further, the information indicating other is information indicating the weighting condition set by the user and its value (weighting coefficient).

  For example, the medical practice weighting information d1 shown in FIG. 4 is information indicating that “when the medical data is document data related to a letter of introduction, the weighting coefficient of this medical data is set to“ 3 ””. Here, the medical practice weighting information d1 has been described as an example, but the same applies to the other medical practice weighting information d2 to d11 illustrated in FIG. 4, and thus detailed description thereof is omitted here.

  The data receiving unit 34 is input from the registration unit 11 in the user interface 1 and receives medical data including at least patient information (in this embodiment, patient identification information, patient name information, and gender information). Is received, the medical data that has received the input is registered in the main storage unit. In addition, when the data reception unit 34 receives input of patient identification information (patient identification information) sent from the registration unit 11 in the user interface 1 with the patient visit, the data reception unit 34 is identified (identified) by the patient identification information. The data generation unit 35 is requested to generate the overhead view data of the patient.

  When receiving the overhead data generation request from the data reception unit 34, the data generation unit 35 has a function of acquiring medical data including the above-described patient specifying information (hereinafter described as patient identification information). Specifically, first, the data generation unit 35 extracts management information including the patient identification information attached to the overhead data generation request from the information management storage unit 31. Next, the data generation unit 35 acquires medical data including the above-described patient identification information from the storage destination (which is one storage area in the storage unit) indicated by the storage destination information included in the extracted management information. Furthermore, the data generation unit 35 acquires medical data including the patient identification information attached to the overhead view data generation request via the interface unit 36. Examples of the medical data acquired from the other system 2 include medical data e1 to e4 as shown in FIG. 5, but are not particularly limited thereto.

  The data generation unit 35 stores the medical data acquired as described above, the first generation reference information and the second generation reference information stored in the data generation reference storage unit 32, and the medical practice weight management storage unit 33. Based on the stored medical practice weighting information, the medical course of the patient indicated by the patient identification information attached to the overhead data generation request is shown to the user (for example, doctor, nurse, medical clerk, etc.) The overhead data generation process for generating the overhead data that can be presented is executed. The details of the overhead data generation processing will be described later together with the description of the sequence diagram shown in FIG.

  The interface unit 36 is a communication interface for enabling communication between the other system 2 and the medical data management apparatus 3.

  The medical data management device 3 described above includes a CPU (Central Processing Unit) (not shown), and each unit is controlled by this CPU.

  Next, an example of the operation of the medical data management apparatus 3 configured as described above will be described with reference to the schematic diagrams of FIGS. 2 to 5 and FIGS. 7 to 9 and the sequence diagram of FIG. Here, the registration unit 11 in the user interface 1 will be described as patient identification information (hereinafter referred to as patient identification information) generated by a patient visit in response to an operation of a user (here, assumed to be a medical clerk). ) Is sent to the medical data management apparatus 3. In the present embodiment, the patient identification information generated along with the patient visit is patient identification information. However, the present invention is not limited to this, and if the patient identification information is data generated along with the patient visit, in particular, It does not ask the type. In this embodiment, it is assumed that this patient specifying information is obtained by scanning an insurance card with a specific device when the patient visits the patient.

  Further, a plurality of medical data is registered in advance in the main storage unit of the medical data management device 3, and is stored in the information management storage unit 31, the data generation reference storage unit 32, and the medical practice weight management storage unit 33 in the medical data management device 3. Assumes that various types of information shown in FIGS. 2 to 4 are stored in advance.

  The various processes shown below are executed by a CPU (not shown) controlling each unit according to a program stored in advance.

  First, when receiving the patient specifying information (patient identification information) sent from the registration unit 11 in the user interface 1, the data receiving unit 34 is specified (identified) by the patient specifying information that has received the input. The data generation unit 35 is requested to generate patient overhead data, that is, an overhead data generation request with patient identification information is sent to the data generation unit 35 (step S1).

  Subsequently, when the data generation unit 35 receives the overhead view data generation request sent from the data reception unit 34, the data generation unit 35 extracts management information including the patient identification information attached to the overhead view data generation request from the information management storage unit 31. (Step S2). Here, it is assumed that the patient identification information attached to the overhead data generation request is “1”. Therefore, the data generation unit 35 extracts management information a1 to a10 including the patient identification information “1” from the information management storage unit 31 as illustrated in FIG.

  Next, the data generation unit 35 acquires medical data from the storage destination indicated by the storage destination information included in the extracted management information a1 to a10 (step S3).

  Subsequently, the data generation unit 35 acquires medical data including the patient identification information “1” attached to the overhead data generation request from the linked other system 2 via the interface unit 36 (step S4). ). Here, it is assumed that the data generation unit 35 has acquired the medical data shown in FIG. Note that any method may be used as the method by which the data generation unit 35 acquires medical data from the other system 2.

  Next, the data generation unit 35 performs a weighting process on the medical data acquired by the above-described steps S3 and S4 according to the medical practice weighting information stored in the medical practice weight management storage unit 33. (Step S5). Here, the data generation unit 35 weights the acquired medical data as shown in FIG. For example, the management information a1 acquired by the process of the above-described step S3 indicates that “there is medical image data taken by ultrasonic diagnostic examination (US) and its diagnostic report (image / REP)” based on the type information and the detailed information. Since it is clearly shown, the data generation unit 35 refers to the medical practice weight information d7 shown in FIG. 4 and sets the weighting factor to “3”. The data generation unit 35 repeatedly executes this weighting process not only on the management information a1 but also on all acquired information.

  Subsequently, the data generation unit 35 acquires the acquired medical data in the overhead view data based on the result of the process in step S5 described above and the first data generation reference information stored in the data generation reference storage unit 32. Is determined (step S6). Here, the data generation unit 35 develops the acquired medical data in the overhead view data based on the result of the weighting process shown in FIG. 7 and the first data generation reference information shown in FIG. Decide how. For example, the type information and detailed information included in the management information a1 indicate “image / REP” and “US”, and the weighting coefficient “3” is set in the management information a1 by the process of step S5 described above. Based on the first data generation reference information b5, the data generation unit 35 determines the medical data development method indicated by the type information and the detailed information included in the management information a1 in the overhead view data as “findings, diagnosis results (ie, , Expand findings and diagnostic results). The data generation unit 35 repeatedly executes the process for determining the expansion method not only on the management information a1 but also on all acquired medical data.

  Next, the data generation unit 35 follows the layout indicated by the second data generation reference information stored in the data generation reference storage unit 32, and determines the acquired medical data by the process in step S6 described above. The overhead view data is generated by the developed method (step S7). Here, the data generation unit 35 generates the overhead data f1 shown in FIG. For example, since the expansion method of the management information a3 is determined as “findings, diagnosis results, key image” indicated by the first data generation reference information b6 as a result of the process in step S6, the type information “image / REP” is determined. And the medical data indicated by the detailed information “US / ES” are displayed including the key image, and the overhead view data is generated.

  In the overhead view data shown in FIG. 8, more detailed information can be obtained by embedding hyperlinks found on Web pages, for example, in places where only facts are developed (eg, medical care, issuance of introduction letters). It may be possible to allow access to. In this case, as shown in FIG. 9, it is necessary to manage information g1 to g4 including URL (Uniform Resource Locator) for accessing detailed information using a storage unit (not shown).

  Thereafter, the data generation unit 35 sends the overhead view data generated by the process of step S7 described above to the overhead view data display unit 12 in the user interface 1 (step S8), and ends the operation in the medical data management device 3. . Here, the data generation unit 35 sends the generated overhead data to the overhead data display unit 12 in the user interface 1 in the form of returning it, but is not limited to this. For example, the data generation unit 35 The generated overhead data may be sent to the overhead data display unit 12 in accordance with the overhead data acquisition request sent from the overhead data display unit 12 in the user interface 1.

  In addition, when the overhead data display unit 12 in the user interface 1 receives the input of the overhead data transmitted from the data generation unit 35, the overhead data that has received the input is displayed on a display device (not illustrated), and is displayed to the user. Present overhead data.

  According to the embodiment described above, it is possible to provide bird's-eye view data that can sufficiently ensure the bird's-eye view of the entire medical course, and as a result, can contribute to improvement of diagnosis accuracy.

  In addition, although some embodiment of this invention was described, these embodiment is shown as an example and is not intending limiting the range of invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

  DESCRIPTION OF SYMBOLS 1 ... User interface, 2 ... Other system, 3 ... Medical data management apparatus, 11 ... Registration part, 12 ... Overhead data display part, 31 ... Information management memory | storage part, 32 ... Data generation reference | standard storage part, 33 ... Medical practice weight management Storage unit 34... Data reception unit 35... Data generation unit 36.

Claims (5)

A medical data management device configured to be able to acquire data from a plurality of databases storing medical data including at least patient information,
Weighting factor information storage means for storing weighting factor information defining a weighting factor indicating the importance of each medical data used when generating overhead data;
Display method of each of the medical data in the overhead data set so as to correspond to the weighting coefficient and at least one of the medical data acquisition destination, data type, and modality type (corresponding to the original expansion method) Data generation reference information storage means for storing data generation reference information defining
A data acquisition means for acquiring medical data of the patient information from the database when receiving an overhead data generation request for generating overhead data of a desired patient;
Overhead data generation that generates the overhead data representing the medical course of the desired patient based on each of the acquired medical data, the stored weight coefficient information, and the stored data generation reference information Means,
Presenting means for presenting the generated overhead view data to a user. A medical data management apparatus comprising: The medical data management apparatus according to claim 1,
The overhead data generation means includes
Means for weighting each acquired medical data according to the stored weight coefficient information;
A medical data management apparatus comprising: means for generating the overhead view data obtained by developing each of the weighted medical data according to a development method indicated by the stored data creation reference information. The medical data management apparatus according to claim 2, wherein
Layout definition information storage means for storing layout definition information defining the layout of each medical data in the overhead view data;
The overhead data generation means includes
When expanding each of the weighted medical data according to the expansion method, the medical data is expanded in accordance with a layout indicated by the stored layout definition information, and the overhead data is generated. Medical data management device. In the medical data management device according to any one of claims 1 to 3,
The data acquisition means includes
Upon receiving the overhead data generation request transmitted from an external device together with patient information for specifying the patient at the time of visit of the desired patient, medical data including the patient information is acquired from a predetermined acquisition destination. A medical data management apparatus characterized by the above. In the medical data management device according to any one of claims 1 to 4,
Each of the medical data is data including at least one of medical image data, a diagnostic report, and document data;
The expansion method is a method for indicating what of the medical image data, the diagnosis report, and the document data included in each medical data is expanded as the overhead data. Management device.

Images