KR102545745B1 - Method of providing evidence-based healthcare services based on personal data - Google Patents

Abstract

The present invention relates to a method for providing based healthcare services based on personal data, comprising: a data collection server for collecting medical information stored in medical institutions such as electronic medical records or disease records and lifelog information stored in mobile or wearable devices; A data management server that standardizes the data collected by the data collection server, transmits it to individuals through encoding and decoding processes, and utilizes it as My Data.

Description

Method of providing evidence-based healthcare services based on personal data

The present invention relates to a method for providing based healthcare services based on personal data.

Medidata, which provides clinical big data analysis and clinical trial solutions in the United States, has a market capitalization of $4.1 billion (approximately KRW 4.4 trillion), and infrastructure to upload and trade health care data is in place in Korea. there is.

Recently, the Ministry of Trade, Industry and Energy announced that 40 institutions, including university hospitals, will participate in the bio big data platform project to share medical information of more than 50 million patients in Korea. There are few companies and institutions that integrate and standardize comprehensive health examination data, so the need for research and utilization of personal medical record integration technology development is emerging.

Due to the aging population and increased interest in health, there is an increasing demand for personal medical information and health information to be integrated, managed and analyzed by individuals to promote customized personal health and establish health care policies, and personal health record services play a key role in Health ICT. As technologies such as IT, BT, and NT convergence with medical services, the healthcare industry that provides medical services anytime, anywhere is expanding, and related technologies such as smartphones, personal health devices, and mobile health technologies In addition, the development of personal health record technology and services, which are expected to be industrialized in the future, are being actively carried out around the world.

In order to activate the personal medical record integration service, the reliability of PHR information must be secured through linkage with the hospital's electronic medical record (emr), and specific related institutions (medical institutions, insurance companies, etc.) can share and interlock. It is necessary to evolve from a hospital system with a dependent system to an interconnected PHR that is not dependent.

Interconnected PHR is a type of PHR that receives necessary information from various medical institutions and integrates and stores them in a plurality of distributed servers or one server.

Because it is not dependent on a specific medical institution, individuals can have complete management authority over their health records, medical information can be exchanged naturally, and personalized services can be easily developed based on individual complete records. there is.

Since medical records in various formats must be received and stored from different institutions, there is a difficulty in that standardization of formats and terms must be pre-determined.

Standardization targets range from the most basic and important content, such as terms and codes, to medical treatment methods, forms, and administrative systems, which are inevitably different for each health and medical institution. Among them, terminology is the biggest obstacle and national standards are required.

Medical data can be divided into three major categories. It consists of medical information such as electronic medical records and disease records, genome information through DNA analysis, and lifelog information collected in real time through mobile or wearable devices. By collecting, combining, and analyzing these data, it is becoming possible to provide personalized medical services.

My Data refers to all processes in which an individual who owns information directly manages his/her information as an information subject and directly controls the provision of information when necessary, thereby actively participating in services linked to various industries such as asset and credit management and personal health management. . In other words, individuals can directly manage personal information generated on various platforms in the form of data, and provide or block personal information as needed when using third-party platforms. My Data technology is a system that supports the safe management of personal information through this process concept, and builds a big data ecosystem so that information providers can safely use personal information in various industries such as finance, medical care, and telecommunications. can do.

However, in the case of Personnel Healthcare Record My-Data and PHR-My-data related to medical care and personal health as shown in FIG. 1, technological progress is slow in Korea, and institutional agreements that must be preceded for technology utilization are also problematic. . To this end, first of all, the data stored in the medical institution must be utilized, and it is necessary to build a standardized API in a form that enables communication.

On the other hand, the above-mentioned background art is technical information that the inventor possessed for derivation of the present invention or acquired in the process of derivation of the present invention, and cannot necessarily be said to be known art disclosed to the general public prior to filing the present invention. .

The present invention has been devised to solve the above problems, and an object of the present invention is to collect and integrate distributed data of various medical institutions, manage them in an encoding-decoding process and transmit them to a user terminal, and in the subsequent process It is to enable personal data-based grounded healthcare services to be realized.

The technical problem of the present invention is not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the following description.

In order to solve the above problems, a personal data-based based healthcare service providing method according to an embodiment of the present invention provides medical information stored in medical institutions such as electronic medical records or disease records and lifelog information stored in mobile or wearable devices. Data collection server to collect; A data management server that standardizes the data collected by the data collection server, transmits it to individuals through an encoding-decoding process, and utilizes it as My Data; and a user terminal unit for storing the data transmitted from the data management server.

In one embodiment, the data collection server includes a medical institution targeting unit that collects and integrates personal medical record data from various medical institutions; and a personal device targeting unit that collects and integrates personal life record data from various personal devices.

In one embodiment, the medical institution target unit, a data structuring unit for structuring medical records of various medical institutions; and a data integration unit that standardizes and integrates storage methods of various types of medical records and integrates medical records by storage section.

In one embodiment, when the data management server receives medical record data from the data collection server and stores the medical record method being used in each medical institution, data for automatically standardizing different medical record methods for each medical institution using a standardization code. standardization department; a data encoding-decoding unit for converting and restoring data using character codes ASCII or Unicode to encrypt (encode) and restore (decode) the standardized data; and a data transmitter for transmitting the encrypted or restored data to the user terminal.

In one embodiment, in the data management server, data may be stored in a physical storage device, which may be stored in a storage housing having a rectangular column shape in a specific space.

In one embodiment, the storage housing may include a shock absorber at each lower corner to protect the storage device stored therein from external shock or vibration.

In one embodiment, the shock absorber is formed in a cylindrical shape, the body portion to which the elastic support and the bottom support are connected; Elastic supports installed along the upper part of the main body so as to be rotatable and inclined in a direction closer to other elastic supports from the upper side to the lower side to support the storage housing seated on the upper side; and a plurality of floor supports installed along the bottom of the main body so as to be rotatable and inclined in a direction closer to other floor supports from the lower side to the upper side to support the floor and the main body.

In one embodiment, the main body portion is formed in a cylindrical shape, and the main body is connected to the elastic support and the bottom support to be rotatably installed in the movable groove formed at an upper and lower sides; an elastic member installed between one side of the elastic support facing downward and the moving groove so that the elastic support can stand upright; and an absorption plate installed along the inlet of the movable groove to absorb shock due to collision with the elastic supporter.

In one embodiment, the elastic support is connected to the movable groove so that the lower part is rotatably installed, the lower inclined surface is supported by the elastic member, and the lower portion of the support triangle is rotatably coupled to the upper portion. Including support pillars; A support triangle having a flat upper surface and a lower part formed in a triangular shape with a narrower gap toward the lower side, and a lower portion connected to a coupling groove formed on an upper portion of the support column to be rotatably installed using a bolt and nut fastening means; and a washboard-shaped concavo-convex made of an elastic material to improve adhesion with the binding groove seated on the upper side is formed along the upper surface, and as the binding groove seated on the upper side rises or falls, the upper part of the support triangle It may include; a support protrusion that slides on.

The above-described problem solving means are merely exemplary and should not be construed as intended to limit the present disclosure. In addition to the exemplary embodiments described above, additional embodiments may exist in the drawings and detailed description of the invention.

According to one aspect of the present invention described above, the dispersed data of various medical institutions are collected and integrated, managed through encoding-decoding processes and transmitted to the user terminal, and in the subsequent process, based healthcare services based on personal data are realized. It has the effect of making it possible.

Effects of the present invention are not limited to the effects mentioned above, and various effects may be included within a range apparent to those skilled in the art from the contents to be described below.

1 is a conceptual diagram showing personal medical record My Data.
2 is a diagram illustrating a method for providing based healthcare services based on personal data according to an embodiment of the present invention.
3 is a block diagram showing a data collection server of a method for providing based health care service based on personal data according to an embodiment of the present invention.
4 is a block diagram showing a data management server of a method for providing based healthcare services based on personal data according to an embodiment of the present invention.
5 is a diagram showing a data management server and a user terminal of a method for providing based healthcare services based on personal data according to an embodiment of the present invention.
6 to 9 are diagrams illustrating a shock absorber of a method for providing based healthcare services based on personal data according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The detailed description of the present invention which follows refers to the accompanying drawings which illustrate, by way of illustration, specific embodiments in which the present invention may be practiced. These embodiments are described in sufficient detail to enable one skilled in the art to practice the present invention. It should be understood that the various embodiments of the present invention are different from each other but are not necessarily mutually exclusive. For example, specific shapes, structures, and characteristics described herein may be implemented in another embodiment without departing from the spirit and scope of the invention in connection with one embodiment.

Additionally, it should be understood that the location or arrangement of individual components within each disclosed embodiment may be changed without departing from the spirit and scope of the invention. Accordingly, the detailed description set forth below is not to be taken in a limiting sense, and the scope of the present invention, if properly described, is limited only by the appended claims, along with all equivalents as claimed by those claims. Like reference numbers in the drawings indicate the same or similar function throughout the various aspects.

On the other hand, throughout this specification, when a certain component is said to "include", it means that it may further include other components, not excluding other components as long as the contrary description is A. do. In addition, a “module” or “unit” for a component used in this specification performs at least one function or operation. And a "module" or "unit" may perform a function or operation by hardware, software, or a combination of hardware and software.

Terms including ordinal numbers, such as first and second, may be used to describe various components, but these components are not limited by the above terms. The terminology described above is only used for the purpose of distinguishing one component from another.

In this specification, the term "comprising" is intended to designate that the features, numbers, steps, operations, components, parts, or combinations thereof described in the specification exist, but one or more other features, numbers, or steps However, it should be understood that it does not preclude the possibility of existence or addition of operations, components, parts, or combinations thereof. It should be understood that when an element is referred to as being “connected” to another element, it may be directly connected or connected to the other element, but other elements may exist in the middle.

In addition, in describing the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be abbreviated or omitted.

Hereinafter, preferred embodiments of the present invention will be described in more detail with reference to the drawings.

1 is a conceptual diagram showing personal medical record My Data.

2 is a diagram illustrating a method for providing based healthcare services based on personal data according to an embodiment of the present invention.

3 is a block diagram showing a data collection server of a method for providing based health care service based on personal data according to an embodiment of the present invention.

4 is a block diagram showing a data management server of a method for providing based healthcare services based on personal data according to an embodiment of the present invention.

5 is a diagram showing a data management server and a user terminal of a method for providing based healthcare services based on personal data according to an embodiment of the present invention.

6 to 9 are diagrams illustrating a shock absorber of a method for providing based healthcare services based on personal data according to an embodiment of the present invention.

The personal data-based based healthcare service providing method 10 according to an embodiment of the present invention may include a data collection server 100, a data management server 200, and a user terminal unit 300.

The data collection server 100 may collect medical information stored in a medical institution, such as an electronic medical record or disease record, and lifelog information stored in a mobile or wearable device.

The data management server 200 standardizes the data collected by the data collection server 100, transmits it to individuals through an encoding-decoding process, and makes it available as My Data.

The user terminal unit 300 may store data transmitted from the data management server 200 .

In one embodiment, the data collection server 100 may include a medical institution targeting unit 110 and a personal device targeting unit 120 .

The medical institution target unit 110 may collect and integrate personal medical record data from various medical institutions. Here, the medical institution may be any place that handles medical data, such as various hospitals and clinics, pharmacies, and the Health Insurance Corporation. Personal medical records may include everything related to medical activities, such as medical records, prescription records, surgery history, and payment history.

The personal device target unit 120 may collect and integrate personal life record data from various personal devices. Here, the personal device may be any device that handles personal life record data, such as a smart phone, a smart pad, or a wearable device (eg, a smart watch). Life records can be measured in relation to health throughout life, such as sleep time, wake-up time, meal amount, meal time, exercise amount, exercise time, sunlight exposure time, standing time, sitting time, and biorhythm. It can be any data that exists.

The medical institution target unit 110 and the personal device target unit 120 may collect data by communicating with various medical institutions and personal devices through a network.

Here, the network may include, for example, wireless communication, wired communication, optical ultrasound, or a combination thereof. Body Area Network (BAN), satellite communications, cellular communications, Bluetooth, Near Field Communication (NFC), Infrared Data Association standard (IrDA), Wireless Fidelity (WiFi), and Worldwide Interoperability for Microwave access (WiMAX) will be included in the communication path. Ethernet, digital subscriber line (DSL), fiber to the home (FTTH), and plain old telephone service (POTS) are examples of wired communication that can be included in a communication network. Also, a communications network can traverse multiple network topologies and distances. For example, a communications network may include a direct connection, a personal area network (PAN), a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), or any combination thereof. In addition, it may be performed through a low power wide area network (Low Power Wide Area Network) including LoRaWAN, NB-Fi, and RPMA. However, the description of the network communication network is not limited to the above communication network, and any latest data communication network may be applied.

In one embodiment, the medical institution target unit 110 may include a data structuring unit 111 and a data integration unit 112 .

The data structuring unit 111 may structure medical records of various medical institutions. In other words, medical records are structured by searching for hospital information, standardizing medical records, real-time linking of hospital items between hospital personnel and individuals, and comparing and analyzing medical items of hospitals in real time reflecting individual medical records.

* The data integration unit 112 standardizes and integrates storage methods of various types of medical records, and may integrate medical records by storage section. In other words, the storage method of various types of medical records is standardized and integrated, and the medical records are integrated by storage section by monitoring the current status of medical treatment so that the individual's medical condition can be confirmed.

In one embodiment, the data management server 200 may include a data standardization unit 210, a data encoding-decoding unit 220 and a data transmission unit 230.

When the data standardization unit 210 receives medical record data from the data collection server 100 and stores the medical record method used by each medical institution, it can automatically standardize different medical record methods for each medical institution using a standardization code. .

The standardization work method includes the first step of collecting medical institutions subject to standardization work, the second step of computerizing treatment and checkup codes for each medical institution, the third step of setting standardized treatment and health checkup codes, and the treatment of each hospital and clinic. And the 4th step of extracting the health checkup result value, the 5th step of automatically converting the result value through the matching algorithm, the 6th step of applying the decision value for each disease using the converted result value, the checkup result value and the decision value A seventh step of reviewing the logic validity of; and an eighth step of completing standardization work.

The data encoding-decoding unit 220 may convert and restore data using character codes ASCII or Unicode to encrypt (encode) and restore (decode) the standardized data.

In other words, as Personal Healthcare Record My-data (hereinafter referred to as PHR-My-data) is sensitive personal information, a method that is more secure than the previous data security level must be presented, and forgery and tampering are impossible. It must be possible, and technical supplements must be set to make information interpretation impossible in case of leakage. Therefore, a data encryption and restoration process is required, and the process may consist of a conversion process of data encoding and decoding. Data security, data processing speed, and data storage management are very easy because the data format undergoes encryption-restoration processes in accordance with applied standards and manuals in the encoding and decoding process.

PHR-My-data that has gone through the encoding process through character code ASCII or Unicode can be stored in a smartphone (ie, user terminal 300), which is a personal device, if the information subject individual consents, and PHR-My-data When an individual activates the use of data in the process of accessing content that requires data, customized services can be provided through a decoding process and matching with the data analysis results required by the content platform. In addition, through interaction between platform subjects who want to utilize PHR-My-data, based healthcare services based on personal data, rather than providing experiential healthcare services after treatment, can be realized.

The data transmission unit 230 may transmit the encrypted or restored data to the user terminal unit 300 .

In the data management server 20 according to an embodiment of the present invention, data may be stored in a physical storage device, which may be stored in a storage housing H of a square column shape in a specific space, , The storage housing (H) may further include a shock absorber 400 at each lower corner to protect the storage device stored therein from external shock or vibration.

delete

In one embodiment, the shock absorber 400 may include a main body 410 , an elastic support 420 and a bottom support 430 .

The body portion 410 is formed in a cylindrical shape, and the elastic support 420 and the bottom support 430 may be connected and installed.

A plurality of elastic supports 420 are installed along the upper part of the main body 410 so as to be rotatable, and installed to be inclined in a direction closer to other elastic supports from the upper side to the lower side, and the storage housing seated on the upper side ( H) can be supported.

A plurality of floor supports 430 are rotatably installed along the lower part of the main body 410 and installed to be inclined in a direction closer to other floor supports from the lower side to the upper side to support the floor and the main body. there is.

The bottom support 430 is shown in a bar shape, but is not limited to that shape and may be formed in the same shape as the elastic support 420.

In one embodiment, the body portion 410 may include a body 412 , an elastic member 414 and an absorption plate 416 .

The main body 412 is formed in a cylindrical shape, and the elastic support 420 and the bottom support 430 may be rotatably installed in moving grooves formed at upper and lower portions inclinedly.

The elastic member 414 may be installed between one side of the elastic support 420 facing downward and the movable groove 413 so that the elastic support 420 can stand upright.

The absorption plate 416 may be installed along the inlet of the movable groove 413 so as to absorb a shock caused by a collision with the elastic supporter 420 .

In one embodiment, the elastic support 420 may include a support pillar 422, a support triangle 424 and a support protrusion 426.

The support pillar 422 is connected to the movable groove 413 so that the lower part can rotate, and the lower inclined surface is supported by the elastic member 414, and the lower part of the support triangle 424 is rotatably coupled to the upper part. It may include a coupling groove (422a) for installation.

The support triangle 424 is formed in a triangular shape with a flat upper surface and a narrower gap toward the lower side, and a lower portion is formed by fastening means of bolts and nuts to the coupling groove 422a formed on the upper part of the support pillar 422. It can be connected and installed so that it can be rotated using it.

The support protrusion 426 has washboard-shaped irregularities formed of an elastic material along the upper surface to improve adhesion with the binding groove seated on the upper side, and as the binding groove seated on the upper side moves up or down, It can slide on top of the support triangle 424 .

In one embodiment, the support triangle 424 may have a rail groove 424a formed in a longitudinal direction along an upper surface thereof.

In addition, the support protrusion 426 may be provided with a rail coupling body 426a on the lower side so that it is connected to the sliding groove 424a and can slide.

In the elastic support 420 having the configuration described above, as the earth wall located on the upper side descends, the support protrusion 426 supporting the binding groove maintains its position, while the support triangle for relative movement ( 424) is driven while the lower part connected to the support column 422 is rotated while sliding in an outward direction.

Since the elastic support 420 having the configuration described above can be equally applied to the floor support 430, a description of the configuration of the floor support 430 will be omitted to avoid redundant description.

The data management server 200 having the configuration described above may be implemented on a development environment management system (not shown in the drawing for convenience of explanation).

In the development environment, a number of developers use a number of development systems for software development, and each development system can develop and directly manage software components and software under the developer's control. Each development system uses Trusted Platform Module (TPM) standard technology, which ensures that software components are only available on licensed development systems. The Trusted Platform Module (TPM) is a kind of security device and can generate and manage security keys for data encryption.

The development environment management system may limit a developer's authority for use of software components and perform security authentication for a development system used by the developer.

When receiving a software component creation or modification permission request message from the development system, the development environment management system may process the software component creation or modification permission request message by checking authority information of the corresponding development system.

Here, the software component may include at least one of a source code, a binary including debugging information, a pure binary not including debugging information, a document for detailed description of the code, and a process formula model for understanding the code. can

The authority information may include at least one of read authority to read software components, storage authority to create and modify and store software components, and rights adjustment authority to adjust authority information. When a software component is created or modified by any one development system that satisfies authority information, the development environment management system can store it and control it so that it can be shared by other development systems. This is because there are cases in which a module built by one development system must be used in another development system.

The development environment management system may build a database storing the creation or modification history of these software components. This is because it is possible to track how the value of a specific variable has changed step by step through the history information, and to understand how the specific variable affects the value change of any other variable.

Specifically, the development environment management system includes the type of software component, creation/modification of the corresponding software component, creation/modification date of the corresponding software component, frequency of creation/modification of the corresponding software component, and creation/modification of the corresponding software component. History information can be created including authority information of the development system.

The development environment management system may assign an index whenever history information is created and store it in a history information database.

In this case, the development environment management system may build a history information database for each type of software component. That is, the development environment management system can build a history information database according to the importance of the software component, and the history information database of the software component corresponding to the highest importance category is a database update target for storage space management, as described later. may be excluded.

Alternatively, the development environment management system may build a history information database for each creation/modification date of the software component. For example, the development environment management system may build a history information database of a specific date and exclude the corresponding history information database from a database update target.

Alternatively, the development environment management system may build a history information database for each authority information. For example, the development environment management system builds a database of history information of software components by the development system corresponding to the authority to adjust authority information considered as the highest authority information, and updates the database with the history information database. can be excluded from

As described above, the development environment management system may update the history information database for efficient storage space management.

Specifically, the development environment management system may update the history information database when the index of the history information database reaches a preset index.

For example, the development environment management system may divide all indexes of the history information database into three sections in ascending order.

The development environment management system can unconditionally delete history information corresponding to the section including the lowest index among the three sections. The history information corresponding to the corresponding section can be regarded as a long time since the date of creation/modification, and the possibility that the corresponding history information will be referred to again is low, so it can be deleted without conditions.

The development environment management system may update the history information corresponding to the middle section among the three sections by determining whether to delete or maintain the history information according to the type of the software component. That is, the development environment management system can classify the importance according to the type of software component, and among the history information corresponding to the middle section among the three sections, only the history information corresponding to the type of software component with the highest importance is maintained, and the rest The history information database may be updated by deleting all of the history information.

Alternatively, the development environment management system may update the history information corresponding to the middle section among the three sections by determining whether to delete or maintain the history information according to the generation/modification frequency of software components. That is, among the history information corresponding to the middle section among the three sections, the history information database may be updated by deleting all of the history information whose generation/modification frequency is higher than the preset reference frequency and maintaining the remaining history information.

Alternatively, the development environment management system may update the history information corresponding to the middle section among the three sections by determining whether to delete or maintain the history information according to the authority information of the development system. That is, among the history information corresponding to the middle section of the three sections, the history information that is the right to adjust the right to adjust the right information that is considered the highest right information is maintained as it is, and all the remaining history information is deleted. The history information database can be updated with .

The development environment management system can maintain history information corresponding to the section including the highest index among the three sections as it is. The history information corresponding to the corresponding section can be regarded as having a relatively recent date of creation/modification, and since the possibility that the corresponding history information will be referred to again is high, it can be maintained as it is.

The data management server 200, which performs the functions described above, is a manager management module (not shown in the drawings for convenience of description) to assist managers to efficiently operate managers for maintaining/repairing devices such as servers. can include

In one embodiment, the manager management module may generate a list of managers listed in order of input.

That is, in the manager management module, regardless of the manager's management ability, the manager entered first is selected as the first manager, and the manager entered next to the highest manager is selected as the next manager according to the order of being registered as a module, regardless of the manager's management ability. and the manager entered next to the next manager is recognized as the third manager.

In an embodiment, the manager management module may request a solution by selecting a manager to resolve the event from among managers included in a pre-generated manager list when a maintenance/maintenance event of a device occurs.

To this end, the manager management module should register manager information (eg, phone number, home address, etc.) of registered managers for each manager.

If the manager selected by the manager management module resolves the event, the manager is given points for resolving the event, but if the event is not resolved, other managers who will resolve the event are included in the previously created manager list. You will be asked to select one of the available administrators and resolve it.

The manager selection according to the above-described manager management module may be selected randomly without a separate order, but it is preferable to prioritize the manager selection as described below so as to respond more efficiently to event resolution.

The priorities of manager selection according to the manager management module are as follows.

First of all, the highest priority among managers included in the manager list (at this time, the highest priority in the initially created manager list is not selected according to the superiority or inferiority of the manager's management ability as described above, but simply according to the rank added to the manager list ) to select an administrator and request resolution of the event.

At this time, if the first selected manager fails to resolve the event or does not respond to the event resolution, the same resolution request is sent to the manager listed next in priority, and this process continues until the event is resolved. .

When a specific manager resolves the event, the manager selection process is stopped, and points are given to the manager for solving the event.

When point assignment is completed, the manager management module updates the minimum created manager list. At this time, the points given according to the resolution of the event are considered in determining the rank among managers.

Accordingly, in the minimum created manager list, even a manager who was positioned in a lower ranking position can rise to a higher rank due to points awarded according to the resolution of a specific event. Due to the resolution of the event, it can be pushed to the lower priority of the manager.

The data management server 200, which performs the functions described above, evaluates the capabilities of the manager using the points given to the managers included in the list generated by the manager management module described above. It may further include a manager evaluation module (not shown in the drawings for convenience of description) that allows a manager to select a manager more suitable for event resolution.

In one embodiment, the manager evaluation module may first add points of a predetermined score to a manager who has resolved the event according to the number of times the event has been resolved.

For example, if manager A participates in a repair event that occurred on a specific device and performs the event, he is given 10 points accordingly, and then participates in a repair event that occurred on another device and performs the event In one case, if 10 points are also given according to this, the ranking of A is determined through a total of 20 points.

However, at this time, the points awarded according to event resolution are not calculated equally for all events, and may be calculated differently for each event depending on the level of labor mobilized according to the expertise required for event resolution or event resolution.

For example, in the case of an event that does not require special labor or expertise, such as simply patrolling a device, a relatively low score of 1 is calculated for resolving the event, while general low-skill related tasks such as server replacement work If it is not expected to solve the problem and the input of a highly skilled person is required, this may correspond to calculating the level of points awarded according to the difficulty of maintenance, such as giving a relatively high score of 10 points.

At this time, if the same event as the existing device occurs for other devices of the same type, the event resolution request is preferentially transmitted to the manager who resolved the event of the existing device by the manager management module described above, and the manager who requested the event If the problem is solved, the manager evaluation module gives points accordingly.

In one embodiment, the above-described manager management module may separately create a manager list for each device so that a manager with more expertise in the corresponding device can be selected for each device.

The data management server 200 performing the functions described above, when new equipment is introduced into the system, the manager list previously created by the manager management module as described above so as to efficiently perform the new equipment. It may further include a list update module (not shown in the drawing for convenience of explanation) for updating.

In one embodiment, the list update module reads whether there is a newly introduced device, and if there is no newly introduced device, the previously created list is maintained as it is, and if there is a newly introduced device, the previously created list is updated. The following procedure is performed to perform the update.

First, the list update module reads whether or not a manager has prior knowledge related to a newly introduced device. At this time, the existence of prior knowledge can be determined by reading manager information stored by the manager management module.

If there is an administrator who has prior knowledge related to the newly introduced device in the previously created list, when an event occurs in the corresponding device, the corresponding administrator can send an event resolution request with top priority. The list to be created is updated by raising the rank of the manager who has the know-how in the device to the highest priority.

And, if there is no manager who has prior knowledge related to the newly introduced device in the previously created list, the equipment with the highest similarity to the corresponding device is read, and the prior knowledge related to the read device with the highest similarity is obtained. When an event occurs in the newly introduced equipment, the manager who has the know-how on the device with the highest similarity in the previously created list is given the highest priority so that the manager can send the event resolution request with the highest priority when an event occurs in the newly introduced device. By increasing the ranking with , the list to be created is updated.

Therefore, a manager with expertise in the device with the highest degree of similarity to the newly introduced device, even though he did not have expert knowledge of each newly introduced device, is required to perform maintenance, so that a new manager can be selected to reduce the trouble of scouting.

Although the preferred embodiments of the present invention have been shown and described above, the present invention is not limited to the specific embodiments described above, and is common in the art to which the present invention pertains without departing from the gist of the present invention claimed in the claims. Of course, various modifications are possible by those with knowledge of, and these modifications should not be individually understood from the technical spirit or prospect of the present invention.

10. How to provide grounded healthcare services based on personal data
100. Data collection server
200. Data management server
400. Shock absorbing part

Claims (2)

A data collection server that collects medical information stored in medical institutions, such as electronic medical records or disease records, and lifelog information stored in mobile or wearable devices; and
A data management server that standardizes the data collected by the data collection server, transmits it to individuals through an encoding-decoding process, and utilizes it as My Data;
The data collection server,
A personal device target unit that collects and integrates personal life record data from various personal devices;
The data management server,
a data standardization unit that receives medical record data from the data collection server and automatically standardizes different medical record methods for each medical institution using a standardization code when the medical record method used by each medical institution is stored;
a data encoding-decoding unit for converting and restoring data using character codes ASCII or Unicode to encrypt (encode) and restore (decode) the standardized data; and
Including; a data transmitter for transmitting the encrypted or restored data to the outside;
In the data management server,
Data may be stored in a physical storage device, which is stored inside a storage housing of a square column shape in a specific space,
The storage housing,
Including; a shock absorber at each lower corner to protect the storage device stored therein from external shock or vibration;
The shock absorber,
A main body portion formed in a cylindrical shape and having an elastic support and a floor support connected to each other;
Elastic supports installed along the upper part of the main body so as to be rotatable and inclined in a direction closer to other elastic supports from the upper side to the lower side to support the storage housing seated on the upper side; and
A plurality of bottom supports installed along the bottom of the main body so as to be rotatable and inclined in a direction closer to other floor supports from the lower side to the upper side to support the floor and the main body,
The body part,
A main body formed in a cylindrical shape and connected to the elastic support and the floor support to be rotatably installed in moving grooves formed at upper and lower portions inclinedly;
an elastic member installed between one side of the elastic support facing downward and the moving groove so that the elastic support can stand upright; and
An absorber plate installed along the entrance of the moving groove to absorb the shock caused by the collision with the elastic support;
The elastic support,
a support pillar having a lower portion connected to the movable groove so as to be rotatable, a lower slope supported by the elastic member, and a coupling groove for being rotatably coupled to the lower portion of the support triangle on the upper portion;
A support triangle having a flat upper surface and a lower part formed in a triangular shape with a narrower gap toward the lower side, and a lower portion connected to a coupling groove formed on an upper portion of the support column to be rotatably installed using a bolt and nut fastening means; and
In order to improve adhesion with the binding groove seated on the upper side, washboard-shaped irregularities formed of a material having elasticity are formed along the upper surface, and as the binding groove seated on the upper side moves up or down, the top of the support triangle A method for providing based healthcare services based on personal data, including a sliding support protrusion.
delete

Images