Co-health

• 

  Cohealth logo

Inspiration

The delayed processing of claims and the economic cost involved in hiring people who will verify the claims implies that most health insurance claims take a lot of time and also result in reduced reimbursement. Covid 19 exacerbates this issue. I have seen friends struggle with this issue and aimed to build an prototype that addresses this problem.

What it does

Currently this is an active area of innovation in the insurance industry. So the focus is to connect a database of users stored by the insurance with an API interface via chainlink oracle to the smart contract. Twilio API is used for the external identification data. Claim data API is still under construction.

How I built it

I built a mock database of users with health data in postgres. A solidity contract was used for claim verification

Challenges I ran into

The main challenge was building the external adapter and integrating it as a chainlink node. Access to sample data from insurance companies is missing. However I received general hints from my cold calls with Aviva, Metlife

What I learned

Postgres database Understanding chainlink node Docker usage External API usage --> Learning how to use Chainlink from scratch to build an adapter was an excellent experience

What's next for Co-health

Goal is to get more tangible data and evaluate the proof of concept more effectively.

Built With

• docker
• javascript
• postgresql
• python
• solidity