Doctor Appointment Scheduling

[Proposal setup] Proposal title

Please provide your proposal title

Doctor Appointment Scheduling

[Proposal Summary] Time

Please specify how many months you expect your project to last

3

[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?

There is no open way for people to book medical appointments directly. Current systems are closed and fragmented, limiting access and making coordination difficult.

[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?

Yes

Please provide here more information on the open source status of your project outputs

Full code will be released on GitHub under the Apache 2.0 license, accompanied by complete documentation and step-by-step tutorials so developers can set up and use the library with minimal effort.

[Theme Selection] Theme

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

Healthcare

[Campaign Category] Category Questions

What is useful about your DApp within one of the specified industry or enterprise verticals?

This demo shows how medical appointments can move beyond today’s manual, isolated systems. By placing booking on a shared, programmable layer, visits become digital building blocks that other services can combine, automate, and build on. It’s a first step toward modular, interoperable healthcare workflows.

What exactly will you build? List the Compact contract(s) and key functions/proofs, the demo UI flow, Lace (Midnight) wallet integration, and your basic test plan.

UI screens:

1. Patient KYC (mock) - simple form with name, date of birth, optional insurance number
2. Doctor certificate generator (mock) - simple form with name, specialization, country, city
3. Doctor dashboard - connect Lace wallet, register doctor certificate, publish available calendar time slots
4. Patient booking UI - connect Lace wallet, choose time slot, pay and book

Public ledger data:

1. list of registered doctors
2. published time slots (doctor id, time, price, requirements hash, status).

Contracts/Circuits

• DoctorSchedule.compact
  • circuit: publish_time_slot
  • public inputs: doctor_id, slot_id, start_time, duraion, price, requirements_hash
  • witness (private inputs): doctor_cert, doctor_cert_sig, doctor_pubkey
  • checks: verifies the dotor certificate signature and that slot is free, then writes a new free time slot to the ledger
• AppointmentBooking.compact
  • circuit: book_time_slot
  • public inputs: slot_id, payment_amount, requirements_hash
  • witness (private inputs): patient_kyc_record, patient_kyc_sig, patient_pubkey, (optional) insurance and test results
  • checks: slot is free, payment amount matches the slot price patient KYC recort is correctly signed

Test plan:

• Unit test using compact testging patterns
• cli testing using cli wallet

How will other developers learn from and reuse your repo? Describe repo structure, README contents, docs/tutorials, test instructions, and extension points. Which developer personas benefit, and how will you gauge impact (forks, stars, issues, remixes)?

Repo structure

The repository follows the standard Midnight project layout (api/, doc/, ui/, cli/, contract/, README.md), making it easy for developers to navigate, extend, and reuse individual modules.

README contents

The README provides a complete overview of the project, setup instructions for the UI, CLI, and contracts, and a quick-start section so developers can run the demo within minutes.

Docs / tutorials

The docs/ directory includes step-by-step guides, architecture notes, full installation instructions, walkthroughs of both circuits, and a complete tutorial explaining how to deploy the contracts and test the booking flow locally.

Test instructions

A dedicated testing guide explains how to run all Compact unit tests, how to execute CLI tests, and how to perform the full end-to-end UI flow from doctor registration to patient booking.

Extension points

The codebase is structured so developers can easily extend it into a full medical booking system, integrate it with existing appointment platforms, or reuse its circuits as building blocks for other programmable-healthcare workflows.

Developer personas

Smart-contract developers, front-end engineers, full-stack builders, and researchers working on programmable healthcare can all reuse parts of the repo for their own prototypes, demos, or production integrations.

How impact will be measure

Adoption will be tracked through forks, GitHub stars, issues from external contributors, and derivative works or remixes that build new booking or identity flows on top of these contracts.

[Your Project and Solution] Solution

Please describe your proposed solution and how it addresses the problem

This solution is an open, decentralized doctor appointment scheduling system that runs on Midnight and does not depend on any closed, proprietary backend. Doctors with a valid signed certificate can publish available time slots, and any patient can privately book a visit using their wallet and a minimal eligibility proof. Patient identity and sensitive data stay off-chain, while only the slot, price, and booking status are public, so the marketplace is transparent but privacy-respecting. By turning medical visits into programmable on-ledger building blocks, the system can later be composed into richer healthcare workflows and integrated with other services.

[Your Project and Solution] Impact

Please define the positive impact your project will have on Midnight ecosystem

This project demonstrates a real-world use case that traditional public blockchains cannot support because they lack the privacy required for medical services. Doctor appointments are a familiar, highly demanded workflow already handled by many centralized platforms, and rebuilding this flow on Midnight shows how privacy-preserving smart contracts can support real services rather than tokens only. By turning medical appointments into programmable, composable on-chain assets, the project highlights Midnight’s strengths and gives the ecosystem a clear example of how sensitive real-world services can be traded, scheduled, and automated on a privacy-focused ledger. This helps developers imagine new applications and expands the practical scope of the Midnight platform.

[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?

I have been working with zero-knowledge technologies for more than two years, both as a developer and as an instructor. I built a zero-knowledge wallet using WebAuthn with Apple Touch ID and Face ID in Noir for the Aztec ecosystem https://github.com/zkworks-xyz/Quetzal, delivered training sessions on the Noir language, and contributed open-source tooling, including a ZK-focused Base64 decoding library: https://github.com/vlayer-xyz/noir-base64. I also worked on https://github.com/vlayer-xyz/vlayer a project using RISC Zero proofs and TLSNotary https://github.com/tlsnotary/tlsn web proofs. Beyond ZK, I have a long track record as a software engineer with experience in Rust, TypeScript, Java, Kotlin, Scala, and Haskell, working on open-source projects with active contributions on GitHub: https://github.com/akonior and I actively develop on Cardano. I hold a Master’s degree in Mathematics with many years of experience in software engineering. I also hold the Plutus Pioneer Certificate and Cardano Blockchain Certified Associate.

This background gives me confidence in delivering a working Midnight proof-of-concept with clear, testable components. The feasibility of the approach will be validated through Compact unit tests, CLI-based end-to-end scenarios, and a full UI flow running against a Midnight node.

[Final Pitch] Budget & Costs

Please provide a cost breakdown of the proposed work and resources

I plan to work on this project over a period of three months. The scope includes implementing the full proof-of-concept: UI screens, circuits, contract logic, Lace integration, and documentation. The work will cover design, development, integration, testing, and writing clear instructions for developers to run the demo locally. The requested budget is ~3300 $USDM per month for 3 months (total: 10,000 $USDM).

[Final Pitch] Value for Money

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

The cost is justified by the project’s role as a practical, end-to-end example of how Midnight can be used for real services rather than abstract demos. The implementation exercises all core components of the platform—private and public inputs, state transitions, signature verification, UI integration, and wallet interaction—so developers can reuse the patterns directly in their own work. The result is a concrete proof-of-concept that not only showcases Midnight’s capabilities but also provides a starting point for real businesses to build privacy-preserving booking and scheduling applications.

[Self-Assessment] Self-Assessment Checklist

I confirm that the proposal clearly provides a basic prototype reference application for one of the areas of interest.

Yes

I confirm that the proposal clearly defines which part of the developer journey it improves and how it makes building on Midnight easier and more productive.

Yes

I confirm that the proposal explicitly states the chosen permissive open-source license (e.g., MIT, Apache 2.0) and commits to a public code repository.

Yes

I confirm that the team provides evidence of their technical ability and experience in creating developer tools or high-quality technical content (e.g., GitHub, portfolio).

Yes

I confirm that a plan for creating and maintaining clear, comprehensive documentation is a core part of the proposal's scope.

Yes

I confirm that the budget and timeline (3 months) are realistic for delivering the proposed tool or resource.

Yes

[Required Acknowledgements] Consent & Confirmation

I Agree

Yes