The problem zk_dynamic_insurance_nft_dapp solves

We Wanted a Painkiller, Not a Vitamin
We wanted to solve the analog way of paperwork in hospitals, the way insurance companies process paperwork, with blockchain.

So we implemented the insurance product as a zk dynamic nft
The Zk + dynamic(oracle) + NFT process is as follows.

1. After a patient finishes treatment at the hospital, the hospital sends data to the oracle for insurance processing.

2. the hospital data oracle recognizes this data and sends it to the dynamic NFT that the owner has.

3. Dynamic NFTs have different triggers depending on the owner's insurance conditions.
   Example)) In the case of dental insurance, insurance processing is done separately for each of the following cases.
   -Scaling
   -Implants

In the above case, the 6551 wallet transfers the stable coin to the hospital according to the insurance conditions.
Why do we need to use blockchain for medical data?
Because it's slower than web2 and comes with fees?

No.
Insurance is currently processed by human hands and the fees are more expensive than gas if you count the time.
As a result, the most critical issue is that personal health data cannot be entrusted to others, must be stored in trusted data, and must be visible only to me.

Challenges we ran into

While using protokit starterkit
I thought it would work if my existing node js version is 18 or higher, but I realized that if I don't use the nvm use command
I realized that nothing would work >> I then ran it with that command and solved it: nvm use v18~~~.

It took me a long time to even understand that o1js is a change from snarkyjs and that protokit is a high-level framework built on top of o1js.
I had to go through several documentation walkthroughs to understand the overall structure >> with the help of Mina Protocol support engineers.

It took me a lot of time to understand that Mina Protocol's dapp structure is calculated off-chain and only the last transaction history goes to L1 >> I understood it with the help of Mina Protocol's technical support engineers.

I thought the frontend was Next.js and the backend was graphql, but it was like a L2 chain, not a backend, and I didn't know about L2.

I had difficulty because I still lacked the concept of creating ZK NFTs.