JP3549049B2 - Medical information system - Google Patents

Description

【００９０】
【表２】

【００９１】
【表３】

このようなレイアウトに用いられるテーブルは、制御アプリケーション用テーブル７１内に格納される。
【００９２】
カード型カルテ制御アプリケーション７上で、上述したようなレイアウト１０１を一例とした任意のレイアウトの設定が可能となっている。このようなレイアウトを作成した後、レイアウト上の各フィールドと、一時テーブル８の検歴テーブル８３などの項目とを対応付けるための設定が可能となっている。このようなレイアウトおよびレイアウト上の各フィールド、各フィールドと一時テーブル８の各テーブル内の項目との対応についての情報が、制御アプリケーション用テーブル７１に格納される。
【００９３】
前述したような処理フロー中において、予め設定されたレイアウトが選択され、この選択されたレイアウト上に配置された各フィールドにデータの変更内容が入力される。ユーザにより入力された変更内容は、制御アプリケーション用テーブル７１内に実体を伴うフィールドについてはその項目のデータ更新が行われ、各フィールドに対応する一時テーブル８内のデータ項目の内容が更新される。このとき更新日時および更新者などの更新記録情報が必要な項目については、一時テーブル８への記録更新時に、交信記録情報が同時に書き込まれる。
【００９４】
カルテの保存処理を行う場合には、一時テーブル８内の各データの変更内容についてサーバ１側に送信し、医療情報データベース群３の内容を更新させる。更新内容のうち、更新日時および更新者などの更新記録情報が必要なデータ項目が含まれる場合、サーバ１の医療情報データベース群３を更新する際に、更新記録情報を同時に書き込む。また、時系列により整列させられるデータ項目が含まれる場合、医療情報データベース群３の内容を更新する際に、前のデータと時系列で関連づけて格納するように構成する。
【００９５】
このように、カード型カルテ制御アプリケーション７を用いて任意のレイアウトを設定することができ、このレイアウト上にサーバ１内の複数のデータベース中の項目を混在させて配置することが可能である。ユーザは、カード型カルテ制御アプリケーション７を利用して予め設定したレイアウトを起動することで、複数のツールを開くことなく入出力制御方法の異なるデータ項目の編集を行うことが可能となる。更新記録が必要なデータについては、更新日時や更新者などの更新記録情報を作成して同時にサーバ１側の医療情報データベース群３内に格納されるため、データの真正性を維持することができる。また、時系列に配列されるデータについては、前回のデータとの時系列についての関連性に基づいて保存されるため、時系列でのデータの読み出しについても対応することが可能となる。
【００９６】
【発明の効果】
本発明に係る医療情報システムでは、内容更新時におけるデータ制御方法により複数のデータテーブルに分類してサーバ内のデータ蓄積手段に蓄積された医療情報を、クライアント側で任意に設定したレイアウト上に呼び出して更新することが可能である。内容更新時には各データ制御方法に基づいてデータの保存が行われるため、データの真正性、見読性、保存性を維持することが可能となる。
【図面の簡単な説明】
【図１】本発明の概略構成を示すブロック図。
【図２】その制御フローチャート。
【図３】その制御フローチャート。
【図４】その制御フローチャート。
【図５】その制御フローチャート。
【図６】その制御フローチャート。
【図７】その制御フローチャート。
【図８】その制御フローチャート。
【図９】その制御フローチャート。
【図１０】具体例の制御ブロック図。
【図１１】サーバ側データベースのテーブルを示す構成図。
【図１２】サーバ側データベースのテーブルを示す構成図。
【図１３】サーバ側データベースのテーブルを示す構成図。
【図１４】サーバ側データベースのテーブルを示す構成図。
【図１５】サーバ側データベースのテーブルを示す構成図。
【図１６】サーバ側データベースのテーブルを示す構成図。
【図１７】一時テーブルの構成図。
【図１８】一時テーブルの構成図。
【図１９】一時テーブルの構成図。
【図２０】一時テーブルの構成図。
【図２１】一時テーブルの構成図。
【図２２】レイアウト画面の一例を示す説明図。[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a medical information system capable of handling patient medical information as electronic data.
[0002]
[Prior art]
In an information management system including a server that manages a database and a client that can access the database, data authenticity, readability, and storability are required. In particular, in a medical facility such as a hospital, many computers are installed in all departments such as patient reception, input / output of medical information and audit information, and accounting. In order to ensure the consistency of the data handled by each department and improve the efficiency of work, such medical information is managed collectively by the server, and the clients installed in each department can access the database managed by the server. Conceivable.
[0003]
When the medical care information is digitized, it is necessary to secure the above-described authenticity, readability, and storability as well as privacy protection. In order to ensure readability and storability, it is possible to output to a terminal monitor or printer, and it is possible to refer to it promptly as necessary, and to refer to data continuously, It is necessary to satisfy the requirement that a simple backup is possible. In order to ensure authenticity, it is necessary to satisfy requirements such as user authentication, falsification prevention, confusion prevention, and history storage. Furthermore, from the viewpoint of privacy protection, it is necessary to satisfy requirements such as system security, network security, access control, and logging (storage of history).
[0004]
In an electronic medical record system that handles such medical information, in order to ensure the authenticity described above, it is necessary to record the input contents together with update record information such as the update date and time and the updater in chronological order ( For example, medical record information on the patient's symptoms including the patient's response to the chief complaint and treatment, and the test history including test instructions and test results, etc., and items that require only the latest information to be recorded (eg, patient Some items have different recording rules, such as basic information. If different databases are constructed in accordance with the differences in the rules of each item when recording, if the data is input, added, or updated, the database corresponding to each item will conform to the respective recording rules. Each data is recorded. As described above, when input, update, or addition occurs in the chart information displayed on the screen, each item is recorded in the corresponding database according to each recording rule.
[0005]
Also, in the electronic medical record system as described above, when referring to the patient's medical record information, a layout according to the conventional paper chart format is configured, and past medical information accumulated in chronological order is displayed on this layout. Is often displayed in a time-series manner in the column corresponding to.
[0006]
[Problems to be solved by the invention]
If a doctor examines a patient and it is a re-examination, determine the points of the diagnosis from past medical records and consider the progress of the symptoms heard in the interview at the consultation. Is going. As described above, if the medical records are simply displayed in chronological order in a format similar to the conventional paper chart, it is possible that the point of this diagnosis may be outside the range of the initial display screen. Yes, it is necessary to search the medical records arranged in chronological order for a matter of interest by operating the screen. Such an operation becomes a burden when a doctor performs a consultation operation, and causes a decrease in operation efficiency.
[0007]
Also, as described above, when a plurality of data tables are set based on the recording rule at the time of updating the content, when data is called from the server side to the client side and used, the data table is prepared in advance for each data table. Each data item is configured to be displayed on the layout. When a data item on another data table is used, a layout corresponding to the data table is opened as another window to display each data, and an input of a content change is received.
[0008]
When the user refers to each data and inputs a content change, the user operates the corresponding tool to display a plurality of layouts on the window and inputs the change content. The accepted change content is reflected in the data table corresponding to each layout by the data control method at the time of updating the data item.
[0009]
As described above, in order to refer to a data item spanning a plurality of data tables or to input a change content, it is necessary to start a tool corresponding to each data table, and a complicated operation is required.
[0010]
In addition, there are many layouts prepared in advance corresponding to each data table, and it is difficult for a user to design an easy-to-use layout. In particular, one data item selected from a plurality of data tables is one. There is a problem that it is not possible to create a layout that is arranged on the screen.
[0011]
SUMMARY OF THE INVENTION An object of the present invention is to allow a doctor to display information of interest to a doctor in a format desired by the doctor when referring to the medical information, so that the contents of the medical record to be grasped can be checked at a glance.
[0012]
Another object of the present invention is to guarantee the authenticity of data, enable layout display in which data items of different data control methods are mixed at the time of content update, and assist arbitrary layout design. To provide a medical information system.
[0013]
[Means for Solving the Problems]
The present invention focuses on the fact that when a doctor performs a medical examination with reference to past medical records, the items to be focused on tend to match to some extent depending on the medical department and the type of patient's disease.
[0014]
That is, the present invention, when displaying the medical information, by registering in advance what kind of layout to display the medical record, by enabling to select which layout to display the medical record, The medical records to be noted by the doctor can be displayed so as to be promptly confirmed.
[0015]
In addition, a layout is registered according to a medical department or a disease, and it is possible to input and update the medical information displayed on the layout, and the input or updated content is stored in a corresponding database. Provide a mechanism to record items in accordance with the recording rules of items, and to be able to comply with the three principles required for electronic medical record systems while increasing the degree of freedom in the display format of medical information.
[0016]
The medical information system according to the present invention classifies data items in medical information including patient profile information and medical examination information into a plurality of data tables by a data control method at the time of content update, and stores the data items in a data storage unit in a server. A medical information system capable of storing and calling and referencing and updating medical information from a data storage unit in a server from a client, and a plurality of temporary storages provided on the client side corresponding to a plurality of data tables. Data table, and data selecting means for selecting required data from the plurality of data tables and storing the selected data in the temporary storage data table, Layout storage means for storing a layout in which input / output fields of data items having different data control methods are set; The data stored in the temporary storage data table is From layout storage means A display format selection unit to be displayed according to the selected layout; and a layout displayed by the display format selection unit, Entering data in the fields allows for different data control methods. A change content receiving means for receiving data change, a temporary storage table changing means for reflecting the data change content received by the change content receiving means on the temporary storage data table, and a change content of the temporary storage data table stored in the server. When updating the contents of the corresponding data table Depends on the data item Data updating means for reflecting the data in each data table based on the data control method.
[0017]
Here, it is possible to adopt a configuration further including a layout support means for associating the temporary storage data table with each field on the layout created in advance.
[0018]
The layout displayed by the display format selection means can be configured to be selectable from a plurality of layouts created in advance according to the item to be focused on.
[0019]
Further, when the layout selected by the display format selection means includes a data item that requires update record information such as an update date and time and an updater, the update record information is stored in the data table when the change content is reflected in the data table. It can be configured to be stored at the corresponding location in the table.
[0020]
Further, when the layout selected by the display format selection means includes data items arranged in chronological order, when the changes are reflected in the data table, the changes can be stored in chronological order. .
[0021]
BEST MODE FOR CARRYING OUT THE INVENTION
[Summary of the Invention]
FIG. 1 shows a schematic configuration of a medical information system to which one embodiment of the present invention is applied.
[0022]
The server 1 manages medical information including patient profile information, medical examination information, and the like, and includes a chart table for managing chart contents, a patient disease name table in which data on patient disease names is stored, and patient profile information. The medical information database group 3 includes a patient profile table in which patient information is stored, and a patient test result table in which various test results are stored.
[0023]
The server 1 includes a retrieval process 4 for retrieving patient information and the like from the medical information database group 3, an update process 5 for updating data based on the contents of changes from the client side, and the like.
[0024]
A client 2 is connected to the server 1 via a LAN, the Internet, a VPN (Virtual Private Network), or the like. The client 2 includes a client core 6 that constitutes an input / output interface between a user and a server. The client 2 is equipped with a card-type chart control application 7. This card-type chart control application 7 can use commercially available card-type database software. For example, a file maker PRO, Microsoft Access, or other database software can be used.
[0025]
The client 2 includes a temporary table 8 including a data table group corresponding to each medical information database group 3 on the server 1 side. The data specifications of this temporary table 8 are disclosed, and the data can be used by the card-type chart control application 7. The data in each data table group is stored in the medical information database group 3 of the server 1. Each downloaded data is temporarily stored, and is updated based on a change in the data received from the user.
[0026]
Further, the client 2 includes a layout group 9 set by the user via the card-type chart control application 7. The card type chart control application 7 is configured to display the data downloaded to the temporary table 8 on the layout selected from the layout group 9.
[0027]
[Control flow of card-type chart]
<Overall processing flow>
FIG. 2 shows an outline of the overall processing flow of the present invention.
[0028]
In step S1, the card-type chart is activated. Here, the card-type chart control application 7 is activated via the front-end tool (input / output means) and the client core 6 by the user's operation.
[0029]
In step S2, the input of the patient ID to be selected by the user is accepted. In step S3, the client core 6 notifies the card type chart control application 7 of the patient selection data based on the patient ID received from the user. In step S4, the card-type chart control application 7 requests the server 1 for data in the medical information database group 3, downloads necessary data, and stores it in the temporary table 8. In step S6, a notice to the effect that downloading of the patient data has been executed is sent to the front-end tool, and the data is read from the temporary table 8 and displayed on a layout that is set in advance or selected each time. .
[0030]
In step S7, a chart input by the user is accepted. The change content of the data input by the user is written out to the temporary table 8 via the front-end tool in step S8, and the change content is reflected.
[0031]
In step S9, an instruction to save the medical chart is received from the user. In step S10, the card-type chart control application 7 reads out the changed contents of the temporary table 8 and issues an update request to the card-type chart database on the server 1 side. At the same time, an update request is made to the document information management process of the client core 6. In step S11, the document information management process of the client core 6 issues an update request for the document database managed in the medical information database group 3 on the server 1 side.
[0032]
In step S12, the server 1 updates the card-type chart database in response to the update request from the card-type chart control application 7. In step S13, the server 1 updates the document database in response to the update request from the document information management process of the client core 6.
[0033]
As described above, the user can display the patient data (medical information of the patient) in a layout desired by the user, input the medical data in a state displayed in the desired layout, and store the input contents in a corresponding database. It can be updated according to the storage rules specified for the item.
[0034]
<Startup process flow>
FIG. 3 shows an outline of a processing flow at the time of activation.
In step S21, this instruction input is accepted when the user activates the user initial startup screen or tool box on the user terminal. In step S22, the card-type chart control application 7 is activated by the management process or the tool box of the client core 6.
[0035]
In step S22, the card type chart control application 7 displays a card selection screen according to the card type chart management master. In step S23, a card selection input from the user is received. In step S24, the corresponding card screen is activated from the card-type chart control application 7 based on the card selection input received from the user. In step S25, the corresponding card screen is displayed on the front end tool.
[0036]
<Patient selection process flow>
FIG. 4 shows an outline of a processing flow in the patient selection processing.
In step S31, an instruction input for performing patient selection by the user is received. When the instruction button set on the patient selection screen is clicked or a patient selection instruction is given from a pull-down menu or the like, the patient selection tool is activated by the management process of the client core 6 or the tool box in step S32. .
[0037]
In step S33, a patient ID input from the user is received. In step S34, a patient ID input by the user on the activated patient selection tool is received, and this is notified to the card-type chart control application 7.
[0038]
In step S35, the card-type chart control application 7 refers to the card-type chart management master and displays the selected patient ID on the card selection screen.
[0039]
In step S36, an instruction input for card selection is received from the user. In step S37, the corresponding layout information is read from the layout group 9 based on the card selection instruction input by the user, and the card screen is activated. In step S38, the selected card screen is displayed on the front end tool.
[0040]
In step S39, patient data is downloaded from the server 1 based on the patient ID input by the user. Here, the download target management master is referred to based on the patient ID input by the user, a request for necessary patient data is made to the server 1, and the search result from the server 1 is notified on the card screen. At the same time, the transmitted patient data is stored in the temporary table 8.
[0041]
In step S40, the server 1 executes a search process based on a search request from the card-type chart control application 7, and transmits the search result to the card-type chart control application 7.
[0042]
In step S41, a notification of the search result is displayed on the card screen of the front-end tool, and the patient data is displayed.
With the above operation, the chart information can be displayed with the layout registered in advance by the user.
[0043]
<Chart input-order screen start processing flow>
FIG. 5 shows a processing flow for starting the chart input order screen.
In step S51, an input of a chart input order instruction from a user is received. Here, an order button is displayed on the card screen, and an instruction input from the user by operating the order button is received.
[0044]
In step S52, the other-screen activation tool is activated based on an instruction input from the user received on the card screen displayed by the front-end tool. In step S53, the card-type chart control application 7 activates another screen activation tool to activate the prescription input screen. In step S54, an order input from the user is accepted on the prescription input screen. In step S55, an order input end instruction is received from the user.
[0045]
In step S56, the contents of the document buffer are updated based on the order input received from the user, and the changed contents are reflected in the editor. In addition, when an instruction to end the order input is received, another screen activation tool of the card-type chart control application 7 is activated.
[0046]
In step S57, the card screen is activated from the other screen activation tool of the card-type chart control application 7, a notification of the end of the order is displayed on the card screen, and the contents of the order input by the user are transmitted via the temporary file. To reflect on the card screen.
[0047]
<Chart input-Schema screen startup processing flow>
FIG. 6 shows a processing flow of starting the chart input schema screen.
In step S61, an input of a chart input schema instruction from a user is received. Here, a schema input button is displayed on the card screen, and an instruction input from the user by operating the schema input button is received.
[0048]
In step S62, the other-screen activation tool is activated based on an instruction input from the user received on the card screen displayed by the front-end tool. In step S63, the card type chart control application 7 activates the other screen activation tool to activate the schema input screen. In step S64, a schema description input from the user is received on the schema input screen. In step S65, an end instruction of the schema description input from the user is received.
[0049]
In step S66, the image file is updated based on the schema description input received from the user. In addition, the schema description input on the editor screen is reflected, and editing from the user is accepted. When a schema description input end instruction is received from the user, another screen activation tool of the card-type chart control application 7 is activated.
[0050]
In step S67, an instruction to delete and save the schema description is received from another screen activation tool of the card-type chart control application 7, and when the schema description is to be deleted, the schema description on the editor screen is deleted. When performing, the image file is copied to the card-type chart control application 7 and passed. These processes are notified on the card screen, and the contents of the image file based on the schema description input by the user are reflected on the card screen.
[0051]
<Chart input-Schema direct description processing flow>
It is also possible to accept the schema description directly on the card screen, and the processing flow in this case is shown in FIG.
[0052]
In step S71, an input of a chart input schema instruction from a user is received. Here, a schema input button is displayed on the card screen, and an instruction input from the user by operating the schema input button is received.
[0053]
In step S72, the screen shifts to a schema input screen on the front end tool. In step S73, a schema description input from the user is received on the schema input screen. In step S74, an end instruction of the schema description input from the user is received. In step S75, the content of the schema description is displayed on the card screen based on the schema description input received from the user. Here, the image file arbitrarily created on the front-end tool is transferred to the client core 6 when the medical record is saved, and at the same time, the medical information database group 3 on the server 1 is updated according to the contents.
[0054]
<Chart input-Disease name screen startup processing flow>
FIG. 8 shows a processing flow of chart entry-disease name screen activation.
In step S81, an input of a disease name registration instruction from a user is received. Here, a disease name registration instruction button is displayed on the card screen, and when the user operates the disease name registration instruction button, it is determined that the disease name registration instruction has been input.
[0055]
In step S82, the other screen activation tool is activated based on an instruction input from the user accepted on the card screen displayed by the front end tool. In step S83, the card-type chart control application 7 activates another screen activation tool to activate the disease name input screen. In step S84, a disease name input from the user is accepted on the disease name input screen. In step S85, an end instruction of the disease name input from the user is received.
[0056]
In step S86, the name of the disease received from the user is transmitted to the medical information database group 3 on the server 1 side, and a saving process is performed. In step S87, the server 1 registers the transmitted disease name in the corresponding database of the medical information database group 3 and updates the data.
[0057]
In step S86, if there is an instruction to shift to editing of patient data from the disease name input screen, the flow shifts to step S88 to activate another screen activation tool of the card-type chart control application 7. In step S88, the disease name data is re-read. In step S89, patient data is downloaded based on the read disease name data. Here, the disease name data is transmitted to the server 1, and the search result transmitted from the server 1 is stored in the temporary table 8.
[0058]
In step S90, in the search process of the server 1, patient data is searched based on the disease name data transmitted from the card type chart control application 7, and the search result is returned to the card type chart control program 7.
[0059]
In step S91, the downloaded patient data is displayed on the card screen activated by the other screen activation tool of the card-type chart control application 7, and the state shifts to a state of accepting a chart input by the user.
[0060]
<Chart preservation processing flow>
FIG. 9 shows a processing flow for storing the medical record.
In step S101, a termination instruction is received from the user. Here, an end instruction button is displayed on the card screen, and when the end instruction button is operated by the user, the chart input processing is ended and the chart storage processing is started.
[0061]
In step S102, the contents of the change made by the user are reflected on the temporary table 8, and a notification to the effect that the user has received an end instruction on the card screen is transmitted to the card-type chart control application 7.
[0062]
In step S103, the card type chart control application 7 transmits the contents of the change of the chart to the server 1 side. In step S104, the server 1 updates the data content in the medical information database group 3.
[0063]
In step S103, the updated document data is stored in the document buffer controlled by the client core 6, and a request to save the document data is issued to the document storage management process of the client core 6. In step S105, the changed document content is transmitted from the document storage management process of the client core 6 to the server 1 side. In step S106, the document data is updated based on the document data transmitted from the document storage management process of the client core 6.
[0064]
In step S103, a request to release the currently used patient data is made to the management process of the client core 6. In step S107, the currently used patient data is released to make it available for use by another client.
[0065]
[Chart data linkage]
FIG. 10 shows an example of actual chart data linkage.
As shown in FIG. 10, the medical information database group 3 in the server 1 includes, for example, a patient database 11, a card-type chart database 12, an outpatient list database 13, a ward patient information database 14, an examination history table 15, and a user database 16. And so on.
[0066]
As shown in FIG. 11, the table of the patient database 11 includes a patient number, a patient's name, gender, date of birth, ward code, ward code, home address information, work place information, and the like.
[0067]
As shown in FIG. 12, the table of the card type medical chart database 12 includes a patient ID, a card number, a registrant ID, a registrant name, a medical department code, a medical department name, a creation date, a last update date, and a last update user ID. , Basic information such as the last updated user name, and various data fields.
[0068]
As shown in FIG. 13, the table of the outpatient list database 13 includes a reception number, a reception date, a patient ID, a patient name, a gender, a date of birth, a reservation time, a reception time, a reservation source medical department code, and a reservation source medical department. Name, appointment department code, appointment department name, doctor's code, doctor's name, medical division, status division, reservation reception, emergency department, medical office code, medical office name, pregnant woman flag, etc. It is composed of
[0069]
As shown in FIG. 14, the table of the ward patient information database 14 includes a patient number, a ward code, a ward code, a bed number, a medical department code, an outpatient flag, an admission date, a system flag, a user flag, an item code, an item attribute, It consists of items such as item names.
[0070]
As shown in FIG. 15, the table of the examination history table 15 includes items such as an order number, a patient ID, a designated date, an information type, an information classification, an identification code, a document number, and an information content part.
[0071]
As shown in FIG. 16, the table of the user database 16 includes a user number, a password, a user name, a date of birth, gender, an e-mail address, a pager number, a job type code, an in-charge / out-charge category, and a requesting doctor input. Required classification, drug user number, personnel ID, medical history room ID, department code, department ward code, department room code, job code, effective start date, effective end date, ... Document type access authority table, tool access The configuration includes items such as an authority table, a valid period start date and time, a valid period end date and time, and an emergency flag.
[0072]
The temporary table 8 of the client 2 includes a patient basic information table 81, a card chart information table 82, an examination history table 83, an outpatient information table 84, a ward patient information table 85, and the like. Corresponding to the card-type chart database 12, the examination history table 15, the outpatient list table 13, and the ward patient information database 14, in which the data downloaded from the server 1 is temporarily stored, and the contents of the change inputted by the user are stored. Configured to reflect.
[0073]
As shown in FIG. 17, the patient basic information table 81 includes a patient number, a patient's name, gender, date of birth, ward code, ward name, ward code, preferential treatment category, vitamin calculation category, updater, update date, and update time. , Home address information, emergency contact information, and workplace information.
[0074]
As shown in FIG. 18, the card chart information table 82 includes a patient ID, a card number, a registrant ID, a registrant name, a medical department code, a medical department name, a creation date, a creation time, a last update date, a last update time, It is composed of basic items such as a last update user ID and a last update user name, and various data fields.
[0075]
As shown in FIG. 19, the examination history table 83 includes a patient ID, an order number, an examination result code, an examination result item name, an examination result value, an examination result unit, a normal value (upper limit), a normal value (lower limit), and an abnormal value. It consists of items such as flags.
[0076]
As shown in FIG. 20, the outpatient information 84 is configured to include items such as a reception number, a reception date, a patient ID, a patient name, gender, date of birth, reservation time, and reception time.
[0077]
As shown in FIG. 21, the ward patient information table 85 has a configuration including items such as a patient number, a ward code, a room code, a bed code, a medical department code, a date of hospitalization, an item code, an item attribute, and an item name. Has become.
[0078]
In the client 2, a control application table further including a plurality of pieces of layout information used by the card-type chart control application 7, a field definition body arranged on each layout, data information with an entity used in each field, and the like. 71 are provided.
[0079]
The client 2 may also be provided with other master files such as a ward patient information reference master, a bed master, a medical department master, a ward master, and a ward master.
[0080]
[Layout design]
FIG. 22 shows a layout of a cardiology re-examination chart (report) as an example of a layout on the card-type chart control application 7.
[0081]
The reexamination chart (report) layout 101 includes an electrocardiogram result input field 111, a chest X-ray finding input field 121, an echo echo result summary input field 131, a treadmill result summary input field 141, a Holter electrocardiogram result summary input field 151, and a myocardium. A cinch result input field 161 and the like are provided.
[0082]
In the electrocardiogram result input column 111, items such as examination date, basic rhythm, heart rate, finding 1, finding 2, finding 3, etc. are set, and field names Date 5, Text 047, Number 23, Text 048, Text 049, and Text 050 are respectively set. The field has been assigned.
[0083]
In the chest X-ray finding input column 121, items such as examination date, cardiac shadow, rib cage, finding 1, finding 2, finding 3, etc. are set, and the field names Date3, Number19, Number20, Text040, Text041, Text042 are respectively set. Fields are assigned.
[0084]
In the echo echo result summary input column 131, items such as examination date, EF, LVDd, AR, MR, PR, TR, and summary are set, and the field name is Date4, Number21, Number22, Text043, Text044, Text045, respectively. , Text046, and Text091 fields are assigned.
[0085]
Items such as examination date, end point, symptom appearance, arrhythmia, main ST-T change, and other diagnosis are set in the treadmill result summary input field 141, and the field names Date1, Text030, and Text031, respectively, are set. , Text032, Text033, and Text035.
[0086]
In the Holter ECG result summary input field 151, the examination date, basic rhythm, minimum heart rate, maximum heart rate, average heart rate, maximum PR interval, supraventricular extrasystole, ventricular extrasystole, symptoms, drugs used, Items such as other are set, and fields having the field names Date2, Text037, Number13, Number14, Number15, Number16, Number17, Number18, Text038, Text055, and Text039 are respectively assigned.
[0087]
Items such as an examination date, an initial image, a late image, and a summary are set in the myocardial scintigraphy result input column 161, and fields having field names Date6, Text092, Text093, and Text094 are assigned to the respective items.
[0088]
Tables 1, 2 and 3 show the correspondence between field names and input item names used in the layout 101.
[0089]
[Table 1]

[0090]
[Table 2]

[0091]
[Table 3]

The table used for such a layout is stored in the control application table 71.
[0092]
An arbitrary layout can be set on the card-type chart control application 7 by taking the layout 101 as an example. After such a layout is created, it is possible to make settings for associating each field on the layout with items such as the inspection history table 83 of the temporary table 8. Information on such a layout and each field on the layout and the correspondence between each field and an item in each table of the temporary table 8 is stored in the control application table 71.
[0093]
In the processing flow as described above, a preset layout is selected, and the data change content is input to each field arranged on the selected layout. Regarding the contents of the change input by the user, the data of the item is updated for the field having the substance in the control application table 71, and the content of the data item in the temporary table 8 corresponding to each field is updated. At this time, for items requiring update record information such as the update date and time and the updater, the communication record information is simultaneously written when the record is updated in the temporary table 8.
[0094]
When the medical record storage process is performed, the contents of change of each data in the temporary table 8 are transmitted to the server 1 and the contents of the medical information database group 3 are updated. When the update content includes data items that require update record information such as the update date and time and the updater, the update record information is simultaneously written when the medical information database group 3 of the server 1 is updated. Further, when data items arranged in time series are included, when the contents of the medical information database group 3 are updated, the contents are stored in association with previous data in time series.
[0095]
As described above, an arbitrary layout can be set using the card-type chart control application 7, and items in a plurality of databases in the server 1 can be arranged on the layout in a mixed manner. The user can edit data items having different input / output control methods without opening a plurality of tools by activating a preset layout using the card-type chart control application 7. For data that requires an update record, update record information such as the update date and time and the updater is created and stored in the medical information database group 3 of the server 1 at the same time, so that the authenticity of the data can be maintained. . In addition, since the data arranged in time series is stored based on the relevance of the previous data with respect to the time series, reading of data in time series can be supported.
[0096]
【The invention's effect】
In the medical information system according to the present invention, the medical information stored in the data storage means in the server after being classified into a plurality of data tables by the data control method at the time of content update is called on a layout arbitrarily set on the client side. Can be updated. At the time of content update, data is stored based on each data control method, so that it is possible to maintain the authenticity, readability, and preservation of data.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a schematic configuration of the present invention.
FIG. 2 is a control flowchart thereof.
FIG. 3 is a control flowchart thereof.
FIG. 4 is a control flowchart thereof.
FIG. 5 is a control flowchart thereof.
FIG. 6 is a control flowchart thereof.
FIG. 7 is a control flowchart thereof.
FIG. 8 is a control flowchart thereof.
FIG. 9 is a control flowchart thereof.
FIG. 10 is a control block diagram of a specific example.
FIG. 11 is a configuration diagram showing a table of a server-side database.
FIG. 12 is a configuration diagram showing a table of a server-side database.
FIG. 13 is a configuration diagram showing a table of a server-side database.
FIG. 14 is a configuration diagram showing a table of a server-side database.
FIG. 15 is a configuration diagram showing a table of a server-side database.
FIG. 16 is a configuration diagram showing a table of a server-side database.
FIG. 17 is a configuration diagram of a temporary table.
FIG. 18 is a configuration diagram of a temporary table.
FIG. 19 is a configuration diagram of a temporary table.
FIG. 20 is a configuration diagram of a temporary table.
FIG. 21 is a configuration diagram of a temporary table.
FIG. 22 is an explanatory diagram showing an example of a layout screen.

Claims (5)

Data items in medical information including patient profile information and medical examination information are classified into a plurality of data tables by a data control method at the time of content update and stored in data storage means in a server, and a client stores data in the server. A medical information system capable of calling and referencing and updating the medical information from data storage means,
A plurality of temporary storage data tables provided on the client side corresponding to the plurality of data tables,
Data selection means for selecting required data from the plurality of data tables and storing the data in the temporary storage data table,
Layout storage means for storing a layout in which input / output fields of the data items having different data control methods are set;
Display format selection means for displaying data stored in the temporary storage data table in accordance with a layout selected from the layout storage means ;
On a layout displayed by the display format selection means, by inputting data in the field, a change content receiving means for receiving a change in data of a different data control method ,
A temporary storage table changing means for reflecting the change content of the data received by the change content receiving means in the temporary storage data table,
Data update means for reflecting the change content of the temporary storage data table in each data table based on a different data control method according to a data item when updating the content of the corresponding data table in the server,
Medical information system comprising: 2. The medical information system according to claim 1, further comprising a layout support unit for associating the temporary storage data table with each field on a layout created in advance. 3. The medical information system according to claim 1, wherein the layout displayed by the display format selection unit is configured to be selectable from a plurality of layouts created in advance according to an item to be focused on. 4. When the layout selected by the display format selection means includes a data item requiring update record information such as an update date and time and an updater, the update record information is updated when the change content is reflected in the data table. The medical information system according to claim 1, wherein the medical information system stores the medical information at a corresponding location in the data table. If the layout selected by the display format selection means includes data items arranged in chronological order, the changes are stored in chronological order when the changes are reflected in the data table. The medical information system according to any one of claims 1 to 4.

Images