You don't have permission to do that.
You have to download the file here
This post is intended for both newcomers to Hedera, as well as those interested in use cases for hashgraph that touch a subject very close to me, physician credential verification. This particular use case is just as important for the future of healthcare use cases such as prevention of counterfeit drugs, transparency of pharmaceutical supply chains, and clinical trial management.
Disclosure before we proceed with this article: while I am not an Intiva Health investor (more in a second), I am a SAFT investor of Hedera.
With that out of the way, I would like to talk about how what Intiva Health is doing on hashgraph. Intiva Heath is an ICO that debuted last year. Its goal is to make healthcare credentialing more efficient and secure, and it’s built on Hedera and raised thru an ICO on ERC-20. I have been a physician in healthcare for the past 15 years between training and private practice. I have also been Chairman of the Credentialing Committee at 2 hospitals. In that role, every month, myself and a few colleagues would have to comb through the files of new incoming physicians and make sure they were not frauds, or had lingering lawsuits, or really were who they stated with experience and training. It took hours to look through 3" files and confirm every certificate of schooling, etc. We even had to do a background check, pay for a national database search and document it all in some file. It was time-consuming, mundane, insecure and stupid. I hated it. But I did it to participate in hospital governance. I spent at least 3-4 hours a month doing something that paid me nothing for being chairman. But my colleagues and I felt an ethical obligation to go through each and every file to make sure no bad actor was allowed 'privileges' to practice medicine at our hospital. And we all reminded ourselves periodically of those charlatans on American Greed or Dateline that were impostors as doctors and forged all of their medical certificates and document and ended up harming hundreds to thousands of people by their fraud.
Here's a recent article about just such a situation: https://www.dailymail.co.uk/news/article-5538455/Gold-Coast-fake-doctor-guilty-fraud-forging-medical-diploma.html* (edited)
Inefficiencies in this credentialing process are almost overwhelming! The typical credentialing process for doctors and healthcare professionals can take up to 3 months. So, in our job contracts, we have to give at least a 90-day notice to quit from an employer or risk being sued for damages and the costs incurred to find another doctor - but the typical notice is 2 weeks,
like most jobs require. Intiva Health is trying to fix this inefficient, insecure and slow process. Building a decentralized certification process on hashgraph, physicians can not only be certified in a secure way, but it can literally occur in SECONDS and not 3 months. Yeah. that's incredible! No more combing files for hours on a monthly basis by every hospital in the country to confirm a new doctor. A Hedera state proof showing timestamped "Active" status of ACLS, CPR, certifications, diplomas, licenses, malpractice Insurance, etc. All of this in seconds, and that doctor is approved based on a simple smart contract and the whole process can end with a cost of a few dollars. Right now, we charge $200 a person for the credentialing process. It is an amazing real-world value proposition that has a huge opportunity to reform another internet, record keeping and certification inefficient process.
That's the future I see with Hedera. Hope that helps!
Get a great introductory description of the concept of sharding, how performance is impacted by this partitioning method, and security implications of sharding in hashgraph.
Dr. Leemon Baird describes how hashgraph is asynchronous byzantine fault tolerant (aBFT) - what does that mean? This video offers a description of aBFT, how to realize this, and real-world examples. Dr. Baird also differentiates between aBFT and BFT.
Information about the author: https://www.linkedin.com/in/nikolaos-siafakas-71771953
Hash-hash.info is a financial audit platform --built using the latest HH-SDK -- that offers insights into wallet activity and keeps records of current account balances along with historical wallet snapshots.
How did we get involved with HH?
A few months back my colleague (Chris) pointed me to Hashgraph because he knew that it would interest me, due to Hashgraph's scientific angle, and he signed us up to take part in London's Hedera18 hackathon. We didn't know much about Hedera and I was reluctant to attend, but a few days before the Hackathon we had news of a successfully completed formal proof using the Coq proof assistant. I've been using Coq extensively a few years back and know how hard it is to get a formal proof, so these HH guys had to be taken seriously.
The theme of the Hackathon was micropayments and we entered with a deal-discovery dApp where users got rewarded for discovering and sharing great deals online. We got a working hack through, had a tremendous time at the event, made many great friends, but had to go back to our deal-dApp supporters and sponsors empty-handed because the prize-cow wasn't as easy of a target as we initially anticipated. The competition was fierce and the best entry -- payper -- went on to win the global H18 hackathon.
The deal-dApp went into the freezer and as Christmas approached my HH activity went into hibernation too. When checking back on HH in the last week of January, I noticed that a reward system was put up for reading articles on dailytimestamp.com. Once past the KYC, I saw my wallet balance slowly going up and was wondering how well other users are doing compared to my own repetitive compulsive clicking testing.
Beginning of hash-hash
A leader-board log is a straightforward thing to do with the SDK; a lot of effort has been put by the HH team to make HH coding as simple as possible. After a few exchanges with @GregScullard, who has a crystal ball with all HH coding answers written on it, we started printing leader-board scores into our system-log. Hash-hash.info was the next natural step where we shared that very same log with the rest of the community.
The initial response was quite encouraging and soon we started taking daily snapshots for over 5000 wallets; we're now monitoring and keeping a daily balance history for each wallet under our monitor. The community soon discovered that there are now enough data to start digging the dataset for more interesting answers.
What started as a leader board evolved into an audit tool just within a matter of days, which proves the power and ease of use of the SDK. The support of the community is impressive; we had numerous private messages that requested our account-id to transfer funds into it in order to keep the service running. It costs us a fee to monitor the accounts indeed, however that won't be an issue when mirror nodes become available. Nevertheless, we did have a 500 hBar donation, which allowed us increasing the frequency of our snapshots.
While donations do certainly help, the true HH way of doing things would be accepting micropayments using the native wallet for using the service. It' not just micropayments between end-users and the service that comes into play here but also micropayments among diverse services. We understand that as HH grows, it will be quite difficult and expensive for us to keep a record of each and every wallet and eventually we would have to buy and share data with similar services, like hbarscan.com, which aims to become a blockchain style scanner for HH.
The true value of payper, and this is why it's such an important contribution, is that it eventually could allow such collaborations to become frictionless and work towards building one coherent ecosystem. We still have a long way to go and we don't know yet what the future will bring, but we'll keep monitoring the progress of HH and will keep listening to the community.
And remember (miss-quoting Danny DeVito) you heard it here first, off the record, on the QT, and very... hash-hash.info.