TWM574268U - Passive medical data exchanging cloud system based on blockchain concept - Google Patents

Abstract

A passive medical data exchanging cloud system based on blockchain concept are provided. The system includes a cloud server, a requester server and a data provider server. The cloud server includes a central processing unit and a register unit connected to the central processing unit; the requester server is connected with the cloud server through the internet and generates a request signal which is transmitted to the cloud server through the internet; the data provided server is connected to the cloud server through the internet and obtains the request signal from the cloud server for generating a data signal corresponding to the request signal which is transmitted to the cloud server and stored in the register unit by the central processing unit. Based on the system and the method provided by the instant disclosure, secure data exchange can be achieved.

Description

Passive cloud medical data exchange system based on blockchain concept

This creation is about a cloud medical data exchange system, especially a passive cloud medical data exchange system based on the concept of blockchain.

In response to the trend of international medical device management, the Food and Drug Administration (TFDA) announced on October 30, 104 that the UDI (Unique Device Identification, UDI specification) Rapid identification of medical devices at the use end (eg, within a medical facility) is enabled. As a result, the marking rate of the medical bar code (UDI code) can be significantly improved, which in turn helps the hospital to successfully import automatic identification (bar code) applications.

In addition to the above advantages, the medical device single identification system specification can be used to establish a bridge of information exchange between medical institutions, medical device suppliers, and government agencies. Specifically, through UDI regulations, medical institutions, medical device suppliers, and government agencies can track and trace medical devices by establishing a data exchange system, and confirm the circulation of medical devices, thereby further ensuring the use of medical devices. Security.

However, in the prior art, cloud data sharing or switching servers are often used for data exchange between two parties or multiple parties. Use existing cloud data sharing or exchange servo In the system of the device, a cloud server with active data exchange function is used as a cloud data sharing or exchange server, and these systems include a storage unit built in the cloud for storage for different users. Exchange of information.

In detail, for an existing system, when information sharing or information exchange is performed, the party requesting the information usually requests the party providing the information through the cloud server to obtain the information corresponding to the request. In other words, the cloud server actively shares and exchanges data. However, when the request for active data sharing and exchange is passed to the party providing the information (such as a medical institution), it is often necessary to increase the security concerns of data sharing and exchange through the verification of the network security mechanism of the party providing the information. .

In addition, when the information to be shared and exchanged is stored in a storage unit built in the cloud, the security risk will also be greatly increased. In particular, when a party providing information is a medical institution with a high level of information security needs, it is urgent to avoid long-term storage of data outside the medical institution's internal network, especially for other uses. In the cloud server accessed by the person.

Therefore, there is still a need to provide a cloud medical data exchange system to solve the above problems.

In view of the above technical problems, the present invention provides a passive cloud medical data exchange system based on a blockchain concept, which comprises a cloud server and a request server server. The cloud server includes a central processing unit and a temporary storage unit connected to the central processing unit. The requesting server is connected to the cloud server through a network, the requesting server generates a request message, and the request message is transmitted to the network to The cloud server. The data provider server is connected to the cloud server through a network, and the data provider server obtains the request message from the cloud server through a network, and generates a message corresponding to the request message. Information message. The data message is transmitted to the cloud server through a network, and is temporarily stored by the central processor in the temporary storage unit. The data message temporarily stored in the temporary storage unit is obtained by the requesting server through a network, so that the cloud server, the requesting server, and the data providing server have A data link.

The main technical means of this creation is that through the configuration of the cloud server, the request server and the data provider server, the cloud server is enabled by the passive cloud medical data exchange system based on the blockchain concept provided by the present creation. In the process of data exchange, it operates in a passive manner, and can avoid the risk caused by long-term storage of high-level confidential data in the cloud. In this way, the request server and the data provider server can be established by forming a block on the request server and the data provider server and forming a data link that is trusted by each other, thereby ensuring information security. Sharing and interaction synergy mechanism.

S‧‧‧ system

1‧‧‧Cloud Server

11‧‧‧Central processor

12‧‧‧Scratch unit

2‧‧‧Request server

21‧‧‧Supplier barcode information maintenance module

22‧‧‧Supplier Mailing Notification Management Module

23‧‧‧Supplier's warehouse inventory management module

3‧‧‧Data provider server

31‧‧‧ Medical institution barcode information maintenance module

32‧‧‧ Medical institutions consume modules

33‧‧‧ Medical institution warehouse inventory management module

1 is a functional block diagram of a system provided by an embodiment of the present invention; FIG. 2 is another functional block diagram of a system provided by the present embodiment; and FIG. 3 is a flow of a method provided by the present embodiment. Figure.

The following is a specific embodiment to illustrate the implementation of the "medical device identification and management system" disclosed in the present application, and those skilled in the art can understand the advantages and effects of the present invention by the contents disclosed in the present specification. This creation can be through other different specific embodiments The details of the present specification can be applied or applied, and various modifications and changes can be made without departing from the spirit of the present invention. In addition, the drawings of the present creation are only for a brief description, and are not depicted in actual dimensions, which will be described first. The following embodiments will further explain the related technical content of the present invention, but the disclosed content is not intended to limit the technical scope of the present creation.

First, please refer to Figure 1 and Figure 2. FIG. 1 is a functional block diagram of a passive cloud medical data exchange system S with a blockchain concept according to an embodiment of the present invention, and FIG. 2 is another functional block diagram of the system S provided by the present embodiment. . In detail, the functional block diagram of FIG. 2 further illustrates the functional modules that the system S can further include, as compared to FIG.

As shown in FIG. 1, the system S of the present creation includes a cloud server 1, a request server 2, and a data provider server 3. Both the requesting server 2 and the data provider server 3 are connected to the cloud server 1 via the network. In addition, as shown in FIG. 2, in the embodiment provided by the present creation, the cloud server 1 may be a passive data exchange server, and includes a central processing unit 11 and a temporary storage unit 12 connected to the central processing unit. In detail, the cloud server 1 is a cloud server that performs data exchange in a passive manner. In the present embodiment, the cloud server 1 does not actively generate or transmit a data exchange request, and does not actively take other requests. Download the data on the server side. The technical content of the data exchange by the cloud server 1 will be described later.

In addition, the cloud server 1 does not include the cloud database commonly used in the prior art. Different from the prior art, the system S provided by the present creation utilizes the blockchain concept, and uses a distributed database, that is, the database is dispersedly arranged on one or more data providers, instead of being set as The cloud server 1 of the data exchange center.

Please also refer to Figure 1 and Figure 2. As mentioned before, the requesting server 2 is through the network. The road is connected to the cloud server 1. The requesting server 2 can be used to generate a request message, and the request message is transmitted to the cloud server 1 via the network. On the other hand, the data provider server 3 is also connected to the cloud server 1 via the network. The data provider server 3 can be configured to acquire the request message from the cloud server 1 through the network, and generate a data message corresponding to the request message. Moreover, the data message is transmitted from the data provider server 3 to the cloud server 1 through the network, and is temporarily stored in the temporary storage unit 12 by the central processing unit 11 of the cloud server 1. The data message temporarily stored in the temporary storage unit 12 can be obtained by the requesting server 2 through the network.

As described above, in the passive cloud medical data exchange system S in the blockchain concept provided by the present embodiment, the requesting server 2 may be installed in a medical institution (such as a hospital or a clinic) and supplied. The information provider server 3 can be located in one of the medical institutions and the supplier base. In other words, when the requesting server 2 is set in the medical institution, the data provider server 3 can be set in the supplier base; and when the requesting server 2 is set in the supplier base, the data is provided. The server 3 can be installed in a medical institution. However, the present creation is not limited thereto. For example, in other embodiments, the requesting server 2 may be disposed in a government unit.

Specifically, both the requesting server 2 and the data provider server 3 can have the function of transmitting and receiving messages. The requesting server 2 is used to generate and transmit a request message. The request message is transmitted to the cloud server 1 via the network. For example, the request message generated by the requesting server 2 is used to provide corresponding data to the data provider server 3. For example, the request message can be used to request the data provider server 3 to provide information about the consumption situation of the medical device, the inventory situation, or other related usage conditions.

Next, the data provider server 3 automatically starts under a predetermined time interval. The request message stored in the temporary storage unit 12 of the cloud server 1 is carried. In other words, in the system S provided by the present embodiment, the cloud server 1 does not actively transmit the request message to the data provider server 3, but the data provider server 3 actively confirms the cloud server 3. Whether there is a request message, and if so, the data provider server 3 downloads the request message and processes it.

As described above, the data provider server 3 is configured to generate a corresponding data message according to the downloaded request message, and transmit the data message to the cloud server 1 and temporarily store it in the temporary storage unit by the central processing unit 11. 12. It is worth mentioning that the central processing unit 11 of the cloud server 1 can temporarily store the data information from the data providing end server 3 in the temporary storage unit 12, and periodically save the temporary storage in the temporary storage unit 12 according to a predetermined period. Information message. In detail, the cloud server 1 can provide a function of temporarily storing data messages. The length of the predetermined period can then be set by the user. For example, the central processing unit 11 of the cloud server 1 can clear (delete) the data information temporarily stored in the temporary storage unit 12 at midnight (0 o'clock) every day. In this way, the system S provided by the present embodiment can greatly reduce the time that the data message is left in the cloud (the temporary storage unit of the cloud server 1), thereby reducing the security risk.

In addition, the foregoing information information provided by the data provider server 3 may include at least one of a medical device consumption message, a medical device inventory message, and a medical device coded message. In other words, the data message can cover various related information about the medical device, and the data message can correspond to the request message provided by the requesting server 2. For example, when the request message provided by the requesting server 2 is used to request information about the inventory of a particular medical device, the data message provided by the data provider server 3 may include a medical device inventory message. In this way, the requesting server 2 can perform other related operations according to the medical equipment inventory information, for example, scheduling the replenishment schedule of the medical equipment.

Please refer to Figure 1 and Figure 2 again. Through the design of the cloud server 1, the request server 2 and the data provider server 3, the cloud server 1, the request server 2 and the data provider 3 have a data link. In fact, through the passive data exchange server, that is, the setting of the cloud server 1, the requesting server 2 and the data providing server 3 can achieve the effect of data transmission or data exchange.

Next, one of the requesting server 2 and the data provider server 3 includes a supplier barcode information maintenance module, a supplier mailing position notification management module, and a supplier mailing stock management module, and the request side servo The other of the device 2 and the data provider server 3 includes a medical institution barcode information maintenance module, a medical institution consumption module, and a medical institution warehouse inventory management module.

For example, as shown in FIG. 2, the requesting server 2 may further include a supplier barcode information maintenance module 21, a supplier mailing position notification management module 22, and a supplier mailing stock management module 23, and the data is provided. The server 3 includes a medical institution barcode information maintenance module 31, a medical institution consumption module 32, and a medical institution warehouse inventory management module 33. The above-mentioned data providing modules with different functions in the server 3 can be used to manage different materials in the medical institution. However, it is worth noting that the content shown in FIG. 2 is only one of the implementation aspects of the present creation, and the creation is not limited thereto.

Next, the passive cloud medical data exchange method based on the concept of blockchain provided by this creation will be described.

Please refer to Figure 3. Figure 3 shows a flow chart of the method provided by the present creative embodiment. As shown in FIG. 3, the passive cloud medical data exchange method based on the blockchain concept provided by the present embodiment includes the following steps: generating a request message through the request server 2, and requesting the message The information is transmitted to the cloud server 1 through the network, wherein the cloud server 1 includes a central processing unit 11 and a temporary storage unit 12 connected to the central processing unit 11 (step S100); through the data providing end server 3 to pass through the network The path from the cloud server 1 acquires the request message and generates a data message corresponding to the request message, wherein the data provider server 3 transmits the data message to the cloud server 1 through the network, and the data message is received by the central processing unit 11 Temporarily stored in the temporary storage unit 12 (step S102); and through the requesting server 2 to download the data information temporarily stored in the temporary storage unit 12 from the cloud server 1 through the network, so that the cloud server 1, the request server 2 A data link is formed with the data provider server 3 (step S104).

Specifically, the passive cloud medical data exchange method provided by the present embodiment can be performed by the passive cloud medical data exchange system S described above in the concept of a blockchain. Therefore, the respective components or components used in the method can be referred to the foregoing description and related drawings.

The passive cloud medical data exchange method based on the blockchain concept provided by the present creative embodiment will be described below with reference to the specific steps. In a specific embodiment, the requesting server 2 is disposed in the supplier base, and the data provider server 3 is disposed in the medical institution. When the supplier wants to exchange information with the medical institution, for example, if he wants to obtain the inventory status of the specific medical equipment in the medical institution, the passive cloud medical data exchange based on the blockchain concept provided by the creation can be used. System S and method achieve the goal. However, this creation is not limited to this.

First, in step S100, the requesting server 2 generates a request message and transmits the request message to the cloud server 1 via the network. In a particular embodiment, the vendor generates a request message via the requesting server 2. Then, the request message is served by the request side through the network. The device 2 transmits to the cloud server 1. At this time, the cloud server 1 receives the request message, and the central processing unit 11 can store the request message in the temporary storage unit 12.

As described above, since the cloud server 1 is a passive data exchange server in this creation, it does not actively transmit the request message to the data provider server 3. In contrast, in step S102, the medical institution obtains the request message from the cloud server 1 (for example, the temporary storage unit 12 of the cloud server 1) through the network provider server 3. In this way, the data provider server 3 actively confirms whether the cloud server 1 has a request message through the network.

In addition, the method provided in this embodiment may further include the following steps: the data provider server 3 automatically downloads the request message stored in the temporary storage unit 12 of the cloud server 1 according to a predetermined time interval. For example, the medical information provider server in the medical institution can confirm whether the cloud server 1 has a request message according to a predetermined time interval, for example, every 6 hours, every 8 hours, every 12 hours or every 24 hours, if any, The request message is downloaded after confirmation. In other words, in the present creation, instead of actively sending a request message to the data provider server 3 through the requesting server 2, the request message is first stored in the cloud (cloud server 1), and then provided by the data. The terminal server 3 actively confirms and downloads the request message. In this way, the method and system S provided by the present embodiment can effectively improve the security of information exchange and simplify the complexity of the data program. For example, this creation can eliminate the techniques commonly used in the prior art, such as the use of complex identity authentication programs, to achieve fast, secure, and efficient data exchange.

Next, in the same step S102, the data provider server 3 generates a corresponding data message according to the downloaded request message. In fact, after the data provider server 3 downloads the request message from the cloud server 1, according to the content of the request message, other information modules or databases in the medical institution can generate corresponding data, and then the data provider Server 3 generates data The message is sent to Cloud Server 1 over the network. The central processing unit 12 of the cloud server 1 temporarily stores the received data message in the temporary storage unit 12. As mentioned above, the information message includes at least one of a medical device consumption message, a medical device inventory message, and a medical device code message. The data provider server 3 may include a medical institution barcode information maintenance module 31, a medical institution consumption module 32, and a medical institution warehouse inventory management module 33 for respectively providing materials of the same or different contents. However, this creation is limited to this.

In other words, in step S102, the data message provided by the data provider server 3 is temporarily stored in the cloud server 1, and is not directly transmitted by the data provider server 3 to the requesting server 2. The cloud server 1 can establish a relay station for data exchange between the requesting server 2 and the data providing server 3.

It is to be noted that the passive cloud medical data exchange method based on the blockchain concept provided by the present embodiment further includes the following steps: the central processing unit 11 periodically clears the data temporarily stored in the temporary storage area 12 according to a predetermined period. message. In detail, one of the technical means of the present creative embodiment includes temporarily storing the data message in the cloud server 1. Compared with the prior art to establish a cloud database in the cloud, the technical means of the present creative embodiment can ensure information security.

For example, the central processing unit 11 of the cloud server 1 can clear (delete) the data information temporarily stored in the temporary storage unit 12 at midnight (0 o'clock) every day. Thus, the predetermined period can be every 4 hours, every 6 hours, every 8 hours, every 12 hours, or every 24 hours. In this way, the system S provided by the present embodiment can greatly reduce the time that the data message is left in the cloud (the temporary storage unit of the cloud server 1), thereby reducing the security risk.

Next, please refer to Figure 3 again. In step S104, the provider can download the data temporarily stored in the temporary storage unit 12 from the cloud server 1 through the request server 2 interest. In other words, the requesting server 2 actively confirms whether the temporary storage unit 12 of the cloud server 1 has a data message. In this way, a data link is formed between the cloud server 1, the request server 2 and the data provider server 3.

The above is only one of the specific embodiments of the present creation. In other specific embodiments, the requesting server 2 may also be disposed in a government unit, so that the government unit can monitor the specific medical treatment in the medical institution by the system S and the method provided by the present creative embodiment. The effect of the use of equipment (or drugs). However, this creation is not limited to this.

[Effective effect of the embodiment]

In summary, the creative effect of the present invention is that the passive cloud medical data exchange system S based on the blockchain concept provided by the present embodiment can pass the "cloud server 1" and the "request server 2". And the design of the "data provider server 3" and the technical means to cooperate with each other, and exchange data in a safer environment.

In detail, the system S provided by the present embodiment uses a passive data exchange server as the cloud server 1, and the request message provided by the request server 2 is stored in the cloud server 1 for the data providing end. The server 3 actively confirms and downloads, and the data message provided by the data provider server 3 is temporarily stored in the cloud server 1 for downloading by the requesting server 2 to obtain. Further, the data information temporarily stored in the cloud server 1 can be periodically cleared according to a predetermined period, thereby further enhancing the security of the information.

It is worth emphasizing that this creation uses the concept of blockchain and then uses a decentralized database, meaning that the data in the database is stored on different users before being shared (for example, stored in a set of data supply) Within the unit of the server, and these data need to be transmitted When it is lost, exchanged or shared, it is obtained by the cloud server in a passive manner and further obtained by the data requesting server.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the scope of the patents of the present invention. Therefore, equivalent technical changes made using the present specification and drawings are included in the scope of protection of the present invention.

Claims (6)

A passive cloud medical data exchange system based on a blockchain concept, comprising: a cloud server, the cloud server comprising a central processor and a temporary storage unit connected to the central processor; a requesting end a server, which is connected to the cloud server through a network, the requesting server generates a request message, wherein the request message is transmitted to the cloud server through a network; and a data providing a server, which is connected to the cloud server through a network, and the data provider server obtains the request message from the cloud server through a network, and generates a message corresponding to the request message. a data message, wherein the data message is transmitted to the cloud server via a network, and temporarily stored by the central processor in the temporary storage unit; wherein the temporary storage in the temporary storage unit The data message is obtained by the requesting server through the network, so that the cloud server, the requesting server, and the data providing server have a data link The passive cloud medical data exchange system according to the concept of the blockchain, wherein the cloud server is a passive data exchange server, and the request server is disposed in a medical institution and In one of the supplier locations, and the data provider server is disposed in the medical institution and the other of the supplier locations. The passive cloud medical data exchange system according to the concept of the blockchain, wherein the central processor periodically clears the data information temporarily stored in the temporary storage unit according to a predetermined period. A passive cloud medical data exchange system based on the concept of a blockchain as described in claim 1 The data provider server automatically downloads the request message stored in the temporary storage unit of the cloud server according to a predetermined time interval. The passive cloud medical data exchange system based on the blockchain concept of claim 1, wherein the data message comprises at least one of a medical device consumption message, a medical device inventory message, and a medical device coded message. . The passive cloud medical data exchange system in the concept of a blockchain according to claim 1, wherein one of the request server and the data provider server includes a supplier barcode information maintenance module. a supplier mailing notification management module and a supplier mailing stock management module, and the request server and the other of the data providing server include a medical institution barcode information maintenance module , a medical institution's consumption module and a medical institution's warehouse inventory management module.