ClinicFlow

The description states that ClinicFlow is a workflow management tool for small clinics. It handles:

• Patient intake
• Doctor visits
• Approved document handover
• Follow-up scheduling

It is structured as a single workflow:

1. Assistant intake → Waiting for doctor → With doctor → Doctor approval → Ready to give to patient → Confirmed handover → Follow-up

The system includes:

• A browser-based staff application that runs locally on one computer
• A separate PostgreSQL Foundation for server-controlled staff roles, clinic separation, persistent sessions, and conflict resolution
• The staff app uses HTML, CSS, JavaScript, Node.js; the Foundation uses Node.js and PostgreSQL
• It does not require public internet at runtime

It is described as a "working hackathon prototype", not a full EMR or clinical system.

Evidence Self-reported by author. No independent verification.

The author states that ClinicFlow was built after speaking with doctors and assistants about how work moves through small clinics. The problem they identified was not a lack of software, but rather:

• Complicated screens
• Difficult training
• Concerns about sensitive information being placed online
• Another monthly subscription

They claim the tool is meant to make everyday clinic work simpler by:

• Keeping each visit, its documents, and follow-up in one clear flow
• Using reusable templates to reduce repetitive typing
• Making it easy to see what has already been done and what needs to happen next
• Reducing time spent searching for information and missed steps

The positioning is that ClinicFlow follows existing clinic workflows while keeping the doctor in control.

Evidence Self-reported. No external validation or customer testimonials.

The description states that ClinicFlow targets:

• Solo doctors
• Small clinic teams
• Staff who want something simple that follows their existing work patterns

It is designed for clinics where staff are concerned about:

• Complicated screens
• Difficult training
• Sensitive information being placed online
• Monthly subscriptions

The author notes that the tool runs locally on one computer and uses bundled assets, suggesting it's aimed at environments with limited internet access or privacy concerns.

Evidence Self-reported. No evidence of actual customer segmentation or targeting data.

There is no evidence provided about pricing, monetization, or business model in the description.

The author states that ClinicFlow is a "working hackathon prototype", not a full EMR or system approved for clinical use.

Evidence Not evidenced.

The project uses:

• Browser-based frontend with HTML, CSS, JavaScript
• Node.js backend
• PostgreSQL database
• Docker (for optional multi-user version)
• Codex and GPT-5.6 for development assistance

It includes:

• A local browser-based staff application
• A separate PostgreSQL Foundation for server-side safeguards
• Support for pausing visits without losing work
• Preservation of earlier approvals during corrections
• Handling of stale or conflicting actions through server/database authority
• Encrypted HTTPS with live updates (in optional version)
• Windows launcher for easier operation

The author mentions that the system was tested at four levels:

1. Individual workflow rules
2. Complete actions against PostgreSQL
3. Safe client behavior when something fails
4. Encrypted HTTPS with live updates

They also mention 300+ automated checks covering permissions, clinic separation, persistence, conflicting actions, privacy boundaries, and reliable refreshes.

Evidence Self-reported. No evidence of production deployment or scalability data.

The description states that ClinicFlow is a "working hackathon prototype", not a full EMR or system approved for clinical use.

It was submitted to the OpenAI 2026 hackathon on Devpost.

There is no evidence of:

• Revenue
• Customers
• Adoption
• Product-market fit
• Any form of traction beyond the prototype

Evidence Not evidenced.

The description does not provide any information about competitors or market positioning.

It does not mention existing solutions in the clinic workflow space, nor does it describe how ClinicFlow compares to them.

Evidence Not evidenced.

• Prototype-only: The system is described as a hackathon prototype with no real-world usage.
• No revenue or customers: There is no evidence of any monetization or customer base.
• Single developer: Only one team member (Lucas Salvana) is mentioned.
• Unverified claims: All descriptions are self-reported and unverified.
• Limited scope: The tool is focused on a narrow use case within small clinics, which may limit scalability.
• No production deployment: No evidence of live systems or infrastructure beyond local testing.

Evidence Self-reported. No external validation or data to support any claims.

1. What specific feedback did you receive from doctors and clinic staff during development?
2. How many clinics have expressed interest in using this tool, if any?
3. Are there plans for clinical validation or regulatory compliance?
4. What are the key assumptions about workflow behavior that need testing in real clinics?
5. Can you describe how the system would scale beyond a single local device?
6. Have you considered integration with existing EMR systems or health IT infrastructure?
7. What is your timeline for moving from prototype to production-ready software?

Inference These questions are based on the lack of evidence around traction, validation, and scalability in the description.