Encrypted records
Record content is kept off-chain. The application is designed around encrypted storage rather than putting sensitive clinical data on a public ledger.
Patient-controlled health data
Privacy-first medical records on Solana.
CypherMed gives patients control over who can access their medical records through encrypted storage and verifiable authorization.
Working prototype · Solana Devnet · Do not use real patient data
CONTROLLED
ACCESS
ACCESS
Patient
owns the recordAuthorization
scoped permissionDoctor
approved viewerRecord
encrypted off-chainBuilt around a simple principle
Health data should move by consent, not default.Next.js Express PostgreSQL Anchor / SolanaThe problem
Medical data is deeply personal.
Records carry intimate details about a person’s life, but access is often fragmented across organizations and systems. Patients deserve a clear view of who can see their information.
01
Sensitive by nature
Medical records contain information that should not be shared casually or invisibly.
02
Fragmented by default
Care can span providers, labs, and institutions with different systems and workflows.
03
Consent should be visible
Patients need a practical way to understand and change access to their records.
The approach
Put access control in the patient’s hands.
CypherMed separates the medical record from the authorization layer: records stay off-chain and encrypted, while permissions and access events are handled through the application and Solana program.
Patient-controlled access
Patients can review access requests, grant scoped permissions, and revoke an active provider grant.
Authorization state
Solana is used as the protocol layer for authorization-related state and the project’s audit direction.
Auditable actions
Access requests, decisions, and record access are represented in the backend audit model for review.
How it works
Consent is the workflow.
A permission is explicit, scoped, and checked when a record is requested. Revocation changes the authorization boundary immediately.
01Patient creates a recordEncrypted data stays off-chain.
02Provider requests accessThe request is tied to a wallet identity.
03Patient grants permissionScope what the provider can view.
04Access is checkedEvery read is evaluated against the active grant.
05Patient can revokeFuture reads are denied after revocation.
Technical architecture
Infrastructure for consent.
Sensitive record content and authorization state have different jobs. CypherMed keeps those layers distinct.
01FrontendNext.js / React / Wallet Adapter
↓02Backend APINode.js / Express / Prisma
↓03Encryption + databaseOff-chain records / PostgreSQL
↓04Solana programRust / Anchor / authorization state
↓05Solana DevnetProtocol environment
Why Solana
Blockchain as an infrastructure layer.
CypherMed does not put medical record content on-chain. Solana provides a programmable environment for authorization-related protocol state and a foundation for verifiable activity, while the backend handles encrypted off-chain data.
◎
Devnet prototype
The current project is built and tested around Solana Devnet. This is an experimental prototype, not a production healthcare system.
Try the workflow
See CypherMed in action.
Connect a wallet, choose a patient or provider role, and explore the consent-driven application flow.
Open source
Built in the open.
Explore the application, Solana program, backend, and documentation on GitHub.
View CypherMed on GitHubgithub.comStaySafe020 / CypherMedSolana · Next.js · Express · PostgreSQLOpen repository