Senior Retool/React Developer for Healthcare Command-Centre Prototype

@diektech

Hi — Elias here from Miami. This is a stabilization project rather than a new build, so my first priority would be making the existing prototype reliable before adding new functionality. The focus should be on completing workflows, strengthening RBAC, and ensuring the UI and database remain in sync. I have experience building operational dashboards, workflow-driven applications, React, TypeScript, PostgreSQL, REST APIs, role-based access control, and backend business logic. My approach is to audit the current architecture, identify incomplete workflows, remove technical debt, then implement patient episodes, tasks, alerts, care plans, audit history, and state transitions in small, testable milestones. I’m comfortable working with Retool, database transactions, and complex business workflows, delivering clean documentation and production-ready code. I prefer milestone-based delivery with regular demos and testing throughout the project. Q1 – Which Retool version and deployment model are you using (Cloud or Self-Hosted)? Q2 – Approximately what percentage of the prototype is already functional? Q3 – Do you already have a prioritized backlog of remaining features and bugs? Looking forward to hearing from you.

@kamran2012

Hey, I will finish and stabilise your Retool healthcare command-centre prototype, delivering database-backed patient episode workflows, role-based authorisation, alerts, care plans, audit history, and UI polish so it is demo-ready for investor and hospital presentations. On a similar Retool operational dashboard, I built a state machine for multi-step case management with full audit logging. One round of revisions is included at each milestone. Questions: 1) How many roles (e.g., clinician, coordinator, admin) need distinct permissions and views right now? 2) Is the existing PostgreSQL schema documented, or should I start with a schema audit? Share the Retool app link and I will review the current state and send a milestone breakdown tonight. Looking forward to talking through the details. Kamran

@ZahidBangash123

Hi, I have extensive experience building complex web applications using React, TypeScript, PostgreSQL, Node.js, Laravel, and workflow-driven systems. While my primary expertise is in custom full-stack development rather than Retool, I'm confident working with Retool-based applications, backend integrations, role-based access control, and database-driven workflows. My approach to stabilising your application would be: • Review the existing Retool app, database schema, and current workflows. • Identify and resolve bugs, incomplete features, and performance bottlenecks. • Complete patient episode workflows, tasks, alerts, care plans, orders, and audit history with proper database transactions. • Implement secure role-based access control and validate all backend operations. • Improve UI consistency, responsiveness, and overall user experience. • Perform end-to-end testing to ensure a stable, demonstration-ready application. My experience includes developing operational dashboards, ERP/CRM systems, healthcare-related workflows, and secure business applications using React, TypeScript, PostgreSQL, and REST APIs. I'm available to start immediately, can provide regular progress updates, and am comfortable working with either milestone-based or fixed-price contracts. After reviewing the current codebase, I can provide a realistic timeline and milestone breakdown. I look forward to discussing your project. Best regards, Muhammad Zahid

@anirudhat

Stabilising and completing an existing Retool healthcare command-centre — taking it from a strong visual prototype to solid database-backed workflows — is exactly the kind of work I do well. My approach starts with an audit of the current app, DB schema and queries, then I lock down the foundations: model the patient episode as a proper state machine (referral → 7–15 day episode → discharge), wrap multi-step writes in PostgreSQL transactions for integrity, and enforce role-based access at the backend with Retool resource permissions plus SQL-level checks so authorisation isn't just UI-hidden. From there I build out alerts, tasks, care plans, orders and an append-only audit history, and tighten the UI. I've worked with Retool, React/TypeScript and Postgres on operational dashboards like this. I keep work in reviewable milestones so you only pay as pieces land, and I'm available for daily check-ins. Can start immediately.

@Hubready

Hello!, I am a Florida-based senior software engineer(frontend, backend, ecommerce, etc) with 15+ years of experience in React, TypeScript, PostgreSQL, backend development, and building reliable data-heavy apps. I read your project description carefully, and I understand you need someone to complete and stabilise an existing healthcare command-centre prototype, not just add features, but make it solid and production-ready. I’ve worked on internal dashboards, workflow tools, and complex admin systems where clean data handling and stability matter just as much as the UI. My approach would be: review the current Retool/React setup and data flow, identify breakpoints, fix the core issues, stabilise the components and queries, then test the full workflow end to end so the prototype behaves consistently. Relevant work includes patient intake and operations dashboards, finance reporting portals with PostgreSQL backends, inventory control tools for mid-size ecommerce teams, and React-based admin consoles for internal SaaS platforms. Could you please clarify the following questions to help me better understand the project? 1) Which parts are already built, and what is still incomplete or unstable? 2) Are there specific healthcare workflows, permissions, or data rules that must be preserved? 3) Is the main priority UI polish, backend stability, query performance, or all three? If you want someone who will actually pay attention to the details and deliver something dependable, I’d

@rizwange4

I believe I am the perfect candidate for your Senior Retool/React Developer role. With exceptional experience in Retool App Builder, React, TypeScript, PostgreSQL, and healthcare workflow management, your project aligns extensively with my skills. To familiarize you with my relevant work, I've built numerous command-center prototypes that closely resemble your project, with a focus on database-backed workflows, role authorization, and operational dashboards. Additionally, I have a solid understanding of the intricate software needs of the healthcare industry including remote patient monitoring and regulated workflows. Having developed AI-powered CRM systems, AI-enhanced marketplaces and much more, I am extremely comfortable with complex software architecture such as the patient episode management and audit history components of your project. I guarantee a quality completion, stabilisation and continuous improvement to ensure a scalable and sustainable product. Let's connect to discuss timeline and pricing structure.

@toriquldev123

Hello There! I’m Md Toriqul Islam, and I’m excited to partner with you. I can dive into your Retool project immediately. I have rich experience in Retool, React, TypeScript, PostgreSQL, workflow automation, and enterprise dashboard development. I understand you need to stabilize and complete an existing healthcare command-centre prototype by implementing database-backed workflows, role-based access control, patient episode management, alerts, tasks, care plans, audit history, and UI refinements. My approach is to first audit the current architecture, resolve workflow and database issues, strengthen backend transactions and RBAC, then thoroughly test each module to deliver a reliable, maintainable demonstration-ready application. I’m available to start immediately and can work with either milestone-based or fixed-price delivery. I am skilled in Retool, React, TypeScript, PostgreSQL, RBAC, REST APIs, workflow design, and dashboard development. I’m ready to start immediately and would be happy to discuss your timeline and share relevant project examples. Looking forward to hearing from you. Best regards, Md Toriqul Islam

@denisSolution

Hi, I can stabilise the command-centre workflow by finalising the state machines and role-based access before polishing the UI. I’ve worked on a Retool/React patient-tracking dashboard that handled multi-stage approvals and audit trails—we had to tighten the PostgreSQL transaction batching to prevent race conditions during high-volume mock data loads. I’d approach this using a state-machine layer on top of Retool’s DB triggers because it keeps the workflows explicit and avoids tangled React event handlers. The biggest improvement will come from isolating each episode’s state so a single backend function handles all transitions without side effects. I’ll keep changes behind feature flags and add unit tests for the critical paths so we can roll back safely if something breaks. The result should be a stable prototype that looks ready for investor demos and won’t collapse under quick user-testing scenarios. Happy to jump in and review the current setup this week if you’re aligned. I can start right now. Thanks, Denis.

@emilesd617

Hi, I am a react developer with 8 years of rich experience in software development. I am familiar with React, TypeScript, Retool App Builder, PostgreSQL, Backend Development, Database Development, Role-Based Access Control (RBAC), and workflow-driven application development. I can help stabilize your existing Retool application by completing the database-backed workflows, strengthening role-based authorization, refining patient episode management, and improving the overall UI and application reliability. I'll focus on clean, maintainable code and a scalable architecture suitable for future enhancements and demonstrations. I'm an individual freelancer and can work on any time zone you want. Please contact me with the best time for you to have a quick chat. Looking forward to discussing more details. Thanks. Emile.

@a4logic

Hello, As a leading web service provider with years of experience in database and software development, my team and I are well-versed in the technologies required for this project. We have extensively worked on projects using Retool App Builder, React, TypeScript, PostgreSQL, and workflow/state-machine design - all skills crucial for the completion and stabilization of your healthcare command-centre prototype. Our approach to stabilizing an existing application is thorough and systematic. We will begin by comprehensively analyzing your prototype to identify areas that need improvement or fixing. Following that, we will prioritize the tasks and implement them progressively to ensure your product becomes robust, reliable, and aesthetically pleasing. To give you an overview of our capabilities in relation to this project, I will be happy to share examples of relevant Retool work we have completed. As for availability, we always welcome every opportunity to work on transformative projects like yours. Hence, we would reschedule or de-prioritize existing commitments if needed to align with your timeline. Regarding the milestone structure, we are open to customization as per your convenience and preference. Let's turn your healthcare vision into reality together! Thanks!

@naminghn

Hi there, I can immediately step in to stabilize and enhance your healthcare command-centre prototype by refining the existing workflows and improving the UI for better user experience. My experience with React, TypeScript, and PostgreSQL aligns well with your project's needs, particularly in database-backed functionalities and role-based access control. I’m ready to discuss my approach in greater detail and provide relevant Retool work examples when needed. Just let me know your preferred milestones and any other specifics, and we can finalize the scope and timeline together. Your satisfaction is my priority, and I guarantee that I will deliver you a high-quality result. Regards, Ali

@DeveloperStation

Hi, Stabilising an existing app is different from greenfield work, so the first thing I'd do is map the current state machine for a patient episode. Referral through a 7 to 15 day care episode to discharge has real state transitions, and most bugs in prototypes like this come from state and role authorisation being enforced in the UI but not at the database layer. I'd move that logic into PostgreSQL functions and transactions so audit history and role-based access hold up under demo pressure. I've built React and TypeScript products on Postgres before, including a dealership admin panel with role management, booking flows and enhanced backend logic on a Nuxt and Prisma stack. Since there's no history between us, we can start with a small milestone on the auth and episode workflow so you only release on working code. One question: is the Retool workflow engine already wired to the database, or are these steps still UI only? Adil

@mobiwebsolutions

✋ Hi There!!! ✋ The Goal of the project:- STABILISE AND COMPLETE THE RETOOL HEALTHCARE COMMAND-CENTRE PROTOTYPE WITH SECURE WORKFLOWS, ROLE CONTROL AND RELIABLE PATIENT EPISODE MANAGEMENT. I have carefully read your complete requirements and understand the existing Retool, React, TypeScript, PostgreSQL and database-backed workflow structure. With 9+ years experience as a full stack developer, I am confident I can strengthen and complete the prototype efficiently. 1. Retool and React workflows with PostgreSQL database transactions. 2. Role-based authorization, patient episodes, alerts, tasks and audit history. 3. UI improvements, testing, database management and full source code delivery. I have completed similar operational dashboards and workflow systems with complex backend logic, authentication and scalable database architecture. Looking forward to chat with you for make a deal Best Regards Elisha Mariam!

@alizain721

Hi, I will complete and stabilise your Retool + React TypeScript healthcare command centre prototype. The app as described uses Retool App Builder, React, TypeScript, Retool Database and PostgreSQL to model a hospital to home patient workflow covering referral through a 7 to 15 day care episode. I will finish database backed workflows, implement backend role based authorisation, patient episode state management, alerts, tasks, care plans, orders, audit history and UI quality improvements, using atomic Postgres transactions and compact state machine logic for predictable transitions. Built 6 Retool apps including a HomeCare Ops Dashboard that implemented patient episode workflows and role controls. Relevant examples include that HomeCare Ops Dashboard and a Remote Vitals Monitor demo that I used to tune alerting and audit trails. My approach is: audit schema and transaction boundaries, implement missing backend functions and role checks, add audit history and testing for critical flows, then polish UI for demo stability. I am available to start in 3 business days and can dedicate 20 hours per week. Estimated timeline 3 to 4 weeks to a demo ready, stable prototype. I prefer a three milestone structure: audit and rapid fixes, core workflow and backend authorisation, final UI polish and testing. If you share Retool editor access and a Postgres dev replica I will deliver a written list of blockers and a prioritized 2 week plan within 48 hours at no charge. Can you grant Retool editor access and a read only Postgres dev replica for the 48 hour review? Ali Zain

@Tacticssoft

Hello, I am an experienced Retool, React, TypeScript, and PostgreSQL developer with strong experience stabilising existing applications and building database-backed operational workflows. I can work within your existing Retool App Builder prototype and systematically complete the remaining functionality without disrupting the current UI and architecture. My experience includes role-based access control, backend functions, PostgreSQL transactions, workflow/state-machine logic, dashboards, alerts, task management, audit trails, and complex business workflows. For this healthcare command-centre prototype, I would first audit the current application, database schema, queries, permissions, and incomplete workflows to create a clear implementation priority list. I can then stabilise the core patient episode lifecycle, including referral, care plans, orders, alerts, tasks, episode progression, discharge, and audit history. I would also review the application for UI consistency, error handling, loading states, data integrity, and overall demonstration quality. I am available to start immediately and can provide regular progress updates with a milestone-based delivery plan. I would be happy to review the existing Retool application and provide a realistic timeline and milestone estimate after understanding the current completion level and remaining priorities.

@vladang

Getting a Retool prototype from "looks complete" to "behaves consistently" usually comes down to tightening the database-backed workflows and making sure role permissions and state transitions can't drift apart. That's where I'd start before adding anything new. My approach is to review the existing data model, backend functions and current workflow paths, then complete each patient episode flow with database transactions where consistency matters, especially around tasks, orders, alerts and audit history. For Retool, I prefer keeping business rules in backend functions rather than spreading logic across multiple component event handlers, which makes the app much easier to maintain as it grows. Could you share how role-based access is implemented today—Retool permissions, database policies, or custom backend logic? That will affect the cleanest way to finish the authorization layer. Please also share examples of the current Retool app so I can estimate the remaining work accurately, along with a milestone-based timeline and pricing.

@rakhshanz3

I'm Rakhshan, and I bring to the table a unique combination of strong academic background in Computer Science, a PhD in AI, and close to 20 years of professional experience in software engineering. My profile spans across various technical domains that align with your project needs, including Backend Development, PostgreSQL and React.js. My vision is to bring cutting-edge technology solutions within easy reach for every industry. Hence, I am particularly thrilled by projects with social value like this one. While I may not have extensive Retool experience to show you immediately, my skill set is versatile enough to adapt and utilise it effortlessly. The journey has taught me how to learn fast and implement effectively in any new technologyscape. Availability-wise, my schedule offers ample time for this project and we can discuss an estimated timeline based on mutual convenience. As far as the payment structure goes, I'm open to negotiation but generally prefer a milestone or fixed-price structure. To sum up why you should choose me: my deep expertise in backend development combined with my wide-ranging knowledge in healthcare app solutions such as complex operational dashboards are just what you need to wrap up & stabilize the existing prototype - perhaps even add more value centered features. Let's work together!

@mojjammil

Hi, I understand this type of project usually involves taking an impressive prototype and turning it into a reliable operational system where workflows, permissions, data consistency, and user actions all behave correctly. In healthcare-style command centres, even with demo data, the operational flow needs to feel realistic because users evaluate the system based on how well it handles real-world scenarios. I'd start by reviewing the existing Retool application structure, database schema, current workflows, and authentication logic to identify incomplete or unstable areas. Then I would stabilize the core data flows first, implement missing backend logic and permissions, and validate each workflow through realistic user journeys before improving the interface details. One key challenge will be ensuring patient episode states, tasks, alerts, and audit history remain consistent when multiple roles interact with the same workflow. 1. How are patient episodes currently expected to transition between stages, and are there specific state changes that require approval or additional validation from certain roles? 2. How should demo users with different roles experience data visibility and actions, especially when multiple care team members update the same patient workflow? If we're aligned, I can outline the implementation phases before kickoff. Best regards, Mojjammil

@kanika6665

Hi, I’ve reviewed your healthcare command-centre prototype and I’m confident I can complete and stabilise it with clean, reliable workflows and polished UI behavior. I have strong experience delivering Software Development projects with React.js and backend-driven applications, including role-based flows, stateful dashboards, data handling, and production-minded fixes that improve stability fast. For your build, I would audit the current Retool/React structure first, then complete patient episode workflows, backend authorization, alerts, tasks, care plans, orders, audit history, and database-backed logic in a maintainable way. I can also help tighten the interface for investor and controlled demo readiness. I’m available to begin promptly, and I’d suggest an 18-day milestone-based plan with an initial stabilization pass followed by workflow completion and QA. Could you share which workflow modules are currently functional versus blocked, so I can map the fastest stabilization path? Best regards, KANIKA - On-Time Project Delivery with Quality You Can Trust.