KR101522333B1 - Method for constructing mobile service system and interworking with hospital information for self-management of blood pressure and blood sugar - Google Patents

Abstract

The present invention relates to a mobile service system interworking with hospital information for self-management of blood pressure and blood sugar and a method thereof. The mobile service system interworking with the hospital information for the self-management of the blood pressure and the blood sugar according to the embodiment of the present invention includes a hospital information database which has EMR/OCS which is a medical record of a patient, a middleware server which responds to a request by searching the data from the database with regard to a vital sign data request related to the blood sugar and the blood pressure, a gateway which relays a first medical examination and V/S of the hospital information database to the middleware server, and a smart device which manages the V/S and receives a related service.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a system and method for synchronizing hospital information and a mobile service system for blood pressure and blood glucose self-

The present invention relates to a hospital information interlocking and mobile service method for preventing blood glucose and blood pressure related diseases and for self-management of blood glucose and blood pressure for continuous aftercare, and more particularly, And the network security factor, and it uses the data combination algorithm to maintain the integrity of the input data, measures the risk of diseases, and links hospital information for blood pressure and blood glucose self-management to provide blood glucose and blood pressure management service And a mobile service system and a method thereof.

Personal healthcare services are a tool that provides the ability for an individual to safely store and manage all his or her health information for the lifetime of the person or family.

The transition to an aging society and the westernization of dietary life are leading to an increase in the number of chronic illnesses, and due to the insufficient management of chronic diseases, the burden of the medical expenses of the people is increasing due to the increase in the cost of treatment due to aftereffects.

In order to solve this problem, a self-care service is required for continuous health management before and after chronic illness.

However, the conventional blood glucose / blood pressure self-management service lacks the reliability of the measurement result simply by maintaining the measurement result only in the own terminal.

Conversely, hospital measurement data is closed because it is difficult for individuals to access.

Therefore, in order to perform a reliable disease management service, it is necessary to correlate the data measured by the individual with the measurement data of the hospital in addition to the measurement records of the hospital, so that the accurate medical management service can be provided by the medical staff.

Accordingly, the present invention specifies a mobile service method for self-management of blood glucose and blood pressure, and a method for linking with hospital information.

SUMMARY OF THE INVENTION The present invention has been made to solve the conventional problems as described above, and has the following objectives.

The present invention relates to a hospital information interlocking and mobile service method for blood glucose and blood pressure self-management for prevention of a blood glucose / blood pressure-related disease and continuous follow-up management, And to provide a system and a method for providing a blood glucose / blood pressure management service by measuring the risk of a disease using a data combination algorithm for maintaining the integrity of input data.

In order to accomplish the above object, the present invention is implemented by the following embodiments.

The present invention relates to a hospital information database having EMR / OCS which is a medical record of a patient having a patient number as a distinguisher;

(V / S) data request from a blood pressure / diabetes self-management app embedded in a smart device, and a database for managing separate blood pressure / blood glucose data for the member, A middleware server for searching for and responding to the request;

(V / S) request for the patient information from the middleware server (Middleware Server) and V / S for the Vital Sign (hereinafter referred to as V / S) A gateway for relaying information to the middleware server;

Administers a blood pressure / diabetic self-management app, manages a V / S for self-management of blood glucose / diabetic patients through service menus based on a signal input from the middleware server, And a smart device capable of receiving related services.

And,

A Mobile Response Module that receives an HTTPS request from a smart device and processes the response;

A message generator module for composing a message for delivery to the smart device;

A Message Parser Module for analyzing the XML message requested by the smart device and extracting the data, storing the extracted XML message in the blood glucose / blood pressure database, or forwarding an XML message to the gateway;

A blood glucose self-management engine module that measures the risk of cardiovascular disease based on blood glucose measurement information and returns the result;

A blood pressure self-management engine module for measuring the risk of stroke disease based on blood pressure measurement information and returning the result;

A DB manager module for storing the V / S data requested from the smart device in the middleware server;

And a gateway request / response module for requesting data from the gateway (gateway) and for receiving the requested data in order to fetch the EMR initial recording sheet and the V / S information of the hospital .

And,

When the middleware server is requested to link with the hospital information by the PHR link button in the blood pressure / diabetes self-management app, the middleware server transmits the patient identifier number to the gateway, Requesting the data, and returning the received data to the blood pressure / diabetes self-management app.

And,

The V / S data that the patient self-measures and inputs are stored and managed in the smart device.

And,

Storing EMR / OCS, which is a medical record of the patient having the patient number as a distinguisher by the hospital information database;

(V / S) related to blood glucose / blood pressure from the blood pressure / diabetes self-management application built in the smart device by a middleware server having a database for managing separate blood pressure / Retrieving data from the database for a data request and providing a response;

Requests a V / S of the hospital information database for the initial registration and V / S of the hospital information database with respect to the initial record and Vital Sign (V / S) request of the patient information from the middleware server by the gateway, Relaying the received initial record and the V / S information to the middleware server;

The V / S for the patient's own blood glucose / diabetes self-management is managed through the service menus based on the signal inputted from the middleware server by the smart device in which the blood pressure / And to receive relevant services;

And a control unit.

The present invention has the following effects with the above-described configuration.

The present invention can measure the blood glucose / blood pressure related disease risk that can be practically utilized when interfacing hospital information and personal measurement input data and system configuration and service method for secure data transmission in performing blood glucose / blood pressure self-management service .

In addition, in order to measure an accurate disease risk, a combination of personal input data and hospital data can prevent an incorrect risk measurement result that may be generated due to inconsistency between personal input data and hospital input data.

Figure 1 shows a 4-Tiers schematic of the overall system.
FIG. 2 is a diagram
FIG. 3 shows an example of a personal measurement input data and a hospital data combination algorithm
4,
FIG. 5 is a graph showing the relationship between the risk of stroke and hospital information
FIG. 6 is a graph showing the relationship between the risk of cardiovascular disease and hospital information
FIG. 7 is a graph showing blood glucose management and hospital information interlocking screen

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The applicants will now describe in detail the construction of the present embodiments with reference to the accompanying drawings.

Detailed descriptions of well-known functions and constructions that may be unnecessarily obscured by the gist of the present invention will be omitted.

The overall system structure consists of 4-Tiers, legacy Hospital Information System, Gateway, Middleware Server, and blood pressure diabetes self-management app.

The legacy hospital information system is a system with EMR / OCS, which is the patient's medical record with the patient number as the distinguisher.

Gateway requests initial recording and V / S of legacy hospital information system for initial record of patient information from Middleware Server and Vital Sign (V / S) request and sends initial record and V / S information to Middleware Server As well.

Middleware Server has a database for managing separate blood pressure / blood glucose data for members. It searches for data from the database in response to requests for blood glucose / blood pressure related V / S data from a self-administered blood glucose diabetes self-management app, Role.

When this server receives a request for interworking with hospital information by the PHR link button in the blood pressure diabetes self-management app, it requests the V / S data of the legacy hospital information system by transmitting the patient distinguisher number to the gateway, Diabetes self-management app.

Finally, the self-managing blood glucose diabetes self-management app on the patient's smart device allows the patient to manage the V / S for his own blood glucose diabetes self-management and receive related services through the service menus.

At this time, the V / S data that the patient self-measures and inputs is stored and managed in the smart device.

In order to prevent network entry and interception security threats between the layers, there is a communication between the middleware server and the gateway through the HTTPS network protocol. .

The encryption method at this time is AES 256 bits or E.C.C. Encryption is performed by a cryptographic technique. Between the gateway and the legacy hospital information system, the hospital uses the connection protocol of the DBMS because it is the hospital's internal network.

The middleware server is composed as follows.

The Mobile Response Module is a module for receiving HTTPS requests from smart devices and processing responses.

The request message from the smart device is delivered to the Message Parser module, and the response message transmitted from the Message Generator module is transmitted to the smart device by HTTPS.

The Message Generator Module is a module that composes a message for delivery to a smart device.

This message consists of user information and V / S information in VitalsignHeight, VitalsignBloodSugar, VitalsignBloodPressure and DiabetesCheckCycle messages written in XML. An example of the message is as follows.

 XML message definition Protocol Response XML VitalsignHeight <ResponsestatusCode = "100">
<Vitalsigns>
<Vitalsign>
<Date> 2013-09-10 </ Date>
<Time> 10:49 </ Time>
<Height> 177.0 </ Height>
<Weight> 72.0 </ Weight>
<DeptFlag> P </ DeptFlag>
</ Vitalsign>
<Vitalsign>
<Date> 2013-09-23 </ Date>
<Time> 17:36 </ Time>
<Height> 177.0 </ Height>
<Weight> 70.0 </ Weight>
<DeptFlag> P </ DeptFlag>
</ Vitalsign>
<Vitalsign>
<Date> 2013-11-14 </ Date>
<Time> 18:33 </ Time>
<Height> 179.0 </ Height>
<Weight> 80.0 </ Weight>
<DeptFlag> P </ DeptFlag>
</ Vitalsign>
</ Vitalsigns>
</ Response> VitalsignBloodSugar <ResponsestatusCode = "100">
<Vitalsigns>
<Vitalsign>
<Date> 2013-05-23 </ Date>
<Time> 10:57 </ Time>
<BloodSugar> 70 </ BloodSugar>
<DeptFlag> P </ DeptFlag>
<Option> 0 </ Option>
</ Vitalsign>
<Vitalsign>
<Date> 2013-05-09 </ Date>
<Time> 12:41 </ Time>
<BloodSugar> 10 </ BloodSugar>
<DeptFlag> P </ DeptFlag>
<Option> 0 </ Option>
</ Vitalsign>
<Vitalsign>
<Date> 2013-04-10 </ Date>
<Time> 23:04 </ Time>
<BloodSugar> 50 </ BloodSugar>
<DeptFlag> P </ DeptFlag>
<Option> 0 </ Option>
</ Vitalsign>
<Vitalsign>
<Date> 2013-05-08 </ Date>
<Time> 15:20 </ Time>
<BloodSugar> 20 </ BloodSugar>
<DeptFlag> P </ DeptFlag>
<Option> 0 </ Option>
</ Vitalsign>
<Vitalsign>
<Date> 2013-04-20 </ Date>
<Time> 06:09 </ Time>
<BloodSugar> 96 </ BloodSugar>
<DeptFlag> H </ DeptFlag>
<Option> 0 </ Option>
</ Vitalsign>
<Vitalsign>
<Date> 2013-04-17 </ Date>
<Time> 02:13 </ Time>
<BloodSugar> 83 </ BloodSugar>
<DeptFlag> H </ DeptFlag>
<Option> 0 </ Option>
</ Vitalsign>
</ Vitalsigns>
</ Response> VitalsignBloodPressure <ResponsestatusCode = "100">
<Vitalsigns>
<Vitalsign>
<Date> 2013/04/18 </ Date>
<Time> 09:00 </ Time>
<BPSystolic> 100 </ BPSystolic>
<BPDiastolic> 60 </ BPDiastolic>
<Pulse> 67 </ Pulse>
<BodyTemperature> 36.5 </ BodyTemperature>
<DeptFlag> H </ DeptFlag>
</ Vitalsign>
<Vitalsign>
<Date> 2013/04/18 </ Date>
<Time> 05:00 </ Time>
<BPSystolic> 120 </ BPSystolic>
<BPDiastolic> 80 </ BPDiastolic>
<Pulse> 76 </ Pulse>
<BodyTemperature> 36.0 </ BodyTemperature>
<DeptFlag> H </ DeptFlag>
</ Vitalsign>
<Vitalsign>
<Date> 2013/04/15 </ Date>
<Time> 04:00 </ Time>
<BPSystolic> 120 </ BPSystolic>
<BPDiastolic> 80 </ BPDiastolic>
<Pulse> 96 </ Pulse>
<BodyTemperature> 36.9 </ BodyTemperature>
<DeptFlag> H </ DeptFlag>
</ Vitalsign>
</ Vitalsigns>
</ Response> DiabetesCheckCycle <ResponsestatusCode = "100">
<DiabetesCheckCycles>
<DiabetesCheckCycle>
<LastCheckDate> 20130724 </ LastCheckDate>
<CheckNm> Ophthalmologic examination </ CheckNm>
<CheckCycle> 12 </ CheckCycle>
</ DiabetesCheckCycle>
<DiabetesCheckCycle>
<LastCheckDate> 20121117 </ LastCheckDate>
<CheckNm> Proteolysis </ CheckNm>
<CheckCycle> 12 </ CheckCycle>
</ DiabetesCheckCycle>
<DiabetesCheckCycle>
<LastCheckDate> 20121117 </ LastCheckDate>
<CheckNm> Blood creatinine </ CheckNm>
<CheckCycle> 12 </ CheckCycle>
</ DiabetesCheckCycle>
</ DiabetesCheckCycles>
</ Response>

The Message Parser Module parses the XML message requested by the smart device, extracts the data, stores it in the blood glucose / blood pressure database, or transmits the XML message to the gateway.

The SAX parser is used because this XML message can have a large amount of data.

The blood glucose self-management engine module is a module that measures the risk of cardiovascular disease based on blood glucose measurement information and returns the result. Age, HDL, total cholesterol, smoking status, presence or absence of diabetes mellitus were the factors for measuring cardiovascular risk.

These factors are composed of the information input from the smart device and the information received from the hospital information. By the data combination algorithm, it is possible to overcome the problem that the exact risk can not be measured due to inconsistency between the personal input data and the hospital input data .

The blood pressure self-management engine module is a module that measures the risk of stroke disease based on blood pressure measurement information and returns the result. Factors for measuring the risk of stroke are "sex, age, weight, height, waist circumference, and hip circumference".

These elements consist of the information input from the patient's smart device and the information received from the hospital information. By applying the data combination algorithm, it prevents the inaccurate risk measurement result that may be caused by inconsistency between the personal input data and the hospital input data. can do.

DB Manager Module is a DB access and management module for storing V / S data requested from a smart device in Middleware Server. Data analyzed in Message Parser Module is stored and managed in DB on middleware server through DB Manager Module.

The Gateway Request / Response Module is a module for requesting data from the gateway and receiving the requested data to retrieve the EMR initial recording paper and V / S information of the hospital.

In order to secure data transmission to the gateway, data is encrypted by AES 256bits or E.C. encryption algorithm, and the data is decrypted and transmitted to the Message Generator Module, the blood glucose self-care engine module, and the blood pressure self-management engine module.

The data received from the hospital is not stored on the Middleware Server and the user measurement data is not transmitted to the gateway. This is to prevent the tampering of the medical record by distinguishing it from the data managed in the existing hospital information system.

The personal input V / S data and the hospital V / S data can not perform accurate self-diagnosis due to inconsistent measurement timing.

Therefore, an algorithm for matching the two data is required. For this, the data combination algorithm used in the blood glucose self-care engine module and the blood pressure self-care engine module is as follows.

When V / S data of patients' smart devices and hospitals are fetched by requesting data designated by period, basic data for measuring self-management risk based on recent date is generated.

Service menu configuration for self-management of blood glucose and blood pressure in smart device is as follows. Blood pressure monitoring, weight management, and menstrual blood pressure monitoring, stress and depression questionnaire, exercise management, nutrition management, diabetes management, blood pressure management, and weight management.

A big menu Sub Menu main function Measurement of cardiovascular risk Cardiovascular disease risk Cardiovascular disease risk measure output Risk of stroke Stroke risk measure output Stress and Depression Questionnaire Stress Questionnaire Stress level output through questionnaire input Depression questionnaire Depression level output through questionnaire input Exercise management Exercise history management Management of exercise history information by calendar Nutrition management What is diabetes? Medical information output for diabetes Health guide Blood Pressure Precautions to Overcome Blood Sugar Related Disease Contents Output Methods for weight loss Weight loss method Content output Recommended food Suggested food content output Food to avoid Output of avoiding food content Search for customized food Food content recommendation service Diabetes Management Diabetes Management Hospital information interworking and personal input data management Blood pressure management Blood pressure management Hospital information interworking and personal input data management Weight Management Obesity test Output of test result by obesity inspection algorithm BMI inspection Output of test result by BMI measurement algorithm Abdominal obesity test Output test result by abdominal obesity measurement algorithm Set User information User information management Set target value Set blood glucose and exercise amount adjustment target value First record Initial record of hospital information interworking alarm Set medication time and gauge check test interval alarm Information Service Introduction Service Introduction

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the inventions. Will be clear to those who have knowledge of.

Claims (5)

A hospital information database having EMR / OCS, which is a patient's medical record having a patient number as a distinguisher;
(V / S) data request from a blood pressure / diabetes self-management app embedded in a smart device, and a database for managing separate blood pressure / blood glucose data for the member, A middleware server for searching for and responding to the request;
(V / S) request for the patient information from the middleware server (Middleware Server) and V / S for the Vital Sign (hereinafter referred to as V / S) A gateway for relaying information to the middleware server;
Administers a blood pressure / diabetic self-management app, manages a V / S for self-management of blood glucose / diabetic patients through service menus based on a signal input from the middleware server, A smart device that allows you to receive relevant services; and a hospital information interlocking and mobile service system for blood pressure / blood glucose self-management.
The method according to claim 1,
A Mobile Response Module that receives an HTTPS request from a smart device and processes the response;
A message generator module for composing a message for delivery to the smart device;
A Message Parser Module for analyzing the XML message requested by the smart device and extracting the data, storing the extracted XML message in the blood glucose / blood pressure database, or forwarding an XML message to the gateway;
A blood glucose self-management engine module that measures the risk of cardiovascular disease based on blood glucose measurement information and returns the result;
A blood pressure self-management engine module for measuring the risk of stroke disease based on blood pressure measurement information and returning the result;
A DB manager module for storing the V / S data requested from the smart device in the middleware server;
And a gateway request / response module for requesting data from the gateway (gateway) and for receiving the requested data in order to fetch the EMR initial recording sheet and the V / S information of the hospital Hospital information interworking and mobile service system for blood pressure / blood glucose self - management.
The method according to claim 1,
When the middleware server is requested to link with the hospital information by the PHR link button in the blood pressure / diabetes self-management app, the middleware server transmits the patient identifier number to the gateway, A hospital information interlocking and mobile service system for blood pressure / blood glucose self-management that requests data and returns the received data to the blood pressure / diabetes self-management app.
The method according to claim 1,
The V / S data that the patient self-measures inputs are linked to hospital information and mobile service system for self-management of blood pressure / blood glucose in smart device.
Retrieving a patient's medical record EMR / OCS having the patient number as a distinguisher by the hospital information database;
(V / S) related to blood glucose / blood pressure from the blood pressure / diabetes self-management application built in the smart device by a middleware server having a database for managing separate blood pressure / Retrieving data from the database for a data request and providing a response;
Requests a V / S of the hospital information database for the initial registration and V / S of the hospital information database with respect to the initial record and Vital Sign (V / S) request of the patient information from the middleware server by the gateway, Relaying the received initial record and the V / S information to the middleware server;
The V / S for the patient's own blood glucose / diabetes self-management is managed through the service menus based on the signal inputted from the middleware server by the smart device in which the blood pressure / And to receive relevant services;
A combination algorithm step of generating integrated data based on recent date for integrating personal input V / S data and hospital V / S data;
A hospital information interlocking and mobile service method for self - management of blood pressure / blood glucose.

Images