How AIBTRUST is putting medical data sovereignty back in patients' hands.

A consent layer the system has to ask permission from.

For decades, hospital records have been treated as institutional property. A patient signs a consent form once, on paper, and the data flows through systems they never see, to parties they never meet, for purposes they were never told about. Revocation is a phone call to a records department. Audit is a request that gets answered weeks later, if at all.

AIBTRUST's premise is that the consent layer itself belongs onchain. Patients grant access, scope it to a specific data type and recipient, and revoke it the moment they want to. Researchers, providers, and insurers all query against the same set of cryptographic permissions before any data moves. The audit trail is not promised by the operator. It is enforced by the chain.

Why a dedicated L1

A general-purpose blockchain is a public ledger. Medical-data infrastructure cannot be that. AIBTRUST's L1 on AvaCloud is permissioned: validators are known, transactions are private to the right parties, and KYC/KYB is enforced at the network layer.

• Patient-controlled. The patient holds the keys. No central authority can release records on their behalf.
• Revocable. Consent expires by default. Renewal is an explicit on-chain action.
• Per-purpose. Research access does not imply care access does not imply insurance access. Permissions are scoped at the data-type and use-case level.

What it unlocks for research

Pharma and academic research has always traded data quality for compliance friction. With a verifiable consent layer, researchers can recruit cohorts in days instead of quarters, and value can flow back to the patients whose data made the work possible.