AMANGO

Problem

Patient records and hospital resources are managed in centralized systems where data integrity and access control depend entirely on trusting a single operator.

Why I built it

To use blockchain for tamper-evident patient data and decentralized access control, so records stay trustworthy without a single trusted intermediary.

Architecture

1. 1

   Identity and access

   Web3 wallets establish identity; access control is decentralized rather than gatekept by one server.

2. 2

   Patient records

   Records are stored with blockchain-anchored integrity guarantees in a Next.js + MongoDB application.

3. 3

   Resource management

   Hospital resources are tracked alongside patient data so availability and allocation stay consistent.

Engineering challenges

• Balancing on-chain integrity guarantees with the practical need for fast, queryable off-chain storage.
• Designing access control that is decentralized yet still usable for hospital staff workflows.

Lessons learned

• Blockchain earns its place when integrity and auditability are the core requirement — not as a default database.
• Healthcare UX must stay simple even when the underlying trust model is decentralized.

Screenshots