CDC and WHO’s Coronavirus data now searchable via Acoer, powered by Hedera Hashgraph
Mance Harmon of Hedera Hashgraph
Acoer, developer of blockchain-enabled applications, announced that it is helping its healthcare and life sciences clients to easily track and visualise the Coronavirus outbreak with its HashLog data visualisation engine.
Built to interact in real-time with Hedera Hashgraph, the enterprise-grade distributed public ledger, the Coronavirus HashLog dashboard allows researchers, scientists, and journalists to easily understand the spread of the virus and trends over time, from a wide set of public data, including data from the Centre for Disease Control (CDC) and the World Health Organisation (WHO).
HashLog allows for the real-time visualisation of Coronavirus data and trends including:
- Confirmed cases
- Deaths and recoveries per hundred infections
- Trends over time
- Interactive views with dynamic sort and filtering capabilities
- Ability to download or extract directly from visualisation.
“There is a growing supply of data about the virus, but the information is not necessarily easy to visualise, consume, or extract in a simple way,” said Jim Nasr, CEO of Acoer. “With HashLog our objective is to make data collection automated, and data visualisation rich, dynamic, and intuitive. Particularly with my own public health background and tenure at the CDC, we are also huge believers that supporting public health is an incredibly important mission and as much as we can do, it is our responsibility to innovate to enhance it.”
“Healthcare and public health is a key area where Distributed Ledger Technologies (DLT) can provide computational trust, and serve as a source of truth for multiple parties to work from, delivering consistent, factual information across distributed communities,” said Mance Harmon, CEO of Hedera Hashgraph. “Acoer’s work to make this Coronavirus data so easy to visualise and understand is a great example of this, and we commend them for this innovative use of DLT for the public good.”
Comment on this article below or via Twitter @IoTGN