[Proposal setup] Proposal title

Please provide your proposal title

Health Data Anchoring and Consent Protocol on Cardano

[Proposal Summary] Budget Information

Enter the amount of funding you are requesting in ADA

200000

[Proposal Summary] Time

Please specify how many months you expect your project to last

10

[Proposal Summary] Translation Information

Please indicate if your proposal has been auto-translated

No

Original Language

en

[Proposal Summary] Problem Statement

What is the problem you want to solve?

Health data access is fragmented, unverifiable, and lacks secure consent. Clinics and patients have no reliable way to prove ownership, trace access, or audit how medical data is used.

[Proposal Summary] Supporting Documentation

Supporting links

• https://www.techstars.com/blog/program-news/introducing-the-2025-techstars-cardano-founder-catalyst-cohort
,
• https://www.uzimanexus.com
,
• https://www.linkedin.com/posts/techstars_2025-techstars-cardano-founder-catalyst-activity-7382424744463192064-R0sp/?utm_source=share&utm_medium=member_ios&rcm=ACoAABZP5vEBS26mqc7XpE0OvEd8rR5l-l6Bxo8
,
• https://h2i.utoronto.ca/startup/uzimanexus/
,
• https://www.linkedin.com/posts/ibizafrica-incubation-center_this-week-h2i-had-the-pleasure-of-hosting-activity-7398644668328083456-Co__?utm_source=share&utm_medium=member_android&rcm=ACoAACrbTl8BkCp5SpaCXX8_jv6Cp9F0Cll7hrI

[Proposal Summary] Project Dependencies

Does your project have any dependencies on other organizations, technical or otherwise?

No

Describe any dependencies or write 'No dependencies'

No dependencies

[Proposal Summary] Project Open Source

Will your project's outputs be fully open source?

No

Please provide details on the intellectual property (IP) status of your project outputs, including whether they will be released as open source or retained under another licence.

Proprietary elements, such as production datasets, clinical UX, and enterprise implementation playbooks, remain retained IP. In addition to, our core technology, innovations, and methodologies are protected intellectual property. Smart contracts, some SDK modules, and integration APIs will be publicly available to accelerate adoption. All on-chain logic and related libraries enabling consent, anchoring, and audit events will remain freely accessible.

[Theme Selection] Theme

Please choose the most relevant theme and tag related to the outcomes of your proposal

Healthcare

[Campaign Category] Category Questions

Describe what makes your idea innovative compared to what has been previously launched in the market (whether by you or others).

Healthcare systems globally face the same core issue: control of patient data lies with institutions, not individuals. Existing records systems rely on siloed databases that cannot be independently verified or shared safely. Even when blockchain is attempted, prior efforts have focused on tokenization, identity NFTs, or basic notarization, often without clear clinical context or real-world integration.

This proposal is fundamentally different.

A. Patient sovereignty enforced at the protocol layer

We treat the clinical record not as a single object, but as a sequence of attestations linked to verifiable consent. Instead of storing raw health data on-chain, we anchor:

• Data hash commitments
• Consent states
• Actor identities (provider vs. patient)
• Access events and revocation

This creates cryptographic accountability, while keeping sensitive data off-chain.

B. Designed for healthcare workflows, not blockchain theorists

Most blockchain health projects start from crypto-first assumptions and struggle to integrate with:

• EMR/PACS systems
• Telemedicine platforms
• Research registries
• Regulated diagnostic processes

UzimaNexus already integrates:

1. AI assisted ICD-11 diagnostics
2. DICOMweb medical imaging
3. FHIR-based health records
4. Consent-based user roles

This means Cardano becomes a trust layer, not a marketing add-on.

C. Active transaction generation

Previous Cardano health proposals anchored static documents or were pilots without sustained usage. Our design uses blockchain as a live transactional substrate, not a certificate store.

Every meaningful healthcare event becomes a verifiable on-chain action:

• A patient grants access → transaction
• A clinician reads imaging metadata → transaction
• Research participation event → transaction
• Revocation of access → transaction
• Second opinion request → transaction

This ensures network participation, not passive storage.

D. Clinical-grade auditing

Hospitals already spend millions on compliance, risk audits, and credentialing. We replace:

• Hard to follow e-mail threads
• Offline signatures
• Unverifiable access logs

With a tamper-proof clinical audit trail where every action has:

1. Proven source
2. Consent justification
3. Time boundary
4. Actor identity

E. Interoperability-first

We integrate Cardano next to clinical workflows, not instead of them.

This enables ecosystem growth—developers can adopt the anchor layer without reinventing healthcare.

Describe what your prototype or MVP will demonstrate, and where it can be accessed.

The MVP will demonstrate a working, testnet-deployed system enabling:

1. Patient-issued consent

Patients generate digital consent tokens with:

1. Time-bound access
2. Data category restrictions
3. Provider identity reference

2. Clinical event anchoring

When a clinician performs an action (e.g., viewing imaging metadata), the system stores:

1. A content hash
2. Consent reference
3. Provider identity
4. Timestamp

No clinical data is stored on-chain.

Only cryptographic proofs.

3. Consent revocation

Patients can revoke permissions and immediately restrict further actions.

Revocations are also on-chain for accountability.

4. Audit verification

A hospital or researcher can request a verifiable proof of access.

The system responds with a chain of anchored events.

Prototype availability

a) Code & Contracts:

1. GitHub repository
2. Plutus smart contract package
3. API reference microservice

b) Front-end Demo UI:

1. Web and Mobile app on testnet
2. User roles (patient/provider/admin)
3. Live workflow demonstration

c) Testnet deployment:

1. Cardano testnet endpoint
2. Test wallet scripts
3. Sample synthetic datasets

Healthcare partners and Cardano community members can interact directly, generate tokens, perform access-bound actions, and review audit histories.

Describe realistic measures of success, ideally with on-chain metrics.

A successful healthcare data integrity protocol must be measurable in a way that reflects real clinical value, not just technical achievement. UzimaNexus is designed with quantitative and qualitative KPIs that demonstrate adoption, trust, consent utilization, and interoperability across institutions.

A. Prototype Adoption

1. ≥1000 early users interacting with the demo
2. ≥75 healthcare testers (radiologists, research assistants, clinicians)

B. Transaction Activity

We expect sustained on-chain events generated by real workflows:

Metric Target (6–9 months)

Consent issuance ≥4,500

Data access logs ≥10,000

Revocation events. ≥2,000

Research participation ≥700

Each result represents authentic behavioral events, not vanity metrics.

C. Developer Uptake

1. ≥15 forks or integrations from third-party developers
2. ≥5 external teams integrating anchoring in their apps
3. Contributions to open SDK modules

D. Ecosystem Engagement

1. Community demos with Cardano health groups
2. Feedback-driven iterations
3. Shared learnings with Catalyst-funded health projects

E. Path to real-world pilot

A successful prototype unlocks:

1. African imaging clinics
2. Remote telemedicine networks
3. University research studies

These environments will produce steady transactional demand, benefiting the network.

[Your Project and Solution] Solution

Please describe your proposed solution and how it addresses the problem

UzimaNexus proposes a Cardano-based clinical data anchoring and patient consent protocol that enables healthcare institutions to create immutable, verifiable hashes of medical records on-chain while keeping actual medical files stored securely off-chain. Patients retain full ownership of their health data and use programmable access consent contracts to determine who can view specific documents and for what clinical purpose.

This approach solves the core failures of current systems—data loss, fragmentation, duplication, fraud, and lack of verifiable provenance—by replacing informal, trust-based exchanges with cryptographic proof of authenticity. Instead of hospitals or insurers calling each other, sending scans via social media, or emailing PDFs, clinical actors can reference an anchor hash tied to a patient wallet, time-stamped and publicly auditable on Cardano.

1. How It Works: Two-Layer Architecture

Layer 1: Clinical Data Anchoring (Cardano On-Chain)

When a hospital, lab, imaging center, or specialist creates a record, the system generates a cryptographic hash of the data. That hash is anchored to Cardano via a smart contract or transaction metadata. The anchor includes:

1. Patient DID or pseudo-identifier (ZK safe)
2. Institution identity signature
3. Timestamp and record type: e.g., MRI scan, lab test, diagnosis report
4. Optional reference to off-chain storage URI (encrypted location)

This delivers three guaranteed cryptographic properties:

1. Integrity: The record was not modified.
2. Immutability: Anchoring creates irreversible historical proof.
3. Provenance: The data came from a verified institution or clinician.

No medical data is stored on chain. Only proofs.

Layer 2: Consent Contracts

Patients or guardians control access through smart contracts that:

1. Specify which parties may access which records
2. Define scope: full record, summary, or specific diagnostic results
3. Define duration: one-time, time-bound, or permanent
4. Support revocation at any moment

A patient may, for example, allow:

“Dr. A can access MRI scans from Hospital X for 30 days.”

When a specialist requests access, the contract checks permission. If approved, the off-chain reference decrypts and serves the encrypted file through our API. Logs of these actions are written back to Cardano to maintain a transparent audit trail.

2. Why This Model Works in Healthcare

A. Legal alignment

1. Most regulations (GDPR, HIPAA, Kenya Data Protection Act) prohibit storing identifiable health data on chain.
2. Our model stores proofs, not data.
3. Patients remain owners: consent must be explicit and reversible.

B. Drives real adoption

Hospitals already use EMRs, HIS, RIS, LIS, PACS. Our SDK connects to those systems:

1. No need to replace existing infrastructure.
2. Anchoring becomes a background integrity layer.
3. Consent becomes the standard way to share externally.

Healthcare stakeholders don’t need to become blockchain experts. They simply:

1. authenticate
2. upload clinical records
3. anchor hashes
4. issue consent

3. What Problems We Solve

1. Provenance

Medical records currently travel across Kenya and Africa with zero cryptographic guarantees. Radiology CDs, printed lab reports, and emailed attachments are trivial to forge.

Cardano anchoring prevents fraud by tying each record to:

1. an institution identity
2. a timestamp
3. a clinician signature

Forgery becomes cryptographically detectable.

2. Fragmentation

Patients accumulate records across multiple providers, often in different cities. Even in digitized facilities, EMR systems are siloed.

Our protocol aggregates integrity proofs in a single patient-owned ledger, regardless of where care was provided.

3. Missing or Lost Data

Patients lose CDs, printed reports, and even patient files. Providers often demand repeat imaging.

Anchoring ensures:

1. the canonical version exists
2. institutions can verify authenticity remotely
3. files can be retrieved via patient consent instead of re-scanning

This directly lowers cost, risk, and radiation exposure.

4. Insurance & Claims Fraud

Insurance approvals are delayed because:

1. Documents are unverifiable
2. Hospitals must re-validate referrals
3. Documents can easily be forged

With anchored clinical proofs, insurers simply check:

Does this record hash match what was generated by the issuing provider?

If yes → claim validated.

If no → claim rejected instantly.

4. Why Cardano

A. Patient-first identity model

Cardano is uniquely aligned with verifiable credential frameworks and self-sovereign identity. Patients do not need to trust a central database—their identity anchors their history.

B. Finality and governance

Clinical anchors must be auditable years later:

1. treatment disputes
2. malpractice cases
3. organ donor eligibility
4. research history

Cardano’s immutability and governance stability provide long-term reliability.

C. Low fees + predictable cost

Healthcare operates at scale:

1. every lab
2. every visit
3. every referral

High fees kill adoption. Cardano ensures anchoring is affordable at thousands or millions of events.

5. Why Not Traditional Web2 or Private Blockchains

A conventional centralized cloud or hospital EMR still leaves core problems unsolved:

1. Admins can tamper with records
2. Ownership sits with institutions, not patients
3. Interoperability requires bilateral agreements
4. Vendors lock-in data
5. Fraud remains invisible
6. No standard for cross-provider verification

Private blockchains have one fatal flaw:

"Whoever controls the node controls the truth."

Cardano provides global neutrality:

1. No single hospital or ministry can edit history
2. The ledger persists beyond one vendor or political cycle

Healthcare consumers deserve a neutral infrastructure.

6. Why We Will Win Adoption

Because our model does not expect clinicians to change how they work.

1. They still upload records.
2. They still approve referrals.
3. They still interact through their EMR consoles.

Blockchain is invisible behind:

1. SDK integration
2. signed transactions
3. patient consent dashboards
4. automated verification flows

We solve real pain points, not hypothetical Web3 problems.

7. How This Solution Addresses the Core Problem

It replaces a trust-based health system with a verification-based system.

Right now:

• A document is accepted because it looks legitimate.

With UzimaNexus:

• A document is accepted because it is cryptographically valid.

That single shift eliminates:

1. forged imaging
2. fraudulent claims
3. lost records
4. duplicated tests
5. unverifiable referrals

And most importantly:

• patients become owners of their health data.

[Your Project and Solution] Impact

Please define the positive impact your project will have on the wider Cardano community

Our project creates a bridge between a high-demand real-world industry—healthcare—and the Cardano ecosystem. Healthcare data is among the most valuable and sensitive categories of human information. Today, it is fragmented, unverifiable, and siloed in back-of-house hospital systems that offer no guarantees of provenance or integrity. By introducing a patient-governed healthcare anchoring and consent protocol on Cardano, we materially expand the network’s utility into the largest information economy after finance.

A. Bringing verifiable, high-value transaction volume to Cardano

Healthcare is not a “nice to have” vertical—it is a constant, daily source of transactions:

1. Every lab test is an event
2. Every radiology scan is an event
3. Every referral is an event
4. Every insurance approval is an event
5. Every discharge summary is an event

Each of these can be cryptographically anchored:

→ one Cardano transaction per clinically relevant record or consent event.

This project does not rely on speculative DeFi volume or user incentives. Instead, it produces sustainable, organic demand driven by real-world clinical workflows. In regions like Africa, where digital health records are inconsistently managed, this can translate into millions of events per year once deployed at scale.

B. Expanding Cardano’s role beyond finance

Cardano has demonstrated excellence in DeFi, governance, on-chain identity, and proof-of-stake sustainability. However, real-world utility that touches lives daily is still underrepresented. Healthcare is the ultimate public infrastructure. When Cardano becomes the ledger of clinical integrity, medical authenticity, and patient consent, the ecosystem gains a socially important and politically defensible use case.

Unlike games, NFTs, or speculative markets, governments do not shut down infrastructure that reduces fraud, prevents unnecessary radiation exposure, protects patient rights, and improves insurance efficiency. This creates a policy tailwind rather than regulatory friction.

C. Positioning Cardano as the foundation for sovereign digital identity

Our approach strengthens Cardano’s identity position. Instead of DID being used only for wallet logins or membership verification, we tether DID to critical human documentation:

1. imaging
2. pathology
3. prescriptions
4. surgical notes
5. vaccination history

This expands identity from identity-as-access to identity-as-health-continuity. When patients use their keys to authorize medical record access, self-sovereign identity becomes tangible and life-relevant.

D. Demonstrating interoperability without centralization

Many blockchain initiatives try to replace existing hospital databases. That approach has failed for 10 years. Hospitals will not abandon their EMRs, LIS, RIS, or PACS systems. They will, however, layer tools that protect liability and reduce operational waste.

Our protocol integrates through SDK/API, allowing:

1. HIS → EMR → Cardano anchor
2. PACS → imaging hash → Cardano anchor
3. LIS → lab report hash → Cardano anchor

This allows healthcare institutions to keep their internal systems, while Cardano becomes the global truth layer.

This model is mass-adoptable because:

1. It fits into existing clinical workflows
2. It does not require blockchain literacy
3. It is invisible to clinicians
4. It turns health IT into a compliance asset

E. Developer opportunity

By publishing SDKs, smart contract templates, and integration documentation:

1. Third-party developers can build regional medical modules
2. Startups can build insurance dashboards and provider portals
3. Research institutions can create anonymized, opt-in datasets
4. AI developers can train on patient-consented records

We want Cardano engineers to extend our primitives into:

1. Oncology treatment record registries
2. Organ donation verification
3. Telemedicine EHR verification
4. Cross-border medical tourism
5. Public health surveillance

Every extension benefits Cardano and its user base.

F. Strengthening Cardano’s reputation globally

Healthcare systems in Africa, Latin America, India, and Southeast Asia are leapfrogging legacy Western architectures. They do not have entrenched incumbents like Epic, Cerner, or Allscripts. They are hungry for open, trustless, low-cost infrastructure.

If Cardano becomes their anchor:

1. Providers become indirect Cardano users
2. Hospitals become recurring on-chain participants
3. Entire governments may adopt Cardano as a registry layer

This gives Cardano:

1. Real-world economic stickiness
2. Regulatory legitimacy
3. Institutional partnerships that outlast hype cycles

[Your Project and Solution] Capabilities & Feasibility

What is your capability to deliver your project with high levels of trust and accountability? How do you intend to validate if your approach is feasible?

Delivering a healthcare-grade blockchain system requires not only technical maturity but also operational reliability, regulatory compliance, and an understanding of clinical workflows. UzimaNexus is positioned to deliver this project with trust because of our technical background, our institutional partnerships, and our real-world operating environment in Africa’s healthcare ecosystem.

1. Team Experience and Domain Readiness

UzimaNexus is led by professionals who have spent years working at the intersection of biomedical engineering, AI, blockchain infrastructure, and regulated data environments. Our engineering leadership has built digital health systems that integrate imaging modalities, HL7 FHIR, DICOMweb, and EMR/PACS ecosystems. This gives us practical insight into where blockchain fits—not as a buzzword, but as a trust layer that solves real bottlenecks in care delivery.

We deeply understand clinical realities:

1. Offline hospitals
2. Patients who physically carry records
3. Inconsistent EMR systems
4. Insurance fraud
5. Referral authenticity
6. Tampered or repeated diagnostic tests

Because we operate in markets where healthcare infrastructure is incomplete, adoption must be frictionless to succeed. Blockchain should be invisible to doctors and patients. This mindset shapes our delivery capability and accountability: we focus on anchoring data integrity and consent flows, not trying to replace existing health systems.

2. Real-World Deployment Experience

UzimaNexus has built and deployed working systems, not just demos. Our architecture already integrates:

1. backend microservices
2. imaging storage
3. structured datasets
4. a patient-facing mobile prototype
5. provider identity issuance

These experiences demonstrate feasibility beyond theory. Our core infrastructure has been designed to survive real hospital environments with poor connectivity, unreliable power, and diverse digital maturity levels. This ensures we are accountable to actual users, not just blockchain metrics.

3. Clinical and Institutional Relationships

We have already been onboarding healthcare institutions across Kenya and have managed to come up with a huge waitlist of over 500 facilities. These environments are extremely risk-averse: if systems fail, clinicians suffer and patients get hurt. Gaining early institutional partners is itself a credibility marker. Hospitals and diagnostic centers have chosen to collaborate with UzimaNexus because:

1. We respect regulatory boundaries
2. We understand their workflow pain points
3. We implement interoperability rather than replacing their systems
4. We do not force cryptocurrency use on doctors or patients

These partnerships provide real test beds to validate our approach.

4. Integration with Ethical and Compliance Frameworks

Healthcare demands more than innovation—it demands a compliance posture. Our team has designed systems guided by:

1. GDPR principles of data minimization
2. HIPAA privacy safeguards
3. African data localization norms
4. patient identity sovereignty
5. biometrics compliance

Blockchain does not absolve us of regulation; it increases the need for disciplined data governance because transactions are permanent.

UzimaNexus keeps payloads off-chain. We store only:

1. anonymized record hashes
2. consent state transitions
3. provider attestations
4. institutional signatures

No patient health data or images are stored on-chain. This demonstrates responsible engineering and legal defensibility.

5. Accountability Through the Techstars + Cardano Founder Catalyst Program

We are part of the Techstars + Cardano Founder Catalyst Program, which provides:

1. direct mentorship from protocol experts
2. startup governance best practices
3. investor readiness and accountability frameworks
4. technical sessions with Cardano engineering leaders

This is significant because it means:

1. We have already been vetted by the Cardano ecosystem
2. Our solution aligns with Cardano ecosystem priorities
3. We are trained to manage delivery risk, financial transparency, and stakeholder communication
4. We are prepared to escalate issues to technical advisors, Cardano core contributors, and industry partners

Participation in this program provides institutional credibility, not just narrative credibility. We understand how Cardano funding must be deployed responsibly and measurably.

6. Transparent Development and Verification Approach

We will operate with high accountability by providing:

1. Open-source smart contracts where feasible (MIT or Apache license)
2. A public testnet deployment
3. Regular milestone reporting
4. Usage transparency dashboards
5. On-chain queryable metrics
6. Clinical pilot updates

Transparency is not a feature—it is a governance design.

7. Milestone-Driven Deliverables

We will deliver in practical increments:

1. Smart Contract Alpha — onboarding logic, consent lifecycle
2. Anchoring SDK — hash creation and record attestations
3. Institutional Dashboard — track referrals, access control events
4. Patient Mobile App — transparency, audit trails, revocation controls

Each milestone is testable by third parties. Our cadence will allow both community and institutional stakeholders to validate progress.

8. Feasibility Validation Strategy

We validate feasibility at three layers:

A. Technical Feasibility

1. smart contracts deployed on pre-production networks
2. DICOMweb anchoring test suites
3. performance under realistic load (batch referrals, high-density imaging)
4. edge-case testing: revoked access, tampered data, mixed timestamp errors

B. Clinical Feasibility

1. real-world pilot in active healthcare environments
2. clinicians validating referrals at point of use
3. reduction of repeated scans
4. faster insurance claim validation
5. improved patient access to medical history

If a doctor doesn’t adopt the system, the system has failed—no matter how elegant the chain design is.

C. Ecosystem Feasibility

1. interoperability with Cardano identity primitives
2. compatibility with wallet infrastructure
3. developer ecosystem reuse of our APIs
4. open-source contribution activity

Blockchain projects fail when they treat users as transactions. We are treating users as lives.

9. Risk Awareness and Mitigation

We acknowledge real risk:

1. institutional resistance
2. regulatory ambiguity
3. clinical liability
4. infrastructure dependency
5. user literacy

Mitigations include:

1. no patient payload on-chain
2. cryptographic abstraction layer (no wallet management burden)
3. progressive pilots rather than mass rollout
4. capacity building with clinicians
5. disaster recovery provisions
6. offline caching for degraded environments

Risk is handled with documented, clinical-grade engineering discipline.

10. Trust Reinforced by Auditable Outcomes

Cardano’s decentralized infrastructure allows third parties to verify:

1. when a record was anchored
2. who issued a consent contract
3. who revoked it
4. how many institutions participated

We will expose this to the community through:

1. dashboards
2. block explorer tooling
3. developer access endpoints

If we fail to generate measurable anchor events and revocation events, the community will see it instantly.

Why We Will Succeed

We are not building a fantasy blockchain dream—we are solving a problem that costs African families money, dignity, and health outcomes daily. We are already in the field, and our architecture is designed around existing workflows.

Most importantly:

• We are accountable not because a grant requires it, but because patients’ lives depend on what we build.

[Milestones] Project Milestones

Milestone Title

Core Contract Architecture: Anchoring & Consent Lifecycle

Milestone Outputs

We will design and implement the core smart contract architecture that powers medical data anchoring and patient-controlled consent. This includes:

1. Anchoring Hash Contract – Registers cryptographic hashes for clinical data events (DICOM scans, lab reports, diagnostic notes, pathology).
2. Consent Lifecycle Contract – Provides patient-to-provider access delegation, revocation, expiration, and time-bounded access.
3. Provider Attestation Contract – Registers institutional signatures and verifies organizational authenticity.

Contracts will be designed for:

1. Permissionless verification
2. Off-chain medical data
3. Open future integration

Outputs also include:

1. Final contract schemas
2. Error models
3. State machines
4. On-chain transaction workflow diagrams
5. API contract for SDK

The deliverable is a working testnet deployment of the core protocol.

Acceptance Criteria

1. Smart contracts compile and deploy on Cardano testnet
2. Consent can be created, revoked, and reissued
3. Hash anchoring supports ≥ 1,000 simulated records
4. Provider issuance supports at least 100 unique identities
5. SDK exposes createHash(), grantAccess(), revokeAccess()
6. Full technical documentation delivered

Evidence of Completion

1. On-chain testnet addresses
2. Audit logs of contract deployment
3. GitHub repositories (MIT/Apache licensed code)
4. Test scripts
5. Video walkthrough of contract interactions
6. Technical whitepaper section describing core architecture

Delivery Month

2

Cost

60000

Progress

20 %

Milestone Title

SDK & Anchoring API Gateway for Health Systems

Milestone Outputs

We deliver the tooling layer that allows healthcare applications to interact with Cardano without needing blockchain expertise.

Deliverables:

1. TypeScript/Python SDK
2. REST gateway for EMR/PACS
3. Consent enforcement proxy service
4. Wallet abstraction layer
5. Schema validation (HL7 FHIR / DICOM metadata)
6. Institutional onboarding flow

The SDK must allow developers to:

1. Hash records locally
2. Submit hashes to the blockchain
3. Generate consents
4. Query consent validity
5. Verify provider authenticity

Developer Experience (DX):

1. Example integrations
2. Postman collection
3. OpenAPI 3.0 spec
4. Tutorials and sandbox environment

Acceptance Criteria

1. SDK published on GitHub & package managers
2. API supports 5+ example record types
3. Developer docs produced
4. End-to-end consent demo with testnet transactions
5. At least 2 EMR or radiology system simulated

Evidence of Completion

1. GitHub release
2. API documentation site
3. Testnet transaction IDs showing successful anchoring
4. SDK integration demo video
5. Mock clinical workflow results

Delivery Month

4

Cost

40000

Progress

30 %

Milestone Title

Mobile & Web App for Patient Consent and Audit Logging

Milestone Outputs

We deliver a patient-facing UI that makes sovereignty and transparency real.

Features:

1. View anchored clinical records (metadata only)
2. Approve or revoke provider requests
3. Consent expiration timers
4. Digital audit log of access events
5. Multi-language support
6. Clinician/Institution lookup

UX prioritizes:

1. Minimal technical complexity
2. Ledger-agnostic identity layer
3. Smooth onboarding for non-crypto users

Backend:

1. Institutional trust registry
2. Consent query endpoints
3. Identity abstraction

Acceptance Criteria

1. App builds on iOS & Android
2. Web dashboard fully functional
3. Consent approval + revocation
4. Audit log for ≥500 events
5. No PHI on-chain
6. User onboarding < 2 minutes
7. Demo Video and Live Tutorial

Evidence of Completion

1. Working builds (TestFlight/APK or staging link)
2. Repository commits
3. Testnet logs mapped to UI events
4. Demo scenarios
5. User test session summary

Delivery Month

6

Cost

30000

Progress

50 %

Milestone Title

Pilot: Clinical Anchoring + Real-World Consent Use Cases

Milestone Outputs

Deploy the system in real health environments.

Pilot objectives:

1. Validate referral authenticity
2. Reduce repeated imaging
3. Enable patient-controlled access
4. Measure fraud resistance
5. Collect clinician feedback

Institutions:

1. Diagnostic labs
2. Imaging centers
3. Clinics
4. Insurance or payers

Hardware + Workflow:

1. Anchoring gateway deployed
2. Patient mobile app used
3. 300–1,000 anchored records
4. 50–100 patient consents

Training:

1. Workshops with clinicians
2. SOPs for clinical staff
3. Rapid support channels

Acceptance Criteria

1. ≥ 300 real-world record anchors
2. ≥150 consent transactions (create or revoke)
3. ≥50 clinician users onboarded
4. Support requests < 48 hours
5. Institutional adoption reports

Evidence of Completion

1. Signed participation letters
2. Usage dashboard screenshots
3. Transaction lists (testnet → mainnet)
4. Pilot assessment summary
5. User satisfaction metrics
6. Recorded clinical feedback interviews

Delivery Month

8

Cost

40000

Progress

80 %

Milestone Title

Mainnet Release, Documentation & Ecosystem Toolkit

Milestone Outputs

Turn the project into a community-usable infrastructure layer.

Deliverables:

1. Mainnet deployment of contracts
2. Public API gateway
3. Technical documentation
4. Tutorials
5. Governance & escalation playbook
6. Developer onboarding program

Sustainability:

1. Institutional pricing model
2. Community support program
3. Healthcare integration roadmap

Acceptance Criteria

1. Fully deployed mainnet protocol
2. Public endpoints documented
3. 10+ independent developers using SDK
4. GitHub wiki + API reference
5. On-chain metrics dashboard live
6. Live Tutorials

Evidence of Completion

1. Mainnet contract addresses
2. API base URL
3. Developer testimonials
4. SDK usage statistics
5. Training video playlist

Delivery Month

9

Cost

20000

Progress

90 %

Milestone Title

Project Close-out, Reporting & System Verification

Milestone Outputs

Formal closure of the funded project.

Deliverables:

1. Final Impact Report
2. Governance Paper
3. Performance benchmarking
4. Independent community review
5. Final video presentation
6. Recommendations for future funding or research

We ensure long-term sustainability:

1. Recommendation for open governance
2. Roadmap for developer contributions
3. Compliance pathway for public health systems

Acceptance Criteria

1. All milestones approved
2. Measurable usage metrics
3. Final Report delivered
4. Final Video published
5. Open-source repositories fully updated
6. All Video Tutorials published

Evidence of Completion

1. Milestone approvals
2. Project close-out report
3. Published final video link
4. Cardano community post
5. Verified GitHub documentation

Delivery Month

10

Cost

10000

Progress

100 %

[Final Pitch] Budget & Costs

Please provide a cost breakdown of the proposed work and resources

The total project budget of 200,000 ADA is carefully structured to support nine months of intensive development, testing, clinical piloting, and open-source release of the UzimaNexus Cardano health-data anchoring and consent platform. The budget is designed to maximize efficiency, reduce delivery risk, and ensure the Cardano ecosystem receives long-term reusable infrastructure rather than one-off code. Each cost category reflects both the technical complexity of the solution and the real-world requirements of healthcare-grade systems.

1. Personnel Costs (114,000 ADA)

Personnel represents the largest portion of the budget because this project requires advanced engineering and specialized domain expertise. Healthcare systems, medical imaging pipelines, patient-consent architectures, cryptographic hashing, and smart-contract design all demand skilled contributors. These costs cover the core team actively developing the platform:

• CTO & Lead Blockchain Architect — responsible for Cardano smart contracts, metadata anchoring protocols, DICOM integration, and the overall system architecture. His leadership ensures that the technical direction is secure, scalable, and aligned with Cardano best practices.
• Backend and Platform Engineers (provided through Le-Bumba Technologies) — building the hospital-facing APIs, the anchoring gateway, microservices infrastructure, consent lifecycle logic, and DevOps pipelines required for continuous deployment and testnet operations.
• Frontend & UX Engineer (provided through Le-Bumba Technologies) — responsible for the patient-facing mobile/web dashboard and clinician interfaces, making consent controls intuitive and accessible for non-technical users while maintaining strict data-security guidelines.
• CEO & Product Lead — responsible for clinical workflow mapping, compliance strategy, user research, coordination with healthcare partners, and ensuring that the final solution fits real-world adoption environments.

This personnel allocation ensures that all layers — infrastructure, smart contracts, SDK, and user interfaces — are built by capable professionals with direct experience in healthcare systems and blockchain technologies.

2. Infrastructure, DevOps & Technical Tools (34,000 ADA)

A robust infrastructure foundation is necessary for both development and real-world healthcare usage. These funds cover:

1. Cloud hosting, compute environments, and secure storage for development, testing, and pilot deployment
2. CI/CD pipelines to ensure consistent delivery, test automation, and rapid bug fixing across all environments
3. DICOM and PACS tooling, which is essential for handling medical imaging metadata and ensuring compatibility with radiology and diagnostic centers
4. Security frameworks and testing, including encryption layers, access-control verification, and penetration testing
5. On-chain operational costs during development, including testnet/mirror fees, metadata pinning, and eventual mainnet deployment

This investment ensures that the UzimaNexus system is reliable, secure, compliant, and performant when operating within clinical environments.

3. Pilot Implementation and Real-World Validation (32,000 ADA)

A real-world clinical pilot is central to proving Cardano’s value in healthcare. This phase involves:

1. Integrating the system with partner clinics, diagnostic centers, and imaging facilities
2. Mapping actual patient and clinician workflows to Cardano interactions
3. Running structured user tests with clinicians, lab technicians, radiologists, and patients
4. Collecting metrics and qualitative feedback to refine the system

Pilot implementation is essential for demonstrating practical viability and generating evidence metrics, which will be important for both Cardano and healthcare stakeholders.

4. SDK, Documentation & Developer Tooling (10,000 ADA)

One of the most important deliverables for the Cardano ecosystem is the SDK that enables developers to integrate medical-data anchoring and consent features into their own applications. The budget covers:

1. Engineering time to write, publish, and maintain the UzimaNexus–Cardano SDK
2. Developer documentation, schema definitions, and example applications
3. Tutorials and reference integrations to reduce friction for future builders

This transforms the project into a foundational layer that can be reused by any developer working on clinical systems, insurance solutions, identity frameworks, or blockchain-based governance.

5. Contingency, Risk Mitigation & Regulatory Alignment (10,000 ADA)

Healthcare is a high-stakes sector with strict requirements. This category anticipates:

1. Unplanned infrastructure spikes
2. Additional compliance modeling
3. Emergency security reviews
4. Additional testnet deployments
5. Workflow adjustments during clinical pilot testing

A contingency reserve ensures the project remains on schedule and capable of handling unexpected but realistic scenarios without compromising quality or scope.

[Final Pitch] Value for Money

How does the cost of the project represent value for the Cardano ecosystem?

A. High Leverage for Cardano

This project builds reusable infrastructure for one of the most strategically important real-world sectors: digital health and medical imaging.

The system includes:

1. A Cardano-based consent & access control model
2. A pipeline for anchoring medical imaging metadata (DICOM) on Cardano
3. A provider-facing SDK accelerating adoption of Cardano in healthcare
4. Compliance-aligned architecture that can be reused across industries (legal, research, insurance, identity)

These components reduce future development costs for other builders by orders of magnitude.

B. Long-Term Ecosystem Utility

The following reusable outputs ensure compounding value:

1. Cardano Medical Data & Consent SDK

Open-source modules allow any Cardano developer to implement:

1. Patient-controlled data sharing
2. Delegated provider consent
3. Immutable imaging references
4. Consent revocation & event logging

This dramatically expands real-world utility applications.

2. Real-World Adoption in a Regulated Sector

Healthcare is one of the hardest industries to break into due to compliance, liability, and data-handling standards.

This project delivers:

1. Real clinical workflows
2. Real patient data flows (de-identified)
3. Real hospital integrations
4. A pilot environment that showcases Cardano’s actual utility

Cardano gains credibility and evidence of feasibility in a high-value industry.

C. Team Capability & Reduced Delivery Risk

Value for money is strengthened by the team’s background:

1. The team is part of the Techstars + Cardano Founder Catalyst Program, providing external validation, due diligence, and ecosystem accountability
2. CTO with experience building hospital systems, DICOM integrations, blockchain infrastructure
3. Engineering partner (Le-Bumba Technologies) with proven experience building enterprise systems
4. CEO with biomedical engineering background and healthcare deployment experience

This ensures the project is delivered efficiently, reliably, and with reduced risk.

D. High Return on Investment for Cardano

For every ADA spent, the ecosystem gains:

1. New on-chain clinical imaging use-case
2. Reusable compliance infrastructure
3. Developer SDKs
4. Hospital integrations
5. A real pilot demonstrating Cardano utility
6. An architecture replicable across Africa and emerging markets

This is a rare opportunity where cost is low, impact is high, and outputs are durable.

[Self-Assessment] Self-Assessment Checklist

I confirm that evidence of prior research, whitepaper, design, or proof-of-concept is provided.

Yes

I confirm that the proposal includes ecosystem research and uses the findings to either (a) justify its uniqueness over existing solutions or (b) demonstrate the value of its novel approach.

Yes

I confirm that the proposal demonstrates technical capability via verifiable in-house talent or a confirmed development partner (GitHub, LinkedIn, portfolio, etc.)

Yes

I confirm that the proposer and all team members are in good standing with prior Catalyst projects.

Yes

I confirm that the proposal clearly defines the problem and the value of the on-chain utility.

Yes

I confirm that the primary goal of the proposal is a working prototype deployed on at least a Cardano testnet.

Yes

I confirm that the proposal outlines a credible and clear technical plan and architecture.

Yes

I confirm that the budget and timeline (≤ 12 months) are realistic for the proposed work.

Yes

I confirm that the proposal includes a community engagement and feedback plan to amplify prototype adoption with the Cardano ecosystem.

Yes

I confirm that the budget is for future development only; excludes retroactive funding, incentives, giveaways, re-granting, or sub-treasuries.

Yes

[Required Acknowledgements] Consent & Confirmation

I Agree

Yes