We have always emphasized the importance of our medical data, but they are fragmented, island-shaped, and not in a continuous storage state.Therefore, these have caused our medical world to be a “shallow” medical world.
The traditional Internet is a protocol that follows the HTTP method as the mainstream. It specifies what kind of messages the client may send to the server and what kind of response it gets. We hardly have much control over the client. The vision that patients will become the core of the medical industry’s ecology is incompatible with the current technical architecture.We have fully experienced the benefits of HTTP, and many times some technologies have been relatively perfect, but the structure is still not in line with the future medical development trend.Centralized service providers have two famous examples of failures, one is GoogleHealth and the other is Microsoft Healthvault. These two major projects persisted for several years, that is, they were closed one after another in about 10 years.Weibo and blog sites developed at the same time, and some companies have done well so far. Why is it difficult for medical service providers to do it? We observe that patients have special needs for medical care. They are not satisfied with centralized service providers and maintain a more alert mentality. Patients need to store and control their “status”. If an error such as “404 not found” occurs, it will be difficult for the patient to continue to accumulate patiently, even if the frequency of 404 errors is very low. HTTP is a stateless protocol, that is, the server does not retain any state during transactions with customers, and cookies are also stored by the central server, and everyone knows that the weak state of cookies can be easily cleaned up. How to describe this feeling, it seems that the medical preparations provided by the Internet are all “soft”, easy to erase and unstable, and beyond control. However, medical care needs exactly the “hard core” things, including Filecoin’s “persistent preservation of human valuable data”, which is very much in line with the medical tone.Let’s make another vivid analogy. Now the components provided by the Internet are like butter bricks, and the real medical system needs real fire bricks.
In the state layer, we can choose better tools like filecoin or Crust, which can solve the problem of the state layer. In this way, the medical system will become more “hardcore”. Crust is also based on IPFS, and replacing the HTTP protocol based on content addressing is the most basic technical paradigm shift. When we are building object-oriented programming, our instance state can be fully reflected in object-oriented thinking. What we emphasize in the encapsulation of states and attributes is not a logical unit, but a physical encapsulation mapping relationship. We look at the structured design method from the object-oriented thinking,”The design idea adopted by the structured design method is not to take the object as a whole, but to extract the behaviors attached to the object, and to design and construct the application system with the function as the goal. This approach causes people to have to map the real world composed of objects to the space composed of functional modules when designing programs. This transformation process not only increases the complexity of program design, but also deviates from people’s basic ideas of observing and solving problems. “
Let’s look beyond the current classical object-oriented thinking. In fact, although classical object-oriented design is better than classical structuring, it still does not solve the core problem, that is, classical object-oriented still exists, “mapping the real world constituted by the object Into the space composed of functional modules”. The objects we build are unstable objects. This kind of instability at the bottom makes it difficult for everyone to build a “soil of trust.” Blockchain technology is no longer an auxiliary additive for medical care. In order to become the core infrastructure of future medical care, it will soon become an industrial-grade standard infrastructure in the near future.
With the emergence of smart contracts and virtual machines, code and data can be well packaged together. Classical object-oriented, we think it emphasizes logical encapsulation. In web3.0, we use the blockchain method to encapsulate the persistence layer. We can imagine our AI medical assistant running in our EVM or WASM. Other state layer projects such as Dfinity are also planned to be compatible with WASM. For the medical computing layer, this will build a complete layout. Our encrypted assets will be traded in a trusted and safe environment. Without the protection of property rights, there will be no prosperous market economy. This simple truth is very useful in the medical industry. Any knowledge of our assets, identity, NFT, originality, including the dynamic value of the body’s health, digital assets, etc., need to be sorted and accumulated one by one, and given the corresponding infrastructure to improve.In order to be able to build a complete application, we need to redesign these building blocks from the bottom up in a “hard core” way. With more freedom and autonomy contained in web3.0, we should be able to independently publish codes in an independent manner and maintain the individualization of the “containers” of individual medical systems. It is almost impossible for us in the earliest foxbase era. In the JAVA era, we may be living in an “illusion”. In the era of blockchain, it has finally begun to “hard core” and has its own territory. Just like everyone is not willing to spend a lot of money to renovate a rented house, the current system is very sloppy, and life is of course not so happy:
Blockchain will bring us the “exquisite” medical world where we begin to live a serious life.
To be continued…
